Need help REMOTE COMMAND NOT ALLOWED (Can't go back to stock) - Huawei P9 Questions & Answers

I have an L19C900B220 origanally C185, I tried changing the cust and got stuck on C900, and I also lost root access for some reason, so I tried to reboot to TWRP but it would just take me back to huawei recovery, so I went on SRK and tried to reflash TWRP and it gave me an error (Remote command not allowed) I tried to relock the bootloader same error, I tried to flash the revcovery.img through adb and got the same error, and I checked that OEM unlock was turned on, any ideas? Also DLOAD method gives me something along the lines of your deivce isn't compatible with this software or something
EDIT: NOW ON TWRP 3.1.0-0 can't mount data or system, can't do a data format either, don't know where to go from here, also lost access to use my phone so need an urgent fix, found out I'm still on NRD90M test-keys firmware
EDIT: Flashed recovery and boot, tried to flash system.img it said it worked in SRK, but my phone would be stuck on the bootloader warning screen

From where did you download your firmware? Use official website to download for right and not corrupted firmware.

kyle_2103 said:
I have an L19C900B220 origanally C185, I tried changing the cust and got stuck on C900, and I also lost root access for some reason, so I tried to reboot to TWRP but it would just take me back to huawei recovery, so I went on SRK and tried to reflash TWRP and it gave me an error (Remote command not allowed) I tried to relock the bootloader same error, I tried to flash the revcovery.img through adb and got the same error, and I checked that OEM unlock was turned on, any ideas? Also DLOAD method gives me something along the lines of your deivce isn't compatible with this software or something
Click to expand...
Click to collapse
I had the same issue, I had to use DC Phoenix to restore mine, which was a total pain

Related

Forced recovery stuck at 5%

Hey all. I was trying to rollback my P9 to a stock ROM, but it failed and now I am stuck with a bricked P9 (bootloop).
My phone is a European P9 (EVA-L09C432). I have an unlocked bootloader.
- Huawei eRecovery and HiSuite restore does not work.
- I've tried forcing the update using the SRK Tool brick utility, but receive the message "FAILED (remote: sparse flash write failure)" when it's strats writing 'system'.
- My TWRP backup does not work, I had a 7GB backup that installs fine, but the phone is still stuck in a bootloop.
- I can flash EVA-L09C432B378 ROM using the SRK brick utility fine, but the phone is still stuck in a bootloop.
- After I have installed B378 and try to force flash B136 using the dload method, it either gets stuck on the "going into restore mode" or it goes to the "installing package" screen, where it is stuck at 5% until it reboots.
Any suggestions?
try one more time install rollback package by download mode
I've tried. Several times, all day :crying: My process:
Write TWRP from fastboot so I can boot into TWRP and transer UPDATE.app to the dload folder
Reboot into fastboot
Write stock recovery image from fastboot
Boot into recovery mode
Get stuck at 5% on the "Installing update" screen.
I've tried the UPDATE.app or firmware B136 (stock), and UPDATE.app for B378 (Nougat)
Both get stuck at 5%.
I'm stuck at the bootloop
isn't srk tool only for MM?
maybe try extract recovery , boot and system partition from b378 and flash by fastboot , next start flash rollback package by download mode
I noticed when I tried to restore my backup using TWRP it failed at "vendor" (Failed to wipe vendor). I receive this issue at vendor and product.
I tried using fastboot to flash vendor and product manually, I receive these error messages:
"failed: remote command not allowed"
The phone won't allow me to write vendor and product.img... but my bootloader was unlocked?
Is it possible I could have relocked my bootloader? How am I supposed to get the bootloader code for my P9 again :/ It's nearly impossible.
I managed to use the recovery dload method to install a beta version of B378 (build number NRD90M test-keys). Will now try to use the recovery method to roll back to B136 and update back to B378 again.
Highfall said:
I managed to use the recovery dload method to install a beta version of B378 (build number NRD90M test-keys). Will now try to use the recovery method to roll back to B136 and update back to B378 again.
Click to expand...
Click to collapse
I'm having similar issues. Have you solved your problem? What have you tried so far?
Same problem here! Did you resolve?
Thanks you.
Try unplug charger or usb cable then do it
WTF, that ist the solution to the whole damn problem! Just unplugging the damn usb cable and it installs the update just fine. ive spend 2 whole days on this, almost giving it up beacuse everytime it got stuck at 5% and then this...
seriously thank you!
JimmyEatFood said:
Try unplug charger or usb cable then do it
Click to expand...
Click to collapse
thx i managed to boot my device, but i relocked bootloader and factory reset doesnt work correctly it deleted 3rd party apps and leaved few system apps and blotware. what should i do.
and really thanks, you saved me.
Removing cabled worked for me also

twrp on p9 problem

Hello everyone, I wanted to revert to stock from bluewei, i flashed stock rom via dload method, but now it just bootloops. so i wanted to install twrp again so i can flash stock through twrp or atleast flash bluewei again but every time i try to flash with fastboot flash recovery command it says "remote: command not allowed", even tho i have my bootloader unlocked (everytime i turn on my phone it shows the warning that it is unlocked).
now i cant install twrp, cant flash through hisuite (it says that my device is not supported, tried the trick with changing ip address and port, nothing) and i dont have a idea how to make my phone useful again
Please can someone help me? THANKS!
p.s. device is p9 L09

Unable to boot images via Fastboot

Hi,
Recently I updated my EMUI firmware via the official OTA system.
I had the bootloader unlocked prior to installing the update however afterwards the bootloader was locked. I have verified this in Fastboot.
I wish to flash Magisk on my P9 Plus, however, I have a bootloader unlock code (back when Huawei gave them out freely) however I don't want to unlock the bootloader as it will factory reset (I spent a long time setting everything up).
I tried flashing a TWRP image however the bootloader prevents it as it is not unlocked.
The only other method would to boot the custom recovery image however when executing fastboot boot recovery TWRP twrp-3.1.1-1-vie.img it gives FAILED (remote: Command not allowed). I had noticed this inability to boot images even when I had the bootloader unlocked (I did not want to overwrite the stock recovery or eRecovery for easier OTA updates).
I have the Chinese variant of the P9 Plus : VIE-AL10 Full Netcom Edition.
Is anyone else having this problem? Please let me know if or how to fix this.
Thanks
It's been a while since I last used fastboot boot but if i remember correctly the command is "fastboot boot recovey.img, without that" recovery" in between
if the bootloader is locked you cant flash magisk or any other, also you cant boot with any images

can't unlock bootloader critical and other things..

ok guys so my dad has bricked his nokia .8.. i managed to get Twrp working again. and that's about it.. the bootloader is unlocked but i cant can't unlock "bootloader critical" it says something like " (remote command not allowed)" when i check the device info it says bootloader is unlocked but bootloader critical is not.. iv tried flashing via the ost but it says i need to unlock the critical bootloader..
another problem is that i cant flash in twrp. it says invalid zip file or something...
has anyone got a Twrp Backup they could upload so i can try and get this thing working again? or a zip i can flash via twrp?
cheers.
Did you do "fastboot flash unlock <path to unlock.key>" before trying to execute "fastboot oem unlock_critical"?
Did you maybe have an unlock key that was generated through the unofficial unlock (every build before august 2018) and are now on a newer build that supports only the official unlock?
If you can't manage to unlock the bootloader to critical, get some stock boot image (I have some at https://bit.ly/nokia-nb1), flash that to your active boot partition in fastboot (overwrite TWRP with it), then boot into stock recovery and sideload a full OTA package (which will restore all partitions that might be corrupted). All 1.5 GB files you can see in the OTA folder at the link I posted are full OTAs and will work.
ok so just an update i managed to get a rom on there, i found the right key and did the unlock all over again.. all booted ok, problem now is that i have no signal... i cant send any mssgs or phone calls. i tired to update the smsc. via this *#*#4636#*#*. and going phone info etc, but it says update error, iv also tried the encoded number for ee, but still says update error. i can put the sim card into another phone and it will send messages etc, i did read that i could update the smsc on a diffrent phone then put it back into the nokia and it will work, but it did not for me...
again there was another video showing how to fix this via backing up the firmware folder on rom then replacing with the one that dose not work . but ... i dont have a rom that works lol . iv also tried to install diffrent roms or systems and still the same problem.. i use the NOST tool. to update the firmware
any advice????
also this is his account hence a diffrent account name lol
cheers

P9 Plus not booting after flashing twrp backup

Hi i have this p9 plus vie-l29, i unlocked the bootloader, installed twrp and root, everything worked perfect until i found a backup online and restore it using twrp. Since then, P9 shows "device has failed verification and may not work properly".
I boot to erecovery, but i got this error: "getting package info failed", I tried to flash again twrp from fastboot and resccue mode, but not working because i did a factory reset and cannot activate usb debugging. It still has stock recovery but I only have 3 options, reboot, clear cache and factory data reset.
Can you give me a solution to this please? If i try dload method from sdcard, should work?
UPDATE: So, I tried dload method, did not worked for me. Now phone is in service center, I hope it can be fixed.

Categories

Resources