yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] gfrank227:
I am not familiar with this specific encryption method. You can try winrar and see if that can read it.
[Android Q&A, Help & Troubleshooting] jaccydan:
This did it in the end:

Releases · mcmilk/7-Zip-zstd

7-Zip with support for Brotli, Fast-LZMA2, Lizard, LZ4, LZ5 and Zstandard - mcmilk/7-Zip-zstd

github.com

..and I had a successful boot.img file with data on it. I then patched that file in magisk and then transferred it via minimal adb to my PC ready for adb fastboot flashing.

I am so close to getting this magisk_patched.img onto the phone in order to root it. As stated, I have been trying to use the minimal adb program you posted, however I had been running into adb driver issues (exclamation marks) which I seem to now have sorted:

My phone is however not being recognised in device manager when I manually put the phone into download mode and plug it into the PC..

'Download mode'

..the driver entries shown above disappear. The driver entries only reappear when the phone is plugged in and in normal charging/file transfer mode:

If and when I can sort this out I should be able to get my device (when it's in download mode), recognised in minimal adb (and device manager), in order to flash that patched magisk file I now have on my PC. I will keep searching for a solution.

Any helpful suggestions welcomed.
[Android Q&A, Help & Troubleshooting] gfrank227:
What's your phone model?
[Android Q&A, Help & Troubleshooting] gfrank227:
ensure that usb debugging is enabled. You probably already tried this, but Samsung's adb drivers are here. There's some info i found regarding google adb drivers as well; it referenced a youtube video that I didn't watch but might be helpful. It is here.
[Android Q&A, Help & Troubleshooting] jaccydan:
USING: Samsung S20 Ultra SM-G9880 Hong Kong Variant (256GB Internal Storage).
[Android Q&A, Help & Troubleshooting] jaccydan:
I have adb drivers installed and there are no errors. I ran Driver Booster and it showed the drivers were from 2017 and it installed the latest (as shown).

However, still no luck with the way I put the phone into download mode and the drivers immediately disappear in device manager.

I just tried trying to boot into recovery mode from adb, but it done the same thing.

I saw these posts regarding this issue and I couldn't find a way to adb shell setprop, because my settings showed that it was the opposite of what the guy said it should be for 'device allowing ADB access in recovery mode'. And apparently you have to be rooted anyway in order to make value changes. :rolleyes:

Not sure with the bottom comment if adb sideload can be used for .img files (just zips I think). Would prefer to still try to carry out the normal adb fastboot command for the patched magisk file, and get this phone recognized by the drivers when in download mode so I can do it.
[Android Q&A, Help & Troubleshooting] jaccydan:
Thanks @gfrank227 for helping. I have enabled USB debugging on the phone, and I downloaded some Samsung adb drivers - which were later updated by Driver Booster software (see my other post). I initially used the manual driver installation method as shown in the youtube video you referenced.

My adb drivers look good now, but are disappearing when I plug phone in in download mode, and reappearing when the phone is plugged in normally in charging/MTP mode. Thus I can't carry out that adb magisk patch to root the phone. So close tho. We need to figure out why this is happening.
[Android Q&A, Help & Troubleshooting] gfrank227:
Check out this forum. Sounds like your exact problem.

https://xdaforums.com/t/downgrading...rce=threadloom&utm_medium=email#post-85831741
[Android Q&A, Help & Troubleshooting] jaccydan:
I now have the v.23 patch.img as advised, but the problem lies in that when I put my phone into download mode the adb drivers disappear from the device manager which means my phone ceases to be recognized and I therefore cannot fastboot flash the patched file to the phone.

This happens in minimal adb:

In any case, if i search for 'adb devices' nothing comes up.
[Android Q&A, Help & Troubleshooting] toolhas4degrees:
Did you reenable oem unlock in developer options after msm? And usb debugging?
[Android Q&A, Help & Troubleshooting] jaccydan:
Yes oem unlocking is always on in there and greyed out like it can't be changed. USB debugging activated too.
[Android Q&A, Help & Troubleshooting] jaccydan:
Tried flashing by using platform tools instead of minimal adb.

First installed this:

Then installed platform tools and ran cmd from the platform tools explorer folder:

Same erroneous result as before. :(
[Android Q&A, Help & Troubleshooting] gfrank227:
In my mind, it's clearly a driver issue, not a phone issue. Unfortunately, I don't have a Samsung phone, so it's difficult for me to give specific driver advice. Have you tried on a different computer? Also try with a different charging cord. Sometimes cords can cause weird problems as well. For example, I've had cords that would charge my device just fine but would not be recognized for file transfer at all.
[Android Q&A, Help & Troubleshooting] jaccydan:
I have just tried a different cable and that made no difference. Unfortunately I don't have access for this task to a different computer., I was hoping I could fix this one.

It's strange because my drivers seem up-to date, and my phone gets recognized by the drivers in normal MTP/charging mode and adb works like that. :unsure:
[Android Q&A, Help & Troubleshooting] jaccydan:
I just thought that this might work..

I have twrp recovery which seems to have overridden the stock recovery when I press the required button combinations to get into recovery mode.

Well anyway, when I boot into twrp (phone plugged in), my adb drivers are present in device manager (see image below⬇) (whereas in normal download mode they are not). Thus i was wondering if I could be able to flash the magisk_patched.img with twrp, rather than with adb in download mode?

I would like to know which partition I choose to carry out this flashing of the magisk_patch.img in twrp?

I think this could be the answer, if someone knows which partition I need to flash this magisk_patched image to?

Any Samsung/twrp users? Thanks.

UPDATE:

According to this instruction (see pic below ⬇) regarding adb flashing, it must be the 'boot' partition option to choose in the above twrp screen - and I have created the magisk_patched.img file from the stock 'boot.img' file.

If I'm correct with this (?) I will take a deep breath and go ahead with it.
[Android Q&A, Help & Troubleshooting] gfrank227:
magisk takes the boot.img file and patches it. you would patch it to the boot partition. If you had been using adb, the command would have been "fastboot flash boot ..." so therefore, you should choose 'boot" where your question mark is
[Android Q&A, Help & Troubleshooting] jaccydan:
Yes, (see my update comments in post above @ Oct 29, 2021 at 10:12 AM).

So therefore I take it I should proceed with trying to do the flashing 'but in twrp' by choosing the Boot partition option on that twrp screen (?)
[Android Q&A, Help & Troubleshooting] jaccydan:
@gfrank227.

Just flashed the patched .img file in twrp and the process reported as successful. However after immediate reboot I checked the Magisk app and it shows as not installed:

Root checker app confirms that there's still no root.

Therefore it appears it's via adb fastboot or nothing.

Not sure how to proceed now, but I need to ensure my adb driver stays active in device manager when I plug in phone in download mode.

Just noticed, there's no menu options on this home screen at the bottom of my Magisk app; and when I choose the option cog at the top right hand corner and go into the options, there's a lot of stuff missing. (?)

Will try a reinstall of the app, recreation of patch file, and try this patching process all over again.
[Android Q&A, Help & Troubleshooting] jaccydan:
Installed canary/app-debug.apk (22003) version of manager, made sure channel was on canary and patched boot.img. Then flashed patched.img using the twrp method and was unsuccessful again.

Need to concentrate I think on v.(23000) and using adb fastboot method somehow - meaning my adb driver needs to stop disappearing from device manager when I plug phone into PC in download mode.

If I can achieve that then I think I can achieve root.

Any help?
[Android Q&A, Help & Troubleshooting] gfrank227:
I am not familiar with twrp. I think it might be flashing to the wrong boot sector. Is there any way in twrp to specify which boot sector to install to? make sure it's installing to boot_a, not boot_b
[Android Q&A, Help & Troubleshooting] jaccydan:
There doesn't appear to be any way to specify a or b. It's just 1 option for boot. Nothing is reported in twrp logs after the flashing process completes.

Here is a website extract explaining the process:
[Android Q&A, Help & Troubleshooting] jaccydan:
Enabled 'show hidden' drivers in Device Manager

When in download mode and plugged into PC..

..All adb drivers are blanked out. This is like this when phone unplugged also:

When in normal charging/MTP mode, these drivers are no longer hidden/blanked out, and are active.

Therefore, phone is not being recognized in download mode.
[Android Q&A, Help & Troubleshooting] jaccydan:
Interesting..when phone in download mode and plugged in, I'm still getting the no show in Device Manager, but I started up Odin just to check and the phone was actually recognized:
[Android Q&A, Help & Troubleshooting] jaccydan:
Booted phone into fastboot mode (below is an example, not my PC):

Copied magisk_patched image into the platform tools folder in explorer. Then ran command fastboot flash boot (name of my magisk patched image), as per instructions: (I don't understand the /path/to/magisk.patched.img part if the image is in the platform tools folder anyway).

Ran the command as shown below. Coming up with an error (unknown command)??:

If anyone knows how I should express this command correctly that would be much appreciated.

Phone is being recognized in this fastboot mode: (re. fastboot devices)
[Android Q&A, Help & Troubleshooting] jaccydan:
Fastboot flashing error. I must be entering a bad command, but can't work out what I'm doing wrong.

As can be seen - my bootloader is confirmed as unlocked.

Wondering if fastboot mode actually allows flashing of patched magisk image files, although it should do because it's just a modified boot.img file. :unsure:

fastboot is reporting the correct size of the magisk_patched file at 65536 KB. It's the "FAILED (remote: unknown command) that is the problem.

In this instance above I tried dropping the magisk_patched file straight on the root of C:\ instead of trying via the platform tools folder, but it came up with the same error.

The good news is my drivers are ok when I'm in fastboot mode:

Does anyone have any ideas how I should proceed?
[Android Q&A, Help & Troubleshooting] gfrank227:
The command as you entered it appears correct.

Several ideas: run the following command before you run the flash command:

fastboot --set-active=a

if you have more than one boot slot, this will make sure you're booting to the correct boot slot before you flash it.

Also, try a different set of adb platform tools. It could be the platform tools adb that you're using.
[Android Q&A, Help & Troubleshooting] jaccydan:
Thanks for the advice, but before I proceed with that script, Is it slot a or slot b I need to be flashing to?

How do I know if my phone has more than 1 boot slot?

I have used minimal adb method and standard platform tools method. (I have also tried using a couple of transfer cables.)

Getting back to the partition slot, I followed this tutorial (https://krispitech.com/check-partition-slot-a-b/) and found cmd is displaying a whole load of other stuff about the phone but is not displaying (bootloader) current-slot, or the slot that is currently being used.
[Android Q&A, Help & Troubleshooting] gfrank227:
you'll want to flash to slot a. It's possible that your phone doesn't have more than one boot slot, in which case this whole thing is moot...but i couldn't find that detail from a quick search of your phone.
[Android Q&A, Help & Troubleshooting] jaccydan:
This is the message I got when I ran the command fastboot --set-active=a
[Android Q&A, Help & Troubleshooting] gfrank227:
This means that you only have one boot slot. I was thinking that the twrp was flashing correctly but to the wrong boot slot. But since the device doesn't support boot slots, that can't be what's happening.
[Android Q&A, Help & Troubleshooting] jaccydan:
No quite. I'm running out of ideas tbh. What should I try next?!
[Android Q&A, Help & Troubleshooting] gfrank227:
Well, tbh, if it were me, I would long since have backed up my data and started over.

Otherwise, you could go back to the newer version of magisk and try to reroot with the newer version.

A new version of universal safety net has been compiled for early access for a price. Once it hits GitHub you should be able to pass safety net without magiskhide (I think but can't swear to it).
[Android Q&A, Help & Troubleshooting] jaccydan:
You know what? I was actually thinking along the same lines - I will start over again. I have the ROM files to begin flashing with Odin (and therefore resetting the phone). I have my old forum posts to guide me in doing all the rooting, etc procedures.

I will want to eventually go back to the old v.23000 Magisk (not the brand new version), and to a method with magisk hide that I know works now. Basically how I was set up before I messed the whole think up doing the Magisk update in the first place.

Who knows what happened to my phone, but I want to get Google Pay back.

Also a pain doing all the backing up to begin with, but thinking about it, I have an old s10 that I could do a full transfer to via Samsung Smartswitch using a usb-c to usb-c cable, that could actually make the whole procedure much easier.
[Android Q&A, Help & Troubleshooting] gfrank227:
that sounds like a reasonable approach. Be aware that you might eventually be forced to upgrade Magisk. Magiskhide will become stale, and eventually Google will beat it and you will fail SN. However, by that time, hopefully, the new magisk version will be stable and you'll have a tested and true way to pass SN with the new version.

Do you get the same error mesage, BTW, if you try to flash the stock boot image without the magisk patch? Because if not, you could flash the stock boot image, delete magisk completely, restart, and then start again with magisk from scratch and see if you have any better luck.
[Android Q&A, Help & Troubleshooting] jaccydan:
Ok, I have a new problem. I tried to install what I believed was the correct patched boot image via twrp and I've now ended up with a bootloop - the phone starts up to password prompt but when I enter it it just goes back to ask for password again.

The phone is showing up in minimal adb as an active device. I can reboot into fastboot mode and I can reboot into twrp recovery.

I have a feeling I need to just wipe some sort of cache in twrp recovery and then reboot to clear the bootloop (?)

I tried an adb command to try to remove magisk modules upon boot, but that didn't work:

The issue I have with this is that I have my data on the phone which I'd rather not lose instead of just going in with Odin and flashing a clean firmware install and losing everything!

There must be a way of getting rid of this bootloop either via adb or twrp. I've tried googling but not personally able to find what I'm looking for.
[Android Q&A, Help & Troubleshooting] Pharcanal40:
Just flash your original boot.img and it'll be fine...then try again. You should just be able to install Magisk Canary by twrp... It's the easiest
[Android Q&A, Help & Troubleshooting] Soumyajit kar:
hey

the files are not downloading , can you please share me that apk file
[Moto G5 Plus Questions & Answers] Birkorn:
Mastercloud y argo.scvmot.com
[Moto G5 Plus Questions & Answers] sd_shadow:
Please use English on XDA
[Moto G5 Plus Questions & Answers] Birkorn:
Why SEE this in My moto g5 plus (Master cloud Argo.svcmot.com
[Moto G5 Plus Questions & Answers] sd_shadow:
I don't know what that means
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] gelo0526:
any of you encountered the same problem. after I installed Oxygen os port, now I cannot go back to any custom rom. in twrp it says error 7. even in Fastboot and adb sideload, I get the same error. can someone help me
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cyanGalaxy:
First flash Stock ROM back with Mi Flash
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] gelo0526:
I have tried it. but in just a sceond it says success but nothing is happening on the phone.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] gelo0526:
update:

I was able to flash it back to miui via miflash tool.

THANKS ALOT!
[Xiaomi Mi 10T / 10T Pro Questions & Answers] ahb83:
So I've been using this phone for a few months and love it. The only issue I have is that when I update a ROM, regardless of which one it is, it bootloops and I have to start fresh.

What happens is that the phone works, I make a nandroid backup, flash rom, gapps, and magisk. When I reboot, it stays on the MI logo and reboots to recovery. The only way to fix it is by using FORMAT DATA, which wipes the phone clean and boots to the last rom that was flashed with it.

Thinking it was an issue with the ROM (crDroid), I reflashed it with Nusantara and it booted just fine. When I went back into recovery, to restore data and apps, it went smooth until reboot. After reboot, it sticks on MI logo and reboots into recovery.

Something in my DATA is causing a recovery bootloop. Has anyone else experienced this? This makes me not want to update my ROM if I have to painstakingly restore apps, from nandroid backup, using the outdated TitaniumBackup.

What am I doing wrong here?

Is there a better way to restore data from the nandroid backup?
[Samsung Galaxy Tab A series Questions & Answers] Fusseldieb:
Howdy,

I've used the Tab A for a couple of months now as literally a daily driver, since I modified it to fit into the multimedia slot in my car. It was rooted, had TWRP and even Viper4Android on it.

Long story short:

Since it's laggy I thought to test project Treble on it, since it's supported.

I wiped the tablet with TWRP and installed arm64 A/B (since it's Android 10) and it wouldn't boot anymore. It showed "Samsung Galaxy Tab A", shut off, vibrated and repeat. Also tried "Only A". Same result.

I thought to install it via fastboot. Since TWRP effectively replaced Fastbook afaik, I tried to flash the original "BL" downloaded form sammobile for this exact model. Flashed it, it succeeded and then...

It turns on with a blue screen that essentially says "This phone has been modified and is locked" with red letters on top stating "SECURE CHECK FAIL: recovery.img"

I can't get into download, it always jumps to this message. I tried all possible combinations, plugged the tablet into my pc while holding down buttons - nothing.

If I hold the pwr+down for circa 10-15 seconds while in this screen, it reboots and goes to a slightly different message stating: "SECURE CHECK FAIL: boot.img"

My PC doesn't recognize any USB devices, not even in the device manager.

What should I do? Any help would be greatly appreciated.

(I guess no music on the daily commute tomorrow lol)
[Samsung Galaxy Tab A series Questions & Answers] Fusseldieb:
Tried a Samsung JIG adapter. Still no success
[Samsung Galaxy Tab A series Questions & Answers] Fusseldieb:
Finally good news!

I tried it again with new combinations.

Turns out, if you hold all three buttons (pwr, down and up) eventually DOWNLOAD mode appears.

Worked here and am flashing stock now.
[Samsung Galaxy Tab A series Questions & Answers] Mafworld:
For rooting on latest bootloader (Rev:4, U4) which is the one you've installed already, you must purchase a subscription on this page and download that file for root:

https://support.halabtech.com/index.php?a=downloads&b=file&id=452768

As you described, it seem that you updated the bootloader and there's no way to get back at Rev:3 U3 bootloader, having the same trouble in rooting terms, I just hope a developer or an advance user that have a subscription in such page can help us and share the file that is on that page
[Samsung Galaxy Tab A series Questions & Answers] Grippingly:
No it wont work i have tried it. It gets secure check fail boot.img
[Redmi Note 9T] Z A N N:
Is same Redmi note 9 5G (Cannon) and Redmi note 9T 5G(Cannong)?
[Redmi Note 9T] jc-b:
Yes just a different interpretation between Asia and Europe.
[Redmi Note 9T] Dimon1982:
why when I install beta firmware on Redmi note 9t, it does not see the SIM card and do not have it?!?
[Redmi Note 9T] jc-b:
maybe because you install a Beta
[Google Pixel 4 XL Questions & Answers] epic_task:
Got a phone call from T-Mobile saying that the Pixel 4XL I activated last year will not work when T-Mobile repurposes Sprint's 4G bands. I can't believe this: this is a carrier-unlocked phone I got on eBay; I would have been able to activate it on T-Mobile just as well as I did on Sprint. The guy from T-Mobile swore that the phone will not work when they do the cutover. Is this really true?

I also have a Samsung Galaxy Tab A tablet that the T-Mobile guy says will work fine after the switch if I just swap the SIM for a T-Mobile one; he said this was possible because the tablet does not need to do VoLTE. Could a SIM swap let me continue using my Pixel?

I really like this phone. I've seen people complain about the phone's big forehead. For me, that's a non-issue. I love Soli's ability to wake up the display when it detects motion. I'd like to hold off on another round of researching what phone has features I want--features which include the ability to unlock the boot loader. I'm in no hurry to get 5G.
[Google Pixel 4 XL Questions & Answers] #mcl:
Hi! 👋🏻

I wrote a post on how to get any SIM work with any Pixel, independent of the carrier. 😊

I am still looking on how to unlock the bootloader. 🧐

I think I am close to get it working, however I need to test my theory yet. Here is a thread of a guy that has a similar issue, and I told him how to use SIM on his Pixel and shared my progress about unlocking the bootloader on this kind of devices.

Hope this helps you!🤞🏻
[Google Pixel 4 XL Questions & Answers] batteryguy:
I moved my (unlocked, purchased from Google) 4XL from Sprint to TMo, and have heard nothing from TMo. One of the reasons I bought the 4XL was because it had coverage of all of the TMo bands (at the time). I think you're getting bad info. I think the guy at the store needs to sell more phones to make his quota.
[Google Pixel 4 XL Questions & Answers] batteryguy:
On the TMo web site, go to the 'bring your own phone' page under Phones&Devices. Enter the IMEI and it will tell you what you need to know. This is what mine said:

View attachment 5401675
[Google Pixel 4 XL Questions & Answers] epic_task:
That was a nice suggestion to try the bring-your-own-device page. I got those same happy fully-compatible/not-blocked messages as @batteryguy got when I entered my IEMI. The woman at the T-Mobile store told me that she was surprised to see that result since the indication she had from her tools was that the phone would not be compatible.

Ah, but I got some insight when I asked about getting a T-Mobile SIM for the tablet. She said that the tablet also wasn't set to come over now to T-Mobile (as the guy on the phone had told me), but left it open that the transition would come later.

Soo--from what I can gather, everyone now on Sprint will be transferred fully to T-Mobile in the next months. When that happens, it looks like we can bring our compatible devices fully into happy land.

If I can make that transition without picking up T-Mobile's bloatware, that will be a big win.