Related
EDIT: Unfortunatelly this is not working any more due to recent SafetyNet updates
Hello everyone. This is first guide i'm trying to write here so don't be to harsh for me also sorry for my english, it's not my native language.
After almost 3 days of messing with various roms and kernels i finally managed to successfully installl Magisk V6 on my Z3 D6633 (yes, Pokemon Go 0.37 works too ) .
First of all you need unlocked bootloader. Without it you won't be able to flash custom kernel. Also, if your kernel is still locked, and you want to unlock it remember that doing so will wipe all data from your device, so backup everything that is important to you prior to following this guide.
This is the setup that works for me:
SLiMM 3.1 rom by Wajk:
http://forum.xda-developers.com/z3/development/rom-slimm-t3359907
Advanced stock/beta kernel Marshmallow 6.0.1 - 06/aug/2016 by Gustavo RD78:
http://forum.xda-developers.com/z3/development/kernel-advanced-stock-kernel-t3345880
Magisk v6 - The Universal Systemless Interface by topjohnwu:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Here are the steps:
1. flash rom with 6633 patch, reboot
2. full unroot and clean in SuperSU, reboot
3. flash kernel, reboot
4. flash Magisk V6 and PHH root, reboot
5. install PHH root from play store and Magisk Manager
I used SafetyNet Helper to verify if SafetyNet is working several times during all those steps:
after 1 - not working,
after 2 - working,
after 3 - working,
after 4 - not working,
after 5 - not working,
after disabling root in Magisk Manager - working.
Hope it helps someone
Hi,
For this tutorial I still need the unlocked bootloader?
Regards!
ask the following I
is a LB or UB requirement ?
If the Rom matter as long as the kernel is flashed ?
If the whole with D6603 ?
Thanks for your tutorial
adripred said:
Hi,
For this tutorial I still need the unlocked bootloader?
Regards!
Click to expand...
Click to collapse
smellz said:
ask the following I
is a LB or UB requirement ?
If the Rom matter as long as the kernel is flashed ?
If the whole with D6603 ?
Thanks for your tutorial
Click to expand...
Click to collapse
I haven't try with locked bootloader, because I unlocked mine a while ago, but in the kernel thread there is info that unlocked bootloader is required. It might be possible to do it with other roms, as long as they work with Advanced Stock Kernel from the link in first post. D6603 should work too, only difference is that you don't need dual sim patch for SLiMM 3.1 rom
I must have had a similar problem to you originally, I had a working D6603 with a Rooted Marshmellow 6 Rom.
Then, performed the following Steps;
1. Unroot (Inside the SuperSU App)
2. Booted into TWRP and flashed Magisk - v6
3. Then Flashed phh 's systemless superuser
I rebooted the phone and now it is not working. Does not Boot, Black Screen.
The Led will flash red quickly and I am not able to boot into TWRP.
I can see the Phone is Recognised by the Computer (S1 /SOMC Flash Device in Device Manager.)
Could someone please post step by step instructions to restore a to Marshmellow Rom (Any)?
Will I have to download an Image and a Flashtool?
same problem here. I manage to boot to twrp by flashing back the recovery image using fastboot.
Z3- said:
I must have had a similar problem to you originally, I had a working D6603 with a Rooted Marshmellow 6 Rom.
Then, performed the following Steps;
1. Unroot (Inside the SuperSU App)
2. Booted into TWRP and flashed Magisk - v6
3. Then Flashed phh 's systemless superuser
I rebooted the phone and now it is not working. Does not Boot, Black Screen.
The Led will flash red quickly and I am not able to boot into TWRP.
I can see the Phone is Recognised by the Computer (S1 /SOMC Flash Device in Device Manager.)
Could someone please post step by step instructions to restore a to Marshmellow Rom (Any)?
Will I have to download an Image and a Flashtool?
Click to expand...
Click to collapse
Resolved using Emma. I installed the S1 SOMC Flash Device Drivers and I was able to download lollypop.
I will attempt now to reinstall recovery, new rom, and Magisk
Guide helped alot thanks!
Important part was to uninstall SuperSU. Before that ROM appeared to reject the kernel or vice versa, but now it boots on Fragment ROM and unmount seems to work!
Better be worth unlocking the BL
Z3- said:
I must have had a similar problem to you originally, I had a working D6603 with a Rooted Marshmellow 6 Rom.
Then, performed the following Steps;
1. Unroot (Inside the SuperSU App)
2. Booted into TWRP and flashed Magisk - v6
3. Then Flashed phh 's systemless superuser
I rebooted the phone and now it is not working. Does not Boot, Black Screen.
The Led will flash red quickly and I am not able to boot into TWRP.
I can see the Phone is Recognised by the Computer (S1 /SOMC Flash Device in Device Manager.)
Could someone please post step by step instructions to restore a to Marshmellow Rom (Any)?
Will I have to download an Image and a Flashtool?
Click to expand...
Click to collapse
Just flash stock kernel with flashtool.
This Process worked for Me - D6603
1. flash SLIM Rom 6603 and reboot
2. Disable SuperSu, Unroot SuperSu, Boot to Recovery and Wipe Davilk, Reboot
3. Reboot to Recovery, Flash Advanced Kernel, Reboot
4. Flash Magisk V6 and PHH root, Reboot
5. install PHH Super from play store and Magisk Manager
Thanks for the tuto.
Of course you need to have Unlocked Bootloader, this is the principle of flashing a custom kernel. And systemless root like magisk needs custom kernel. With LB you will not boost after flashing a custom kernel.
kotlin said:
Hello everyone. This is first guide i'm trying to write here so don't be to harsh for me also sorry for my english, it's not my native language.
After almost 3 days of messing with various roms and kernels i finally managed to successfully installl Magisk V6 on my Z3 D6633 (yes, Pokemon Go 0.37 works too ) .
This is the setup that works for me:
SLiMM 3.1 rom by Wajk:
http://forum.xda-developers.com/z3/development/rom-slimm-t3359907
Advanced stock/beta kernel Marshmallow 6.0.1 - 06/aug/2016 by Gustavo RD78:
http://forum.xda-developers.com/z3/development/kernel-advanced-stock-kernel-t3345880
Magisk v6 - The Universal Systemless Interface by topjohnwu:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Here are the steps:
1. flash rom with 6633 patch, reboot
2. full unroot and clean in SuperSU, reboot
3. flash kernel, reboot
4. flash Magisk V6 and PHH root, reboot
5. install PHH root from play store and Magisk Manager
I used SafetyNet Helper to verify if SafetyNet is working several times during all those steps:
after 1 - not working,
after 2 - working,
after 3 - working,
after 4 - not working,
after 5 - not working,
after disabling root in Magisk Manager - working.
Hope it helps someone
Click to expand...
Click to collapse
thanks for sharing this... and did you try to install Systemless Xposed? is it working on your Z3?
It didnt work for me... the Magisk manager cannot toggle Root...it just greyed out...
kotlin said:
Hello everyone. This is first guide i'm trying to write here so don't be to harsh for me also sorry for my english, it's not my native language.
After almost 3 days of messing with various roms and kernels i finally managed to successfully installl Magisk V6 on my Z3 D6633 (yes, Pokemon Go 0.37 works too ) .
This is the setup that works for me:
SLiMM 3.1 rom by Wajk:
http://forum.xda-developers.com/z3/development/rom-slimm-t3359907
Advanced stock/beta kernel Marshmallow 6.0.1 - 06/aug/2016 by Gustavo RD78:
http://forum.xda-developers.com/z3/development/kernel-advanced-stock-kernel-t3345880
Magisk v6 - The Universal Systemless Interface by topjohnwu:
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Here are the steps:
1. flash rom with 6633 patch, reboot
2. full unroot and clean in SuperSU, reboot
3. flash kernel, reboot
4. flash Magisk V6 and PHH root, reboot
5. install PHH root from play store and Magisk Manager
I used SafetyNet Helper to verify if SafetyNet is working several times during all those steps:
after 1 - not working,
after 2 - working,
after 3 - working,
after 4 - not working,
after 5 - not working,
after disabling root in Magisk Manager - working.
Hope it helps someone
Click to expand...
Click to collapse
thnx for this workaround. if you follow it to the letter, you should be fine, else it won't work, and you still get "cts profile match: false"
( it cost me 2 attempts because i flashed the kernel directly)
finally there is someone who desire to create specific systemless method with magisk for xperia device line
unfortunately I've tried earlier than this thread exist so I have to clearance to noob xperia user, here's my post
ryandxter said:
well well I'm here just to give specific classification / explanation about what is this projects do
I'm here to say that this method is about modifying boot partition to make systemless works (correct me if I'm wrong), since my device was Xperia Z3 then this require "unlocked bootloader" for any Xperia device in case to use custom boot.img script from this projects... please please OP underline this before another people from Xperia users with locked bootloader flash this projects, thanks
I'm already tried on myself almost hardbricking my phone and this isn't funny
Click to expand...
Click to collapse
that's mean xperia device line (no exception) need to be Unlocked Bootloader before flashing magisk otherwise the'll soft brick
hi mr @kotlin can you add this to OP for specific clarification?
that's mean xperia device line (no exception) need to be Unlocked Bootloader before flashing magisk otherwise the'll soft brick
hi mr @kotlin can you add this to OP for specific clarification?
Click to expand...
Click to collapse
and don't forget that unlocking the bootloader is easy, but your phone will be wiped clean.
( i forgot about that....)
Z3- said:
This Process worked for Me - D6603
1. flash SLIM Rom 6603 and reboot
2. Disable SuperSu, Unroot SuperSu, Boot to Recovery and Wipe Davilk, Reboot
3. Reboot to Recovery, Flash Advanced Kernel, Reboot
4. Flash Magisk V6 and PHH root, Reboot
5. install PHH Super from play store and Magisk Manager
Click to expand...
Click to collapse
This worked for me!
ataraxist said:
thanks for sharing this... and did you try to install Systemless Xposed? is it working on your Z3?
It didnt work for me... the Magisk manager cannot toggle Root...it just greyed out...
Click to expand...
Click to collapse
Yes I installed Systemless Xposed from magisk thread, it works like a charm, hadn't any problems Did you followed all the steps? It's order is very important. You have unlocked bl? I just put info in op that it is necessary. For me toggle root was greyed out when i didn't properly flashed magisk to kernel, or after restoring kernel. Try to make backup and follow the steps again.
ryandxter said:
finally there is someone who desire to create specific systemless method with magisk for xperia device line
unfortunately I've tried earlier than this thread exist so I have to clearance to noob xperia user, here's my post
that's mean xperia device line (no exception) need to be Unlocked Bootloader before flashing magisk otherwise the'll soft brick
hi mr @kotlin can you add this to OP for specific clarification?
Click to expand...
Click to collapse
Thanks, just did that
kotlin said:
Yes I installed Systemless Xposed from magisk thread, it works like a charm, hadn't any problems Did you followed all the steps? It's order is very important. You have unlocked bl? I just put info in op that it is necessary. For me toggle root was greyed out when i didn't properly flashed magisk to kernel, or after restoring kernel. Try to make backup and follow the steps again.
Thanks, just did that
Click to expand...
Click to collapse
I'm coming from Xperia Z... not z3
can't be sure if the problem is coming from different advance stock kernel...
Thanks for sharing the steps...I will try again when I have time...
I finally got it working after several attempts. Everyting went well with unlocking the bootloader and installing the rom.
In magisk manager i got Selinux toggle working for me. I just cant use the root toggle. The toggle is on, and if i want to disable it it says: magisk manager is granted superuser acces. Then it turns the toggle back on. Should i not grant SU acces to the magisk manager or is there another problem?
I've had this working a while and even used Android Pay for the first time. However Viper4Android doesn't seem to be working well and sounds are too quiet do any existing mods still work or would they break SafetyNet?
I'm on a B09, bootloader unlocked and rooted with SuperSU 2.65 A2017G.
Except from the 2.65 version, is there another one working for the A2017G?
I want to get Xposed and if I do understand I need SuperSU 2.75 or above to get Xposed to work in systemless.
If there isn't another version could you guys help to get Xposed working on my phone?
That would be much appreciated.
EDIT: Well I'm dumb, I assumed Oki's guide only worked on the A2017U variant. Sorry guys :/
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Yeah I figured it out with the help of Oki's guide.
Thanks for the answer!
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
nuserame said:
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
Click to expand...
Click to collapse
Did you make sure to disable system write protection? Boot into TWRP, open up the terminal emulator, and issue the command: reboot disemmcwp
I'm having a similar problem while flashing superuser. The error happens after the "patching sepolicy" line runs. The error prevents SuperSU from being installed at all. Any suggestions?
You need to flash twrp 3.0.3 or above and flash SuperSU 2.79
Latest SuperSU Causes Endless Loops on the Axon 7
Literally, every time I install the latest version of SuperSU on my axon I get an endless bootloop. These are SuperSU files I get directly from chainfire's website. There must be something im missing, or maybe im downloading the wrong version? Im not sure i was hoping to get some help. I just tried installing: SR3-SuperSU-v2.79-SR3-20170114223742.
>> Can anyone point me in the right direction of the latest SuperSU that works with the Axon 7 that doesnt bootloop it.
I remember that the Pixel phones had SuperSUs that were made for it. I am wondering does the same thing apply here?
I have installed everything right on my phone to the T. Everything was brand new stock.
Kinanizer said:
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Click to expand...
Click to collapse
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.
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
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
SteadyDisorder said:
I can't seem to find any rooting method for C432B380 software. Is there any step-by-step guide for this version? I'm currently on fully stock firmware, and I haven't unlocked my bootloader yet.
Click to expand...
Click to collapse
Well, ask for unlock code - that's the first step.
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Makishima said:
I am interested in this as well, as from what I see some people seem to run into problems. Say one is on Nougat C432B380 (I'm B381) and has now got the unlock code. What then? First of all, unlocking the bootloader will result in a reset, clean C432B380 installation, right? Or will there be any need to flash something else?
EDIT: I passed the unlock part following the Guide, and ended up with a clean Nougat installation as I thought. Now what? In the OldDroid TWRP thread I see many people having trouble...
Click to expand...
Click to collapse
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Moemen Shahawy said:
I recommend staying away from any custom roms for now as all seem to have problems... you say you have an unlocked bootloader, then next step would be flashing a custom recovery, then from there... flashing supersu... try not to do much more than that and accept a fully functioning rooted phone better than getting a squichy camera or whatever from custom roms.... wait till they get stable
Click to expand...
Click to collapse
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Makishima said:
I was not planning to install a custom ROM, I just want root, mainly for Viper4Android and some other things, but after reading the whole OldDroid TWRP thread I saw some people reporting problems with bootloops and whatnot, mainly after flashing SuperSU. Is flashing TWRP and then EliteKernel and rooting with phh or Magisk preferable? I just got my device back from the Huawei services, with a new board and everything and I don't want to ruin the stock installation again, so I am trying to be a bit more certain before I do anything.
Thank you for replying.
EDIT: Okay, so what I did was flash the latest OldDroid TWRP through fastboot and then I booted into recovery and flashed the latest Magisk (v13.3 I think). Now I have root and everything seems to work. So happy.
EDIT2: It seems that although it says I have root, I can't actually do anything with it, e.g. I can't uninstall system apps with Link2SD even though it says it was successful - reboot, still there - and the modules won't appear even after installing.... So, I don't know what's wrong.
Click to expand...
Click to collapse
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Moemen Shahawy said:
stay away from magisk if you want something stable... at least my opinion. Magisk is fine, the only add it adds, is magisk hide, which seems to keep failing now for most people. I'm suffering through it now and switching to supersu... try finding the correct way to remove magisk root and go the chainfire's supersu
Click to expand...
Click to collapse
I restored a backup of the boot partition I had made when I first flashed TWRP which seems to have deleted Magisk, the app told me it was not installed (even though I see now a Magisk folder in data...) and then flashed Super SU, but I still can't delete system apps and having trouble with Viper*. But maybe it's not SU's fault. I don't know. I flashed v2.79, I previously had trouble with the newest versions.
Also, I had not activated the Hide function, I think.
*It is driving me crazy! Why does it not work? Supposedly I am root, I even deleted the system apps with the file managers but when I exited and reentered the folder they were there again. What is going on?... Wait... Is this normal, is it because it is system-less root?
To root any nougat fw:
1)unlock bootloader. You have to get unlock code from huawey and then in fastboot mode do: "fastboot oem unlock yourcode"
2)flash twrp recovery, i suggest you the hassan's recovery https://www.androidfilehost.com/?fid=745425885120756473
3)in fastboot mode do "fastboot flash recovery nameoftherecovery.img
4)reboot in recovery and flash this supersu
It is the 2.82 for emui 5 without loop mount,is perfect for p9lite https://www.androidfilehost.com/?fid=817550096634776377