I have flashed Rollback package and stuck in bootlogo.
I can boot only in Fastboot mode but i cannot flash anything.
Message says FAILED (remote: Command not allowed)
How i will recover this device ?
Device is VNS-L31
mahmutelmas06 said:
I have flashed Rollback package and stuck in bootlogo.
I can boot only in Fastboot mode but i cannot flash anything.
Message says FAILED (remote: Command not allowed)
How i will recover this device ?
Device is VNS-L31
Click to expand...
Click to collapse
Hello,
take a look at the UNIFIED HELP THREAD,
post#6 ---- UNBRICKING AND DOWNGRADING FROM EMUI 5
where it is well explained how to use the rollback package.
You need the marshmallow version of your ROM stock.
Ex: VNS-L31 Rollback Package + VNS-L31 (C432 or C185 or others) B160 / 1,
depends on whether dual or single SIM or others available for your CUST / Region (C432 or others).
Follow the procedure carefully ...
Cheers
Related
Is there somehow I can RE-lock the bootloader, UN-root my mate 8 - L09 and reset everything like it was when it was new?
edit:
This is what I have done until now.
- flashed to stock recovery (phone is not rooted any more)
- factory reset
Then when I try to relock the the bootloader , I get message FAILED (remote: root type is risk)
fastboot oem relock ****************
...
FAILED (remote: root type is risk)
finished. total time: 0.970s
Someone know how to resolve this issue?
Could this be fixed by installing fresh and untouched complete firmware from huawei?
If yes, some know which link to use for my device and version?
Model number: HUAWEI NXT-L09
Buld number: NXT-L09C432B152
All help is highly apprechiated.
Can someone please delete this thread - I created a new thread in the troubleshooting section.
http://forum.xda-developers.com/mate-8/help/problem-lock-bootloader-remote-root-t3363216
Hey,
i had some issues with Nougat so i decided to wipe everything via Revolution Recovery and reinstall MM
but i got some errors..
via Revolution Recovery:
Error: 7
via Fastboot:
target reported max download size of 471859200 bytes
sending sparse ´system´ 1/6 <451240 KB>...
OKAY [11.546s]
writing ´system´ 1/6...
FAILED <remote: sparse flash write failure>
finished. total time: 11.582s
P9 Lite VNS-L31
Bootloader is unlocked
Please help me i have no idea what to do
You shoud NEVER do wipe via twrp on Nougat!
Now try to flash compatible Oeminfo first and have in dload folder a B160/B161 stock firmware
and make repair via 3 keys pressed.
p9litesol said:
can you tell me how to flash oeminfo? i have only access to twrp and fastboot
Click to expand...
Click to collapse
Attach is a zip twrp flashable for VNS-L21 DS C432.
Probably works for L31 too...
I flashed the oeminfo.
Now i am stuck on the logoscreen and i cant even boot to recovery.
Edit:
Probably wrong oeminfo ver.
I fixed it but i cant find a flashable oeminfo vers. for VNS-L31.
Found a ver. for fastboot but when i try to flash it i get this error:
FAILED <remote: Command not allowed>
i tried different versions of oeminfo but when i flash it i get stuck on the logo screen.
Can someone upload a backupfile for me?
Solved! Bought an Oneplus 3t
Hello, and I have mist built yesterday with my Huawei P8 Lite ALE-21 dual Sim.
I wanted to play this Rome yesterday
https://forum.xda-developers.com/showpost.php?p=73230358&postcount=2 b895_update.zip
This did not work and made a mistake.
After that, I re-imported the original ROM without any problems.
After all it was again, I booted into the bootloader / fastboot synonymous but works
as soon as I now the recovery (fastboot flash recovery recovery.img)
I always get the following message.
target reported max download size of 471859200 bytes
sending ´recovery´ (25152kb)...
OKAY [ 0,797s]
writing ´recovery´...
FAILED (remote: Command not allowed)
finished. total time: 0.797s
The bootloader / fastboot is unlocked.
Did I shoot this now?
What could I do about it because the Huawei site where you get
the bootloader unlock code did not work anymore in Germany!!
Would appreciate a response or help very much.
Sorry for the bad english, i have translated with google
EDIT: it work again!
same issue
Hi I have the exact same issue with my Huawei p8 lite I can only go into fast boot mode but it says Phone locked and all my commands give me the exact same error Failed (remote:command not allowed ) and advice for me ? Thank you
Unlock the bootloader again (fastboot oem unlock <code>) and try again
Stucked at rescue mode
says this
Code:
RESCUE MODE
Attention!
Please update system again
Update user guide:
link from emotion download
*android error droid image*
Error!
Func NO : 9 (dsp image)
Error NO : 1 (security verify failed!)
I already make a folder called dload in my sd whit my UPDATE.APP but i cant restore my phone
I already extracted the update.app with the huawei extractor and tried flash system cust boot recovery recovery2
I tried too flash dsp.img
Code:
C:\adb>fastboot flash dsp dsp.img
Sending 'dsp' (2190 KB) OKAY [ 0.187s]
Writing 'dsp'
FAILED (remote: Command not allowed)
Finished. Total time: 0.218s
I tried too with mfastboot but nothing I tried unlocking oem but says is already unlocked and relocking says this
Code:
C:\adb>fastboot oem relock *****my number*********
FAILED (remote: root type is risk)
Finished. Total time: 0.062s
i try too flashing diferents version of twrp for my phone but still cant access to recovery
i think i got this error trying to change my data to f2fs and install MorfuZ V3.4 and i don't know what i do my last hope is this forum
pls help i need this phone for work :crying:
Im in a cam-l03 fastboot says this
Code:
Fastboot&Rescue Mode
Please Connect Usb Cable to
Your Computer and Open Hisuite(don't work)
More Information:
emotiondownloadlink
volumnkey_down_press_process_func (don't know why says this)
Phone Unlocked (bootloader already unlocked)
FRP Unlocked
To force an update, you also need to hold vol+ vol- and power button with update.app in dload folder on your microsd card.
Sent from my LG-K220 using XDA Labs
Botar230 said:
To force an update, you also need to hold vol+ vol- and power button with update.app in dload folder on your microsd card.
Sent from my LG-K220 using XDA Labs
Click to expand...
Click to collapse
yes i already do this too but i can't exit from rescue mode only i can go to fastboot now im trying with a another microsd idk if is because i can't find the correct firmwere
i already see you in other post and i try this
If your phone still boots in rescue mode, then I think the rom you've flashed is not compatible with your phone. As @up said, try to force an update.
Sent from my LG-K220 using XDA Labs
Click to expand...
Click to collapse
im trying to force and update.app but its does nothing
I'm trying to root my Huawei P8 Lite 2017 PRA-LX1 (running on EMUI 5.0.3 Android 7.0). But I'm getting stuck :
My BootLoader is unlock, but my FRP is locked when I access the fastboot mode.
The option Allow OEM unlock is turned off and greyed out in the dev settings.
It prevents me from doing any command with fastboot, except "fastboot devices" and "fastboot oem get-bootinfo". All other commands return me :
Code:
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
I'm worried cause it looks like I no longer have a recovery img : when I boot with Vol UP + Power, I got a screen with the Android guy saying :
Code:
ERROR MODE
Attention !
Please Update system again
Error
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Each time I boot, I have a black screen with white and yellow writtings saying
"your devices has been unlocked and cannot be trusted"
From there I can boot normaly to the standard OS (EMUI 5.0.3 ; Android 7.0).
I can also enter the eRecovery mode to download latest version and recovery. But it fails and say "Getting package info failed".
When I try the factory reset from the settings, I get the same error as the one I got when trying to access the recovery more :
Code:
ERROR MODE
Attention !
Please Update system again
Error
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
To get to this situation, I tried to follow this guide :
[GUIDE] Unlock bootloader, root the device and install any custom ROM! (ALE-L23/21)
Hi all! So, you have a P8 lite in your pocket and you hate EMUI? Well, that was my case too, it's uncustomizable, ugly, and removes plenty of features from android stock. I do not like it one bit, and I like even less the fact that this phone is...
forum.xda-developers.com
I was not able to flash any OS with the dload/ procedure.
So I followed this guide :
[UPDATED GUIDE] [BOOTLOADER UNLOCK] Huawei p8 lite 2017 (pra-lx1)
This guide is the only one made and tested personally by me, I am not responsible for malfunctions or any damage to the device, carefully read every single step and everything will be successful [ATTENTION]: Before proceeding, save all your...
forum.xda-developers.com
and was able to correctly unlock my bootloader.
Then, I got back to the first guide to Install TWRP. The command fastboot flash recovery was working well :
Code:
$ fastboot flash recovery twrp-3.6.2_9-0-prague.img
Sending 'recovery' (14998 KB) OKAY [ 0.430s]
Writing 'recovery' OKAY [ 0.370s]
Finished. Total time: 0.828s
But I never managed to enter the TWRP recovery.
The Vol UP + Power reboot was getting me the eRecovery mode (to install the standard OS).
I tried to enter TWRP with fastboot :
Code:
$ fastboot boot twrp-3.6.2_9-0-prague.img
Sending 'boot.img' (14998 KB) OKAY [ 0.420s]
Booting FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Trying to solve this situation have made the things worse and worse.
I would like to follow this tutorial
[Solution]BL unlocked&FRP Locked-Fastboot FAILED (remote: Command not allowed)
Note: THIS IS NOT A SOLUTION TO BYPASS FRP! I am not responsible if you are dumb dumb and break your phone This Solution is written in under 10 minutes AND WORKS ONLY AND ONLY FOR STOCK people with no experience stay away This is not a...
forum.xda-developers.com
but since I cannot do a factory reset (first step tutorial) and I don't have a recovery img working, I'm a bit timorous.
Do you think I can upgrade my OS (from my OS settings menu) without a recovery img ? Will that solve the issue with my recovery img ?
Any thoughts on the situation would be much appreciated.
Thanks for reading me !