yashsingh1/xdaforums huggingface dataset:
[Huawei P9 Guides, News, & Discussion] zgfg:
By using JamesDSP Magisk module, see instructions:

https://xdaforums.com/showpost.php?p=79181207&postcount=1682

with ViPER-DDC enabled and DDC file set to IdealEQ.vdc, there is also a notable gain in volume (both for Speakerphone and Headset, didn't test for Bluetooth)

PS: Although JamesDSP is not as good as Viper4Android was (V4A does not work on this Chinese Oreo), it is still useful - and this is the last link that was really missing to me compared to the ever excellent [MENTION=6870018]Tecalote[/MENTION]'s MagicRainbow v4 ROM (it had also KangV Settings goody)
[Huawei P9 Guides, News, & Discussion] alexrainmk:
Does not work, is there any way to enable Permissive mode? Thank.
[Huawei P9 Guides, News, & Discussion] zgfg:
Ki

As of March 27, there is a new BusyBox update, but again under the v1.30.1 version number

JasonDSP also updated to v2.0

PS:

Updated also Magisk Manager to v7.1.0

(Waiting for official Magisk update to v19.x:

https://xdaforums.com/showpost.php?p=79216305&postcount=50)
[Huawei P9 Guides, News, & Discussion] jonathanhenry81:
because I can not prevent the System from showing notice of high consumption of James DSP .. even occasionally closes the application.
[Huawei P9 Guides, News, & Discussion] zgfg:
Yes, it's annoying that JDSP cannot be 'normally' closed. But when you don't need anymore, you can go to Settings / Apps /JDSP and do Force Close

For the Launch permissions, I don't give it Manage Automatically but Manually, and only to Run in the Background.

Hence, when need to play music, I manually start JDSP, and kill it afterwards.

Btw, despite the notification of battery consumption, JDSP consumes only few percents of battery, if not killed overnight
[Huawei P9 Guides, News, & Discussion] jonathanhenry81:
#zgfg

Hi friend. You could help me with kernel auditor, the best configuration to save battery. If you have time to help me, thank you very much.
[Huawei P9 Guides, News, & Discussion] zgfg:
I have experimented only with Governors, to find that blue_active (big and little clusters) is good compromise - keeping fluid GUI and somewhat saving the battery

Convolvers in JDSP don't reproduce smooth with blue_active on big cluster (blue_active can be on little) - better don't enable Convolvers, then ok

Btw, to enable On Boot changes (e.g. to force the chosen Governors), Kernel Adiutor must be enabled for Manage Manually: Auto Launch (or Manage Automatically) under Settings / Battery / Launch
[Huawei P9 Guides, News, & Discussion] xxxvego:
Hello, today, including Google Maps and Yanosik apps, my phone did not catch GPS signal. Sometimes he will catch for a short moment. What can I do to fix it?

A few days ago I just updated Magisk to version 19.1.
[Huawei P9 Guides, News, & Discussion] zgfg:
Did GPS work before you installed Yanosik and with stable Magisk v18.1 (v19.x is still beta)?
[Huawei P9 Guides, News, & Discussion] andrzej.brudnick:
Hello.

I have a question about battery life after change from L09 to AL10 emui 8.0.

How is yours sot?

In battery settings you have automatic closing and opening apps or you do it manually on each app?

Because I installed this Rom yesterday morning and first day I had sot about 2h. Today it's the same. I have new battery and on c432b504 had 3,5h+. I read that this rom is the best in battery care. What should I do to improve this score?

Thank you.

Wysłane z mojego EVA-AL10 przy użyciu Tapatalka

Sorry, its called launch. I didnt use English language :)
[Huawei P9 Guides, News, & Discussion] zgfg:
Generally, automatic launch management should not affect SOT but battery consumption in idle mode, with the locked screen and particularly overnight

Nevertheless, it's better to set most of the apps to Manual management and to give only to some permissions to Run in background (like to the browser if you think you will sometimes leave browser to download in the background)

And to leave Automatic management (or Manual with all three enabled: Start on boot, Secondary start and Run in background) only to Social Media and Messaging apps, Magisk Manager and similar apps you need them to always and immediately react on the notifications and requests

Sorry, I have other issues with the bad/weak battery and cannot share you good statistics (anyway, having more than 2 hrs of SOT)

Of course, disable what you don't need permanently, like Bluetooth, NFC (general rules, applicable also to Nougat)

You can additionally save battery if you install ECO kernel and switch to blue_active governors
[Huawei P9 Guides, News, & Discussion] xdacalvien:
Hi all,

I can't install Xposed SDK 26 ( Android 8.0 ) from Magisk.

Have try two times, will bootloop, after that need reband back only become normal.

---------- Post added at 11:48 AM ---------- Previous post was at 11:06 AM ----------
[Huawei P9 Guides, News, & Discussion] zgfg:
In browser, you have Search box on the top-right of the page.

Search for Xposed and you will find previous discussions here

See e.g., given Xposed ZIP installation worked through TWRP (tested with b539 and NW patch v1.2, probably should work the same with b540 and NW patch v2.6):

https://xdaforums.com/showpost.php?p=78503465&postcount=1259

https://xdaforums.com/showpost.php?p=78715699&postcount=1349
[Huawei P9 Guides, News, & Discussion] xdacalvien:
Really thanks...

I did type xpose in search but not xposed, nowonder nothing found in result ....

--------------------

I am using B540, flash with TWRP with mount SD Card. After few minutes into Android, couldn't found Xposed App.....
[Huawei P9 Guides, News, & Discussion] zgfg:
XposedInstaller.apk to manage Xposed modules must be installed manually (always the case when installing XPosed via TWRP), see:

https://xdaforums.com/showthread.php?t=3034811
[Huawei P9 Guides, News, & Discussion] xdacalvien:
Thanks, lastly I success to install.
[Huawei P9 Guides, News, & Discussion] Wize.:
hello may someone help me? i followed the steps to update from b535 to b540 and it worked fine but I lost root access, twrp and obviously the network patch. i also can't do "adb reboot bootloader" for some reason, it says "device offline". I can go into fastboot and it says that the phone is unlocked, which, if I remember correctly (because it's been long time since I last messed up with my phone) means that bootloader is unlocked right? I fear something because I don't remember well: If I flash TWRP will my phone do a factory reset? If so, I remember there was a way to avoid it, right?
[Huawei P9 Guides, News, & Discussion] zgfg:
You must enable Development menu and inside ADB/USB debugging.

Flashing TWRP does not trigger Factory reset.

Please read OP instructions, all should be there
[Huawei P9 Guides, News, & Discussion] Wize.:
thanks for replying, that was already checked but I unchecked and rechecked them and now adb works, but fastboot doesn't. it says "waiting for any device" is there any fix for this? i searched the thread and it seems nobody else has my problem, and it is not in OP instructions either

edit: usb port seemed to be the problem, i just switched it and it worked
[Huawei P9 Guides, News, & Discussion] zgfg:
Magisk Module: ADB & Fastboot (use over USB OTG)

Screenshot from Terminal Emulator:

ADB and Fastboot over OTG cable from P9, running Magisk module ADB and Fastboot NDK, towards another phone :)

Hence, you can run ADB and Fastboot, without PC

---

Small differences between this library on Android and Minimal ADB & Fastboot on Windows

On Windows, you get ADB help for:

adb
adb -h
adb --help

On Android, only for:

adb
adb --help

On Android, for

adb -h

you get

adb: unknown command -h

On Windows, you get Fastboot help for:

fastboot
fastboot -h
fastboot --help

On Android, only for:

fastboot -h
fastboot --help

I.e., you can test on Android just

adb

You will get help and you will know that ADB lib was correctly installed

But if you test on Android just

fastboot

You will get:

fastboot usage: no command

Don't think that Fastboot lib was not even installed

So don't rely on Step 5 'test' from:

https://www.DROIDVIEW.com/use-your-android-device-as-pc-for-fastboot-and-adb

Append an S at the end of DROIDVIEW - it doesn't allow me to post with that S appended!?
[Huawei P9 Guides, News, & Discussion] Tecalote:
I tried with xda Forums app:

https://www.**********.com/use-your-android-device-as-pc-for-fastboot-and-adb/amp/

It doesn't work to post this link

Now with Chrome:

http://www.**********.com/use-your-android-device-as-pc-for-fastboot-and-adb/amp/
[Huawei P9 Guides, News, & Discussion] zgfg:
I don't know why XDA does not allow the word

d_r_o_i_d_v_i_e_w_s

Either as word or as part of the url?!
[Huawei P9 Guides, News, & Discussion] daveh077:
Is Magisk 19 officially out yet or is it still a beta?
[Huawei P9 Guides, News, & Discussion] zgfg:
Still Beta, you can install by putting Beta channel in Settings.

Using for two+ weeks, working fine.

Direct update or by flashing patched Ramdisk from my Mega:

https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ
[Huawei P9 Guides, News, & Discussion] mmiyahki:
How can i enable VoLTE with 540 any one knows?
[Huawei P9 Guides, News, & Discussion] zgfg:
If you searched for VoLTE (up-right Search box), you will see:

https://xdaforums.com/showpost.php?p=79170401&postcount=1665

It is also mentioned in the OP post #2, VoLTE unfortunately still does not work
[Huawei P9 Guides, News, & Discussion] ozeanblau:
Thanks Tecalote for all the great info, I followed your guide and I'm now on a working L09 Rebranded.

I chose not to flash the face unlock and I had to follow these steps to get Playstore working.

- Flash EMUI Recovery (instead of TWRP) -

- fastboot flash recovery_ramdisk EVA-b540-EMUI-RECOVERY_RAMDIS.img

- Go to settings /system /restore /data Factoryreset with Wipe of internal storage.

- After Factoryreset you must not flash Network Patch or Faceunlock again

- Use apk from here:...

I'm now wondering if I'd like to flash the face unlock to use.

Can I flash TWRP again and then flash the Face unlock?

Would face unlock be available if I just flash OmniROM Pie Alpha 5.2 from OpenKirin, or do I need to do the patch first?
[Huawei P9 Guides, News, & Discussion] zgfg:
You can always flash between TWRP and stock Recovery.

And yes, you can still flash Face Unlock.

But this Face Unlock add-on is for stock EMUI, not for Open Kirin ROMs.

Per Omni Changleogs, it should come with Face Unlock, but you must ask the ROM users

https://openkirin.net/download/
[Huawei P9 Guides, News, & Discussion] Tecalote:
Magisk 19.1:

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page6
[Huawei P9 Guides, News, & Discussion] ogisha:
Hi [MENTION=6870018]Tecalote[/MENTION],

I am on stock and I updated to the latest 19.1 Magisk.

After reboot I am asked for password to decrypt the storage!? I have never seen screen like this.

I entered my pin code and I have god the answer that password is correct but the data on my phone is corrupt, so I have to do the factory reset to resume using my phone.

What should I do?

Please help me.

Thank you very much.

Edit: I can enter twrp.
[Huawei P9 Guides, News, & Discussion] zgfg:
Hmm, this is strange, I have updated to Magisk v19.1 with no problems - patched Ramdisk available from my Mega:

https://mega.nz/#F!JwkVyRya!Rb7OUE0z3PEpXBRxGOM-vQ

Btw, I've seen similar reports about password suddenly being asked for SD card, but also by people using stock Eu cust c432, with no root, etc:

https://xdaforums.com/p9/help/sd-card-password-start-restart-t3591115

PS: Yours is about the password for Internal Memory, not for SD card...
[Huawei P9 Guides, News, & Discussion] ogisha:
Thank you for your answer.

Meanwhile, I did factory reset and all system updates and now I am working on getting back my phone's previous condition, but I am afraid to root the phone with Magisk now. :(

I am not sure whether the problem will rise up again. I saw that somebody reported similar problem on some other non Huawei device. I am not sure shoukd I try with latest Magisk, previous version or wait for some update to the latest one. :confused:
[Huawei P9 Guides, News, & Discussion] zgfg:
When you were upgrading to Magisk v19.1, did you have both Forced Encryption and Force AVB checked in (first must be always checked in and the second if you had OTA patch02)?

I.e., I don't know if for some reasons now v19.x needs AVB checked in even if you don't have b540 OTA Patch02.

(I have Patch02), I've been using Magisk v19.0 beta for couple of weeks and now using v19.1, always with both Encryption and AVB checked in, and TG, did not have any problem.
[Huawei P9 Guides, News, & Discussion] Tecalote:
Hi [MENTION=4657522]ogisha[/MENTION] nice to hear from you :)

I missed you in the Huawei Forum. The last information I had was that you bought another phone, which is not from Huawei.

Is your problem with Magisk on a Xiaomi phone, or for which phone you are talking about?

So far I know it's recommended to set the flag in Magisk for "force encryption" (for phones with encrypted data) and "AVB2.0 dm-verity" (for to work with the newest Security Patches) on all phones with Stock Firmware now and in the future.

(must be set before flashing Magisk to flash Magisk with this options)

Same for EMUI. This will prevent for such problems you have.

On all newer EMUI versions (original Firmware) it is required. Phone wouldn't boot without this two options enabled.

Additional, on EMUI 9 the recovery_ramdisk must be patched manually (instead of ramdisk, because it doesn't exist anymore)

It might be different on Non Huawei phones.

How to flash Magisk right for your phone is dependent on the configuration of your phone.

If flashing Magisk with TWRP, you must set the flags with TWRP Terminal before flashing Magisk.

If TWRP doesn't support session decryption of encrypted data, you must use additional "cache" with Terminal for flashing Magisk instead of using data (which cannot be mounted)

The alternative method is patching the ramdisk.img (on Non Huawei Phones it might be the boot.img) with Magisk Manager, but also for this method it is recommended to set the two flags before patching and flashing the patched_boot.img.

For help I need exactly information which phone you have.
[Huawei P9 Guides, News, & Discussion] ogisha:
I miss you too my fellow Tecalote. :) (and zgfg, of course)

I did not change my phone. You had the wrong information. :silly:

I am on the same Huawei P9 L09C432. I just did not have time to participate in discussions. I was busy with some other things.

When it happened I was on B395. Everything you said upper was turned on. I regularly updated Magisk with every new version without problems, untill 19.1. Then happened everything I described before.

Now I am on B504. I did not unlock bootloader, nor installed twrp, nor installed Magisk. I am afraid whether Magisk would do the same harm to my phone. I am waiting to get some feedback from community that this bug is corrected or it will not happen again.

While I am waiting and working on my courage, cold you please give me some advices about installing Magisk? As far as I remember, it shold be just flashed regularly from twrp. I think there is no need for any special settings, or I am wrong?

Also could you please recommend me some modules for fooling PlayStore and for other useful things on P9? ;)

Thank you very much.
[Huawei P9 Guides, News, & Discussion] zgfg:
Sorry for interrupting the conversation.

You will need to unlock Bootloader to install NW patch - or it survived your Factory Reset and the firmware reinstallation?

You can flash by TWRP or from Fastboot the patched Ramdisk from my Mega - there is also Magisk Manager v7.1.2 apk there.

Magisk will be installed with both Encryption and AVB

EDIT: Misunderstanding, you are on Nougat c432 b504

NW patch I mentioned is for Oreo AL10
[Huawei P9 Guides, News, & Discussion] ogisha:
I reinstalled b504.

What the NW patch is?

Thank you. I will try it.
[Huawei P9 Guides, News, & Discussion] zgfg:
Latest Network patch v2.6 from [MENTION=6870018]Tecalote[/MENTION] - without, Mobile Network cannot work

EDIT: Misunderstanding, you are on Nougat c432 b504.

NW patch I mentioned is for Oreo AL10 b540
[Huawei P9 Guides, News, & Discussion] Tecalote:
I was sure you said in another Thread that you would sell your phone because Huawei didn't make official Oreo...

Fine to see you again. But I guess you are on Android 7 with b504, right?

You didn't rebrand to AL10 and update to Oreo - in this case you can NOT do what [MENTION=7786725]zgfg[/MENTION] mentioned one post before mine, because he was thinking, you are already on Oreo.

On Android 7 you have TWRP by olddroid which has encryption/decryption support for the internal storage.

Flashing Magisk on a clean Firmware should not be a problem - but I would recommend for any case to use both Flags I mentioned before.

You can use Point 6 and 7 from this Guide:

https://xdaforums.com/showpost.php?p=77161300&postcount=4

So copy Magisk to external storage, boot to TWRP, go to "Advanced" and open Terminal and write the two commands from Point 6 exactly in Termial and then confirm it and flash Magisk 19.1.

If you miss after Reboot Magisk Manager, just install Magisk Manager apk.
[Huawei P9 Guides, News, & Discussion] zgfg:
Oops, sorry, you were writing in this thread Oreo AL100 thread, I assumed you are on AL10 Oreo....

I have mistaken your Nougat b504 with Oreo b540

But of course, for Nougat you MUST NOT use patched Ramdisk from Oreo and you MUST NOT flash any Network patch
[Huawei P9 Guides, News, & Discussion] ogisha:
You are right.

Thank you very much.

What module should I use to fool playstore that my phone is certified?

Are you sure that Magisk 19.1 would work?

I saw many people in Magisk thread with P9 mini complain about same problem. Most of them flashed Magisk 18.1 after factory reset.

---------- Post added at 07:24 PM ---------- Previous post was at 07:19 PM ----------

Thank you very much for your help.

I was in panic yesterday, after everything what happened, so I entered first Tecalote's P9 thread, I saw, to ask for help.

Regards.
[Huawei P9 Guides, News, & Discussion] zgfg:
Btw, I'm now experimenting to update from Magisk v18.1 to v19.1 on Magic Rainbow v4 (my second P9), which is based on Nougat c432 b398

I tried without AVB and then with AVB - both time when rebooted it asked me for Memory password, my phone PIN failed and it told me I must Factory reset

BUT I didn't Factory Reset, instead I longed pressed Power button, then rebooted to TWRP (TWRP happily accessed Internal mem and SD card) and from TWRP I flashed my old Boot image that was patched with Magisk v18.1 - and everything worked fine again, not asking for Memory password, reading both Internal mem and SD card

I.e., there are might be problems with updating to Magisk v19.1 on Nougat (NO PROBLEM on Oreo), but it's not necessary to do Factory reset when it asks so
[Huawei P9 Guides, News, & Discussion] ogisha:
Reboot to twrp also worked for me, but I did not have any old boot image. :(
[Huawei P9 Guides, News, & Discussion] zgfg:
(For future) You can extract stock Boot (Nougat) or Ramdisk (Oreo) images by Huawei Update Extractor from update.app (unzipped update.zip, downloaded by Firmware Finder)

You can also disk-dumo your working (patched with Magisk) boot/ramdisk image, instructions in post

https://xdaforums.com/showpost.php?p=78774472&postcount=1382

(On Nugat, replace all occurances of "ramdisk" with "boot" in the dd commands)

But now, why don't you jump to the Oreo band wagon - no problem with Magisk v19.1 on Oreo

Edit:

Per the second ticket reported, it seems that fresh installation of Magisk v19.1 might work for Huawei Nougat firmwares:

https://github.com/topjohnwu/Magisk/issues/1390

https://github.com/topjohnwu/Magisk/issues/1409
[Huawei P9 Guides, News, & Discussion] deltaf007:
I had done the whole procedure a month ago and installed everything even magisk and everything working. Then everything stopped and I had to do the recovery from e-recovery huawey that the 537 firmware mounted on me. Now the problem is that the 540 can't mount with hwota7 because this software only works with nougat! I don't even find the firmware 540 that can be installed from twrp or the flashable version with huawei. I also tried restoring from hisuite to a nougat version, but eventually it crashes. How can I solve it?

#DONE#

I managed to install nougat via hisuite, now I'm following the guide. Thanks anyway.
[Huawei P9 Guides, News, & Discussion] zgfg:
Do you have P9 (EVA) or P9 Plus (VIE)?

b537 is latest Oreo for P9 Plus (and there is no b540 for P9 Plus), while b540 is latest for P9 (and there is no b537 for P9)

That is, if you got b537 by eRecovery, then you must have P9 Plus, and for P9 Plus your b537 is the latest available

There is another XDA thread for HWOTA7/Oreo AL10 for P9 Plus VIE:, you can also find there that b537 is the latest for Plus:

https://xdaforums.com/p9-plus/development/rebrand-update-tool-hwota7-p9-plus-vie-t3843930
[Huawei P9 Guides, News, & Discussion] ogisha:
Hi [MENTION=7786725]zgfg[/MENTION]!

I have flashed twrp and Magisk 19.1. After reboot the same problem with locked system partition appeared, but this time I rebooted to twrp and flashed Magisk 18.1 over 19.1 and it worked! Now I am getting back my phone to previous condition. I will stay on 19.1 until the proper patch is released.

Thank you and [MENTION=6870018]Tecalote[/MENTION] for your help!
[Huawei P9 Guides, News, & Discussion] zgfg:
Can you please clarify two things:

- Are you staying now on Magisk v19.1 or v18.1 (please double check what you wrote)

- You flashed fresh installation of v19.1, by forcing Encryption (and AVB?) in TWRP and still, it asked for password and failed to decrypt storage?

Edit-1:

- I tried also a clean installation of Magisk v19.1 to P9 Nougat (MR v4) and it fails to me as well, asking for storage password and failing to decrypt

- Thanks to [MENTION=9185201]AndrzejDwo[/MENTION], installed Magisk Manager Canary app from

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

and then tried (upgrading from v18.1 on P9 Nougat) Magisk v19.2 Canary, Encryption and Encryption+AVB, again the same (pass for storage, failing to decrypt)

Edit-2:

Installed Magisk Manager 7.1.2-209 Canary on Oreo AL10c00, selected Canary channel, and successfully updated to Magisk v19.2 Canary
[Huawei P9 Guides, News, & Discussion] xxxvego:
For all who want to use contactless payments.

You need Magisk, GPay, I have Magisk 19.1 and Magisk Manager 7.1.2.

In Magisk Manager hide GPay, Google Play Services and Google Services Framework.

I have a Revolut card added to GPay. Currently there is a promotion, using my link, the person registering for the first time will receive a free physical card. Link for those interested: https://revolut.com/r/adam1pyi.

If the phone's root message pops up (steps that work for me):

1. Force stop GPay, clear cache and data GPay

2. Rename /data/data/com.google.android.gms to /data/data/com.google.android.gms.bak in File Manager

3. Reboot phone and configure contactless payments.

Google Pay 2.86

Google Play Store 14.3.20

Google Play Services 16.0.91
[Huawei P9 Guides, News, & Discussion] ogisha:
Sorry. I just have realised that I made typing mistake.

I am staying on Magisk v18.1.

Yes it is. I did it all and I was asked for password and failed to decrypt storage so I rebooted into twrp and flashed v18.1.

Thank you.
[Huawei P9 Guides, News, & Discussion] Hermanos01:
Can anyone help me? because my p9 stock on marshmallow when i go settings, system update, no nougat update?
[Huawei P9 Guides, News, & Discussion] zgfg:
You didn't write most important thing, what is exactly your model, cust and build number (precise full build name from Settings/About, like EVA-L09c900b182 or so), but read this about rebranding and updating from Marshmallow:

https://xdaforums.com/showpost.php?p=72153575&postcount=2
[Huawei P9 Guides, News, & Discussion] Hermanos01:
Thank you! You solved my problem. :o