Database Info

TWRP, Magisk, & Xposed for the NX619J

This is a translation and rework of youyim2's executable. I've rewritten some of the batch file to make things more streamlined, as well as translated the whole thing into English. I am not the device maintainer. If you have questions, I'll help as best I can. This is only for getting TWRP, Magisk, and Xposed. You should be able to flash Open GAPPs if needed with no issue once you've got TWRP installed.
Download the zip file. Extract the contents. Run the *.bat file. Follow the instructions.
INSTRUCTIONS:
1) Unlock the bootloader first.
2) Unlock fastboot flashing.
3) Flash TWRP.
4) Reboot into recovery (TWRP)
5) Flash the version of Magisk that is included.
6) Reboot into the system
7) Install the included APK for Magisk. Official Magisk does not support this device.
8) If you want Xposed, reboot to recovery, and flash the included EdXposed zip and the riru-core zip.
9) Reboot back to the system
10) Install the included EdXposed apk
TWRP:
To get TWRP into English (or your language of choice), boot to TWRP recovery. When it shows up, slide the bar to the right to unlock it. After that, tap the button second from the bottom on the right column. This takes you to the Settings menu. In here, tap the globe icon in the top right tab. Choose your language from here.
NOTES:
1) The flashing unlock needs to be run EVERY TIME you reboot into bootloader, as it locks the flash mode every reboot. This type of unlock does not wipe data.
2) DO NOT WIPE /SYSTEM IN TWRP. It will brick your phone.
Download:
Link: Red Magic Mars-TWRP3.2.3.0-v1.1.zip
MD5: 84AB33312633B9AF91DD4E07478A059C
Size: 71.5 MB

Thanks, I can't flash twrp is fail

decscomputer said:
Thanks, I can't flash twrp is fail
Click to expand...
Click to collapse
Did you unlock the bootloader and do the flashing unlock? Both are required for TWRP to flash.

Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.

decscomputer said:
Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.
Click to expand...
Click to collapse
If you read Chinese, you could try the tool in this thread. It's what mine is based on, and may be better suited to the Chinese version.

Added options to reboot into recovery and bootloader as well as some more translation and other text adjustments.

decscomputer said:
Yes, I did the process completely. I have the last Chinese Rom. The bootloader was unlocked, the fastboot Flash too but when I click the number 4 Is fail flashing twrp and there's a message saying Max limit exceded and too bootloader password Is error.
Click to expand...
Click to collapse
OEM unlock has to be switched on in developer options do you have that switched on?

cajunflavoredbob said:
Did you unlock the bootloader and do the flashing unlock? Both are required for TWRP to flash.
Click to expand...
Click to collapse
Yes, I did the bootloader Is unlocked and I did the fastboot unlock but when I try to Flash twrp Is fail with a message exceded limit Max AND too password Is error or something like that. I try with the .exe AND directly with adb but it has the same result.

cajunflavoredbob said:
Hello friends. I have a problem and I can not find the solution .. in the magisk manager some modules are not shown when looking for them, like pix3lify, google framework, camera2api y more. The first time I rooted my nubia and installed magisk manager, the modules were shown and I could install them and they worked, but then I gave a full reset to red mars and since then I have not seen the modules never again. I have already reset the nubia more than 10 times, changed the language, installed other magisk manager apk, and nothing.
this magisk manager does not let me install modules from github and if I download and install a thirdparty zip from the web, magisk installs it but the module does not apply or is not installed for some reason.
Is the same in twrp:crying:
I do not ask for support, but if someone knows how to solve it or gives me any suggestions? please
Thanks
Click to expand...
Click to collapse

I have a problem with the bootloader
when i try to bootloader my nx619j , the bootloader failed and the message is "command write failed((too many links))" can u help me pls?

cajunflavoredbob said:
INSTRUCTIONS:
1) Unlock the bootloader first.
2) Unlock fastboot flashing.
3) Flash TWRP.
4) Reboot into recovery (TWRP)
5) Flash the version of Magisk that is included.
6) Reboot into the system
7) Install the included APK for Magisk. Official Magisk does not support this device.
8) If you want Xposed, reboot to recovery, and flash the included EdXposed zip and the riru-core zip.
9) Reboot back to the system
10) Install the included EdXposed apk
NOTES:
1) The flashing unlock needs to be run EVERY TIME you reboot into bootloader, as it locks the flash mode every reboot. This type of unlock does not wipe data.
2) DO NOT WIPE /SYSTEM IN TWRP. It will brick your phone.
Download:
Link: Red Magic Mars-TWRP3.2.3.0-v1.1.zip
MD5: 84AB33312633B9AF91DD4E07478A059C
Size: 71.5 MB
Click to expand...
Click to collapse
One thing that I have found rather disappointing with all of the "guides" (that can only be loosely called such) is that nobody has explicitly mentioned HOW you have to unlock the bootloader on Nubia devices without downloading something.
In fastboot mode, after toggling Bootloader Unlock in developer settings, one must type:
fastboot oem nubia_unlock NUBIA_NX619J
THEN you can do: fastboot flashing unlock
Flashing a boot image may require you to redo the bootloader flashing unlock to bypass the "This device is corrupt" screen.
Packed up Windows executables aren't exactly helpful for those of us using Linux or MacOS based systems. Even then, the Red Magic Mars packaged bat files/tools didn't install correct drivers for me on Win10. Could never get the device recognized within Fastboot on my Win10 Intel desktop after updating and reinstalling drivers.
There is also another quirk with the Nubia devices that I ran into that I have seen mentioned only once on another device's forum.
If you're running a Ryzen/AMD based system, you may have to issue the fastboot commands on an Intel based system instead.
Why? Beats me. It makes no sense, but after hours of pulling my hair out, I happened to come across a post suggesting it and gave it try.
Typing in the same commands with fastboot in the same OS (xUbuntu 20.04) with the same exact versions of every tool used... failed on my Ryzen desktop but worked fine on my Intel laptop. Had I known, it would have saved me several hours of swapping cables and reflashing software.
Also, for those (like me) who don't exactly like blindly trusting software found on forums.
You can download the official system images here:
REDMAGIC Mars
VERSIONS Europe & Asia: V207 North America: V111 LAST UPDATED 10/28/2019 DOWNLOAD V207: Download V111: Download Go to flash instructions UPDATED AND ADDED FEATURES Game Space: Call...
help.redmagic.gg
Pull boot.img from the update archive and use another device with Magisk installed to repackage the boot image for the Mars to flash yourself.
fastboot flash boot modified_boot_image.img
And done.
Due to the risk of bricking the Red Magic Mars within TWRP, I'd rather avoid using it entirely... so I only flashed a boot.img modified with Magisk instead.
One nice thing of note about the Red Magic Mars. It has an actual recovery partition and doesn't use the clusterfluck that is the A/B partition scheme.

Root Guide

Found this while trolling through the Chinese forums, none of this is my work, I have translated the instructions as best I can.
Disclaimers; I have not tried this, it may brick the global rom, the custom recovery is likely only in Chinese language.
You need:
Boot Loader unlock code (currently probably not possible to get)
Huawei USB drivers
Recovery image (attached)
Magisk package (attached)
files: https://mega.nz/#!PM0EmYLA!384hZjmJ9ExNc7Q8rSqssHunWSO7AxQ3GA4qet6RX4E
Extract files to a folder, open command prompt and change into this folder.
Unlock bootloader (BL unlock will clear the phone data, please do a backup)
- Obtain an official unlock code
- double-click to open the "Huawei Toolbox.exe"
- click "unlock bootloader "
- enter the unlock code in the pop up window , click OK, and wait for the phone to unlock complete restart.
Flash the third-party recovery
- Turn off the phone and connect the computer. Press and hold the “Volume Down” button and “Power button” until the phone displays the android page and release your finger.
- open command prompt and run:
fastboot flash recovery_ramdisk twrp.img
- after seeing the two OKAY feedback from the command line, the flash is successful.
Enter recovery to flash root image (this step will clear all data of the mobile phone including memory card, please make a backup in advance)
- long press “Volume Up” and “Power” ", until you see the a twrp logo, release the keys and wait to enter recovery mode
- After entering recovery, click the second item “Clear”, click “Format Data Partition” in the lower left corner, slide the slider to enter the clear, wait for the progress bar to complete
- Return to the recovery homepage, click on the last item "Advanced", select the last item "Remove data forced encryption", slide the slider to release, wait for completion
Copy the root package to the phone
- In Command Prompt type or copy the following commands
adb push magisk-installer.zip /sdcard
adb push magisk.apk /sdcard
Install Image
- Whilst still in recovery mode, click the first item to install the magisk-installer.zip package from the sdcard , slide the slider to install, wait for the flash to complete, and restart the phone
- After reboot is complete, click “File Manager”, select the apk file “magisk.apk” just copied from the memory card when install is finished, open the magisk app and click “No, thank you” in the pop-up window
- Return to the command line tool, type the code to execute, and wait for the phone to automatically restart
Fastboot reboot recovery
- after the restart, open "magisk", it should show that the installation is complete, that is, ROOT is achieved.

Anything in that forum on how to manually update phone?

technotika said:
Anything in that forum on how to manually update phone?
Click to expand...
Click to collapse
That is actually what I was looking for
But none, problem is the v20 (china version) seems to get OTA way before us, they all got v143 2 weeks ago.
I did find the menu to do it, but it only supports if the image is stored on an sdcard, and when I click it it says no sdcard found. so its impossible.

Tried same with similar results. One day eh? ?

İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader

greenblueye said:
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
Click to expand...
Click to collapse
If you read what I wrote in the first post you would see you cannot root without a bootloader unlock code.

Tested! Work bootloader code on Russia services (Cost 20USD)

belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Nice! Did unlocking bootloader factory reset your device?

Yes of course. All new Huawei and Honor do a reset after unlocking

i get bootloader unlock code from funkiehuwai for 20$
any one tried this instructions and have success?
I just wonder comments below will work?
*adb push magisk-installer.zip /sdcard
*adb push magisk.apk /sdcard
because there is no sd card support for view20?
when i opened huawei-toolbox.exe its in chinese and im afraid to continue other instructions

Did anyone use TWRP and which version?
Did the View 20 Boot correctly?
I read in a Forum, that with the view 20 doesn´t boot correctyl with TWRP. The reason should bei the Storage...
Best regards

Unlocked Bootloader
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Does that mean you rooted you device (with the files from above) or you just unlocked the bootloader?
I was able to unlock my bootloader with a code from funkyhuawei (about 18 €, site seems to be down currently). I did not use the unlock tool above, mainly because its chinese
- Enabled "USB debugging" and "OEM unlock" in developer settings
- Connected phone to PC, opened adb and used "adb reboot bootloader"
- Unlocked via "fastboot oem unlock *16digit code*"
This worked out fine. However, as far as i understand it magisk is installed over twrp (recovery_ramdisk), removing twrp but granting you root. This makes me kind of nervous since twrp has been a nice safety net on several occasions. This is why I stopped after unlocking the bootloader. Maybe someone has more experience on this? Why is there so little interest in rooting this phone?
Regards

root achieved
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards

garris_bibop said:
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
Click to expand...
Click to collapse
Well done good job:good:
İ have chinese version PCT-AL10 9.0.1.144 right now. Do you think i can use the same way? İ wonder from which version to extract recovery_ramdis.img

I have my view20 rooted
Thanks for the instructions.

greenblueye said:
I have my view20 rooted
Thanks for the instructions.
Click to expand...
Click to collapse
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?

garris_bibop said:
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
Click to expand...
Click to collapse
I get recovery-ramdisk from firmware PCT-AL10 9.0.1.129 . my phone is on version 9.0.1.144 but it worked:good:

After root i can not auto update software. 9.0.1.166 version is seen on ota but after download it says update is unsuccessful. Do you have any suggestion?

I think thats to be expected when rooted. Go for manual update I guess (https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). Personally I wouldn't bother with every update unless theres interesting new features and/or security updates. just to be on the safe side I would reflash the original recovery_ramdisk before updating! And backup your data!

NM Card
Hello !
Unless I'm mistaken, the View20 must be able to use nano sd cards (NM Card)

[GUIDE][ROOT]Galaxy M30S Bootloader Unlocking and Rooting Guide

Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.​
Before Installing Magisk
Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue( I would recommend to use SmartSwitch app for backup )
You have to have your bootloader unlocked before following the instructions.
Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot your device to download mode. Turn off your device and hold volume up + volume down button, connect usb cable to PC
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk.
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
Your bootloader now accepts unofficial images in download mode.
Instructions
Method 1
1. Download the latest firmware for your device.
2. Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
3. Install the latest Magisk Manager
4. In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
5. Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar, Copy the patched file to your PC.
6. Download and extract odin(link given below).
7. Install Samsung USB drivers if not installed automatically.
8. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
9. Flash magisk_patched.tar as AP in Odin, together with the BL, CP and CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
10. Magisk is now successfully flashed to your device! But there are still several steps
before you can properly use the device.
11. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press and hold Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press and hold the Volume up + Power button to enter stock recovery.
12. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
13. This time, we can finally boot to the system with Magisk.
Important: Select Reboot system now, and immediately press the Volume up + power button after seeing the bootloader warning screen, release all buttons so it can boot to the magisk system.
14. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
15. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
16. You shall see Magisk Manager in your app drawer; if not, manually install the APK and continue to the next step. The app will automatically upgrade to the full Magisk Manager when you open it.
17. Enjoy Magisk
Method 2
INS Only
*To Make Things Easier*
1. Download the firmware(already patched) from the link given below
2. Unzip the firmware to any folder on your PC.
3. Download and extract odin(link given below).
4. Install Samsung USB drivers if not installed automatically.
5. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
6. Flash AP, BL, CP and CSC files from extracted firmware. Do not load HOME_CSC and also leave USERDATA empty in odin.
Important: Uncheck “Auto Reboot” in Options!
7. Continue steps from 10 to 17 from method 1
Method 3: Rooting with TWRP[Thread]
1. Download Twrp based on ASL2 firmware only which already have magisk patched.
2. Go to download mode
3. Using odin flash TWRP in AP slot.
4. Reboot to twrp and format data.
4. Now you have Magisk + Twrp
Note: Magisk will be disabled when you reboot the device normally. To get into Magisk enabled system, Turn off your phone and use Volume up + power buttons to turn on and release it as soon as you see Samsung Galaxy M30S logo. This will boot into magisk system, I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC used instead of CSC)
Downloads
Patched Firmware INS only
Odin
Samsung USB Drivers
NOTICE: Flash TWRP To Fix Reboot Issues After Patching ROM

????
Thankyou bro
But I think u should also post the process to patch the firmware.

Is this verified did u tried it physically? If yes then also make a video thanks

Gurjotjatt said:
Is this verified did u tried it physically? If yes then also make a video thanks
Click to expand...
Click to collapse
Yes Verified root, will try to post video soon

santhoosh said:
Yes Verified root, will try to post video soon
Click to expand...
Click to collapse
Ok thanks I will be waiting for your video:good:
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
santhoosh said:
Yes Verified root, will try to post video soon
Click to expand...
Click to collapse
And if I root will I receive updates? Like nextyear m30s will get andriod 10..will I be able to update ..Cruz I think magisk offers OTA updates to!?..am I right?

santhoosh said:
Disclaimer
I'm not responsible if something went wrong on your phone(Usually nothing goes wrong). You are doing this on your own responsibility. Rooting your phone may void warranty so don't root your device unless you know what you are doing.​
Before Installing Magisk
Your device is non-A/B and uses system-as-root, so Magisk will be installed to the recovery partition of your device.
Installing Magisk for the first time REQUIRES a full data wipe, backup before continue( I would recommend to use SmartSwitch app for backup )
You have to have your bootloader unlocked before following the instructions.
Unlocking Bootloader
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot your device to download mode. Either use adb reboot download, or Turn off your device and hold volume up + volume down button, connect usb cable to PC
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk.
Enable developer options, and confirm that the OEM unlocking option exists and grayed out!
Your bootloader now accepts unofficial images in download mode.
Instructions
1. Download the firmware from the link given below.
2. Unzip the firmware to any folder on your PC.
3. Download and extract odin(link given below).
4. Install Samsung USB drivers if not installed automatically.
5. Reboot into download mode, odin will indicate blue in id:com if the device is connected.
6. Load AP, BL, CP and CSC files from extracted firmware. Do not load HOME_CSC and also leave USERDATA empty in odin.
Important: Uncheck “Auto Reboot” in Options!
7. Now Start Flashing!
8. Magisk is now successfully flashed to your device! But there are still several steps
before you can properly use the device.
9. We now want to boot into the stock recovery to factory reset our device.
Full data wipe is mandatory! Do not skip this step.
Press and hold Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press and hold the Volume up + Power button to enter stock recovery.
10. Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
11. This time, we can finally boot to the system with Magisk.
Important: Select Reboot system now, and immediately press the Volume up + power button after seeing the bootloader warning screen, release all buttons so it can boot to the magisk system.
12. The device will automatically reboot for the first time it boots. This is completely normal and done by design.
13. After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
14. You shall see Magisk Manager in your app drawer; if not, manually install the APK and continue to the next step. The app will automatically upgrade to the full Magisk Manager when you open it.
15. Enjoy Magisk
Click to expand...
Click to collapse
Where is the step for patching magisk, if you flash it on AP slot you must insert the Magisk_patched.tar file, it look like you did not do it by your self. The latest Magisk v20.1 may be does not work. the problem is random boot loop.
You can watch this video below it will show you clearly steps by steps, you just need to change the firmware that match your M30s model number.

redymedan said:
Where is the step for patching magisk, if you flash it on AP slot you must insert the Magisk_patched.tar file, it look like you did not do it by your self. The latest Magisk v20.1 may be does not work. the problem is random boot loop.
You can watch this video below it will show you clearly steps by steps, you just need to change the firmware that match your M30s model number.
://www.youtube.com/watch?v=ILvgki0pFHE
Click to expand...
Click to collapse
To make things easier I have already patched the firmware that I have attached, And it is patched with magisk latest v20.1 which is working fine.

Gurjotjatt said:
Ok thanks I will be waiting for your video:good:
---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------
And if I root will I receive updates? Like nextyear m30s will get andriod 10..will I be able to update ..Cruz I think magisk offers OTA updates to!?..am I right?
Click to expand...
Click to collapse
For every update either it may be magisk or firmware update, you need to patch firmware and flash it manually

shamsud said:
????
Thankyou bro
But I think u should also post the process to patch the firmware.
Click to expand...
Click to collapse
Post Updated with patch method

Please help: no "OEM unlocking" in Developer options of my M30s -- i.e. there is literally nothing between ""Enable Bluetooth HCI snoop log" and ""Running services" lines.
Thus after "adb reboot download" pressing Volume Up -- does nothing as well...

_hunter said:
Please help: no "OEM unlocking" in Developer options of my M30s -- i.e. there is literally nothing between ""Enable Bluetooth HCI snoop log" and ""Running services" lines.
Thus after "adb reboot download" pressing Volume Up -- does nothing as well...
Click to expand...
Click to collapse
Yes there is OEM unlocking in developers mode it's like 6the option

Gurjotjatt said:
Yes there is OEM unlocking in developers mode it's like 6the option
Click to expand...
Click to collapse
OK... funny thing: it is there now. The only thing is changed: I "gave up" on rooting -- and started setting up phone -- inserted SIM-card and attached my Google account. -- might be worth adding this to the first post.

Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
And error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software.
Click to expand...
Click to collapse
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...

_hunter said:
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
Click to expand...
Click to collapse
Ok, can I know which firmware you used and odin version, also did you unlocked your bootloader properly?

its not workimg for my m30s i have followed every step
but its still showing cts profile:false

santhoosh said:
Ok, can I know which firmware you used and odin version, also did you unlocked your bootloader properly?
Click to expand...
Click to collapse
Resolved that issue flashing original (without Magisk patching) firmware.
Confirmed afterwards that you only can see "OEM unlocking" when your Google account attached.
But yes: it's appears that bootloader still was locked -- that "OEM unlocking" -- it's not grayed-out.
So, the question is: how you're supposed to unlock it?
-- "reboot download" and long pressing Volume Up there -- from the first post -- does nothing
-- "reboot recovery" + wipe data + reboot to bootloader -- from the "movie" -- does nothing

Comment if someone got success in Rooting m30s..!!

_hunter said:
Another issue: Odin flashing failed "in the middle" with small red text like "User firmware disabled".
Now phone is not bootable -- text appears:
But the Smart Switch says "unsupported device"...
And "adb devices" can't see the phone now...
Click to expand...
Click to collapse
I have the same problem.

Gurjotjatt said:
Comment if someone got success in Rooting m30s..!!
Click to expand...
Click to collapse
Considering we have Magisk available -- rooting is rather trivial. Setback is with unlocking bootloader

Finally Rooted
After couple of tries and disappearing OEM Unlocking button, finally I was successful in rooting using the method from this post. It took me some time to master booting directly into recovery after flashing patched images using Odin!
Also, did not realized that you need to connect USB cable to PC and press volume up and down at same time to get the bootloader unlock option.
Thank You OP.

How To Guide Pad 11 (TB-J606F) Unlock! Magisk! RoooooT !!!

Lenovo Tab P11 (2021г.) - Обсуждение - 4PDA
Lenovo Tab P11 (2021г.) - Обсуждение, Планшет, 11"
4pda.to
Translator from Russian: https://www.deepl.com/translator

Basically
1. Enable OEM Unlock in Developers Settings
2. (Your host PC should have LMSA installed) Open command window, and go to where ADB is
3. Turn your tablet off. Press and hold volume down and power buttons to enter bootloader
4. Enter the following in command window
Code:
fastboot flashing unlock
. Answer yes to unlock bootloader
warning: your tablet is wiped during the process!!![/B]
5. Reboot

To root, patch boot with Magisk
You can use LMSA to download matching ROM, and use rescue to update ROM if necessary. You can get needed boot at c:/program data/LMSA/download/romfiles/
Copy boot.img to your phone and use Magisk to patch, and copy patched_boot.img back to host computer.
Turn your tablet off and enter bootloader
Switch to fastbootd
Code:
fastboot reboot fastboot
Flash the patched boot
Code:
fastboot flash boot
Press spacebar once and drag and drop the patched boot onto command window, and press enter
Reboot

does this work with Lenovo Pad Pro 2021 (SD870) ?

Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.

I had this issue too, I had to run the command:
Code:
fastboot flashing unlock

aurelienlux said:
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
Click to expand...
Click to collapse
I flashed vbmeta.img and now I can't boot into system/fastboot/recovery. Do you know how to restore ? I also tried LMSA, device cannot be detected.

cyatsl said:
I flashed vbmeta.img and now I can't boot into system/fastboot/recovery. Do you know how to restore ? I also tried LMSA, device cannot be detected.
Click to expand...
Click to collapse
DO IT ON YOUR OWEN RISK! I HAVE NOT TESTED ON A LENOVO TAB P11 YET!
These are the steps for rooting a Lenovo Tab M8 FHD!
I think essential are the points 19 to 21, to flash the boot.img ONCE AGAIN after vbmeta.img.
It discribes ... this part is key, otherwise you'll bootloop!
Fully charge tablet
Turn tablet on
Skip as much of the initial setup process as possible, however you MUST be connected to the WiFi in order to allow unlocking of your bootloader (Start -> More/Accept -> no wifi/Set-Up Offline -> skip setting current time set -> Choose reporting options / Hit Accept -> Skip Pin -> Skip Lenovo ID -> Lenovo User Experience Program (choose if you want to skip or not) -> Choose navigation etc) Get to the home screen
Swipe down from top of screen and open Settings
Developer Tools (enable dev tools if you don't yet have access) -> Enable USB Debugging
Developer Tools -> Enable OEM Unlocking (again, if you're not on WiFi, it may not allow you to do this)
Connect tablet usb and usb to computer (Click "allow" when the usb debugging popup comes up)
./adb devices (Make sure the computer can see the tablet)
./adb reboot bootloader
./fastboot devices (Make sure the computer can see the tablet)
./fastboot flashing unlock then press volume-up on the device
./fastboot reboot`
On the Lenovo loading splash screen, you should now get the Orange State alert that the device is unlocked. It may take a bit to reboot as you've just wiped all data again and it must do initial setup
Device boots up normally. Now you can do real setup steps if you like, or you can ignore everything like in Step 3 above.
Enable USB Debugging again (Step 4-5)
Grab the boot.img and vbmeta.img from the LMSA TB_8505FS_S300025_201015_BMP update. Copy the boot.img to the tablet, taking note of the location (e.g., ./adb push boot.img /sdcard/)
Install latest version of Magisk Manager (doesn't need to be the Canary version, can be the regular version) and patch the boot image.
Clicked on "Install" on the righthand top in magisk manager
Clicked on "Next" Righthand top.
Selected "Select and Patch a File".
picked the boot.img file I had copied in step 1. Take note of the location of the patched image (magisk_patched.img), and copy it to your PC.
Reboot into bootloader again (./adb reboot bootloader)
Flashed the magisk patched boot.img ./fastboot flash boot path/to/magisk_patched.img
Flash the VB meta with the disable-verification flag ./fastboot --disable-verification flash vbmeta path/to/vbmeta.img
Flashed the magisk patched boot.img AGAIN!!!!!! (this part is key, otherwise you'll bootloop) ./fastboot flash boot path/to/magisk_patched.img
Reboot, you should now be rooted (can confirm in Magisk Manager) ./fastboot reboot

Is it ok/safe to flash this to TB-J606L?
It is the same model but with sim card and 4G.
Sometimes WiFi vs 4G models have the same software and detect differences on startup and sometimes not... Not sure about this model. I would prefer to not (soft)brick it.

Hi there. First time boot-unlocker needing help. I also have the P11 TB-J606F and would like to root it. I believe I need to do this first. I cannot seem to get any response from the tablet when doing this. In "regular tablet" mode I can connect and do ADB-commands, but in this "bootloader" mode I cannot seem to connect. I just get "Waiting for any device"
Could it be a driver issue? In device manager there is an Android device with an exclamation mark? I have no clue how to update this? Automatic doesn't work and I can't seem to find any drivers that work. I am not sure if this indeed is the problem, but you know - help needed, please.

skodkassen said:
Hi there. First time boot-unlocker needing help. I also have the P11 TB-J606F and would like to root it. I believe I need to do this first. I cannot seem to get any response from the tablet when doing this. In "regular tablet" mode I can connect and do ADB-commands, but in this "bootloader" mode I cannot seem to connect. I just get "Waiting for any device"
Could it be a driver issue? In device manager there is an Android device with an exclamation mark? I have no clue how to update this? Automatic doesn't work and I can't seem to find any drivers that work. I am not sure if this indeed is the problem, but you know - help needed, please.
Click to expand...
Click to collapse
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.

sc00ter98 said:
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
Click to expand...
Click to collapse
And thus my problems were solved. It took me a few hours going nowhere and thanks to you everything is now cool

sc00ter98 said:
Not sure if it helps. I had a similar issue with my Lenovo Tab M8 FHD.
The big issue was to get the android driver for win10, fastboot was not working. I found it under win10 update >> optional updates >>driver updates >> there was a medi.... as installable update. Afterthem fastboot was working fine.
Click to expand...
Click to collapse
Solution
Download and install LMSA and use Motorola ADB driver Device Manager
You should see P11 with no driver. Update driver > Let me choose > Android ADB > choose Motorola ADB driver

aurelienlux said:
Thanks for the guide, I've successfully unlocked the bootloader and rooted with Magisk.
I also installed the unofficial TWRP from here: https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j606f/
However I didn't flash the provided vbmeta.img and everything still seems to be working fine, including booting into TWRP.
Anyone know if not flashing it may cause issues to appear?
The reason I didn't flash it is because someone else on another thread here said they got stuck in a boot loop after flashing it and that after restoring they decided not to flash it and everything worked fine, which seems to be my experience too, but maybe there are implications I'm not aware of with not flashing it.
Click to expand...
Click to collapse
Be aware: The link above is not the right TWRP for the P11 Pro. I lost two days an bricked my tablet to find out that. The TWRP for P11 Pro is at https://unofficialtwrp.com/twrp-3-4-2-root-lenovo-tb-j706f/

37_ said:
does this work with Lenovo Pad Pro 2021 (SD870) ?
Click to expand...
Click to collapse
Did you try it ? I think this method can work on Pad Pro 2021 SD870

mingkee said:
Basically
1. Enable OEM Unlock in Developers Settings
2. (Your host PC should have LMSA installed) Open command window, and go to where ADB is
3. Turn your tablet off. Press and hold volume down and power buttons to enter bootloader
4. Enter the following in command window
Code:
fastboot flashing unlock
. Answer yes to unlock bootloader
warning: your tablet is wiped during the process!!![/B]
5. Reboot
Click to expand...
Click to collapse
does work with me . it repeat the same error:
C:ladb>adb reboot bootloader
error: device '(null)' not found

Two questions:
1. Did anyone lose their Widevine level when unlocking, installing Magisk and/or rooting? I currently have L1 and would hate to lose that (to L3).
2. Is it possible to use the TWRP version for the TB-J706F for the TB-J716F as well? Basically, they are very similar devices, but the screen (90 Hz OLED) and processor (Snapdragon 870 instead of Snapdragon 730G) are different, but I don't know what is relevant for TWRP. Otherwise, could I also root without TWRP?
Thanks in advance!

HANN1860BAL said:
Two questions:
1. Did anyone lose their Widevine level when unlocking, installing Magisk and/or rooting? I currently have L1 and would hate to lose that (to L3).
2. Is it possible to use the TWRP version for the TB-J706F for the TB-J716F as well? Basically, they are very similar devices, but the screen (90 Hz OLED) and processor (Snapdragon 870 instead of Snapdragon 730G) are different, but I don't know what is relevant for TWRP. Otherwise, could I also root without TWRP?
Thanks in advance!
Click to expand...
Click to collapse
1. Yes you will lose L1 when unlock bootloader
2. No , TWRP with very different hardware so don't hope so much .
I see there is no reason to root TB-J716F now, current firmware is stable and smooth

luizkun said:
1. Yes you will lose L1 when unlock bootloader
2. No , TWRP with very different hardware so don't hope so much .
I see there is no reason to root TB-J716F now, current firmware is stable and smooth
Click to expand...
Click to collapse
Thanks for the fast reply!
Is it possible to lock bootloader after rooting again and gaining L1 back with keeping device rooted?
That's true, but I want to use some rooted apps, like Titanium Backup and AdAway ;-)

HANN1860BAL said:
Thanks for the fast reply!
Is it possible to lock bootloader after rooting again and gaining L1 back with keeping device rooted?
That's true, but I want to use some rooted apps, like Titanium Backup and AdAway ;-)
Click to expand...
Click to collapse
you can root after unlock bootloade by patching boot.img from stock rom (by magisk ) and install magisk without TWRP

Is possible to root Xcover Pro?

Hello,
I have unlocked the bootloader. I tried to do the steps with Magisk, this is it:
-Install Magisk.
-Patch AP.
-Copy it to PC.
-ReFlash with ODIN.
But when I do that, I got errors during installation on Download mode and the phone bricks. So I don't know if I am doing something wrong or happens that this device can't be rooted.
I have been searching but can't find any reliable information about, could you please give me some information or help?
Thank you!

Bump!

Got this error following installation instructions:
ODIN MODE (AVB Fail)
vbm*** Error verifying vbmeta image: HASH_MISMATCH (3)
vbmeta: VERIFICATION_DISABLED bit is set
CUSTOM VBMETA
VBMETA G715FNXXU8CUE1, 4000301 4R

Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
tys0n said:
It's pretty simple and straight forward. I won't go in on details about odin, drivers etc as there's many guides about that already.
Or join the A40 tg group for any assistance with firmware, odin etc.
You'll need to unlock bootloader first, and it will TRIP KNOX.
Please read up on what it means before you proceed if you're not sure about it. It can't be reversed.
Download and install latest Magisk manager to your phone. https://github.com/topjohnwu/Magisk/releases
Download and install 7zip ZS to your pc. https://github.com/mcmilk/7-Zip-zstd/releases
Get the firmware for your phone and extract the AP file from the firmware zip. (Use samfirm or frija for fast download)
Open the AP*.tar.md5 with 7zip ZS and click on the boot.img.lz4, then drag the boot.img out of there.
Copy the boot.img to your phone, open Magisk Manager and click install, and again install, then "select and patch a file".
Browse to the boot.img you just copied to your phone and let Magisk do it's magic.
You'll find a magisk_patched.img in your download folder when it's done.
Copy it over to your pc, rename it to boot.img and make a .tar archive with boot.img in it.
Open Odin, put the tar in AP slot, connect your phone in download mode and hit start in Odin.
Open Magisk Manager again once the phone is booted to finish the setup.
Done.
Click to expand...
Click to collapse
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.

Awesome! The bad thing is that I already sold Xcover Pro because I need root yes or yes but well, I hope it will be useful for people in the future! Maybe even somebody try to port LineageOS.

d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later

-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
-SpaceCowboy- said:
I have the xcover pro g7151u but Magisk cannot flash the boot.img file my AP version is "G715U1UEU9BUF4", I leave this answer in case someone can solve it later
Click to expand...
Click to collapse
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?

-SpaceCowboy- said:
Update: At the beginning in download mode it only appreciates the FRP lock status, but not the others, after flashing the stock ROM to the last one the KG status has appeared in "Cheking" mode but there is no OEM unlock status, this means That the bootloader is no longer blocked or that it will never have the option again?
Click to expand...
Click to collapse
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far

On my rooted SM-G715FN, I have:
CURRENT BINARY: Custom (0x3)
KG STATE: Checking
FRP LOCK: OFF
OEM LOCK: OFF(U)
Secure Download: Enabled
Click to expand...
Click to collapse
In Developer Options, I have `OEM Unlocking` enabled.
iBowToAndroid said:
You can't root without an unlocked bootloader. And you can no longer unlock your bootloader on the version that you have - it's been updated too far
Click to expand...
Click to collapse
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.

d5sword said:
Why it is not possible to unlock bootloader on his phone? I have unlocked bootloader on my phone without problems.
Click to expand...
Click to collapse
Because his phone is not SM-G715FN

The ADB removal method worked for me. There's a "Debloat" text file up on GitHub that makes this a breeze.
Link: https://github.com/khlam/debloat-samsung-android tellthebell
Once in debug mode, USB connected, and drivers installed:
ADB shell < commands.txt
Obviously, the text file must reside in the same folder as ADB.

travis659 said:
El método de eliminación de ADB funcionó para mí. Hay un archivo de texto "Debloat" en GitHub que hace que esto sea muy sencillo.
Enlace: https://github.com/khlam/debloat-samsung-android tellthebell
Una vez en modo de depuración, USB conectado y controladores instalados:
Shell ADB <comandos.txt
Obviamente, el archivo de texto debe residir en la misma carpeta que ADB.
Click to expand...
Click to collapse
i think only working in snapdragon devices, no? the Xcover use Exynos

d5sword said:
Finally, I have successfully rooted Samsung Galaxy Xcover Pro (SM-G715FN/DS, Europe Version, Android 11, Firmware version: G715FNXXS9CUF2).
I also had the same HASH_MISMATCH error before. But the method described in this post worked for me:
After doing this procedure, the system didn't boot. An option to execute Factory Reset appeared instead. I chose this option and confirmed to wipe all data.
After the factory reset, the system booted correctly and the phone was rooted. During the first boot I had to wait very long (maybe about ~15 minutes) while Samsung logo splash screen was displayed, but finally the system booted correctly. I also needed to install Magisk apk again, because all data was wiped.
After I bought the phone, the "OEM unlocking" option was missing in "Developers options". But after using my phone for 7 days this options appeared.
Additionally I enabled "MigskHide" option in Magisk and installed this: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.2.0 . After doing this SafetyNet passes successfully.
Click to expand...
Click to collapse
Just wanted to say a huge thank you to yourself and tys0n.
I purchased an Xcover Pro brand new from Microless global for an absolute steal...as in a price that was simply too good to be true. It was only upon setting up the device that I realised why they were offering such a low price.
The device was encumbered by an unavoidable corporate knox enrollment service. Sadly I suspect most people who purchase from them won't realise just how much control of their device they are handing to some random company if they just press OK during setup, but I wasn't having it. Ignoring the enrolment promp was not possible; you couldn't even access the home button or recent button until you'd authorised under knox and handed control of the device over to some faceless entity.
Thanks to the efforts of those in this thread I have been able to unlock BL, root the SM-G715FN/DS and freeze all of the knox bull****. The device now belongs to me.
The only thing I'd like to ad for those that come here looking for answers is that the process above is spot on, but I had to use this tool to create my .tar file. Simply creating a .tar archive with the .img file in it wasn't good enough for my device; it rejected that as an unauthorised file.
Use this tool once you've patched the boot.img with magisk and renamed it.
[Script][Tool] how to create a tar.md5 file from img For Odin
for how want to use Odin to flash the ClockWorkMod Recovery img or any image files like "boot.img", this is a tool to create a tar.md5 file from the img file. unzip the file tool, and put your img files into the same directory of the batch file...
forum.xda-developers.com
Props to mkh.mourad and testament to the usefulness of XDA that a file from 2013 got me over the line.
I'm certainly no developer, but given the relative ease with which we got this far, I hope it's not too far down the road until we get TWRP and can start mucking around with some roms. Please post here if you have any ideas. This device has real potential as a very long term solution.

Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.

TomasNM said:
Hello,
I did all as described, however I am stuck in ODIN during flashing attempt.
I unlocked the OEM lock first, then I unlocked the bootloader (using long press Vol+ option, prior to download mode, what wipes the device).
I updated the system prior to attemt this procedure, downloaded the match image from sammobile.
Can please someone help to get through this step?
Thank you, Tomas.
Click to expand...
Click to collapse
The "KG" status must be in "checking" so that you can flash a custom binary, you must leave the phone on 168 hours in a row with an internet connection otherwise it will not disappear

SpaceCowboy,
thank you for the advice, I waited a bit and today I managed to root the phone successfully.
However, I tried to install some Magisk modules and the phone stuck on initial screen (Samsung Galaxy Xcover Pro), even not get to the "SAMSUNG" screen.
Only solution was to wipe all data in recovery.
Any ideas how to install Magisk modules without risk?

Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.

Psyckosama said:
Trying to root mine but just ran into a little problem.
Development mode lacks an OEM unlock option.
Click to expand...
Click to collapse
What's your Baseband Version?

iBowToAndroid said:
What's your Baseband Version?
Click to expand...
Click to collapse
g715u1uescbuj1

Psyckosama said:
g715u1uescbuj1
Click to expand...
Click to collapse
OEM unlock doesn't exist on US models. This model is bootloader unlockable via paid 3rd party services, but only up until bootloader revision 7. Since you're fully updated, you have revision 12