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

[wate87]

Hi, I was stuck in fastboot mode.

- P9 Nougat Emui 5.0
- PHONE unlocked
- FRP lock

I tried in cmd window to flash TWRP but always failed....

C:\Users\Jecht\Downloads\adb-fastboot-tool-2016>fastboot flash recovery recovery
.img
target reported max download size of 471859200 bytes
sending 'recovery' (25282 KB)...
OKAY [ 0.729s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.755s

any idea/guide for me?

 

[dkionline]

Hi, I was stuck in fastboot mode.

- P9 Nougat Emui 5.0
- PHONE unlocked
- FRP lock

I tried in cmd window to flash TWRP but always failed....

C:\Users\Jecht\Downloads\adb-fastboot-tool-2016>fastboot flash recovery recovery
.img
target reported max download size of 471859200 bytes
sending 'recovery' (25282 KB)...
OKAY [ 0.729s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.755s

any idea/guide for me?

flash back to stock with dload and activate oem unlock in developer options.

 

[wate87]

flash back to stock with dload and activate oem unlock in developer options.

Thanks for your replied, do you mind guide me step-by-step flash back to stock with dload ?
I have no idea how to do that

 

[zgfg]

Hi, I was stuck in fastboot mode.

- P9 Nougat Emui 5.0
- PHONE unlocked
- FRP lock
I tried in cmd window to flash TWRP but always failed....
C:\Users\Jecht\Downloads\adb-fastboot-tool-2016>fastboot flash recovery recovery
.img
target reported max download size of 471859200 bytes
sending 'recovery' (25282 KB)...
OKAY [ 0.729s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.755s
any idea/guide for me?

Did you mind to read single page back on this thread, posts #484-#486 (same problem, solution that worked)
https://forum.xda-developers.com/showpost.php?p=72682125&postcount=486

Btw, "reinstalling (stock) firmware" is not enough, as described, you need to rollback to MM...

 

[dyollabus]

Whenever im making a backup and reboot. And tried to go back, the recovery is always on stock. Twrp is missing.. Is it a bug?

 

[LastStandingDroid]

Did you mind to read single page back on this thread, posts #484-#486 (same problem, solution that worked)
https://forum.xda-developers.com/showpost.php?p=72682125&postcount=486

Btw, "reinstalling (stock) firmware" is not enough, as described, you need to rollback to MM...

That's just a hoax u don't "have to"

Sent from my FRD-L09 using Tapatalk

 

[Guugle_]

NOT BAD

 

[Tecalote]

@OldDroid The new TWRP 3.1.1-1 is better for backup and restore - but I find some things better in previous version.
If I disable in actual v automount of vendor in settings and uncheck it in "Mount" - after restarting TWRP, vendor is mounted again - even it is unchecked in settings.
The mount of vendor is good for some reason but for other it makes complications when flashing something other than SuperSU. Example: read only error...
Some partition cannot be wiped with graphics ui, not good if Custom Roms having most Partitions included.
And who of the normal user make the work to start Terminal for backup the other Partitions as img, except boot, data, system, vendor and cache (which is possible in grafic ui).
If I test something which modify product, version, cust and perhaps Phone doesn't boot - its no help to restore the Nandroid, cause it dont include the other Partitions.
So I must flash whole Stock Firmware again...
I just wanted to report and notice.
Thanks anyway for your good work

 

[ricardo99831390]

You can try to relock/unlock bootloader but it will probably fail similarly.
Check your Fastboot screen on the phone - does it show FRP Locked?
If so, make sure you enable OEM Unlocking under Developer Options.

But if:
- OEM Unlocking is disabled and grayed under Developer Options
- Fastboot shows FRP Locked (with Bootloader Unlocked)
then you're in trouble, you will have to Downgrade to b300, upgrade to b182, and then upgrade (hopefully by OTA) to b383->b386 to be able to enable OEM Unlocking (unlock FRP) and to proceed with flashing TWRP

I understand but in order to downgrade acording to huawei, you need to have the bootloader locked and flash the rollback file. something i cant do because i cant lock the bootlader since i dont have adb comands cause i have the frp locked.
is there something i could do?? its not my ohine but i would like to help a friend

 

[ksuhiyp]

where can we donate, flattr?

 

[OldDroid]

where can we donate, flattr?

paypal ([email protected])

 

[Tecalote]

@OldDroid If you get time - can you fix please the vendor issue?
Vendor stays mounted - even it is unchecked /disabled in settings (Auto-Mount).
After reboot TWRP vendor is mounted...
Thanks

 

[OldDroid]

@OldDroid If you get time - can you fix please the vendor issue?
Vendor stays mounted - even it is unchecked /disabled in settings (Auto-Mount).
After reboot TWRP vendor is mounted...
Thanks

yes, i will remove the feature!
it requires too much modifications to get it running properly.
E.g. it is mounted on every start but as RO, not RW

Regards

 

[Tecalote]

yes, i will remove the feature!
it requires too much modifications to get it running properly.
E.g. it is mounted on every start but as RO, not RW
Regards

Yes, if it is too complicated it's better to remove, because RO is sometimes a problem with updater-script. If I would like to install something to vendor I get the RO error during the script - if I don't uncheck vendor in Mount before.
If it would RW maybe the problem didn't occur.
Its not a big issue. I can disable vendor before flashing Rom. I just must not forget to do it...
But you decide what's the best to solve.
Thank you

 

[rayman95]

is this the maximum to safely wipe to have a clean flash, or check internal storage can cause disfonction???
there isn't like described in Bluewei op cust, product and system....

2a. Wipe cust, data, vendor, version, product and system for clean flash

is it due to new TWrp version??
thank's

 

[Tecalote]

is this the maximum to safely wipe to have a clean flash, or check internal storage can cause disfonction???
there isn't like described in Bluewei op cust, product and system....

is it due to new TWrp version??
thank's

You can do it with previous version and you can download it from here:
https://www.androidfilehost.com/?fid=817550096634785012

Internal storage I wouldn't wipe directly before Rom Installation - its not necessary and can make errors during installation, if you want to wipe internal storage do it in an extra step before wiping the other Partitions and then Reboot TWRP. After you can allow system modification again (cause TWRP stores his settings on internal memory, which are wiped too during wipe internal storage)
After you can make the wipe of the recommended Partitions and flash the Rom.

 

[rayman95]

You can do it.

So just to be sure I have understand correctly...
1. Downgrade Twrp
2. Wipe internal storage
3. Reboot Twrp
4. Wipe cust, product, system, cache, dalvik, factory reset.
5. Flash the ROM....reboot...
And enjoy super clean ROM!!!!
Is it correct????
Thanks...
Sorry to be so precautionous, but the thread Q&A is full of post about bricked phones....

 

[Tecalote]

So just to be sure I have understand correctly...
1. Downgrade Twrp
2. Wipe internal storage
3. Reboot Twrp
4. Wipe cust, product, system, cache, dalvik, DATA
5. Flash the ROM....reboot...
And enjoy super clean ROM!!!!
Is it correct????
Thanks...

Yes, at point 4 use Advanced Wipe and wipe only the Partitions which @dkionline recommended (it includes also vendor?) - look once again please
All the other steps are okay

 

[rayman95]

Yes, at point 4 use Advanced Wipe and wipe only the Partitions which @dkionline recommended (it includes also vendor?) - look once again please
All the other steps are okay

2a. Wipe cust, data, vendor, version, product and system for clean flash

this is what he posted in his OP, so I will try this afternoon.....
many thank's
EDIT : No issues with that, perfect and clean flash...thanks again...

 

[spartan02sparte]

I can not install TWRP, I go back every time to huawei erecovery

EDIT : It's fixed

I changed the cable and everything worked