Database Users

Root not sticking! Need professional help.

Good evening ladys and gentlemen,
hoping you can help me with my root-not staying-problem.
I have the A2017G B09 version. I already managed to unlock my device and I had root with xposed installed.
Sounds good so far, right?
Well my problem is that after the restart that is needed to activate my xposed modules, my root went away and I couldn't get it back. After that I tried to do it again but root wouln't stick no matter what.
And yes, I did use the "reboot disemmcwp" command.
I tried to root by flashing the newest chainfire supersu 2.79, since I have newest twrp 3.0.3-1.
It would be great if you would be able to help me on my journey and maybe explain to me the difference between systemless and normal, and what magisk is since I saw that op up a few times.
Oh and please tell me from where I should start if I want to work on everything android related (roms, kernel, apps) since my semsester is nearing its end.
Thanks in advance.

Systemless root means that the /system partition is not modified, however the boot image is altered. There is much hype on this, however there still are many mods out there requiring modifications of /system. I personally do not see any advantage of it, probably because I have been using custom ROMs for years, and custom ROMs has many alterations to the /system compared to stock or pure CM or AOSP roms. However it is clear that the future goes that way and eventually most of the mods will be systemless. The advantage is that you will supposedly be able to flash OTA upgrades, however if the OTA is also modifying the boot partition, then it doesn't matter, you will not be able to flash the OTA upgrade. So the benefits of systemless mods are arguable.
Magisk is an open root. it is systemless from the beginning and any module under Magisk framework will be systemless. So far no official Magisk release (latest at this time is v10.2) is compatible with the Axon stock ROM. However, the latest v10.3-beta2 seems to fix the root injection problem. It is included in the Bad Boyz custom ROM.
There are some apps not working on root devices. They use a SafetyNet procedure to check for that, such as Android Pay or Pokemon Go. However there are ways to overcome this security check and you can enjoy root and SafetyNet compatibility either using SuperSU or Magisk, system or systemless root. the issue becomes a little tricky when adding Xposed mod framework to the mix, since the procedures to have all 3 (root, SafetyNet and Xposed) working is not that straightforward. However this is possible in the Axon 7. You can find one of my guides in the links in my signature.
Enjoy!!!!

Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.

Try reflashing supersu don't reboot, then use terminal in TWRP to do reboot disemmcwp and see if it works. I usually use root Explorer to see if I can change /system to r/w. If it did not work go back to terminal in TWRP and try again. I have had to do it a few times to get it to work. Using adb terminal seems to work first time, terminal apps have not worked for me.

Yuujinz said:
Thanks for the info. I actually used your guide but nothing came out of it. I got stuck on the Axon screen. Tried it multiple times. Guess I'll try again either after the N update or when I get impatient.
Click to expand...
Click to collapse
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.

Oki said:
If you tried my guide, then you must use ROM B29 or any other ROM based on B29. I am afraid that the patch is only compatible with B27 or B29 based kernels.
Click to expand...
Click to collapse
Wouldn't it brick my european device?

Yuujinz said:
Wouldn't it brick my european device?
Click to expand...
Click to collapse
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484

Oki said:
You can flash directly the BootStack for your version of Axon 7 and the B29 ROM (or any other custom ROM) using TWRP. You can get those files from https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Click to expand...
Click to collapse
Ok thanks I'll do it this evening
Or maybe not, to risky.

[T-Mobile D6616] Updated Root Method Request

Good afternoon,
After MUCH research, I have arrived at the conclusion rooting the D6616 with T-Mobile's likely final Z3 build for 5.0.2 (Build 23.1.C.0.399 and, really anything past KK) is no longer possible without involving Kingroot.
Why does this matter? Because there may not be a feasible way to remove the most recent builds of Kingroot from the D6616 ROM. Using Kingroot's own uninstaller in the App settings fails and factory resetting using the ROM/stock recovery threw my phone into a bootloop. Other users report it successfully factory reset their ROM with kingroot installed as a system app and their device no longer rooted. I attribute the variety of outcomes to different software builds and Kingroot versions.
It seems as though the only working root method also uses ZXDualRecovery. Though I have not tried it, all procedures that show the ZXDualRecovery method of pushing recovery and superSU involved rooting the device with Kingroot first and removing it after SuperSU is installed. This appears to be the only still-working method of acquiring temporary root long enough to install recovery. The only way to remove Kingroot is to use flashtool and a new Sony TFT, which also removes root and recovery.
Has anyone successfully been able to pull off rooting a D6616 lately? I want to keep this phone but it is unfortunately useless to me without working root so I'll likely be returning it if nobody still has one that's running the last software with a locked bootloader.
I would really appreciate any help anyone can give.

I believe I have done it! I think SuperSU is ever so slightly ahead of Kingroot.
What I did:
1) Rooted via Kingroot app on Google Play. Run rootchecker after it's done its business to make sure. DO NOTHING ELSE IN THE APP. Doing so may prevent SuperSU from kicking its ass later.
2) Downloaded and upacked to desktop the file for Xperia Z3 from here:
http://nut.xperia-files.com/path/XZD...ecovery_2.8.26
Z3-lockeddualrecovery2.8.26.-RELEASE.combined.zip
3) Disabled antivirus
4) Installed USB drivers via Windows 7 plug-n-play. Unplug phone.
5) Downloaded SuperSU recovery flashable zip from here:
http://www.supersu.com/download#zip
6) Ran install.bat from extracted ZXDualRecovery zip
7) Enabled developer options in phone, enabled USB debugging, revoked USB devices, rebooted phone, plug in phone.
8) Connect Phone, wait for device to register in windows.
9) Okayed communication from PC.
10) Place in USB Install Mode on phone.
11) Choose option 2 to install to device rooted by SuperUser. Kingroot has blocked option 1 (old method)
12) Enter TWRP (Automatic) and go to Backup, check all boxes, create Nandroid by sliding the slider
13) Reboot, ensure phone boots. Put SuperSU.zip on the external flash drive. Go to your new App: NDR Utils. Choose TWRP as Primary Recovery. Choose Reboot to Primary recovery
14) Flash zip for SuperSU. DO NOTHING ELSE. Do not wipe cache, do not fix permissions. Click REBOOT.
15) Launch SuperSU App. Attempt to update Binaries. It will not, but it will detect Kingroot, and somehow can get rid of it itself using onboard capabilities. It will do so and update binaries.
16) Reboot (Automatic via SuperSU)
17) Check to make sure SuperSU binaries installed by launching the app.
18) Reboot to recovery using the steps from step 13) above.
19) Create another backup using step 12) above
20) Reboot and DONE.
To the best of my knowledge, nobody has indicated how to do this in a clear Step-By-Step for the final build of this ROM. So because I've troubled you all for small chunks of the process I figured I would.
This applies to T-Mobile's likely-final software release for the Xperia Z3 android 5.0.2 on build 23.1.C.0.399.
DISCLAIMER TO ANYONE ATTEMPTING THIS: It appears Kingroot is "onto" what it is being used for. Given the behavior of this application, there is no reason for anyone to believe it is not a malicious program, but it is a necessary evil for this purpose. Newer versions of SuperSU are capable of removing Kingroot on their own, but alternative methods may be necessary. I attempted an earlier version of SuperSU and it was incapable of removing Kingroot.
It might remove via debloater. This is the only way to remove the system apps on this phone reliably, so you WILL need it if you intend to keep the bootloader locked. I couldn't get any root-enabled appstore app to do it including ES File explorer and Titanium Backup. It looks like you need a computer to remove system apps on this phone. Fantastic. Debloater works great though so don't be afraid to use it. Use the filter to search for Apps. You can remove them, but they will not be gone until you reboot your device. Hooray no more filecommander and lookout! Debloater can be found here:
https://forum.xda-developers.com/and...bloat-t2998294
Plug in your phone. Give it root access. Easy peezy.
Then Xposed current framework and installer:
https://forum.xda-developers.com/sho....php?t=3034811
Version 3.1.1 fixed the bootloop problem, so you shouldn't need the fix zip, or at least I didn't. But if you do, you can find it here:
https://dottech.org/187028/how-to-fi...-z5-z4-z3-tip/
Flash the framework for your device in recovery (arm) and then the installer APK from the ROM using a file browser.
FINALLY Youtube Adblock and minimized playback. SCORE!
I think that's about it. That's literally the best we can currently hope for from this device. I think there is an Xposed module to heavily alter the look of the ROM here but I have not tried it. Plus it only claims to work w/ 4.4, and we have 5.0.1.
https://forum.xda-developers.com/z3/...6#post71601966
For devicewide adblocking I use DNS66 since there are no proxy settings for adblocking on this device, unless I'm missing something. I really hope I am. This means there's no native adblocking.
Xposed modules worth using you can find by searching in the Xposed store: Blurred System UI (LP), Gravity Box [LP], RootCloak, Xperia/AOSP NavBar Buttons, Xperia Super Radio, YouTube AdAway, YouTube Background Playback. And of course DNS66 (PlayStore).
I have tinkered with the rest and find them of no value.

I followed the steps but SU didn't ask to update anything. It just opens up and everything is fine?
Then all I did was unistall kingroot(purify) and it looks like it's gone, but is it?

Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.

stef-nix said:
Just leaving this here, this is how I rooted on Android 5.0.2 with the D6616
http://nut.xperia-files.com/
Read the documentation that comes with the latest XZDualRecovery and flash SuperSU or whatever you want.
Click to expand...
Click to collapse
Were you able to install twrp without rooting first on your PC? It doesn't work for me. I did option 3, install on unrooted device.
Are you able to systemless root?

When I run the installation it fails at step 3 on the install bat.

Hi, a bit of an old thread, but has anyone had any success rooting the D6616 without using Kingoroot or Kingroot? Both are malware which are designed to not be fully removed and be as resilient as possible, and uninstall does not actually uninstall them...

Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.

i followed these steps, and have gotten to the point where you flash supersu and reboot, but i'm stuck in a reboot loop now. wanted to use this old z3 as a dedicated audio player, and needed to root for some audio enhancements...
edit: i did have TWRP for a minute, but now when i go into recovery it's the stock recovery again, with options only to continue booting, boot to safe mode, factory recovery or power down. the first two options return to a boot loop. can/should i attempt to use flashtool, or factory recovery? i don't want to accidentally wipe something i might need in the backup.\
UPDATE 10/19: I was able to get back to ground zero using Sony's xperia companion software repair. Flashtool 9.25 and 9.26 would never successfully install flashmode drivers, nor would it display the stock .ftf file.

fierogt42 said:
Yes, the old method still works. Use the search feature. I'd just link you, but I"m busy at the moment.
Click to expand...
Click to collapse
this new method seems to fail for me on both of my old z3's. does the method you're referring to involve downgrading to 4.4.4? i've done some extensive searching of this forum (and the android development ones as well) but don't seem to be able to find any other info.

Rooting Moto G4 Plus

I just got my Moto G4 Plus and want to root it. Does somebody have a good guide for rooting it?
I found this guide on youtube, can I just follow this?: https://www.youtube.com/watch?v=g3bhXe3msxU&t=3s

What stock OS are you running on your device, Marshmallow or Nougat?

echo92 said:
What stock OS are you running on your device, Marshmallow or Nougat?
Click to expand...
Click to collapse
I just updated to Android 6.0.1 Marshmallow

If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.

echo92 said:
If you're on Marshmallow (6.0.1), then the guide you linked should work, you may wish to keep the stock kernel (and not flash ElementalX). Also, instead of phh superuser, you could choose to flash SuperSU or magisk.
Here's a guide for rooting on Marshmallow 6.0.1 as well https://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772 You may wish to use a newer build of SuperSU than mentioned in the guide - the latest build currently is 2.82 SR1.
Click to expand...
Click to collapse
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw

skismas said:
I found a video that showed how to unlock bootloader, and uses SuperSU when rooting. Can I use this guide insted, or is it to old you think?: https://www.youtube.com/watch?v=dK2uacpjGwc&t=119s
Thank you so much for all the help btw
Click to expand...
Click to collapse
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12

Don't FLASH TWRP, just BOOT it up, do whatever you need to do and... keep your stock bootloader. The TWRP is useful mostly for CM/Lineage ROM's, for stock it's just a headache waiting to happen.

echo92 said:
Looking through that video, I think it should work for 6.0.1 - as an aside for anyone reading this, the root procedure for Nougat is different. Though the resources linked in the video may work (I have not tested them), you may, as I mentioned above, wish to flash newer versions of TWRP and SuperSU than that linked in the video:
TWRP - (official): https://dl.twrp.me/athene/
I personally use shreps' TWRP: https://forum.xda-developers.com/mo...covery-twrp-3-0-2-r3-moto-g4-g4-plus-t3494337
SuperSU v2.82: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703 Ideally, you'll want to use v2.79 SR3 or newer as they're systemless root.
EDIT: this guide linked to in the video has a nice description of some of the steps you'll need: https://forum.xda-developers.com/moto-g4-plus/how-to/guide-newbie-resource-thread-t3386584
One thing I'd add to those guides is before you flash SuperSU, make a backup of all of the partitions in TWRP (on the TWRP main menu, you'll see 'Backup'). If SuperSU fails to root or causes instabilty, you'll have a backup to fall back to.
Additionally, when flashing TWRP, you'll see the 'Image not signed or corrupted' warning, that's normal. As long as [OKAY] comes up in fastboot after flashing and you reboot to recovery afterwards (so TWRP is set as your recovery), then TWRP should stick.
You may also receive OTA messages - do not accept these whilst rooted and with TWRP. if you wish to turn them off, have a look here: https://forum.xda-developers.com/showpost.php?p=72373828&postcount=12
Click to expand...
Click to collapse
I managed to root my phone without bricking it! I think......
SuperSU was not on the phone when I rebooted the phone like in the video. I had to download it through play store. But since it says its rooted on root checker, and I could grant it permission, im pretty sure I done it right.
Thanks for the help I really appreciate it

Any root method for the Moto G4 yet?

Is there a working root method for the Moto G4 (Running Android 7.0) yet?
And I'm not talking about the G4 plus...
I desperately want to break my phone free.
There must be one by now.

TheTechnoToast said:
Is there a working root method for the Moto G4 (Running Android 7.0) yet?
And I'm not talking about the G4 plus...
I desperately want to break my phone free.
There must be one by now.
Click to expand...
Click to collapse
G4 and G4 plus use the same method, flash TWRP then elemental x kernel and then you can root it With super su or magisk.
Enviado desde mi Moto G⁴ #StayUnbeaten

syverman said:
G4 and G4 plus use the same method, flash TWRP then elemental x kernel and then you can root it With super su or magisk.
Enviado desde mi Moto G⁴ #StayUnbeaten
Click to expand...
Click to collapse
Thanks for the reply! Is there a guide to do this?

TheTechnoToast said:
Thanks for the reply! Is there a guide to do this?
Click to expand...
Click to collapse
I wanted to try it but I have a problem with the bootloader that I can not unlock because my computer is the amazon version that no one could remove said ads in the latest security update NPJ25.93.14.5, if anyone knows of any solution I will be grateful .

TheTechnoToast said:
Thanks for the reply! Is there a guide to do this?
Click to expand...
Click to collapse
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting

echo92 said:
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting
Click to expand...
Click to collapse
Thanks for this. Yes, I'm okay with all of this (I've rooted my previous phones), I'm aware of the risks and stuff. I'll give this a try ?

flako72 said:
I wanted to try it but I have a problem with the bootloader that I can not unlock because my computer is the amazon version that no one could remove said ads in the latest security update NPJ25.93.14.5, if anyone knows of any solution I will be grateful .
Click to expand...
Click to collapse
Um... Could you ask questions in your own forum please? This forum is for rooting help for the Moto G4.

TheTechnoToast said:
Um... Could you ask questions in your own forum please? This forum is for rooting help for the Moto G4.
Click to expand...
Click to collapse
I think he is asking about the Moto G4 Amazon version. So he is in the right forum.

Caxref said:
I think he is asking about the Moto G4 Amazon version. So he is in the right forum.
Click to expand...
Click to collapse
Oh, okay. But even still - I think he should be asking the question individually. Not only would he get more help from people but it wouldn't detract from my post.

echo92 said:
This guide shows you how to root with SuperSU https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
Ensure you've flashed a custom kernel such as ElementalX before rooting, else you'll trip anti-rooting protections built into the stock kernel, which may necessitate a re-flash of your stock ROM. You may wish to use newer versions of SuperSU. Alternatively, if you wish to use magisk for rooting, you can have a look at this guide I've written based on the above link: https://forum.xda-developers.com/showpost.php?p=72496111&postcount=270
I've used this method to root a G4 Plus running NPJS25.93-14-8 (June 2017 stock ROM) with magisk 13.3 and have EX Kernel Manager, Amaze and other root utilities running okay. Furthermore, with the built-in root hiding abilities of magisk, SafetyNet dependent apps appear to run okay. I believe SuperSU has a similar addon to hide root from various detection methods too.
Something I've run into with using the stock ROM with TWRP is that Google Play Store may show an error 0 when attempting to download apps or updating. Seems this is related to permissions issues on the data partition and you may be able to correct them with this post: https://forum.xda-developers.com/showpost.php?p=73604008&postcount=19
As mentioned above, the same steps should apply to G4 devices (and has been tested on G4 devices). As usual, unlocking your bootloader will wipe your device (as a security measure) so back up your data and move it off your device. You may wish to back up your SD card if adopted as internal storage (or find a way to save your encryption key). Also, requesting the unlock key from Motorola, regardless of whether you use it, appears to void your remaining service warranty.
Futhermore, once rooted, you will not be able to accept OTA updates, and attempts to do so will soft-bootloop your device unless you boot to bootloader and select 'Start' to boot to system. To accept OTA updates, you'll have to revert back to a clean stock ROM (and of the same build or newer - attempts to revert back to older stock ROMs than what you had, especially if you were previously on the March/June 2017 patch level, have a nasty habit of hard bricking if you took OTA updates).
If you're okay with all that, then good luck rooting
Click to expand...
Click to collapse
Thanks so much! Worked perfectly on the Moto G4.
Consider the question closed

SM-G5520 Nougat Not Flashing GApps with Flashfire after rooting with magisk, Help me

I Have SM-G5520 Nougat, I rooted it successfully here
Link: https://forum.xda-developers.com/sa...g5520-g5520zcu1brb1-nougat-root-twrp-t3772104
But, as mentioned there, I run Flashfire, Grant root access, Browse for GApps.zip and flash it, but after click on flash screen goes black and didn't show any proccess of flashing GApps.
After waiting 2 - 4 Hours, There was still a black screen like my phone is off and I restart my phone. Now there is not a single GApp installed there. Please help me to flash GApps.
I continue my research on rooting and flashing and i got some points that are below,
1. Magisk is system-less root that's why when ever i tried any app to modify system folder or root directory my phone got restart.
2. I tried SuperSU system-less but the device isn't going to root.
3. I tried King Root, Kingoapp, OneClickRoot, Dr. Phone root, iRoot and much more with and without PC but my device was not going to root but only Magisk root my device.
4. I tried CFAuto Root with all modifications but due to my phone didn't have "OEM Unlock" option, flashing CF Root cause failure.
5. I tried to push GApps into Original Firmware, but that way takes a lot time and i failed there because of security reasons (And that was my first attempt to modify "Firmware" I must failed ).
All the conclusion of my work let me know that i have to root my SM-G5520 Nougat as system root that will going to work 100% to flash GApps.
Now Please help me to root system wise and flashing GApps.
Thanks Advance

plz contact Gsm helper team