yashsingh1/xdaforums huggingface dataset:
[Google Pixel 8 Pro] bigtlt:
Saw that. And now my eSIM isn't provisioning. What a day.
[Google Pixel 8 Pro] awarman:
Just happened to me today at about 4:00. I noticed if I uninstall updates to messages that RCS works.
[Google Pixel 8 Pro] bentree:
Uninstall updates doesn't work for me, sadly....
[Google Pixel 8 Pro] awarman:
Stopped working after about 15 minutes so I take it back..ugh.
[Google Pixel 8 Pro] x111:
can someone explain why would you use google rcs ?

I have never used it and cannot see why would anyone want to use it.
[Google Pixel 8 Pro] bentree:
Well it's very handy when you are in remote areas and don't have phone reception. As you can still get RCS messages with WIFI, my phone can get wifi calls but not wifi txt.

Also it allows you to send much higher quality pictures and videos without needing an email addy.

My partner works in age care and finds it very handy when working with elderly people as they don't really grasp having emails and such on a phone or tablet.

They find it much easier if people can just "text" them a nice picture or video.

I'm sure there are much more uses but I think these are the main ones.

Cheers, Bentree
[Google Pixel 8 Pro] Androiduser2390:
Use PIF module.
[Google Pixel 8 Pro] sawdoctor:
Stopped working with rcs messages today for everyone
[Google Pixel 8 Pro] BillGoss:
Not quite. Still works for my wife's phone (P8P, rooted, PIFork 8).
[Google Pixel 8 Pro] bentree:
What messages version is she using and is it a private PIF?

Cheers, Bentree
[Google Pixel 8 Pro] BillGoss:
We are both running messages.android_20240308_01_RCO3.phone_dynamic. And we're both using the Xiaomi.eu json.

I'm on a OnePlus 8T running LineageOS 21.

And we both pass Basic and Device integrity.
[Google Pixel 8 Pro] redondo_se:
Worked for me this morning, broken tonight. I really don't want to unroot.
[Google Pixel 8 Pro] HipKat:
No, I just checked mine. Stock/Rooted. RCS is still connected and working, still meeting BASIC and DEVICE Integrity
[Google Pixel 8 Pro] bentree:
So it must be region/area specific then...
[Google Pixel 8 Pro] Ultimoose:
Broke today for me as well after applying the play integrity fix earlier this week.
[Google Pixel 8 Pro] bentree:
No RCS, Country Australia.

Can people list country you are in and if you have RCS working or not? Trying to work out if it's region related.

Cheers, Bentree
[Google Pixel 8 Pro] travisjshepherd:
US, no rcs
[Google Pixel 8 Pro] Ultimoose:
US, Midwest, broke around 1:30 p.m. CST.
[Google Pixel 8 Pro] BillGoss:
I was wondering if country might be the key. But I'm also in Australia and RCS is working fine for me (as mentioned previously).

Weird, eh?!
[Google Pixel 8 Pro] bentree:
Weird and annoying. What are they checking that makes the difference?

Cheers, Bentree
[Google Pixel 8 Pro] redondo_se:
Probably a server side rollout like Google does for lots of stuff.
[Google Pixel 8 Pro] simplepinoi177:
As with what happened a couple weeks back with the 95% of FPs banning, RCS was enabled for me, but all of the people that used Google RCS reverted to SMS/MMS -- had to look at the details of the message thread to see that "End to End Encryption: Off" to understand that RCS wasn't working (because of the FP banning) -- is the same thing as now; RCS chats showed enabled and "Connected", but it is not when checked manually & individually.

I'm on the xiaomi.eu FP. Still passing DEVICE & BASIC, but not good enough for RCS. Wallet, searching for Netflix, and all of that seems to work as expected -- my "GPay Checker" hasn't alerted me that the flag in Wallet hasn't been triggered. From the limited I've read in the PIF thread, it seems it's expected to see some proactive action from Google at the beginning of the month; i'm worried this is a precursor...!
[Google Pixel 8 Pro] sawdoctor:
Seems it's the xaiomi (griffin) fingerprint that's burnt. Rcs messages won't work with it but gpay does for the moment. If you have managed to find a private print then rcs messages will still work
[Google Pixel 8 Pro] redondo_se:
I'm not using the xiaomi fingerprint. I'm using one from one of the tools that tries random ones to find one that works. I'm passing basic and device integrity. Wallet is working. RCS stopped working last night.
[Google Pixel 8 Pro] sawdoctor:
Your the 1st person to report this, could you post it in the play integrity fix thread as it will be useful information to the Devs discussing it in the thread
[Google Pixel 8 Pro] redondo_se:
Could you please share a link to the thread?
[Google Pixel 8 Pro] RAZINARES:
Check out this post on XDA forum:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

Sent from Pixel 7a using ReLabs
[Google Pixel 8 Pro] HipKat:
I must be lucky. US Midwest, still working, passing Device and Basic, but I'm not using Play Integrity Fix. I'm, using osm0sis Play Integrity Fork v8. Is there a difference?
[Google Pixel 8 Pro] Ultimoose:
Interesting. Also US Midwest (OK) but using V8 I only pass Basic and while I was able to turn RCS on and it shows connected in the Messages settings, I don't have any RCS values on any given thread's details, not even a "You aren't allowed to use E2E mister.".
[Google Pixel 8 Pro] Ultimoose:
Switched back to 15.9.6 which lets me pass all but strong but I still can't see any RCS data on details on Messages. At a loss right now. If I have to wipe and lock to get it back, I shan't be buying the P9.
[Google Pixel 8 Pro] jljtgr:
Sometimes I can't believe Google's own strategies. They run public campaigns to shame Apple into supporting RCS... and then they start disabling it for categories of Android devices while never making it fully compatible with their Google Fi web messaging service.
[Google Pixel 8 Pro] sawdoctor:
Only difference seems to be people not using the xaiomi/griffin fingerprint are the ones with working rcs messages

ATM it looks like you can either have Google play working (with pif and a fingerprint) or you can remove the working print and have rcs messages but no Google pay.

Some users who are lucky enough to have found a private working print have reported both working
[Google Pixel 8 Pro] ajerkdude:
30 minutes ago I got every RCS message that I missed since Friday.

New messages delivering/receiving.

Now I have to switch my whole family to something that google can't f-up.
[Google Pixel 8 Pro] Starman2021:
Mine just started working as well!
[Google Pixel 8 Pro] JEANRIVERA:
I can confirm it is working again on my end, I didn't change anything at all
[Google Pixel 8 Pro] HipKat:
I guess mine wasn't working after all. I also got a blast of messages from last week
[Google Pixel 8 Pro] simplepinoi177:
Also came on here to confirm that, without doing absolutely anything, my RCS started working...

I was surprised that all of a sudden the family member's that use Google Messages suddenly showed "RCS chat" instead of SMS -- and "End to End Encryption: On" now!

I wonder if this portends/foreshadows that something big/bad is gonna happen since this suddenly came back the 1st of the month....
[Google Pixel 8 Pro] BarackMitzvah:
April update, rooted with magisk, messages and rcsservice on the dentist, tried switching from Denylist to Shamiko, fingerprint passes with MEETS_BASIC_INTEGRITY using PIF

This is ridiculous - it is unacceptable for folks to send me messages with RVS and having them just go into a black hole. Nothing in the messages app even says anything is wrong until it randomly decides whether or not it's going to let you send ****

Sorry for the tone, I'm livid. Maybe it's time to swap over to GrapheneOS and tell Google Play Devices to f$&# off
[Google Pixel 8 Pro] Ducter:
If you're switching your family, give signal a go or if you prefer FOSS, there's a fork of signal called Molly.
[Google Pixel 8 Pro] ajerkdude:
I got everyone on Signal once. Then they dropped SMS/MMS compatibility in the bone-head of all bone-head moves. So some still use it, which helped over the RCS breakage. I might look at Molly, since they might have fixed some of the other issues.
[Google Pixel 8 Pro] BABYFACE10:
Working 4 days now
[Google Pixel 8 Pro] Skye.life:
When this happened to me on my Google Pixel 8 Pro running EvoX, I just added Google messages to the "DenyList" in Magisk and restarted. After that my RCS messages started sending and I starting receiving RCS messages as well.
[Google Pixel 8 Pro] BABYFACE10:
Do not touch anything after du pass safety, cts with pif. Everything work perfect

My phone is rooted and Google Wallet also works
[Google Pixel 8 Pro] thatsupnow:
Working just fine for me. Never an issue
[Google Pixel 8 Pro] murphyjasonc:
It's still working for me. For those that it quit working try installing play integrity next by Chiteroman and Play Curl by daboynb. It might just be a matter of time but those modules got it back working for me.
[Google Pixel 8 Pro] simplepinoi177:
Personal suggestion, I feel @osm0sis Play Integrity Fork and his autopif.sh script is FAR superior. It's developed by the member who created the guideline that all the experts had used and referred to when getting their own custom fingerprints (100% of all the custom fingerprints; until Google banned 95% of them) and it has a better written code keeping futureproofing in mind

source
[Google Pixel 8 Pro] HipKat:
Agreed. Since we started this at the beginning of the year, I've only had to redo mine twice, the last after the March update. And with PF, it was a very easy process
[Google Pixel 8 Pro] PelsonMX:
Hey , I have P8P , compared to my old mi9t pro it's very very quiet while someone is calling me , the ringtone level compared to other media like YouTube etc is 50% quieter ... Everything is maxed out , any solution for this ? Barely can hear phone at work while incoming call .
[Google Pixel 8 Pro] salimifran:
There are few things that you can try doing to resolve the issue. You can try turning off the "Hearing aids" accessibility setting. This might seem counterintuitive, but apparently it can sometimes mess with call volume. It's easy to check: just head over to Settings > Accessibility > Hearing aids and toggle it off. See if that makes a difference on your next call. Sometimes the latest software update is like a magic bug-zapping wand for our phones. So, check and see if there's an update available for your Pixel 8 Pro that might fix the low call volume. These updates can sometimes include fixes for sound issues, so hopefully it'll do the trick!
[Google Pixel 8 Pro] Ultimoose:
Is it just the notification/ringer that's very quiet or is it the speech coming over the call? I assume you've tried changing ringtones among the various options because some are definitely louder than others but in general they're all pretty loud in my experience at full ringer volume.
[OnePlus 3 Guides, News, & Discussion] KeplerK20:
I have a Oneplus 3 Stock OS

TWRP Recovery

Magisk installed (Magisk Manager 5.4.0) [Yeah i rooted it long back]

I am trying to use Google Pay but Safetynet fails.

Please guide me on what changes need to be made to pass Safetynet ?

Do i need to update Magisk ? Will that work ?
[OnePlus 3 Guides, News, & Discussion] zSyntex:
I thought there's a module called SafetyNet Fix, but now Google checks in a different way the OS
[OnePlus 3 Guides, News, & Discussion] KeplerK20:
I just updated the Magisk to v27

But now it (Magisk App) shows

"Required Additional Setup"

Your Device needs reflash Magisk to work properly. Please reinstall Magisk within app , recovert mode cannot get correct device info.
[OnePlus 3 Guides, News, & Discussion] KeplerK20:
Device Info If it helps with the issue

Oneplus A3003

Android Version

7.1.1 (API 25)
[OnePlus 3 Guides, News, & Discussion] Nimueh:
It says "Please reinstall Magisk within app" - did you do so? You should simply be able to do a "Direct Install" from within the app.
[OnePlus 3 Guides, News, & Discussion] Viper The Ripper:
Install it throgh the .apk, or try an older version of Magisk
[OnePlus 3 Guides, News, & Discussion] KeplerK20:
I installed Magisk from inside the app twice using Direct Install Option>

After the third try

This is the current Scenario [Image Inserted in Next Comment]

Now What to do next ? How do i Run Banking apps which check for safetynet or whatever its checking now (Playintegrity and all )
[OnePlus 3 Guides, News, & Discussion] KeplerK20:
View attachment 6086707
[OnePlus 3 Guides, News, & Discussion] KeplerK20:
Which Version works best for Oneplus 3 ?

Please let me know , ill install that one only
[OnePlus 3 Guides, News, & Discussion] Nimueh:
Try with Play Integrity Fix - but if that doesn't work then no idea.

And OP 3 is no different than any other phone, always use the latest Magisk.
[OnePlus 3 Guides, News, & Discussion] KeplerK20:
Says i cant use this module on Module on Version < 8.0
[Samsung Galaxy A34] ghostFun98:
Hello guys. I have Galaxy A34 device and recently it got FRP locked (it has it's own story). So I decided to fix the issue by following some a youtube video which in the end bricked the device. After some research I got to know that currently the phone is at BROM mode. I can't flash stock roms with SP Flash Tool because there is no scatter files that I found + I don't think that would even help. Then tried using mtkclient to at least know what's wrong with it, printed all partitions, and couldn't see there preloader partition (at least, it's name didn't popup). Command I tried was `python mtk printgpt`.

So is there any solution for my problem? I don't have backed up preloader.img to try flashing that, but even if I had, how would I flash with mtkclient?? In any case I am sure I need that file. Can't find it in the internet, so If anyone has the same device, can you please make a backup of preloader? I would be grateful for any help. I will post more info soon.
[Samsung Galaxy A34] mvikrant97:
you don't need preloader backup.

you need to flash your device in BROM mode using Unlock tool.
[Samsung Galaxy A34] ghostFun98:
You mean flash ROM?
[Samsung Galaxy A34] mvikrant97:
Yes let me show you an example video.

here is a Samsung A12 being fixed in BROM mode
[Samsung Galaxy A34] mvikrant97:
Let me tell you that the tool being used in the video is a paid tool.

I have the license to use the tool and admins have authorised me to help people using the tool.

In case you can access BROM mode on your device I can help you fix your device remotely.
[Samsung Galaxy A34] ghostFun98:
ah, legit... Yeah then we could try remotely, the worst part is I live in a country where access to internet is restricted. Still would be glad to try this way out.
[Samsung Galaxy A34] ghostFun98:
oh also, when I attach USB device appears in Devices Manager as MediaTek USB COM port
[Samsung Galaxy A34] ghostFun98:
Alright I actualy activated my account (thanks to my friend). I repeat everything in the video (except I don't open back cover). This appears:

View attachment 6085932
[Samsung Galaxy A34] ghostFun98:
Is it necessary to open back cover?
[Samsung Galaxy A34] mvikrant97:
No need.

You have not configured the lib usb drivers.
[Samsung Galaxy A34] mvikrant97:
The very first step you would always do is readback the device firmware dump even if the device is in bricked state.

Then also do a nvdata backup.

After all the above steps are done then only proceed to flash the device.
[Samsung Galaxy A34] ghostFun98:
Okay, by configuring you mean I also need to filter? Can you please explain this a bit more? Yesterday I didn't understand what to do with it.
[Samsung Galaxy A34] ghostFun98:
Okay seems like I installed it + installed filter. Now I get another error

View attachment 6086492
[Samsung Galaxy A34] ghostFun98:
bro, any suggestions I could try?
[Samsung Galaxy A34] mvikrant97:
Yes update MTK drivers and then try again
[Samsung Galaxy A34] ghostFun98:
Hmm, I reinstalled MTK drivers, still the same thing... I have libusb installed as well, tried changing phone driver in devices manager to VCOM, PreLoader VCOM, DA port, etc. nothing changed. Don't know what else I can try, there is also nothing about it in the internet. Could it mean that the tool itself doesn't support MT6877? I would want to know what is this error and why that occurs.
[Samsung Galaxy A34] mvikrant97:
Install the Mediatek drivers you installed earlier.

Then install the drivers from the link below and then add filter in lib usb, restart your PC and then retry.

XIAOMIMTKDRIVER.rar

drive.google.com
[Samsung Galaxy A34] ghostFun98:
the password?
[Samsung Galaxy A34] ghostFun98:
bro, you forgot to tell me the password
[Samsung Galaxy A34] mvikrant97:
Password is password
[Samsung Galaxy A34] ghostFun98:
hmm, it's the same driver as I install. I also instell the new version of the driver (which is 5.23... something). It didn't help, the same error.
[Samsung Galaxy A34] fede2782:
Can't you boot in Odin/DL? Shutdown-> Keep both volume buttons pressed and connect usb to pc

If you want to force H/W reboot you just need to press volume down+power for a about 10 second and then do the procedure written before
[Samsung Galaxy A34] ghostFun98:
welp actually it is in BROM and has preloader broken, I don't think it can boot to Download Mode. UnlockTool also doesn't support authentication bypass for this phone (more specifically the chipset MT6877), only FRP and Factory resets are supported, but it's too late. I can't use them because I already broke preloader and they work on Download Mode.
[Samsung Galaxy A34] fede2782:
This mean you bricked also the sboot partition. to unlock FRP there are easier methods which doesn't even require unlocked bootloader and firmware flashing
[Samsung Galaxy A34] ghostFun98:
yes but what to do. I have done steps provided in the youtube video in my first post in hope of resetting FRP, after that I got the phone to this state. I didn't want to pay anything so, yea...
[Samsung Galaxy A34] fede2782:
You could just have done the browser method, i think it still works. Basically you force the device to open a browser and bypass the frp screen. There are a few tutorials. Flashing things randomly without knowing exactly what is being done is EXTREMELY dangerous. Moreover if you had a PIN/Password inserted you could have used it to unlock frp
[Samsung Galaxy A34] xdsubho01:
s

wht update
[Samsung Galaxy A34] ghostFun98:
wdym wht update? I just the latest unlocktool.
[Samsung Galaxy A34] cactus018:
Hi. I also have this phone. I think you could have removed the FRP lock by doing a NAND erase through Odin then reflash the PIT, BL, AP, CP and CSC.

You can try SP Flash Tool to fix your phone. If you don't have a scatter file, you can generate one using MTK Droid Tools. As long as your phone starts in BROM mode, it can be saved with a bit of effort.

Try this and if it doesn't work, we'll further troubleshoot.
[Samsung Galaxy A34] kmp1:
hello, my device is infinix smart 5 which is in preloader mode and trying to crash, status is 7024

can you help me fix my device please, i am not expeirenced in these kind of stuffs
[Samsung Galaxy A34] mvikrant97:
how did you bricked it?
[Samsung Galaxy A34] mvikrant97:
remove this comment -- admin
[Samsung Galaxy A34] khusika:
isn't that link mentioned for Xiaomi devices? correct me if I'm wrong
[Samsung Galaxy A34] mvikrant97:
Yes it's wrong. Please remove my comment. Thankyou.
[Samsung Galaxy A34] kmp1:
flashed AOSP gsi and then the bootloop started.

after using mtkbypss tool i learned that the device is in preloader mode and trying to crash, can you suggest something please???
[Samsung Galaxy A34] mvikrant97:
What is the Chipset of your device?
[Samsung Galaxy A34] kmp1:
Mediatek MT6761D Helio A20
[Samsung Galaxy A34] Nisar Ahmed Nisar:
I can fix your bricked A346E in matter of minutes just PM me when you are ready, no need any paid tool etc.
[Samsung Galaxy A34] ghostFun98:
This one is interesting. But SP Flash Tool v5 didn't support MT6877 chipset. Did you mean v6 instead? Also, I think FRP is already removed, it's just the phone is in bricked state (in BROM)
[Samsung Galaxy A34] ghostFun98:
Also, I tried UnlockTool again with Stock Samsung ROM, but this time also set "Custom Preloader | EMI" option and passed `preloader.img` (I extracted it from ROM and uncompressed with lz4). This time it gives me another error:
[Samsung Galaxy A53 5G] Ferchurito:
looking forward to root my device but i dont seem to find any updated guide
[Samsung Galaxy A53 5G] mdnssknght:
OEM unlock, patch boot image with Magisk app, flash patched recovery with Odin, boot to recovery, flash patched boot image with fastboot, wipe data and boot to system

Sent from SM-A536E using ReLabs
[Samsung Galaxy A53 5G] immortel_la:
1. unlock the bootloader?

Go to your phone → Settings → About Phone → Software information → Press Build number 7 times until you see the notice “You’re now a developer”

Back in Settings → Developer options → enable OEM unlocking

Power off your phone first. Then, connect a side of your USB to your PC/Laptop, press Vol Up + Down and then plug in the USB while keeping Vol Up+Down pressed.

When you arrive at Download Mode, long press volume up until you see the green screen. Confirm to unlock the bootloader and you will erase your device.

2. Root your phone

After you unlock your bootloader, you set up your phone (connect to wifi) and ensure you do not sign in to your Google account first. Install Magisk https://github.com/topjohnwu/Magisk/releases/download/v27.0/Magisk-v27.0.apk on your phone. You need to allow the app to install other apps so that you can install the apk.

Download your A53 stock rom here https://samfw.com/firmware/SM-A536E (make sure right model a536e or 536b or whatever your phone is) (through google drive link is the fastest). Unzip stock rom to a folder.

Transfer AP_xxxxxxxxxx.tar.md5 in the firmware you download from your PC/Laptop to your phone.

Open Magisk on your phone and press the install button in the Magisk column. Select 'Select and Patch a File', 'Let's Go and find the AP_xxxxxxxxxx.tar.md5 and select it. You can have a cup of coffee if you like when you waiting for the patching of the file.

After finishing the patching, transfer the file magisk_patched-24xxx_xxxxx.tar in the Downloads folder back to your PC/Laptop.

Turn off your phone. Connect a side of your USB to your PC/Laptop, and keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrive at Download Mode press volume up. Open Odin3_v3.14.1.exe on your PC/Laptop:

Click on BL and select BL_xxxxxxxxxx.tar.md5

-Click on AP and select magisk_patched-24xxx_xxxxx.tar

-Click on CP and select CP_xxxxxxxxxx.tar.md5

-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5 (absolutely not HOME_CSC or you'll brick your phone)

When it finishes flashing, it will automatically reboot, error message will display, just press 'factory reset'

Install Magisk again, and press the install button in the Magisk column. Select 'direct...' and let's Magisk do it job and then reboot and voila, you have root access

3. Install TWRP

downloads

Downloads for SM-A536(B)

git.severkar.eu

4. Bypass Samsung Knox

install knoxpatch-v0.6.8.apk, https://github.com/Mesa-Labs-Archive/KnoxPatch/releases/tag/v0.6.8

install knoxpatch-enhancer-v-0.4.zip via magisk, link github

install safetynet-fix-v2.4.0-MOD_2.0.zip via magisk, link on github

install LSPosed-v1.9.2-7024-zygisk-release.zip via magisk, link on github

restart phone and open lsposed manager and initialize knoxpatch
[Samsung Galaxy A53 5G] Ivan Fuentes Hagar:
So... am I to ubnderstand root is properly working on the A53 under Android 14?
[Samsung Galaxy A53 5G] mdnssknght:
Yes, of course

Sent from SM-A536E using ReLabs
[Samsung Galaxy A53 5G] Ivan Fuentes Hagar:
Thanks! Had read there were some issues with Magisk and been keeping 13 for a while.
[Samsung Galaxy A53 5G] mdnssknght:
Never heard about Android 13 having problems with root. I recommend you to root using a patched recovery with fastboot enabled. (https://github.com/engineer4t/fastboot-patcher)

Sent from SM-A536E using ReLabs