yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Guides, News, & Discussion] Tecalote:
You dont buy the Unlock code. You buy credits for using DC Unlocker Software (and you can use also HCU Client - its newer Software from DC). The Phone must be connected with USB in Manufacturer mode (described in the Link I give you) - you can read with this Software the Unlock code from your Phone.

Then you can Unlock the Bootloader, rebrand finally to AL10 and update to Oreo....
[Huawei P9 Guides, News, & Discussion] DarkD3v1L:
Hello

I tried to put TWRP in openkirik, result error ... it should not be possible to use TWRP.

The thing is that I'm looking for the original recovery but I can not find it, can someone link it to me?

Thank you
[Huawei P9 Guides, News, & Discussion] Tecalote:
You can find it here in this Thread, Post #304: https://xdaforums.com/showpost.php?p=77255913&postcount=304

Unzip (extract) B528-RECOVERY_RAMDIS.zip - and use RECOVERY_RAMDIS.img

Download from here: https://mega.nz/#!PNQmiQAa!jSfGntw8072gQzkrPrDvxYJhTNRyXWz42Y6KZPNhk-c

Flash RECOVERY_RAMDIS.img in Fastboot Mode:

fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img

BTW: Use search function for related Thread - see Screenshot :)
[Huawei P9 Guides, News, & Discussion] benjamen50:
Going to try this out later, I had the bootloader unlock codes saved from when I got them from the Huawei bootloader request website, hopefully I did not delete it. Luckily I have a DC-Unlocker dongle so it shouldn't cost me to get the bootloader codes.

I'm guessing global OREO for these older huawei devices are still yet a few months away or more.
[Huawei P9 Guides, News, & Discussion] Tecalote:
Hello and welcome :)

I guess, Oreo probably don't come to markets outside of China.

Changes:

If you are successfully rebranded and updated to EVA-AL10 Oreo b528 -

don't edit manually prop and xml (configuration has been changed)

Use instead the files for replacing from this post (related to your original device) :

https://xdaforums.com/showpost.php?p=77382818&postcount=407
[Huawei P9 Guides, News, & Discussion] benjamen50:
Thanks for the heads up, I'm currently rebanded to C432 Nougat for both my P9's. Will keep that in mind.

Edit: This may be a silly question but after doing the unofficial update thing, is the enable OEM unlock greyed out and permanently enabled when the bootloader is unlocked? The reason I ask this is because I plan to sell these two phones after updating them to OREO.
[Huawei P9 Guides, News, & Discussion] Tecalote:
The original EVA-AL10 does not have FRP (OEM Lock / Unlock) in Settings or on Bootloader Screen.

The new configuration files also do not include this.

It can be included if someone wants to have it in settings, but I would not share it for everyone.

AL10 does not have it and the phone can be locked or unlocked without OEM Unlock.

If someone rebrand it back to original, the setting comes automatically back.

If you sell the p9, the buyer might want to have the device unlocked, including the unlock code
[Huawei P9 Guides, News, & Discussion] kristiansja:
I seem to have lost the mobile data connection the day after :X a bit irritated :/ No luck with rebooting
[Huawei P9 Guides, News, & Discussion] Tecalote:
Check the permissions from the files you have replaced. All of them must have 644.

If it doesn't work, it is for sure a permission problem or you copied something to the wrong place.
[Huawei P9 Guides, News, & Discussion] zgfg:
Few questions here please - regarding to L19:

1) /cust/all/cn/prop/local.prop

is the same as described in post #373

2) /hw_oem/prop/local.prop=/product/hw_oem/EVA-AL10/prop/local.prop

is the same as described in post #373, however you have removed (commented out) frp line

3) /hw_oem/xml/unstall_apk.xml=

/product/hw_oem/EVA-AL10/xml/unstall_apk.xml

I don't see any difference compared to the original xml file on my L19 rebranded to AL10 - no change here?!

Btw, why is in (2) this line, since L19 has no NFC:

ro.config.hw_nfc_on=true
[Huawei P9 Guides, News, & Discussion] superkryo:
Apologies, I didn't see your post until now. Did you manage to repair the P9P and make HWOTA7 to work on it? Looking forward to your new thread
[Huawei P9 Guides, News, & Discussion] Tecalote:
Yes, it's working.

But I am a single person and have a lot to do.

Currently I am working on Oreo Custom Rom for P9.

I have to port some features from other phones.

My next step is in the next days to update OP, because of new configuration files and optimized steps. Not only here, also on Android Hilfe de.

Then I make Thread for the Custom Rom for P9.

I think sometime in the next two /three weeks I will make the Thread for P9 Plus.

Rebranding is tested, but I have to test the Oreo Update also and to look how it goes for VIE.

I am doing all this in the limited space of time.

So stay tuned.

I do not have to do that, I just do it for fun. But I do not do anything if someone is stressing me here :silly:

.
[Huawei P9 Guides, News, & Discussion] Tecalote:
Question 1+2:

Yes, it's the same content as in Post: https://xdaforums.com/showpost.php?p=77296996&postcount=373

I just uploaded the finished file, so it just needs to be replaced. This is easier for some than editing the file itself.

Question 3: No change here - but it will have a lot of changes in the Custom Rom. But for updating to Oreo and then going to AOSP Rom, nothing must be changed here. Why I did include this file? I dont know :D

Question BTW: You can set ro.config.hw_nfc_on= to true and to false, it does not make any difference. And it is original in the Firmware, you can find it in:

\product_\hw_oem\EVA-L19\prop. Just have a look :laugh:
[Huawei P9 Guides, News, & Discussion] zgfg:
Thanks

Tnx for detailed answer/clarification

On my L19, happily running /hw_oem/prop/local.prop as sym-linked to /product/hw_oem/EVA-AL10/prop/local.prop with both NFC lines commented out (by ampersand):

#ro.config.hw_nfc_on=true

#ro.config.hw_nfc_msimce=false
[Huawei P9 Guides, News, & Discussion] superkryo:
Great news!

Of course and fully appreciated. Take your time
[Huawei P9 Guides, News, & Discussion] zgfg:
For AL10 b528, Chinese voice search

HwSpeechService app (com.iflytek.speechsuite,

at /data/hw_init/system/app

can be removed as noted in

https://xdaforums.com/p9/developmen...ta7-p9-eva-t3820849/post77238090#post77238090

Is it possible then to assign Google app (search) to the Home button long press?
[Huawei P9 Guides, News, & Discussion] zgfg:
On my L19 rebranded to AL10 c00 b528, notification now for OTA upgrade (11,28 MB)

What should I do

- to accept or not?

- to request full update or to keep as differential (11,28 MB)?

- if accepting, I have to flash stock Recovery and remove Magisk

Apparently, I will have to follow

https://xdaforums.com/showpost.php?p=77255913&postcount=304

https://xdaforums.com/showpost.php?p=77212268&postcount=176

- should I also revert all local and build prop changes (incl those redefining model from AL10 to L19) before OTA?

Did anybody else receive such OTA notification for Oreo b528?

Btw, I don't see anything newer than b528 from July on FirmwareFinder

PS: Phone is in Airplane mode for many days, but WiFi was enabled
[Huawei P9 Guides, News, & Discussion] zgfg:
Did you successfully update b528 by OTA and did you resolve issues with repeating OTA notifications
[Huawei P9 Guides, News, & Discussion] jonathanhenry81:
do not. I did not succeed just disable the update application. I will enable it to make sure of the new update
[Huawei P9 Guides, News, & Discussion] jonathanhenry81:
the same update that gave me problems to apply and chose not to apply it because it is the same installed and because everything is going well.
[Huawei P9 Guides, News, & Discussion] Tecalote:
Hi - this is already answered here: https://xdaforums.com/showpost.php?p=77263790&postcount=331

By [MENTION=7404650]urbanmec[/MENTION] :

The solution is as simple as installing the google app through playstore.

then go to : /cust/All/cn/xml/hw_defaults.xml and add the line :

<integer is_show_google="1"/>

[MENTION=4900664]dkionline[/MENTION] did see this OTA (I dont, because I have for ROM Development OTA App disabled yet) - we have not tested yet.

The changelog says: "This update fixes an issue where phone numbers in text messages could not be edited before dialing."

Changelog: http://update.hicloud.com/TDS/data/files/p3/s15/G3115/g1699/v155640/f1/full/changelog.xml

If you want to apply the update, you must not revert the changes in local.prop or elswhere....

But if you dont have the mentioned issue, why applying this update?

→ everything fixed in MRv5 - which is coming soon.
[Huawei P9 Guides, News, & Discussion] zgfg:
Tried but still, long press to Home button invokes nothing (particularly, not the Google app)

Exactly - that is the Changelog popping up.

For now I have disabled System Update through Quarantine app (no more popping up and cannot be opened from Settings - but update badge is still showing an available OTA).

Later I will try to update because I think there is a problem here:

- send or receive an SMS with a (phone) number

- open SMS and tap to the number

- my b528 Oreo does nothing

- Nougat, however, pops up a menu to choose: Call, Edit calling, etc.

Please test yourself.

Strange: My doesn't even offer to Call (by Changelog only a fix for Edit before calling is mentioned)

Looking forward :)
[Huawei P9 Guides, News, & Discussion] Tecalote:
B528 Patch - DO NOT UPDATE YET

[MENTION=7786725]zgfg[/MENTION] I did the Update with (only) following steps:

I did not uninstall Magisk Manager and did not restore props.

0) restore HwOUC (Systemupdate App)

1) boot to TWRP - flash original RAMDISK.img (choose img) to: ramdisk

2) flash with TWRP (using img) original RECOVERY_RAMDIS.img to: recovery_ramdisk

3) Reboot Recovery = Stock Recovery /only wipe Cache Partition.

4): Reboot to system and apply OTA Systemupdate (only some KB)

The Phone does not Reboot to EMUI Recovery!

Patch was installed in some second.

Now I flash patched ramdisk.img and TWRP...

EDIT: After this Update it is not possible to flash patched_ramdisk !!!!

So dont update, because after flashing patched ramdisk you will have a bootloop (stuck on "your device is booting now" screen)

It is possible, to boot to system with original ramdisk.img → but from that moment on, it is not anymore possible to flash patched_ramdisk without Bootloop.

It seems, it blocks the magisk directory.
[Huawei P9 Guides, News, & Discussion] Tecalote:
[MENTION=7786725]zgfg[/MENTION] and all:

Do not update the new patch!
[Huawei P9 Guides, News, & Discussion] zgfg:
8

Unfortunately you added RED WARNING with delay - I followed your original instructions as above (without red notice) and also ended with the bootlop as you described.

Steps 0-4 worked as described, got successfully the OTA patch 01 as on your screenshot.

Btw, I'm happy to know that from this TWRP is also possible to flash recovery and boot partitions :)

Btw, I tried then tapping to the phone number from an SMS, but it still did not work (no pop-up to choose Call, Edit before calling, etc).

Then I flashed patched boot and TWRP and bricked my phone just as you described in the lately added Red note

Good that you have the same problem - hope you will find a solution tomorrow ;(

---------- Post added at 01:31 AM ---------- Previous post was at 01:05 AM ----------

Ended with the bootloop as you also described - see my previous post.

Then I connected USB with PC, rebooted by Vol- & Pow to fastboot, flashed the non-patched Ramdisk again - it boots now to Oreo, however I have no more Magisk and root

To be continued tomorrow - if nothing else, to re-flash original b528 without the OTA patch again (by HuRUpdater)?!
[Huawei P9 Guides, News, & Discussion] Tecalote:
Thats exactely the case - system starts with original ramdisk.img + TWRP, but not with patched ramdisk.img → so no chance to root....

I will find a way tomorrow - how to get rid of this patch.

[MENTION=4900664]dkionline[/MENTION] and I tried a lot of things in the meantime.

In this patch includes in the update.app a Patch.img. Normally it is not possible to open, but I know a trick in Ubuntu and opened it. (the patch.img)

Inside is not only the mms.apk patch, but also a kernel.patch and some prop changes.

I will see tomorrow, what can be done.

It is for sure, that this patch block Magisk Root Method. I guess, it blocks the magisk directory. But another thing is, I am not sure yet, if they changed anything on the xloader. This could be dangerous too.

→ I will explain tomorrow.
[Huawei P9 Guides, News, & Discussion] Tecalote:
[MENTION=7786725]zgfg[/MENTION] Don't use HuRUpdater at the moment.

If this patch had changed something to the Xloader the phone could be hard bricked by using HuRUpdater.

The safest way I think is eRecovery. But I will test first.

Edit: Currently I download latest version and recovery with eRecovery (USB connected, Vol+ and Power Button) It is b528 without patch.

But it will reset the phone (normal User reset) - so backup before doing so is required.
[Huawei P9 Guides, News, & Discussion] zgfg:
Do you mean the following:

- to copy all three b528 ZIPs as from post #2 to DLOAD folder on SD card

- to reboot to eRecovery (Vol+ & Pow)

- it would start installation?

- (how) to force complete wipe?

I'm little afraid of the fact that I cannot root but I have a number of Huawei system apps disabled by Quarantine (incl. Huawei IME - default Chinese keyboard) - I cannot reenable them before reinstalling.
[Huawei P9 Guides, News, & Discussion] Tecalote:
[MENTION=7786725]zgfg[/MENTION] - Detailed answer is coming soon. (about 15 min) You did not understand what I meant yesterday.
[Huawei P9 Guides, News, & Discussion] Tecalote:
No, sorry, you did not understand me! I mean NOT the Stock EMUI Recovery - which you can boot with Vol+ and Pow and disconnected USB

- I mean Huawei eRecovery - which you can boot with Vol+ and Pow but WITH connected USB (Screenshot)

- You forgot it, we talked about in P9 TWRP Nougat Thread (a long time ago) and I wrote it here in this Thread:

Point 9: https://xdaforums.com/showpost.php?p=77243079&postcount=263

And here: https://xdaforums.com/showpost.php?p=77186132&postcount=74

- it is not possible to flash FullOTA-MF Firmware with dload

- HuRUpdater is able to flash FullOTA-MF Firmware (I mentioned in Post #3: https://xdaforums.com/showpost.php?p=77161314&postcount=3) Post #3 is made for downgrade to Nougat AL10, but the method is the same, if you use the b528 FW, HuRUpdater flash this Firmware.

- But I would not recommend , I recommend eRecovery for now

The solution I did:

1) Backup your data /apps

2) flashing original ramdisk.img (ramdisk_recovery is not required, you can apply eRecovery with installed TWRP)

3) Restore Phone with eRecovery to b528 (without patch): Connect the USB Cable on the one end with the charging power outlet and on the other with your P9. Press Vol+ and Power Button (while USB connected) and keep pressing until Phone reboot to eRecovery (which is basically different than EMUI Stock Recovery)

4) Soon you are in eRecovery - you choose "Download latest version and Recovery" - then you connect your P9 with WLan (enter PIN in eRecovery). Yesterday eRecovery connected automatically to WLAN. eRecovery is searching "Get info package" and will start the download (Full firmware) and after restore your Phone to AL10 b528 Oreo Firmware. But with User reset (similar than factory reset)

5) When you are back to system, dont enable WLAN and make a short setup (skip most things, but accept GOOGLE SERVICES together with Huawei Services)

6) Enable USB Debugging, disable HDB HiSuite, disable Trust Space... (and later disable also Systemupdate!) Dont apply the OTA Patch01 - BTW: Same issue in Huawei Mate 10 Forum (received also Patch01 -which disable the possibility to Root!)

7) Flash patched ramdisk.img and boot to system, boot again to bootloader and flash TWRP and boot to TWRP - Root is back again :)

8) I had a TWRP Backup with: cust, kernel, odm, oeminfo, product, ramdisk, system-image, vendor-image and version and succesfull restored - if you dont have, you must set up your phone again....

9) for the MMS/sms issue - you can try attached apk - extract Mms.zip and copy the folder Mms to: /system/priv-app - and replace the Mms folder (but not the MmsService folder!)

10) reboot phone

Tell me the result, thanks

And please other Users: test also the new mms and report me, if everything is working with (then we dont need Huawei Patch...)
[Huawei P9 Guides, News, & Discussion] Adilox9:
Hi, i just rebranded and flashed openkirin RR Tom I now I want to root my phone. I have to use ramdisk.img

Can I use the patched one provided here ?

Thx
[Huawei P9 Guides, News, & Discussion] zgfg:
Will have to wait, I'm out of the town these days, without stable WiFi to download 2,3 GB from eRecovery
[Huawei P9 Guides, News, & Discussion] Tecalote:
Yes, you can use the Oreo patched ramdisk.img from here.
[Huawei P9 Guides, News, & Discussion] Tecalote:
Okay, keep me updated
[Huawei P9 Guides, News, & Discussion] Adilox9:
ok thanks mate
[Huawei P9 Guides, News, & Discussion] Tecalote:
Your welcome.

Once you flashed patched ramdisk.img install Magisk Manager.

Then change in settings stable channel to Beta.

Go back to the main window of Magisk Manager and you will receive 16.7 Magisk zip.

- Install with Direct install method, save Log and reboot.
[Huawei P9 Guides, News, & Discussion] Adilox9:
When I downloaded magisk it said it's already installed

???

In the official thread they say copy the .IMG and click on instal, I don't have it I have uninstall :/
[Huawei P9 Guides, News, & Discussion] DarkD3v1L:
Only using the modified ramdisk is it possible to produce the "False" status in Safetynet?

I give uninstall magdisk, but I still get the same error, should I flash the original ramdisk again?

Thank you very much Tecalote
[Huawei P9 Guides, News, & Discussion] zgfg:
What do you mean by False error with SafetyNet - there was a change in API/keys, causing some apps to fail checking the SafetyNet status.

See posts 563, 565, 566 (MR v4 thread)

https://xdaforums.com/showpost.php?p=77338116&postcount=565
[Huawei P9 Guides, News, & Discussion] Tecalote:
Yes, it can be that using the patched ramdisk together with Magisk Manager is enough on AOSP Rom.

I told you, what we do on Stock..

So if everything is fine and you have Root, you must not reinstall..

And the SafetyNet Check you must do now with another App, because Google changed the API, as [MENTION=7786725]zgfg[/MENTION] mentioned.
[Huawei P9 Guides, News, & Discussion] Adilox9:
thank you my friend it all went flawlessly
[Huawei P9 Guides, News, & Discussion] Victor7w7:
After removing the root completely, if I get a future update via ota I will not have problems installing it? Are the updates in this unofficial version of Oreo functional?
[Huawei P9 Guides, News, & Discussion] Tecalote:
You know how to remove Root? If not, ask later.

You can remove and you can get the future Updates without any problems.

The Firmware is not an unofficial version of Oreo, it's the official version.

Only rebranding for to get this update is unofficial.

But there's no other way since Huawei don't release Oreo outside of China although it's running better than Nougat..

However, you can go without Root = original ramdisk.img and original recovery_ramdisk.img but the Bootloader should stay open in case for any reason to correct some settings.
[Huawei P9 Guides, News, & Discussion] meshoo00oo:
Good Day:)

I have P9 plus VIE-L29C185B395 , Can I use this tool to rebrand and update to Chinese version VIE-AL10C00B528 ?
[Huawei P9 Guides, News, & Discussion] Tecalote:
No, you would brick your phone - this Tool is only for EVA and not for VIE - but:

→ Sometime within the next two to three weeks, I will open a thread for P9 Plus, with its own rebrand tool specifically for VIE
[Huawei P9 Guides, News, & Discussion] RandomQuezoPH:
Remove . .
[Huawei P9 Guides, News, & Discussion] Tecalote:
I need ramdisk.img and kernel.img from system with patch01

[MENTION=7786725]zgfg[/MENTION] Can you please make a backup for me from ramdisk.img and kernel.img and give me the Link for Download, before you restore b528 - you are currently on the Patch01 Firmware?

If I get the two files from you, I would patch the ramdisk.img with Magisk 16.7 and flag "force encryption".

Then you could test, please, if you can boot with it. If booting into the system does not work, you only need to restore the current ramdisk.

1) make TWRP Backup from current ramdisk and kernel

2) store image on external_sd (must be mounted before)

dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
dd if=/dev/block/bootdevice/by-name/kernel of=/external_sd/kernel.img

Then we would know with certainty whether the patch is made to prevent root, or if Magisk only does not work because ramdisk / kernel was changed - and patching the changed ramdisk is necessary. Thanks :good:

I reported the issue to topjohnwu: https://xdaforums.com/showpost.php?p=77418253&postcount=6557
[Huawei P9 Guides, News, & Discussion] RandomQuezoPH:
Updated MagiskHide Props Config to v2.3.6-v28 and whenever I check SafetyNet Status, it says "This response in Invalid" I don't know if updating Props caused the problem. Any fix? Thank you :D
[Huawei P9 Guides, News, & Discussion] Tecalote:
This is not an issue - just Google changed the API and current Magisk Manager can't check.

It doesn't mean, you aren't pass by safetynet check

Look here:

https://xdaforums.com/showpost.php?p=77419040&postcount=454

2) In the meantime it's no more required to use the module for change /emulate another fingerprint.

We found a way that safetynet passes with original Fingerprint (will be included in MRv5 and updated in OP, soon I have time to reorganize the Guide with actual information)

Have a nice day :)
[Huawei P9 Guides, News, & Discussion] Victor7w7:
previously you already told me how to remove the root, and flash the original RAMDISK.IMG, but now I see that you say that I have to flash the original RECOVERY_RAMDISK.IMG, so that I can give it completely as a stock?

and if I already realized that closing the bootloader the signal is lost, I had to reopen it and everything went back to normal.

and could you tell me the command line to flash the RECOVERY_RAMDIST.IMG by fastboot, thank you very much in advance.
[Huawei P9 Guides, News, & Discussion] meshoo00oo:
Thank you ?
[Huawei P9 Guides, News, & Discussion] zgemb0:
VIE-L29 ->AL10 ->oreo

[MENTION=6870018]Tecalote[/MENTION]: dude, thanks. Impatient as I am, I bit the bullet and updated my P9 Plus to oreo. Worked a treat.

At one point though I thought I had bricked it, turns out the bootloader had locked itself :D

I wouldn't want to share too much info on conversion and upgrade (as that might cause mass bricking), let's just say it rather straight-forward and done, for the most part, by following your OP (including tweaks to get the cell reception going and enable NFC).

Kudos, my good man.

Also, ro.treble.enabled reports true. Does this mean treble is fully supported, have you (or anyone else) experimented with treble updates on EVA/VIE?