Database Users

moto x pure stuck on motorola logo after installing superSU?

so i recently got the pixel, had the moto x for about a year and decided to see what was going on with the rooting scene with this device. turns out that someone came along and created a simple solution to rooting and installing twrp for this device. I was happy. TWRP works just fine. But upon flashing SuperSU and rebooting from that i'm now stuck on the M logo permanently it seems. Yes i can reboot back into recovery and fastboot mode. But i can't seem to get past the M logo and all i've done was flash TWRP and SuperSU any idea about what's going on?

You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.
The SuperSU zip from my thread does it: https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120

Spasticdroid said:
You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.
The SuperSU zip from my thread does it: https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
awesome thanks!!!! <3 now i just need to find a rom to play around with :3

silvernirvash said:
awesome thanks!!!! <3 now i just need to find a rom to play around with :3
Click to expand...
Click to collapse
No offense, but why are you bothering to root if you are just going to flash a ROM?
Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.

acejavelin said:
Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.
Click to expand...
Click to collapse
That's exactly what my zip does. I've only put it together to make the process much simpler, and I love automating stuff when it's possible.
SuperSU inside is unmodified. Updater-script copies a file named "systemless" from the zip which has "SYSTEMLESS=true" in it to /data, renames it to ".supersu", then proceeds flashing SuperSU.

Hello all,
I need some help!I have a Moto X Pure Edition XT 1575 I just unlocked bootloader and then intalled TWRP 3.1.1 and then installed SuperSU 2.79 and now no Sim is detected. What did I do wrong?
Thanks!

Unroot & clean with supersu app. It should restore boot image.
/You can also restore boot, system, wipe data in twrp/
Reboot & check.
If ok try rooting with supersu 2.82 or magisk 14. @kaleend101

[Guide] How to systemlessly root your Pixel XL on Android 8.0 (SuperSU)

Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
EDIT: It's been confirmed that SuperSu Config is not required for Android 8.0, as systemless SBIN is the default for 8.0. I had seen this before, but decided to do it anyway to be extra sure (I like the extra redundancy). I'm leaving the steps in in case others want to be extra sure of this, or want the options provided by the installer.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system (Edit 8/28/17: DO NOT install TWRP, just boot to system)
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
UPDATE 10/2 The links for SuperSu and SuHide have been updated to the latest releases.

GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.

raazman said:
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
Click to expand...
Click to collapse
Yeah I'm not sure about Magisk. I do k ow that Magisk needs a custom kernel, so that might be your issue. Did you try flashing something like Franco or ElementalX? Or did you try using my instructions specifically?
Sent from my Google Pixel XL using XDA Labs

GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
GroovinChip said:
Yeah I'm not sure about Magisk. I do k ow that Magisk needs a custom kernel, so that might be your issue. Did you try flashing something like Franco or ElementalX? Or did you try using my instructions specifically?
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I haven't tried magisk yet. I just tried your instructions specifically. If I wanted to remove the changes I did from your instructions and try again, would this just mean flashing stock boot.img?

raazman said:
Thank you for this guide! I was wondering if we can use magisk instead of supersu?
Edit: I was not able to root this way. My device says it's not rooted.
Click to expand...
Click to collapse
I've seen some folks report that they couldn't get Magisk to work. I can't confirm that right at this moment though. You can test and see if it'll work by just using the TWRP provided. Not sure if it's based off RC2 or RC1.

raazman said:
I haven't tried magisk yet. I just tried your instructions specifically. If I wanted to remove the changes I did from your instructions and try again, would this just mean flashing stock boot.img?
Click to expand...
Click to collapse
It depends, are you able to boot to system? If not, like you're stuck in a bootloop, I'd suggest flashing completely back to stock. It would mean you'd lose your apps and data, but if you can't boot to system anyway then it doesn't really matter.
If you CAN boot to system, then I'd suggest just starting over and use SuperSu with SuHide. I doubt that any changes actually took place on your device since you didn't flash a custom kernel. But this is only if you can boot to system successfully.
Sent from my Google Pixel XL using XDA Labs

Worked great. Even let's me add a CC to Android Pay. I have not tested if it works yet.

GroovinChip said:
3) Download SuperSu Config
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
Click to expand...
Click to collapse
SBIN mode is the default one for Android 8.0, so you don't need to use SuperSUConfig at all.

Mike02z said:
Worked great. Even let's me add a CC to Android Pay. I have not tested if it works yet.
Click to expand...
Click to collapse
Great!
I haven't tested my debit card after adding yet either. Been home the whole time
Sent from my Google Pixel XL using XDA Labs

@GroovinChip Is your bootloader unlocked?

Kisakuku said:
SBIN mode is the default one for Android 8.0, so you don't need to use SuperSUConfig at all.
Click to expand...
Click to collapse
Ok, I'll edit the OP. I wasn't 100% sure, that's why I did it anyway.
Sent from my Google Pixel XL using XDA Labs

GroovinChip said:
Hi everyone, first time posting a guide here. I've started writing my own guides for the stuff I do to try and make it a bit more clear for myself, and I've decided to start sharing!
I literally just finished doing this on my own device, and I can confirm that it works with no issues; I'm passing SafetyNet and have root. However, as with all the other posts people make, I'm not responsible for any damage done to your device! I don't think anything will happen, this process is very painless.
EDIT: It's been confirmed that SuperSu Config is not required for Android 8.0, as systemless SBIN is the default for 8.0. I had seen this before, but decided to do it anyway to be extra sure (I like the extra redundancy). I'm leaving the steps in in case others want to be extra sure of this, or want the options provided by the installer.
1) Download the modded TWRP
2) Download SuperSU
3) Download SuperSu Config
4) Download SuHide
5) Copy the modded TWRP to PlatformTools. Rename it however you like. I'm using twrp-oreo for now.
6) Copy SuperSu, SuperSuConfig, and SuHide to internal storage
7) Boot the device into bootloader - adb reboot bootloader
8) Boot into TWRP - fastboot boot twrp-oreo.img
9) Flash SuperSuConfig, then choose add more zips. Choose SuperSU.
10) In the Aroma installer for SuperSuConfig, choose Systemless SBIN. For all other options, I chose let SuperSu decide.
11) Boot to system
12) Go back to bootloader and boot to TWRP
13) Flash SuHide
And that should do it!
Click to expand...
Click to collapse
Rooted perfect however I cannot uninstall system apps, how come?

have you tried going into adb shell and type the su command?

I'm using the system app remover from playstore. It says failed to uninstall.

Root works. AndroidPay works with SUHide!
Thanks!

Ok after reflashing, everything works as intended. Thanks for the guide!

I can confirm this works with the Pixel XL.

Stupid question but I'm guessing bootloader must be unlocked first correct?

Denton.S said:
Stupid question but I'm guessing bootloader must be unlocked first correct?
Click to expand...
Click to collapse
Not a stupid question yes, the bootloader mist be unlocked.
Sent from my Google Pixel XL using XDA Labs

GroovinChip said:
Not a stupid question yes, the bootloader mist be unlocked.
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
I was afraid you were going to say that. For one brief, glorious moment I thought I could get rid of adds without having to deal with this damn locked bootloader. My own mistake for getting the phone from EE direct. Thanks dude, much appreciated though

[GUIDE] Root using Magisk, keep stock recovery for OTA

This is a guide for people who want a rooted MIUI. It will keep stock recovery and system partitions untouched to allow MIUI OTAs to install without problems. It will also pass Google's safety net test so bank apps keep working. The best of both worlds really
Requirements:
- Unlocked bootloader
- Windows PC
- fastboot (present in the miunlock app folder)
- Latest TWRP (download here)
- Latest Magisk (download here)
Steps:
- Install latest Magisk app
- Put latest Magisk zip on your device storage (SD)
- Shut down device
- put latest twrp.img in miunlock folder
- Connect phone to PC
- Press volume down and power button to boot to fastboot mode
- Open "Command Prompt" on your PC
- Type: (without quotes)
----- "cd C:\Users\[your name]\Desktop\miflash_unlock-en-2.3.803.10" . (or wherever the folder is)
----- "fastboot devices"
----- "fastboot boot twrp.img"
- In a few seconds, TWRP will boot on your phone. DO NOT swipe to make changes to system.
- In TWRP, flash the Magisk zip
Enjoy root
Disclaimer: I will not be help responsible for any damage or loss caused by following those steps.

Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g

kn1g said:
Does it mean I can install TWRP and flash xposed etc and still have OTA updates?
What is the difference to this one: https://forum.xda-developers.com/redmi-note-4/how-to/red-wolf-install-twrp-root-device-t3708337
Best,
kn1g
Click to expand...
Click to collapse
Same as my question. Let say system partition won't touch by root, but twrp is installed over the Mi stock recovery. Will it install Eta?

This guide DOES NOT flash TWRP. Stock recovery remains so OTA updates work.
The only thing that is touched by this guide is the "Boot" partition to install magisk. You can restore stock "Boot" using magisk manager's uninstall option at any moment and be 100% stock again.

Ok, but is Xposed etc. possible?

kn1g said:
Ok, but is Xposed etc. possible?
Click to expand...
Click to collapse
I haven’t tried but should work.
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

It is really works! Thank you!

gonna check this cause i wanna root the phone but keep enjoying updates

I just rooted my Note 4 Qualcomm by this method, so far so good. Really easy and dummy-proof tutorial

I bump this because it worked. Quite easy, clean and fast. Thanx!

I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?

masri.razak said:
I already install latest TWRP for mido and latest magisk, but still I can not update my mido using OTA updater
Anyone can help me?
Click to expand...
Click to collapse
Wrong...u need to boot twrp not to install. Read the OP for steps.

Dadovvv said:
Wrong...u need to boot twrp not to install. Read the OP for steps.
Click to expand...
Click to collapse
Well... That's I mean, boot TWRP using adb
After have TWRP, how can i get update via OTA?

it successfully worked for Redmi Note 4 global beta/stable MIUI9.2
even installed camera api 2 using magisk module

Just a quick question. I've TWRP right now with SuperSU. So I'll remove SuperSU, flash Magisk in TWRP. All good till now, but I'd want the stock recovery, a flash-able zip maybe. How can I get it? From where?
**[EDIT]**
Okay. One can get it from fastboot ROMs available at MIUI website (here), extract the pack and get recovery.img.

Installed successfully on miui 9.2.1.0 stable
Now when a new update for magisk is released, how should i update it??

I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
I'd like to keep the phone untouched but I need to change emojis and with Xposed I can use Youtube in background.

Giacomo_ITA said:
I have two questions:
1. Why does the bootloader need to be unlocked and how can I do that?
2. What happens to Magisk if I install an OTA?
Click to expand...
Click to collapse
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)

Baxeisindi said:
1. sign on en.miui com and you can use xiaomi unlocker (after 72 hours)
2. two OTA updates and I had to reroot it
but it seems that it is not necessary, I can not post the link
google --> github magisk tips (it should be the first result)
Click to expand...
Click to collapse
Do you mean this?
When an OTA is available, please go to Magisk Manager → Uninstall → Restore Images. Do not reboot immediately or you will have Magisk uninstalled. This will restore your boot (or dtbo if available) back to 100% untouched stock images in order to pass verifications. This step is required before doing any of the following steps written below!
Click to expand...
Click to collapse

Giacomo_ITA said:
Do you mean this?
Click to expand...
Click to collapse
Yes, I hope it works, anyway at the next update I will reroot it in a few minutes.

Help with installing Magisk on Verizon Samsung Galaxy Note 3 SM-N900V

I have read many threads and lots of videos and cannot seem to get the Magisk installed.
I have flashed back to stock many times with (N900VVRUEOF1_N900VVZWEOF1_N900VVRUEOF1_HOME.tar.md5) in order to try multiple methods.
Rooted with Arabictoolapp - used rootchecker to verify/application also says true for root
followed: https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed: https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
installed twrp using official twrp app & also tried ODIN in another trial (picked verizon americas and got twrp-3.2.3-0-hlte.img.tar and twrp-3.2.3-0-hlte.img )
turned phone off and boot into recovery to verify; at this time i created a recovery
using MagiskManager i downloaded the zip (Magisk-v18.1.ip) and flashed using twrp - no errors but when i restart the phone it says Magisk not installed
next attempt was to extract the boot.img from the stock OF1 and then flash the Magisk - no errors but when i restarted the phone it says the same thing - Magisk not installed
another attempt was to patch the boot.img and got a patch_boot.img then using TWRP i flashed the patch_boot.img - restarted and magisk not installed
after further digging, i tried another method which was to unroot using SU, reboot, go into recovery to then install Magisk - magisk not installed
*note each attempt to install Magisk unrooted my phone
*was able to use Magisk-uninstaller-20190204.zip to uninstall Magisk manager from recovery - icon went away
anyways i am completely stuck now. any suggestions or comments on my approach?

jordanfan23 said:
installed SU from playstore to unlock bootloader using the adp method - shows developer mode to verify - using eMMc to verify CID starts with 15
followed:
Click to expand...
Click to collapse
Did you uninstall SU before trying to install magisk. The two together may cause conflict.

cssr said:
Did you uninstall SU before trying to install magisk. The two together may cause conflict.
Click to expand...
Click to collapse
Yes my last attempt i tried.

please help! there has got to be something i am doing wrong or missing. i can flash the uninstall zip and it does uninstall the magisk manager

@cssr any other input or suggestions?

jordanfan23 said:
@cssr any other input or suggestions?
Click to expand...
Click to collapse
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.

cssr said:
Try twrp 2.8.7 hltevzw. You are using the stock ROM which is android 5. Twrp 3.1 and higher is for android 7 and up. I missed that the first time I read your post.
Click to expand...
Click to collapse
no go =(

@cssr should i try another version of magisk?

jordanfan23 said:
@cssr should i try another version of magisk?
Click to expand...
Click to collapse
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?

cssr said:
Yes. Are you installing Magisk .zip in twrp and installing Magisk Manager APK after normal reboot?
Click to expand...
Click to collapse
what do you mean after normal reboot? so flash magisk in twrp. reboot. reboot again then install magisk manager? do you know what version of magisk i should run and where i can find the dl link?

What he means is you install the Magisk ZIP via TWRP in Recovery mode, reboot the phone, then you install Magisk Manager via the APK.
Go to magiskmanager dot com website which has the ZIP installer plus the APK for the Manager.

I only just recently tried to tackle this challenge. I also installed 0F1 with Odin, then rooted with Arabic. I was messing with Pokemon go and it wasn't happy I was rooted. I downloaded magisk manager, installed it that way. At reboot, angry message from Verizon that I have custom software and phone won't boot. I assume this is because I didn't install custom recovery.
If you figure a way to get this done, I will be grateful. One thing I don't quite follow. Magisk is a root method...so should we really be rooting the phone prior? Seems redundant and going against the whole point of magisk. Right?
I wanted to play around with spoofing GPS with PGO which requires making a GPS spoofer a system app (need root for that). Is that still possible using magisk?
I'll post any updates I have as well.

Root for RMX1931 Realme UI Android 10

fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no

Files
https://forum.xda-developers.com/realme-x2-pro/development/orangefox-recovery-x2-pro-t4063301
use vbmeta from this post
Magisk
https://github.com/topjohnwu/Magisk/releases/tag/v20.4

hi, any idea to fix fingerprint?

[email protected] said:
hi, any idea to fix fingerprint?
Click to expand...
Click to collapse
We need to wait for Realme to release a fix, just like what happened on color os when fingerprint wasn't working

On C.27 Bootloader Unlock and Root, Fingerprinter works

How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You

minoccio said:
How to upgrade from Android 9 Color OS 6 rooted and with magisk 20.4 to new C.27? Is there a tutorial? Thank You
Click to expand...
Click to collapse
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.

deviantor said:
Instal stock recovery like you did to install custom recovery.
Uninstall Magisk with the .zip from their site. Github here
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
So basically if I'm on c27 already, it's okay to use the same root method?

adsubzero said:
So basically if I'm on c27 already, it's okay to use the same root method?
Click to expand...
Click to collapse
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.

deviantor said:
Yea. I was on C27 total stock then followed these tips to root and custom recovery. Its all working well so far and fingerprint works.
Click to expand...
Click to collapse
I tried several thins to install Magisk succesfully with no luck.
I received my Global x2 Pro this thursday and i successfully unlocked the bootloader and flashed twrp recovery. But when I flask the magisk 20.4 zip and reboot my device, i get an error saying that my boot / recovery partition is corrupt. I have to install C27 again from twrp and it boots up.
Can anybody help me how to install Magisk succesfully? It's driving me nuts. Also, i cant download the vbmeta.img from the OP. So i tried to extract the vbmeta.img from the c27 image to flash, but also no lucck
Edit: Finally having it working with the Orangefox recovery with the vbmeta.img. I thought that the link in OneDrive wasnt working, but it was my home networks which was blocking OneDrive. Problem solved!

deviantor said:
Uninstall Magisk with the .zip from their site. Github here
Instal stock recovery like you did to install custom recovery.
Next, download the C.27 update and run it from the file manager. Phone will reboot and start updating
After update, just do the whole process to root C.27 version like for Android 9.
Click to expand...
Click to collapse
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?

minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
It's possible if someone makes a flashable zip, though I dont know of that can be done for every phone. Otherwise you need a stock recovery to install the OTA.

minoccio said:
Isn't it possible to install ota update from twrp? (I use mauronofrio). Is it mandatory to unroot, install C27 and then re-root?
Click to expand...
Click to collapse
Like @adsubzero said. Unless you have a custom ozip file to flash on TWRP, you need to have stock recovery to install a standard ozip.

ogutolopes said:
fastboot flash recovery OrangeFox-R10.1_1.img
boot in twrp
flash OrangeFox-R10.1_1.zip
rebbot in recovery
flash magisk 20.4
reboot recovery
flash vbmeta.img (FOR RECOVERY)
Clean caches
Reboot
fingerprint, no
Click to expand...
Click to collapse
for recovery mean recovery ka option ckick krna hai..vbmeta krty huay

In the backup options I don't see system, only system image. Does anyone else have this issue?