yashsingh1/xdaforums huggingface dataset:
[OnePlus Nord CE 5G] marcosanto35:
Hello everyone, I hope you can give me a hand.

Since August the backup on whatsapp gives me serious problems.

While doing the backup correctly via drive, when I go to restore it does not recover any media, video, photos or audio.

I just tried it and on the old op3 it doesn't give any problems. Has it happened to any of you?
[Redmi 9A Questions & Answers] t0bM:
Hello,

how can I root my phone with magisk 25.2?

My bootloader is already unlocked.

Thank you very much!
[Redmi 9A Questions & Answers] normredmiuser:
First,

Find the boot.img of your firmware

Patch it using magisk app

Find a patched vbmeta of your phone's version

Move those to your pc and into the folder where fastboot is found

Reboot to fastboot mode and connect it to your pc

Type fastboot devices to check if it is connected

Type fastboot flash boot nameoffile.img(the boot file name)

Type fastboot flash vbmeta nameoffile.img(the vbmeta file name)

Restart the phone either manually or using fastboot reboot
[Redmi 9A Questions & Answers] normredmiuser:
you should also put this command to avoid bootloop or any problem with booting your phone

fastboot --disable-verity --disable-verification flash vbmeta nameoffile.img(vbmeta file name)
[Redmi 9A Questions & Answers] the_arxyn:
The easiest method is by downloading magisk latest apk from the github and rename it to Magisk.zip and flash it with your custom recovery
[Magisk] randoomkiller:
Hey there folks,

Today morning I have looked into the Magisk app, I think it was in version 24.3, and it said it has an update.

I have pressed on the update, it opened the shell, and patched the relevant ROM, nothing unusual.

Then it rebooted.

Here comes the hassle.

The stock oneplus boot image came in (my phone has a boot animation and an 1+ and android splashscreen before) and I was like waiting.

After 30 secs I thought that it is taking an unusually long time, but maybe its the new module.

A few minutes later I considered that there is something wrong with it, and tried to hardware reboot it, maybe it would solve my problem.

Still nothing

Current situation : My guess is that it got bricked, it is not in bootloop, but probably my patch has failed as it does not boot in

nor adb nor fastboot (while the device is in fastboot mode) detects it from a Win10 powershell/cmd, from which I have had no problem connecting before

Any idea how can I fix it and recover the data from it at least?
[Samsung Galaxy Tab A series Questions & Answers] HarvHouHacker:
Since my last post, I got the error "One UI isn't responding". I wasn't able to type in the password, as the user interface seemed laggier than usual. What could be causing this?
[Samsung Galaxy Tab A series Questions & Answers] lewmur:
You said you had a problem running an app on the SD card. Samsung doesn't support running apps on the SD card. That's because the SD card is much, much slower than Internal storage and causes things to be laggy.
[Samsung Galaxy Tab A series Questions & Answers] HarvHouHacker:
Yes, but the SD cad is not being seen at all, even when not running apps from the SD. Documents, music, etc. are inaccessible because the SD card "disappears".
[Samsung Galaxy Tab A series Questions & Answers] HarvHouHacker:
Just posting to keep this thread relevant. The issue persists.
[Samsung Galaxy Tab A series Questions & Answers] HarvHouHacker:
...So... Anything else you guys have would be great.
[Samsung Galaxy Tab A series Questions & Answers] woodz007:
Get a new sd Card, format it as internal storage at first then format it as external storage

After that
[Samsung Galaxy Tab A series Questions & Answers] HarvHouHacker:
...Then what?
[Samsung Galaxy Tab A series Questions & Answers] HarvHouHacker:
I don't think the SD card is the issue, though, as I've been getting "One UI" errors as well. I suspect something more system-level.
[Samsung Galaxy Tab A series Questions & Answers] HarvHouHacker:
Never mind. I'm getting my friend a better tablet, so this is now an useless thread. Glad I could get so much help. 🙄
[General Questions and Answers] johann99:
Hello, does anyone know if I can revoke special app access and permissions from 1) Carrier Provisioning Service 2) Carrier Setup 3) Modem Service 4) LifetimeData? I live in Europe and I think I got the normal OEM version, as there's no carrier information in "About Phone" and fastboot says that my device is "oem_locked." Thanks for any help.
[Sony Xperia XZ Premium Questions & Answers] IRLNPC:
I'm trying to install LineageOS 19.1 but I'm having trouble as stated in the title. Every guide I've read mentions that I need to flash TWRP recovery in which case I need to go in fastboot. Problem is once in fastboot I cannot progress any further. I'm not sure what step I missed or what I'm missing. I can detect my device with "adb devices" while the device is on and "adb reboot bootloader" puts it into fastboot (notification light turns blue) but any other commands just result in "waiting for any device" after going into fastboot. Here's some additional info:

- Model is SO-04J Docomo

- Can confirm that bootloader is unlocked (OEM unlocking can be toggled on/off)
[Sony Xperia XZ Premium Questions & Answers] CookieCream:
actually, you have to unlock your bootloader first (which erases DRM Keys to take photos etc) and you surely haven't done that YET... Just follow the Instructions from Sony and you might wanna consider Backing up DRM Keys first, before you unlock your Bootloader.

1. Type in this number into your Dialer, if it (Bootloader unlocked) says YES, then your Bootloader is already unlocked but if it says, that Bootloader unlock is supported, backup your DRM Keys first and then

2. "Install the device drivers and platform tools" (from Sonys Website) (i just post the link to the driver for you to make it easier)

If you're using Windows for this, I mentioned it before (I had the same Problem as you do) And figured out, that you have to tap on your Device first IN SYSTEM MAINTAINCE (mine was labeled "Android") then Update driver, search on PC, select from List, choose ADB Interface (Samsung Android ADB Interface) and go ahead and unlock bootloader first (which ensures, TWRP CAN be flashed and to install custom ROM)
[Samsung Galaxy S10 5G Questions & Answers] IanInVR2474:
hi can anyone please help me unlock the bootloader of s105g heres the model number sm-g977u

thx
[Samsung Galaxy S10 5G Questions & Answers] kvasimodo:
Here's a video tutorial for the S10 series:
[Samsung Galaxy S10 5G Questions & Answers] IanInVR2474:
I don’t have oem unlock how am I supposed to unlock it
[Samsung Galaxy Z Fold3] ButterflyFlutterflyMyOhMy:
Is anyone else having the issue where you try taking a scroll capture screenshot, but some apps like Messages (texting) no longer have the option while the apps that still do, it does not work? If I do it in Samsung Browser, it scrolls the page, but does not save the scrolled portion (only the first shot) and grays out the scroll capture button after. I use this feature often, so it is annoying!

Samsung's advice for a fix was to reset all my apps (which would remove all permissions and such settings) and all settings (including network settings), which is ludicrous and highly doubtful it would fix it. 🤦‍♀️
[OnePlus 9 Pro] blindcat97:
I recently purchased a 9 Pro T-Mobile edition. It was supposed to be a global edition, but this information was willfully obscured by the eBay seller. Whatever, I figured I could follow this guide to convert it to global firmware. I've rooted plenty of OnePlus phones before and am very comfortable with the process, as well as using MSM to fix things when they go wrong. However, things went even worse than normal. I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed. Now I cannot access fastboot or recovery, or do quite literally anything with it.

I figured I'd use MSM and fix it just like I did when things like this happened to my OnePlus 8. So I downloaded the T-Mobile MSM from this thread and ran it. When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."

I assumed that this error was due to the fact that some of the images that were successfully flashed are from the global image, while this MSM tool is for TMO specifically, so I tried to the global MSM tool from the same thread instead. It also fails Sahara communication with the exact same error. If I use Lite Firehose, it gives the error "Unsupported Target TMO."

At this point, I'm at a complete loss. I've tried to power off the phone via holding the power button + volume up button, but it never gives any response no matter how long I hold it. I'm not sure that the phone is able to turn on at all. My next guess would be to disconnect the battery and reconnect it, but I'm very hesitant to pull apart the phone without seeing if anyone has any better suggestions first. If I could access fastboot, I could have a download of a clean TMO firmware and could easily re-flash everything, but I can't get a single response out of the phone besides MSM errors. Any help would be much appreciated.
[OnePlus 9 Pro] blindcat97:
I just realized that that article is for the Oneplus 9 and NOT the Pro. That definitely explains why it broke in the first place, but doesn't help me get it back. The MSM Tools I'm using ARE for the Pro.
[OnePlus 9 Pro] CZ Eddie:
When you open Windows Device Manager and expand out the "Ports" section, what COM port is your phone using? Does that match up with the port the MSM tool is trying to use?
[OnePlus 9 Pro] blindcat97:
They're both using COM3
[OnePlus 9 Pro] TheGhost1951:
Qualcomm.......9008?
[OnePlus 9 Pro] blindcat97:
The full title of the device is Qualcomm HS-USB QDLoader 9008 (COM3)
[OnePlus 9 Pro] TheGhost1951:
That is the correct id and driver....however, is it the latest driver. That makes a difference as well.
[OnePlus 9 Pro] blindcat97:
Windows lists the drivers version as 2.1.2.2 and date as 3/25/2016. I can't find anything newer by googling, and Windows automatic search for updated drivers reports it as the latest version.
[OnePlus 9 Pro] CZ Eddie:
Is there something in this link that will help?

Fix Sahara communication failed error in MSM Download Tool

In this tutorial, we will show you how to fix the Sahara communication failed and other related MSM Download Tool errors.

www.droidwin.com
[OnePlus 9 Pro] blindcat97:
No, I tried what I could in that article earlier already. At this point, I'm fairly certain that the only thing I could do would be to somehow force MSM to flash even though it thinks it has the wrong device, which I don't think is possible.
[OnePlus 9 Pro] CZ Eddie:
I'm a little confused about how you got your phone to its current state.

Your first paragraph has some minutia in it.

" I went through the usual process of unlocking the bootloader, and began flashing the images from the download. However, as usual, they don't tell you to unlock flashing for critical partitions, so only half the partitions got flashed and the whole thing failed."

What images did you download and how did you apply them to your phone?
[OnePlus 9 Pro] blindcat97:
I was following this guide to convert OP9 (not *pro*, which is where I messed up and I feel very stupid for not realizing that) from T-Mobile to Global firmware. It provided download links to a zip file full of img files, and a flash-all.bat which used fastboot commands to flash the individual files. Half of the files didn't flash because "Flashing critical partitions is not allowed", but some of them did flash successfully. There's no log file to tell me which ones did and did not work. Here's the chunk of the flash-all script that actually contains the fastboot commands:

Spoiler content hidden.

It got through the first reboot okay (despite booting to fastbootd and me having to manually redirect it back to fastboot), but when it reached the second reboot command, it just died and wouldn't turn on any more, and the third block of commands were never executed. So I'm guessing that something it flashed in that second block is what completely broke its ability to boot. I would flash the images from a clean copy of OP9Pro TMO firmware, but I can't get to fastboot at all.
[OnePlus 9 Pro] TheGhost1951:
You will need a modded MSM tool....when you use the stock TMO MSM tool what error do you get?
[OnePlus 9 Pro] skillz123:
im not really that experienced with this stuff but this kind of happened to me today so i decided to make an account and try to help you. Basically what I did was I deleted everything on it, like I could only use fastboot mode. Then i used an msm tool from here. make sure you get the tmobile one because i tried global and it didn't work. after i used the msm tool it started working again. once again, i am not experienced in this stuff, so my advice may screw you over, but at this point you don't really have anything to lose.
[OnePlus 9 Pro] blindcat97:
From my original post: When I try to run it normally, it gets as far as "Start download Firehouse binary" and will attempt for 18 seconds, at which point it shows the error "Sahara Communication Failed. Please try again after power off phone (FH:258)". So I tried ticking the box to use Lite Firehose. It gets farther, but errors during Param preload, with the message "Device not match image."
[OnePlus 9 Pro] CZ Eddie:
I've never run into the firehouse issue before.

But it's very common and is talked about in dozens of threads here.

But it looks like you've actually flashed some system files from a different phone.

I hope that doesn't mean MSM is rejecting you because it thinks you're a different phone.

Maybe try flashing a 9pro boot.img that would match the software you're supposed to be at right now?

Not sure if that'll mess you up more or not though.
[OnePlus 9 Pro] CZ Eddie:
Double-check that you've downloaded the correct MSM file

Research the SMT mode.

It's disabled for a reason - because it'll wipe your IMEI & other important things.

I don't know how to use it yet, but supposedly it'll fix unfixable things. When used properly.

View attachment 5731009
[OnePlus 9 Pro] blindcat97:
I have no way of flashing. I can't get to fastboot, I can't get the phone to respond to quite literally anything other than MSM. Any combination of buttons does nothing. I'm not a professional with this stuff; if there's a way to flash to EDL without MSM, I don't know it. It looks like MSM rejecting because it thinks it's a different phone is exactly what's happening, and the only thing I can think to do would be essentially to mod it so that it thinks it's allowed to flash OP9 as well as 9Pro, or otherwise bypass the device check.

I'm certain I've got the right MSM tool. Doing some research into the SMT Download mode, it looks like it breaks core features, like the IMEI, and widevine. Is it possible to backup those partitions from EDL mode?

Basically, if my only way of recovering the device is to destroy critical sectors entirely, I might just send the device to OnePlus for repairs. My warranty was already voided by unlocking the bootloader.
[OnePlus 9 Pro] CZ Eddie:
Why not? What happens when you power off the phone.

Wait 15 seconds.

And then press + hold the volume(-) and power button at the same time?

Remember to hold them until *after* the splash screen comes up.
[OnePlus 9 Pro] blindcat97:
The phone is already off and cannot be turned on in any way, to any mode. Nothing happens when I hold that combination, nor any other. The phone is completely unresponsive.
[OnePlus 9 Pro] CZ Eddie:
Then how are you getting to EDL mode?

If it's getting to EDL mode then it's responsive.

Press and hold the volume(+) and power button for 45-60 seconds.

It'll need to be at least a minimum of like 35 seconds but more often longer.
[OnePlus 9 Pro] blindcat97:
I held the buttons for a full minute (set a timer) and it never buzzed like it's supposed to to indicate power off. Holding power + vol down never loaded fastboot or showed any kind of response at all. EDL remains the only thing that works.
[OnePlus 9 Pro] CZ Eddie:
Just to confirm, you held the volume UP(+) not the volume down.

You held the volume UP and the power button together for a full minute and got nothing but a black screen?
[OnePlus 9 Pro] blindcat97:
Yes, exactly that.
[OnePlus 9 Pro] AndyC76:
You've more than likely tried this, do you have access to different usb cable?
[OnePlus 9 Pro] blindcat97:
Yes, I've tried both my usual debugging cable and an official cable. Same result either way
[OnePlus 9 Pro] TheGhost1951:
Do you unplug and replug your phone in-between failures? When the first failure occured unless the phone is rebooted or cable unplugged and plugged back in and msm tool restarted, the EDL mode is non-functioning....
[OnePlus 9 Pro] TheGhost1951:
i am working on making you a modded msm tool so give me a few minutes to upload it. It is uploading and will take a bit.
[OnePlus 9 Pro] TheGhost1951:
First things first 1) with phone connected to PC check device manager to see if it is recognized as qualcomm.....9008 under ports and leave device manager open. 2) disconnect phone from PC 3) execute the MSM Tool I sent, uncheck SHA and check use lite firehose then click on start 4) connect phone to pc 5) phone should be reaquired in ports and msm tool should take off running. If failure try changing the SHA around and also checking both boxes. It may take making more changes in the settings.xml file in the .ops file. Let me know of what errors you get.......file is attached and unzip it to PC
[OnePlus 9 Pro] blindcat97:
Okay, I checked and the device is listed correctly in device manager. I ran it with Sha256 unchecked and Lite Firehose checked, and get the error "Get TID Failed". I tried playing with the check boxes, but unchecking Lite Firehose just causes the Sahara communication failed error, and there's no difference if I check Sha256 or not.

I notice that this is labeled as for OP9Pro global, but my device is a TMO variant. Is it possible that that's causing the TID error?
[OnePlus 9 Pro] TheGhost1951:
No, it was global with TMO IDs....I created another a little differently and will upload it to be tried...
[OnePlus 9 Pro] TheGhost1951:
this will take about 30 mins to upload, be patient.....:) if the next one fails, leave the phone alone for at least 24 hours giving the phone time to run the battery down and shutdown so that we can start fresh.....maybe thirty six hours...not sure how long it will really take. Sorry, scratching my head here as well. I am new to OP phones....
[OnePlus 9 Pro] TheGhost1951:
Sorry for all you bad luck.....🙁
[OnePlus 9 Pro] TheGhost1951:
#2

Should have left it in fastbootd because that is what was expected....
[OnePlus 9 Pro] blindcat97:
Thank you for all the help regardless! I don't know the first thing about modding MSM tools, I've had issues but never anything that a stock MSM couldn't clear up.

As for the fastbootd thing, it wasn't progressing. This is something I noticed with flash scripts for my OP8, too; fastboot commands don't work in fastbootd, so the script was stuck on "Waiting for device" until i rebooted to regular fastboot. Regular fastboot doesn't recognize fastbootd at all.
[OnePlus 9 Pro] TheGhost1951:
I think a problem is the Qualcomm driver version is incorrect. I am not finding a Qualcomm oem driver of the version you stated
[OnePlus 9 Pro] TheGhost1951:
#2
[OnePlus 9 Pro] TheGhost1951:
Sahara com error is related to driver problem. If mod #2 fails, with phone connected, go into device manager and uninstall the driver. Reboot PC, disable driver signing on PC, you should see a watermark in the bottom right corner of you PC homescreen, when you see that, install the driver based on your PC version 32 or 64 bit from the link given, reboot PC, start the msm tool click start, then connect phone.....

Download Qualcomm Usb Drivers All Latest Versions

DOWNLOAD Qualcomm USB Drivers all latest versions. Basically, these USB Drivers are used for flashing, updating or unbrick your android mobile phone.

mobifirmware.com
[OnePlus 9 Pro] TheGhost1951:
I do not find any qualcomm usb driver version 2.1.2.2 on the internet....
[OnePlus 9 Pro] CZ Eddie:
I'm using 2.1.2.2 with my TMO phone. No issues.

I have not tried your MSM though.

View attachment 5731607
[OnePlus 9 Pro] TheGhost1951:
All this is a crap shoot any way you go about it....you just have to have patience and perservance! It will take some trial and error until you get it right. USB 2 port in most cases is a must along with the right cable.
[OnePlus 9 Pro] CZ Eddie:
I do get a Sahara error if I try to MSM again right away after a previously failed MSM, without having rebooted the phone in between and disconnected-reconnected the cable.

Gotta reboot and re-connect the cable and then try MSM a second or you'll get this:

View attachment 5731629
[OnePlus 9 Pro] TheGhost1951:
Try to uncheck the SHA and checking use lite firehouse and after rebooting into EDL after clicking start and connect phone in EDL mode
[OnePlus 9 Pro] blindcat97:
I reconnect the cable between every try anyway. Tried mod #2, still Sahara errors with full Firehose, still can't get TID with Lite Firehose. I tried reinstalling Qualcomm drivers, no change. Checking or unchecking Sha256, no change.

The tool produced a log folder (on my laptop's SD card instead of the main drive for some reason?), if any of those logs would be useful I can provide them.
[OnePlus 9 Pro] TheGhost1951:
All I can say is at this point if you want to send your phone to me to fix, that may be an option, otherwise continue searching for your issue, I have no other options left remotely...
[OnePlus 9 Pro] blindcat97:
I think I'll try talking to the techs at my local repair shops first. While I'm immensely grateful for your help (seriously, thank you for trying so much), you can imagine I might be a little hesitant to send my brand new phone to a stranger on the internet, because even if the whole motherboard has to be replaced, it would be cheaper than buying a whole new phone again because this one was stolen.
[OnePlus 9 Pro] TheGhost1951:
I understand perfectly. May the Lord bless you.
[Samsung Galaxy A30s Questions & Answers] leoramireztoro:
I saw a way to root an A30s, but when i did the procedure with odin in android 11, i got an error in download mode after odin finished, error Error Verifying VBMeta Image OK_NOT_SIGNED(3) and i saw a solution that was install the twrp to fix that, the set up in odin was sucessfull but after that my phone when i rebooted it show me the logo and the letters or headers of android and 5 seconds later all that goes green and the screen goes black, but i can access the internal storage, but is blanket, what should i do to fix my phone. Please help.........

​
[Samsung Galaxy A30s Questions & Answers] leoramireztoro:
I tried to make root my a30s and after i used odin i got this error with the patched firmware: Verifying VBMeta Image OK_NOT_SIGNED(3), and i saw a video with a solution that was installing twrp but that process destroy the android boot like i am showing in this video:

After the black screen the phone appears in windows, and you can see the internat storage and sd card but i dont know if there is a solution for this problem.

If somebody knows how to fix this, it will be awesome. Thanks for the attention.

​
[Samsung Galaxy A30s Questions & Answers] mathew811:
you have to install twrp on your phone with Android 10, cause with android 11 doesnt work ;)
[Samsung Galaxy A30s Questions & Answers] vrpaulinx:
Im stuck in that problem. I flashed twrp and after it my A30s only turn on if I press volume down + power, and then show the logo and got a black screen. In my computer open the internal storage. I cant acess recovery mode and download mode, I dont know what to do and idk if the a30s has bricked