Database Users

Help me Zenfone 2 laser ZE500KG Bootloop!!!!!

my zenfone 2 laser is bootloop! (ZE500KG)
I try flash file TWRP but I can't do that!
It say ''Failed'' > '' zip verification failed''
anyone know how to fix it faulty?
TWRP 3.0.2-0 (TeamWin) for zenfone 2 laser!
ALSO DO NOT FLASH WITH ADB! Help me. :crying::crying::crying::crying::crying:

Hey,I dont know if u found the answer yet
TWRP can just flash unofficial rom
not official rom
if you want official rom
you have to use oem recovery...not twrp
I m look for answer too...that is all i know

TWRP can install both Stock Or Custom Roms...it is based upon the update-script...

I had an issue where I could install any of the cyanogenmod 13 nightly updates past June 14th on my phone, a ze551kl. I resolved the issue by updating to the OEM ROM 21.40 from the Asus website. Hopefully this is helpful.
I downloaded the following files from the?*Asus website and copied them into the?*SD Card?*of my phone:
- UL-Z00T-WW-1.16.40.763-user.zip
- UL-Z00T-WW-1.17.40.1234-user.zip
- UL-Z00T-WW-21.40.1220-1615-user.zip
- UL-Z00T-WW-21.40.1220-1794-user.zip
I then used fastboot to install the stock recovery image. After installing the stock recovery, I rebooted into recovery mode and installed 1.16 and restarted the phone. After the phone booted into 1.16, I rebooted into recovery and installed 1.17, etc . . . until I updated to 21.40.1220-1794.
After the last update, I replaced the stock recovery with TWRP and l was able to install the latest nightlies. It seems like installing 21.40 was the key to fixing this issue.
An important side note : I downloaded the WW ROMs because my phone is a WW region. If your phone is from a different region, you will need to download the appropriate ROMs.
Good luck with your phone.

Help need Zenfone 2 laser ZE551KL STOCK recovery.img & working sideload ROM .zip

Hi all, I somehow borked my Z00T and it's stuck on ASUS logo spinner now.
ZE551KL, OTA MM upgrade which was working..
bootloader not unlocked (can't use ASUS Unlock current version w/MM)
(I tried to do a downgrade to Lollipop, didn't take as recovery rejected a downgrade. Then, in my lack of sleep, I tried isntalling SuperSU via TWRP and I think that's where it all went wrong.)
I can't find a STOCK recovery.img for Z00T online (just Z00L)
TWRP for Z00T can't see my microSD for some reason so I can't sideload from card; ADB mode in TWRP isn't see by my Windows machine either, so I have no way to get a working ROM back on the phone!
(I've tried the CynanogenMod recovery, which will take a sideload but any ASUS *-user.zip image fails with "Error: whole-file signature not valid" or something like that.)

for working sideload reboot pc and no open any program

Recovered with CM13 Z00T recovery.img and complete reflash with CM13
Whew. I was really scared there for a bit. The only thing that seemed to work was going completely CyanogenMod 13 (recovery and latest stable install).
Luckily I like CM, and the ZenUI Launcher and apps were backed up with all my other apps and re-installed reasonably well it appears.
[Edit: also thanks very much to the team maintaining Open GApps, I was able to install GApps CM13 for Android 6.0 smoothly after a factory reset of CM13 post-install.]
Big lessons I learned:
* DO NOT try to downgrade from Marshmallow to Lollipop on Zenfone 2 Laser, and definitey DO NOT install SuperSU v2.46 while on Marshmallow.
* Research further than I did before trying a downgrade, upgrade, or Unlock -- if the Unlock isn't for your EXACT stock ROM version it won't work.
* Also don't overwrite stock recovery.img via fastboot, as no one seems to have a real ZE551KL stock recovery.img for download ou there. Only switch to a new recovery loader when once you're SURE you're ready to go permanently down the road with an alternate distro like CyanogenMod.
* Finally, TWRP 3.0.2.x for this phone seems to have sketchy ADB/USB support, at least on Win7 x64, as I wasn't able to use it to successfully connect for adb sideload attempts at all.
I'd still like to understand exactly what the failure messages mean when trying to sideload other ASUS UL-Z00T*-user.zip images ("Failed whole-file signature" or whatever that was)... I don't understand the signing process of vendor-provided ZIPs: why would the CM13 recovery flash its own CM13 release but refuse any others (and TWRP for that matter)? Do different release distributions have their own certs that have to match what the recovery.img expects, or ??

Has someone the stock recovery for ze551kl z00T 21.40.1220.1615 ?
Sent from my ASUS_Z00TD using XDA-Developers mobile app

Chicken & egg situation caused by system & recovery SKU mismatch from the factory

Chicken & egg situation caused by system & recovery SKU mismatch from the factory
Hi All,
I've been stuck on this for 2 days now and I thought maybe it would be quicker for someone here to point me in the right direction.
This thread isn't for my model of phone but it does help explain my problem in the most clear way.
https://www.asus.com/zentalk/thread-14962-1-1.html
This is what I have:
Asus Zenfone Max ZC550KL
- Z010D
- 8916
- 410
- 2GB
- CN Recovery
- WW System
The phone is stuck on android 5.0.2 and never received the OTA updates. or it did, but failed. I think the reason the phone has so many issues with updates is because the supplier of the phone side loaded the WW system image on top of a CN recovery. Apparently this is a no no.
So now I'm trying to fix the problem but I seem to be trapped in a chicken and egg type situation. I need to change the recovery firmware from CN to WW. To change the recovery firmware I first need to unlock the boot loader. When I try to install the unlock boot loader apk through adb it says "[INSTALL_FAILED_OLDER_SDK]". To unlock the boot loader I need to first update android. But I can't update android over OTA because that isn't working. I also can't update the firmware by copying the latest version from asus (8916-13.8.26.110) to the SD card because android doesn't notify me that it has found this update in the root directory. I can't even update the firmware by pushing it through adb. It says something like 'Can't install WW firmware on a CN phone'. Lastly I have also tried using the ASUS flash tool but that was unable to extract the firmware.zip. Apparently I need a raw firmware zip for aft to work but those are hard to come by.
I'm thinking my only option would be to either find an Asus boot loader unlocker that works on android 5.0.2 and the Z010D. Anyone know if this exists?
or force the normal asus boot loader unlocker to install on android 5.0.2. Anyone know if this is possible?
or find a raw firmware zip for the z010d to flash using AFT. Anyone seen this?
Any other suggestions?
Edit: I figured it out. Follow the instructions for using AFT here https://ainotech.com/how-to-flash-firmware-asus-zenfone-max-zc550kl-root-custom-twrp-recovery/
I used AFT v0.34 because the newer versions either couldn't see my phone or couldn't handle the zip file.
I also flashed the old v12 firmware they have listed because I couldn't find a newer version in raw format. (AFT requires raw zips). But it doesn't really matter if it's an old version because once AFT has flashed the WW recovery, you can freely update to whatever WW version you want using traditional methods. I didn't even manage to get that version running because of boot loops. But the recovery works perfectly. From there it was simply a matter of downloading the v13 zip from the asus website and flashing it from the recovery menu.

Can't Install Custom Roms

Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.

Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
Most pie roms are base on the latest stock pie firmware, you probably need to flash that. Plus Ur twrp version is probably not the newest, all the links are available in the telegram group, and I'm not going to put them here out of respect for the devs. But .339 firmware is the Oreo firmware, I think the one u need to flash is the .050 firmware.
The telegram groups have them all and a little searching can give you all the links you need.

Azyaan124 said:
Hello,
Firstly, my device is the Asus Zenfone Max Pro M1 6GB Ram variant.
I was using the Pixel Experience rom as my daily ROM (I don't remember which build), it worked fabulously. But I hadn't updated it in a few months. So after enough procrastination I decided to update. I tried the regular software update method where you go to settings and check for updates, when it booted to TWRP recovery, it failed with an error. I thought it was because the update was the latest one and I was on an older build. So I tried doing a clean install by booting into recovery and wiping everything except internal storage. But the same error popped up again
I don't remember the exact error but it was an Error 7 and said something about the 'firmware version' required is 15.2016.1901.339 or newer. At first I didn't really get it and I kept trying again.
But after spending some hours it started making some sense and so I tried to install the required firmware. Even after doing so, the error kept showing up.
I thought it might be a ROM specific error. So I also tried Resurrection Remix (Pie version) but it yielded the same Error 7. This is the phone I use on a daily basis so I had to get it working somehow. So I flashed the stock ROM, the one that comes out the box. I flashed it using the flashall_AFT.cmd, I'm on the stock ROM now and it's obviously nothing like a custom ROM.
I also tried editing the updater script from the ROMs and deleting the part that was about the error (the first few lines). That didn't work either. The Error 7 was gone but another Error 6 popped up which said it failed to install.
I'd love to go back to using a custom ROM. It bugs me because I couldn't find any way to fix the error.
I'd greatly appreciate it if you can guide me step-by-step on how to install the custom ROM from where I am now i.e from the stock and fix the error.
I hope the above information suffices.
Thanks.
Click to expand...
Click to collapse
The latest Pixel Experience works great!
So you are on the Stock Firmware then.
1) Unlock the bootloader by Unofficial method (It will help when you want to relock it in future.)
2) Flash the latest TWRP Recovery.
3) Download whatever ROM you want to install and read all the requirements first! The error 7 you mentioned was the Firmware issue and could have been fixed by flashing the Firmware first and then the ROM.
GApps are not required for Pixel Experience as it comes with all the necessary Google Apps.

TWRP E1001 - Updater process ended with ERROR: 7

Hi,
I have recently decided to move my FIG-LX1 to Android 10 (previously using LineageOS 16.0), and after moving to LineageOS 17.1 (apparently unstable) and trying to install AOSP instead I seem to have screwed up something. I didn't manage to run the AOSP, but after playing around in recovery and fastboot, flashing ROMs via TWRP stopped working properly. Every time I try to flash any ROM using TWRP it shows "E1001: Failed to update system image" and "Updater process ended with ERROR: 7". AFAIK this error is connected to the device check and indicates that the ROM is not suitable for my device, but these are the same ROMs (i. e. LineageOS 16) i have previously installed with no problem (they are definitely compatible with my phone). I have also tried multiple TWRP versions (3.2.1, 3.3.1, 3.4.0) with no luck.
I have searched for this error a lot, but it's usually been connected with flashing on invalid devices, which is not the case here.
I would be grateful if someone could help me fix this error.
Thanks in advance!