Database Develop

Root G800F with stock 6.0.1

Hi guys,
the new Firmware with Android 6.0.1 is launched. Is there a way to root it?
I know there is way with installing a mod with deodexing the ROM, but do u know another way?
Thx!

I tried the linked way. Unfortunately it doesn't work for me
Anyone who made to root the Arabic Update?

kixaze71 said:
I tried the linked way. Unfortunately it doesn't work for me
Anyone who made to root the Arabic Update?
Click to expand...
Click to collapse
A user in the 6.0.1 UAE thread suggests that the CF autoroot for 5.1.1 firmware works on 6.0.1 as well. Haven't tried it myself but if you try it tell us how it goes.

kom-pakt said:
A user in the 6.0.1 UAE thread suggests that the CF autoroot for 5.1.1 firmware works on 6.0.1 as well. Haven't tried it myself but if you try it tell us how it goes.
Click to expand...
Click to collapse
I tried CF Autoroot or to flash the current SuperSU.zip via TWRP.
Both times I get the following error if I trying to open the SuperSU App:
"There is no SU binary installed, and SuperSU cannot install it. This is problem! If you upgraded to Android 5.0, you will need to manually re-root - consult the relevant forums for your device!"
Of course I already tried different times after resetting and flashing the hole phone and also I tried an older SuperSU ZIP via TWRP, but everytime I get this error.

CF autoroot for 5.1.1 works on the 6.0.1 rom, I have just use it on 2 G800F without problem.
Envoyé de mon iPad en utilisant Tapatalk

kixaze71 said:
I tried CF Autoroot or to flash the current SuperSU.zip via TWRP.
Both times I get the following error if I trying to open the SuperSU App:
"There is no SU binary installed, and SuperSU cannot install it. This is problem! If you upgraded to Android 5.0, you will need to manually re-root - consult the relevant forums for your device!"
Of course I already tried different times after resetting and flashing the hole phone and also I tried an older SuperSU ZIP via TWRP, but everytime I get this error.
Click to expand...
Click to collapse
This is how I could root stock Arab 6.0.1 ROM:
1) Download original Firmware
2) Boot to recovery and wipe everything (internal storage isn't necessary, but it is always recommended to start a 100% clean
installation)
3) Boot to Download mode and flash original firmware using ODIN
4) Had to wait appr. 10 minutes to boot.
5) Let it boot, configure your things
6) Arabic apps (SHAHID and Papergarden) cannot be removed but you can disable them.
7) Start SuperSU. It gives you the usual message: "There is no SU binary installed,...." Dont worry just close SuperSU.
8) Go to ODIN in and flash Chainfire root (CF-Auto-Root-kminilte-kminiltexx-smg800f.zip)
9) Restart phone and root is done.
10) SuperSU could not be updated from PlayStore initially. However after restarting phone it was successful. Then it asks to update SuperSU binary...
11) Warning message of Knox pops up, you need to disable it. After this SuperSU binary is successfully updated. Restart phone and you are done.

how to switch from super su to magisk?

Hello, I am currently rooted on stock oos 4.0.3, with latest TWRP and super su free v2.79, can anyone help me out and tell me how to switch to magisk please, thank you!
Can I just use super su full unroot option then flash magisk?

Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.

palesaint said:
Either reflash the original boot.img or download the unsu script from https://forum.xda-developers.com/showpost.php?p=63615067, then flash magisk again.
Click to expand...
Click to collapse
so flash unsu, then flash magisk. simple?

Dr Grato said:
so flash unsu, then flash magisk. simple?
Click to expand...
Click to collapse
If you use the unSU script the process is:
unSU
stock boot image
Magisk

This method did not work for me.
I am on KETAN n10 and initially, viper did not work. I installed magisk but that didn't fix it. nor the meefik busy box. So i decided to uninstall magisk and go back to superSU and it magically worked...

I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:

SourPower said:
I unrooted from SuperSU itself like shown on the app's forum I believe. It rebooted my phone, I went into recovery first and then just flashed the latest magisk and made the switch :laugh:
Click to expand...
Click to collapse
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?

JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
If there's a proper backup of the boot image for the SuperSU app's full unroot option to restore, then that process should work perfectly (I've done it on a few devices myself). It's when it can't properly restore the boot image you might have issues and you'll have to do it yourself.
Take a look in the Magisk Troubleshooting guide, under "Moving from another systemless root solution to MagiskSU".

The nuclear method might be, to just flash the full stock OOS zip (can flash in TWRP) which will unroot and restore the boot.img (and everything else!). Then immediately flash Magisk before rebooting (so have the Magisk zip on the phone before updating). This should fully remove SuperSU, install Magisk, and keep TWRP on the phone.
Seeing as the original poster is still on OOS 4.0.3, you may want to update, anyway!

JG420 said:
So you just went into the SuperSU app and used the built in Unroot option, and when the phone rebooted, you went back into recovery and flashed the latest Magisk and did NOT flash a boot.img and everything worked fine? you have root with Magisk now instead of SU and you didnt get a bootloop at all??? (i really want to swap out SU for magisk in my sons LG G2, so he can play PoGo again lol) (His G2 is running CRdroid custom rom, I wonder if that effects the steps I'll need to take)
Can anyone offer me some guidance or assistance please and thank you?
Click to expand...
Click to collapse
I've done this on my 3t but I do have a G3 coincidentally lol, but yes I unrooted from su, it restarted my phone, before booting back into the system I went in twrp right away and then flashed magisk.

There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?

hypothrax said:
There are two options given in the SuperSU app, one is clean up to switch to a different SU app and the other is to permanently unroot. Which option is better?
Click to expand...
Click to collapse
I chose the Full Unroot option. Then flashed magisk. Worked perfectly.

Use the full unroot option. Catch here is that you might get dm-verity warning. It won't affect the phone in anyway but Android Pay might not work and you will see the warning for 5 seconds, everytime you restart the phone.

Thanks so much for ths thread. I am on Resurrection Remix OS and inititally installed SuperSU over Magisk (which came with the ROM). I decided that I wanted to use Magisk instead and followed the instructions in this thread and it worked a treat.

There is no SU binary installed. Help

My device is BLU Dash X2 ( D110L ) running android 6.0 with Kernel Version 3.18.19.
It's an MTK phone ( MT6580 ).
I managed to port and flash TWRP custom recovery by myself and it's working find. So I decided to flash SuperSU.zip with it. Everything seem to be working perfectly but after the flashing finished and I tried to open SuperSU app a message pop up with text "There is no SU binary Installed, and SuperSU cannot install it. This is a problem. If you just upgraded to android 5.0 you need to manually re-root - consult the relevant forums for your device!".
Please help me find a solution. I tried many version of SuperSU.zip already but the same message still appear. I also tried remove SuperSU app first before re-flash SuperSU.zip. I even tried to perform a clean stock rom flash before flashing latest SuperSU.zip and it's still the same.

I have the same phone, also managed to port TWRP, working fine after edit fstab, but no way I can root this device.
Tried with phh s SuperUser instead supersu, but no avail.
My biggest regret was buy this fone, it works fine but seems impossible to root.

Sorry for late update, you can root this device with magisk, successfully done with magisk v18.00

Super su
Sent from my Samsung Galaxy Note 8 using XDA Labs

[SOLVED] Samsung A5 2017 (A520F) Dual Sim - How to Root Nougat?

I flashed the Russian Firmware for my A5 (2017), but the Magisk 13.3 root method didnt work.
So far, I have failed in rooting Nougat with the following methods:
1. Magisk 13.3
2. CF Root although this is for Nougat. The phone goes into bootloop.
Currently, out of options as not too many options/info available for this phone.
Any definite way of rooting on this device?
[EDIT:]
SOLVED:
Flashed this version of SuperSU through TWRP and it worked!
Once installed SuperSU will ask KNOX detected, try to disable: Press OK.
Going to test it out & see if anything is off about it.
EDIT 2:
False Alarm. SuperSU flashed but does not have Root access as apss dont have SU Binary access. This is getting frustrating.
Any other way to root?

Keith0222 said:
I flashed the Russian Firmware for my A5 (2017), but the Magisk 13.3 root method didnt work.
So far, I have failed in rooting Nougat with the following methods:
1. Magisk 13.3
2. CF Root although this is for Nougat. The phone goes into bootloop.
Currently, out of options as not too many options/info available for this phone.
Any definite way of rooting on this device?
[EDIT:]
SOLVED:
Flashed this version of SuperSU through TWRP and it worked!
Once installed SuperSU will ask KNOX detected, try to disable: Press OK.
Going to test it out & see if anything is off about it.
EDIT 2:
False Alarm. SuperSU flashed but does not have Root access as apss dont have SU Binary access. This is getting frustrating.
Any other way to root?
Click to expand...
Click to collapse
For android 7. Extract boot.img archive. Install it from Twrp reboot then install magisk

say55 said:
For android 7. Extract boot.img archive. Install it from Twrp reboot then install magisk
Click to expand...
Click to collapse
Hey! Thanks for the reply. So, I just Flash this in TWRP like all Zip's and then Flash Magisk?
EDIT: It seems the boot image is something I have already tried, except I flashed SuperSU after, instead of Magisk. If you don't mind, could you go through this post, as this is the only problem remaining.

Samsung A5 2017 [A520F} Root issue resolved.
Gonna leave the steps for future reference if anyone needs it:
Firmware, Magisk & dm_verity all linked in my original post.
1. Install Samsung Nougat 7.0 (Russian Version in this case)
2. Flash TWRP
3. Try to flash dm-verity through TWRP
3. If it doesn't work go to Wipe > data > Change System Files > FAT & F4 wipe to change
3. Flash dm-verity again. The .zip should flash successfully this time.
4. Flsh Magisk 13.3. It will flash.
and you are rooted!

Keith0222 said:
Samsung A5 2017 [A520F} Root issue resolved.
Gonna leave the steps for future reference if anyone needs it:
Firmware, Magisk & dm_verity all linked in my original post.
1. Install Samsung Nougat 7.0 (Russian Version in this case)
2. Flash TWRP
3. Try to flash dm-verity through TWRP
3. If it doesn't work go to Wipe > data > Change System Files > FAT & F4 wipe to change
3. Flash dm-verity again. The .zip should flash successfully this time.
4. Flsh Magisk 13.3. It will flash.
and you are rooted!
Click to expand...
Click to collapse
Hi, will smart switch still work after rooting?

Root and Bootloop problem fix [Tested on RMX1993EX]

I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.

Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?

Lemmy554 said:
Didn´t faced this like you. I installed LOS from RUI and Magisk on the guided way without issues (I have RMX1993 also). What´s your ctsProfile status in magisk? False or true?
Click to expand...
Click to collapse
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.

Almasd said:
Now it's working well. How could I show ctsProfile. I tried terminal emulator and su to get root access. Then did props command. But it doesn't seem to there.
Click to expand...
Click to collapse
In Magisk Manager you have to "Tap to start SafetyNet check".

Oh I see. Thanks. It's ctsProfile: true. (Now I'm on stock rom with root)

Almasd said:
I tried to root my device with this instruction: https://forum.xda-developers.com/realme-x2/how-to/root-howto-t4011357
But I don't installed Manager.apk first. That might cause. But I don't know cause clearly, device was in boot loop.
I tried flash vbmeta and boot etc. but hadn't got luck.
Finally successfully turned on with stock ROM and then installed custom ROM and rooted.
My model is Euro RMX1993(EX)
Here is the what I did:
1. Installed Fastboot flashable ROM with fastboot.
2. Downloaded RMX1993EX_11.C.05 from https://www.realme.com/eu/support/software-update and installed it with TWRP
3. Cleaned cache/Dalwik, Format and Rebooted to system. Finally it's successfully booted up. :victory:
Then I installed Lineage OS with instruction step by step. After turned up phone I downloaded and installed Magisk manger apk from
https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
Then I rebooted to TWRP recovery again and installed Magisk zip.
Then directly rebooted to System. This time it's booted and root was success. Didn't installed touched vbmeta etc.
I hope it might help someone. It was very long road about 24 hours for me.
Update:
I reinstalled stock ROM and installed apk before flashed twrp &vbmeta. This time it's worked and finally I successfully rooted stock ROM.
Click to expand...
Click to collapse
How to unlock ur bootloader plz suggest me.

Risul49 said:
How to unlock ur bootloader plz suggest me.
Click to expand...
Click to collapse
I don't have RMX1993(EX) anymore. But below might help you.
If you are on ColorOS (Android 9) or RUI1 (Android 10) then you can directly follow the bootloader unlock tutorials on the internet. But if you are on RUI2 (Android 11) then you need to downgrade to RUI1 first.
I also did the same procedure.
But below is for RMX1901CN Realme X device procedure. I believe it would give you a hint.
1. I found Rollback_RMX1901_11_OTA_1190_all_EyyIUd8KYxPI.ozip (for Chinese version) firmware from Realme X Official Telegram group.
2. Then I opened it from the file manager and the device rebooted automatically and the downgrade firmware was installed. After that, I unlocked it with the DeepTesting app for RUI1 with instructions that I found on the internet.
Also, you might try this method: https://c.realme.com/in/post-details/1476520599785316352
Also, comments on this post might help (I have no idea Realme X2 Pro instruction is works for your device but JFYI): https://c.realme.com/in/post-details/1478098096796815360