Rebrand-Update-Tool-HWOTA7-P9-EVA

[Tecalote]

I have eva-l19c185b403 should i download the chinese noght rom directly and rebrand?

Rebrand to EVA-AL10C00B399sp17a is required before updating to EVA-AL10 Oreo. If you skip the step between, mobile network will not work on Oreo.

 

[csmarino90]

@csmarino90
HuRUpdater is working pretty good on Oreo - you need just Oreo b528 FullOTA-MF (instead of Nougat Firmware) and TWRP installed - in the advanced tab of Wipe you have the option to format data - format data with TWRP, (format - not wipe) reboot TWRP and flash HuRUpdater (described in Post #3)
HuRUpdater must be together with the 3 Firmware zip files in "Update" folder (two of the zip files renamed)
HuRUpdater flashes automatically the Full Firmware.
After this step reboot Recovery and do Factoryreset in Stock Recovery (Stock Recovery is automatically flashed with HuRUpdater, because it's in the update.zip)

With this method you don't need to flash system.img or any other imgs.
Just do it with TWRP and HuRUpdater - if eRecovery want work

I did it and worked perfect. Thanks!

But after HuRUpdater I want to check the eRecovery and still fails. I'm wondering that it may be related with my SD card. Sounds crazy but the factory reset with SD card fails and without it pass. I'm still researching...

Now I'm in LineageOS and with SD inserted the factory reset fails. I read somewhere that another person have the same "problem".

Only to report: Magisk, root and TWRP (without data decryption) works good along AOSP based ROMs. I could install GApps too!

Enviado desde mi EVA-AL10 mediante Tapatalk

 

[Giovanni9921]

I'm really determined to do the process to update my European p9 to oreo ... But I have some doubts?

1) After updating, in the system info -> model number remains EVA-AL10 instead of EVA-L09?
2) When I receive an update, I have to have the recovery stock installed, but once the update is finished and the phone is restarted I have to enable root permissions every time?
3) If I do the whole procedure correctly, everything works? (being an update file that comes from huawei and not a custom rom)

 

[zgfg]

I'm really determined to do the process to update my European p9 to oreo ... But I have some doubts?

1) After updating, in the system info -> model number remains EVA-AL10 instead of EVA-L09?
2) When I receive an update, I have to have the recovery stock installed, but once the update is finished and the phone is restarted I have to enable root permissions every time?
3) If I do the whole procedure correctly, everything works? (being an update file that comes from huawei and not a custom rom)

1) Yes, although if you follow later posts (search for Yellow Pages) you will find directions how to redefine model to Lx9 in the props files
2,3) Uncheck automated System Updates because if you accept OTA Patch 01, you will no more be able to root (you will have to go back to b528 without Patch if you want root) - read the posts from last week - this is current status with Patch 01 and nobody knows what the future OTAs may bring.
All else works fine and battery consumption seems to be better than with Nougat

 

[and-roid007]

i have installed latest version of magisk manager.
unfortunately I have lost root and there is no direct install option on magisk manager .
I have uninstalled the magisk and reinstalled old one but no luck bringing back root and magisk.I also flashed patched ramdisk again but no success again.

what should I do now?

 

[Tecalote]

i have installed latest version of magisk manager.
unfortunately I have lost root and there is no direct install option on magisk manager .
I have uninstalled the magisk and reinstalled old one but no luck bringing back root and magisk.I also flashed patched ramdisk again but no success again.

what should I do now?

I can upload patched ramdisk.img for Magisk v17.
Or you can do it for yourself.
You need the Stock ramdisk.img (from update.app b528)
Place it on internal storage in the folder: MagiskManager.
Open Magisk Manager and click: install
Choose: boot.img patch
Navigate to the Stock ramdisk.img in MagiskManager folder and Magisk patches the ramdisk.img with v17. No need to restart now.
You have then in the same folder: patched_boot.img (=the new patched ramdisk.img)
Flash it with Fastboot Mode.

 

[Fil76]

Hi, I have a p9 plus c432 with b387 with bootloader locked (but one year I used DC unlocker for Debrand and saved keys)

I would like to install open Kirin cause I read somewhere that if I Debrand to al10c00 my IMEI would not be recognised anymore

So if I understand correctly

1) unlock bootloader
2) Debrand to al10c00
3) install Oreo update
4) install open kirin ?

Correct ?

 

[Tecalote]

Hi, I have a p9 plus c432 with b387 with bootloader locked (but one year I used DC unlocker for Debrand and saved keys)

I would like to install open Kirin cause I read somewhere that if I Debrand to al10c00 my IMEI would not be recognised anymore

So if I understand correctly

1) unlock bootloader
2) Debrand to al10c00
3) install Oreo update
4) install open kirin ?

Correct ?

Between 3 and 4 are steps required to get mobile network and NFC and other things to work.
Note: This Thread isn't for P9 Plus (VIE) - it's only for EVA.
The Thread for P9 Plus wil come during the next weeks - with own HWOTA7 which is special for VIE together with a Guide how to do it correctly.

Also this Thread for EVA will get a complete updated Guide during next week.
To simplify everything.
Be patient.

 

[Fil76]

Great ! Thank you

 

[and-roid007]

I can upload patched ramdisk.img for Magisk v17.
Or you can do it for yourself.
You need the Stock ramdisk.img (from update.app b528)
Place it on internal storage in the folder: MagiskManager.
Open Magisk Manager and click: install
Choose: boot.img patch
Navigate to the Stock ramdisk.img in MagiskManager folder and Magisk patches the ramdisk.img with v17. No need to restart now.
You have then in the same folder: patched_boot.img (=the new patched ramdisk.img)
Flash it with Fastboot Mode.

thank you very much my dear friend .i'll do it myself.


it works.thanks again.

 

[csmarino90]

Did you replace TWRP by EMUI Recovery and did you also flash back System partitipn before eRecoverying

Alternatively, post #3 describes HuRUpdate method

Yes, I did both of them but eRecovery didn't work

 

[Engsalam22]

Can i have stock recovery after update to the chinese oreo so i can recive ota updates and i dnt need root

 

[Tecalote]

Can i have stock recovery after update to the chinese oreo so i can recive ota updates and i dnt need root

Everything is possible.
But at first you need root to do the required changes.
At the moment you rebranded your phone to AL10 and updated to Oreo - you will have a lot of Chinese stuff - what you don't need.
And you have no mobile network - that's why steps (described in OP) are required to make your phone properly working.
This steps can not be done without Root.
After that you can remove Root and receive OTAs.

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.

 

[Tecalote]

Yes, I did both of them but eRecovery didn't work

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.

 

[Tecalote]

Update Magisk 16/16.7 → Magisk 17.1

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

 

[Engsalam22]

Its better to wait for thread update?
Will u make the process easier? What will be updated

 

[and-roid007]

- Install latest Magisk Manager v5.9.1 : https://github.com/topjohnwu/Magisk/releases/download/manager-v5.9.1/MagiskManager-v5.9.1.apk
- Dont use Magisk direct install over 16 or 16.7
- Reboot phone to Fastboot mode
- Flash b528-Magisk-17.1-force-encrypt-patched_ramdisk.img : https://mega.nz/#!nNZXSAoQ!r-yXfzs_Wx5dCtbiudkXad0WSMHM13ClGPbWuwzgM2U
- Reboot phone, open Magisk Manager and you are done.
-

I have patched ramdisk through magisk itself.do I need to flash your patched ramdisk file?

 

[Tecalote]

I have patched ramdisk through magisk itself.do I need to flash your patched ramdisk file?

No, if everything works you don't need

 

[Tecalote]

Its better to wait for thread update?
Will u make the process easier? What will be updated

Much more easier

 

[Engsalam22]

Much more easier

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