Related
Hello I'm trying to flash stock ROM via adb, specifically cust.img, boot.img, system.img, Because I've bricked my phone and it stuck on huawei logo, but when i try to flash, i got the following error "FAILED (remote: Command not allowed)"
Code:
C:\adb>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (304183 KB)...
OKAY [195.875s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 195.899s
c:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (21690 KB)...
OKAY [ 13.671s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.694s
c:\adb>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460798 KB)...
OKAY [314.622s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 314.665s
Please how I can unbrick my phone and reinstall the firmware
Obs. My bootloader is unlocked and I'm using TWRP recovery
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens.
In later days, we've got a lot of troubleshooting topic opened up with your problem, the users cannot flash even with unlocked bootloader, and yet, there's no real solution to them.
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
daviddosa said:
Is your phone really shows Unlocked in red color when it's in fastboot mode?
Was your phone rooted, if yes, with which method?
You should try doing:
fastboot erase cache
fastboot erase userdata
These commands perform the same thing as Factory Reset do.
If it's not working, try to do the "dload" method with your original firmware your phone was shipped with.
Create a folder, called "dload" in your sdcard root, put the UPDATE.APP file of the firmware in it, and without connecting it to PC, press Vol + and Vol - and Power button until it starts flashing the firmware, and see what happens..
Click to expand...
Click to collapse
Yes, it shows PHONE unlocked in red name, and I've made the root using an app called kingroot
I've tried to erase cache and userdata using adb but I can't, still got the same error "FAILED (remote: Command not allowed)"
I can't make dload method because I don't have stock recovery, and I can't flash the stock recovery using adb because its keep saying "FAILED (remote: Command not allowed)".
I don't know what to do
sokkoban said:
I suggest that you use Windows 10? If I'm right sometimes this version of Windows cannot be used to flash via adb
I recommend you to use Windows 8.1 or 7 . My best way is of course using Linux
Click to expand...
Click to collapse
I'm using windows 7 is this moment, maybe I try to flash using Linux later
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
daviddosa said:
Seems like all the guys with the same problem used KingRoot to root...that is the common thing amongst all.
I dont't think you need the stock recovery to update via the "dload" method, but I'm not sure.
If you don't have your original firmware's UPDATE.APP yet, download it, as well as the Huawei Update Extractor.
Load your file into the program, select ONLY BOOT.IMG, CUST.IMG(if it has one), SYSTEM.IMG and RECOVERY.IMG(optional, if selected, restores original recovery) right click on one, and press Create Flashable Zip.
Copy this to your sdcard and try to flash it.
I did not thest this above method, and don't know it the created flashable zip is really flashable, but I'm running out of possible solutions slowly.
Let us know what happens.
Click to expand...
Click to collapse
So I tried to create a flashable zip using the Huawei Update Extractor however, was not possible, it's showing the following message "no suitable files selected. Check profiles.xml"
I've tried also creating flashable zip manually and flash it using TWRP, but TWRP reboot every time I try to flash theses files, that's why I think dload method work only with stock recovery
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
Thanks for the help but this method didn't work, everytime I try to flash the files, I got the same error "FAILED (remote: Command not allowed)” I don't know what is happening my bootloader is unlocked, why I can't flash the files with adb
Code:
target max-download-size: 450MB
sending 'boot' (21690 KB)...
OKAY [ 13.912s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 13.919s
target max-download-size: 450MB
sending 'recovery' (34264 KB)...
OKAY [ 21.963s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 21.985s
target max-download-size: 450MB
sending 'cust' (304183 KB)...
OKAY [191.580s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 191.603s
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [366.120s]
writing 'system'...
FAILED (remote: Command not allowed)
finished. total time: 366.144s
ROM flashed , if all went well
You must be restarted.
If you leave the recovery to hard reset and restart the phone
Created by sokoban. Thank you for using my release
rebooting...
finished. total time: 0.054s
Pressione qualquer tecla para continuar. . .
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
sokkoban said:
This is very strange. May be you really have locked bootloader
Post answer from this command in fastboot mode:
Code:
fastboot oem get-bootinfo
Click to expand...
Click to collapse
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Same issue with Huawei G6-U10
I'm having the same problem with Huawei Ascend G6-U10
Currently running on ROM b146, since it has some issues I was trying to downgrade or upgrade ( there is a b330 out).
I'm not an expert.
This morning I've unlocked the boot loader and then tried to flash a couple of different ROMs and I always get the same error message:
c:\adb>fastboot flash BOOT ./G6-U10verb330/boot.img
target reported max download size of 536870912 bytes
sending 'BOOT' (9696 KB)...
OKAY [ 0.310s]
writing 'BOOT'...
FAILED (remote: Command not allowed)
finished. total time: 0.321s
c:\adb>fastboot oem get-bootinfo
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
I'm guessing this is not a G6-U10 specific issue so if anyone can give any hint it'll be very appreciated.
Thanks.
I have the same problem with a honor 4x.
Rooted with kingroot. We haven't writing permission in /system. That's why we can't install the recovery. If you try to install superSU and update the binary I guess you get an error.
Now the question is: how we can do to make writeble /system with fast boot?
"mount -o rw,remount -t ext3 /dev/block/xxxxxxxxx /system" in terminal doesn't work...
Similar thing happened to me. Even if command for showing unlocked bootloader said it was unlocked that was false because I used Kingroot previously. Only thing that helped was to unlock the bootloader through fastboot again. Then it was really unlocked and I could flash recovery (in my case TWRP) which before I was unable to.
Diego Sousa said:
This was the result
Code:
C:\adb>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
As you can see the ADB says that the bootloader is unlocked, but I'm still having trouble
Click to expand...
Click to collapse
Have you tried it with linux yet?
And have you used the Update.APP and dload method?
Maybe a driver problem? Have administrator rights? And debug mode on?
Try to connect your phone (power on) to the pc and wait to be recognized. In cmd type this:
Code:
adb devices
It has to show you your serial number right? If doesn't your device is not being recognized by adb.
Next type:
Code:
adb reboot-bootloader
This will restart your phone into fastboot and now you can type "fastboot devices" like first command and it has to show you your serial number again.
Try rebooting into bl with this, not by plugin in the phone, and install the rom again
Huawei P8 Lite
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Have you tried install it in twrp? You don't have a twrp backup of stock rom?
In this case if you go in the Huawei eRecovery you can restore stock rom and twrp will be overwrited downloading the last rom , i tried it with my p8 lite 2017 .
Tuki2 said:
Hello I have a problem with my phone. I do not know how to hell I fix it.
It says error cannot load system.img but still I can install boot.img and others.
I¨d tryed that "dload" with update.app doesnt work.
phone is Huawei P8 Lite
this is my first time here
Click to expand...
Click to collapse
What are you using to go into fastboot mode? Is it ADB from Android SDK?? It turns out that using ADB from Android SDK lets you flash small files but not large files... I suggest you try flashing the file through Minimal ADB & Fastboot
sokkoban said:
Hello,
I created the script for flash via fastboot if you want try this method
Extract BOOT.img, Cust.img, Recovery.img, System.img and copy to fastboot folder.(attachment)
Enable developer options and USB debugging
Simply run file FLASH-ALL.bat file
Click to expand...
Click to collapse
i have the same issue as well, but just with Cust.img
For those who bricked their phone and facing any of the following issue (Black screen, vibrating only, no fastboot, unable to start, unable to install firmware etc.)
If you got No Fastboot, No recovery, No Display, hard bricked your device.You must perform sequential steps indicated below, process will include many small steps. Plz make sure to perform all steps in same sequence and same manner as prescribed. Remove all drivers related to mobile you have installed earlier.
Step 1: Install the Intel Soc USB driver:
(if you are using windows 8 or 10. it is very important to disable driver signature enforcement. see the sections related to your windows below. (note: if you will reboot pc after disabling it will be enabled again)).
This Is the driver which help a computer connecte to your Zen2 IntelSoc mode. To install these driver you need to perform special steps if you are using windows 8 / 8.1, 10 . you need to disable driver signature enforcement before installing drivers. below i have mentioned steps needed to install driver for various versions of windows. but first download the needed driver from link given below.
https://drive.google.com/open?id=0B72QQTXqZSRwR0JGeFI2U3FUZ2c
Step 1.1 - how to install these drivers:
(Note: if you see the image like below attached thumbnail and you click install software any way 2 times means drivers are installed correctly. if you don't see image below while installation it means you need to disable driver signature enforcement)
If you're using Windows 7:
Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc.
If you're using Windows 8 / 8.1 :
On Keyboard press Windows + I to show charm bar in the right corner,
click on the option setting. Choose "Change PC Settings" to enter the PC Settings.
Choose the General tab and navigate to Advanced Startup section, continue click Restart now.
This will reboot windows and allows you access to the advanced mode, now select the following options: Troubleshoot - -Startup Settings Advanced Options and then click the Restart button to restart the computer.
now you will see screen with various options numbered from 1. Find disable driver signature enforcement. And press the appropriate number on keyboard your pc will reboot
Now Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2
If you're using Windows 10 :
On Keyboard press Windows + I or click Start, select Settings.
In The Settings window, select the Update & security.
Continue Choose recovery and then advanced startup and click "Restart now".
When The computer has access to the Advanced screen you will see screen with various options numbered from 1. Find disable driver signature enforcement. And press the appropriate number on keyboard your pc will reboot
Now Right-click the file - iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
After This step, the driver installation is finished, continue to section 1.2
1.2 Connect Zenfone with computer IntelSoc Mode:
Now you must complete this step before installing xfstk downloader. it helps to setup device's connection to PC
on your pc open device manager and find Intel Soc.
Click to expand it. You will see a single option under here.
Connect your phone to computer via USB cable,
now back to the phone, hold power button for 10 seconds to shutdown completely, then press simultaneously the key "power" + "volume down", until phone vibrates. Or computer makes detection sound, wait a few seconds. it will add an item immediately below intelSoC in device manager ?MOOREFIELD? new devices is connected successful.
Now Download intel android USB Driver and install normally from link below:
https://drive.google.com/open?id=0B72QQTXqZSRwSU5CdDNuUElEcUE
( only after installing the above driver with correct steps and connecting Soc then only install xFSTK).
Step: 2 Installing xfstk-downloader:
installation of xFSTK is very simple. download xFSTK setup from the link below. to install. right click the setup file and run as Administrator. click next next simply until you finish the installation process
Here is the download link:
https://drive.google.com/open?id=0B72QQTXqZSRweDdfMjlPOGEyTW8
Now to Unbrick Process.
( only after installing the above driver with correct steps) go ahead to unbrick process.
Unbrick Process:
-The Necessary files:
ZE551ML: https://drive.google.com/open?id=0B72QQTXqZSRwV0QyWFRXbjMxaFk
ZE550ML: https://drive.google.com/open?id=0B72QQTXqZSRwY1AyLUdKdkI3OWM
After downloading the necessary files extract it. it will contain 3 files:- dnx_fwr.bin, ifwi.bin, droidboot_dnx.img.POS_sign.bin.
-Run XFSTK Downloader as Administrator, click the second tab at bottom MRD A0 / B0 + MOOR A0 + CRC .
-Then Go to Options to change the value in the Value Section Override Flag GP 0x80000807. Tick GP value over ride, change device detection time out value to 220 and Click OK is complete initial preparation. (important note: never use wrong gp flag value it may complicate things)
+ First select Firmware files FW DnX: and IFWI: by clicking small three dots:- IFWI DNX 2 dnx_fwr.bin and ifwi.bin file.
+ Now select operating system : skip the first box, in second box select file droidboot_dnx.img.POS_sign.bin
now switch off your mobile by holding power button for long and connect to pc.
now click begin download on xFSTK. after that simply power on mobile.
-Here You may see error multiple times just try to power off device completely and turn on again. flash again and again Until you see success: FW+OS Download complete!
After that you may see a 4 color screen, just like some TV stations stop broadcasting on TV. You have to wait a little. after few seconds or minutes device will boot into bootloader. wait 10 to 15 min if no success, If not repeat the xFSTK process again. once you get fastboot screen on device go ahead to flash RAW firmware
Now there are two ways to flash RAW firmware one is Asus Flash Tool (AFT) other is without AFT with help of commands. Personally, i like command method as it is much more reliable than Asus Flash Tool. both methods are provided here under.
Flash Raw Firmware Using Asus Flash Tool:
Required Files:
Asus Flash Tool: https://drive.google.com/open?id=0B72QQTXqZSRwUDZqa0M4SWRObVE
Raw Firmware File:
ZE551ML: https://drive.google.com/open?id=0B72QQTXqZSRwb2x1SHg2UUlsT0U ( Link updated to google drive and latest raw firmware 2.20.40.194)
ZE550ML:https://drive.google.com/open?id=0B72QQTXqZSRwcTBDaXZOYUNBdHM
Download Asus Flash Tool and install. Run asus flash tool as administrator. And select the phone model. Then select the downloaded raw file and click start button to flash.
Note: sometimes flash process may go endless. If this happens remove the usb from computer. Kill asus flashtool process from task manager. Now run tool again and flash.
Flashing Firmware Without AFT:
For this you need two things first is adb tool and second is raw firmware file both links are provided here under:
Fastboot and adb tool: ( includes setup as well as independent files ) latest version updated
https://drive.google.com/open?id=0B72QQTXqZSRwMGVuT0cwRlp2UG8
Adb fastboot tool for 64 bit windows and for those who are facing issue to load zip files while adb sideload. or unable to load system.img
https://drive.google.com/open?id=0B72QQTXqZSRwUkFRMl81b1pWa0k
Raw firmware ( you can use any earlier downloaded RAW firmware file)
ZE551ML: https://drive.google.com/open?id=0B72QQTXqZSRwb2x1SHg2UUlsT0U ( Link updated to google drive and latest raw firmware 2.20.40.194)
ZE550ML: https://drive.google.com/open?id=0B72QQTXqZSRwcTBDaXZOYUNBdHM
Now very first of all, rename .raw firmware file to .zip file and extract all files from it.. now place all files in adb and fastboot folder. ( Note: to extract raw file to avoid extension issue please give firmware file a complete new name ie: "user.zip" or anything you like
now in folder ( where you placed files from raw firmware and adb and fastboot tool folder) at empty place anywhere in folder hold Shift on computer keyboard and right click with mouse. Now click open command window here.
perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. don't worry, first boot gonna take a little longer time. so have patience and watch some funny video till phone boots up.
Now you can install any firmware version via adb sideload. make sure to install latest lollipop firmware before flashing Marshmallow. follow the guide to sideload.
How to Install firmware using adb sideload:
First of all go to setting > About >Software information > tap build number 7 times to enable developer options. now under setting go to developer options and find USB debugging here. tick to enable USB debugging
Now go to Asus website and download the desired firmware and place that file in adb fastboot tool folder. rename the files to your desirable short name ( lets take an example rename it to User.zip). now move your mouse cursor in folder anywhere at some empty place, press and hold the keyboard shift Button now right click your mouse button and open command window here. in cmd type adb devices and press enter ( note it will prompt an option on mobile to authorize the computer for adb. Please authorize this computer. ) after this your device will be listed under adb devices with some number. if not type command once again, if no success this time please ensure you have installed usb driver and authorized computer.
after adb recognize the device. run the following command
"adb reboot recovery"
phone will reboot into recovery ( Note you can go to recovery manually as well. for doing so power down your device. after that press and hold volume + button and press power button as mobile shows asus logo leave power button but keep holding volume button. you will boot into fastboot mode use your volume up and down key to go to option recovery mode. now click power button. phone will reboot into recovery mode.
once phone reboot into recovery mode find option apply update from adb and press that option with the help of power button
now go to cmd and run the following command
" adb sideload user.zip " ( Note: User.zip is the firmware file you download from asus and placed in adb tool folder and renamed so can be replaced with the name you renamed your file)
now let the computer do its work sit back and relax. once file loaded successfully reboot device.
( note first boot always takes little longer time so don't panic have patience and wait till phone boots completely
if you have any question please post here. use hide button while replying to avoid unnecessary length of post..
If the guide was helpful to you and your device is alive again. Hope you can hit the Thanks button. it will not take much effort or long time. Thank you.
Well hello sorry for the silly or stupid question but since I'm new to asus, And I see a lot of peoples bricking your devices I wanted to ask, There are some risk in update it if my bootloader locked and my phone fully stock? I received it some weeks ago and I not rooted or unlocked bootloader yet, so there are some chance to I get in a brick? Like some peoples did? I going to update next week, but just on case I wanted ask.
I gonna be very thankful if someone answer me
Tayanarak said:
Well hello sorry for the silly or stupid question but since I'm new to asus, And I see a lot of peoples bricking your devices I wanted to ask, There are some risk in update it if my bootloader locked and my phone fully stock? I received it some weeks ago and I not rooted or unlocked bootloader yet, so there are some chance to I get in a brick? Like some peoples did? I going to update next week, but just on case I wanted ask.
I gonna be very thankful if someone answer me
Click to expand...
Click to collapse
if you are stock. you can update without any issue. just keep in mind update to latest lolipop first.. ( Z00A-WW-2.20.40.194 ) then to MM
those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds
thank you
i could not flash the raw file via Asus Flash Tool. then i followed this process. after successful reboot updated to last official lollipop rom by copying it to phone root directory. after that finallly upgraded to official android 6.
phone working fine now. thanks a lot
touhid7 said:
i could not flash the raw file via Asus Flash Tool. then i followed this process. after successful reboot updated to last official lollipop rom by copying it to phone root directory. after that finallly upgraded to official android 6.
phone working fine now. thanks a lot
Click to expand...
Click to collapse
Glad to know that it was helpful for you
sukhwant717 said:
After a long time Asus funally launched MM for ZE551ML. but be very careful to install. Do not try to install it from custom recovery, do not install if you have rooted the phone. first return to stock rom. install latest lolipop build. then only update to MM.
any how for those who bricked their phone: use the following guide to unbrick ZE551ML
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Read the above guide carefully. but even after that people are unable to unbrick. people who are unable to flash raw. perform step 2 of the above guide. after that do not use the asus flash tool. Try the following guide,
very first of all. rename .raw firmware file to .zip file and extract all files from it.. now place all files in adb and fastboot folder.
open command window here. ( where you places files from raw firmware and adb and fast boot tool folder)
perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Question is,, if I'm already in android mm,,will my custom recovery still be there? Or do i need to flash it again via adb? Thnks..
jeffrey roy said:
Question is,, if I'm already in android mm,,will my custom recovery still be there? Or do i need to flash it again via adb? Thnks..
Click to expand...
Click to collapse
yes you need to flash if you want to install custom recovery . but flash it after updating to latest MM
if you are on unofficial MM. and you have custom recovery installed. don't try to install official MM. you will brick your device
Ahm question again bro..you mention in op install first to latest lollipop right,, how did you install it,, i mean via twrp or what?
---------- Post added at 03:43 PM ---------- Previous post was at 03:38 PM ----------
jeffrey roy said:
Ahm question again bro..you mention in op install first to latest lollipop right,, how did you install it,, i mean via twrp or what?
Click to expand...
Click to collapse
Sorry for bunch of questions,, I'm just making sure bro..
jeffrey roy said:
Ahm question again bro..you mention in op install first to latest lollipop right,, how did you install it,, i mean via twrp or what?
---------- Post added at 03:43 PM ---------- Previous post was at 03:38 PM ----------
Sorry for bunch of questions,, I'm just making sure bro..
Click to expand...
Click to collapse
if yoy want to install latest MM. for that purpose you must install official asus recovery.. or if you want lolipop only then you can install it from twrp
sukhwant717 said:
if yoy want to install latest MM. for that purpose you must install official asus recovery.. or if you want lolipop only then you can install it from twrp
Click to expand...
Click to collapse
ok, got it, but where can i download official recovery? for firmware 2.20.40.194? thanks!!
---------- Post added at 05:16 PM ---------- Previous post was at 05:08 PM ----------
jeffrey roy said:
ok, got it, but where can i download official recovery? for firmware 2.20.40.194? thanks!!
Click to expand...
Click to collapse
nah never mind found it!!!
jeffrey roy said:
ok, got it, but where can i download official recovery? for firmware 2.20.40.194? thanks!!
---------- Post added at 05:16 PM ---------- Previous post was at 05:08 PM ----------
nah never mind found it!!!
Click to expand...
Click to collapse
just flash firmware with sideload i think it will replace recovery automatically. if not then you can flash manually afterwards
Not able to go to the legit serial number... Can I start from the fastboot steps?
surajpai said:
Not able to go to the legit serial number... Can I start from the fastboot steps?
Click to expand...
Click to collapse
yes. you can but exit the Asus flash tool
Recovering to android L from back up
sukhwant717 said:
After a long time Asus funally launched MM for ZE551ML. but be very careful to install. Do not try to install it from custom recovery, do not install if you have rooted the phone. first return to stock rom. install latest lolipop build. then only update to MM.
any how for those who bricked their phone: use the following guide to unbrick ZE551ML
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Read the above guide carefully. but even after that people are unable to unbrick. people who are unable to flash raw. perform step 2 of the above guide. after that do not use the asus flash tool. Try the following guide,
very first of all. rename .raw firmware file to .zip file and extract all files from it.. now place all files in adb and fastboot folder.
open command window here. ( where you places files from raw firmware and adb and fast boot tool folder)
perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the volume down button and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Before installing custom CM13 I had taken the backup of my device which ran android L.
I have just begun the operation to recover that. Hopefully it should not brick my phone
---------- Post added at 01:21 AM ---------- Previous post was at 01:12 AM ----------
deepankdude said:
Before installing custom CM13 I had taken the backup of my device which ran android L.
I have just begun the operation to recover that. Hopefully it should not brick my phone
Click to expand...
Click to collapse
Good news people, my phone did not brick.
Did not need to move to android L via any method, just restored my back up
please help.
My phone showed in devices manager as Moorefield and xfstk dont show any errors after the "begin download" The process is completed without any problem. The phone restart and show me the 4 colours and then restart, not showing me the fastboot. I did many times the process of xfstk, but always is the same result.
what i did is update the zf2 through twrp.
pd: excuse my english.
sukhwant717 said:
if you are stock. you can update without any issue. just keep in mind update to latest lolipop first.. ( Z00A-WW-2.20.40.194 ) then to MM
Click to expand...
Click to collapse
Oh thank you for the reply, I'm on latest stock firmware, so I going to update to MM next week
xFSTK seems to detect my phone and copy files, but at the end of the process it won ´t reboot. The program then makes 20 retries, and gives up. No error message, only "success"
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--GetOpCode
16:00:43 - XFSTK-LOG--ReadInAck
16:00:43 - XFSTK-LOG--GetAck - HLT$(4)
16:00:43 - XFSTK-LOG--FW: Firmware update completed...
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--LogError
16:00:43 - XFSTK-STATUS--Error Code: 0 - Success
16:00:43 - XFSTK-LOG--void MerrifieldDownloader::do_abort()
16:00:43 - XFSTK-LOG--Abort
16:00:43 - XFSTK-LOG--C:/Users/agm21_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
16:00:43 - XFSTK-STATUS--PASS
16:00:43 - XFSTK-STATUS--Firmware download completed. Continuing to OS...
16:00:53 - XFSTK-STATUS--Reconnecting to device - Attempt #20
16:00:54 - XFSTK-STATUS--Timeout to detect the device, make sure to charge up your phone before flashing
Can someone help me, please ...
agm2112 said:
xFSTK seems to detect my phone and copy files, but at the end of the process it won ´t reboot. The program then makes 20 retries, and gives up. No error message, only "success"
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--GetOpCode
16:00:43 - XFSTK-LOG--ReadInAck
16:00:43 - XFSTK-LOG--GetAck - HLT$(4)
16:00:43 - XFSTK-LOG--FW: Firmware update completed...
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--LogProgress
16:00:43 - XFSTK-LOG--LogError
16:00:43 - XFSTK-STATUS--Error Code: 0 - Success
16:00:43 - XFSTK-LOG--void MerrifieldDownloader::do_abort()
16:00:43 - XFSTK-LOG--Abort
16:00:43 - XFSTK-LOG--C:/Users/agm21_000/Downloads/xFSTK_ZE551ML-sal358-amtech.vn/ifwi.bin size:4194468 bytes
16:00:43 - XFSTK-STATUS--PASS
16:00:43 - XFSTK-STATUS--Firmware download completed. Continuing to OS...
16:00:53 - XFSTK-STATUS--Reconnecting to device - Attempt #20
16:00:54 - XFSTK-STATUS--Timeout to detect the device, make sure to charge up your phone before flashing
Can someone help me, please ...
Click to expand...
Click to collapse
you can power on manually while device connected to it. have you changed device detection time out to 120. when it give three four tries and phone don't starts press power button and start in manually
I have following errors on last cmds :
Code:
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
error: write_sparse_skip_chunk: don't care size 1650659389 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1078366269 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 516055101 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 45117 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 3.181s]
sending sparse 'system' (472927 KB)...
error: write_sparse_skip_chunk: don't care size 1650659389 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1650659389 is not a multiple of the block size 4096
OKAY [ 17.123s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 23.692s
Full process :
Code:
C:\adb>fastboot devices
C:\adb>fastboot devices
C:\adb>fastboot devices
0123456789ABCDEF fastboot
C:\adb>fastboot oem erase_osip_header
...
(bootloader) cmd_oem!arg= erase_osip_header S
(bootloader) [0]erase_osip_header S
OKAY [ 2.274s]
finished. total time: 2.275s
C:\adb>fastboot oem erase_token
...
(bootloader) cmd_oem!arg= erase_token S
(bootloader) [0]erase_token S
OKAY [ 1.805s]
finished. total time: 1.807s
C:\adb>fastboot oem start_partitioning
...
(bootloader) cmd_oem!arg= start_partitioning S
(bootloader) [0]start_partitioning S
(bootloader) Start partitioning
OKAY [ 2.255s]
finished. total time: 2.256s
C:\adb>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 1.685s]
writing '/tmp/partition.tbl'...
OKAY [ 2.253s]
finished. total time: 3.941s
C:\adb>fastboot oem partition /tmp/partition.tbl
...
(bootloader) cmd_oem!arg= partition /tmp/partition.tbl S
(bootloader) [0]partition S
(bootloader) [1]/tmp/partition.tbl S
OKAY [ 2.404s]
finished. total time: 2.405s
C:\adb>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 3.950s]
finished. total time: 3.951s
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.441s]
finished. total time: 2.441s
C:\adb>fastboot erase data
******** Did you mean to fastboot format this partition?
erasing 'data'...
OKAY [ 18.099s]
finished. total time: 18.108s
C:\adb>fastboot erase APD
******** Did you mean to fastboot format this partition?
erasing 'APD'...
OKAY [ 2.632s]
finished. total time: 2.633s
C:\adb>fastboot erase ADF
******** Did you mean to fastboot format this partition?
erasing 'ADF'...
OKAY [ 2.373s]
finished. total time: 2.374s
C:\adb>fastboot oem wipe splashscreen
...
(bootloader) cmd_oem!arg= wipe splashscreen S
(bootloader) [0]wipe S
(bootloader) [1]splashscreen S
(bootloader) CMD 'wipe /splashscreen'...
(bootloader) erasing volume "/splashscreen", size=4194304...
(bootloader) wrote ret 194304, count 2, "/dev/block/by-name/splashscreen
(bootloader) read back ret 194304, count 2 "/dev/block/by-name/splashscre
OKAY [ 2.351s]
finished. total time: 2.353s
C:\adb>fastboot oem stop_partitioning
...
(bootloader) cmd_oem!arg= stop_partitioning S
(bootloader) [0]stop_partitioning S
(bootloader) Stop partitioning
OKAY [ 2.261s]
finished. total time: 2.262s
C:\adb>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 2.135s]
writing 'fastboot'...
OKAY [ 2.556s]
finished. total time: 4.693s
C:\adb>fastboot flash token PROD_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 1.681s]
writing 'token'...
OKAY [ 2.442s]
finished. total time: 4.124s
C:\adb>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 1.804s]
writing 'ifwi'...
OKAY [ 3.350s]
finished. total time: 5.158s
C:\adb>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 1.712s]
writing 'splashscreen'...
OKAY [ 2.276s]
finished. total time: 3.991s
C:\adb>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 2.058s]
writing 'boot'...
OKAY [ 2.601s]
finished. total time: 4.662s
C:\adb>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 2.051s]
writing 'recovery'...
OKAY [ 2.586s]
finished. total time: 4.644s
C:\adb>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 2.560s]
sending 'APD' (183963 KB)...
OKAY [ 7.546s]
writing 'APD'...
OKAY [ 7.787s]
finished. total time: 17.898s
C:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
error: write_sparse_skip_chunk: don't care size 1651515453 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1076383805 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 511402045 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 12349 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 3.206s]
sending sparse 'system' (477812 KB)...
error: write_sparse_skip_chunk: don't care size 1651515453 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1651515453 is not a multiple of the block size 4096
OKAY [ 17.487s]
writing 'system'...
FAILED (remote: flash_cmds error!
)
finished. total time: 24.071s
C:\adb>
Can you help me ?
History :
Wanted to update to MM
- unrooted
- try recovery mode and install from asus support new firmware with adb, problem was that i had a custom recovery, i think this is what failed and i had black screen after the update.
- followed your tutorial
- stuck at asus boot logo after having the error i pasted above.
Edit : Seems the archive is corrupted, 7zip throw following error when i extract : Data error : system.img
Gonna try raw file from there : http://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
May be i had a problem while downloading the previous one, but i prefer to test another one.
In this thread u can find "HOW TO COMPLETLY RELOCK DEVICE" / UNBRICK VIDEO TUTORIAL
" ADB COMMAND METHOD":
In this method You can find how to unbrick device
If your device is only capable to access fastboot mode only
1.Find your stock firmware HERE
2.DOWNLOAD HuaweiUpdate extrator below in download section
3.open HuaweiUpdateExtractor select the update.app which was extracted from firmware zip
4.then extract the following files :::
-->boot .img
-->cust.img
-->recovery.img
-->system.img
Then boot your device into fastboot ,open adb command then type
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
device is now working but bootloader is still unlocked.
to lock the bootloader reboot your device into fastboot mode type :::
fastboot oem lock (your 16 digit bootloader code)
<<if it fails>>
then copy the update.app which was extrated earlier into sd card / dload
then force update by pow+volume +&volume-
THAT'S it UR DEVICE IS NOW FULLY LOCKED.
FOR VIDEO TUTORIAL :::
https://youtu.be/OMKDnBqbi3U
When flashing
fastboot flash cust cust.img
i get
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 13.837s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 13.848s
In twrp i can see that the "cust" partition is 184MB, the cust.img il over 400MB, can be this the problem?
mandelbort said:
When flashing
fastboot flash cust cust.img
i get
target reported max download size of 471859200 bytes
sending 'cust' (433554 KB)...
OKAY [ 13.837s]
writing 'cust'...
FAILED (remote: partition error)
finished. total time: 13.848s
In twrp i can see that the "cust" partition is 184MB, the cust.img il over 400MB, can be this the problem?
Click to expand...
Click to collapse
The bootloader is in unlock state or not??
VenuGopalu said:
The bootloader is in unlock state or not??
Click to expand...
Click to collapse
Unlock
are us using the last firmware? and also try all steps one more time respectively .. is your device working fine now
My p9 lite is stuck on the huawei logo, its been a week now. it all started when I flashed a wrong update.app (i mistakenly flashed the rollback update.app while i was on b161)
now I cannot use the device anymore, i can only get to bootloader mode but cant flash anything
help
I had the exact same problem. I got out of that situation by rooting the phone, and re-flashing it.
However I already had the unlock code handy. If you don't have that then you are mostlikely f'ed.
My bootloader is unlocked yet I am unable to fastboot flash anything as i get errors.
HEY! I've done the same thing yesterday But now phone working great! I find the way
1. Download C432B160, Huawei Extractor and SRK Tool Huawei
2. Prepare your unlock bootloader code
3. Unpack UPDATE.APP by Huawei Extractor (You need files: boot.img, system.img, recovery.img, cust.img)
4. Go to folder SRK Tool Huawei -> Command
5. Put *.img files to Command folder
6. Put UPDATE.APP (Not extracted) on your sdcard in folder "dload"
6. Hold Shift + right right mouse button "Open the command line here"
7. Plug your phone in fastboot mode (vol- and power button then fast plug USB)
8. Type in cmd "fastboot devices" (Now you probably see your device)
9. Type:
fastboot oem unlock xxyourfastbootunlockcodexx
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img (that command takes 2-3 minutes)
10. Unplug Your device
11. Hold vol- vol+ and power button, it will install UPDATE.APP from your sdcard
12. Done!
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
elliotn said:
My bootloader is unlocked yet I am unable to fastboot flash anything as i get errors.
Click to expand...
Click to collapse
You only think it's unlocked (yeah, it's showing Bootloader UNLOCKED) but no, it isn't. I don't know why, but you must unlock it first.
Links:
Huawei Exctractor XDA
Huawei SRK Tool XDA
VNS-L21C432B160 HUAWEI PAGE
ugh
I'm stuck at "6. Hold Shift + right right mouse button "Open the command line here"" I have no idea what to do
You have to hold the "Shift" button on your keyboard (under Caps lock), and click on the right mouse button in the folder. Then in the menu, choose "Open the command line here"
help
BaXeL said:
HEY! I've done the same thing yesterday But now phone working great! I find the way
1. Download C432B160, Huawei Extractor and SRK Tool Huawei
2. Prepare your unlock bootloader code
3. Unpack UPDATE.APP by Huawei Extractor (You need files: boot.img, system.img, recovery.img, cust.img)
4. Go to folder SRK Tool Huawei -> Command
5. Put *.img files to Command folder
6. Put UPDATE.APP (Not extracted) on your sdcard in folder "dload"
6. Hold Shift + right right mouse button "Open the command line here"
7. Plug your phone in fastboot mode (vol- and power button then fast plug USB)
8. Type in cmd "fastboot devices" (Now you probably see your device)
9. Type:
fastboot oem unlock xxyourfastbootunlockcodexx
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img (that command takes 2-3 minutes)
10. Unplug Your device
11. Hold vol- vol+ and power button, it will install UPDATE.APP from your sdcard
12. Done!
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
You only think it's unlocked (yeah, it's showing Bootloader UNLOCKED) but no, it isn't. I don't know why, but you must unlock it first.
Links:
Huawei Exctractor XDA
Huawei SRK Tool XDA
VNS-L21C432B160 HUAWEI PAGE
Click to expand...
Click to collapse
I KEEP GETTING THIS ERROR: error: cannot load 'RECOVERY.img' HELP ME I AM DESPERATE
firmware
BaXeL said:
HEY! I've done the same thing yesterday But now phone working great! I find the way
1. Download C432B160, Huawei Extractor and SRK Tool Huawei
2. Prepare your unlock bootloader code
3. Unpack UPDATE.APP by Huawei Extractor (You need files: boot.img, system.img, recovery.img, cust.img)
4. Go to folder SRK Tool Huawei -> Command
5. Put *.img files to Command folder
6. Put UPDATE.APP (Not extracted) on your sdcard in folder "dload"
6. Hold Shift + right right mouse button "Open the command line here"
7. Plug your phone in fastboot mode (vol- and power button then fast plug USB)
8. Type in cmd "fastboot devices" (Now you probably see your device)
9. Type:
fastboot oem unlock xxyourfastbootunlockcodexx
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img (that command takes 2-3 minutes)
10. Unplug Your device
11. Hold vol- vol+ and power button, it will install UPDATE.APP from your sdcard
12. Done!
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
You only think it's unlocked (yeah, it's showing Bootloader UNLOCKED) but no, it isn't. I don't know why, but you must unlock it first.
Links:
Huawei Exctractor XDA
Huawei SRK Tool XDA
VNS-L21C432B160 HUAWEI PAGE
Click to expand...
Click to collapse
I neeeeed firmware for vns-l22
ughhead said:
I KEEP GETTING THIS ERROR: error: cannot load 'RECOVERY.img' HELP ME I AM DESPERATE
Click to expand...
Click to collapse
Did you unlock your bootloader first?
hey
BaXeL said:
Did you unlock your bootloader first?
Click to expand...
Click to collapse
I'm no longer getting the error I mentioned but now my phone wouldn't respond to the three button boot... it gets stuck on the logo again and doesn't do anything. I don't think I have the correct firmware. I need for VNS-L22C636B101 and I cant find it anywhere :crying: my phone is done for
You have to flash custom oeminfo.img to debrand your phone (it's fully legal). You'll find it on htcmania
thanks but..
BaXeL said:
You have to flash custom oeminfo.img to debrand your phone (it's fully legal). You'll find it on htcmania
Click to expand...
Click to collapse
if you don't mind can you explain this further and how it will help my situation?
ughhead said:
if you don't mind can you explain this further and how it will help my situation?
Click to expand...
Click to collapse
Yes, you can't flash C432B160 if your phone is branded by operator, the flashing will always end at error. Flashing oeminfo.img and Huawei firmware is fully legal and you don't loose warranty. And debranding is a good thing because (in future) you can download faster official Nougat.
okay
BaXeL said:
Yes, you can't flash C432B160 if your phone is branded by operator, the flashing will always end at error. Flashing oeminfo.img and Huawei firmware is fully legal and you don't loose warranty. And debranding is a good thing because (in future) you can download faster official Nougat.
Click to expand...
Click to collapse
Alright so let me explain my situation properly (I'm a big dumb-doofy-doo so i'm not even sure if my phone is branded) I bought my phone off amazon last year and 2 days ago I made the mistake of trying to update it to Nougat using http://www.droidviews.com/update-huawei-p9-lite-manually-official-android-7-0-nougat-emui-5-0/ and the files for build number VNS-L22C636B360 however my build number is VNS-L22C636B101 (Huawei P9 Lite). using the first file called "update.zip" I tried upgrading but it said software update failed. I turned on OEM and tried using "update_data_full_VNS-L22_hw_spcseas.zip" to update. it worked but I don't think this was the full update as it rebooted and I was greeted by Huawei eRecovery which had three options: "Download latest and recovery" "reboot" and "shut down" so naturally I chose the first option. It however ended with "Getting package info failed". I tried it over and over but it didn't change. so this is where I because frustrated, and stupid, and factory reset my phone. it didn't make a difference. same eRecovery prompt (but did the reset take off OEM??) I took out my SD Card and replaced the Update.app with another one (I cant remember which I was sad but I definitely complicated matters more by doing this) and I came upon the same problem the person who made this post: stuck on Huawei logo. if I power it off it will vibrate and boot back up on it's own to get stuck on the Huawei logo thing (it wouldn't even do the pretty flowy smoke thing) so because of this it does not respond to the 3-button force update anymore idk why the only mode I can get it into successfully is fastboot mode but even after following the step by step answer I cant get it to respond to the 3-button force update (I also dont have the exact firmware for my build number) I did skip the bootunlocker steps because I dont have a product id or IMEI to generate a code from the Huawei website. in fastboot mode however it says "Phone Unlocked" and "FRP Unlock"
I dont know what to do... I think I need the firmware but I cant find it specific to my build number VNS-L22C636B101
First of all you must have your bootloader unlock code...
You wrote that you get error on flashing by fastboot probably "Command not allowed" because, your bootloader is locked (Yes it's only display "unlocked" I also got on that )
If you don't have code you can't do anything, sorry. You must send your phone to huawei store on warranty.
You don't have phone box?
ya
BaXeL said:
First of all you must have your bootloader unlock code...
You wrote that you get error on flashing by fastboot probably "Command not allowed" because, your bootloader is locked (Yes it's only display "unlocked" I also got on that )
If you don't have code you can't do anything, sorry. You must send your phone to huawei store on warranty.
You don't have phone box?
Click to expand...
Click to collapse
ya I got that error.. and yes I have the box but I bought it off amazon so idk where to send it
ughhead said:
ya I got that error.. and yes I have the box but I bought it off amazon so idk where to send it
Click to expand...
Click to collapse
Ask your seller, hope you'll get a working phone
Mine was solved by booting to fastboot and did fastboot OEM unlock "unlock code" then fastboot flash recovery TWRP.img
Even though my bootloader was unlocked it worked
tq
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
BaXeL said:
HEY! I've done the same thing yesterday But now phone working great! I find the way
1. Download C432B160, Huawei Extractor and SRK Tool Huawei
2. Prepare your unlock bootloader code
3. Unpack UPDATE.APP by Huawei Extractor (You need files: boot.img, system.img, recovery.img, cust.img)
4. Go to folder SRK Tool Huawei -> Command
5. Put *.img files to Command folder
6. Put UPDATE.APP (Not extracted) on your sdcard in folder "dload"
6. Hold Shift + right right mouse button "Open the command line here"
7. Plug your phone in fastboot mode (vol- and power button then fast plug USB)
8. Type in cmd "fastboot devices" (Now you probably see your device)
9. Type:
fastboot oem unlock xxyourfastbootunlockcodexx
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cust cust.img
fastboot flash system system.img (that command takes 2-3 minutes)
10. Unplug Your device
11. Hold vol- vol+ and power button, it will install UPDATE.APP from your sdcard
12. Done!
---------- Post added at 12:39 PM ---------- Previous post was at 12:35 PM ----------
You only think it's unlocked (yeah, it's showing Bootloader UNLOCKED) but no, it isn't. I don't know why, but you must unlock it first.
Links:
Huawei Exctractor XDA
Huawei SRK Tool XDA
VNS-L21C432B160 HUAWEI PAGE
Click to expand...
Click to collapse
.....................................
C:\WINDOWS\system32>fastboot oem unlock xxyourfastbootunlockcodexx
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\WINDOWS\system32>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
error: cannot load 'recovery.img': No error
C:\WINDOWS\system32>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
error: cannot load 'boot.img': No error
C:\WINDOWS\system32>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
error: cannot load 'cust.img': No error
error: cannot load 'SYSTEM.img'
Sorry you guy for such a long thread, but my phone, Huawei P9 Lite VNS-L31 has exactly the problem in this thread and when i follow the lead on #4, every step are working well until the: "fastboot flash system system.img" on step 9, I got "error: cannot load 'SYSTEM.img' ". All other flash working well but i don't know why it returned an error on that step, could you guy please help me to get over it, thank you very much!
my log:
>fastboot oem unlock (my code)
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.002s
>fastboot flash recovery RECOVERY.img
target reported max download size of 471859200 bytes
sending 'recovery' (33112 KB)...
OKAY [ 0.707s]
writing 'recovery'...
OKAY [ 0.775s]
finished. total time: 1.482s
>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (13998 KB)...
OKAY [ 0.299s]
writing 'boot'...
OKAY [ 0.324s]
finished. total time: 0.623s
>fastboot flash cust CUST.img
target reported max download size of 471859200 bytes
sending 'cust' (428162 KB)...
OKAY [ 9.108s]
writing 'cust'...
OKAY [ 5.520s]
finished. total time: 14.629s
>fastboot flash system SYSTEM.img
error: cannot load 'SYSTEM.img'
My zenfone 2 laser are stuck in fastboot mode, can't go to recovery or any thing, using the adb and fastboot i can flash boot.img, system.img etc. but nothing happens. and the bootloader are locked too, and i don't find some way to unlock without the app from asus, tried to put 'fastboot oem get_unlock_ability' or 'fastboot oem unlock' but i just receive 'FAILED (remote: 'unknown command')'
i don't know what to do, someone know what i can do? pls
Reflash ofw via adb with stock boot/recovery
lukk321 said:
My zenfone 2 laser are stuck in fastboot mode, can't go to recovery or any thing, using the adb and fastboot i can flash boot.img, system.img etc. but nothing happens. and the bootloader are locked too, and i don't find some way to unlock without the app from asus, tried to put 'fastboot oem get_unlock_ability' or 'fastboot oem unlock' but i just receive 'FAILED (remote: 'unknown command')'
i don't know what to do, someone know what i can do? pls
Click to expand...
Click to collapse
Hi dude try flash boot and recovery from h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[/
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
[/B]
and will begin to install and hope all goes well and good luck
Hi man, thank you for reply
Foggalias said:
Hi dude try flash boot and recovery from h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[/
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
[/B]
and will begin to install and hope all goes well and good luck
Click to expand...
Click to collapse
But i alredy try to flash boot, recovery, twrp, even try use flashall.bat, but my bootloader are locked, so when i type 'fastboot flash recovery recovery.img' it appears that worked, but when i try to go to recovey, the phone just shows the asus logo with 'fastboot mode' on the top, even typing 'fastboot reboot-bootloader' or 'fastboot reboot' while holding the volume down button, it don't work. And typing 'fastboot getvar recovery or boot' shows nothing.
Probably i need to unlock the bootloader first, but i don't know how to do that.
lukk321 said:
But i alredy try to flash boot, recovery, twrp, even try use flashall.bat, but my bootloader are locked, so when i type 'fastboot flash recovery recovery.img' it appears that worked, but when i try to go to recovey, the phone just shows the asus logo with 'fastboot mode' on the top, even typing 'fastboot reboot-bootloader' or 'fastboot reboot' while holding the volume down button, it don't work. And typing 'fastboot getvar recovery or boot' shows nothing.
Probably i need to unlock the bootloader first, but i don't know how to do that.
Click to expand...
Click to collapse
sorry to hear dude and sorry for late reply I'm sure I used the app to unlock my boot loader ill do a bit of digging if I find anything
---------- Post added at 11:48 PM ---------- Previous post was at 11:36 PM ----------
Foggalias said:
sorry to hear dude and sorry for late reply I'm sure I used the app to unlock my boot loader ill do a bit of digging if I find anything
Click to expand...
Click to collapse
hi dude try here its flashing tarp without unlocking boot loader and its through fastboot mode
h***s:/.asus.com/zentalk/in/thread-128115-1-1.html
---------- Post added 11th October 2018 at 12:10 AM ---------- Previous post was 10th October 2018 at 11:48 PM ----------
Foggalias said:
sorry to hear dude and sorry for late reply I'm sure I used the app to unlock my boot loader ill do a bit of digging if I find anything
---------- Post added at 11:48 PM ---------- Previous post was at 11:36 PM ----------
hi dude try here its flashing tarp without unlocking boot loader and its through fastboot mode
h***s:/.asus.com/zentalk/in/thread-128115-1-1.html
Click to expand...
Click to collapse
try this unlock bloody via fastboot
h***s://drive.google.com/file/d/0ByzlvYYhluSdR3ZpdWYzX1ZfRUE/view?usp=drivesdk
Hi again dude how u getting on? I remember when I used the unlock tool app it just rebooted and nothing looked different at all and the only way I found putTit was u locked was on fastboot mode using this command:
fastboot oem device-info
Said something like bootloader unlocked: True
I'd give it a shot and hopefully its just the case of some bad img's good luck
thanks helping me
Foggalias said:
sorry to hear dude and sorry for late reply I'm sure I used the app to unlock my boot loader ill do a bit of digging if I find anything
---------- Post added at 11:48 PM ---------- Previous post was at 11:36 PM ----------
hi dude try here its flashing tarp without unlocking boot loader and its through fastboot mode
h***s:/.asus.com/zentalk/in/thread-128115-1-1.html
---------- Post added 11th October 2018 at 12:10 AM ---------- Previous post was 10th October 2018 at 11:48 PM ----------
try this unlock bloody via fastboot
h***s://drive.google.com/file/d/0ByzlvYYhluSdR3ZpdWYzX1ZfRUE/view?usp=drivesdk
Click to expand...
Click to collapse
the asus site are off now, so later i'll see that
the unlock tool look that worked, but the phone still stuck in fastboot
Foggalias said:
Hi again dude how u getting on? I remember when I used the unlock tool app it just rebooted and nothing looked different at all and the only way I found putTit was u locked was on fastboot mode using this command:
fastboot oem device-info
Said something like bootloader unlocked: True
I'd give it a shot and hopefully its just the case of some bad img's good luck
Click to expand...
Click to collapse
fastboot oem device-info shows that:
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.017s]
finished. total time: 0.018s
even after using the unlock tool
Thank you for helping dude
I gonna send the phone to the support center, before i explode the phone haha, sorry for taking your time, bye.
lukk321 said:
I gonna send the phone to the support center, before i explode the phone haha, sorry for taking your time, bye.
Click to expand...
Click to collapse
no worries dude sorry coudnt sort it
---------- Post added at 12:26 PM ---------- Previous post was at 12:17 PM ----------
lukk321 said:
fastboot oem device-info shows that:
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.017s]
finished. total time: 0.018s
even after using the unlock tool
Click to expand...
Click to collapse
hi dude sorry to hear but people have managed to flash boot using certain version img file and then able to flash the recovery on locked bootloaders
id say try before it costs you at service
here: https://www.asus.com/zentalk/in/thread-88877-1-1.html
Same issue with my phone but i'm getting different error
I guys,
I gone through your post and similar issue I'm facing. As suggested I tried unlock boot loader or whenever trying to flash getting below error. Can you help me to get this fix. Might be I'll recover my phone.
target reported max download size of 268435456 bytes
sending 'fastboot' (13273 KB)...
OKAY [ 0.419s]
writing 'fastboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.426s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Below device info i can see but still it boots into fastboot and not in recovery mode
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.004s]
finished. total time: 0.004s
Hiya dude I know there's a certain fw version that it'll let u adb sideload, I take your getting this issue from trying to side load, I'll have a look and try and find fw I used. It does state device unlocked: true which I did mine using an app if I remember correctly
Are you able to flash recovery ar all ??
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Hiya dude again I think what u used is linked above in thread, have you tried thise by any chance?
---------- Post added at 11:02 AM ---------- Previous post was at 10:57 AM ----------
krahul99 said:
I guys,
I gone through your post and similar issue I'm facing. As suggested I tried unlock boot loader or whenever trying to flash getting below error. Can you help me to get this fix. Might be I'll recover my phone.
target reported max download size of 268435456 bytes
sending 'fastboot' (13273 KB)...
OKAY [ 0.419s]
writing 'fastboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.426s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Below device info i can see but still it boots into fastboot and not in recovery mode
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
Try this dude:
https://www.asus.com/zentalk/in/forum.php?mod=viewthread&tid=128115&mobile=2
Let me know how u get on
---------- Post added at 11:09 AM ---------- Previous post was at 11:02 AM ----------
krahul99 said:
I guys,
I gone through your post and similar issue I'm facing. As suggested I tried unlock boot loader or whenever trying to flash getting below error. Can you help me to get this fix. Might be I'll recover my phone.
target reported max download size of 268435456 bytes
sending 'fastboot' (13273 KB)...
OKAY [ 0.419s]
writing 'fastboot'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.426s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
Below device info i can see but still it boots into fastboot and not in recovery mode
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Adb Enable: 0
OKAY [ 0.004s]
finished. total time: 0.004s
Click to expand...
Click to collapse
Hi dude try flash boot and recovery from here a little guide in there to (update error fix): h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
and will begin to install and hope all goes well and good luck
Tried this but still it comes in fastboot mode only
Yup i tried these methods earlier. It shows written but when I reboot and try to go to recovery it directly comes into Fastboot. Rather if I remove battery and just plug the usb cable even though it shows fastboot mode.
Foggalias said:
Hiya dude I know there's a certain fw version that it'll let u adb sideload, I take your getting this issue from trying to side load, I'll have a look and try and find fw I used. It does state device unlocked: true which I did mine using an app if I remember correctly
Are you able to flash recovery ar all ??
---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------
Hiya dude again I think what u used is linked above in thread, have you tried thise by any chance?
---------- Post added at 11:02 AM ---------- Previous post was at 10:57 AM ----------
Try this dude:
https://www.asus.com/zentalk/in/forum.php?mod=viewthread&tid=128115&mobile=2
Let me know how u get on
---------- Post added at 11:09 AM ---------- Previous post was at 11:02 AM ----------
Hi dude try flash boot and recovery from here a little guide in there to (update error fix): h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
and will begin to install and hope all goes well and good luck
Click to expand...
Click to collapse
Same issue with my asus
krahul99 said:
Yup i tried these methods earlier. It shows written but when I reboot and try to go to recovery it directly comes into Fastboot. Rather if I remove battery and just plug the usb cable even though it shows fastboot mode.
Click to expand...
Click to collapse
I'm facing same issue with my device.. Pls can you hlp me
Mohanking6 said:
I'm facing same issue with my device.. Pls can you hlp me
Click to expand...
Click to collapse
Install recovery and boot image version 1531 then use adb sideload to flash latest version of ROM.
Foggalias said:
Reflash ofw via adb with stock boot/recovery
Hi dude try flash boot and recovery from h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[/
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
[/B]
and will begin to install and hope all goes well and good luck
Click to expand...
Click to collapse
I just wanted to Thank you! I was about to give up and sell the phone because ive tried all countless methods and now i have recovery mode. Thank you so much forr keeping the google drive links alive..
frenchiejoshy said:
I just wanted to Thank you! I was about to give up and sell the phone because ive tried all countless methods and now i have recovery mode. Thank you so much forr keeping the google drive links alive..
Click to expand...
Click to collapse
unable to flash boot.img brother
fastboot flash fastboot boot.img
target reported max download size of 268435456 bytes
sending 'fastboot' (24547 KB)...
OKAY [ 0.775s]
writing 'fastboot'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.803s
osm gkkkkkk said:
unable to flash boot.img brother
fastboot flash fastboot boot.img
target reported max download size of 268435456 bytes
sending 'fastboot' (24547 KB)...
OKAY [ 0.775s]
writing 'fastboot'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.803s
Click to expand...
Click to collapse
which file did you use and how
Foggalias said:
Reflash ofw via adb with stock boot/recovery
Hi dude try flash boot and recovery from h**ps://drive.google.com/folderview?id=0B0aDjdU4gTwZRWxzLWxhYUZPbVk&usp=drive_web
then reboot holding volume down button once done should have recovery menu select install through adb sideload etc
download fw from here: h**ps://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS550KL/UL-Z00L-WW-21.40.1220.2196-user.zip?_ga=2.175867362.1367738333.1539164489-1033220152.1538417076[/
then on pc copy downloaded fw to adb folder and type: adb sideload UL-Z00L-WW-21.40.1220.2196-user.zip
[/B]
and will begin to install and hope all goes well and good luck
Click to expand...
Click to collapse
pls help which file and how ,i have th same issue as was faced by one of the used
unable to install boot.img
unable to flash boot.img brother
fastboot flash fastboot boot.img
target reported max download size of 268435456 bytes
sending 'fastboot' (24547 KB)...
OKAY [ 0.775s]
writing 'fastboot'...
FAILED (remote: cannot flash this partition in locked state)
finished. total time: 0.803s