Related
Hi everyone! Yesterday I updated my new Sony E1 phone (D2005) to the latest firmware 20.1.A.2.19 with KitKat 4.4.2, and tried to root it with Root Genius 2.2.6: it worked! I just had to install first the ADB drivers shipped with FlashTool and then used Root Genius to root the device. It was as simple as that! I'd like to know if it was just me being lucky or this procedure can be applied to every E1.
Hello Atanor7,
thank you for information. I'll try this asap.
Do you flash a new rom or upgraded from previous one?
Did you remove Genius after boot? Don't install Genius too much bloatwares?
I upgraded from stock firmware via PC Companion (the phone is brand new, purchased yesterday, 70 euros!), then used Genius to root. It's a Windows program, so you have to install nothing on your device, just the ADB drivers on your PC (I used a VM to install so bloatware wasn't an issue for me). After rooting, Genius automatically installs Kinguser to manage root permissions.
Atanor7 said:
I upgraded from stock firmware via PC Companion (the phone is brand new, purchased yesterday, 70 euros!), then used Genius to root. It's a Windows program, so you have to install nothing on your device, just the ADB drivers on your PC (I used a VM to install so bloatware wasn't an issue for me). After rooting, Genius automatically installs Kinguser to manage root permissions.
Click to expand...
Click to collapse
As boatware, I spoke about Kinguser, supposed to be replaced by Supersu
another question: do you kept your settings after upgrade (apps, screens, sms, calls, wifi points, bt devices, ...)?
I can't tell you about that, the phone was new so didn't have any personalization yet, the only settings I made (WiFi, couple of apps) were kept.
Do you think I should replace Kinguser with SuperSU?
Ok, after reading about how KingUser could be a "tricky" app I switched to SuperSU: the "SuperSU-me" app from the store did the job quick and flawlessly. Thank you for your advice
Atanor7 said:
Ok, after reading about how KingUser could be a "tricky" app I switched to SuperSU: the "SuperSU-me" app from the store did the job quick and flawlessly. Thank you for your advice
Click to expand...
Click to collapse
I tried to uninstall kinguser after supersu setup, but IMPOSSIBLE
how did you uninstall kinguser?????
I only can freeze it with titanium, but impossible to remove any file of that f****** app!!!!!
daktary said:
I tried to uninstall kinguser after supersu setup, but IMPOSSIBLE
how did you uninstall kinguser?????
I only can freeze it with titanium, but impossible to remove any file of that f****** app!!!!!
Click to expand...
Click to collapse
Install this app from the Play Store: "Super-Sume" and run it. Hit the button and... it does it all, wipes Kinguser and replaces it with SuperSU, works like a charm!
Thank you for your advice Atanor7, I think I am late for that since I tried to use Super-Sume to replace Kinguser app but it didn't work on my case.
It's good to know that it worked on yours because next time if I reflash my phone I will try to use Super-Sume again.
in my case, I went for old fashion root after unsuccessful attempts on using Super-Sume, I flashed 20.1.A.29 then flashed back the kernel and root with towelroot then flashed back 20.1.A.29 kernel after rooted.
Atanor7 said:
Install this app from the Play Store: "Super-Sume" and run it. Hit the button and... it does it all, wipes Kinguser and replaces it with SuperSU, works like a charm!
Click to expand...
Click to collapse
ok works for me, super-sume didn't ended (probably because supersu was still installed), but after closing app, kinguser was uninstalled without traces
thanks
Atanor7 said:
Hi everyone! Yesterday I updated my new Sony E1 phone (D2005) to the latest firmware 20.1.A.2.19 with KitKat 4.4.2, and tried to root it with Root Genius 2.2.6: it worked! I just had to install first the ADB drivers shipped with FlashTool and then used Root Genius to root the device. It was as simple as that! I'd like to know if it was just me being lucky or this procedure can be applied to every E1.
Click to expand...
Click to collapse
genial
Atanor7 said:
Hi everyone! Yesterday I updated my new Sony E1 phone (D2005) to the latest firmware 20.1.A.2.19 with KitKat 4.4.2, and tried to root it with Root Genius 2.2.6: it worked! I just had to install first the ADB drivers shipped with FlashTool and then used Root Genius to root the device. It was as simple as that! I'd like to know if it was just me being lucky or this procedure can be applied to every E1.
Click to expand...
Click to collapse
Hello Atanor7,
it's my first time that I root a smartphone (it's the same that you have), so I've no experience with what you've written. Can you please make a kind of guide, please ?? Where can I find Rootgenius and the ADB drivers ??? What is flashtool and how to use it ?? Can you link the url to download it ???
Thank you for your gentle reply.
No one can help me ??? Some one other can link me a guide how to root a Sony Xperia E1 D2005 ?? Please help me.
iamnone said:
No one can help me ??? Some one other can link me a guide how to root a Sony Xperia E1 D2005 ?? Please help me.
Click to expand...
Click to collapse
1. Download ADB: https://drive.google.com/file/d/0B0MKgCbUM0itVVFWRC02Q0VBQnc/view
2. Install it.
3. Downlod Root Genius: http://www.shuame.com/en/root/
4. Enable USB Debugging.
5. Launch Root Genius and click on Root. Thats all.
This is driving me nuts... I was on 5.1.1 and I am trying to get it rooted.
I'm following a guide which goes like this..
1. downgrade to kitkat 4.4 using flashtool
2. root 4.4
3. Install custom recovery
4. Flash 5.1.1 pre-rooted zip
I have had problem after problem and I think something may have screwed up along the way.
I finally managed to get kitkat installed using flashtool and a generic C6903 .108 ftf.
Problem 1... I used 'Easy Root tool' from xda to root kitkat... but it seemed to hang at the cleaning up' stage - is this a problem?
Problem 2... every time I restart my phone - kitkat asks what language etc. Whats that all about?
PROBLEM 3. The guide Im following says to install busybox after rooting kitkat.
I've tried 2 different busybox installers and both of them fail when trying to install bb.
QUESTION: Are these 3 problems linked and will it prevent me from continuing with the guide I am trying to follow??? i.e. do I need busybox to install XZ Dual Recovery and therefore a pre-rooted zip?
Root Checker basic says kitkat is rooted, as does the first busybox installer.
I'm taking a short break from this nightmare, so in the meentime if any of you chaps could advise me on whether or not its ok to continue or if I have fecked up the whole process, that would be great.
Thanks in advance
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Gamer4Life said:
problem 1 : re run the installer again, don't use administrator mode
problem2 : use any simcard on your phone
others, sorry i have no idea, you could download busybox from playstore ?
Click to expand...
Click to collapse
Problem1... thank you, I'll try again
Problem2... Thanks. I thought It could be the lack of a SIM card and then I thought no! that can't be it lol... as usual - I was wrong ha
others... yeah mate, tried 2 different installers from play store - no joy with either.
Thanks for your help
xasbo said:
I would just start over and try a different root program. busybox is failing to install because the root didn't work.
Click to expand...
Click to collapse
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
thesweeney80 said:
Cheers bud, I'll try 'easy root tool' once more without admin priv, if its the same story I'll start over and try a different root tool. Any suggestions on that?
Also: how come root checker says I'm all good and rooted but busybox wont install? even one of the busybox installers says "Your device is rooted"!?!?
Thanks for all the help mate
Click to expand...
Click to collapse
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Gamer4Life said:
i think you don't have supersu installed, and busy box couldn't get root rights
so download supersu from playstore, open it and update binaries as normal, then reboot
and you would be able to install bb
Click to expand...
Click to collapse
thanks for the tip mate but no joy see my reply to xasbo, cheers
xasbo said:
Try the suggestion made by @Gamer4Life, just in case you somehow got root but it failed to install the APK needed to manage it. Might save you some work. That would explain why everything thinks you're rooted.
As for an alternative, if you still need it, I think I used kingroot successfully on 4.4.4.
Click to expand...
Click to collapse
Thanks mate. I was hoping Gamer4life might be right as there was no Supersu installed.
I installed supersu from play store no problem... but when I try to update binaries it says' update failed. Please reboot and try again.'. tried reboot but same story.
I guess I'll try 'easy root tool' again and then will give kingroot a bash if needbe.
One last pre-emptive question...
If I root kitkat using kingroot... should I replace kinguser with supersu before proceeding with XZDR and a pre-rooted zip or will kinguser be sufficient to continue.
Many thanks to you and everyone else who has tried to help me with this clusterf*ck,.. I appreciate it
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Gamer4Life said:
can you screenshot the error you got ?
i reread your op, you don't need busybox to install dual recovery, it installs like the easy root installer, very easy
just one click and you are ready to go
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
must have been a glitch in the matrix mate becuase its now working (Possibly thanks to your suggestion of installing Supersu?).
I reconnected to PC in order to give 'easy root tool' another crack at it.
As soon as I start install.bat It says checking if device is rooted AND I get a superuser request on my phone for adb.shell - Happy days!
I granted root access to adb shell and the root tool says Job Done. Root success etc.
So I disconnect and try to update su binaries and it worked first go!!!
*Touch wood* I think I'm now past the tricky part and it should be plain sailing from here on in. lol
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Gamer4Life said:
also xzdualrecovery will root your device and install supersu by default if you have kitkat, so you can skip that.
edit (i don't think this will work because towelroot doesn't work on z1 4.4.4 108)
Click to expand...
Click to collapse
Correct, TowelRoot doesn't work for this version.
---------- Post added at 01:27 PM ---------- Previous post was at 01:26 PM ----------
thesweeney80 said:
THANKS for the help Gamer4Life, and everyone else who has chipped in.... hopefully my next post will be to report a fully rooted 5.1.1 :fingers-crossed:
Click to expand...
Click to collapse
:good: godspeed
@thesweeney80 you are welcome have fun
xasbo said:
:good: godspeed
Click to expand...
Click to collapse
Gamer4Life said:
@thesweeney80 you are welcome have fun
Click to expand...
Click to collapse
you fellas are the muts nuts.
All done, everything went smoothly once I got kitkat rooted properly.
MANY thanks for all your help.
Honestly I wouldnt even bother owning a smartphone if it wasnt for the peeps on XDA... F*cking awesome. THANKS :good: :highfive:
:good: awesome! don't forget to pay it forward sometime.
Hi there fellows ! ^^
First of all, I want you all to know that I really am sorry if this is something that has been asked before. I tried, but couldn't find an answer by myself and I don't want to damage my phone again (I may have been waaaaay too hasty in the past...). So here goes.
I have a Honor 5C NEM-L51 (European variant) which I rooted a while ago (two or three months ago maybe ? Can't remember for sure) by unlocking the bootloader, installing TWRP from ADB, flashing the SuperSU zip file... You know, the usual thing. After that I went ahead and installed Xposed Framework, Busybox and several applications and modules which needed root like many of you I guess. Everything went fine. And still is, for the record.
Now I realize that I may have been living under a rock because I discovered very recently that not only SuperSU can be downloaded from the Play Store but also that there is Magisk, an open-source alternative with more functionnalities. Guess what ? I want it.
Soooo I did some research and read this https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 along with other articles here and there on the web and it seems that I'd just have to install some Magisk Manager app' from the Play Store... Is that really all there is to do ?!
I'm worried because it says "If you're already rooted with MagiskSU or Latest Official Systemless SuperSU". Yep, the "Systemless" part get me worried. While I do understand what it means, I can't help but wonder : since I installed SuperSU from a flashable zip file, is it Systemless ? How can I tell ?
Plus the whole thing is kinda confusing to me. If I do that, will Magisk remove SuperSU ? But if so, won't there be a problem with Xposed and other apps that need root ? Same question applies if I first manually remove SuperSU (assuming I can actually do that) before installing anything else.
In short, how should I proceed ? Do I have to remove anything ? Can I do anything ?
Again, sorry if things had been told already. I really want to take my shot, but I don't wanna soft brick my device again by being too carefree one more time.
Thank you for your time and your help.
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
ken2802 said:
When super su is installed magisk will make it automatically systemless. But it can't guarantee that it can always hide it. If super su isn't installed /you are unrooted then magisk will install and use magisk su.
Click to expand...
Click to collapse
Thank you for your answer. Can I uninstall SuperSU to install Magisk su instead then ? Do I need to remove Xposed module and my root apps too ?
ken2802 said:
Also since you mentioned them: soft bricks can be resolved by just reflashing your Rom, no need to wipe (lose your data) in most cases
Gesendet von meinem SM-G925F mit Tapatalk
Click to expand...
Click to collapse
Yeah, I do know that, but I really do need my phone at the moment, so I'd kinda be in a world of pain if I brick it.
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
ken2802 said:
You can Uninstall super su if you want but it isn't a must if you don't care magisk su. I would remove xposed before installing magisk and after having installed magisk you can install the systemless version. As for your apps that use root, you don't need do deinstall them
Click to expand...
Click to collapse
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Zarou said:
Sorry for the late reply.
I do want to use Magisksu instead of SuperSU. So basically, what I have to do is :
1 - Uninstall Xposed by flashing the uninstaller from TWRP
2 - Uninstall SuperSu (by the app menu ? Is it enough to remove root ?
3 - Install Magisk from the store
4 - Install systemless Xposed from the store
And I'll be all set, correct ? Nothing should go wrong ?
Click to expand...
Click to collapse
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Zarou said:
Thank you for this clarification. Can you also tell me how can I restore the stock boot image only ? Or Do I have no choice but to re-flash the whole ROM in order to do so ?
Click to expand...
Click to collapse
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
ken2802 said:
Just flash the boot image from an near stock custom Rom. You can flash it through a recovery menu
Click to expand...
Click to collapse
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
You can try but if magisk complain while instalation you need to flash a fresh boot image/Rom
Gesendet von meinem SM-G925F mit Tapatalk
Zarou said:
Well, all I can find with Huawei Firmware Finder seems to be full or OTA ROM updates. I can't download the boot image only.
However, within the SuperSU app settings, there are two options : one to change superuser app and a second one to completely remove root. By any chance, does one of these options clear the boot image by itself ?
Click to expand...
Click to collapse
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Didgeridoohan said:
It can be a bit of a bother getting the boot image from inside a Huawei factory image...
SuperSU can restore your boot image when you do the full unroot. That was actually what I was referring to with my 2.5.
Click to expand...
Click to collapse
Thank you, I managed to get by the whole thing with no issue. Problem solved !
Didgeridoohan said:
I'll add a couple of points to your list:
2.5 - Make sure to restore the stock boot image.
3.5 - Flash magisk.zip in recovery. You can't install through the Manager if not rooted.
If you want to use Magisk Hide to pass SafetyNet you'll have to disable Xposed. Magisk can't hide it, even if it's systemless.
Click to expand...
Click to collapse
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
tutabeier said:
Hi all,
Yesterday I've unlocked my Oneplus 3T bootloader and installed TWRP.
After that I flashed Lineage 14.1, Open Gapps, addonsu-14.1-arm64-signed.zip and finally Magisk. Reboot and install SuperSu.
But I'm wondering if I still need to flash the Lineage addonsu and SuperSu.
Click to expand...
Click to collapse
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Didgeridoohan said:
What are you doing mixing all those root solutions? Pick one... If you want Magisk, you do not need the other two.
Click to expand...
Click to collapse
Thanks. I probably missed something when reading the threads. I understood Magisk can root my devices, but didn't understood that simply installing it would root my device. So that's why I was flashing su binary and using SuperSU app.
Thanks a lot.
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
xdaVTU said:
First of all I'm sorry for answering this post so late but I needed to do it.
Well, according to all I've seen about magisk, and obviously with this post, everything I must do to use magisk is:
1. Unlock Bootloader
2. Flash Official Stock ROM
3. Flash Magisk.zip
4. Install Magisk Manager
Is it all? Really? Shouldn't I do anything else, because I'm too worried about it. I've ever used SuperSU until now, and this things of MagiskSU, Magisk Manager and Magisk Hide option are really new for me.
If someone could answer me, including the owner of this post it'd be VERY APPRECIATED and I would thank you all a lot!
Thanks haha
Click to expand...
Click to collapse
It's not quite apparent from your post if you have rooted with SuperSU already and now want to use Magisk instead. But, considering that you're posting in a thread that deals with moving from SuperSU I'm gonna go with that... Kind of...
You will need an unlocked bootloader, yes.
If you've rooted with SuperSU you can reflash your ROM, or use something like @osm0sis unSU zip and then flash the stock boot image only. Depends on your setup which option is easier. If you're not already rooted, this step is unnecessary.
Installing Magisk is just as easy as that, yes.
The Manager is also installed when flashing the Magisk zip, so this step is unnecessary. However... In rare cases the Manager doesn't install with the zip. If that happens you just have to install it manually.
The only step I'd like to add is to have a backup of all important data and files on your device. That's always good practice when tinkering with your device...
The release thread and the installation/troubleshooting thread (I'm hoping to have time to update it for Magisk v15.2 tonight) are good resources when setting everything up and if you encounter issues. Searching through the general support thread is also a good idea if issues arise. Most questions have been answered numerous times already.
I'm new to Magisk but have a couple of questions. I have a pixel XL running Dirty UNICORNS rooted with SuperSU. If I want to use Magisk can I just flash my dirty UNICORNS rom, gapps and then the magisk.zip?
Sent from my Pixel XL using Tapatalk
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
jc1266 said:
Hi ..I am using Nexus 6 stock rom , super su, and with all kind root apps Xposed modules .
My questions is do I need to uninstall all the root apps first before flashing the UN su zip ?? Pls help sir
Click to expand...
Click to collapse
No. You merely need to uninstall SuperSU, either through the SuperSU app (complete uninstall) or by using the unSU zip. You'll also have to make sure that you restore the stock unpatched boot image.
After that you can flash Magisk and you'll be good to go.
Hi
I have a rooted Huawei Mate 10 Pro with TWRP 3.2.1.0
January Patch. (I have an update but did not install it)
so I installed the latest Xposed Installer 3.1.5 and grant it Root too.
when I go to the Install Via Recovery it does download the v90 beta 3 and reboot to TWRP. and it says that it install the framework. but after that I get bootloop.
I managed to uninstall Xposed framework using the latest Uninstaller (by using the adb sideload) and the phone goes back to booting normally.
is there a fix for this? am I doing something wrong here? it's my first time rooting and installing Xposed. sorry that I had to post this here, I've been searching for two days now without any luck :crying:
Amajed said:
Hi, I have a rooted Huawei Mate 10 Pro with TWRP 3.2.1.0, January Patch. (I have an update but did not install it). so I installed the latest Xposed Installer 3.1.5 and grant it Root too...
Click to expand...
Click to collapse
I don't have this device but, you may find the following threads to be helpful for what you are looking to do and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=3743298
https://forum.xda-developers.com/showthread.php?t=3709535
https://forum.xda-developers.com/showthread.php?t=3736062
https://forum.xda-developers.com/showthread.php?t=3716814
https://forum.xda-developers.com/showthread.php?t=3753956
https://forum.xda-developers.com/showthread.php?t=3761827
PLEASE NOTE: Some of the above threads may not have XPosed in the Threads Title but, it does have some chat regarding XPosed.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Did you find a way to get exposed to work?
After updating to the latest security patch (PRA-LX1 8.0.0.374(C432patch01)), I can't seem to root my phone anymore. Flashing supersu or magisk with TWRP causes my phone to not start up anymore. Are there any alternatives to magisk or supersu, or are there any particular (older) versions who are still able to root my phone?
Share your experience!
Thanks in advance
Hello. I rooted PRA-LX1 8.0.0.374(C432patch01). Following the next guide.
https://www.xda-developers.com/huawei-update-broke-magisk-fix/
MindCr said:
Hello. I rooted PRA-LX1 8.0.0.374(C432patch01). Following the next guide.
https://www.xda-developers.com/huawei-update-broke-magisk-fix/
Click to expand...
Click to collapse
Much thanks This resolved the issue!