Rebrand-Update-Tool-HWOTA7-P9-EVA

[csmarino90]

In the meantime you did it with HuRUpdater, right?

Note for eRecovery:
eRecovery is working, if you do it the right way.
We have tested eRecovery in different situations, also for going back from AOSP to Stock.
For eRecovery it is not required to flash system.img and it works as well if you have TWRP installed instead of Stock Recovery.
But flashing back Stock Recovery before using eRecovery is recommended (but not required)
eRecovery is a cool option in Chinese Firmwares.

Yes, I did it with HuRUpdater. I didn't be able to make eRecovery work.

 

[Twisted Prime]

Thanks much waiting for it

---------- Post added at 02:58 PM ---------- Previous post was at 02:17 PM ----------

A question more please when i boot in fastboot mode where to put the files i want to flash on pc or device

Put the firmware in C:\HWOTA7\update

 

[dbesoli]

Wait, before you start now - because the whole Thread will get an Update during the next week.
Then it's more clear also for User's which decide to stay on Oreo without Root.

Great! I don't have any reason to have it rooted and I need to keep on GPay working. I was determined to follow your guide but I will wait the new version then. Meanwhile I've some question about the chinese stuff on the Oreo roms. Can it be removed as usual from adb shell with pm uninstall?

thanks a lot

 

[zgfg]

Great! I don't have any reason to have it rooted and I need to keep on GPay working. I was determined to follow your guide but I will wait the new version then. Meanwhile I've some question about the chinese stuff on the Oreo roms. Can it be removed as usual from adb shell with pm uninstall?

thanks a lot

During rebranding you must enable root (for changes to make Mobile connection working, and NFC - for L09), at that time you can remove bloatware
https://forum.xda-developers.com/p9...ta7-p9-eva-t3820849/post77238090#post77238090

Later you can remove root

 

[Tecalote]

During rebranding you must enable root (for changes to make Mobile connection working, and NFC - for L09), at that time you can remove bloatware
https://forum.xda-developers.com/p9...ta7-p9-eva-t3820849/post77238090#post77238090

Later you can remove root

Root is currently necessary, but not anymore in a few days.
Because I made a Base flash zip, which you can just flash and everything is fine and as it should be.
I made it for Single SIM and for Dual-SIM.
That means, soon you are on Oreo - you just flash this Rom and don't have to modify anything..
It can also be used to go straight after on AOSP Rom, or come back from it and it can also be used as daily driver with and without Root.

I mentioned, that the Thread will become a complete Update...

Regardless, there will be MRv5.

 

[heindrix]

- Dont use Magisk direct install over 16 or 16.7
- Make sure you have in Developer Options: ADB Debugging and USB Debugging enabled!
- Uninstall/or disable installed modules, reboot phone
- From Settings /Apps/Magisk Manager /storage delete data and cache of old Magisk Manager and uninstall Magisk Manager
- Reboot phone to Fastboot mode
- Flash b528 Kernel: https://mega.nz/#!KYww3CDZ!lywS0yWaGmZ1c0a2ENZKEMQlWoaOKmMDxow9J1mHiSk

fastboot flash kernel b528-kernel.img

- Flash b528-Magisk17.1-force-encrypt_ramdisk.img: https://mega.nz/#!6Q50RYxR!r-yXfzs_Wx5dCtbiudkXad0WSMHM13ClGPbWuwzgM2U

fastboot flash ramdisk b528-Magisk17.1-force-encrypt_ramdisk.img

- Reboot phone
- Install latest Magisk Manager v5.9.1 (Download Button in official Magisk Thread): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- Open Magisk Manager and reinstall or enable modules, reboot phone
- Open Magisk Manager and check safetynet
Note: There is no need to install again Magisk 17.1 with direct install over 17.1 patched ramdisk.img

→ If you use Busybox for Android NDK by osmosis, make sure, you have created in /system/ the folder "xbin" (/system/xbin) with an empty text file in this folder (ph.txt) - if not, create this folder and reboot your Phone, before you flash with Magisk Manager/Downloads the Busybox.
If you do not have xbin folder in system, Busybox uses /system/bin → this can make issues with safetynet.

Hi there,
I encountered the same case as your post : https://forum.xda-developers.com/showpost.php?p=77415750&postcount=6555
I'm sorry, although this thread is not for my device (my device is Huawei Nova 2s), but could you help me?
I've made a copy of my current (Patch01) kernel and ramdisk, could you help make it make it works to use Magisk?
Thank you very much.

 

[zgfg]

We

Hi there,
I encountered the same case as your post : https://forum.xda-developers.com/showpost.php?p=77415750&postcount=6555
I'm sorry, although this thread is not for my device (my device is Huawei Nova 2s), but could you help me?
I've made a copy of my current (Patch01) kernel and ramdisk, could you help make it make it works to use Magisk?
Thank you very much.

In case of Huawei P9 (AL10), it was not possible to install Magisk if updated to OTA Patch 01.
Three of us who accepted OTA update Patch 01, we had to use eRecovery (switch off, connect to charger, boot by Vol+ & Pow) to reinstall and reset to b528 as before Patch 01.
With Patch 01 and Magisk it was only bootloop.
To get rid of bootloop you can flash non-rooted ramdisk as before Patch 01, then it boots but without Magisk/root.

By scrolling back in this thread you will find instructions by @Tecalote (search for OTA, Patch 01 or bootloop) - I don't know but probably you have the similar problem with OTA Patch 01 on your Huawei device.

 

[dbesoli]

Root is currently necessary, but not anymore in a few days.
Because I made a Base flash zip, which you can just flash and everything is fine and as it should be.
I made it for Single SIM and for Dual-SIM.
That means, soon you are on Oreo - you just flash this Rom and don't have to modify anything..
It can also be used to go straight after on AOSP Rom, or come back from it and it can also be used as daily driver with and without Root.

I mentioned, that the Thread will become a complete Update...

Regardless, there will be MRv5.

I will wait the new version of the thread. Thanks for your great job on this

 

[Tecalote]

Hi there,
I encountered the same case as your post : https://forum.xda-developers.com/showpost.php?p=77415750&postcount=6555
I'm sorry, although this thread is not for my device (my device is Huawei Nova 2s), but could you help me?
I've made a copy of my current (Patch01) kernel and ramdisk, could you help make it make it works to use Magisk?
Thank you very much.

Hi, yes, the problem is on all Huawei Phones, which got Patch01 (on Mate 10 reported too)

All you can do is downgrade to the Firmware, which does not include this Patch (or upgrade to a reported Firmware, that does not include it)
For this you can use HuRUpdater (xda)
You need just the FullOTA-MF Firmware, which matches your device and cust.
And you need a working TWRP for your device, which can access data.
If TWRP can't access data, you must format data (not wipe data) confirming by typing "yes" and reboot TWRP - before you can flash HuRUpdater.

 

[heindrix]

Hi, yes, the problem is on all Huawei Phones, which got Patch01 (on Mate 10 reported too)

All you can do is downgrade to the Firmware, which does not include this Patch (or upgrade to a reported Firmware, that does not include it)
For this you can use HuRUpdater (xda)
You need just the FullOTA-MF Firmware, which matches your device and cust.
And you need a working TWRP for your device, which can access data.
If TWRP can't access data, you must format data (not wipe data) confirming by typing "yes" and reboot TWRP - before you can flash HuRUpdater.

Hi there,
Thanks for the tips, i've already done it before i read it, lol.
I downgraded to latest FULLOTA before the Patch01.
Looks like nothing we can do for now.
Thanks!

 

[Necrodaemon]

Root is currently necessary, but not anymore in a few days.
Because I made a Base flash zip, which you can just flash and everything is fine and as it should be.
I made it for Single SIM and for Dual-SIM.
That means, soon you are on Oreo - you just flash this Rom and don't have to modify anything..
It can also be used to go straight after on AOSP Rom, or come back from it and it can also be used as daily driver with and without Root.

I mentioned, that the Thread will become a complete Update...

Regardless, there will be MRv5.

Great, one question... This zip Is Stock Oreo with NFC and Network enable, and this zip it will have Flash ON Nougat (AL10) or Oreo?

Thanks

 

[Tecalote]

Great, one question... This zip Is Stock Oreo with NFC and Network enable, and this zip it will have Flash ON Nougat (AL10) or Oreo?

Thanks

You can not update your phone from Nougat to Oreo with this Base Rom zip.
First you must rebrand and update to Oreo. Even the steps to Oreo get an update (much more easier)
On Oreo you have first no mobile network and a lot of Chinese stuff and no Playstore and in case of L09 no NFC - but then you flash the Base Rom (which comes in two editions, one for L09 and one for L19 and a Patch zip for L29) - and you have everything you need...

Tomorrow I rewrite the whole OP - the zips are ready

 

[Tecalote]

Post for Update to OREO updated (#2)

The instructions for rebrand and update to Oreo are updated now (Post #2):
https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2

The other related posts will get also an update soon - but for now - this was the important one​

 

[Tecalote]

Push Notifications and Notifications on Lockscreen

→ some small updates and additional information are added to Post #2 right now...

New Topic: Push Notifications and Notifications on Lockscreen on Stock Firmware:

Just rebranded my L09 using HWOTA7 by @Tecalote
Battery holds better for sure but notifications on locksreen isn't showing up, Apple music getting closed even though I made Manual Autostart.

@zgfg reported following:
"There are problems with notifications (on locked screen). Running Blue Mail on both L09 Nougat (MR v4) and L19=AL10 Oreo (b528)
L09 pings me, AL10 not. Even when I unlock and open Blue Mail, it takes time. I've tried Launch combinations, no full proof solution
People also complained on XDA, P9, Oreo Experience"

→ Chinese firmware has different default settings than European firmware. For the notifications to work, two changes are required:
1) Open Settings /Battery - click on settings symbol above on the right - you will see:
"Keep WLAN on when sleeping" = While charging → Leave this as it is set by default

2) Open Settings /Wireless & networks /Mobile network - ADVANCED - you will see:
"Mobile data always on" = disabled → change this to: enabled

3) If you change a Theme → keep always Magazine Unlock. Only this enables notifications on Lockscreen
4) Open Settings /Apps & notifications /Notifications & status bar → check out the right settings for you

I hope, it helps...

 

[dbesoli]

I have a short question about NFC. Despite it's working after the rebrand and updated to Oreo my doubt is, Can I still use it with Google Pay or any other card payment method installed?
This is my main reason to not root the device. I use the phone to pay in a long list of commerces and I don't want to loose it.

So, if I decide to make the A decision to remain in a official rom and not root, etc. With the bootloader locked, will be the phone still able to be used for electronic payments?

 

[Tecalote]

I have a short question about NFC. Despite it's working after the rebrand and updated to Oreo my doubt is, Can I still use it with Google Pay or any other card payment method installed?
This is my main reason to not root the device. I use the phone to pay in a long list of commerces and I don't want to loose it.

So, if I decide to make the A decision to remain in a official rom and not root, etc. With the bootloader locked, will be the phone still able to be used for electronic payments?

You mean: With Bootloader unlocked..
Yes, unlocked Bootloader does not prevent you from using Payment Services or receiving OTA Updates.

GPay is not tested yet. So maybe you wait until we have Feedback from User's which are using GPay.

I only know, that if Magisk 17.1 is correctly installed (special method - I will post later) safetynet is complete green with Playstore certified and without additional modules needed, except Busybox module (virtually enabled to /system/xbin)

There's no guarantees that it will work on Stock without Root, since the phone is updated unofficial to official Oreo for rebranded AL10...
Perhaps it's working better with Magisk?

I will also make a Custom Rom, which have GPay included.
Based on b533. Let's see and just wait until we know more about this stuff

 

[dbesoli]

You mean: With Bootloader unlocked..
Yes, unlocked Bootloader does not prevent you from using Payment Services or receiving OTA Updates.

GPay is not tested yet. So maybe you wait until we have Feedback from User's which are using GPay.

I only know, that if Magisk 17.1 is correctly installed (special method - I will post later) safetynet is complete green with Playstore certified and without additional modules needed, except Busybox module (virtually enabled to /system/xbin)

There's no guarantees that it will work on Stock without Root, since the phone is updated unofficial to official Oreo for rebranded AL10...
Perhaps it's working better with Magisk?

I will also make a Custom Rom, which have GPay included.
Based on b533. Let's see and just wait until we know more about this stuff

thanks by the answer. Well, as the rebrand can be undone as is explained on POST 3 I will try to have some time to test it this evening and will go back to Nougat and L09 if not. And after my tests will tell here.

And if with magisk GPay is ok maybe my better choose will be the 'B' decission.

so, lets see with 'A' today and I will back with the results

 

[Tecalote]

thanks by the answer. Well, as the rebrand can be undone as is explained on POST 3 I will try to have some time to test it this evening and will go back to Nougat and L09 if not. And after my tests will tell here.

And if with magisk GPay is ok maybe my better choose will be the 'B' decission.

so, lets see with 'A' today and I will back with the results

:good:
@dbesoli
Edit/note:
One thing you should know - soon if you made the Factory reset with EMUI Recovery (after flashing A) - you will receive OTA Patch01 - this make the system like "read only" Ofc - you can install apps and everything, but you can not Root (but TWRP can be installed too).
Patch01 comes at the moment on different phones and we guess, Huawei wants to prevent root - but we are not sure yet, it is perhaps only a side effect.
I just mention, because if you face any problems to go back → it is possible to restore b528 without this Patch with eRecovery method (Download latest version and recovery). https://forum.xda-developers.com/showpost.php?p=77461032&postcount=504
After that step you can downgrade to Nougat for sure (with instructions from Post #3)

 

[Engsalam22]

In last step how to choose flashing recovery to recovery-ramdisk or ramdisk how to determine the destination of flashing

 

[zgfg]

In last step how to choose flashing recovery to recovery-ramdisk or ramdisk how to determine the destination of flashing

P9-EVA-8.0.0-TWRP-v4.img (new TWRP) and
b528-RECOVERY_RAMDIS.img (stock recovery) must be flashed to recovery_ramdisk

fastboot flash recovery_ramdisk P9-EVA-8.0.0-TWRP-v4.img

fastboot flash recovery_ramdisk b528-RECOVERY_RAMDIS.img

If you flash b528-RECOVERY_RAMDIS.img from P9-EVA-8.0.0-TWRP-v4, it will popup with asking for destination partition (you must choose to flash IMG and from SD card since TWRP for Oreo can't yet read Internal mem)