Insert the old SIM, delete all Fingerprints, shutdown the phone. Insert the new SIM and create new Fingerprint.I have same problem; How can i solve it?
Insert the old SIM, delete all Fingerprints, shutdown the phone. Insert the new SIM and create new Fingerprint.I have same problem; How can i solve it?
I'm not going to rebrand and upgrade my P9 these days coz I permanently need it but thank you for the link. I'll wait for the announcement before doing anything.I have also upgraded MR v4 to Magisk 17.1 and got a bootloop.
TG, I had a recent TWRP backup hence I fixed by restoring Boot and System partitions (to keep Magisk 16.1)
Btw, you can keep Magisk Manager 5.9.1 but not Magisk 17.x
If you are asking about rebranding and upgrading to Oreo AL10, you should better go back to stock by HWOTA method (post #2) and upgrade to the latest (b504 for P09, b399 for L19) and then follow
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
- but @Tecalote is announcing new custom ROM for these days
For me this trick worked:I have same problem; How can i solve it?
Turn off phone hold down power and volume Up and Down together for 10 seconds. It will start in hardware control mode presss power button and phone will restart. This should clear the fault.
Hello @tonyarossThis sounds great! I look forward to it. Please let me know once you update the thread so that I can try it right away.
Thank you so much! I'll try to do it this weekend and then report back! Much Appreciated!!:good:Hello @tonyaross
The updated version for rebranding to EVA-AL10 and update to Oreo is ready
Make a list of the installed modules (you must reinstall after)After I update magisk to v17.1, fingerprint tab in "settings" is gone and also its functionality, cannot open my device (Huawei P9 eva-L19) now using fingerprint. Any fix? Please help.
It should be possible.and if I'm in the latest firmware version with the August patch, can I install on this firmware?
It should be possible.
One User in German Forum did it and reported no problem.
To be safe:
You need TWRP anyway.
Before you flash this ROM do a Backup with TWRP of your current Firmware - Backup everything which is possible to Backup.
In the worst case you can just restore.
Tell us the result.
Must have OEM Unlocked (FRP) and UDB debugging (read the first OP posts in this thread)I will try to install it on the EVA-L09C432B504 firmware and you could do a mini tutorial to install the twrp, with the fastboot commands pls
echo on
PAUSE
cd \adb
PAUSE
adb devices
PAUSE
adb reboot-bootloader
PAUSE
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot flash recovery twrp-3.1.1-1-eva_extended.img
PAUSE
fastboot reboot
the c505 is not yet approved? and thanks now proceed to install the rom, I hope everything goes well, as for the patch I hope soon present your rom to the last patch until now or at least one more recent.Must have OEM Unlocked (FRP) and UDB debugging (read the first OP posts in this thread)
Of course, Bootloader must be unlocked
Use the TWRP from post #1
Must have ADB installed, eg Minimal ADB
Usually, ADB installs to c:\adb, copy there TWRP img file twrp-3.1.1-1-eva_extended.img and the following batch script, run the script from there
For each PAUSE you press EnterCode:echo on PAUSE cd \adb PAUSE adb devices PAUSE adb reboot-bootloader PAUSE fastboot devices PAUSE fastboot oem get-bootinfo PAUSE fastboot flash recovery twrp-3.1.1-1-eva_extended.img PAUSE fastboot reboot
Before rebooting (last Enter) you MUST:
- press and KEEP PRESSING Vol+ and Pow (eg left hand)
- press Enter and IMMEDIATELY after unplug USB (right hand)
It must boot to TWRP, then choose Reboot Sustem
If you fail to reboot to TWRP after flashing, you loose TWRP and you must flash it again
Btw, there is also new b505 today on FF.
Nevertheless, MR v4 is based on b398 and once you install MR v4, you will have the older Sec patch from Feb, because MR v4 overwrites the b39x/b50x System
You could install b505 by use of HWOTA method from post #3, but it doesn't matter because MR v4 was based on b398, hence you will loose improvements from b505 Change Logthe c505 is not yet approved? and thanks now proceed to install the rom, I hope everything goes well, as for the patch I hope soon present your rom to the last patch until now or at least one more recent.
I managed to flash the rom correctly, but the safetynet in magisk tells me "the answer is not valid" and another thing, I came by the design of ios 12 that is in the change register, where I find that option ??? in fact that's why I decided to flash the rom, one last thing you could provide me with the comment about how to update magisk I find it very difficult to find it because I do not speak English and I have to translate, thanks in advanceYou could install b505 by use of HWOTA method from post #3, but it doesn't matter because MR v4 was based on b398, hence you will loose improvements from b505 Change Log
Btw, you might have problems if you accept Magisk update to 17.0 or 17.1, look to the previous posts if you want to update from Magisk 16.x that comes with MR v4
Hi, welcome in this Thread!I managed to flash the rom correctly, but the safetynet in magisk tells me "the answer is not valid" and another thing, I came by the design of ios 12 that is in the change register, where I find that option ??? in fact that's why I decided to flash the rom, one last thing you could provide me with the comment about how to update magisk I find it very difficult to find it because I do not speak English and I have to translate, thanks in advance
Magisk Manager will offer you to upgrade to 5.9.3, newer version that will correctly validate SafetyNet check, as @Tecalote already answered youI managed to flash the rom correctly, but the safetynet in magisk tells me "the answer is not valid" and another thing, I came by the design of ios 12 that is in the change register, where I find that option ??? in fact that's why I decided to flash the rom, one last thing you could provide me with the comment about how to update magisk I find it very difficult to find it because I do not speak English and I have to translate, thanks in advance
update only the apk and now I give it to the safetynet and I get false in both.Hi, welcome in this Thread!
Thanks to @zgfg for helping you.
I would recommend to stay on the installed version of Magisk (and not to update to newest 17.1 - this can probably result in a Bootloop) , but you can update the Magisk Manager.
Download the latest Magisk Manager (only Manager apk) from this site: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Safetynet is okay, Google changed the API, that's why it couldn't be tested with the older Magisk Manager.
If it couldn't tested with the newest Manager, you can test it with attached Root Check apk
With Design App you can change Themes and there is also a Button for "customize"
Try to disable/enable ADB Debugging (first) and USB Debugging in Developer Options. Finally this options should be enabled.update only the apk and now I give it to the safetynet and I get false in both.
Try to disable/enable ADB Debugging (first) and USB Debugging in Developer Options. Finally this options should be enabled.
Delete data and Cache for Magisk Manager from Settings/Apps/Magisk Manager /storage.
Reboot phone.
Have you also done the "Safetynet-Workaround in Magisk-Edition" from Post #1 OP?I saw that there is a magisk module that corrects that error but I do not remember what it's called, I remember that it was in a tutorial on how to make the magisk functional in hwota android oreo to change the brand
and I also did what you told me and keeps coming out false