Database Develop

[Q] Droid 4 CM12/5.0 Root

so I installed the latest CM12 Droid 4, and for some reason it's telling me I'm not rooted.
I was rooted in 4.1.2 using the razr utility for the XT894.
I first flashed original firmware
then did step 3 (root)
then installed safestrap using a 3.75 download link.
booted into recovery, installed latest CM12 nightly...
... but i can't get root access?
How do I restore root access now that I'm on 5.0.x?
Yes, I ENABLED root access in developer options. Still won't give root access.
Root Checker says:
Root access: no access
Su Found: system/xbin, system/bin

Hi,
After flashing CM12.1 you need to flash SuperSU:
http://forum.xda-developers.com/showthread.php?t=1538053

Actually, I didn't have to do that. I just started over again. I did try flashing SuperSU by downloading the APK they have linked on the playstore page, through SafeStrap Install ZIP function, but it didn't work.
I went with the Razr Utility and installed 4.1 with wipe. then reinstalled root. then I went and installed safestrap 3.75, followed by lollipop.
all is well now.
I think the cable extension i was using was causing packet loss issues of somesort, as i can touch the cable end and it cuts in and out. But the root process said it was completed successfully. I think it just didn't go through the cleaning process and left files over that caused a root loss of some sort.
It seems to be fine now.

Cm12 has it's own root, and is different from stock rom.
When device is in twrp recovery, it doesn't matter if Rom is Rooted or not.
Guessing it was a bad cm12 install, you didn't need to reflash firmware, just reboot to twrp, reinstall the Rom.
May need to redownload the Rom, and verify the md5 checksum.
To root Rom in twrp use
SuperSu flashable zip (UPDATE-SuperSU-v2.45.zip - 28 Jan 2015)
Sent from my XT907 using Tapatalk

sd_shadow said:
Cm12 has it's own root, and is different from stock rom.
When device is in twrp recovery, it doesn't matter if Rom is Rooted or not.
Guessing it was a bad cm12 install, you didn't need to reflash firmware, just reboot to twrp, reinstall the Rom.
May need to redownload the Rom, and verify the md5 checksum.
To root Rom in twrp use
SuperSu flashable zip (UPDATE-SuperSU-v2.45.zip - 28 Jan 2015)
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
if you look at my second post, I said I tried to install the SuperSU binary using recovery, and it did not do anything.
I just reinstalled the rom after wiping the partition to avoid any issues.

Can't install TWRP after updating to Nougat

I recently updated my EVA-L09 to Android 7.0. Before that, I was rooted and I had TWRP. After I updated, I obviously would need to install TWRP and root again, but when I install it with SRK Tool or even with fastboot, it always goes back to stock recovery. I already tried to flash it by "recovery.img" as well.

Gutito said:
I recently updated my EVA-L09 to Android 7.0. Before that, I was rooted and I had TWRP. After I updated, I obviously would need to install TWRP and root again, but when I install it with SRK Tool or even with fastboot, it always goes back to stock recovery. I already tried to flash it by "recovery.img" as well.
Click to expand...
Click to collapse
that would be because the TWRP in SRK Tools is only for android 6 (EMUI 4.1 - 4.1.1) and not for android 7 (EMUI 5 - 5.1)
the recovery that you need to use in order for twrp to be installed is this one https://github.com/OpenKirin/android_device_huawei_eva/releases/download/3.1.0/twrp-3.1.0-0-eva.img
then once its installed boot up your phone and then type in "adb reboot recovery" and that will then boot your device into TWRP 3.1.0.0

Thank you, it worked!
Another question, but now related to SuperSU.
I am with the 2.79 version of SuperSU and I downloaded the binary .zip of this version and flashed it by twrp. The problem is that it keeps saying ""There is no SU binary installed and SuperSU cannot install it. This is a problem!".

I already got it to work. Thanks btw

Gutito said:
I already got it to work. Thanks btw
Click to expand...
Click to collapse
Could you post how perhaps? I had the same problem as you - the TWRP posted about fixed my first problem but now I can't get SuperSU to install either. Would be interested to know how you fixed it!

kzip said:
Could you post how perhaps? I had the same problem as you - the TWRP posted about fixed my first problem but now I can't get SuperSU to install either. Would be interested to know how you fixed it!
Click to expand...
Click to collapse
I solved it by this post https://forum.xda-developers.com/showpost.php?p=70927601&postcount=456
I ended up not using super su but If you want you can use it instead of the one suggested there
By flashing the file provided in the post, I managed to automatically get access to super user (root)

[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?

Is there any way to root this phone?

Please don't suggest the regular ways to root the j7 prime. I tried cf auto root as well as the supersu.zip method to root this. Twrp cant mount data. After flashed supersu.zip. it shows integrity verification and after i reset my phone in that screen. I lose supersu. What can i do to root my stock rom. Its up to date. Please any one suggest me a working method . I don't want to lose any of my data again.

before flash supersu.zip
you must be fomatdata
enjoy

Can you suggest me a recovery that mounts data? Thanks in advance

https://forum.xda-developers.com/ga.../recovery-twrp-3-2-0-galaxy-j7-prime-t3716355

flash TWRP first via odin and if you don't know on how to use odin, there's a lot of tutorials in youtube. then after you flash the twrp flash also superSU in order to root your unit.

SuperSU is from the past, flash Magisk instead. Just make sure you have the latest version of TWRP for J7 Prime and put the magisk flashable zip in your internal storage since TWRP can't recognize Sd card yet. and BTW you DON'T need to format anything just do a backup for the sake of data safety and go on

Installed Magisk 19.3 using TWRP, seems not installed in Magisk Manager.

Hello,
I flashed a stock ROM on my Samsung Galaxy Tab S3 running Android 7.0.
Then I installed TWRP, and with that Magisk 19.3. All were installed successful, however after rebooting there was no Magisk Manager app, so I installed this myself.
When opening the Magisk Manager app it shows that Magisk has not been installed.. how can I fix this?
I've been trying for 10 hours now, I really need help.
Before flashing the ROM I had TWRP installed with SuperSU.

NeroDePero said:
Hello,
I flashed a stock ROM on my Samsung Galaxy Tab S3 running Android 7.0.
Then I installed TWRP, and with that Magisk 19.3. All were installed successful, however after rebooting there was no Magisk Manager app, so I installed this myself.
When opening the Magisk Manager app it shows that Magisk has not been installed.. how can I fix this?
I've been trying for 10 hours now, I really need help.
Before flashing the ROM I had TWRP installed with SuperSU.
Click to expand...
Click to collapse
1. Uninstall Super SU
2. Uninstall Magisk from TWRP (using uninstall.zip)
3. Install Magisk.zip latest version in TWRP
4. Install Magisk Manager latest version using APK
Remember to use both latest versions of Magisk (zip and apk).
It should work for you.
Sent from my SM-N960F via Tapatalk

zencooler said:
1. Uninstall Super SU
2. Uninstall Magisk from TWRP (using uninstall.zip)
3. Install Magisk.zip latest version in TWRP
4. Install Magisk Manager latest version using APK
Remember to use both latest versions of Magisk (zip and apk).
It should work for you.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
The thing is, I did a full clean stock ROM install and there is no SuperSu app left on my device.
If I download the SuperSu APK now it says I don't have ROOT access and therefore I cannot uninstall SuperSu using the APK.
I have used Root Checker Basis (app) to check if there is a ROOT available, but it says ROOT access is not properly installed on this device.
Is it still possible for SuperSu to be installed on my device while I cannot see or find it? Even after a clean install?
Also, I believe 19.3 is the latest version of Magisk. I also tried 19.2, but I am having the same problem with that version.

NeroDePero said:
The thing is, I did a full clean stock ROM install and there is no SuperSu app left on my device.
If I download the SuperSu APK now it says I don't have ROOT access and therefore I cannot uninstall SuperSu using the APK.
I have used Root Checker Basis (app) to check if there is a ROOT available, but it says ROOT access is not properly installed on this device.
Is it still possible for SuperSu to be installed on my device while I cannot see or find it? Even after a clean install?
Also, I believe 19.3 is the latest version of Magisk. I also tried 19.2, but I am having the same problem with that version.
Click to expand...
Click to collapse
I don't know what the smartphone you have but the best way is to get boot.img from stock firmware and then patch it via Magisk Manager (you can install it even if you don't have root). Then after boot.img is patched you can flash it instead of the standard boot.img (any method you are doing it now).
BTW: the latest version of Magisk is 19.4. Check it on Magisk repository.
Sent from my SM-N960F via Tapatalk

zencooler said:
I don't know what the smartphone you have but the best way is to get boot.img from stock firmware and then patch it via Magisk Manager (you can install it even if you don't have root). Then after boot.img is patched you can flash it instead of the standard boot.img (any method you are doing it now).
BTW: the latest version of Magisk is 19.4. Check it on Magisk repository.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
I am using a Samsung Galaxy Tab S3 (T825). I used a stock firmware from SamMobile (which exists of 5 times an .tar.md5 file) and flashed it on my device using Odin.
[EDIT] So here is what I did. Made a back-up using TWRP, and used that boot.img to patch in Magisk Manager.
Now I have a patched IMG file. But when I want to install it using TWRP I have to pick a partition and I am not sure which one to pick.
[EDIT] I tried installing it, and it was successful, yet shows the Magisk manager app that there is no ROOT available.
I guess I just need to start from the very beginning over again. Can you help me with that?
I have stock firmware .zip for my T825 from SamMobile which I can install using Odin.
I also have a working TWRP .zip file that works fine with that firmware on my device.
Other than that I'll need guidance because I keep screwing up :')
Your help is much appreciated

I did a factory reset, flashed TWRP, and installed Magisk using TWRP. After rebooting there was no Magisk Manager app (but it did install a TWRP app).
I installed the Manager app with a downloaded .apk (latest version) and it shows that Magisk is not installed.
So, I want to try patching my .img file using the manager app. The only problem is that I do not have an .img file, as I used . md5 files.
Can I make a back-up with TWRP and use the .img file from there?