Database Develop

xposed-v80-sdk23-arm.zip - BOOTLOOP Nexus 5, stock latest firmware (February patch)

Hi, my Nexus 5 is using: Stock firmware rom (feb patch)
ElementalX Kernel (latest) Latest SuperSu root
SELinux set to passive
Busybox Pro installed
I tried flashing the xposed installer under TWRP but it comes up with Error Executing updater binary, I cleared the cache, waited about 10mins and still bootlooping. I then re-downloaded the file, same problem when flashed again. I have ran the uninstaller flash that has now removed the bootloop, but the question remains how do I get it to install successfully? Thanks.

djdynamite123 said:
Hi, my Nexus 5 is using: Stock firmware rom (feb patch)
ElementalX Kernel (latest) Latest SuperSu root
SELinux set to passive
Busybox Pro installed
I tried flashing the xposed installer under TWRP but it comes up with Error Executing updater binary, I cleared the cache, waited about 10mins and still bootlooping. I then re-downloaded the file, same problem when flashed again. I have ran the uninstaller flash that has now removed the bootloop, but the question remains how do I get it to install successfully? Thanks.
Click to expand...
Click to collapse
Most likely, system partition has not enough free space to fit xposed files in place. Try deleting/uninstalling unnecessary system apps such as keyboards you don't need (e.g. Pinyin, etc...)

Nexus 6 + SuperSU + ElementalX = no (full) root?

Root checker and AdAway are telling me that I don’t have root. I’ve rooted my phone using super su and other root apps are working ( FireFlash and Clocksync for example). But AdAway and BusyBox are not.
Flash stock system.img (june security update)
Flash stock boot.img (june security update)
Flash supersu
Flash elementalX
No profit ☹
I’m using:
twrp-2.8.6.0-shamu
ElementalX-N6-3.16
Systemless supersu 2.74 ( on I have 2.65 same issue)
Everything was working for me since last year after update to june security update I can't root fully my phone . Any ideas? Please help.

You didn't give much information about the state or history of your device before hand. Stock/Custom ROM? Wiped? Factory reset from stock recovery? For starters, you're using a way outdated version of TWRP. Should be 3.0.2-0. Install the latest recovery and try flashing SU again from recovery. Any errors? Record them. If that doesn't work, flash the stock recovery and do a hard factory reset and try again using fastboot (not FF).

radziop said:
Root checker and AdAway are telling me that I don’t have root. I’ve rooted my phone using super su and other root apps are working ( FireFlash and Clocksync for example). But AdAway and BusyBox are not.
Flash stock system.img (june security update)
Flash stock boot.img (june security update)
Flash supersu
Flash elementalX
No profit ☹
I’m using:
twrp-2.8.6.0-shamu
ElementalX-N6-3.16
Systemless supersu 2.74 ( on I have 2.65 same issue)
Everything was working for me since last year after update to june security update I can't root fully my phone . Any ideas? Please help.
Click to expand...
Click to collapse
flash your kernel first. EDIT: first meaning before supersu. And also try updating to TWRP 3.0 always want to stay up to date on recovery releases.

I have the same set up with root...

radziop said:
Root checker and AdAway are telling me that I don’t have root. I’ve rooted my phone using super su and other root apps are working ( FireFlash and Clocksync for example). But AdAway and BusyBox are not.
Flash stock system.img (june security update)
Flash stock boot.img (june security update)
Flash supersu
Flash elementalX
No profit ☹
I’m using:
twrp-2.8.6.0-shamu
ElementalX-N6-3.16
Systemless supersu 2.74 ( on I have 2.65 same issue)
Everything was working for me since last year after update to june security update I can't root fully my phone . Any ideas? Please help.
Click to expand...
Click to collapse
I have the exact same issue. The issue is we can't seem to remount the system partition as read/write anymore.
The problem is that for the life of me I can't get it to remount using any method. Someone else has the same issue also https://www.reddit.com/r/nexus6/comments/4nvgfv/can_no_longer_modify_system_after_june_ota_even/
Any help would be appreciated.

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

Mi Max 2 (Oxygen), trouble with rooting !!!

The situation:
1. Mi Max 2 is unblocked.
2. Has TWRP 3.2.1-0.
3. Has been rooted before :laugh: (used in MacroDroid 3.22.0 for starting GPS and TomTom Go and checked with Root Check 4.3.7.0), but root disappeared after an update. Now running Android 7.1.1 (Nougat).
4. Rooting again always fails.
a. with Mi Max 2 Rooter`via my PC with W10Pro.
b. with Magisk-v16.0 with TWRP.
c. with lazyflasher-no-verity-opt-encrypt and SuperSU-v2.82-201705271822 with TWRP.
They al run OK, with only the message after:
Checking patch status:
--- Already patched, attempting to find stock backup :victory:
--- Stock backup restored :victory:
After Wis cache / dalvik and Herstart (takes a while) the Mi Max 2 is still NOT rooted :crying::crying::crying: (checked with Root Check 4.3.7.0).
What am I doing wrong, please help. SciFi.

There are a few thoughts I have:
1 - in your root management tool, did you give your root required apps permission to root?
2 - have you tried a "fresh" install of your ROM from fastboot (if using official ROM) with full wipe?
3 - in TWRP, can you find the su app (likely in /system/bin or /system/xbin)?

@mollex
Here is what i did for a successful Magisk root
1) Clean flashed the Global stable 9.5.4.0 via Fastboot method and set up as normal ( i tried this procedure on Global Dev rom, you will fail the safety net check )
2) Once set up, boot to Stock Recovery and wiped twice to ensure it is clean
3) flashed TWRP 3.2.1.0
4) flash MAGISK V14 via TWRP, again, V14 only i tried to flash v16 directly it throwed a lot of error messages , once magsik v14 is flashed boot into system and install the latest magisk manager .apk
5) install the latest Magisk Manager then it will ask you to install the latest version of Magisk , install and reboot
once rebooted here is what you will see , a fully rooted mi max 2 with safetynet fully passed, greetings from the Philippines

Thanks bmg002,
1. Of course.
2. A full wipe costs me 2 days work, I 'll try any other way.
3. I'll have a look. Not found.....
fire.fox_009,
I will try Magisk again, according your advise.
Were can I find MAGISK V14?
Clean flash of the Global stable 9.5.4.0 means wipe Data, System and Dalvik /ART cache. I loos 2 day's work. Try to find another way.
Everything I in TWRP do with Magisk gives: No digest file found, followed with a 225 error.
Thanks (from the Netherlands) anyway for advise.
PS. I am rooted now !!!!! Used the latest MAGISK: Magisk-v16.4.zip. :highfive: you all.

Magisk patch on SM-A520F (Galaxy A5 2017) FAILED

Hello,
I've been using magisk for some time now and no problem until now. I recently updated my firmware to the last version and intended to update it and keeping magisk, but it didn't worked.
Every time I would flash magisk to the boot image by any mean, the system would boot and tell me "system was modified : press the nuke button to restore it (you will lose all your data lol)" or womething like that.
I was able to flash the stock update and get my phone working with the last firmware but magisk is not installed. I also installed TWRP without problems (helped me a lot to flash the stock boot.img and restore the phone).
I tried to install magisk using :
- Odin : Modified boot.img using magisk app and repacked as boot.img.lz4 in the AP file (with correct lz4 parameters)
- TWRP : Flashed modified boot.img from earlier
- TWRP : Flashed magisk ZIP directly
- Odin : Flash full AP modified by Magisk app
Every time, I have that black screen that tells me my system will be wiped if I continue. Magisk, Odin or TWRP do not return any error
Feel free to ask for any file or further info and thank you for your help !
Firwmare version is A520FXXUGCTKA_CL19831441_QB36271825_REV00
Magisk app returns :
- Ramdisk YES
- A/B NO
- SAR NO

Did you try after you install the new rom through Odin, then instal Twrp and then in Twrp you Format data(not wipe) then immediately install magisk. If dosen't work try with another firmware.
I never update firmwares if there isn any visible difference. Mostly is always some security fixes which i dont care about.

hey, Im having a different issue where after installing lineage 18.1 on my a5 i flashed the latest magisk but once i got in the phone it cycled into a bootloop and now it's eternally turned off cant even turn it into twrp. any suggestion?