Bros!
I am in serious need of help right now.
I could not find the OTA patch for elite roms,so I wiped all the partitions available in twrp except internal storage.
Changed data to ext4.
Flashed stock recovery.img from twrp and proceeded to dload method, it gives an error on 5 percent.
Now i only have stock recovery and fastbooot.
I tried fastboot flashing different images eg recovery,twrp,system,vendor etc but they all give an error of "command not allowed".
(On fastboot screen,it shows: "phone unlocked" and "frp lock")
I tried some guide for solving this error which said to "fastboot oem relock *16 digit code*" but it also gives error : "root type is risk".
I had legend rom installed before starting all this.I wanted to go completely back to stock.But now i have bricked my device with a stock recovery and a fastboot which can apparently get no useful command to work.i have searched all the google for all the the different huawei devices but nothing is working.
Help me please!!!Any and help will be appreciated!!
Model before any moddingRA-LA1
Salman Farooq01 said:
Bros!
I am in serious need of help right now.
I could not find the OTA patch for elite roms,so I wiped all the partitions available in twrp except internal storage.
Changed data to ext4.
Flashed stock recovery.img from twrp and proceeded to dload method, it gives an error on 5 percent.
Now i only have stock recovery and fastbooot.
I tried fastboot flashing different images eg recovery,twrp,system,vendor etc but they all give an error of "command not allowed".
(On fastboot screen,it shows: "phone unlocked" and "frp lock")
I tried some guide for solving this error which said to "fastboot oem relock *16 digit code*" but it also gives error : "root type is risk".
I had legend rom installed before starting all this.I wanted to go completely back to stock.But now i have bricked my device with a stock recovery and a fastboot which can apparently get no useful command to work.i have searched all the google for all the the different huawei devices but nothing is working.
Help me please!!!Any and help will be appreciated!!
Model before any moddingRA-LA1
Click to expand...
Click to collapse
Are you able to flash TWRP?
@dmilz yes, unsuccessfully
Salman Farooq01 said:
@dmilz yes, unsuccessfully
Click to expand...
Click to collapse
What does it say when you
Fastboot flash recovery recovery.IMG
?
Rename TWRP to recovery ( according to my experience, I get error when recovery has other name)..
If that fails use firmware finder to download firmwares..try them all if possible..including different models of the same Honor (in case OEM changed)
dmilz said:
What does it say when you
Fastboot flash recovery recovery.IMG
?
Rename TWRP to recovery ( according to my experience, I get error when recovery has other name)..
If that fails use firmware finder to download firmwares..try them all if possible..including different models of the same Honor (in case OEM changed)
Click to expand...
Click to collapse
"Comman not allowed"
There are 3 files in available to download in ff.How to flash them ?
Related
Hi, my problem is with the L31,
I've trying to downgrade from Nougat to MM. I saw on the thread this steps and i followed:
"Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Then I flashed badwolfs recovery b2 as that one lets me transfer files from pc to phone and followed instructions from htcmania from here".
The problem is that i didn't reach to downgrade and when i try to reinstall Nougat by TWRP i get this error messages:
" E: Unknow comand (errno) update_huawei-pkg_from_ota_zip: update package from zip failed"
"Updater process ended with error: 7
Error installing zip file '/external_sd/DLoad/Update.zip'
Updating partition details...
...done"
Now my phone stays freeze on the huawei logo and the flashtool doesn't even recognize my device.
Can someone help me with this matter, please?
try to flash stock recovery and do a factory reset
simo255 said:
try to flash stock recovery and do a factory reset
Click to expand...
Click to collapse
Problem solved.:good:
aalmeida1972 said:
Problem solved.:good:
Click to expand...
Click to collapse
how did you flash a stock recovery please ???
darth_us37 said:
how did you flash a stock recovery please ???
Click to expand...
Click to collapse
I followed the steps that someone advice me. Like above.
"I had to first extract the nougat firmware with huawei firmare extractor and flash everything by fastboot
Fastboot flash boot boot.img
Fastboot flash system system.img
Fastboot flash cust cust.img (This one is in the second zip from badwolf nougat download)
Booth files you can find it in this page.
http://forum.xda-developers.com/huawei-p9lite/development/android-nougat-dev-build-huawei-t3488360/page33"
To flash img. i used the file that i attached.
Good luck
so now i restored twrp , i put the update app in sd card and it doesn't want to flash , i'm still trapped in bootloop but i have access to twrp now what to do now ?
I found the old twrp is okey for downgrade,
Just put b161 update.app into sdcard/dload and press volume down + power key.
but flash badwolf's twrp will get stuck in fastboot, though It's not really bricked.
hi, maybe you also have a solution for my problem.
i installed a wrong update via sd card (dload etc.), now my phone is just black no signal nothing. and it seems like a fastboot loop always when i plug into the pc im in fastboot without doing anything
when i try to unlock the bootloader i get "failed command not allowed")
and also when i try to flash the extracted files from update.zip i get the same error ("failed command not allowed")
by the way i didnt active usb debuggin or oem unlocking
please help thank you
Hello I have managed to brick my P9 lite with the nougat rom. I can only access bootloader, the phone is both oem and bootloader unlocked and currently it's on bootloop. I have tried the upgrade with 3 buttons pushed but I can't get the phone to accept the package(put in the dload folder on SDcard) it only shows 'install failed - Incompatibility with current version please download the correct package'. I have also tried the fastboot flash system command it went without errors but the only result is that it no longer bootloops and only shows black screen after the warning that I have unlocked bootloader. So is there anything else I should try? Thanks.
Fastboot??
Odoslané z VNS-L21 pomocou Tapatalku
Try this
@mrmajco
I don't understand what you mean. Could you give me some commands to use? If I flash recovery with fastboot I can't get into the recovery (nougat rom) and if I flash system with fastboot flash system I only see black screen and nothing boots up.
fastboot flash zip gives me FAILED command not allowed.
@zgomot
Well, either I'm really dumb or doing it wrong but once I flash the meticulus recovery with fastboot flash recovery recovery.img nothing really changes and I can't get into the recovery.
To flashing oem info I get FAILED (remote: command not allowed). I will post it here but I doubt it will be of any help.
IMAGE
edit: I really don't know how but I'm in the recovery so I think I will manage to flash the stock image from there and make it work. I will once I resolve the problem or brick it once more Thank you for the link.
I got a problem with mij P9 i mest up my system
i installed Nougat but wasnt happy without working bleutooth. I treid to do rollback but mest up my system
What happend; i took the howto rollback and downloaded the files i needed i took the oeminfo and flashed it, from that point on i tried to install recovery but nothing worked, i think i flashed the wrong oeminfo "L21" but my phone is a L31..
I can boot the phone, but i gives me a red warning message "Your device has failed verification and may not work properly"
I lost a lot off apps
I can boot Fastboot and bootloader is unlocked
i tried the folllowing to fix it
Flashed (all) recovery trough fastboot gives a "Failed" message (fastboot gives a lot of failes) but trough fastboot it says bootloader unlocked
I tried with 3 buttons an dload tot flash oeminfo but i get erecovery with message data damaged and i can choose to wipe all and install trough wifi but that dosnt work.
Ad this time im confused and i woud really like to get my system up and runnng like it supose to
So if someone could help me out i would be veryy thanfull
grtz
Maarten
maartenhordijk1978 said:
I got a problem with mij P9 i mest up my system
i installed Nougat but wasnt happy without working bleutooth. I treid to do rollback but mest up my system
What happend; i took the howto rollback and downloaded the files i needed i took the oeminfo and flashed it, from that point on i tried to install recovery but nothing worked, i think i flashed the wrong oeminfo "L21" but my phone is a L31..
I can boot the phone, but i gives me a red warning message "Your device has failed verification and may not work properly"
I lost a lot off apps
I can boot Fastboot and bootloader is unlocked
i tried the folllowing to fix it
Flashed (all) recovery trough fastboot gives a "Failed" message (fastboot gives a lot of failes) but trough fastboot it says bootloader unlocked
I tried with 3 buttons an dload tot flash oeminfo but i get erecovery with message data damaged and i can choose to wipe all and install trough wifi but that dosnt work.
Ad this time im confused and i woud really like to get my system up and runnng like it supose to
So if someone could help me out i would be veryy thanfull
grtz
Maarten
Click to expand...
Click to collapse
If your phone is VNS-L31C432, then try these methods:
1. In bootloader "fastboot boot TWRP_Recovery.img"
this should boot you into twrp without flashing it, from there flash B161_update.zip (which should be in your SD card).
(If that doesn't work, try "fastboot -c "lge.kcal=0|0|0|x" boot TWRP_Recovery.img"
haven't tried this on P9 Lite, but used to work on other phones).
2. If "fastboot flash recovery TWRP_Recovery.img" returns errors, but says bootloader unlocked, try to relock the bootloader and unlock it again.
"fastboot oem lock"
"fastboot oem unlock YOUR_CODE"
then try flashing recovery again.
Maybe also try flashing other recoveries, e.g. TWRP (which is for MM ROMs) or Revolution (which is for N ROMs) or even the stock boot.img.
3. Try the dload method wth B161 and maybe B160 - I know my P9 Lite would only accept B161 via dload, even though B370 and B360 and B130 are for the same model, those builds just wouldn't install this way.
4. Unpack B161 zip so you have update.app, extract from that boot.img, recovery.img and system.img.
Then do:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Some of these methods might work, some won't but from my two experiences of bricking the P9 Lite, one of the four fixed the issue.
If you don't know where to get the B161 zips, I can post them later.
Also, this is just to get your system to a working and bootable condition. If you want to get back to full-fledged MM, you will also need to install the hw_eu zip after the B161 zip (and maybe do a factory reset after that for the sake of it).
Your apps and files are already gone, so no way to save that. Hope your phone gets back to working order soon enough.
JHD94 said:
If your phone is VNS-L31C432, then try these methods:
1. In bootloader "fastboot boot TWRP_Recovery.img"
this should boot you into twrp without flashing it, from there flash B161_update.zip (which should be in your SD card).
(If that doesn't work, try "fastboot -c "lge.kcal=0|0|0|x" boot TWRP_Recovery.img"
haven't tried this on P9 Lite, but used to work on other phones).
2. If "fastboot flash recovery TWRP_Recovery.img" returns errors, but says bootloader unlocked, try to relock the bootloader and unlock it again.
"fastboot oem lock"
"fastboot oem unlock YOUR_CODE"
then try flashing recovery again.
Maybe also try flashing other recoveries, e.g. TWRP (which is for MM ROMs) or Revolution (which is for N ROMs) or even the stock boot.img.
3. Try the dload method wth B161 and maybe B160 - I know my P9 Lite would only accept B161 via dload, even though B370 and B360 and B130 are for the same model, those builds just wouldn't install this way.
4. Unpack B161 zip so you have update.app, extract from that boot.img, recovery.img and system.img.
Then do:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Some of these methods might work, some won't but from my two experiences of bricking the P9 Lite, one of the four fixed the issue.
If you don't know where to get the B161 zips, I can post them later.
Also, this is just to get your system to a working and bootable condition. If you want to get back to full-fledged MM, you will also need to install the hw_eu zip after the B161 zip (and maybe do a factory reset after that for the sake of it).
Your apps and files are already gone, so no way to save that. Hope your phone gets back to working order soon enough.
Click to expand...
Click to collapse
Thnx mate ill try tommorow and let you know how it went. For now its sleepy time
JHD94 said:
If your phone is VNS-L31C432, then try these methods:
1. In bootloader "fastboot boot TWRP_Recovery.img"
this should boot you into twrp without flashing it, from there flash B161_update.zip (which should be in your SD card).
(If that doesn't work, try "fastboot -c "lge.kcal=0|0|0|x" boot TWRP_Recovery.img"
haven't tried this on P9 Lite, but used to work on other phones).
2. If "fastboot flash recovery TWRP_Recovery.img" returns errors, but says bootloader unlocked, try to relock the bootloader and unlock it again.
"fastboot oem lock"
"fastboot oem unlock YOUR_CODE"
then try flashing recovery again.
Maybe also try flashing other recoveries, e.g. TWRP (which is for MM ROMs) or Revolution (which is for N ROMs) or even the stock boot.img.
3. Try the dload method wth B161 and maybe B160 - I know my P9 Lite would only accept B161 via dload, even though B370 and B360 and B130 are for the same model, those builds just wouldn't install this way.
4. Unpack B161 zip so you have update.app, extract from that boot.img, recovery.img and system.img.
Then do:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Some of these methods might work, some won't but from my two experiences of bricking the P9 Lite, one of the four fixed the issue.
If you don't know where to get the B161 zips, I can post them later.
Also, this is just to get your system to a working and bootable condition. If you want to get back to full-fledged MM, you will also need to install the hw_eu zip after the B161 zip (and maybe do a factory reset after that for the sake of it).
Your apps and files are already gone, so no way to save that. Hope your phone gets back to working order soon enough.
Click to expand...
Click to collapse
thnx mate unlcoked the phone again and got into twrp happy me!!!
Follow Guide 1 from this link - https://forum.xda-developers.com/huawei-p9lite/help/unbricking-vns-l21-vns-l31-tutorial-t3583400
B130 is the perfect stock MM ROM
Hi I have a similar problem
JHD94 said:
If your phone is VNS-L31C432, then try these methods:
1. In bootloader "fastboot boot TWRP_Recovery.img"
this should boot you into twrp without flashing it, from there flash B161_update.zip (which should be in your SD card).
(If that doesn't work, try "fastboot -c "lge.kcal=0|0|0|x" boot TWRP_Recovery.img"
haven't tried this on P9 Lite, but used to work on other phones).
2. If "fastboot flash recovery TWRP_Recovery.img" returns errors, but says bootloader unlocked, try to relock the bootloader and unlock it again.
"fastboot oem lock"
"fastboot oem unlock YOUR_CODE"
then try flashing recovery again.
Maybe also try flashing other recoveries, e.g. TWRP (which is for MM ROMs) or Revolution (which is for N ROMs) or even the stock boot.img.
3. Try the dload method wth B161 and maybe B160 - I know my P9 Lite would only accept B161 via dload, even though B370 and B360 and B130 are for the same model, those builds just wouldn't install this way.
4. Unpack B161 zip so you have update.app, extract from that boot.img, recovery.img and system.img.
Then do:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Some of these methods might work, some won't but from my two experiences of bricking the P9 Lite, one of the four fixed the issue.
If you don't know where to get the B161 zips, I can post them later.
Also, this is just to get your system to a working and bootable condition. If you want to get back to full-fledged MM, you will also need to install the hw_eu zip after the B161 zip (and maybe do a factory reset after that for the sake of it).
Your apps and files are already gone, so no way to save that. Hope your phone gets back to working order soon enough.
Click to expand...
Click to collapse
Hi I have a similar problem, I know you are all busy, but please help me out. My phone(P9 Lite) L31C16 emui4.1 but I installed a firmware of L31C169 emui5.0, now I'm stuck with andriod 7 which doesn't function perfectly and I'm stuck with a boot error of "Your device has failed verification and may not work properly". Please help me out.
Hello mates!
Yesterday I accidentally bricked my phone and I spent ours and ours on this and others forums to find solution but without succes, so here is what was happen:
I was on L21C432B380 firmware, stock, bootloader locked, without root acces. So I tried to flash ROM 7.1.2 AOSP by Meticulus. I followed step by step guide. I succesfully unlocked bootloader using fastboot. Then I flashed TWRP again using fastboot so I can downgrade to EMUI 4.X and that was succesfull also. After that I flashed oem-info using TWRP and flashed stock UPDATE.ZIP using three button method, both succesfully but when phone tried to boots up It shows message "No OS installed".
My entire system and data was deleted, there is no recovery, bootloader is again locked, I have only managed to get into fastboot mode using adb
Every single command I tryed to run in cmd results in this message: "FAILED (remote: Command not allowed)
Somehow I need to install Firmware using fastboot but don't know how cause bootloader is again locked
My knowledge about this things is above average but I cannot "google" the problem
Please help and thanks in adavnce
Tomislav Veličanstveni said:
Hello mates!
Yesterday I accidentally bricked my phone and I spent ours and ours on this and others forums to find solution but without succes, so here is what was happen:
I was on L21C432B380 firmware, stock, bootloader locked, without root acces. So I tried to flash ROM 7.1.2 AOSP by Meticulus. I followed step by step guide. I succesfully unlocked bootloader using fastboot. Then I flashed TWRP again using fastboot so I can downgrade to EMUI 4.X and that was succesfull also. After that I flashed oem-info using TWRP and flashed stock UPDATE.ZIP using three button method, both succesfully but when phone tried to boots up It shows message "No OS installed".
My entire system and data was deleted, there is no recovery, bootloader is again locked, I have only managed to get into fastboot mode using adb
Every single command I tryed to run in cmd results in this message: "FAILED (remote: Command not allowed)
Somehow I need to install Firmware using fastboot but don't know how cause bootloader is again locked
My knowledge about this things is above average but I cannot "google" the problem
Please help and thanks in adavnce
Click to expand...
Click to collapse
Hello man,
Dont know why u do that (downgrade to MM)...
Explicitly written for flash AOSP 7.1.2 to be on emui5 (were u was)...
Flashing oem also relocked your bootloader (written ton of times in threads)....
Now using fastboot re-unlock bootloader re-flash TWRP.
If u maked a full backup just use it, otherwise try to follow this guide..
https://forum.xda-developers.com/showpost.php?p=73619842&postcount=44
Hope u will resolve.
Regards
To summarize, I have a Moto G5 Plus, with locked bootloader and I decided to update a ROM STOCK and made a simple mistake by forgetting the OEM unlock option in advance in the configuration menu. An error occurred on the way and tried to return to the stock. Now, when the phone boots up, it enters the boot loader (which is locked) and displays a startup error message that states that you must use the Software Repair Wizard.
trying to enter the recovery gives a code:
AP Fastboot Flash Mode [Secure]
Fastboot Reason: UTAG "bootmode" configured as fastboot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Boot up failed
Is there a known solution or force a recovery to work?
Thanks to all
Hello;
I found the solution, download the latest firmware from your cell phone, download it just unzip the zip and look for the files: gpt.bin and bootloader.img, those 2 ctrl + c and files go to the folder where they downloaded ADB tools and paste the files there , then execute the steps to open command window here and execute the following:
fastboot flash partitiongpt.bin
fastboot bootloader bootloader.img
fastboot reboot-bootloader
and it is ready to install the downloaded rom.
Gracias a AndresBRS https://www.clangsm.com/forum/index.php?showtopic=466891
Same problem with moto g5s plus xt1804
After flashing it shows failed to start ..failed to boot recovery and when I am trying to unlock bootloader it shows unlock data unavailable
beyondsunshine92 said:
After flashing it shows failed to start ..failed to boot recovery and when I am trying to unlock bootloader it shows unlock data unavailable
Click to expand...
Click to collapse
Install lenovo moto smart assistant in pc and go for rescue and flash the whole firmware.if your device is not supported then flash manually.
Moto smart assistant shows device not supported however I tried many fastboot stock roms but every time I get error invalid signed image. .ph stuck in fastboot
beyondsunshine92 said:
Moto smart assistant shows device not supported however I tried many fastboot stock roms but every time I get error invalid signed image. .ph stuck in fastboot
Click to expand...
Click to collapse
Download the firmware from here and then flash.
https://mirrors.lolinet.com/firmware/moto/potter/official/
riyan65 said:
Download the firmware from here and then flash.
@beyondsunshine92: Did you tried this? Is it working? I am also having the same issue. Please help guys
Click to expand...
Click to collapse