yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL Questions & Answers] hg1218:
This video they show a pixel 4 apparently they made their own kernel and got it to work with Pixel 4

has this been achieved by anyone on xda or can it be replicated ?

interested in buying this phone but I need hdmi out
[Android Q&A, Help & Troubleshooting] Carlbrixneedhelp:
Can anyone help me how to root my vivo y91 1811 snapdragon? Any method except using pc please😊.
[Android Q&A, Help & Troubleshooting] asyhaaa:
Ya.. saya ingin mengroot hp saya tipe hp Vivo y91
[Android Q&A, Help & Troubleshooting] wahyuginanjar:
Mod edit - translated by https://translate.google.com/. Oswald Boelcke, Senior Moderator.

I want to root my Vivo y91c cellphone

*********************

Saya ingin mengroot hp saya Vivo y91c
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good morning, @wahyuginanjar Welcome to XDA! I hope you'll always get the support you require and have enjoyable times on our platform.

However, as a one-time courtesy I've translated your above quoted posts. With reference to rule no. 4 of the XDA Forum Rules, please post in English or add at least an English translation to your Indonesian posts.

Spoiler content hidden.

Regards

Oswald Boelcke

Senior Moderator
[Samsung Galaxy S21 Questions] Aisp:
I recently purchased a refurbished phone Samsung Galaxy S21 5G. I just got it yesterday, and found that I am not able to use my mobile network. The sale said it is factory unlocked, and according to the descriptions, it should work just fine with my US Mobile SuperLTE network as well. When I switched on the phone, I see Verizon on the screen and so, I assume that it was locked to Verizon in the past.

When I tried to change the network settings, specifically the APN settings, I get the message "Access Point Name settings are not available for this user." The three dots on the top with reset to default is also greyed out along with Network mode in the previous page. When I click Network Operators and try to connect to the network manually, I am only able to connect to Verizon Wireless and no other. But, calling and messaging seems to work fine. Is it that the unlock process has not been completed properly? Did any of you face the same problem before? It would be great if there is something that I could do to unblock the APN settings as the rest of the phone works really well. The specific model is SM-G991U.

Thanks!
[Samsung Galaxy S21 Questions] AsItLies:
So, you need to go into the settings menu and find about phone, software info. What you want to find is the CSC information.

It will basically look something like this: XAA / XAA-XAA / XAA (or some other letters like VZW or ATT or TMB etc etc.

What taht will tell you is very helpful in determining what rom the phone is running and what kind of device it was originally. Find that in your device and post it and people will help you to figure out what it means.
[Samsung Galaxy S21 Questions] Aisp:
Thank you so much for your reply. I looked through the software section in the about section. I found the following codes about the rom.
[Samsung Galaxy S21 Questions] AsItLies:
So the csc info is complicated, I'm no expert on it. But it does look like the OYN indicates it's a multi csc rom. It does have XAA as a part of the code, and that indicates it's 'open' for that specific part. But all the others are VZW. So it's running a vzw rom, obviously.

Your sim US Mobile uses both verizon and t-mobile networks. So it working for calls and texts makes sense, as a vzw phone. You could use patched Odin and flash a different (open) rom, but first you should verify that the device really is unlocked from vzw.

Best way to do that would probably be to insert another carriers sim card and see if it can make calls / texts. If not, it's not unlocked. But are you saying everything works now except mobile data? IOW, no internet access?
[Samsung Galaxy S21 Questions] Aisp:
I had an international sim card at hand and I put it in. Interestingly the APN settings are no longer blocked. But, I do get a notification from setup wizard saying the inserted sim is not from Verizon and some services may not be available. But, messaging still seemed to work and I was also receiving 4G.
[Samsung Galaxy S21 Questions] AsItLies:
Oh then yer okay. That message from verizon can be gotten rid of a couple of ways; 1) use adb commands to disable the specific packages 2) use patched Odin and flash a different rom

VZW is the only rom I think that does that, and it's very annoying. I don't remember exactly which packages have to be disabled, but search google and use xda and vzw in keywords and u should find it.

The 2nd option would be my choice. It would do away with vzw crap and with an open rom you may find volte and vowifi will work also.

cheers
[Samsung Galaxy S21 Questions] Aisp:
Thank you so much for your reply. That sounds great! To just give it a try, I tried putting in a TMobile sim and phone restarted to install software for TMobile. After that the APN settings were unlocked and now I am also able to connect to the internet using my US Moblile sim. The only problem is the the network mode is greyed out.

This rom I think only recognizes network from major telecom providers. So, just flashing with an unlocked rom would just help to unlock all the features and also remove telecom specific crap. I will try to flash it today.

Thank you again!
[Samsung Galaxy S21 Questions] Aisp:
I also just flashed the stock firmware which is fully unlocked. And there is no bloatware from telecom OEM's. I am now able to use the network and set the APN's, but the Network Mode is still greyed out. Is it possible to know why? I am guessing that if the phone is fully unlocked, I should be able to change the Network Mode. Is there any other info that I can give you to help understand what is happening? I do not see vowifi as well.
[Redmi Note 10S] Kinzhal:
Hello! Has anyone had issues while using mobile data? My device's warranty has recently expired and today, without changing any settings, the banking apps started malfunctioning (they had been working fine up to this afternoon). I'd like to assess if installing a custom ROM would fix the issue. Thanks in advance!
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] sergio😀:
View attachment 5665695

Droidian for Poco X3/NFC​

ABOUT:

Droidian is a Gnu/Linux Distribution which uses Halium to have compatibility with android smartphones

Website: https://droidian.org

Telegram: Device Group | Global Group

Github: https://github.com/droidian

WHAT WORKS?

- Almost everything

WHAT DOESN'T WORK?

- Audio

- You tell me..

DOWNLOADS:

GSI rootfs

Adaptation package

boot-surya.img

boot-karna.img

dtbo-surya.img

dtbo-karna.img

vbmeta-surya.img

vbmeta-karna.img

Surya Installation:​

Flash boot.img: fastboot flash boot boot-surya.img.

Flash dtbo.img: fastboot flash dtbo dtbo-surya.img.

Flash vbmeta.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-surya.img.

Flash your favorite recovery ( TWRP Recommended ).

Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.

Now boot into recovery.

Go into sideload mode and sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip: adb sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip

Now extract adaptation-surya-script.zip on your PC/Laptop and push it to your device: adb push adaptation-surya-script /tmp

Get a shell into your device: adb shell

Change directory to /tmp and run the script: cd /tmp/adaptation-surya-script && chmod +x install.sh && ./install.sh

Now boot into your device.

The first boot will take a while.

Karna Installation:​

Flash boot.img: fastboot flash boot boot-karna.img.

Flash dtbo.img: fastboot flash dtbo dtbo-karna.img.

Flash vbmeta.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-karna.img.

Flash your favorite recovery ( TWRP Recommended ).

Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.

Now boot into recovery.

Go into sideload mode and sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip: adb sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip

Now extract adaptation-surya-script.zip on your PC/Laptop and push it to your device: adb push adaptation-surya-script /tmp

Get a shell into your device: adb shell

Change directory to /tmp and run the script: cd /tmp/adaptation-surya-script && chmod +x install.sh && ./install.sh

Now boot into your device.

The first boot will take a while

Notes:​

The default password is 1234.

If you see a black screen, don't worry it takes a long time to boot.

Droidian GSIs are experimental! Bugs and missing features are expected.

You need this miui build LINK

Thanks to: Barry, Javad and myself for making this rom possible
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] Srilakshmidaran:
Does VOIP VoLTE work?
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] nakedpwr:
im not being sketchy... when you say audio doesnt work... is that global for the phone or glitchy... or because i so want to use a linux os for my phone but i do still need it to be a phone.... i was hoping you might say that phone calls work but the external speaker has a bug or something.... (praying)
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] sergio😀:
Nope, they don't work, you can use something like telegram if your headphones have a microphone
[Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot] sergio😀:
Doesn't work with any Halium-based distro right now, but some people are working on it
[General Questions and Answers] Danishblunt:
Saw on reddit that some people have issues with google pay, since the new update added some new checks. So here is what you do:

- Update Magisk to 25.2, Update magisk app to 25.2 as well

- Rename Magisk app if you havent already

- [ OPTIONAL ] Add all google apps on deny list (good practice in case google wants to detect root throught their other apps)

- install these modules: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf and https://github.com/kdrag0n/safetynet-fix

- then:

step 1.) Download any terminal (I use termux)

step 2.) type SU

step 3.) type props

step 4.) edit device fingerprint

step 5.) follow the onscreen promt

step 6.) once successfully changed, reboot device

optional (i didnt have to but you can try) reset google play, play services and google wallet appdata.

step 7.) enjoy working google wallet.

- Reboot

NOTE: Remeber to clear google wallet just in case.

ANOTHER NOTE: If your device is not on this list: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/blob/master/common/prints.sh

then you'll have to manually obtain an old fingerprint for your device, its all on here how to do:

MagiskHidePropsConf/README.md at master · Magisk-Modules-Repo/MagiskHidePropsConf

This tool is now dead... Contribute to Magisk-Modules-Repo/MagiskHidePropsConf development by creating an account on GitHub.

github.com

Enjoy.

EDIT: Alternatively try this:

https://github.com/Displax/safetynet-fix/releases/

it wont work for all from what I know but it was successful for some.
[General Questions and Answers] tin2001:
I only had to update magisk then add Wallet to the deny list.... Haven't tested an actual payment yet, but it stopped complaining about root when I open it.

I probably already had some of those modules installed from before. Some of the names look familiar.

Tried it at McDonald's... Didn't work. I guess the app stops complaining after a few goes of starting it up... Need to check in the "contactless setup" part of the Wallet app to be sure. Has a warning there if your device is "unsafe".

I'll try the full list of steps above tonight and confirm tomorrow if I can pay with it.
[General Questions and Answers] onesolo:
ahhh, it was not only with me... going to install to see if it passes...
[General Questions and Answers] covar:
None of the above works. If you try to pay contactless it will fail. If you try to add card it will fail also. I think that the new google wallet can detect if bootloader is unlocked. I don't see any workaround on this.
[General Questions and Answers] taldershof:
Yeah I removed Magisk and I still failed. It seems bootloader related I think.
[General Questions and Answers] Danishblunt:
works fine for me, I added something you should try as well in case it didnt work for you.
[General Questions and Answers] covar:
Still nothing. Have you try to make payment????
[General Questions and Answers] Danishblunt:
I made 4 payments after the fix, latest being 12 minutes prior to this reply. it works fine.

I suggest starting from my post 1point by point. If it still doesnt work then you may have an app that somehow triggers the root detection that I don't have on my phone.
[General Questions and Answers] ezdiy:
You should probably mention that picking correct CTS fingerprint is crucial. Sometimes its one version down for your device, but other times you have to use entirely different (but probably related somehow?) device FP, either because prior version doesn't exist, or Google simply doesn't accept it. The Google Pay thread has a scattered reports of working combos somebody should probably make a nicer list of.
[General Questions and Answers] Paulo_1307_:
I think some steps are not necessary. Like hiding all Google apps and SQ Lite

Also, momo-hider is depreciated. Use shamiko.

Lastly, I just installed magisk hide props (and configured it) and now it works.
[General Questions and Answers] chapod:
Thanks its work✓ !! Is it permanent? Or someday its gonna pop out because some updates?

Magisk user
[General Questions and Answers] covar:
You are correct. The only thing to do is to configure props. I personally change the fingerprint and now works fine.
[General Questions and Answers] Danishblunt:
You're right, just listed old modules i gathered over time just in case without testing if they are needed anymore. Tested if they were needed and indeed, they arent.

Hiding the google apps is a good idea regardless if its needed or not.

Fixed the original post to reflect the changes.
[General Questions and Answers] darkhunter9:
hi may I ask what does step 5 mean? Thanks!
[General Questions and Answers] Danishblunt:
baisically just means follow instructions on your screen.
[General Questions and Answers] stardestroyer7771:
Can confirm this works 💯
[General Questions and Answers] V0latyle:
I had both GPay and Wallet installed on my Pixel 5; yesterday I got the "security requirements" notification.

I've now removed both apps. When I tap on the GPay tile in Quick Settings, it says "Hold to reader", but when I tap Show All, it says "Not set up". I'll test it later today.

Does anyone know how to clear cache for embedded GPay?
[General Questions and Answers] Danishblunt:
It will show an error when you try to do a transaction if you havent done the above. Minr also showed that it was reafy but when trying to pay it would throw error.
[General Questions and Answers] V0latyle:
I just went to Dollar General and successfully used tap to pay. I do not have either of the discrete apps installed, just embedded GPay.
[General Questions and Answers] TheDon13:
Even tho Xiaomi Mi 11 Lite 5g (European version) is not on either list, I got Google Wallet to play nicely (ie work! 😃) using this guide. In effect the Xiaomi Mi 11 Lite Indonesia Xiaomi:M2101K9AG must have similar coding to Xiaomi M2102K9G. I am now on 13.0.6 SKIEUXM MIUI version. I was worried in the termux app re warnings about ensuring device fingerprint is compatible etc, but when I got the sae warning in adb shell command within minimal adb & fastboot command, I decided to see what happens and it all worked for me. Have carried 2 transactions within Google wallet over yesterday & today with complete success. My device was already certified within Play protect part of Google Play Store.

So I have rooted phone with Magisk 25.2 version, zygisk and deny list set up ; magisk hidden (Hide) then froze Magisk Hide within SD Maid so my fully rooted phone runs Ad Away, no ads & all my banking apps eg Santander & Halifax work fine, so root is hidden from them. Given up trying to get Chase banking app tho :rolleyes:
[General Questions and Answers] chiteroman:
Download this app and click "Check" button: https://play.google.com/store/apps/details?id=gr.nikolasspyr.integritycheck

Send screenshot of the result.
[General Questions and Answers] chiteroman:
Also, you can try this but I don't think it will work: https://xdaforums.com/t/magisk-module-universal-safetynet-fix-2-4-0.4217823/post-88425857
[General Questions and Answers] znbaboy:
This did not work
[General Questions and Answers] chiteroman:
You pass PI so it isn't a root problem. Unless they force to pass Strong in your device but I don't think so... Sorry but I can't help more, with this info I don't know what can be the problem 😓
[General Questions and Answers] simplepinoi177:
That's true...in that case, I'm thinking maybe it's something like when the cache on an app/program leaves an instance or some data leftover that conflicts later on.

You've posted a lot so you may have mentioned it as I'm not gonna go through them all, but have you done the obligatory clearing data & cache of all the related apps and services; Play Services, Google Framework, Play Protect, GPay, Wallet, one or two others I can't recall as I'm doing at the top of my head...? Be aware that clearing both data & cache on these will also remove the cards in the app, so you'd need to re-enter them...

it is a curious error that it's coming up as a network issue than anything else; but it doesn't make sense that other cards work and/or the card works on other devices...
[General Questions and Answers] znbaboy:
Yeah I've done a clean wipe and the issue persisted. I am going to do a full factory wipe tonight with no root + bootloader locked and try adding again. I'll let you know.

Also just got off the phone with the bank I'm having issues with, they insist everything is working on there end so I'm just lost at this point
[General Questions and Answers] simplepinoi177:
If it doesn't work after unrooting & relocking bootloader, I don't know what leg the bank can stand on. Maybe, for one reason or another, they blacklisted your IMEI or something!

I doubt it's Google (Wallet/Gpay), but maybe it lies with them...this certainly is a weird enough issue...

but with other cards working, I can't think of any other reason/way it can't be on the bank's end -- probably, in the end, it's probably a bit of both; Google Wallet/Gpay holding/caching some kind of info that is causing the bank to blacklist the device (since you say your card works on other devices)...
[General Questions and Answers] znbaboy:
- used https://flash.android.com/

- Wiped phone, locked bootloader, force flashed all partitions

- installed latest Pixel 7 Pro image

- SAME ISSUE

going to try an older Pixel build, then LineageOS (as thats what my OnePlus 7 Pro is on with root and has the card added fine)

if none of that works. game over. i give up.
[General Questions and Answers] znbaboy:
Ladys and gentlemen, boys and girls. I'd like to announce that.....

nothing worked. LineageOS and older Pixel builds, all the same issue. I'm done. Thanks for watching
[General Questions and Answers] simplepinoi177:
Holy crap that's ridiculously confusing...

When you added the card on other devices, was it on Wallet or another NFC Tap to Pay deal (Samsung Pay, Apple Pay, etc.)? If you did use Wallet, was the account that you used your Google account you are using on your Pixel 7 Pro, or the owner of the other device's own Google account (I'm thinking maybe your bank may have blacklisted your Google account for some reason somehow)?
[General Questions and Answers] znbaboy:
its the same account on the other phones. I did it through the banks app and worked fine.

I spoke with Google again last night, and they insisted that my bank needed to reset the tokens from their end as they are assigned to each specific device and there is a limit on how many can be assigned per device (i was removing and adding my google play card a lot)

so im going to call them again and rip them a new one for not understanding their own systems
[General Questions and Answers] simplepinoi177:
Interesting...!

I'll have to keep that in mind for future reference! Fascinating how Google and the banks go about it... I never considered the whole devices are given "tokens" thing, no less that it's limited; and that it comes out as a network error if it runs out...?!?!

It did sound more device specific than magisk/wallet/root-detecting -- especially considering all the data erasing and resetting and it working on other devices and other cards worked...
[General Questions and Answers] Toni Moon:
I have the same issue as you, i tried diferent roms without root, etc.. nothing works but in my older phone a Oneplus with root and Flamingo rom works perfectly.

Whem i buy the new phone the contactless payments works but i install 2 or 3 roms at week and everytime i setup the contactless payments.

I suposse that the bank blacklisted my phone model or my imei for suspitous activity, i dont have other explanation.
[General Questions and Answers] znbaboy:
this is 100% what it is. My OnePlus is now getting the same thing. I frequently add and remove cards and it looks like after a certain amount of times, it is blocked. You should be to reach out to your bank to have them reset the tokenization or whatever. I pray your bank isn't as oblivious to their own systems like mine are :)
[General Questions and Answers] TOMTERA:
Still working on my LG V60 in 2023. Thank you for the tutorial.
[General Questions and Answers] tin2001:
Died today on my Samsung A52. Been working fine for many months, and suddenly couldn't pay for KFC in the app.

The thing that ****s me more than anything is their lack of errors when this happens. It just doesn't respond. Even opening up the wallet app doesn't tell you there's a problem until after you reboot.

I think I'm done with Google Pay. I think I'll just move back to keeping my contactless card in my phone case like I used to. What a win for security, Google. 🙄

Edit: Solved. Updated the module in magisk that said it had an update, deleted the Wallet data, and it seems to not care again. Haven't tried a payment yet but it's not telling me off in the actual app now.
[General Questions and Answers] brambles1234:
I'm having same problem it's just died on me this evening. I have been using it all day. I have all latest modules installed, banking apps are working fine. I have latest magisk manager and magisk installed. I have exhausted everything. I'm beginning to think it's not something 8ve done.
[General Questions and Answers] Muarco:
Wallet was working fine but since I installed TWRP it started crashing and I can't even get the app to open now. All other banking apps are working. I got all the modules installed and Magisk is hidden. Just saw that also other people are having issues.
[General Questions and Answers] mircea2s:
I had the same issue starting a few days back, and I managed to get it sorted. I had recently updated Magisk Manager and it looks to have dropped a Magisk<version>.apk in my Downloads directory. Upon deleting that apk, Wallet again considers my device "secure enough".
[General Questions and Answers] pennywaltz:
Thanks. This was my issue. Interesting they scan what's in our sd card also.
[General Questions and Answers] ChillerMarvin:
you're the man! thank you so much!

my wallet app stopped working a few months ago but i was way to lazy to fix it. now i tried to fix it, i already had done all the steps described by OP when i first setup wallet, but as i said it stopped working some time ago.

thanks to you i checked my downloads folder and found many magisk apks from previous updates. i deleted all files related to magisk from my download folder, reset the wallet app and now i don't get the "unsecure"-warning anymore. gonna test it later that day and let you know if it truly works again.