Huawei P9 [ROM][Android 7.0][EMUI 5.0.1][European Firmware b398]*MagicRainbow* v4

Pfiou

Member
Oct 14, 2017
9
2
0
Angers
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
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.
For those who plan to install Magisk 17.1, be aware that the gps seems to have gone nuts. Many satellites losses and precision is now about 100m ! (usually 30m). TopJohnWu is working on a 17.2 version which is supposed to correct those bugs. This being said, Magisk is really a great mod.
 
  • Like
Reactions: Tecalote

Tecalote

Senior Member
Aug 6, 2015
4,077
3,104
253
Leipzig
This sounds great! I look forward to it. Please let me know once you update the thread so that I can try it right away.
Hello @tonyaross
The updated version for rebranding to EVA-AL10 and update to Oreo is ready: https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2

Note: You must go back first to Stock Firmware. For this you can also use the HWOTA7 Tool and you need the FullOTA-MF Firmware for your original device first. You have L19c185 - here are the Download-Links for b399 → Note for other Users, the Firmware Links are only for EVA-L19C185 and you can not use them, if you have original another model!:

In Post #1 is described, how you must rename the last two Firmware zip files.

The Download Link for HWOTA7 Tool is also in Post #1: https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
1) Make Backup of the (for you important) folders from internal storage and Huawei Backup from (User)Apps/data (do not Backup System-Settings/Apps) - because the phone will be wiped several times
2) Download Firmware b399 + HWOTA7 Tool + the two Firmwares, which you need for Rebranding to AL-10 and update to Oreo
3) Copy first the 3 Firmware b399 zip files to the C:\HWOTA7\update folder (two zip files renamed) and start update_eng.bat.
4) Connect your phone with PC in Fastboot Mode (USB cable stays connected during all steps) - TWRP will be flashed - boot with Vol+ and Power Button to TWRP and allow system modification - hit "enter" in HWOTA7 Terminal - Use Upgrade options: 2.Using the script - 1.Change firmware (Same brand update )
5) Firmware b399 will be flashed. After reboot to System, you should receive an OTA for L19c185. If not you can download FullOTA-MF here, and do it with HWOTA7 Tool (I checked the Firmwares, and I would recommend b402 - because b405 is listed for L09 and b403 has: MLA-L11C185B349 in changelog)
b402:

6) After your Phone is updated to b402 you can do the Rebranding....
Wish you success - have a nice weekend :)
 
Last edited:

ninoying

New member
Jan 9, 2015
2
0
0
Missing fingerprint after Magisk v17.1

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.
 

Tecalote

Senior Member
Aug 6, 2015
4,077
3,104
253
Leipzig
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.
Make a list of the installed modules (you must reinstall after)
0) Enable ADB Debugging and USB Debugging in Developer Options.
1) Open Magisk Manager and use uninstall Button
Magisk will going to be uninstalled and reboot automatically the phone.
2) If the phone is stuck on Bootscreen or have a Bootloop (I don't think so) - press Vol- and Power Button while USB connected with Phone and PC, to enter Fastboot Mode. If phone boot normal go to 4)
3) flash original boot.img (you find it in the extracted ROM zip)
4) Boot to TWRP, flash Magisk 17.1, reboot phone.
5) Open Magisk Manager and go to menu Download, search for Busybox for Android NDK and install it, reboot phone.
6) In the extracted ROM zip you find the SELinux Permissive Script module, install it with Magisk Manager menu "Module" and use + Button. (Permissive Script must be on internal storage in the Download folder)
Tell me the result
 
  • Like
Reactions: Twisted Prime

Tecalote

Senior Member
Aug 6, 2015
4,077
3,104
253
Leipzig
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.
 

Victor7w7

Member
Aug 5, 2018
20
1
0
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.

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
 

zgfg

Senior Member
Oct 10, 2016
4,419
1,899
233
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
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

Code:
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
For each PAUSE you press Enter

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
 
Last edited:

Victor7w7

Member
Aug 5, 2018
20
1
0
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

Code:
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
For each PAUSE you press Enter

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
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.
 

zgfg

Senior Member
Oct 10, 2016
4,419
1,899
233
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.
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 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
 
Last edited:
  • Like
Reactions: Victor7w7

Victor7w7

Member
Aug 5, 2018
20
1
0
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 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
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
 

Tecalote

Senior Member
Aug 6, 2015
4,077
3,104
253
Leipzig
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
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"
 

Attachments

Last edited:
  • Like
Reactions: Victor7w7

zgfg

Senior Member
Oct 10, 2016
4,419
1,899
233
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 you :)
But don't update Magisk itself to 17.x

You can also correctly validate SafetyNet with the two apps from an earlier post in this thread
https://forum.xda-developers.com/showpost.php?p=77339761&postcount=566
 
Last edited:
  • Like
Reactions: Victor7w7

Victor7w7

Member
Aug 5, 2018
20
1
0
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"
update only the apk and now I give it to the safetynet and I get false in both.
 

Victor7w7

Member
Aug 5, 2018
20
1
0
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.

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
 
Last edited:

Tecalote

Senior Member
Aug 6, 2015
4,077
3,104
253
Leipzig
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
Have you also done the "Safetynet-Workaround in Magisk-Edition" from Post #1 OP?

There's a module, but it doesn't help if the basic integrity is not true.
This can occur if you have deleted apps from system or modified system.
For example, if you have installed Xposed Framework (it's not possible to pass safetynet with Xposed)

Try out first the workaround from OP
 
  • Like
Reactions: Victor7w7