[TWRP][P9][3.1.1-1][EMUI 5.x/AOSP N][DECRYPTION SUPPORT]

[mnv12345]

@OldDroid,
Could you tell if I will install your twrp to Erecovery will it work?

 

[lapocompris]

I want to reinstall L09C432B378, is it possible to flash the EVA-L09C432B378.zip with TWRP ?
If not how to revert to stock recovery ?

 

[dkionline]

@OldDroid,
Could you tell if I will install your twrp to Erecovery will it work?

You can flash to recovery or recovery2 partition but not on both at same time.

I want to reinstall L09C432B378, is it possible to flash the EVA-L09C432B378.zip with TWRP ?
If not how to revert to stock recovery ?

Just wipe and flash zip

 

[lapocompris]

Just wipe and flash zip

Nope, didn't work.
Do you know how to revert to stock recovery ?

 

[dkionline]

Nope, didn't work.
Do you know how to revert to stock recovery ?

Flash stock recovery from update.app with fastboot flash recovery recovery.img then install firmware + hw/eu through dload. Please not spam here and check specific thread for this.

 

[ogisha]

Hy guys I need a help.
I own P9 B378.
I properly unlocked bootloader with code I got from dc-unlocker and I am getting yellow warning message every time I reboot.
Now I want to install the recovery.
ADB is working fine, it detects my device, but when I type fastboot devices or fastboot reboot-recovery nothing happens. Like my windows fastboot driver has disappeared!?
When I manually enter eRecovery, by pressing vol+up, and type fastboot flash recovery twrp-3.1.0-0-eva.img then I get waiting for device message.
Fastboot devices also does not giving me any answer.
I tried rebooting both phone and computer and it did not help.
Edit:
I have found the solutions. I was typing fastboot reboot-recovery instead of adb reboot-recovery. Everything worked like a charm.
I have one more question. Where could I find @Atarii's prerooted boot.img?
Edit2: I have found prerooted boot.img. I tried to flash supersu afterwards, because I read here somewhere that it is possible, and now my phone is in bootloop.
Please help!!
Edit3: I have solved it by flasing unSU.zip which removed both supersu and superuser. Flashed prerooted boot.img and rebooted, afterwards, system booted fixed and phh's superuser rooted.
I thought I should delete this post, because I had solved everything on my own with no help from anybody, but I thought maybe my experience would be of help to somebody else.
Pitty there is no way to install Chainfire's SuperSU.
Moderator is free to delete this post if he wants to.

 

[sherazjaved]

Help me i think i have bricked my huawei p9..
i unlock mu bootloader and then it restart but stuck on
your device is booting now...
Nothing works i restarted several times but it is stuck here.
i tried to put a dload file in sd card and then try to manually update by pressing 3 buttons simultaneously but didnt worked and it restart every time and stuck on
your device is booting now...
Nothing works help me please

 

[zgfg]

After TWRP was installed, you should reboot your device into TWRP in this way :

- with your device in bootloader mode ( and after TWRP was installed by : fastboot flash recovery C:\twrp-3.1.0-0-eva.img, in your case ) you should make three operations at the same time :

* press & keep pressed Volume Up
* fastboot reboot
* disconnect the USB cable as soon as possible !

Right now your device will boot into TWRP ( you can release Volume Up, at the same time with : "your device is booting now ... ")

This is the right way to install any custom recovery !

It worked for me but only by
* simultaneusly pressing both Volume Up and Power buttons (not just the Volume Up)
and the rest as you have described

 

[OldDroid]

It worked for me but only by
* simultaneusly pressing both Volume Up and Power buttons (not just the Volume Up)
and the rest as you have described

you have to press both, power and vol+, after device vibrates you should release only the power button.

 

[OldDroid]

lil teaser: unified support is incomming, means los and emui ready..

 

[SideSkroll]

Guys, first of all. I want to thank the devs for what they have done here. I know kirin is kinda new and not many people are interested in cracking it open it appears as previous huawei phones never got CM /lineageOS.
Thanks for that.
Anyway, now onto my issue at hand.
I have a P9 L09 cust 432. I had it with nougat (378) and I decided to try and install a custom recovery and root it if possible.
I found the appropriate threads etc.
Well, apparently I managed to install the recovery correctly as I'm now able to get into TWRP and everything seems to be working fine, EXCEPT for the factory reset it appears... Cause I did it (from within TWRP) and well, apparently it messed up my phone since now not only are icons and wallpapers "old" (ugly looking) but things like flashlight don't work. The phone itself boots no problem, I can connect to the internet (haven't tried calls etc since I have no SIM in it ATM) so I'm not sure what has happened... Did the factory reset corrupted the rom? If that's the case, is there a way to reinstall from TWRP instead of having to go the dload + 3 buttons method (and having to unlock, install recovery and root AGAIN)
Basically, a stock 378 rom in zip format?
Any help would be greatly appreciated.
And keep up the good work guys!

 

[OldDroid]

Guys, first of all. I want to thank the devs for what they have done here. I know kirin is kinda new and not many people are interested in cracking it open it appears as previous huawei phones never got CM /lineageOS.
Thanks for that.
Anyway, now onto my issue at hand.
I have a P9 L09 cust 432. I had it with nougat (378) and I decided to try and install a custom recovery and root it if possible.
I found the appropriate threads etc.
Well, apparently I managed to install the recovery correctly as I'm now able to get into TWRP and everything seems to be working fine, EXCEPT for the factory reset it appears... Cause I did it (from within TWRP) and well, apparently it messed up my phone since now not only are icons and wallpapers "old" (ugly looking) but things like flashlight don't work. The phone itself boots no problem, I can connect to the internet (haven't tried calls etc since I have no SIM in it ATM) so I'm not sure what has happened... Did the factory reset corrupted the rom? If that's the case, is there a way to reinstall from TWRP instead of having to go the dload + 3 buttons method (and having to unlock, install recovery and root AGAIN)
Basically, a stock 378 rom in zip format?
Any help would be greatly appreciated.
And keep up the good work guys!

thanks for your thankful question!
No you didn' mess up your rom!
You just wiped data which has rom parts in it!
so you either have to find your corresponding rom data zip which you need to flash, or do it the hard way like you mentioned already.
I suggest you ask for the link in the Q&A section,
really don't know where to find it actually.
Maybe @Atarii could help?

 

[SideSkroll]

thanks for your thankful question!
No you didn' mess up your rom!
You just wiped data which has rom parts in it!
so you either have to find your corresponding rom data zip which you need to flash, or do it the hard way like you mentioned already.
I suggest you ask for the link in the Q&A section,
really don't know where to find it actually.
Maybe @Atarii could help?

Thank you for replying.
So I take it that factory resetting from TWRP when on a stock ROM is a big no-no?
Damn... I was hoping that I'd be able to somehow restore/re-flash from TWRP... :crying:

 

[OldDroid]

Thank you for replying.
So I take it that factory resetting from TWRP when on a stock ROM is a big no-no?
Damn... I was hoping that I'd be able to somehow restore/re-flash from TWRP... :crying:

you can, but that requires the hw data update zip i mentioned. It's emui fault as they are storing system related stuff on userdata / data partition

Edit: https://www.hidrive.strato.com/lnk/aAFDlgDX
Here you go

Regards

 

[zgfg]

Why this TWRP names its back-ups as TEST KEYS, like 2017-03-29--08-29-19_NRD90M_test-keys

 

[Tecalote]

Why this TWRP names its back-ups as TEST KEYS, like 2017-03-29--08-29-19_NRD90M_test-keys

Cause you have in your Phone Info this build.
That means you didn't use the official way to receive Nougat.
Your steps of installations of different Firmwares makes something corrupted.

 

[OldDroid]

Why this TWRP names its back-ups as TEST KEYS, like 2017-03-29--08-29-19_NRD90M_test-keys

thats the standard backup description on twrp, whats wrong with it?

 

[Tecalote]

thats the standard backup description on twrp, whats wrong with it?

Sorry, I didn't know this Previous TWRPs are using always the Name which is given in Phone Info App in relation to the info in buid prop...
As I heard the name with "test keys" I thought the Nougat Installation of @zgfg must be corrupted, because a friend of mine has a corrupted Nougat Installation and in his Phone Info is a simular name..

 

[zgfg]

Sorry, I didn't know this Previous TWRPs are using always the Name which is given in Phone Info App in relation to the info in buid prop...
As I heard the name with "test keys" I thought the Nougat Installation of @zgfg must be corrupted, because a friend of mine has a corrupted Nougat Installation and in his Phone Info is a simular name..

---------- Post added at 11:20 AM ---------- Previous post was at 11:20 AM ----------

thats the standard backup description on twrp, whats wrong with it?

[/COLOR]

It's not an important feature but I've seen TWRP ports to other phones that replace the string template "test-keys" by TWRP version, phone model and/or firmware version.
Firmware version is particularly useful for later keeping back-ups of different versions and restoring them (experimenting with) back and forth.
Of course, one can always rename it manually...

---------- Post added at 11:30 AM ---------- Previous post was at 11:20 AM ----------

Thank you for replying.
So I take it that factory resetting from TWRP when on a stock ROM is a big no-no?
Damn... I was hoping that I'd be able to somehow restore/re-flash from TWRP... :crying:

you can, but that requires the hw data update zip i mentioned. It's emui fault as they are storing system related stuff on userdata / data partition

Maybe also related to something like this. IMO, TWRP port to the given phone (and/or EMUI version in this case) could adjust to the peculiarities on the given platform (like specific paths and so)

 

[OldDroid]

---------- Post added at 11:20 AM ---------- Previous post was at 11:20 AM ----------


[/COLOR]

It's not an important feature but I've seen TWRP ports to other phones that replace the string template "test-keys" by TWRP version, phone model and/or firmware version.
Firmware version is particularly useful for later keeping back-ups of different versions and restoring them (experimenting with) back and forth.
Of course, one can always rename it manually...

---------- Post added at 11:30 AM ---------- Previous post was at 11:20 AM ----------





Maybe also related to something like this. IMO, TWRP port to the given phone (and/or EMUI version in this case) could adjust to the peculiarities on the given platform (like specific paths and so)

well, i won't touch twrp code directly unless strictly necessary! And since this isn't considered as a bug/error for me, i won't change it.

Regards