yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] bdr127:
T-Mobile blocks UDP, which is the default protocol for most VPNs. Try using TCP instead. It's usually slower than UDP, but at least it works.

EDIT: To be more specific, I think it's that they block UDP on 5G. If you were to force 4G LTE, then it might work with UDP.

EDIT 2: On second thought, maybe UDP is also blocked on 4G LTE (and it's 3G that is clear).... It's been a long time since I tested it out, and I can't quite remember for certain. :p
[Google Pixel 7] skyfall1235:
Hi all! this is my first post here, glad to join the community. I need help getting my banking app to working after unlocking my bootloader and using Magisk.

the banking app i am trying to get working in question is the SECU app for NC.

i am on the most recent update of android as of may 5th

build AP1A.240505.005

So far, my first boot loader unlock went successfully and I've gotten many patches working, but when trying to open this app, I've had a myriad of problems. here are my current attempts to get this to work.

1st attempt - attempt to open app after unlocking bootloader. Failed: "This app is not supported on rooted or emulated devices"

2nd attempt - add to deny list in magisk and enforce deny list. Failed: "This app is not supported on rooted or emulated devices"

3rd attempt - installed play integrity fix and ran. Failed: "This app is not supported on rooted or emulated devices"

4th attempt - installed hide my applist, the LSPose module. failed. did not note outcome.

5th attempt - Installed Shamiko. failed, did not note outcome.

done combinations of hide my applist and shamiko, shamiko and play integrity fix, and others. Nothing has gotten me into the app.

So far, i have only come across 2 screens. the "This device cannot be ran rooted or emulated device" screen, or a screen where the app launches but only displays the app icon and the default app color background.
[Google Pixel 7] bdr127:
I haven't used it, but some people report good results with Zygisk Assistant.

Going forward, however, you'll need to uninstall LSPosed and really clean up after it. From what I understand, some of the modules for LSPosed leave behind quite a bit of residual files and directories that some apps detect. If you've just uninstalled it, that might not be enough.
[Google Pixel 7] swangjang:
When using Shamiko, turn off "Enforce DenyList".

Also, did you clear the app data/cache and reboot?
[Google Pixel 7] skyfall1235:
I have attempted both with enforce denylist off and force deny list on. i did these tests by deleting the banking app, installing the module and rebooting, and then reinstalling the app.
[Google Pixel 7] skyfall1235:
Ok, so i have attempted to follow this instruction to the letter. I removed LSPosed and all modules in it, fully deleted them from internal storage where any of the modules or LSPosed itself was. i cleared the cache of the banking app, then deleted it. then i installed zygist assistant, i then did a full reboot, redownloaded the banking app, and then launched it.

i received the same error, "This app is not supported on rooted or emulated devices". any other suggestions would be greatly encouraged.
[Google Pixel 7] bdr127:
Maybe try asking in the Zygisk Assistant thread:

[MODULE] Zygisk Assistant (FOSS Root Hider)

Zygisk Assistant (FOSS Root Hider) This module is designed to hide root similar to Shamiko. While capabilities may not be the same, it's worth noting that this module is open-source whereas Shamiko is closed-source. One of the advantages of this...

xdaforums.com

I'd recommend saying the same things you said here, what you tried, the result, etc. Also note the FAQ in the first post:
[Google Pixel 7] kerryh:
Don't know if this has anything to do with it or if it could be the cause but I do know that a few years ago with my pixel 4 when I unlocked the bootloader, and at the same time rooted it, my banking app didn't like that and refused to work with phone while rooted.

Since a rooted phone is waaaayyy more important to me than a stupid ****ing banking app that refuses to work while rooted I uninstalled the banking app and just use the desktop version (ie: access my stuff through chrome browser installed on phone). Does everything I need it to. Don't know if that info can help you at all but....good luck.
[ZTE nubia Z60 Ultra] Return1980:
Hello, friends, I need your help to brick the phone - there is no signal, only a message that the phone is permanently blocked. That's why I need two fsg and fsc from engineering rom files, otherwise I won't be able to fix it, please help
[ZTE nubia Z60 Ultra] Dadovvv:
How u manage to broke that? Is your IMEI saved?
[ZTE nubia Z60 Ultra] Return1980:
Generally, I wanted to make a backup which was not created because it turned out that there was not enough space on the disk, then I wanted to win the Gsi rom for it, unfortunately during the rego process poodle laptop battery I restored the phone but the sim card doesn't work
[ZTE nubia Z60 Ultra] Return1980:
Will someone help or not
[ZTE nubia Z60 Ultra] mrcust:
Have you got any solutions. I kinda have the same problem. Tried everything but imeis are showing like 00003.... and 0044. It happened with gsi rom also.
[ZTE nubia Z60 Ultra] bandario:
I think we need a clear explanation of how you did this so that everyone else can avoid doing it.

From what I have seen here and in the telegram group, nobody has yet figured out how to restore a lost IMEI on this device.
[OnePlus 8 Questions & Answers] 535iu:
[TWRP].

Up to which Android version is data decryption supported?

Only with stock ROM or also custom ROM?

[OP8Pro].
[OnePlus 8 Questions & Answers] 535iu:
Please, can anyone help me?
[Samsung Galaxy A22 5G] daviardev:
Hi all, I want to install a GSI room by fastboot, I know I have to use the original vbmeta,img file from my phone firmware, I downloaded the same firmware I installed and still I keep getting the same error.

error: Failed to find AVB_MAGIC at offset:

I use the comand 👇

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img.lz4

I know that the lz4 format does not affect since I changed the name and passed it through 7zip and still the same error, I tried the version 30.0.5 of platform-tools and still the same error, I would like to use twrp to install the room, but for my phone there is no version available, my phone is a samsung galaxy a22 5g the firmware is a226brubs9dxc1, if someone finds something.

PSDT: The bootloader is unlocked, the phone is rooted, I don't have a custom recovery installed (if anyone knows which one I could install for my model, please let me know), the phone's firmware is installed from https://samfw.com/firmware/SM-A226BR/COL/A226BRUBS9DXC1

UPDATE: The error now

Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
[General Topics] Oswald Boelcke:
Hello and good morning, @CaruzoOnTop Thanks very much for your contribution.

However, I've removed the reference to Telegram from your above post. Regarding social media please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. These conditions obviously don't apply to you, your threads and your posts. Additional information is also available here:

Telegram Chat Channels - Way Forward

WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...

xdaforums.com

Please refrain from sharing links or references to social media in future. Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Samsung Galaxy J8] Red_Bird_:
I was going to flash TWRP for my device using adb sideload. So, I turned on USB debugging in developer mode but forgot to turn off OEM lock. then using adb I typed this command:

adb reboot recovery

after applying the command my device booted into this menu.

View attachment 6102361

This asks for a sideload command, but it does not respond when I apply a sideload command. it does not even show the device using

adb devices or fastboot devices

I also installed latest samsung ADB drivers but still it's not responding.

I can boot into download mode by pressing the key combination. using download mode, I flashed the official firmware for my phone using Odin, but still after rebooting my phone shows the sideload menu shown above in the image.

I tried flashing TWRP using Odin, but it got blocked by OEM lock in download mode.

Here is the download mode screen:

View attachment 6102362

I also tried depleting the battery completely and waiting for a few days before recharging it again but still no luck. I've been trying to fix this problem for a week now. can somebody please help me solve this issue?
[Samsung Galaxy J8] ZG_DEV:
You need to unlock the bootloader in order to flash twrp, also the best way to flash is by using Odin, unlock the bootloader first then flash through Odin.

How to unlock ?, you need to enable Developer options from settings by going to settings > device info > Version number (build number) , press it about 7-8 times, the developer options button will appear in settings app, go to it, enable "allow OEM unlock" and "USB Debugging" , shutdown the device, press both volume up and down button only, release once connected to PC, a blue screen with 3 options will appear, one of them says "unlock bootloader" press it, it will wipe data so please take a backup before unlocking process.

Now after unlocking the bootloader, go to Odin again, flash vbmeta image with twrp and done :)
[Samsung Galaxy J8] Red_Bird_:
THanks for replying. but I can not unlock the bootloader becuase I cant boot into the system so unlocking the bootloader via developer options is not possible for me. I also tried to unlock it using adb (I remember turning on USB debugging), but the problem is my device is not recognized in adb. adb devices and fastboot devices commands return nothing. I installed the latest samsung drivers too but no luck.

I have acces to the download mode only. using that I flashed a stock firmware but still my phone boots in the sideload menu as shown in the image attached in my original post.

Is there any other way to solve my issue?
[Samsung Galaxy J8] Ibrahim117:
Can you boot into recovery mode?
[Samsung Galaxy J8] Red_Bird_:
I can not, my phone can only boot into download mode and this: View attachment 6103421

It asks for a sideload command but it does not respond when I type adb sideload recovery.img
[Samsung Galaxy J8] Ibrahim117:
Drain the battery, after it drains, plug it back and hold the recovery button keys, you can search it up
[Samsung Galaxy J8] Red_Bird_:
I will give it a try :)
[Samsung Galaxy J8] Ibrahim117:
Sure!

Honesty I don't use or have this phone but have an understanding of Samsung old phone, I myself used to use the S7
[Samsung Galaxy J8] Red_Bird_:
Tried after draining the battery and booting into recovery mode, but the problem persists. my phone is stuck in the same menu as shown in the image in my original post.

Is there someway to unlock the bootloader without adb or booting into system? maybe by tinkering with stock firmware files, becuase I can use download mode and flash stock firmware successfully.
[Samsung Galaxy J8] Ibrahim117:
Unfortunately you are at a dead end, with bootloader locked, it makes things harder, give this to Samsung and see if they can do anything, otherwise in worst scenario you would need to replace the motherboard, I had a similar experience with the S7, except that my bootloader was unlocked and bootloop at twrp splash screen. Or just get a new phone, that's what I can say now
[Samsung Galaxy J8] Red_Bird_:
I will give it to samsung only they can fix it now. thanks for your time anyways :)
[Android Q&A, Help & Troubleshooting] efegegg:
Mod Translation:

Hello, I'm trying to remove the bootloader, to then have root access on my Moxee tablet, it already enters all the codes that exist in fastboot mode and nothing, no message appears on either the switch or the phone, the codes I entered were .

oem get_identifier_token fastboot OEM unlock_data fastboot flashing unlock fastboot oem unlock: none of this works for me please help me

Hello, hello, I am trying to remove the bootloader, to then have root access on my Moxee tablet, I have already entered all the codes that exist in fastboot mode and nothing, I do not see any message on the switch or on the phone. The codes that I entered were.

oem get_identifier_token fastboot OEM unlock_data fastboot flashing unlock fastboot oem unlock : None of this works for me please help me

Hola buenas, estoy tratando de quitar el bootloader, para luego tener acceso root en mi tablet Moxee ya ingresa todos los códigos que existen en el modo fastboot y nada no me aparece ningún mensaje ni en la conmutadora ni en el teléfono lo códigos que puse fueron .

oem get_identifier_token fastboot OEM desbloquear_datos fastboot flashing unlock fastboot oem unlock : ninguno de esto me funciona por favor ayudenme

Hola hola estoy intentando quitar el bootloader, para luego tener acceso root en mi tablet Moxee ya ingresé todos los códigos que existen en el modo fastboot y nada no veo ningún mensaje ni en el switch ni en el teléfono Los códigos que puse fueron.

oem get_identifier_token fastboot OEM desbloquear_datos fastboot flasheo desbloquear fastboot oem desbloquear : None of this works for me please help me
[OnePlus 12] ThatStella7922:
OK story time. I upgraded to the Android 15 Beta on my CPH2583 NA variant and didn't like it really. Has bugs obviously that I didn't like, so I decided to wipe data and downgrade.

Note that OnePlus neglected to include the LocalUpdate APK that you need to downgrade (and the LocalUpdate APK for android 14 does not work, ADB says it's older than the version already installed). So I decided to downgrade via mark332's downgrade/unbrick tool, thread here.

I decided to use the "USA_CPH2583export_11_14.0.0.404EX01_2024012900480091.zip" file, so I pointed the downgrader to the images folder and let it run. And it downgraded just fine, but now I am running into this odd issue:

View attachment 6103113

Every time I turn on the phone, it thinks that there's something on the proximity sensor for a few seconds, even if there is NOTHING there.

I decided to check with the diagnostics tool (by dialing *#899#) and sure enough you can see the mean value is 1259 and the distance is near, indicating that the phone thinks it has something on the proximity sensor:

View attachment 6103114

It does this for 3-6 seconds before returning to normal readings, and normal proximity detection. Phone works perfectly if I swipe up to exit the pocket mistouch prevention screen every time I want to unlock my phone.

What can I do from here? Maybe there's a calibration I can do for the proximity sensor?

For now my current idea is to grab the "9331_sign_CPH2583_11_A_OTA_0660_all_xl5ubJ_10100001.zip" official downgrade package from OnePlus (because they gave us the zip, just not a local update APK to install it with), extract the images from the payload.bin, and try this downgrade tool once again.

The one thing that I haven't tried though, is upgrading *back* to Android 15 and seeing if the proximity sensor issue exists there.
[OnePlus 12] JEANRIVERA:
did you factory reset after downgrading?
[OnePlus 12] Jookean:
Please use LocalUpdate (https://oxygenos.oneplus.net/OTA-OnePlus-localUpdate-Oplus_key_t_s.apk) and the file 9331_sign_CPH2583_11_A_OTA_0660_all_xl5ubJ_10100001.zip to fix the issue
[OnePlus 12] JEANRIVERA:
That APK doesn't work on A15 beta 1, it doesn't install, that is not the rollback apk
[OnePlus 12] clsA:
I'm stuck now too

No apk will install and work on A15
[OnePlus 12] Jookean:
Try convert to OnePlus 12 IN or EU, and rollback
[OnePlus 12] ThatStella7922:
I formatted data immediately after downgrading, according to mark332‘s instructions.
[OnePlus 12] ThatStella7922:
OK so new info! I upgraded to Android 15 beta again and my proximity sensor issues are gone!

Lock screen:

View attachment 6103283

Diagnostics tool:

View attachment 6103284

So it looks like the way I downgraded initially caused the proximity sensor issue. What I will try next is using mark332's tool again, but use the images from "9331_sign_CPH2583_11_A_OTA_0660_all_xl5ubJ_10100001.zip" official downgrade package instead of the regular firmware file I used last time (USA_CPH2583export_11_14.0.0.404EX01_2024012900480091.zip).

Hopefully this works.
[OnePlus 12] ThatStella7922:
Unfortunately this didn't work. I am back to having proximity sensor issues. No matter how I downgrade, I run into the proximity sensor issues.

Note that my phone is not damaged as the proximity sensor works normally in Android 15.

I picked apart the official downgrade package and noticed the following lines at the bottom of the payload_properties.txt:

POWERWASH=1
SPL_DOWNGRADE=1

I think we need the A15 beta 1 downgrade apk from OnePlus for the downgrade to work properly. I don't know what else to try.
[OnePlus 12] clsA:
I posted my experience here > https://xdaforums.com/t/the-android...oneplus-12-oneplus-open.4671837/post-89509492

I turned off pocket detection in the settings and the proximity thing didn't come back on reboot
[OnePlus 12] ThatStella7922:
Your solution does prevent the pocket mistouch prevention screen from showing, but the proximity sensor is still glitching as seen in diagnostics mode.

I am not considering this a full fix as it can possibly affect phone calls too.
[OnePlus 12] clsA:
I'm not saying it's a full fix it just eliminates the annoying screen at bootup.

I have never tested the sensor so I have no idea what the proper readings should be or how it would get messed up by just resetting the phone with EDL

I did notice that some files fail to restore in the unbrick tool, like modem1, so maybe force installing some of those could help
[OnePlus 12] ThatStella7922:
yeah my current solution is just waiting for OnePlus to release the official downgrade APK for NA. Your solution makes the phone usable until then though!
[OnePlus 12] EtherealRemnant:
EDIT: Doesn't work.
[OnePlus 12] ThatStella7922:
Doesn't install, and ADB says the package version of 14000003 is lower than what's on the phone, then denies the installation. This installs and runs on Android 14, however so it's just the LocalUpdate APK for android 14.
[OnePlus 12] JEANRIVERA:
That APK won't install on A15 others have already tried it
[OnePlus 12] EtherealRemnant:
Guess Oxygen Updater isn't on top of it like they usually are since they say that's the downgrade APK.

No choice but to wait for OnePlus I guess. Glad I didn't install the beta.
[OnePlus 12] clsA:
They updated the post again and are offering this APK > https://oxygenos.oneplus.net/OTA-OnePlus-localUpdate-Oplus_key.apk

I didn't test it. I have no interest in going back to that Beta

OnePlus Community

Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.

community.oneplus.com
[OnePlus 12] JEANRIVERA:
That APK will not install on A15 it will still not work
[OnePlus 12] clsA:
That figures, I guess the wait continues
[OnePlus 12] xirosiman:
The problem is when you unlock the device. For 2-3 seconds proximity sensor is not working. It shows "near" in the test, and thats the problem. its a delay somehow.. there is one solution to disable the sensors. but thats not right

eu version with the same problem here
[OnePlus 12] metaLhax:
*#899# -> manual test -> DEVICE DEBUGGING -> Proximity Sensor Test -> Infrared Proximity Calibration -> Tap on the input field and enter 6776 to enter the calibration process. Hit the 'Offset Calibrate' button and follow the instructions.

I just roughly put my hand at 3cm and 1cm during the calibration and it fixed the issue for me. I foolishly updated to the android 15 "beta" and hated it so I then downgraded back to 14. I'm currently on CPH2583-14.0.0.604(EX01) and was having the same proximity sensor issue.
[OnePlus 12] xirosiman:
Yes i did that but everytime the calibration failed. i returned to android 15 and everything is ok even the calibration works as it should
[OnePlus 12] xirosiman:
Even with the new .802 android 14 released version , the problem with proximity sensor still exists.

In android 15 beta 1 though, there is no problem..
[OnePlus 12] kanon75:
It's incredible no one can fix it, i have the same issue, downgrade to 610, upgrade to 802, but nothing to do, also with proximity calibration, alway fail or bad calibration....no solution about OnePlus?
[OnePlus 12] xirosiman:
I am now stuck in 802 as the zips to beta 15 and rollback dont work in 802.

i opened a reqest to oneplus without solution and they direct me to service center

last hope is that the next android 15 beta is going to release these days. lets hope they provide new zips that fix the problem... otherwise..
[OnePlus 12] kanon75:
i think the only solution is wait the next release of android 15 beta

😵‍💫😵‍💫
[OnePlus 12] xirosiman:
Yes and its definitely a software problem. But for everything, oneplus suggests service center as a solution..
[OnePlus 12] z.v.a.a.h.i:
Here.

Android 14 Promixity Sensor Fix

Hello friends. When you install Android 15 beta and switch back to Android 14, it gives a proximity sensor error. To do this, flash the following file with fastboot. "fastboot flash persist persist.img" Tested on CPH2581- CPH2573- PJD110, not...

xdaforums.com
[OnePlus 12] xirosiman:
Don't try this you will brick the device cause the persist.img is unique to our devices.

Android 14 Promixity Sensor Fix

Hello friends. When you install Android 15 beta and switch back to Android 14, it gives a proximity sensor error. To do this, flash the following file with fastboot. "fastboot flash persist persist.img" Tested on CPH2581- CPH2573- PJD110, not...

xdaforums.com
[OnePlus 12] z.v.a.a.h.i:
No, wrong information, it is the sensor section file taken from the edl file.
[OnePlus 12] clsA:
@ xirosiman

I had a backup of my persist.img from when the phone was new

and restoring it with fastboot flash persist persist.img does seem to fix the pocket detection problem

thanks

@ kanon75

If you have a backup of this file restoring it does seem to fix the proximity issues after flashing the A15 beta and then going back to A14 .610
[OnePlus 12] kanon75:
No...i never did a backup of my persist.img, but i dont understand...the proximity issues is not when have A15 beta, but when downgrade from the beta...once installed the beta, the proximity sensor is working.....
[OnePlus 12] joechow05:
It seems that "Pocket mistouch prevention" is buggy (due to the proximity???).

I simply disable "Pocket mistouch prevention"...
[OnePlus 12] kanon75:
will not resolving, if you make the proximity test, you will not pass it
[Samsung Galaxy S23] calipolo:
Hello, I have a new S23 with Android 14 that came with AT&T firmware, so I was able to flash U1 (XAA) firmware on it. However, the service provider software version doesn't show XAA at any point of the process, like many posts and guides are saying it should. It just said ATT/ATT,ATT/ATT and when I inserted my Verizon SIM, it asked to restart the phone and switched to VZW/VZW,VZW/ATT. Searching through the forums here people insist it should be XAA/XAA,XAA/ATT. What am I doing wrong?

Separately, the top of my phone in ODIN mode says "Carrier: ATT" despite being flashed with XAA and the software version saying VZW. Shouldn't this say XAA too, now?

Any insight would be appreciated. Thank you.
[Samsung Galaxy S23] jrkruse:
Use samfw tool to change csc to xaa
[Samsung Galaxy S23] calipolo:
Wouldn't the firmware flash (with CSC of XAA) have taken care of that? Why is there an additional step needed to change the CSC?

Also, do you know if the ODIN/Download mode "Carrier: ATT" text stays after a successful flash, or if it should change to XAA too?
[Samsung Galaxy S23] jrkruse:
That never changes