Related
Hello all,
I really need help for my ZE500KL. In summary, it stucks on ASUS logo and bootloop. I can't get to welcome screen.
It is not rooted, i've never touched to the original system. I got this problem after an update from OTA. The update was not interrupted for information.
I can get to the recovery menu, can do a wipe data/factory reset, but it solves nothing. Same problem.
I've tried :
- apply update from adb but this stops at 46% and failed with an error like E:failed to verify the whole-file signature
- apply update from microSD but it stops and failed without error message
I don't know if there is another way to fix.
Thanks
Bro go to the asus site and download the whole rom nd flash it thru recovery.
M also had a same problem.
So let me know nd which variant u hav?
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Fus_XDA said:
Thanks for the reply.
When i said "I have apply update", this means that i've downloaded zip file from Asus website, and loaded it via the recovery but the process stops at 46%.
Maybe it will work for a custom recovery like CWM or TWRP but as i know, there is not a working CWM or TWRP for ZE500KL at this time. Maybe.
For me, the stock recovery don't work for loading the zip file from ASUS. It says something like : Unable to verify the whole-file signature, Process failed
Click to expand...
Click to collapse
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
kvantor said:
If your device stops at logo this means that it boots into fastboot mode. I`ve had a same problem. You can take this adb driver . After installing you need to put in C:\adb file boot.img from archive which you dowloaded from official asus.com, then run cmd.
Code:
cd c:\adb
and last command will be...
Code:
fastboot boot boot.img
try it.
Click to expand...
Click to collapse
I tried. It doesn't work.
I proceed like this :
1- I've booted the device in recovery mode, connect it to PC and uninstall the device and his driver in to the device manager. I do the same in fastboot mode
2- I've installed the 15 seconds adb ver 1.43. As it is recommanded, I force install of drivers to "Android ADB interface" for recovery mode and "Android Bootloader Interface" for fastboot mode. At this time, adb detects the device via "c:\adb> adb devices"
3-I've extracted the "boot.img" from UL-ASUS Z00E-WW-12 8 5 106-user.zip from Asus Website
4-No problem to proceed with "c:\adb> fastboot boot boot.img" BUT that's all.
--> The device boots, passes the ASUS logo with the powered by android at the bottom", arrives to the second ASUS logo (the one animated), then there are messages "Android upgrading, optimising 1 of 1 app", "Starting apps", then it reboots, and bootloops .... again and again. I have to take out the battery to turn it off.
Have you tried downloading the full ROM image from the ASUS support website again? (yes, download again and try flashing your device again). Usually when it says something about signature verification failed, it is due to the incomplete download of the ROM image (corrupted), or that it has been modified.
Do report back the results.
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Download Link (for your convenience): http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500KL/UL-ASUS_Z00E-WW-12.8.5.222-user.zip
Click to expand...
Click to collapse
I's been thinking to this ...
I've downloaded 3 times the ROM from asus website. The download procees has been interrupted because of internet problem but i was able to resume after. I've even downloaded previous version. I am able to extract the zip file to my computer without error like cooupted file or CRC..
I need to know if other persons have the same problem exactly with this ZE500KL because, i have recently done the same thing with my ZE551ML and i had no problem.
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Rizzed said:
Have you tried flashing the previous updates (software versions) instead? Could be a "bogus" update.
Click to expand...
Click to collapse
Yes. Same problem with .172
I was been delighted when i see this TWRP for ZE500KL http://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704 and it works,
But my joy was so short.
It says that it was unable to install the ZIP file because the ZIP is for WW_PHONE, and my phone is an OMNI_ZE500KL !!! What is this ? Never heard about it before. What's weird with this AUS ZIP file !!!??
Can you try to ADB Sideload the ASUS ROM?
sagematt said:
Can you try to ADB Sideload the ASUS ROM?
Click to expand...
Click to collapse
Yes. I've tried every way to install.
Fusxda said:
Yes. I've tried every way to install.
Click to expand...
Click to collapse
Open a thread on ZenTalk: http://www.asus.com/zentalk/
Never heard about this OMNI SKU before.
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
up
Rizzed said:
If someone else has the same exact phone with you with a different SKU (perhaps WW?), you could try asking him to backup the recovery.img on his phone for you to flash. After that, just flash recovery via fastboot and you should be good to go.
Click to expand...
Click to collapse
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
2xboy said:
Hello , do you find the solution i have the same problem
could you help me , thanx a lot :good:
Click to expand...
Click to collapse
Stock recovery (and TWRP):
https://github.com/sabpprook/android_device_asus_ze500kl/releases
Guys I Found The Solution For This Problem :
1-Flash TWRP Recovery From The Link : https://github.com/sabpprook/android_device_asus_ze500kl/releases
2- Wipe Data and Cache And dalvik Cache and Very Important (Wipe System).
3-Flash Back The Stock recovery From The Same Link Above.
4-Flash Your .zip Stock Frimware From The Link : https://www.asus.com/support/Download/39/1/0/20/KsY29RCpsJ2bea9O/32/
5-Please if this Helped You Press Thanks! Button And Enjoy.
The Trick: Stock Recovery Cannot Wipe System But TWRP Can.
P.S: You Cannot Flash The Frimware From TWRP ... It Will Give An Error.
Enjoy
I find answer
Bro, download this file failobmennik.usite.pro/updater-script.noext and change \META-INF\com\google\android\updater-script
Hi,
I'll test it, and will give feed-back
Thanks
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I used to be difficult to use TWRP menu, then the menu advanced Wipe Wipe then select all topics except the MicroSD and then manage Otg Wipe it !! Flash Stock Recovery to be done to make Flash official rom first official rom files onto the MicroSD example, I was. UL-ASUS_Z012D-WW-13.20.10.79-user. To change its name Then insert the MicroSD MOFD_SDUPDATE Recovry Mode, then select update to zip and then choose File. "MOFD_SDUPDATE.zip" I will wait a little longer for the update firmware and set up virtually everything is not lost through the OTA.
ผมเคยเป็นแก้ไม่ยากใช้ TWRP แล้วเข้าเมนู Wipe แล้วเข้าเมนู advanced Wipe ทำการเลือกทุกหัวข้อ ยกเว้น MicroSD และ Otg แล้วจัดการ Wipe ครับ!! เสร็จแล้วให้ทำการ Flash Stock Recovery เพื่อที่จะใช้ Flash official rom ก่อนอื่นทำไฟล์ official rom ลงไปยัง MicroSD ผมยกตัวอย่างเป็น UL-ASUS_Z012D-WW-13.20.10.79-user ให้เปลี่ยนชื่อเป็น MOFD_SDUPDATE แล้วนำใส่ MicroSD แล้วเข้า Recovry Mode แล้วเลือก update to zip แล้วทำการเลือกไฟล์ "MOFD_SDUPDATE.zip" แล้วรอสักพักอาจจะนานหน่อยเพราะเป็นการ update firmware ข้อมูลและการตั้งค่าทุกอย่างจะไม่หายเสมือนอัพผ ่าน OTA
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
I got the same issue, where did you get these files?
roosevelt84 said:
I got the same issue, where did you get these files?
Click to expand...
Click to collapse
I have the exact same error. Same here. Please someone can post download link.
SuperDizor said:
Hi guys,
I try to restore my Zenfone 3 with his original firmware downloaded from Asus website. [Version WW_V13.20.10.79]
When i restart my phone, i got the first warning to let us know the bootloader is unlocked but after i got this error.
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
If i try to flash with TWRP with Install Zip, i got this error:
Code:
...
This package is for "WW_Phone" devices; this is a "omni_ze552kl".
Updater process ended with Error: 7
Error installing zip file '/sdcard/Download/<nameOfTheZipFile>.zip'
Updating partition details...
...done
(sorry i can't post image)
when i try fastboot recovery, it stuck to <waiting for device>.
This is my first time with Android, and rooting and all this sh*t. I'm coming from iOS jailbreak side but iTunes couldn't help me.
If you need to know anything, let me know.
I would greatly appreciate if anyone could help me.
Thanks!
SuperDizor
*English is not my first language, sorry about that*
Click to expand...
Click to collapse
I found a solution, and now my ZF3 is working but its showing a second screen with a error when it boots.
1 - download a zip file rom from asus site
2 - open it with winrar or another of your choice
3 - go to \META-INF\com\google\android
4 - open the updater-script with a text editor
5 - search for all the words WW_Phone and replace it for omni_ze552kl
6 - save the change and close, update the file inside the compressed zip
7 - put the zip rom inside your phone and flash it through twrp, done!
*sorry about english, its not my native lang.
Hi SuperDizor,
The issues you are having are both caused by the installation of TWRP 3.0.2. that was compiled for the Zenfone 3 using omni_ze55kl as the device type instead of WW_ZE552KL or CN_ZE552KL. I assume that the person that compiled it tried to make TWRP as universal as possible (instead of making two different versions, one for each device type - the TWRP code would have been the same except for this string...). However, the updater checks for this device type string and fails (unless you modify the updater config file as described in the post above). This is also why flashing stock recovery solved your issue.
The second error message you have, the one with dm-verity not being in enforcing mode was caused by having you install TWRP and allowing it to modify the system partition. This was necessary in the past but not anymore. When you flash TWRP, the first time you start it, it ask for your permission the make the system read-write, and you should refuse, as TWRP will function anyway and you will not get the dm-verity error. The dm-verity thingy is a software module in the bootloader (aboot to be precise) that checks the integrity of the system partition. TWRP has to force it in non-enforcing mode since it modifies the system partition and your device would not boot if it left dm-verity in enforcing mode. When you don't let TWRP modify the system partition (ie staying read-only), it does not change the dm-verity mode and you don't get warning messages. Don't worry, TWRP will still enable you to root your device and do whatever it does even if it is in "read only" mode.
Hope this helps !
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same.
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
Niemer said:
I just got this error seemingly out of the blue on my ZenFone 3 Laser. I didn't do anything, just walked up and it was showing this screen
Code:
The dm-verity is not started in enforcing mode and may not work properly
To learn more, visit: g.co/placeholder
Haven't rooted, unlocked bootloader, or tried to install any rom manually.
Click to expand...
Click to collapse
Same happened with my device too. How did you fix it? Can you please let me know the procedure for same. Thanks
SuperDizor said:
I was able to fix my phone with flashing both boot.img and recovery.img with stock image and i used WW-13.16.5.36 firmware to flash and it's worked.
Thanks for the help JadeKubPom
Click to expand...
Click to collapse
but how to flash? its not booting in recovery mode.
This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M
Reserved for future use
can i follow this step for ZE520KL ?
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.
DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me
Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome
DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP
Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.
I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!
Hey Guys. This guide will help you if
1. If Using Custom Rom and want to revert to latest stock rom.
2. If Stock Rom got corrupted or became laggy.
3. You want to reinstall stock rom.
Warning:
1. Method 1 require unlocked bootloader. If you want to unlock then go Here . Method 2 doesn't. Don't worry.
2. This will clean your phone just like new phone.
3. First read the post twice carefully then proceed.
4. ALL .bat FILES TO BE RUN IN FASTBOOT MODE ONLY, IF YOU DON'T KNOW ABOUT FASTBOOT MODE THEN GOOGLE "HOW TO GET FASTBOOT MODE IN ASUS ZENFONE 2
5. I may change name of files in folder. Use common sense to identify them.
Pre-requisites:
1. Charge your phone atleast 60%.
2. Backup any important data you might not wanna loose to either sd card or usb drive or pc.
3. Copy the rom zip in the sd card of your phone. (The one with size in GB)
4. Android USB Driver should be installed already, if it is not then install all drivers in the "Drivers Folder".
5. Enable USB Debugging.
For that go to "Settings" ,Scroll to bottom goto "about", goto "Software Information", tap "Build number" upto 7 times or till it
says "You are a developer now". Then go to "Settings" you will find "Developer Options", open it and enable "USB Debugging"
4. Common sense, patience.
Download Link:
For Method 1
Click here Android Filehost
Download these folders: TWRP, STOCK RECOVERY, STOCK ROM, DRIVERS
For Method 2
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Procedure:
METHOD 1Step 1. Flash TWRP recovery if not installed by using "TWRP.bat" (Given in twrp folder) in fastboot mode or bootloader mode whatever you call it.
Step 2. Go to Twrp recovery then choose "wipe" then choose "Advance wipe" and tick everything except "SD card or external sd card". then swipe to wipe.
Step 3. Go to fastboot/bootloader mode and flash stock recovery running appropriate .bat file. It is given in "Stock Recovery" folder.
Step 4. When the command executes from the above step, Go to "recovery" by pressing volume down button, then press "power" button.
Step 5. You will see a dead android logo. Nothing else. Then go to stock recovery options.
If you don't know how then use following methods
Method 1:
When you see a dead android bot with an error press and hold power button, then (while holding power button) quickly press Vol up and release and then release power button..
Method 2:
Go to fastboot mode. Connect your device and open command prompt there. Then Type
Code:
fastboot erase cache
Step 6: You should see stock recovery options. Then choose "Update from sd card" and select the rom zip you pasted in SD card.
(If you don't have sd card, then paste rom in internal memory and don't tick "internal storage" in twrp in step 2) But micro
sd is preferable.
Step 7: Wait. Your phone may take 20-30 or more minutes. So leave it on charging.
METHOD 2Step 1: Download and Install all drivers given in download folder. Download RAW firmware for your phone. See above in download links.
Step 2: Install "ASUS FLASH TOOL"
Step 3: Go to fastboot/bootloader mode on your phone. Run asus flash tool, select your phone model and browse for the raw firmware. Check wipe all data. And start the process.
Step 4: Wait for program to say successful. If it takes more than 30 minutes. Disconnect your phone and check phone if rom installed or not.
If this process does not work. Then switch methods.
If you have any questions, problems .. Just Comment it.
Every Suggestion welcomed. Also you can join telegram group to get help and help others.
MOD EDIT: LINK REMOVED
If the guide works for you or you want to thank me for development of tools then you can donate me via
Paypal paypal.me/KapilTapsi (You can donate any amount, It will be of great help)
FAQ
1. Having problems with device connection? like waiting for device.
Sol. Make sure you have enabled USB Debugging (Not applicable for BL Unlocking and TWRP Flashing)
Uninstall all drivers previously installed on computer(every driver of any device)
Reboot your computer. And then install all drivers given in the driver folder.
If the problem persists, try different computer and different usb cable.
2. Facing permission denied in fastboot mode or while running script files.
Sol. Try disabling your lock screen security to none.
File Credits:
1. RealYoti
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Would it not be easier to get the stock raw image and just flash it with the asus flash tool?
Click to expand...
Click to collapse
Thanks for suggestion. But the reasons are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Kapil Tapsi said:
Thanks for suggestion. But the reasons are
First thing is stock raw image of latest version is very difficult to find.
Second thing sometime asus flash tool stops responding. So you have to wait again for 30 minutes. Also it doesn't show progress sometimes.
Click to expand...
Click to collapse
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Click to expand...
Click to collapse
It is a guide only. Users are free to choose from where to download. Thats it. I only shared my collection.
E: footer wrong
E: footer wrong
Installation aborted
I need your help!
I follow the instructions in Method 1 but the device give me this error message when I try to update via SD-card...
May I know whats the solution?
Rom used: Fastboot Rom WW-4.21.40.327
Thank you very much!
kenbo111 said:
No offense meant. But the entire collection of raw files are here: https://forum.xda-developers.com/showthread.php?t=3448966
As long as you have the correct drivers (which you need for your process too) the AFT will get the job done in one easy step.
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
Thanks, finally got it
Hey...when I get to part 6 I get this Error >>
footer is wrong
signature verification failed
installation aborted
Hey..I also Tried Flashing with the method 2 it was installing but i got an error after
Man, this thread saved my ass. thank you for all your time all!
I have the Asus Zenfone 2 ZE551ML with sound issues, (it's only when the phone rings that the speaker works) and I put it into recovery mode to wipe cache/data, but it got stuck while doing that and I forced it off. But now, it's stuck at the Asus Boot logo with the rotating icon underneath.
Please help!!!!
Hello, my 551ml has stock LP, it's rooted with bootloader unlocked and Xposed installed. If I want to install the latest MM with through the raw flashing tool, should I install the MM bootloader first or it is included into the raw file? Thank
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
stevegtrlmk said:
just trying to revert back to locked bootloader and stock recovery once I have wiped all data with twrp and go to bootloader how do I actually flash stock rom noob thanks
Click to expand...
Click to collapse
use asus flash tool
damn my asus flash tool says error flashing image failure.... (remote not allowed to flash this partion)
ow btw i already bricked it cause it only does boot fastboot lol no more android
how do i flash it back again i need to send the phone back to amazon by 18/05 lol i mean i can just send it back and say also that it wouldnt boot cause i tried to reset it to get my touchscreen to work but yeah lol dont want them to refuse my retour
No way to simple flash the stock rom through/keeping twrp in the device, like I do with other Custom Roms?
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
euphrodil said:
Ok. humm, in AFT, it recognize my phone. (there is no OS on it), i choose the good model, i choose the good firmware, but i got this error in a box
"Can't open file 'SERIALNUMBER_frp_request_server_log.txt' (error 5:denied access)" i can only press OK
and now the button under "state" is red and under description, it's " check the detected serial number failure (not found the device of "SERIALNUMBER") "
you understand the i've replace the real serial number by SERIALNUMBER in those lines.
Anyone ever had this problem?
Click to expand...
Click to collapse
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Kapil Tapsi said:
Try manual flashing then. Not the aft flashing
Sent from my MI MAX 2 using Tapatalk
Click to expand...
Click to collapse
Ok thanks, i'll look for a thread that explain this.
euphrodil said:
Ok thanks, i'll look for a thread that explain this.
Click to expand...
Click to collapse
did you find any?
i want to remove the lineageos and install latest stock LP but i have no clue how to do it
I followed step by step: https://clickitornot.com/install-twrp-recovery-and-root-sony-xperia-x-compact/
(the xda guides lingo was hard to understand and follow, I'm a noob at rooting sony phones. I don't have previous knowledge so I followed the above)
-Got stuck in TWRP recovery mode after following the link posted.
-Looked into it and read something about a boot.img missing?
-Downloaded boot.img from here: https://forum.xda-developers.com/x-compact/how-to/stock-8-0-root-recovery-t3747479
-Flashed recovery on boot_32.img via TWRP, now screen stays at white Sony logo. Cannot go into TWRP at all, computer doesn't recognize phone and Sony flash tools does not recognize phone.
I just need this phone to root and turn on so I can get my old photos and conversation back. :crying:
Been stuck for 12 hours...any help is much appreciated!
1 - what do you ultimately want, rooted stock rom, custom rom, or...?
2 - what was the state of your phone when you started, (fully stock, which fw version, etc)?
3 - Did you do anything else to it besides flashing twrp and flashing boot.img?
levone1 said:
1 - what do you ultimately want, rooted stock rom, custom rom, or...?
2 - what was the state of your phone when you started, (fully stock, which fw version, etc)?
3 - Did you do anything else to it besides flashing twrp and flashing boot.img?
Click to expand...
Click to collapse
1. Anything, I simply just need it to work so I can use a software to get my lost data. In order to get my data back the phone needs to be rooted under the prerequisites for the Dr. Fone software.
2.Fully stock android 8.0
3. No, it was fine and I went through dozens of threads and youtube tutorials. It kept going into TWRP exclusively until I flashed boot.img now it just boot loops or crashes on the white sony screen.
(BTW, my phone finally has been recognized by Flash Tools (Emma). I have updated it via Emma but it has done absolutely nothing.
ThisAintEz said:
1. Anything, I simply just need it to work so I can use a software to get my lost data. In order to get my data back the phone needs to be rooted under the prerequisites for the Dr. Fone software.
2.Fully stock android 8.0
3. No, it was fine and I went through dozens of threads and youtube tutorials. It kept going into TWRP exclusively until I flashed boot.img now it just boot loops or crashes on the white sony screen.
(BTW, my phone finally has been recognized by Flash Tools (Emma). I have updated it via Emma but it has done absolutely nothing.
Click to expand...
Click to collapse
So the whole Emma process completed successfully, but the phone still won't boot? That's strange, because Emma usually overrides everything, (including your userdata, I think, so if you wanted to save it, that may have been the wrong thing to do). If all you did was flash a bad boot img, then re-flashing stock fw should solve the problem, but you might lose your data with Emma, so Androxyde Flashtool might be better choice, since it gives you the option.
Did you unlock the bootloader? If not, then nothing is going to work. If you did, then it will be easy to get the phone booted again...
levone1 said:
So the whole Emma process completed successfully, but the phone still won't boot? That's strange, because Emma usually overrides everything, (including your userdata, I think, so if you wanted to save it, that may have been the wrong thing to do). If all you did was flash a bad boot img, then re-flashing stock fw should solve the problem, but you might lose your data with Emma, so Androxyde Flashtool might be better choice, since it gives you the option.
Did you unlock the bootloader? If not, then nothing is going to work. If you did, then it will be easy to get the phone booted again...
Click to expand...
Click to collapse
The phone itself has been factory reset (long story short x compact said my password was incorrect and factory reset, itself after numerous tries, even though I only have one password) so I know my info is gone but the software can get the most of the things I want.
Yes, boot loader is unlocked. I have basically rooted it but the last step of actually getting to use it is out of reach.
ThisAintEz said:
The phone itself has been factory reset (long story short x compact said my password was incorrect and factory reset, itself after numerous tries, even though I only have one password) so I know my info is gone but the software can get the most of the things I want.
Yes, boot loader is unlocked. I have basically rooted it but the last step of actually getting to use it is out of reach.
Click to expand...
Click to collapse
For TWRP recovery, you need to flash via fastboot. I wasn't clear what you were saying about how you did it before. You should,
- Download TWRP img file (there is official TWRP for xc, so download the latest from TWRP site)
- Open command prompt in the directory you downloaded it to
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type
Code:
fastboot flash recovery (name of file).img
Then you can boot into recovery by powering off, and holding volume down while powering on. Then do a reset in recovery.
Now you'll need to flash a boot img...
You said it was stock 8.0, but do you know if it was the latest update? (fw ending in. 118) If so, and if your system files are still intact, then you should be able to download this - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA - (it's a boot img), and flash it with fastboot. So,
- Download the boot img file
- Open a command prompt in the directory you downloaded it
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type in command prompt,
Code:
fastboot flash boot (name of file).img
- Reboot
I'm assuming that since you used Emma already that you have drivers installed, so should work. If the commands complete successfully, but your phone still doesn't boot, then probably system is messed up, and you'll have to flash a new rom.
levone1 said:
For TWRP recovery, you need to flash via fastboot. I wasn't clear what you were saying about how you did it before. You should,
- Download TWRP img file (there is official TWRP for xc, so download the latest from TWRP site)
- Open command prompt in the directory you downloaded it to
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type
Code:
fastboot flash recovery (name of file).img
Then you can boot into recovery by powering off, and holding volume down while powering on. Then do a reset in recovery.
Now you'll need to flash a boot img...
You said it was stock 8.0, but do you know if it was the latest update? (fw ending in. 118) If so, and if your system files are still intact, then you should be able to download this - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA - (it's a boot img), and flash it with fastboot. So,
- Download the boot img file
- Open a command prompt in the directory you downloaded it
- Connect the phone in fastboot mode, (power off > hold volume up while connecting cable and don't let go of the button until you see blue led)
- Type in command prompt,
Code:
fastboot flash boot (name of file).img
- Reboot
I'm assuming that since you used Emma already that you have drivers installed, so should work. If the commands complete successfully, but your phone still doesn't boot, then probably system is messed up, and you'll have to flash a new rom.
Click to expand...
Click to collapse
Thank you, the good news is I can finally get back into TWRP, so that's a relief! I appreciate you for saving me there!
I followed the instructions with the boot.img with the following script
max download size of 536870912 bytes
sending 'boot' (17220 KB)...
OKAY [ 0.556s]
writing 'boot'...
OKAY [ 0.113s]
finished. total time: 0.673s
But I'm back to square one with the screen prompt "your devices has been unlocked and cant be trusted. Your device will boot in 5 sec" with the Sony white screen back to the "your device has been unlocked" screen and then it freezes at the Sony white screen. The only way i can turn off my phone from here is Power button + volume up
ThisAintEz said:
Thank you, the good news is I can finally get back into TWRP, so that's a relief! I appreciate you for saving me there!
I followed the instructions with the boot.img with the following script
max download size of 536870912 bytes
sending 'boot' (17220 KB)...
OKAY [ 0.556s]
writing 'boot'...
OKAY [ 0.113s]
finished. total time: 0.673s
But I'm back to square one with the screen prompt "your devices has been unlocked and cant be trusted. Your device will boot in 5 sec" with the Sony white screen back to the "your device has been unlocked" screen and then it freezes at the Sony white screen. The only way i can turn off my phone from here is Power button + volume up
Click to expand...
Click to collapse
So now you can just decide if you want to go the route of stock rom or custom. Quickest choice to get the phone booted would probably be Omni or something. Just download the rom, download the oem file, and flash in fastboot. Check the Omni threads in "Roms" forum... If you wanted to go stock, I would suggest Androxyde Flashtool, but would be a few more steps... Or you could try Emma again...
levone1 said:
So now you can just decide if you want to go the route of stock rom or custom. Quickest choice to get the phone booted would probably be Omni or something. Just download the rom, download the oem file, and flash in fastboot. Check the Omni threads in "Roms" forum... If you wanted to go stock, I would suggest Androxyde Flashtool, but would be a few more steps... Or you could try Emma again...
Click to expand...
Click to collapse
I tried Emma again but my phone is still frozen on the white Sony screen. I checked out the ROM threads but the "download weekly" links are down for both Pie 9.0 and Oreo 8.1
ThisAintEz said:
I tried Emma again but my phone is still frozen on the white Sony screen. I checked out the ROM threads but the "download weekly" links are down for both Pie 9.0 and Oreo 8.1
Click to expand...
Click to collapse
Strange - I wonder what's going on... I might have a zip I can upload. Meanwhile, maybe try Lineage - https://forum.xda-developers.com/x-compact/development/rom-lineageos-16-0-xperia-x-compact-t4080903
levone1 said:
Strange - I wonder what's going on... I might have a zip I can upload. Meanwhile, maybe try Lineage - https://forum.xda-developers.com/x-compact/development/rom-lineageos-16-0-xperia-x-compact-t4080903
Click to expand...
Click to collapse
Thank you for your help! I checked out the thread but I'm not advanced enough to understand the steps without it being written out as I'm still new to this. Is their any links or tutorials you would recommend? My apologies!
ThisAintEz said:
Thank you for your help! I checked out the thread but I'm not advanced enough to understand the steps without it being written out as I'm still new to this. Is their any links or tutorials you would recommend? My apologies!
Click to expand...
Click to collapse
- Download the zip - https://drive.google.com/open?id=14iXmvLOMXLoZdJoCahcRhBzbUr1Eu7gw (There are 2 options, just pick one - one's a little newer)
- Copy to phone's SD card
- Boot to recovery
- Choose "wipe data/factory reset"
- Choose "install", and select the zip file you downloaded
- Reboot
There are more options, but I think you want to just get the phone to boot at this point. You can do more later if you want...
BTW - what is happening when you flash with Emma? I haven't seen it ever flash successfully, but not work on the phone. Are you getting errors?
levone1 said:
- Download the zip - https://drive.google.com/open?id=14iXmvLOMXLoZdJoCahcRhBzbUr1Eu7gw (There are 2 options, just pick one - one's a little newer)
- Copy to phone's SD card
- Boot to recovery
- Choose "wipe data/factory reset"
- Choose "install", and select the zip file you downloaded
- Reboot
There are more options, but I think you want to just get the phone to boot at this point. You can do more later if you want...
BTW - what is happening when you flash with Emma? I haven't seen it ever flash successfully, but not work on the phone. Are you getting errors?
Click to expand...
Click to collapse
Much appreciated! I will try that out soon. Regarding Emma it seems pretty useless, unless I'm missing something. Every time I use it, it says it's successful but nothing changes.
LEVONE1 YOU ARE THE MAN!!! I cannot thank you enough! It worked! You made my day, I appreciate your patience and willingness to help a stranger out even when you didn't have to!
ThisAintEz said:
LEVONE1 YOU ARE THE MAN!!! I cannot thank you enough! It worked! You made my day, I appreciate your patience and willingness to help a stranger out even when you didn't have to!
Click to expand...
Click to collapse
Glad to hear it... It's been done for me more than once, so....
Maybe your happy with Lineage, but if you're feeling ambitious, you can start messing around with Androxyde Flashtool, and getting back to stock, and you can try my eXistenZ port - https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917 - I think eXistenZ is the best rom for this phone, (probably for Sony phones overall). The downside is that it is based on stock, so no updates since 2018 for XC...
The processes are a bit more complicated, so might take some time / learning to get it down, but with TWRP, you can always make a quick backup, and flash right back to where you were any time...
levone1 said:
Glad to hear it... It's been done for me more than once, so....
Maybe your happy with Lineage, but if you're feeling ambitious, you can start messing around with Androxyde Flashtool, and getting back to stock, and you can try my eXistenZ port - https://forum.xda-developers.com/x-compact/themes/existenz-xc-t3867917 - I think eXistenZ is the best rom for this phone, (probably for Sony phones overall). The downside is that it is based on stock, so no updates since 2018 for XC...
The processes are a bit more complicated, so might take some time / learning to get it down, but with TWRP, you can always make a quick backup, and flash right back to where you were any time...
Click to expand...
Click to collapse
Will do. Cheers!