yashsingh1/xdaforums huggingface dataset:
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] jordi1910:
Hello again. First of all I'd like to wish all best for everyone in 2018 . Big thanks [MENTION=6870018]Tecalote[/MENTION] for another great ROM. So far everything is working great and there was no issue with install.

Anyway I have one question as I can't manage myself. Is there in this ROM any option to switch of special characters in SMS messages (I'm using default app). If I'm using English language only I can use all 160 characters in 1 message, however if I only add just 1 non standard character (like e.g any Polish or Irish letter it automatically reduces it to approx 70 characters. I remember that there was for 100% an option for switching this issue in older ROMS (I'm just not sure it was in stock or yours) but cant find now. Using this I was able to typing even everything with non standard characters but the program converted them for standard ones (I thing they are GSM-7-Bit alphabet instead of unicode 16-Bit-Alphabet UCS-2).
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Open sms, right below: more /settings /advanced /creation mod (dont know yet how this point is displayed in other languages, buts the last one) - set the mod to: free (if possible) :)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] jordi1910:
Thank you for quick response. I'm using English as my language so it's displayed exactly like you mentioned and I had it setup to free already. when I'm creating new message there is no visible characters counter (so I don't know how many letters left in message) . Once I'm trying to reply for received message and will use just 1 not standard character it's automatically showing me the reduced amount of free letters in message.

I enclosed screenshots with only 1 standard and non standard letter
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Try SwiftKey Keyboard - is it the same?

I have seen your Screenshot but at the moment I don't know how to change this..
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] jordi1910:
Thanks [MENTION=7786725]zgfg[/MENTION] it make sense what you wrote here and explaining how it works. I Google a bit and looks like in Huawei the "create mode" in advance menu is only the way when and how the phone will convert longer messages into multimedia messages - MMS.

The thing what I'm missing is something different.

Before P9 I owned for a long time Samsung S3 and the Rom I used had implemented an option for converting characters. It was called a "GSM alphabet" and was simply changing a non standard letters into their English equivalents. For example I could write Polish "ąęśćźń" etc but the SMS message was sent as "aesczn" so every message I composed could be 160 characters long, and that is what I was thinking about. Anyway it's nothing serious and I can obviously live with this "issue" and I have only to compose messages without polish characters or keep in mind that once I'll use them the SMS must be shorter or the phone will send few of them.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
[MENTION=7786725]zgfg[/MENTION] Wow that's very scientific and interesting - I think I am going to subscribe :o

Just a joke :) I found it really very detailed and interesting
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
[MENTION=7786725]zgfg[/MENTION] - all tested now:

o) MR v3 -> b394 working...

a) b395 -> MR v3 = working

b) b395 -> MR v3 -> b394 by HWOTA.zip = not working!

c) b395 -> MR v3 -> b395 by HWOTA.zip = working

b395 HWOTA.zip is uploaded and placed in #3
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] jaceleon:
Nice to see that you had released this, [MENTION=6870018]Tecalote[/MENTION]! Good for you to do this for us! Downloading this now to update my MRv2 in my L19! Gonna report any errors if found.

Thanks!
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Yes, please report :) - I have not tested yet from MRv2 (b386) upgrade with my modified HWOTA Tool to b394. This would be good to know

Versions for L19c185, c636 wil come soon (already - but I must upload)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
I don't like to bother you (it's almost a midnight) but it becomes more and more complicated (for you, too). When Huawei releases b396, you will need to prepare HWOTA(b396).zip, etc.

Besides, in the post #1, installation instructions, you say it "Works from: b386+ until b395".

So what would be HWOTA. zip for somebody who installed MR v3 from b386, v390, b391 or b393

Couldn't it be that the newest HWOTA.zip wins all - i.e., that HWOTA(b395).zip is good for all, no matter from which b386 - b395 they installed MR v3

Maybe it is, because it forces upgrade to b395 by use of no-check recovery?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Hello [MENTION=7786725]zgfg[/MENTION]

This are good questions..

We cannot be sure if it is not tested.

I was wondering:

On my Test Phone I used from MRv3 the b394 HWOTA to go back to Stock and it worked.

Then I made official OTA Update to Stock b395.

After I flashed MRv3 just to see if it would work over b395 and yes, it does.

Then I tried to go back to Stock with HWOTA b394 - but it doesn't work.

So I made HWOTA b395 to come back from MRv3 b394 to Stock b395 and it worked...

If you observe the Updates, which are coming on Stock by OTA and you start from Android 6 b182 you receive first b383 and after b386 (even both are FullOTA-MF-PV) and then some between until you end up with b395 (even if you use FullOTA)

That's why I don't know...

I must make in every case the HWOTA for the different cust - only L29 isn't possible at the moment, because of missing no check Recovery for that.

The script must be customized for each version and cust.

It includes the version number of the Firmware and the different no check Recovery for L09 and L19

I am interested if the update from MR v2 (b386) going directly to b392 (for L19) with HWOTA is working.. ( [MENTION=7289277]jaceleon[/MENTION] will test, cause he has L19)

That could maybe bring light into the question.

If this will work, I guess Update to higher version is possible, but maybe no downgrade.

In this case b395 for c432 L09 and b392 for L19 (it hasn't higher version yet) is enaugh and b394 for L09 would not be needed as you guess too..

Edit: From BlueWei b393 directly updated to Stock b395:

https://xdaforums.com/showpost.php?p=75146019&postcount=651
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] jaceleon:
As of the moment, I wiped my fingerprint and PIN. The MRv2 is still there. Haven't done the flash. Awaiting instructions, and downloading your HWOTA from the link. You told on your post that we need to go to stock B395 at least. I wonder if it would go in such a way...

Quick advise, [MENTION=6870018]Tecalote[/MENTION].

I might make a guide on doing an update to stock B395 via Huawei Firmware Finder and HiSuite if this experiment of mine goes to a bootloop. After all, if many are patient enough, the Huawei Firmware Finder on HiSuite can be a lifesaver for bootlooping phones.

Instructions of doing downgrade to MM then changing cust to C432L09 (or L19 in my case) can be found between my post and [MENTION=6870018]Tecalote[/MENTION]'s post in the MRv2 post. By doing the downgrade directly via the rollback package, installing MM stock, then changing your cust to L09-C432 (if you want it easy) or L19-C432 (if you really want the dual SIM feature but harder), then upgrading is the long way of doing it, but it will save those who are stuck in the "no higher firmware than 382" dilemma or balong bugs or any people who are having any problems with the HWOTA packages, but that is just my theory, and this is tedious, not to mention excruciatingly long (2 days for me).

Those others may start reading from https://xdaforums.com/p9/development/rom-huawei-p9-magic-rainbow-t3601064/page16.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
[MENTION=7289277]jaceleon[/MENTION] MRv3 can flashed directly from MRv2 - this ROM here can be flashed from b386 until b395 - its working!

I will test if theres a way from MR v2 to go quick to MR v3

with HWOTA Too

l Firmware Update between.

For this experiment I must downgrade first to MM and than I check everything. At the moment I am on my Test Phone on b395 (EVA-L09-c432), downgrade is not working with HWOTA Tool. I tell you my results soon I did all steps - and make a guide in MR v2.

One way for those who want go back MRv2 to Stock is already posted in MR v2 Post #1 4): "How to flash Firmware - or GOING BACK TO STOCK"

But its a bit difficult, cause you must flash after this method even again one times with dload method and do factoryreset and make OTAs....

So I try now, what will be easier.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Mr. [MENTION=7289277]jaceleon[/MENTION] :)

1) Be careful! - If you have debranded to L19 and you like to stay with L19 and have a properly working system you have to know, there is NOT YET a Firmware for L19c432 avialable higher than b392 !

2) I am testing at the moment, if the Firmware Update from b386 MRv2 is working with the HWOTA Tool and tell you later the result

3) If it works - you must take for L19 that one: EVA-L19-c432 (b392) HWOTA.zip - and not the b395 HWOTA.zip for L09!

4) Some additional infos in #309

5) Complete information comes in some hours
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] jaceleon:
I hereby report that the HWOTA provided by [MENTION=6870018]Tecalote[/MENTION] for L19 is working, and I used it to go to B392, then after some time I got another OTA to B395 (I wonder why B395, but oh well). After all of those updates, I did the flashing of MRv3, with all instructions from post 1 followed, and it resulted in an amazing installation!

I also did the 392 to MRv3 via HWOTA. It caused a boot loop. It seems that you really have to get to B395 in L19 just to install MRv3.

I tested the HWOTA instead of directly flashing to see if upgrading from B386 directly to the ROM is good as it is.

Kudos for a job well done! It is worth the wait!

I forgot if I did anything on TWRP before doing the HWOTA update though. Sorry about that.

Gonna report on battery usage later, as well as multitasking and greenifying apps. Not gonna touch Xposed yet, so no testing there. Bug in fingerprint when I did app locking on file manager and then opening file manager , but fixed by miraculously restarting device. (again, dunno why).

Music with Dolby Atmos is VERY good. Another +1 for me. Just weird-ed out that Dolby Atmos is working even with alarm chimes and notification chimes, but I can get used to a well-tuned Jingo Jungle with a nice bass when waking up (this is not the case in MRv2) so not complaining on this and I concluded this as a bonus.

I use plain Vanilla EMUI Launcher, so I can't report any performances on other launchers. But this EMUI launcher seems to be snappy. I like it! Did you do any special config on this one?

Music is piling my music and audiobooks on a single pile. This is a bit of a pickle... Any tips?

Video playback is okay. File opening takes a good speed than before. Though I would still suggest MXPlayer for your .mkv files, since the default video player takes a while to load the .mkv file.

The optional PMPlus is a very welcome addition for me. Another +1. And you even add Adiutor! +1 again. I hope this won't affect my other wallet apps, since after installing PMPlus, it removed Android Pay from my apps.

Expect more reports later. Again, thanks!
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
Good for you to join the club of happy MR v3 users, but could you shortly elaborate:

- what was your full build version before you installed MR v3, was it L09 or L19, c432 or c185?

- did you really flash HWOTA.zip for L19 c432 b192 or some other HWOTA.zip (for L09 c432 or for L19 c185)?

- when you received b395 by OTA, was that really L19 c432 b395 (there is no such thing on Firmware Finder), or L09 c432 b395 or L19 c185 b396 (there are only b394 and b396 for L19 c185, no b395)?

Because, as you wonder yourself, to what b395 and how/why you upgraded by OTA?!
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
theres no need to update Firmware first to b394 or b392 for installing MRv3

[MENTION=7786725]zgfg[/MENTION] - Same questions I have

[MENTION=7289277]jaceleon[/MENTION] Another question to you: After flashing MagicRainbow v3 - did you flash from #1 the data-files_patch.zip related to your (debranded to L19xxx (?) ) Phone - before first reboot?

Because if not, you would have installed L09 ROM over L19 phone branding...

Thanks for your feedback anyway - I'll talk about your questions tomorrow. :)

I did following experiment in the meantime:

My phone is eva-L09 - I started from b395 Stock Firmware (unrooted and with Stock Recovery)

flashed b300 - flashed b182 - downgrade was ready - unlocked Bootloader with lowlevel FR - did not connect WLAN (to receive no OTA)

flashed TWRP for MM (not the one for N)

made a new HWOTA.zip to upgrade directly from b182 to b386 - flashed the zip with TWRP - system rebooted with Systemoptimizing to b386

flashed TWRP for N - made Fullwipe - flashed MagicRainbow Version 2

tried to flash HWOTA.zip b395 for L09 - does not work (Software Installing failed)

tried to flash HWOTA.zip b394 for L09 over MagicRainbow V2 (b386) - and it worked - but:

got Bootloop after installing

connected USB Cable and booted with Vol- and Power into Fastboot Mode - Bootloader was closed (FRP unlocked of course)

opened Bootloder with Lowlevel Wipe and System booted to b394 Stock Firmware...

Users of MagicRainbow v2 - who prefere to go back first to Stock Firmware before installing MagicRainbow v3, can just flash FullOTA-MF-PV b386 as I described in MRv2 Thread #1 Point 4 and then use the HWOTA.zip b394 for L09 or the zip b392 for L19 - this works then without Bootloop. But Unlock Bootloader after is required, because it will be closed.

But theres no need to update Firmware first to b394 or b392 for installing MRv3 - because it can flashed over MRv2. It can flashed dirty and clean. And the result is MRv3 b394 (for L09 and L19 and L29 - with flashing the right data-files_patch.zip for the device before first Reboot.

If any User want after a while going back from MRv3 to Stock can use then HWOTA.zip in MRv3 Thread #3

I dont want to Spam the Thread with Update issues, its interesting anyway, but may we should open a new Thread - only for that :)

And BTW - Debranding is also possible with my modified HWOTA.zip - but for this I would need sources:

I would need oeminfo (Backups with TWRP) with the exactly note on which Firmware the oeminfo is stored to the Backkup. Because it can only be used, if installing immediately same Firmware (from which oeminfo is) after flashing oeminfo. And then I could add debranding into the script.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] syrkles:
Just did this after a botched RROS install and it worked to perfect. Thanks for the guide buddy
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] jaceleon:
It seems that I didn't became clear with my experiments.

1. Experiment 1: Did HWOTA on MRv2. Successful to B392. Then directly installed MRv3. Results in Bootloop.

2. Experiment 2: Flashed L19C432B386 via dload. Used HFF+HiSuite to force the upgrade (I think I have used L09 as a mistake), causing a crossflash between L09 and L19 and a balong bug (This made up for a very weird buildinfo.sh, I wish I had saved it.). Updated to latest stock firmware according to system update. Installed MRv3. Successful with some bugs like fingerprint.

3. Experiment 3: Unrooted. Downgraded to MM using transition package to remove balong bug and the crossflash effect. Updated on latest stock firmware (EVA-L19C432B392). Installed MRv3. Successful.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
[MENTION=7289277]jaceleon[/MENTION] Good if everything fine now.

But the easier way would have been just Unroot and Wipe MRv2 and then flashing directly MRv3 (it's working)

There's no need to update Firmware first for MRv3.

But btw I always update Firmware first and then flash Rom which is based on it..

You didn't answer my question:

Did you flash data-files_patch for L19 after flashing MRv3 before first Reboot?

Just want to know. Thx
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] jaceleon:
I did it after the installation. then when it asked for a reboot in twrp, I directed it to reboot to recovery then I flashed the patch.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] diabolo24:
Just installed Magisk 15.3 and everything works
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Did you use Direct install or flashing with TWRP?

I am asking cause haven't time to test before tonight :)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] SkywalkerZ:
excuse me if this has already been answered, believe me i tried to search for it.

Anyway so i followed the instructions like the OP said to install, during my installation i get an error saying cant mount userdata (/data block), which is causing the patch files to not be installed at all. Cant find the special cust files in /data. Any ideas?

My previous rom was rros and i had formatted my data partition to ext4 instead of f2fs to overcome the partition wipe bug that it had. But i dont think this is the cause?

Have a L19 P9 and had no issues installing v3 of this rom when it came out

Edit: OR maybe changing the data file system maybe have been the root cause. In that case ll have to flash a stock firmware again and build my way back up?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
This is exactly the case - your data partition MUST be f2fs, cause MRv3 is a Stock based Rom!

I am sorry - but you must go back to Stock Firmware first.

Use the technique from Post #3.

After boot to Stock Rom with short setup.

And then do the Installation Guide from Post #1

Its a bit of reading and making but if you like to have a properly working Rom you must do the related steps ;)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Edit: Which cust to you have?

Cause if it is c636 I upload HWOTA.zip for this tonight
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] SkywalkerZ:
Its either c432 or c636 and i cant confirm it because the dialer codes don't seem to work. Any other way to confirm?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
With Root Explorer navigate to /cache/recovery/last_log

Open last_log with Text-Editor and search for the Line (mostly Line 564): persist.radio.cota_version=_C432_ (?) - (example) it will show your cust
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] SkywalkerZ:
This line doesn't exist

Wait if i purchased this Phone from a Asia, then the cust should be 636 correct?

IS checking in /cust reliable?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] syrkles:
I was in the same boat and I used the HWOTA method thats in the second post
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
So your cust is c636 - and it is important (for using other custs Debranding would necessary)

I will upload L19c636 b394 HWOTA.zip tonight.

(here in Germany time is 0:50 PM - upload is ready arround 12 PM cause I am on work now)

List of CUST Region Provider:

C02 Europe Vodafone

C10 Russia

C21 Telefonica / O2

C40 Czech Republic Telefonica / O2

C55 Italia TIM

C86 Spain Yoigo

C112 Latin America

C121 Türkei

C123 Switzerland

C150 Telekom

C151 India

C185 Middle East

C209 Asia (Pacific)

C249 Serbia Telekom

C432 Europe

C470 Asia (Pacific)

C605 Colombia

C636 Asia (Pacific)

C637 Spain

C675 India

C900 Generic Free intern. Version
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
It's in Post #3
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] PetoNHL:
since i installed the v3 version on my P9 EVA-L19 in Magisk is always "ctsProfile: false" in SafetyNet check... i made a clean instal + patch... what should i do to fix this? :)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Have you done (see Post #1) Safetynet Workaround?

Yes /no?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] diabolo24:
Installed Magisk 15.3 and everything works

I used a direct installation.

Previous magisk 15.2 installed using the flashable zip by Tecalote method.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] zgfg:
Magisk Manager 5.5.5 and Magisk 15.3, everything ok.

This time and in previous updates: Direct installation with both Preserve Force encryption and AVB 2.0
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Magisk 15.3 Update

Users who have already previous Magisk v15.2 installed - current Magisk Update to 15.3 is working in both situations with Direct Install Method

Situation 1:

If you had used my provided zip for updating from older version to 15.2 from here: https://xdaforums.com/showpost.php?p=75059492&postcount=222

Current update to version 15.3 works with Direct Install method like [MENTION=7468280]diabolo24[/MENTION] told - but in this case also without "Preserve AVB 2.0 /dm-verity"

"Preserve force encryption" - is enabled by default.

Situation 2:

If you made previous update from older version to 15.2 without using my zip but with Direct Install method like described here: https://xdaforums.com/showpost.php?p=74997195&postcount=162

- it works like [MENTION=7786725]zgfg[/MENTION] told with Direct Install method with both "Preserve AVB 2.0 /dm-verity" and of course with "Preserve force encryption" enabled (force encryption is enabled by default)

For Updating to v15.3 after new ROM Installation you can use this special zip for MRv3 made by Tecalote:

https://www.androidfilehost.com/?fid=817906626617958352

Just flash with TWRP and reboot (without wipe dalvik/cache)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
[MENTION=5432718]SkywalkerZ[/MENTION] Your hwota.zip EVA-L19-c636 (b394) is uploaded and linked in this post #3 on page 1: https://xdaforums.com/showpost.php?p=74913874&postcount=3
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] PetoNHL:
i can't find "Huawei-ID (Huawei Mobile Services)" what is the name of the file? other files are chcecked for hide
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] SkywalkerZ:
How was your bootup time like? i have gone into boot loop after installing firmware. cant factory reset.
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] syrkles:
Did u format internal storage??
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] SkywalkerZ:
nvm fixed it :D
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Which Phone model do you have?

EVA-xxx-c...?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] PetoNHL:
c432... with installed data files patch v2 for the L19c432
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
Have you used the updated data files patch v2 zip 187,5 MB?

You should have in native settings "Huawei ID" and in Magisk Hide the package Name is: com.huawei.hwid
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] PetoNHL:
updated to data files v2 via twrp, wiped dalvik/cache, restarted, in magisk hide checked hicare, hwid, com. android.vending and hidisk, rebooted and still ctsProfile: false
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] Tecalote:
If you look into Magisk Manager, which Modules have you installed? Tell me

(because there are some preinstalled ones and if they are not there, safetynet will not work)
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] darrr1:
I had MRv.2 on b386 and next I instaled MRv.3 . Can I use HWOTA.b394 to back to stock?
[Huawei P9 ROMs, Kernels, Recoveries, & Other Devel] PetoNHL:
there are the following Modules: Busybox for Android NDK, Huawei Property Fix, Magisk SELinux Permissive Script and i have installed also injected Youtube Background Playback for Magisk