Related
Hello guys,
Frank is writing. Sorry for disturbing, but i´m in big trouble right now. I made a Factory reset, wipe Dalvik etc. and flashed the PA Aosp Mako 4.0 + latest Gapps.. Nothing special so far, but now my Nexus is still in a bootloop. If i go to the recovery mode, i have no access to TWRP just have the possibility to choose between Start, Start bootloader, Power off, or Recovery Mode. But if i go to the recovery mode the bugdroid is there and nothing happens further. After connecting the device to my mac there is a message on the screen that it´s in download mode?! i didn´t seen this before.. So if you have any solution, it would be great. a factory reset to if possible or even necessary.
Right now I am at my wits end. May someone has an advice for me what to do? i can´t imagine christmas without my beloved smartphone.. ;(
Thanks for your attention!
cheers
Frank
You need fastboot working on your computer, not sure of the exact steps for a mac, but if you download the Android SDK it will be in there. Then you can directly flash a factory image for your phone from the fastboot screen. (The one you describe with start, start bootloader, etc)
You can download the factory images here https://developers.google.com/android/nexus/images#occam
Android sdk for mac http://dl.google.com/android/android-sdk_r22.3-macosx.zip
hey.. thank you for your reply. i downloaded the required files but how to get the access with terminal when it´s still not possible to start the phone? If i type in ./adb devices in terminal just following popped up but nothimg else:
-bash: /Users/frankherrmann/Desktop/adt-bundle-mac-x86_64-20131030: is a directory
do u know what to do now?
At the dead android screen, hold the power button and press vol+. Does it get you to stock recovery?
unfortunately nothing happens the screen turns off, that´s all... ;(
You should try flashing a stock 4.4.2 occam image using fastboot. This would return you to stock and you can then root and install TWRP or CWM.
endxpen tyrants
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image. but anyway, it seems that i can´t get the access to the phone. if i go in the adt folder and use the command adb services in the terminal my device will not be recognized.
Frank-iMac:adt-bundle-mac frankherrmann$ ./adb devices
List of devices attached
Frank-iMac:adt-bundle-mac frankherrmann$
Do i type in something wrong? maybe it´s just a thinking error by myself
thanks againfor your help!
FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Franks-MacBook-Pro:Android Tools leherman$ ./fastboot flash /Users/leherman/Desktop/android\ tools/image-occam-kot49h.zip
unknown partition '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
error: cannot determine image filename for '/Users/leherman/Desktop/android tools/image-occam-kot49h.zip'
Franks-MacBook-Pro:Android Tools leherman$
Click to expand...
Click to collapse
Sorry, I can't help you with flashing on Mac. Do you have access to a PC?
FrankHPunkt said:
FrankHPunkt said:
ok, thanks...meanwhile i did a factory reset with in the recovery mode, but after reboot the same thing happens, still bootloop.. now i just downloaded the adt bundle with sdk inside and the latest factory image and put it in the same folder that i named as adroid tools. i got the access to the folder and after type in the command ./fastboot devices my devices has been recognized and the number too. but if i try to flash the stock image it will not work. i typed in ./fastboot flash and the image name but the failure message -bash: ./flash: No such file or directory
so... i suggest that it´s been just a problem that i typed not the correct command, isn´it?
Click to expand...
Click to collapse
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse
Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Federico_96 said:
FrankHPunkt said:
Yes you got 2 options,run the flash-all script or flash the files manually for example typing fastboot flash recovery recovery.img or fastboot flash radio radio.img, you didn't specified the partition to flash
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FrankHPunkt said:
Hey Frederico,
thanks for your reply i did it as you told me and typed this in terminal : as you can see something should work, but it was not possible to flash the image.
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash radio-mako-m9615a-cefwmazm-2.0.1700.98.img radio-mako-m9615a-cefwmazm-2.0.1700.98.img
sending 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img' (45537 KB)...
OKAY [ 1.715s]
writing 'radio-mako-m9615a-cefwmazm-2.0.1700.98.img'...
FAILED (remote: partition table doesn't exist)
finished. total time: 1.718s
Franks-MacBook-Pro:android tools leherman$ ./fastboot flash image-occam-kot49h.zip image-occam-kot49h.zip
sending 'image-occam-kot49h.zip' (429746 KB)...
OKAY [ 15.845s]
writing 'image-occam-kot49h.zip'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.848s
do u have an idea whats still not right. Seems to be on the right way!
thank you very much so far!
Click to expand...
Click to collapse
The right command is ./fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.98.img, so it is ./fastboot flash <generic name of partition> <exact name of the file> hope this will work, but my suggestion is to run the flash-all script,it will do it authomatically for you, if you want do it manually,here at step D there are all the commands
Thanks a lot, you made may day! the phone is rebooting....
merry christmas!
cheers
Frank
I am quite new to the android rooting & custom recovery and having a problem with my Huawei P8 GRA-UL00 flashing (purchased from China), when I try the procedure with MAC OS X. My step by step actions and result was as follows:
1. I installed "SDK Tools Only" for Mac. Connected the device via USB, launched terminal and successfully see the device with the "adb devices" command.
2. Vol +, Vol- and Power didn't work to enter to the fastboot&rescure mode. However, Vol- and Power worked. (Also, Vol+ and Power enters to the Huawei eRecovery mode, which shows EMUI logo, Reboot, Download new version and recovery and Shutdown buttons. I guess this is stock recovery???)
3. In the fastboot mode, I have successfully seen the device with "fastboot devices". Then I unlocked the bootloader with the code. The first problem was here, there were no auto-reboots and I entered "fastboot reboot" command, and stuck in seeing "reboooting..." in terminal. Nothing happened after this command. After 10 minutes I manually rebooted the phone by pressing power and entered into the fastboot mode. I was written as "Phone Unlocked". (Do u think it was really successful?)
4. I tried to flash the TWRP file which was uploaded by @jniklast (openrecovery-twrp-2.8.7.0-p8-ul10-r4.img). The result was like that:
MacBook-Airlatform-tools go$ ./fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img
target reported max download size of 471859200 bytes
sending 'recovery' (25566 KB)...
OKAY [ 0.703s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 1.056s
MacBook-Airlatform-tools go$
5. Tried fastboot reboot, but I wasn't successful:
MacBook-Airlatform-tools go$ ./fastboot reboot-bootloader
rebooting into bootloader...
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 0.121s
MacBook-Airlatform-tools go$
I am not sure if I have correctly defined my problem. I guess I wasn't successful to install TWRP even it says so. What should I do after finishing the flash recovery command?
Can anyone help me with this error?
@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.
I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.
samusalo said:
@landros57 That recovery is only for Android 5.1.1 beta version. You should flash the @jniklast 's GRA-L09 version of TWRP which is for Android 5.0.
Click to expand...
Click to collapse
Thank you samusalo.. Then I understand that TWRP for GRA-L09 can work on a GRA-UL00. I will try.
jniklast said:
I'm not quite sure what the problem is? You enter rescue mode via power + vol- so that's correct. You enter recovery via power + vol- and vol+ so what happens if you do that after flashing TWRP? And better not use the adb command go voot into recovery as that will lead to a bootloop to recovery which has to be broken by manually booting into it once.
Click to expand...
Click to collapse
I don't use adb reboot, I manually press Vol - and Power. Then, the Fastboot & Rescue mode opens, and I enter to the terminal "fastboot flash recovery openrecovery-twrp-2.8.7.0-p8-ul10-r4.img". It quickly shows that the installation is successful. Then I enter fastboot reboot-bootloader (I guess this is required to launch TWRP) but it shows that usb read error.
@jniklast and @samusalo thank you for your explanations. They both worked.
I flashed the GRA-L09 version of the TWRP to my GRA-UL00 and it worked! Now I have a backup...
I also realized that I am doing something wrong.. After installing TWRP, I was trying to fastbot reboot-boatloader in order to get TWRP launched automatically. However, the only thing I need to do is to follow jniklast's instructions and after the phone shut down, press Vol+ Vol- and Power together to get the TWRP launch.
Now I will try to flash an official International ROM, instead of my Chinese ROM.
Is the following command correct for this?
fastboot flash system "HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version).zip"
No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor
jniklast said:
No, you need to extract the img files to be able to flash it via fastboot. Look for huawei image extractor
Click to expand...
Click to collapse
Many .img files exists in the update.app file. I guess I need to flash only the system.img?
If I flash the recovery.img or boot.img inside the update.app, will I lose the custom recovery and my backup?
I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Partially Successful
jniklast said:
I'd first try to only flash system.img. If that doesn't work also flash boot.img. it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
Flashing boot and system was successful! Then, again, my "fastboot reboot-bootloader" didn't work and retured me my initial error. But I rebooted manually and successfully launched my phone OS.
I now have a slow-operating new Android firmware, which is a little weird )) I think it is now a international&chinese hybrid version. Some apps disappeared and I have a complete new page for google services and apps. However, my chinese stuff (baidu spotlight search, notifications, etc.) remains The EMUI Build is: GRA-UL00V100R001C00B120, which should be V100R001C900B141 as I have flashed the img files of this update.
I tried "fastboot erase userdata", "fastboot erase cache" and "fastboot erase system" but they both returned with "FAILED (remote: Command not allowed)".
The following were my successful fastboot flash commands:
MacBook-Airlatform-tools go$ ./fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (23256 KB)...
OKAY [ 0.653s]
writing 'boot'...
OKAY [ 0.569s]
finished. total time: 1.222s
MacBook-Airlatform-tools go$ sudo ./fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (459646 KB)...
OKAY [ 20.184s]
writing 'system'...
OKAY [ 6.149s]
sending sparse 'system' (450260 KB)...
OKAY [ 22.868s]
writing 'system'...
OKAY [ 6.051s]
sending sparse 'system' (437337 KB)...
OKAY [ 18.146s]
writing 'system'...
OKAY [ 5.952s]
sending sparse 'system' (460637 KB)...
OKAY [ 19.570s]
writing 'system'...
OKAY [ 6.267s]
sending sparse 'system' (448019 KB)...
OKAY [ 18.582s]
writing 'system'...
OKAY [ 5.982s]
sending sparse 'system' (165186 KB)...
OKAY [ 6.853s]
writing 'system'...
OKAY [ 2.206s]
finished. total time: 138.824s
MacBook-Airlatform-tools go$
jniklast said:
it might be though that you have to flash another cust.img as well and I'm not quite sure if that's possible via fastboot. In that case you'd have to do it via TWRP which is a bit tricky
Click to expand...
Click to collapse
I was finally successful to flash cust.img with fastboot and now I have B141 and all Chinese apps are removed. All Chinese ROM specific apps are disappeared and the only remaining Chinese stuff is the text in the Magazine Unlock, accessible when swiped up from the bottom of the screen at the lock screen.
The remaining problem for now is; when I press the Dialer, Contacts and Messages apps at the bottom, they crash.
Do I need to flash any other from the following extracted img files?
3RDMODEM.img
CACHE.img
CRC.img
CURVER.img
DTIMAGE.img
EFI.img
FASTBOOT.img
HIFI.img
MCUIMAGE.img
MODEM.img
MODEM_DSP.img
MODEMNVM_UPDATE.img
RECOVERY.img
RECOVERY2.img
SENSORHUB.img
SHA256RSA.img
TEEOS.img
TRUSTFIRMWARE.img
USERDATA.img
VERLIST.img
XLOADER.img
This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8
jniklast said:
This is now delicate stuff, you could try and flash the radio (aka modem.img) but that will probably break connectivity as that is different in hardware. Maybe you'd need to install the dialer and messaging apks from the ul00 firmware. Does an alternate dialer work so that you can actually call someone?
And I think fastboot reboot-bootloader doesn't exist. It's either fastboot reboot bootloader or maybe only fastboot reboot. Anyway, booting into bootloader or recovery is better done by pressing the keys on the P8
Click to expand...
Click to collapse
Hello again,
Actually the hardware is the same, it is GRA-UL00. The device originally had: GRA-UL00-UL10_EMUI3.1_Android5.0_C00B173
I tried to fastboot the following ROM:
HUAWEI P8 Firmware(GRA-UL00&UL10,Android5.0,Emtion UI 3.1,V100R001C900B141,General Version)
I was successful to flash Root, CUST and System but when I try to flash any Modem-related img files (Modem.img, 3RDMODEM.img, MODEM_DSP.img, MODEMNVM_UPDATE.img), I get the following error:
sending 'modem' (38865 KB)...
OKAY [ 1.038s]
writing 'modem'...
FAILED (remote: Command not allowed)
finished. total time: 1.039s
I didn't try to install APKs.
I am still having crash problems with the dialer, contacts, messages, google play, and some other google services.
Network Mode FREEZE AUTO
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.
Finally Done!
meetkhems said:
Hi did you try checking Mobile Networks In Settings, As i m unable to open that. As soon as i click on it the network gets released and then comes back. THATS' ALL. I have the same phone and did the same stuff. Unable to Flash Modem.IMG as well.
Click to expand...
Click to collapse
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.
landros57 said:
I finally succeeded.
After flashing the Boot.img, system.img and cust.img and launching the phone, I flashed the stock recovery and made a wipe/reset to factory settings. First, I extracted the recovery.img from the update.app file which you can find after downloading the official firmware and running the Huawei Update Extractor script available in the forum. Then I flashed this stock recovery.img in the fastboot mode. And finally I entered in the stock recovery (Huawei eRecovery) mode by pressing the Vol+, and Power buttons. After the wipe & reset to factory settings, I launched the phone and all problems with the radio, dialer, contacts, google services, etc were solved.
Thank you @jniklast for your help.
Click to expand...
Click to collapse
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.[/QUOTE]
meetkhems said:
Thanks a lot but i m still facing the problem. As soon as i select Mobile networks in settings nothing opens just the network gets released "NO Service" & comes back. I m unable to open it to select Network Mode or to change apn. It is not greyed Out but still not opening rest everything is working beautifully. Please Help. @jniklast for your help.
Click to expand...
Click to collapse
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.
Any Update on this anyone? I am unable to use the phone as it drains a lot of battery on 3G and i cant change it to 2G as due to Blank Mobile Network Settings.
Guys I have one problem I want to flash stock recovery for P8 L09 but in cmd it fails like not allowed command anybody knows why ?
landros57 said:
Just checked and realized that I also have the same problem. THe contents of the "Mobile Networks" button doesn't show up and it works like a reset button. When I press, it disconnects me from the network and then the it reconnects to the network automatically.
Click to expand...
Click to collapse
Hi landro57 have you tried to flash the update.app file of 18 Kb from local update? Some owners of the P8 gra ul09 variant are using that file to debrand their P8s. The mobile networks problem you ae experiencing is the same some other people have turnaround with that trick. You should check with it and report back to us, because if that goes ok, it means no more china firmware on our P8 gra ul00, we can simply flash the international general P8 firmware V100R001C900B141.
Inviato dal mio SGP311 utilizzando Tapatalk
GryphonA said:
flash the update.app file of 18 Kb from local update
Click to expand...
Click to collapse
Hi GryphonA, I don't get it, which 18kb update.app file do you mean?
I got the same problem (no access to mobile networks settings) and I can't remember if I never had that access or it happened due to my rooting/cusomizing activities.
I have GRA-UL00C433B180. I flashed also C470B180 but that didn't solve the problem.
BTW: There are a lot of mobile network setting apps and widgets in the Play Store but all apps I tested show the same failure as the mobile network settings: There seems to be a network reset and nothing more.
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.
Hi Guys,
I have finally successfully flashed a phh AOSP 8.1 provided in the following thread to Lenovoz5
Before proceeding, here are the basics,
Do not Ever ever ever EVER flash zui_3.9.075_Z5_L78011_multi
Bootloader needs to be unlocked only if you wantto flash custom Android 9.0 Pie roms,
If you want to stick to stock Lenovo rom, then you do not need to unlock bootloader.
If you start your phone and it says "Your device is corrupt" then your phone has zui_3.9.075_Z5_L78011_multi.
This rom is a dirty version of stock rom, that Chinese sellers sells your phone with. This is not the original rom.
Always use "L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst" for unlocking bootloader, 075, this version is the only version that allows unlocking bootloader.
With other versions like L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.390_ST_180809_qpst, L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.200_ST_180809_qpst
This option is hidden by manufacturer under Developer options.
If you start your phone and you dont get option to activate via Wifi or Network, then your phone doesnt have stock rom and it has been tweaked by your seller.
Here is the download link for stock rom, do not use the rom that has _multi in its name.
https://mega.nz/#F!9953xR6a!76EEVKmW3LtjE7tYPF2Z1Q
If you get Sahara error when flashing through QFIL
1) Make sure your phone is in edl mode, follow the video for that
2) Make sure the config is correctly set in Settings within QFIL
3) Try changing USB ports on your PC, It only works on USB 2.0, will throw error on USB 3.0 and 3.1
Make sure you go through this thread, each and every question is answered already.
If you have any questions, make sure to list out everything you did and what you are trying to do,
My phone doesnt start
I cant proceed
I cant flash
I am stuck
I cant unlock bootloader
This doesnt help, please post full description with screenshots , what you have done to your phone after your received it from your seller, what you want,
Google the basics, bootloader unlocking, stock rom, custom rom, Android 8.0, Android 9.0 etc
I have created Lenovo z5 group on telegram, pls post there if you have any questions, i dont check xda, but i will respond on telegram whenever i can.
Check out this video on how to flash using qfil
https://youtu.be/TdkNaKpiiUw
Go through this thread and read all the posts, most of your questions is probably already answered.
I would recommend if you are not good at flashing then back up all partitions on external sd card. (WIFI and data working now )
To backup stock partitions,
1. Unlock bootloader
2. Flash TWRP through fastboot
3. Boot to TWRP and do a full back up of all partitions.
https://forum.xda-developers.com/pr...-development/experimental-phh-treble-t3709659
All the credits for the rom goes to developers in that thread, i have only flashed it to Lenovo z5.
Flashing guide for Android 8.1: (Everything is working on Android 9.0, check out second post in this thread.)
What you will need:
ADB: https://www.mediafire.com/file/8j84x6j1g2xb8z6/adb.zip/file
TWRP.img https://drive.google.com/open?id=1yj9Vu-1YqR8kxMReP5pZerpLa-PKnZ1z
boot.img - This is the same boot.img in stock qpst from L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.200_ST_1807 21_qpst
or get it from here https://drive.google.com/open?id=14WNBcstAB3A40fafEhI2NWMAhGBtJge_
vbmeta.img https://drive.google.com/open?id=1dTIuxwKnfZFrE7HFtYSMqUx6gItXvxEB
ROM - system-arm64-ab-gapps-su.img from the above link
superuser flash file (To be flashed through TWRP recovery) https://drive.google.com/open?id=1w0PHZFvfYvExBAEnyDyqBpBjMGLBoLes
superuser apk(not necessary to install) https://drive.google.com/open?id=1XU9pydDRPOZ2weq14j6S-hveM98C8zHe
Procedure to Flash custom rom on Lenovo Z5:
Step 1: Flash stock version L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst using qfil mentioned earlier in this thread
(After flashing this stock rom, if your phone goes in to boot loop then don't worry about it, continue with the rest of the process)
Step 2:Unlock bootloader (This will void your warranty) (unlocking command: fastboot flashing unlock)
Step 3: boot to bootloader
Flash with the following commands.
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a system-arm64-ab-gapps-su.img
6. fastboot -w flash system_b system-arm64-ab-gapps-su.img
7. fastboot flash boot twrp.img
8. Once twrp is flashed, do not turn off or restart your phone, press volume down twice, select option boot to recovery
9. Flash superuser flash file(mentioned above)
10. Do not clear any data or cache, we already did that, Start and Enjoy!
After completing these steps please wait for about 25 to 30 mins
(My logs when i flashed the rom)
c:\adb>adb reboot bootloader
c:\adb>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Sending 'vbmeta' (4 KB) OKAY [ 0.018s]
Writing 'vbmeta' OKAY [ 0.037s]
Finished. Total time: 0.079s
c:\adb>fastboot flash boot_a boot.img
Sending 'boot_a' (52261 KB) OKAY [ 1.795s]
Writing 'boot_a' OKAY [ 0.037s]
Finished. Total time: 1.842s
c:\adb>fastboot flash boot_b boot.img
Sending 'boot_b' (52261 KB) OKAY [ 1.798s]
Writing 'boot_b' OKAY [ 0.036s]
Finished. Total time: 1.843s
c:\adb>fastboot flash system_a system-arm64-ab-gapps-su.img
Sending sparse 'system_a' 1/3 (524284 KB) OKAY [ 18.954s]
Writing sparse 'system_a' 1/3 OKAY [ 0.006s]
Sending sparse 'system_a' 2/3 (488160 KB) OKAY [ 20.940s]
Writing sparse 'system_a' 2/3 OKAY [ 0.005s]
Sending sparse 'system_a' 3/3 (514508 KB) OKAY [ 21.349s]
Writing sparse 'system_a' 3/3 OKAY [ 0.010s]
Finished. Total time: 68.562s
c:\adb>fastboot flash system_b system-arm64-ab-gapps-su.img
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 12466167 4k blocks and 3121152 inodes
Filesystem UUID: 98e2d366-b46f-11e8-9d3d-3d9d543f2291
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424
Allocating group tables: done
Writing inode tables: done
Creating journal (65536 blocks): done
Writing superblocks and filesystem accounting information: done
Sending sparse 'system_b' 1/3 (524284 KB) OKAY [ 19.159s]
Writing sparse 'system_b' 1/3 OKAY [ 0.037s]
Sending sparse 'system_b' 2/3 (488160 KB) OKAY [ 20.708s]
Writing sparse 'system_b' 2/3 OKAY [ 0.007s]
Sending sparse 'system_b' 3/3 (514508 KB) OKAY [ 21.250s]
Writing sparse 'system_b' 3/3 OKAY [ 0.007s]
Erasing 'userdata' OKAY [ 3.849s]
Sending 'userdata' (4348 KB) OKAY [ 0.167s]
Writing 'userdata' OKAY [ 0.007s]
Finished. Total time: 73.993s
c:\adb>fastboot flash boot twrp.img
Sending 'boot_a' (58524 KB) OKAY [ 2.021s]
Writing 'boot_a' OKAY [ 0.007s]
Finished. Total time: 2.041s
c:\adb>adb reboot bootloader
c:\adb>fastboot erase cache
Erasing 'cache' FAILED (remote: 'Check device console.')
Finished. Total time: 0.013s
Not working:
Notification LED (Thanks to DarkerMaster)
Pictures taken by camera are always 90 degrees rotated
Google Camera app is crashing
Working on Android 8.1:
Call
Camera
Fingerprint reader
WIFI
Mobile data ...
Almost everything
I am still testing the device. I will post details later.
Android 8.1
https://drive.google.com/open?id=1k1bgp3sLedy-e5vqYKZF47WXRIVfO-tN
https://drive.google.com/open?id=11RAiDNS-1_bv7ceYJDLriOuGtMIkfbXt
https://drive.google.com/open?id=1hDrJHaKKHhowWJSvVUN3Y9scZeCMMLIz
https://drive.google.com/open?id=1bvKErzYwF9qH87Leie_acnwElINM8qxQ
https://drive.google.com/open?id=1Sg5mHLgm6_Bl4xz3ZBrgq7sLDbrveGWg
https://drive.google.com/open?id=1XxaiVKaImXZ64mH-TwuXcXNEFaTn2ydK
https://drive.google.com/open?id=1ABII2x3hWMKwgTr8mVxI-cYTiej1lVlN
https://drive.google.com/open?id=1rn7CXYnhiiiDBYoF_K1us9vXjgTMOigq
Imp:
If you have flashed one of these Roms, and you can boot in to it successfully, please do not use Factory reset. If you do, then the rom wont boot, since Magisk/SU is installed.
If you still do, then boot to Bootloader, flash vbmeta, boot_a, boot_b, twrp, Magisk(Android 9)/SU(Android 8).
If you have unlocked bootloader, do not relock it, ever
Special Thanks to phhusson for his [AOSP 8.1] [2018-08-16] Phh-Treble
Experimental:
Zui FM Radio app (Not working yet!)
Please note this is still under development, i am only posting it here, if anyone wants to work on it.
https://drive.google.com/open?id=1raHCHhMxOQVM8L0rbSjoKeTVLmbtBSIc
Don't forget to hit that Thanks button !
Cheers
Android 9.0 flashing guide
Back up all partitions on external sd card.
Check out this video on how to flash using qfil
https://youtu.be/TdkNaKpiiUw
https://forum.xda-developers.com/pr...ce-development/9-0-pixelexperience-p-t3833294
Rom: PixelExperienceP-arm64-ab.zip
All the credits for the rom goes to developers in that thread, i have only flashed it to Lenovo z5.
What you will need:
TWRP.img https://drive.google.com/open?id=1yj9Vu-1YqR8kxMReP5pZerpLa-PKnZ1z
boot.img - This is the same boot.img in stock qpst from L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.200_ST_1807 21_qpst
or get it from here https://drive.google.com/open?id=14WNBcstAB3A40fafEhI2NWMAhGBtJge_
vbmeta.img https://drive.google.com/open?id=1dTIuxwKnfZFrE7HFtYSMqUx6gItXvxEB
ROM - PixelExperienceP-arm64-ab.img from the above link
Magisk superuser flash file (To be flashed through TWRP recovery) https://drive.google.com/open?id=1FV_ogrSU488bpI_hhuyA8rHm3Fj_xLqb
Magisk superuser apk https://drive.google.com/open?id=1hi_58d1nJ-PNe3aPKb_0YsLrh5ElOXVn
Step 1: Flash stock version L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst using qfil mentioned earlier in this thread
(After flashing this stock rom, if your phone goes in to boot loop then don't worry about it, continue with the rest of the process)
Step 2:Unlock bootloader (This will void your warranty) (unlocking command: fastboot flashing unlock)
Step 3: boot to bootloader
Flash with the following commands.
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3. fastboot flash boot_a boot.img
4. fastboot flash boot_b boot.img
5. fastboot -w flash system_a PixelExperienceP-arm64-ab.img
6. fastboot -w flash system_b PixelExperienceP-arm64-ab.img
7. fastboot flash boot twrp.img
8. Once twrp is flashed, do not turn off or restart your phone, press volume down twice, select option boot to recovery
9. Flash Magisk flash file(mentioned above, once this is done take pictures of the TWRP logs)
10. Do not clear any data or cache, we already did that
11. On first boot install Magisk apk mentioned above. That's it !
Not working:
Notification LED
Working on Android 9:
Call
Camera
Fingerprint reader
WIFI
Mobile data(4G not sure about 3G)
Google Camera (If app crashes then follow procedure in this thread https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-enable-camera2-api-t3419579 )
Almost everything
Android 9.0
https://drive.google.com/open?id=1L_q2b8V0V7lIafcQsMVbKgqyRq3Tt2Hp
https://drive.google.com/open?id=1grkAu-FhZ56LKN82ubXYN3163ChTUVwr
https://drive.google.com/open?id=1yd5B0HN9Bund6UbJrEScbRsvrofExtT2
https://drive.google.com/open?id=1lWnH408p6aIREmEzl8IIKyE4UKS5V0Nk
https://drive.google.com/open?id=12EDJRbNm_4KVPD72FJ4Yem0gt3XE-BVr
https://drive.google.com/open?id=1RBt2miHzcvC9punEytJd_9aRyDwwhtV9
https://drive.google.com/open?id=1saTXcINKgbjw4HKxvRrSlbPrYk6GJfRr
https://drive.google.com/open?id=1QfLT5_gUk6k3U7o6ZJig8skn7Ckr--GK
https://drive.google.com/open?id=1pWJxmxO-ZzdNdGCK4LVO_zqxKpCQV5fG
Some snaps taken from the phone
https://drive.google.com/open?id=1w0GCNHKjuhE3x_A6xAwVgkYua0pMWGj-
https://drive.google.com/open?id=1GZ4LXyBHOL-zWEXrJVSMRPc07Nabg-eB
https://drive.google.com/open?id=1kTyVHk2Gr8LHekjvn7AwtnC92xrj0_7G
https://drive.google.com/open?id=1qgADqYoePMN9B5OMcpXw2pUc5DYXPCLI
If Windows doesnt detect phone in File Transfer mode:
Enable Developer options, turn off USB debugging.
If Mobile data doesnt work:
Settings > mobile data > Preferred network type = 4G and Choose your network providers Access point, if there is none then create one.
Special Thanks to EnesSastim and phhusson for their [9.0][GSI] PixelExperience P - UNOFFICIAL
Follow this process if you want to remove encryption:
This will delete the os and data on your phone. please backup everything before proceeding. External SD card will be untouched.
Flash L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.390_ST_180809_qpst via qfil (This step is to flash latest persist, firmware, vendor etc images available in 390, if you want to stay on 075 and you already have this stock image flashed, then you can skip this step)
TWRP: https://forum.xda-developers.com/an...overy-lenovo-z5-special-edition-twrp-t3850041
boot.img and persist.img are from version 390 of stock rom. (you can also use 075 images)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash boot recovery-TWRP-3.2.3-1002-LENOVO_Z5-CN-wzsx150.img
Press volume down button twice and go to Recovery
(change language to english if needed)
In recovery backup all of your partitions on to External SD card.
Mount system, persist, firmware
Advanced > RM Forceencrypt
Select Remove DMVerity and Remove Forceencrypt
Swipt to confirm
(This should not throw any error in red fonts, should show Done in the end)
(If it says failed to mount Persist, then reboot to bootloader, fastboot flash persist persist.img)
In recovery goto Wipe
Select Format Data
type Yes (This will remove the encryption)
Reboot to bootloader
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash persist persist.img
fastboot -w flash system_a PixelExperienceP-arm64-ab.img
fastboot -w flash system_b PixelExperienceP-arm64-ab.img
fastboot flash boot twrp.img (older version of TWRP)
Boot to TWRP and flash Magisk
Here is the link to the video
https://www.youtube.com/watch?v=brS5tqfx2BQ&index=3&list=PLNqXvI29Azcg9lxA_n6ltytf9aFhn3T1d&t=1081s
download for 075
https://mega.nz/#F!9953xR6a!76EEVKmW3LtjE7tYPF2Z1Q
Return to Stock:
Downloads : ZUI5 https://drive.google.com/open?id=1IL8Pu3Ame9gu6jqAAkBQrEiRL1a93rHK
ZUI10 https://drive.google.com/open?id=1ANAZXbbygyZHAVNGmgoPimJ1fIKbK38D
Credits for ZUI 5 and Zui 10 goes to @M.Z.F and the original developer of the images in these zip files.
https://forum.xda-developers.com/android/development/lenovo-z5-custom-roms-pie-t3904607
Steps to return to stockbackup your data or everything will be wiped)
IF you are on Android 9.0
1) go to TWRP and back up all partitions on SD card (persist, vendor, system, data, boot, firmware, ... )
Step 2 and 3 will turn encryption on, so if u want to disable encryption, after step 3, flash recovery-TWRP-3.2.3-1020-LENOVO_Z5-CN-wzsx150.img and disable encryption. v 474 has new firmware and i have seen better call reception and data connectivity.
2) Flash stock L78011_CN_OPEN_USER_Q00016.0_O_ZUI_3.9.075_ST_180605_qpst through QFIL
3) Flash stock L78011_CN_OPEN_USER_Q00016.0_O_ZUI_4.0.474_ST_190118_qpst through QFilL
4) Boot to bootloader
5) go to Zui5 folder (link is above) and click on Batch.bat file
6) Press 2, Hit enter, enter, enter
7) phone will automatically restart and boot to ZUI5
8) go to ZUI10 folder and click on Batch.bat
7) Press 2, Hit enter, enter, wait for phone to restart.
Congrats you are back to stock ZUI.
Don't forget to hit that Thanks button !
Cheers
Wooow! A few questions%
Have you tested camera? How is the quality?
Also Android 9 working ok? What is the file.Zip that should be downloaded and flashed from the Pixel Experience list in the second link?
First link of Android 8.1 doesn't work.
Thanks!
nfraccar said:
Wooow! A few questions%
Have you tested camera? How is the quality?
Also Android 9 working ok? What is the file.Zip that should be downloaded and flashed from the Pixel Experience list in the second link?
First link of Android 8.1 doesn't work.
Thanks!
Click to expand...
Click to collapse
Thanks for letting me know about the broken link, i have updated it.
I have everything working on Android 8.1 , not tried 9 yet. I will test camera quality tomorrow during day time. But camera does work.
Second link is the boot image.
GREAT!
Wanna go home quickly and play with my Z5!!!
Thank you for your work!!
Notification led work?
Did you tried Google Camera?
Also would you be so kind to explain how to flash another image? For example from AOSP 8.1 to 9.0?or viceversa. Thanks
nfraccar said:
Also would you be so kind to explain how to flash another image? For example from AOSP 8.1 to 9.0?or viceversa. Thanks
Click to expand...
Click to collapse
I have tried that multiple times for Android 9.0, wifi and data just doesnt work, may be we will have to wait for new firmware from Lenovo.
rendroid15 said:
I have tried that multiple times for Android 9.0, wifi and data just doesnt work, may be we will have to wait for new firmware from Lenovo.
Click to expand...
Click to collapse
Is it always possible to reflash stock ZUI?
How?
Thank you for Your kind support
nfraccar said:
Is it always possible to reflash stock ZUI?
How?
Thank you for Your kind support
Click to expand...
Click to collapse
Unless you mess with Vendor and stock firmware partitions, you can always go back to ZUI.
For flashing stock ZUI, please see below thread, it has all the information you need including downloads
https://forum.xda-developers.com/android/help/help-lenovo-z5-chinese-updates-t3812110
DarkerMaster said:
Thank you for your work!!
Notification led work?
Did you tried Google Camera?
Click to expand...
Click to collapse
Google Camera is crashing on start up. I have tried 6 different versions. No luck.
Push Notifications are working so it rings but the led is not blinking.
rendroid15 said:
Google Camera is crashing on start up. I have tried 6 different versions. No luck.
Push Notifications are working so it rings but the led is not blinking.
Click to expand...
Click to collapse
Of course you enabled camera 2 API right?
Yo rendroid, I managed to get my phone working again (first time in a week, woo hoo!)
Since flashing the system image didn't work with the adb, I put it in my phone's storage and flashed it with twrp.
(Btw, enabling the file extensions to be seen in file explorer didn't help with flashing the system image)
I was actually surprised it worked!
So my phone now has a working rom on it but I have a few problems:
-WiFi and Data not working. (The wifi toggle actually causes the phone to freeze. However, it breaks itself out and crashes the wifi toggle, leaving you to use the phone again)
-This is a minor issue but the notifications aren't cropped right (cut off and stuff)
This honestly has been a major breakthrough for me ( now that my phone isn't a paperweight anymore) and it's all thanks to you and the other devs for your hard work.
If you could help me with the wifi and data issue, that would the final piece to the puzzle and I could stop using my malfunctioning S4.
Cirus61 said:
Yo rendroid, I managed to get my phone working again (first time in a week, woo hoo!)
Since flashing the system image didn't work with the adb, I put it in my phone's storage and flashed it with twrp.
(Btw, enabling the file extensions to be seen in file explorer didn't help with flashing the system image)
I was actually surprised it worked!
So my phone now has a working rom on it but I have a few problems:
-WiFi and Data not working. (The wifi toggle actually causes the phone to freeze. However, it breaks itself out and crashes the wifi toggle, leaving you to use the phone again)
-This is a minor issue but the notifications aren't cropped right (cut off and stuff)
This honestly has been a major breakthrough for me ( now that my phone isn't a paperweight anymore) and it's all thanks to you and the other devs for your hard work.
If you could help me with the wifi and data issue, that would the final piece to the puzzle and I could stop using my malfunctioning S4.
Click to expand...
Click to collapse
nice !
now for the wifi and data
i need you to flash the same rom using fastboot not twrp
The File explorer setting was just to see if the file has any extensions. So if you dont see an extension then add .img in the end.
I think there is a bug in twrp that is causing wifi and data to not work.
I have tried flashing the 8.1 and it has given me error in all files by fastboot
rng30 said:
I have tried flashing the 8.1 and it has given me error in all files by fastboot
Click to expand...
Click to collapse
can you post the screenshots?
Its most likely you dont have adb installed,
You can get it from here https://forum.xda-developers.com/showthread.php?t=2317790
nfraccar said:
Of course you enabled camera 2 API right?
Click to expand...
Click to collapse
not yet, i am testing stock rom right now.
rendroid15 said:
not yet, i am testing stock rom right now.
Click to expand...
Click to collapse
Then Google Cam can't work. Activate camera 2 API if you have time and try again Google Cam!
rendroid15 said:
nice !
now for the wifi and data
i need you to flash the same rom using fastboot not twrp
The File explorer setting was just to see if the file has any extensions. So if you dont see an extension then add .img in the end.
I think there is a bug in twrp that is causing wifi and data to not work.
Click to expand...
Click to collapse
Well crap. Just when I thought everything was good. The file does the .img extension but for some reason adb just can't find it even though it's literally in the same folder. I'll try again and let you know.
Cirus61 said:
Well crap. Just when I thought everything was good. The file does the .img extension but for some reason adb just can't find it even though it's literally in the same folder. I'll try again and let you know.
Click to expand...
Click to collapse
try this, copy all files directly in adb folder, get rid of folder "Minimal adb drivers", the spaces in that folder name may be the problem.
If that doesnt work then just rename the rom name to rom.img and use that in fastboot command.
Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.
if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673
you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload
Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.
faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.