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

[zgfg]

Ok, in this case, you might have one more thing to try. Lock back the bootloader (relock) and then unlock it again. Even if this time it fails to flash then it might be something with the new version of your OS.

In Developer Options, OEM Unlocking is grayed out (disabled control), with radio button Off - but I think it was also previously like that, when I was running TWRP+b378/b383.

How does it look for you "OEM Unlocking" looks for you (grayed out, button in Off position, or?)
Should I still try un-locking/relocking Bootloader with this position of OEM Unlocking control?

Another option I was thinking about - if somebody can send me a pre-rooted (based on SuperSU-v2.79-201612051815-EMUI5.0 ?) boot image for l09 c432 b386, I will try to flash by:
fastboot flash boot b386_boot_stock.img
just to start with b386 rooted (while still trying to flash TWRP)

 

[Fabrissa393]

Why the recovery fails to format data ecc?

 

[Tecalote]

Windows Start, Command Prompt - right click, Run as Administrator.
Re-doing again (it was in posts #406 and #408, showing that adb and fastboot commands work, i.e. that USB debugging was enabled, etc)
Now I did also your suggestion: fastboot oem get-bootinfo
- adb devices: WORKS
- adb reboot bootloader : WORKS
- fastboot devices: WORKS
- fastboot oem get-bootinfo: WORKS; says that bootloader is unlocked (just like fastbooot screen on the phone says, and booting screen saying that phone is un-trusted because of unlocked)
- fastboot flash recovery twrp-3.1.0-2-eva.img: NOT WORKING: says that command is not allowed (I tried with 3.1.0-1, -2 and -3, all are in \ADB folder, their IMG file names are correct, copy/pasted)
- fastboot oem device-info: Also NOT WORKING (not important)

Btw, it is the same P9, same two PCs (with the same ADB installation) I used a month ago when I unlocked the bootloader and first time successfully flashed twrp-3.1.0-1-eva.img
Now doing everything the same, itstarts flashing (sending 'recovery' (25220 KB)... OKAY [ 0.540s] writing 'recovery'...) and then says: FAILED (remote: Command not allowed)

ADB-FASTBOOOT commands from Command Prompt:
C:\adb>adb reboot-bootloader
C:\adb>fastboot devices
MWS0216729010044 fastboot

C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.010s]
finished. total time: 0.010s
C:\adb>fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.010s
C:\adb>fastboot flash recovery twrp-3.1.0-2-eva.img
target reported max download size of 471859200 bytes
sending 'recovery' (25220 KB)...
OKAY[ 0.540s]
writing 'recovery'...
FAILED(remote: Command not allowed)
finished. total time: 0.550s

Maybe it's just a fastboot driver problem with windows. Which version to you use - Windows 10?

If so, open device manager during phone is connected with USB in fastboot mode.
If device manager shows you: Kedacom USB Device Android Bootloader Interface - its the wrong one!
You must change it to Android Sooner Single ADB Interface

 

[zgfg]

Maybe it's just a fastboot driver problem with windows. Which version to you use - Windows 10?
If so, open device manager during phone is connected with USB in fastboot mode.
If device manager shows you: Kedacom USB Device Android Bootloader Interface - its the wrong one!
You must change it to Android Sooner Single ADB Interface

Windows 7, Device Manager under Android Device shows: Android Sooner Single ADB Interface

Instead of TWRP, Id like to try flashing SuperSU prerooted boot image for l09 c432 b386 by fastboot, if somebody can send - thanks

 

[Tecalote]

Windows 7, Device Manager under Android Device shows: Android Sooner Single ADB Interface

Instead of TWRP, Id like to try flashing SuperSU prerooted boot image for l09 c432 b386 by fastboot, if somebody can send - thanks

Have you checked again Developer options. Cause I enabled one times USB Debugging and as I leave developer options and opened it again it was unchecked (but before I had enabled it)
That's why I enable 1) ADB Debugging and 2) USB Debugging and then it stays enabled.
Of course "always ask...." must also be enabled
And I use always Minimal ADB and Fastboot program instead of Windows inbuilt cmd.
May you give it once more a try. And maybe also on another PC. Windoof sometimes makes troubles.

 

[jonezie]

Does anyone know when Xposed will be available for Android Nougat? Its been quite a long wait.

 

[zgfg]

Have you checked again Developer options. Cause I enabled one times USB Debugging and as I leave developer options and opened it again it was unchecked (but before I had enabled it)
That's why I enable 1) ADB Debugging and 2) USB Debugging and then it stays enabled.
Of course "always ask...." must also be enabled
And I use always Minimal ADB and Fastboot program instead of Windows inbuilt cmd.
May you give it once more a try. And maybe also on another PC. Windoof sometimes makes troubles.

If you disable USB debugging, would you have any response on adb devices, adb reboot, fastboot devices, fastboot flash, etc?!

I have tried more than 20 times over the last three days, on two PCs (same PCs where it worked a month ago), experimenting eith different USB/ADB and debugging options, revoking credentials for PC, Always ask On and Off, versions of TWRP, etc.

 

[OldDroid]

Try to disable USB debugging, would you have any response on adb devices, adb reboot, fastboot devices, fastboot flash, etc - how would that do if USB debuggibg was not activated?!

I have tried more than 20 times over the last three days, on two PCs (same PCs where it worked a month ago), experimenting eith different USB/ADB and debugging options, revoking credentials for PC, Always asj On and Off, versions of TWRP, etc.

unlock your frp by relocking and unlocking again.
my guess is that your frp lock got set again after an ota update for example.

Regards

 

[ogisha]

Windows 7, Device Manager under Android Device shows: Android Sooner Single ADB Interface

Instead of TWRP, Id like to try flashing SuperSU prerooted boot image for l09 c432 b386 by fastboot, if somebody can send - thanks

Tell me how to make it from twrp or by some other way and I will send you.

 

[zgfg]

Ok, in this case, you might have one more thing to try. Lock back the bootloader (relock) and then unlock it again. Even if this time it fails to flash then it might be something with the new version of your OS.

---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------

unlock your frp by relocking and unlocking again.
my guess is that your frp lock got set again after an ota update for example.
Regards

Thanks, this is on my toDo next list, but (before I possibly screw up my daily driver by relocking/unlocking bootloader while OEM Unlocking control is disabled) I would still like to try fastboot flashing pre-rooted boot img for b386


---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------

Tell me how to make it from twrp or by some other way and I will send you.

TWRP creates boot WIN backup but not IMG, I think mkbootimg tool must be used, but I never tried myself

---------- Post added at 09:13 AM ---------- Previous post was at 08:50 AM ----------

If you want a method which works to 100%. You look the first link to my signature. This is the last tuto, I modify your stock boot and you will be rooted after to have installed supersu Emui 5.0.
This method has been used on:
- Huawei mate 8
- Huawei Honor note 8
- And also Huawei P9
I made it for all these models.

Do you please have SuperSU pre-rooted boot img for l09 c432 b386 - thanks

 

[OldDroid]

---------- Post added at 08:47 AM ---------- Previous post was at 08:46 AM ----------



Thanks, this is on my toDo next list, but (before I possibly screw up my daily driver by relocking/unlocking bootloader while OEM Unlocking control is disabled) I would still like to try fastboot flashing pre-rooted boot img for b386


---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------


TWRP creates boot WIN backup but not IMG, I think mkbootimg tool must be used, but I never tried myself

---------- Post added at 09:13 AM ---------- Previous post was at 08:50 AM ----------



Do you please have SuperSU pre-rooted boot img for l09 c432 b386 - thanks

wont work, you cannot flash images at all when frp lock is active, but since you know better .. try it, feel free to report if it worked

 

[franzyroy]

Do you please have SuperSU pre-rooted boot img for l09 c432 b386 - thanks

I don't make that!
I only modify the stock boot in order that the root is installed without issue.
If you want, send me the stock boot B386 than I modify it.

 

[zgfg]

I don't make that!
I only modify the stock boot in order that the root is installed without issue.
If you want, send me the stock boot B386 than I modify it.

How, where can I extract my boot b386 img, I'm not rooted and don't have TWRP (cannot flash it, described in previos posts, and thus looking just for prerooted boot img...)

 

[franzyroy]

How, where can I extract my boot b386 img, I'm not rooted and don't have TWRP (cannot flash it, described in previos posts, and thus looking just for prerooted boot img...)

You can make it with "adb shell" and bootloader mod but I don't have the command lines in my head.

Edit:

Like that!

adb shell

type enter

dd if=/dev/block/mmcblk0p28 of=/sdcard/boot.img

type enter

---------- Post added at 12:35 ---------- Previous post was at 12:23 ----------

. @zgfg

I edited my post!

 

[zgfg]

I edited my post!

Yes thanks, I've sent you PM

 

[zgfg]

unlock your frp by relocking and unlocking again.
my guess is that your frp lock got set again after an ota update for example.

Unfortunately no success that way either, relocking fails with "remote: root type is risk"
(of course, using the same code as a month+ ago when I unlocked the bootloader):

C:\adb>fastboot devices
MWS0216729010044 fastboot

C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s

C:\adb>fastboot oem relock 3523522616076272
...
FAILED (remote: root type is risk)
finished. total time: 0.010s

C:\adb>fastboot oem lock 3523522616076272
...
FAILED (remote: Command not allowed)
finished. total time: 0.010s

C:\adb>fastboot oem unlock 3523522616076272
...
FAILED (remote: Command not allowed)
finished. total time: 0.010s

 

[Tecalote]

@zgfg It looks like as a small brick on your device. This can be occure if you go back from Custom Rom to Stock with Project Menu instead of 3 Button Method - I think you must go back with b300 TransitionPack to 6.0, then b182 and after you can go back to b378 and up. If dload Method works.
I had yesterday a bricked device from an User to repair and fastboot command told me the same as I tried to relock and unlock bootloader...

 

[chudy_85]

Unfortunately no success that way either, relocking fails with "remote: root type is risk"
(of course, using the same code as a month+ ago when I unlocked the bootloader):

C:\adb>fastboot devices
MWS0216729010044 fastboot

C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s

C:\adb>fastboot oem relock 3523522616076272
...
FAILED (remote: root type is risk)
finished. total time: 0.010s

C:\adb>fastboot oem lock 3523522616076272
...
FAILED (remote: Command not allowed)
finished. total time: 0.010s

C:\adb>fastboot oem unlock 3523522616076272
...
FAILED (remote: Command not allowed)
finished. total time: 0.010s

If you have unlocked bootloader flash b300 then flash b182 and here you must enable developers option and uncheck oem. Now update to b378/383 using ota and you have locked bootloader and frp to

 

[zgfg]

@zgfg It looks like as a small brick on your device. This can be occure if you go back from Custom Rom to Stock with Project Menu instead of 3 Button Method - I think you must go back with b300 TransitionPack to 6.0, then b182 and after you can go back to b378 and up. If dload Method works.
I had yesterday a bricked device from an User to repair and fastboot command told me the same as I tried to relock and unlock bootloader...

Yes, if no other way I'll have to bite the bullet and downgrade, etc.
But I will wait for a major Huawei update, currently (apart from this fact that I cannot install TWRP to proceed with rooting), I'm very satisfied with b386:
- some bloatware (Newsrepublic, etc) are user apps (as always) and they can be uninstalled, some unwanted apps can also be disabled
- very satisfied with battery consumption
- from e.g. your Magic Rainbow (n/a for b386 yet) I mainly miss V4A, and from Advanced Settings back-light flashing notifications

 

[Tecalote]

...
- from e.g. your Magic Rainbow (n/a for b386 yet) I mainly miss V4A, and from Advanced Settings back-light flashing notifications

Yes I am waiting for firmware update too (perhaps Emui 5.1)
then I will update "MR" - sorry for OT