First off, my apologies if wrong sub-forum or what-not, I'm new here.
Secondly, and my reasoning for this post - I was rooted with SuperSU, then read more into Magisk and realised Magisk was probably the better option. However, I was having SafetyNet Check issues and failing all tests so I decided to revert to EMUI 4.1 again (EVA-L09 C432B166) but still failing SafetyNet Checks. I'm wondering if flashing a previous ROM hasn't de-rooted my system or left some residue from the Magisk root. Any help appreciated greatly, thanks.
try to flash this : https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 , then update to latest, b390 if im corect, i got L19 and for me latest is b386.
unlock bootloader, instal this twrp (this is for nuget, dont instal this twrp on marshmalow) : https://forum.xda-developers.com/p9/development/twrp-t3565703 (important, after instaling twrp restart into twrp recovery, not os first time, duno way, but there are a lot who say need to do that)
reboot in system, reboot in recovery, backup boot in recovery (use sd card for backup storage, better than internal, why? if sometime you broke safetynet, you can restore it in twrp when restore boot (there is safety net info))
flash magisk v14 (dont use beta v14,3 or etc, there are safetynet bug, and not work it) here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
for busybox use https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=lv first, then you can https://play.google.com/store/apps/details?id=stericson.busybox&hl=lv if prefer this.
!doing all thease things you will delete all files in internal storage, backup all needet files!
There no other fix for safety net right now, this is best i found for myself
Arnys said:
try to flash this : https://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818 , then update to latest, b390 if im corect, i got L19 and for me latest is b386.
unlock bootloader, instal this twrp (this is for nuget, dont instal this twrp on marshmalow) : https://forum.xda-developers.com/p9/development/twrp-t3565703 (important, after instaling twrp restart into twrp recovery, not os first time, duno way, but there are a lot who say need to do that)
reboot in system, reboot in recovery, backup boot in recovery (use sd card for backup storage, better than internal, why? if sometime you broke safetynet, you can restore it in twrp when restore boot (there is safety net info))
flash magisk v14 (dont use beta v14,3 or etc, there are safetynet bug, and not work it) here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
for busybox use https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer&hl=lv first, then you can https://play.google.com/store/apps/details?id=stericson.busybox&hl=lv if prefer this.
!doing all thease things you will delete all files in internal storage, backup all needet files!
There no other fix for safety net right now, this is best i found for myself
Click to expand...
Click to collapse
Thank you, this worked for me (except I used 14.3 of Magisk, currently SafetyNet Checks are passing so until they fail, I'll stick with it). Many thanks!
Related
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?
Hi guys I'm a beginner so sorry if i did so many stupid mistakes.
I succesfully rooted my Xiaomi Mi A1 with Magisk about 3 months ago and tried to ignore OTA updates until today
I tried to follow a guide in github which i can't link because i'm new in this foru.
Since i rooted with Magisk i followed the first method
I "restored images" then tried to update but still doesn't work
Then i decided to reboot and then tried to update but it doesn't work
So then i tried to uninstall Magisk by dragging it from the home Just like any other app but didn't work
Then proceded to delete all Magisk folders from my downloads but the update still doesn't work
Then desperately tried to reinstall Magisk but it isn't the v16 version so i tried to install it(i don't know which file i need to select so i tried selcting any image files) says it worked but it didn't so i rebooted and tried over and now i'm stuck with incomplete rooting, non-working Magisk and no OTA update.
I'd like to update OTA and bring back Magisk and root.
Ibra2800 said:
Hi guys I'm a beginner so sorry if i did so many stupid mistakes.
I succesfully rooted my Xiaomi Mi A1 with Magisk about 3 months ago and tried to ignore OTA updates until today
I tried to follow a guide in github which i can't link because i'm new in this foru.
Since i rooted with Magisk i followed the first method
I "restored images" then tried to update but still doesn't work
Then i decided to reboot and then tried to update but it doesn't work
So then i tried to uninstall Magisk by dragging it from the home Just like any other app but didn't work
Then proceded to delete all Magisk folders from my downloads but the update still doesn't work
Then desperately tried to reinstall Magisk but it isn't the v16 version so i tried to install it(i don't know which file i need to select so i tried selcting any image files) says it worked but it didn't so i rebooted and tried over and now i'm stuck with incomplete rooting, non-working Magisk and no OTA update.
I'd like to update OTA and bring back Magisk and root.
Click to expand...
Click to collapse
Why you didn just flash Magisk uninstaller. Zip file?
Poslato sa VTR-L29 uz pomoć Tapatoka
urbanboymne said:
Why you didn just flash Magisk uninstaller. Zip file?
Poslato sa VTR-L29 uz pomoć Tapatoka
Click to expand...
Click to collapse
Sorry, i thought that i could still keep Magisk and root intact if i didn't use the uninstaller.
Ibra2800 said:
Sorry, i thought that i could still keep Magisk and root intact if i didn't use the uninstaller.
Click to expand...
Click to collapse
No you cant. You are lucky you didnt brick your phone. Flash uninstaller and than try OTA update. Download TWRP for your phone/new rom and flash working Magisk again and root phone. Is simple. Of course, if you are on TWTP you will be unable to OTA update your phone. You need stock recovery or wait for ZIP flash file of newes rom
Poslato sa VTR-L29 uz pomoć Tapatoka
@Ibra2800 There's no need to uninstall Magisk to update with an OTA. There are however a few prerequisites that need to be fulfilled:
You need to have the stock boot image installed. That can be done by using the restore images option in the Manager or manually flashing the boot.img file with fastboot or equivalent.
You need to have the stock recovery installed. This means the OTA will fail if you have TWRP or another custom recovery installed. Either keep the stock recovery installed and only boot the TWRP image when necessary (the fastboot boot command), or you make sure you restore the stock recovery image when you need to update.
You also need to have a few important partitions on your device untouched. Those include (but may not be limited to) /system and /vendor. If you've so much as mounted these as rw, the OTA will fail. This one can be tricky, because if an app has root access it can easily do this without you noticing.
If you manage to fulfill the above, you should be able to update your device. If the A/B method from @topjohnwu's OTA tips didn't work, use the general case instructions instead.
Right now, it sounds like you need to start from scratch though...
If you can get a hold of a full firmware file for your device, you might be better of flashing that instead. Or, wait for a flashable update, as stated above. And if you want to reinstall Magisk you might have to first uninstall it, to start clean. Use this uninstaller.
Thanks for trying to help me
Sorry to ask but i just can't wrap my head around it, how am i supposed to use the uninstaller, what are the steps ? Also i only user Magisk so i think i don't have any custom recovery and don't know what's TWRP purpose.
Ibra2800 said:
Sorry to ask but i just can't wrap my head around it, how am i supposed to use the uninstaller, what are the steps ? Also i only user Magisk so i think i don't have any custom recovery and don't know what's TWRP purpose.
Click to expand...
Click to collapse
The uninstaller is a zip that you flash in a custom recovery (i.e. TWRP) to uninstall Magisk completely. You should also be able to use the "Complete uninstall" option in the Magisk Manager.
TWRP is a custom recovery that you can use to make backups of your device partitions (so you don't loose any data if anything goes wrong, it's highly recommended to make regular backups in some way) and install custom ROMs and other modifications to your device. You can either install it permanently or just boot it whenever you need it (there are likely gonna be guides about this in your device's forum).
Since you seem to be quite new at this, I would suggest that you take some time to browse through your device's forum and familarise yourself with things like ADB, fastboot, custom recoveries, custom kernels, ROMs, etc. And if you have more questions like this, it's often best to ask them in the device forum, since there sometimes are device specific things that need to be done for everything to work right.
I'm a bit in panic. I've follow all steps from The rebrand guide in the oreo section that is linked to a guide for Mate9.
But i cannot understand this steps:
G. Do "Downgrade Nougat" steps to the rebrand firmware, it fails and reboot but fine.
H. When going to system press "Vol-Up" to enter eRecovery, do "Low-level format data partition".
I do everything on my P10 but I don't have the "low lever format
Click to expand...
Click to collapse
I'm stucked, I have done all steps but in my case The Phone didnt fail, it boot as usual with cust correctly changed to c432 but i dont have italian language.
Now i dont know what to do cause i cant low Level format (i dont see this option).
Can I update with an official firmware from firmware finder? how?
Why i cant install twrp in recovery but only on ram_disk?
thank you for your help
RealPsygnosis said:
I'm a bit in panic. I've follow all steps from The rebrand guide in the oreo section that is linked to a guide for Mate9.
But i cannot understand this steps:
I'm stucked, I have done all steps but in my case The Phone didnt fail, it boot as usual with cust correctly changed to c432 but i dont have italian language.
Now i dont know what to do cause i cant low Level format (i dont see this option).
Can I update with an official firmware from firmware finder? how?
Why i cant install twrp in recovery but only on ram_disk?
thank you for your help
Click to expand...
Click to collapse
A low level format is called factory reset in emui recovery.
After completing the debranding you should receive OTA updates. If not you can use the Huawei Firmware finder app, or if your bootloader is unlocked you can manually update with TWRP (https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286).
In Oreo, the recovery partition is called 'ramdisk', so that is where you have to flash TWRP.
M1chiel said:
A low level format is called factory reset in emui recovery.
After completing the debranding you should receive OTA updates. If not you can use the Huawei Firmware finder app, or if your bootloader is unlocked you can manually update with TWRP (https://forum.xda-developers.com/p10/how-to/guide-manual-updgrade-to-update-oreo-t3758286).
In Oreo, the recovery partition is called 'ramdisk', so that is where you have to flash TWRP.
Click to expand...
Click to collapse
Ok So I do a factory reset and repeat the operation....
what trwp should I install?
EDIT:
I've installed the TWRP in this thread and followed that guide ( @Jannomag ).
Now I have the 8.0.0.384 (C432) that works, with no brand and italian. but I've noticed through file manager that in the internal memory there is all the old file. how can I do and Hard Reset? (Before flashing the update I've done a simple factory reset through TWRP, do I need to format system, cache, and data partition?)
thank you
RealPsygnosis said:
Ok So I do a factory reset and repeat the operation....
what trwp should I install?
EDIT:
I've installed the TWRP in this thread and followed that guide ( @Jannomag ).
Now I have the 8.0.0.384 (C432) that works, with no brand and italian. but I've noticed through file manager that in the internal memory there is all the old file. how can I do and Hard Reset? (Before flashing the update I've done a simple factory reset through TWRP, do I need to format system, cache, and data partition?)
thank you
Click to expand...
Click to collapse
As far as I know TWRP cannot complete a factory reset on kirin devices. So you must first flash EMUI recovery and factory reset from there.
@M1chiel is correct, you need to do a factory reset with Huawei eRecovery. Connect your phone to a PC via USB and boot as you want to boot into TWRP. Or flash stock recovery.
thanks @Jannomag and @M1chiel
now with the bl unlocket I found out that I cannot install some apps like netflix, I've read that relock bootloader with fastbook oem relock code is a bad idea.
Is there something I could do?
lock bl with some trick? (hwota maybe? but i've read that I have to install it through twrp so I don't think the bl will be locked)
root with magisk and use some module? (but I hope this don't give me problems with payments apps)
RealPsygnosis said:
thanks @Jannomag and @M1chiel
now with the bl unlocket I found out that I cannot install some apps like netflix, I've read that relock bootloader with fastbook oem relock code is a bad idea.
Is there something I could do?
lock bl with some trick? (hwota maybe? but i've read that I have to install it through twrp so I don't think the bl will be locked)
root with magisk and use some module? (but I hope this don't give me problems with payments apps)
Click to expand...
Click to collapse
If you are on stock firmware (without root, custom kernel, twrp etc) you can relock your bootloader in fastboot. If not your phone will not boot.
However now you finally unlocked I would not recommend that. For Netflix there may be two options that work: install it from APKmirror instead of the Playstore or install Magisk as you indicated yourself. I'd suggest the latter, since it allows root and the opportunity to install relevant modules (I use debloater and youtube vanced). In addition you can hide root from e.g. Netflix, pay apps and games.
Edit: Magisk also ensures you pass Google's safetynet, which is tripped by unlocking the bootloader.
Even if you don't need to root your phone, do it with Magisk. It's systemless and and you can hide the root for most apps (some banking apps still won't work). I use it, too and have no problems with Netflix, Mario Run and my banking app including app for secure login and transactions.
you two @Jannomag @M1chiel are the best thank you,
What magisk image should I install? and what module to hide bl unlocked and root?
RealPsygnosis said:
you two @[email protected] are the best thank you,
What magisk image should I install? and what module to hide bl unlocked and root?
Click to expand...
Click to collapse
Magisk 18 works fine. You can flash it with TWRP or patch the boot image (called ramdisk in oreo) and flash it in fastboot. No modules are needed to pass safetynet. These threads are useful: https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3035 and https://forum.xda-developers.com/ho...oot-honor-view-10-mate-10-pro-t3749280/page50 (but use the normal channel, not the custom channel).
Make backup of the boot image via TWRP before you install Magisk. The uninstaller works great but I bricked my P10 a year ago without doing something wrong.
Also wait at the first boot, it takes a few minutes (like 5-7 sometimes). Don't cancel it.
M1chiel said:
Magisk 18 works fine. You can flash it with TWRP or patch the boot image (called ramdisk in oreo) and flash it in fastboot. No modules are needed to pass safetynet. These threads are useful: https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page3035 and https://forum.xda-developers.com/ho...oot-honor-view-10-mate-10-pro-t3749280/page50 (but use the normal channel, not the custom channel).
Click to expand...
Click to collapse
Is it normal that for some reason after a few days that I've flashed twrp, it is replaced without my will with e-recovery?!
'cause I found out that I cannot boot to twrp and I had to flash it again through fastboot.
BTW I've installed Magisk and SafetyNet is ok, but I think that BL unlock isn't hidden because I have the same problems with incompatible device for some apps
No it is not normal that twrp disappears. You haven't run an update?
Installing apps from the Playstore may work again if you clear data in settings > apps and notifications > apps > playstore and restart the Playstore.
Hi all,
Finally debricked my phone!!!
Okay, I need Magisk and want to keep my phone updated.
I followed some guides to temporary deinstall Magisk with backup of original file but I can't get trough the update process as described, installation always fails.
I tried multiple recovery flash attempts but it just doesn't work as soon some modifications are done. I did not even use TWRP flashed.
Is unlocked / booting TWRP / flashing Magisk enough to let the updates fail (yes I deinstalled Magisk before update)?
What's the current state, am I following old tutorials?
Thanks
Hello forum, I have been trying to root my motorola G6..
After much struggle, getting stuck in a boot loop and other issues I finally have restored stock roms and now have build PPS29-118-15-11 installed. So at least the phone works again My bootloader is unlocked.
But I still want to root it.
I think I understand the procedure well enough, but I am unsure of the correct/best versions I need for the ROMS/boot, Magisk, and TWRP.
ROMS/boot:
I found a youtube with instructions for updating Android v9
But I haven't tried it as this recommends a boot img:
OPS27.104-15-10_no-verity_boot.img
OPS27.104-15-10_no-verity_boot.img | by dejello for Moto G6
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
I am reluctant to use the above as it looks to be a downgrade from my current version 29-118-15-11.
Also, I thought that the filename prefix "O" indicated oreo instead of "P" for pie? So would this be a version 8 file?
TWRP:
Similarly, I am not sure if I am using the right, or best TWRP version. I currently have twrp-v3.2.3-ali.img
I flash this (with fastboot) and it works but shortly after I encounter the "no command" error (when booting to recovery) and I have to redo it. I am NOT overwriting it with a stock recovery.img.
I have also run into the "encryption password" problem, where I am unable to provide one to decrypt the data partition. So I can't backup the data with twrp (something I really would like to do).
Magisk
I have Magisk-23-0.zip
But I saw a post from brunogroa that recommends installing Magisk 19 and updating it to 23 later. Is this something that is required or can I just install v23?
So, I am looking for the correct versions for ROM, Magisk and TWRP to use, given that I have installed PPS29-118-15-11
Any assistance will be greatly appreciated.
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
pdpantages said:
Well I finally have it I think. I noticed a comment in
[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide. by djello
"(you may not need a modified boot image for Magisk)"
When using PIE instead of OREO.
Being an optimist, I gave it a try and it worked... I installed Magisk and was able to verify root access using the Root Checker Basic App. Kept stock boot img.
This is probably not too amazing for the old hands but us newbies need a break every now and them
So in the end, all I had to do was:
(0) Unlock bootloader
(1) Install stock PPS29-118-15-11
Done earlier with another version of twrp.
Install TWRP 3.5.2
(2) fastboot flash recovery twrp-3.5.2_9-0-ali.img
(3) Use twrp to install Magisk
adb push Magisk-v23-0.zip /tmp
Boot phone into recovery and use twrp to install Magisk
(4) Boot the phone into System and verify Magisk is there and use Root Checker App to confirm I am now rooted.
Issues:
I noticed that a security update for
PPS29-118-15-11-5 failed to apply.
The phone boots into recovery mode and asks for the decrypt password. I don't know the password to decrypt data and how to proceed from here.
I suspect that if I flash the stock recovery img the security update might work. If anyone knows please comment ; I will research this also and maybe just try it.
Click to expand...
Click to collapse
I am stuck in a similar position.
SOLVED IT!!! Followed all of the steps that you posted except I installed Magisk with the patch method because I couldn't get the zip file to push onto the device. Kept getting a read only error, maybe because it wasn't rooted?
Anyway, I am rooted now!!!