• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Is possible to root Xcover Pro?

Search This thread

BWRainbow

Member
Jun 8, 2021
29
3
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!
 
  • Like
Reactions: d5sword

Proverbs2

Senior Member
Feb 1, 2012
294
323
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
Thanks for the advice! I now have a rooted Galaxy XCover Pro SM-G715U (Verizon version) with an unlocked bootloader and TWRP recovery, thanks to @afaneh92's excellent bootloader unlock service.

As iBowToAndroid says, this only works on version 7 bootloader or earlier. (The fifth character from the right on the build number is the bootloader version. For example, my phone's build number is G715USQS7AUA1.)

I thought I should post this success story here in case anyone else is considering the XCover Pro. It's by far the best phone with a removable battery, IMHO. To find a phone that hadn't been updated too far, I just messaged a bunch of ebay sellers until I found a used phone with an older build number.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    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
    Thanks for the advice! I now have a rooted Galaxy XCover Pro SM-G715U (Verizon version) with an unlocked bootloader and TWRP recovery, thanks to @afaneh92's excellent bootloader unlock service.

    As iBowToAndroid says, this only works on version 7 bootloader or earlier. (The fifth character from the right on the build number is the bootloader version. For example, my phone's build number is G715USQS7AUA1.)

    I thought I should post this success story here in case anyone else is considering the XCover Pro. It's by far the best phone with a removable battery, IMHO. To find a phone that hadn't been updated too far, I just messaged a bunch of ebay sellers until I found a used phone with an older build number.
    2
    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
    1
    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!
    1
    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:

    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.

    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.
    1
    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?
    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