I answered in Post #458I guess that's all XD
Last edited:
I answered in Post #458I guess that's all XD
Solved! Thank you.I read the whole thread. Thanks for helping @Party5999
At first you should remove the Universal SafetyNet Fix, because as long as you have this module installed, cts profile will not be true.
The SafetyNet Fix changes the ro.build.fingerprint to a Xiaomi device and this is dedected with newer Firmwares.
1) Use the attached zip for uninstalling SafetyNet Fix. Flash it with TWRP, wipe (only) Dalvik/Art Cache and Cache (with advanced wipe) and reboot phone. (reboot will need perhaps 5 min)
2) Go to settings /apps /Magisk Manager /storage and deleta data and cache - btw: which Magisk version to you have installed? 16 until 16.3 is okay, but I would not recommend 16.4 (because its bugy and misses arm64 libraries)
3) Check settings /developer options - if USB Debugging is enabled (if it is disabled, then enable FIRST ADB Debugging in charging mode and AFTER USB Debugging)
3) Reboot phone, open Magisk Manager, check safetynet and tell me the result. If cts profile is false again, we will do some further steps.
DO NOT - if you can't live with the warning you must flash back to the stock firmware (ROM and recovery), by HWOTA, before relocking the Bootloader.Solved! Thank you.
Can I lock the bootloader? Becasue the warning that appear everey time I boot the phone is annoying.
I can live with it but is so boring but, I'll keep it if there aren't any tricks to hide it.DO NOT - if you can't live with the warning you must flash back to the stock firmware (ROM and recovery), by HWOTA, before relocking the Bootloader.
Relocking triggers internal hard reset and you must be on the stock firmware - otherwise you risk to brick the phone
Search on Google for "Your device is unlocked and cannot...", you will see reports from various phone makes and modelsI can live with it but is so boring but, I'll keep it if there aren't any tricks to hide it.
There aren't any tricks to hide it.I can live with it but is so boring but, I'll keep it if there aren't any tricks to hide it.
Good news here, the update worked, and now I successfully have B190, I got the OTA B361 and were updating. Very thankful for the guide.Okay, I would say before debranding we give it a second try and use instead:
EVA-L19C636B190 Full Firmware for going back from Renovatio to Stock: http://www.carbontesla.com/2016/10/download-huawei-p9-b190-marshmallow-firmware-asia/
You have right now EMUI Recovery instead of TWRP and no Root, right? If yes, this is good, because it is required!
1) Download this Full Firmware, extract it and copy META-INF and UPDATE.APP to dload folder on your external SD. The folder: dload must be in the main directory of your external SD
2) Use Vol+ and Vol- and Power Button. Press Vol+ and Vol- in the middle down and at the same time the Power Button. Keep pressing. Phone reboots and EMUI Update is starting. Release the 3 Button in the moment, the update is started - but not before.
The Update should be arive 100% and Phone reboot after. Only with succesful Update you are back to original Android 6 Firmware for your device and this is required for OTA to Android 7.
Tell me, if the update was succesful and if you receive OTA.
That's good news :good:Good news here, the update worked, and now I successfully have B190, I got the OTA B361 and were updating. Very thankful for the guide.
This is debloated ROM, and rooted hence you can freeze or uninstall further not needed apps.Hi guys, I own P9 too. In general I do not have much time to experiment with different ROM and I am satisfied with the default one, however even after replacing the battery, my phone last on battery barely a day. Do you have experiences with custom ROMs like this one with better battery life? If so, how much is the difference?
Use GreenifyHi guys, I own P9 too. In general I do not have much time to experiment with different ROM and I am satisfied with the default one, however even after replacing the battery, my phone last on battery barely a day. Do you have experiences with custom ROMs like this one with better battery life? If so, how much is the difference?
I'm very impressed with Nougat stock B399, everything's smoother and faster even than Renovation, some things I'm still not satisfied are lacking auto-call recorder, the app-twin is too limited and the ringtone of alarm is from small to very small, I missed twice, luckily I'm not fired for it. Clearly Mashmallow did better with alarms.That's good news :good:
Soon as Oreo will be officially released and then some weeks later (for testing)I'm very impressed with Nougat stock B399, everything's smoother and faster even than Renovation, some things I'm still not satisfied are lacking auto-call recorder, the app-twin is too limited and the ringtone of alarm is from small to very small, I missed twice, luckily I'm not fired for it. Clearly Mashmallow did better with alarms.
I'd like to say Mashmallow is very terrible after long time using even with custom ROM, maybe Nougat will be different. When is your turn with Oreo?
Changing Bootanimation is a little bit difficult, because the path is restricted.Hi everyone, I'm back again.
Can you tell me why, when iI try to paste something like a different bootanimation into product/etc/media, it shows me that error:
https://drive.google.com/file/d/1wqqIyWDBRH4xEHi9ch8tNOLvGi-slXcG/view?usp=sharing
I've already tried with TWRP Filemanager but it only shows the product folder without anything in it. Yesterday night (Italy) I don't know how but with many attempts I could paste things into product/etc/media folder. Now I need to edit it again. Help?Changing Bootanimation is a little bit difficult, because the path is restricted.
The Bootanimation you like to change must have similar size as the original one. Not much more, but it can be less.
The zip must have "store" format (not more compressed) and you can't copy it with Root Explorer.
You must change it with TWRP Filemanager (Advanced /Filemanager) and you must replace the original one with the same name (do not rename original one to .bak and do not delete the original before copying the new one, just replace it)
If you make anything wrong and Android check that you had modified this path, you will see during Boot only Android Logo and cannot change this anymore.
Only way in this case is new flashing the Rom.
You must first mount product in TWRP "Mount"I've already tried with TWRP Filemanager but it only shows the product folder without anything in it. Yesterday night (Italy) I don't know how but with many attempts I could paste things into product/etc/media folder. Now I need to edit it again. Help?
Yes, it is absolutely REQUIREDWill we need to install stock and update to emui 8 (once its out) before we can flash mr5?