[TWRP][P9][3.1.1-1][EMUI 5.x/AOSP N][DECRYPTION SUPPORT]
- Thread starter OldDroid
- Start date
Is it possible to make a backup while you're using external microSD as internal storage? (the microSD is formatted as internal memory and encrypted this way, that's why i'm wondering), it seems a bit weird to me
Last edited:
l09 c432
b386 (upgraded, factory reset, everything looks and Works fine, no missing aps or so)
Bootloader has been unlocked two months ago, I was always able to flash versions of TWRP 3.1.0
When booting it correctly displays "Your phone has been unlocked and can't be trusted".
In fastboot mode it also shows in red "Phone unlocked".
However, flashing of TWRP now fails, telling that remote command is not allowed:
C:\adb>adb devices
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
MWS0216729010044 device
C:\adb>adb reboot-bootloader
C:\adb>fastboot devices
MWS0216729010044 fastboot
C:\adb>fastboot flash recovery twrp-3.1.0-3-eva.img
target reported max download size of 471859200 bytes
sending 'recovery' (25234 KB)...
OKAY [ 0.827s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.858s
b386 (upgraded, factory reset, everything looks and Works fine, no missing aps or so)
Bootloader has been unlocked two months ago, I was always able to flash versions of TWRP 3.1.0
When booting it correctly displays "Your phone has been unlocked and can't be trusted".
In fastboot mode it also shows in red "Phone unlocked".
However, flashing of TWRP now fails, telling that remote command is not allowed:
C:\adb>adb devices
List of devices attached
adb server is out of date. killing...
* daemon started successfully *
MWS0216729010044 device
C:\adb>adb reboot-bootloader
C:\adb>fastboot devices
MWS0216729010044 fastboot
C:\adb>fastboot flash recovery twrp-3.1.0-3-eva.img
target reported max download size of 471859200 bytes
sending 'recovery' (25234 KB)...
OKAY [ 0.827s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.858s
Last edited:
Its like locked, but BL is always unlocked on N until you relock. How did you upgraded it?
I was on Magic Rainbow (prerooted and modded b383) but I had full Nandroid backup of the clean, original b383, made from TWRP 3.1.0-1 or 3.1.0-2.
In TWRP 3.1.0-3 I did:
- wiped Cache and Dalwik
- restored full Nandroid backup of the original b383
then booted to b383 and double-checked: stock bloatware apps were there, no more custom Magic Rainbow apps.
Again from TWRP 3.1.0-3 I did:
- wiped Cache and Dalwik
- installed update.zip and update_data_full_EVA-L09_hw_eu.zip from FullOTA-MF-PV b386
booted to b383 and made Factory Reset.
Everything looks ok, Contacts and Themes present, etc.
As described in the previus post #406, on booting phone displays "Your phone has been unlocked and can't be trusted" and in fastboot mode it shows "Phone unlocked", but fastboot flashing of TWRP fails with "remote Command not allowed".
In Settings, Development mode, "OEM unlocking" is anavailable/grayed out (with radio button off), but I think it was also that way when I upgraded to b383 and when I was successfully flashing TWRP 3.1.0-1 (a month ago)
works absolutely fine - especially since it is the only version that actually works in the first place with Magisk for our device but you must be on ROM version B380 and above as stated in OP.
please read the threads fully before posting a question as most often than not it has already been answered
Last edited:
I don't get why every tutorial is the same but nothing works in my case. I didn't let anything out and I'm sure I didnt overlooked something.
Magisk I don't know.
Hey...i just wanna be sure. Right now i'm on EVA-L19C636B381 and have twrp 3.1.0.2 with a modified SU install right now. What do i do from here to install twrp 3.1.0.3 and magisk without messing up. i have kernal adiutor also to change some settings. Step by step would help .
Thank you
Thank you
Last edited:
More also in the post: https://forum.xda-developers.com/showpost.php?p=72291583&postcount=408
I've also checked by fastboot oem device-info, it also reports failure, command not allowed.
Any idea, help please?
Have you enabled ADB Debugging in Developer options together with USB Debugging?
Another command for checking Bootloader in fastboot mode is: fastboot oem get-bootinfo
Maybe Bootloader is closed and Bootloader Screen shows wrong information..
Have you tried unlock Bootloader again?
If you use Minimal ADB and Fastboot program on PC be sure you execute it with Administrator Permission.
Last edited:
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
Last edited:
I suggest to try flashing the TWRP-3.1.0-3 via TWRP that is already installed on your device and tell us if it is working.
No TWRP is installed anymore (upgraded to b386 and Factory Reset, only eRecovery is installed) - I wouldnt bug you if I had TWRP
As already wrote, tried all three IMGs -1,-2 and -3, same failure. It's not in IMG, but bootloader saying it's still unlocked but not allowing to flash TWRP
Last edited:
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.
Last edited:
Dont do factory reset, that can cause bugs. Only way is downgrade and upgrade again.
New posts
-
[ROM][Unofficial][9.0.0][signed]LineageOS 16.0 for Osprey
- Latest: alanthelinuxguy
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone