Database Users

SOLVED: ZenFone 3 Laser (ZC551KL) dm-verity no boot

I set my phone down last night and came back to it with this screen and it will not boot into Android. It's not rooted or unlocked, the only thing I can think of is that an OTA killed it somehow, although I wasn't alerted to one or initiate anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I touch any of the buttons this screen comes up. Rebooting just starts the process over again.
I can see the phone with fastboot, and I tried flashing the factory boot.img again with no luck. I'm unable to find the factory recovery.img or system.img anywhere to give that a shot.

that was happened to my zenfone 3 5.5 too,
solution just flash firmware from asus with stock recovery

I can't get into the recovery to flash, unless I'm doing something wrong, I can only get to the bootloader and I cant find the proper .img files to flash with fastboot.

when I select reboot to recovery in fastboot it just reboots to the dm-verity screen again. It's like the recovery is just gone.

Just got off the phone with Asus, they were no help at all. I asked for the recovery image and they don't have one, what?
Does anyone know of a way to extract data from the internal storage in fastboot? I'd like to get a copy of that before I send it in...

SOLVED!
I created a modified UPDATE.ZIP using this method and flashed in fastboot like so:
Code:
fastboot flash system update.zip
That allowed the phone to boot to recovery, from there I flashed the firmware that is available to download from the Asus website in recovery and the phone booted up with no loss of data

So I did this with the newest firmware.
I can boot to recovery now (couldn't before just like yourself) but on the flash from fastboot I got
>target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2008017072 is not a multiple of
the block size 4096
erasing 'system'...
OKAY [ 0.010s]
sending sparse 'system' (0 KB)...
error: write_sparse_skip_chunk: don't care size 2008017072 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2008017072 is not a multiple of
the block size 4096
OKAY [ 0.030s]
writing 'system'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 0.060s
Meaning something failed.
I'm stuck on the ASUS boot screen
Tried a Factory Reset from recovery, still nothing.
I tried fastboot erase system -w
then reflashing the newest firmware, and still nothing
Since I can get to the recovery now, does anyone have a stock .img i can flash? or any other ideas?

Try flashing the firmware .zip from either the SD card or sideload in recovery.

Niemer said:
Try flashing the firmware .zip from either the SD card or sideload in recovery.
Click to expand...
Click to collapse
I will try that tonight. Thanks!

unknown partition 'wallox.zip
SOLVED
Hi, Your response has been very useful, but I still Have a Problem With regard. The Times tells me That does not FIND the zip file needed, other times: Unknown Partition 'wallox.zip
What's the Problem?
ps. Excuse my language

Niemer said:
SOLVED!
I created a modified UPDATE.ZIP using http://forum.xda-developers.com/showpost.php?p=69380242&postcount=3 method and flashed in fastboot like so:
Code:
fastboot flash system update.zip
That allowed the phone to boot to recovery, from there I flashed the firmware that is available to download from the Asus website in recovery and the phone booted up with no loss of data
Click to expand...
Click to collapse
the link is broken... can you please give the update.zip file. Thanks
[EDIT: update.zip found ! phone recovered... all ok, thanks ]

Niemer said:
SOLVED!
I created a modified UPDATE.ZIP using http://forum.xda-developers.com/showpost.php?p=69380242&postcount=3 method and flashed in fastboot like so:
Code:
fastboot flash system update.zip
That allowed the phone to boot to recovery, from there I flashed the firmware that is available to download from the Asus website in recovery and the phone booted up with no loss of data
Click to expand...
Click to collapse
link not works

help
hello to all guys, can someone give me the modified file fastboot flash system update.zip .. I'd be very grateful ..
Hello

edowar said:
that was happened to my zenfone 3 5.5 too,
solution just flash firmware from asus with stock recovery
Click to expand...
Click to collapse
how did you able to flash sir? Mine is coming on same dm-verity screen again and again.

akashnigam said:
how did you able to flash sir? Mine is coming on same dm-verity screen again and again.
Click to expand...
Click to collapse
Create the modified update as instructed here https://forum.xda-developers.com/showpost.php?p=69380242&postcount=3
I can boot into the setup dialogue now but the phone keeps shutting down on its own after a few seconds. Anyone experiencing the same thing?

Hi. I just made a post with a fairly comprehensive solution to the brick-problem that I had. If your problem is anything like mine was, then it should be useful.
https://forum.xda-developers.com/zenfone-3/help/unbricking-zenfone-3-ze552kl-dm-verity-t3563970
Much thanks to Niemer for being the inspiration for the solution. And thanks to everyone in the forum for asking good questions and posting good responses.

Niemer can you be so kind and upload your update.zip anywhere?

Lets open this tiny beast up!!!!

One click solution to unbrick and fix "no recovery mode" on zenfone 3 laser (zc551kl)
Just accidentally i found a "one click" solution to unbrick / fix loop boot / fix no recovery mode... My story started after i unlocked my Zenfone 3 Laser ZC551KL (Z01BDC) bootloader with the official tool from Asus. After i couldn't find any custom rom for this phone, i wanted to re-lock my bootloader to receive FOTA updates, so, i flashed boot.img and recovery.img from a Zenfone 2 Laser as i couldn't find files for mine, and i soft bricked it... boot loop, would only boot in bootloader, can't even access the "recovery" to apply the firmware update from sd card. After couple days of searching EVERY SINGLE WEB SITE for a viable, easy solution to fix my phone, and hundreds of files, firmwares, tools downloaded, i found it, right under my nose... Earlier in the process of looking for a solution, i downloaded a stock firmware zip (Asus_ZenFone_3_Laser_ZC551KL_WW-ZC551KL_13.40.104.1_20161014, who also included SP_Flash_Tool_v5.1720_Win. It's roughly 1.84 Gb, and 4.07 Gb after unzipping. So just download the zip, unzipp it and go into the folder and look for subfolder "Firmware+ Tool", where you'll find lots of files... look for "flashall_AFT", it's a "Windows Command script" file... double click it with your phone connected in fastboot mode, and wait. Will take 5-10 minutes, just be patient. I lost all my hopes while i was trying this just for sick of it, i left it "work" and went for a smoke... When i came back, my phone was on, with the Android Welcome setting screen.... I think i cried of happiness in my brain. Hope will help others fix the issue. Just to note, this method did not relocked my bootloader, is still unlocked, but what the hell, my phone is alive again. Aaaa, and even if i had Android 7.1.1 before, after this fix, i have Android 6.1 which i will keep till August 2018 when we'll get the Oreo for Zenfone 3 Laser. If you want to, after this fix, you can go to Asus page and download the latest version you'll like and install it manually. Here is the only link where you need to go and download the zip file to fix (it will redirect you to Mediafire for download): http://stockandroidrom.com/asus-zenfone-3-laser-zc551kl-usb-driver/
Wish you all the best.

Need Latest Firmware+Tool for my Asus zc551kl please. Update.zip and Rother method not working. Progress bar on bootscreen 2 sec delay and power off. I'm no update later 6.0.1 with unlocking bootlooader. Please,help me

Error mode: error 11 no recovery, error 2 failed to load

Help
I tried to relock my bootloader but when the device restarted it went straight to error mode.
I managed to boot straight back to full system but whenever I restart it goes back to error mode. I cant enter fastboot or recovery mode.
I sont know what to do now any help
Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.

How can I unlock bootloader without fastboot? If I attempt to enter fastboot or anything that requires reboot I end up on that screen.

Hmm....
Have you tried rebooting to fastboot using adb?

Johnny TDN said:
Try to boot it again in the full system and from there try to unlock your bootloader.
If you done that, reinstall the software.
Click to expand...
Click to collapse
Johnny TDN said:
Hmm....
Have you tried rebooting to fastboot using adb?
Click to expand...
Click to collapse
I tried but still get to error mode.....I have tried many times

Then i don't know anymore dude. Have you tried reinstalling the firmware using the 3 button method?

elliotn said:
I tried but still get to error mode.....I have tried many times
Click to expand...
Click to collapse
Hello
tested with the toolkit 0.0.0.12.
to see if he recognizes the phone.
he should at least write your serial number.
if that is the case.
you can use DC-unlocker. to open FRP and can be the bootloader.
just an idea.

Dc unlocker needs cash and it doesn t always work.

I am doubting buying DC,unlocker in case,it doesn't work and I will lose money.... I will try toolkit.

3 button upgrade doesn't work either.

I have the same problem after I tried to relock my bootloader using SRKToolHuawei-STABLE-V1.3-20160619 with my bootloader code.
Have you found a solution?
I can boot back into os b394 after I let the battery run out to 0%
I haven't found a way to repair my recovery and fastboot yet because rebooting into fastboot always get's me back to that first error
Func NO: 11 (recovery image)
Error NO: 2 (load failed!)
Then I have to wait for my battery to run out again
Any help to get fast boot and a working recovery back would be appreciated.

Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method

shankarjdhv125 said:
Use Huawei multi tool ,then flash system, custom,recovery image ,
If stock recovery opens then use Dload method
Click to expand...
Click to collapse
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..

Same problem for me
No way to shutdown the phone, someone have solved?
Now I'm waiting for the battery to full drain

Hi guys i ve made mistake because i wanted to update to latest release media pad m3 but i could not be able to boot to stock recovery after i flash recovery img extracted from update.app and second time i flash recovery2.img to erecovery partition and i got the same issue error Func No 11(recovery image) and Error NO 2 (load failed) . I also put the update.app to dload folder on sd card but update system is not starting i press volume up and down and power button at same time but is not working.I tried also with huawei multitool but is not working is not recognize my device. Please guys is any other solution to fix this ?Thank You!

I just fixed after power off device and then press volume down and plug the usb cable to pc and i was able to recognize my device and i have use huawei multiTool to unbrick my tablet media pad m3 and has work.

Almost the same problem, help please!!!
Hi guys someone can help me? I have a Honor 9 lite(LLD-L31). Android version 8.0
I apologize but I'm a new user and i don't have much practice with modding in general.
I tried to install root permission in my device. I get bootloader unlock code by DC-unlocker and installed TWPR on my device.
When i went in recovery the error " Failed to unmount '/system'(Device or resource busy)" rushed, so I tried to format data in order to give partition available. I tried again to flash file.zip but the search was empty so I downloaded a most recent version(3.2.3) of TWPR in recovery ramdisk.
Now if i try to log into recovery mode appear the same error (Error! func NO 11 / NO 2).
I can do everything aside going in recovery mode. How can I resolve it? Is it possible to reset to factory settings and try again?
I hope I have explained well the problem.

elliotn said:
3 button upgrade doesn't work either.
Click to expand...
Click to collapse
how about this 3 button method??

Astarothkun said:
I got stock recovery back with the warning that my device is unlocked. Now I get stuck at 'Your device is booting now'. After some time it reboots and opens eRecovery which I cannot use.
How do I get anything on my phone to continue with dload and which firmware would you advice me to flash if I finally get there.
Should I, if even possible at the moment, choose an older firmware version?
Edit: Would the original service rom help? Found it here https://forum.xda-developers.com/huawei-p9lite/help/original-service-rom-huawei-p9-lite-vns-t3688120 but my build number seems too high as the version I need only mentions b381 and b383 not the 394 I currently have..
Click to expand...
Click to collapse
Could you write down the steps you took to get back in fastboot for me? I'm having troule geting there myself after draining battery.

I fixed it after nothing else here worked.
So this is mostly so I dont ever forget the solution again, but also to possibly help others.
I also have to say that I had the problem with an P8 Lite, but all my problems matched almost exaclty, so It might help you too.
And a third disclaimer: I have no idea if you can flash the stock firmware without having the bootloader unlocked.
If you dont have it unlocked, try this wonderful updated guide: [Links are disabled for me so google this: "Droidhunter unlock huawei bootloader" and pick the article by droithunter.com]
And yes DC-Unlocker, suprisingly actually works (at least for me) and buying their bootloader unlock code was worth the 4 bucks.
So here is the solution:
1. Somehow, however needed get into fastboot. As I couldn't use the volume/power key combo myself, I somehow force reset the phone, pressing various buttons until I managed to boot into it again. I then used the adb bridge to boot into fastboot (google how to connect adb, then use "adb reboot bootloader" to get into the fastboot menu).
2. Download your phone models default stock rom/Update.app (also google that).
3. Extract the Update.app file.
4. Download and use the HuaweiUpdateExtractor tool and open the Update.app file (google again helps).
5. Select the "09.recovery.img" entry (the one with the green arrow on the left), rightclick and select "extract selected" and save it somewhere where you can find it.
6. Open your Fastboot console on PC (its often the same as the ADB console used before, especially if you use Minimal Fastboot and ADB, which I would recommend).
7. Make sure your phone is in Fastboot mode (not recovery) and connected to the pc.
7.1 Make sure your bootloader is unlocked. It might work with a locked one because youre just flashing stock firmware but eh might break more. Its worth the 4 bucks to unlock the bootloader first. (and yes DC unlocker looks super sketchy but somehow it actually worked for me and wasnt a scam).
8. Flash a custom recovery onto the phone (pretty much the same way you flash twrp, but instead of the twrp image you use the .img file you just extracted from the Update.app; Also dont try flashing twrp directly, it will probably not work).
The command to do so is: "fastboot flash recovery [filepath to the .img file without the brackets]".
9. Use the command "fastboot reboot".
10. If your phone doesnt boot normally, use the key combinations to get into the normal recovery screen and recover from a file or whatever (other guides should work from here).
Extra Steps:
As my recovery image was obviously so broken that even flashing twrp on top of it didnt work until I flashed the original reovery image, I went into my phones settings and did a factory reset. Directly after I installed twrps (see google) and set it up so it had full control. Afterwards I rooted and installed LinageOS cause frick EMUI rn).
Hope this helps anyone. If you have any questions feel free to ask me.

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""

Bricked Zenfone 3 ZE552KL - This package is for "WW_Phone" device. This is a ""
I'm handling a bricked Zenfone 3 ZE552KL WW model, but I am unable to flash the stock rom back into the device.
For context, this device has never been unlocked, rooted, and always worked under its original factory Android. As told by the owner, he received an OTA update notification last week and confirmed all prompts to initiate the update. As instructed, he plugged the device to its original charger, left the update running and went by with his day doing other stuff. When he returned, the device was completely OFF with 0% battery. We figured the charging cable disconnected due to a bad connector endpoint, and the phone ran out of juice while the update was running!
The result is a bricked Zenfone unable to boot beyond the ASUS logo. It keeps crashing and gets into a boot loop.
I have tried most of the basic tech support I can give him.
I have downloaded a fresh copy of the official ZE522KL firmware from the ASUS website.
I can boot the phone into recovery, which is still the original ASUS recovery. But as I try to flash the firmware, I get this lovely error message:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ERROR: This package is for "WW_Phone" device. This is a "".
I know for a fact this is a WW_Phone device because when I try to flash the JP firmware, the error message is different.
ERROR: This package is for "JP_Phone" device. This is a "WW_Phone".
Already tried "Wipe data/factory reset" and "Wipe cache partition" from the recovery menu, but that didn't help.
Already tried pushing the firmware via "adb sideload" and placing it in a SD card. Those didn't help either.
I am also willing to flash a community ROM, like LineageOS or Mokee, but I first need to unlock the bootloader. I'm running adb and fastboot from Linux, and I can't find a descent tool to unlock using Linux is proving to be a real pain. Every tool seems to be made for Windows only.
So, I'm resorting to anyone here, hoping anyone could give me a light before we send this phone directly to ASUS tech support, not available in our region (we'll need to ship it to another city).
Anything I can try before that? I'm running out of ideas.
Best regards and thanks in advance for any help.

Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg

Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.

wang1chung said:
Flash the latest stock recovery thru fastboot and then flash the latest raw firmware.
Otherwise try launching, not flashing, twrp thru fastboot and then flash any raw firmware with the updater script edited.
Click to expand...
Click to collapse
Since his phone is locked, he can't flash anything except RAW firmware.
---------- Post added at 11:52 AM ---------- Previous post was at 11:41 AM ----------
juliohm said:
Trying to post a screenshot of the error:
https://i.imgur.com/5RHXM3c.jpg
Click to expand...
Click to collapse
Hey juliohm,
Just follow these steps & your device will operate normally
1) Download and install ASUS Flash Tool :
2) Download Latest Oreo RAW
ZE520KL:
ZE552KL:
3) Enter Fastboot Mode (Power + Volume Up)
4) Open ASUS Flash Tool
5) Select device & select firmware (select YES on wipe data tab too)
6) Connect phone to PC
7) Hit Start and wait 10-15 minutes (ignore the error 5 [FRP])
MOD EDIT: PAY-PER-CLICK LINKS REMOVED

Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?

juliohm said:
Thank you, Saktis_STi. But these are Windows tools and I'm running Ubuntu on my local system. No Linux tools available for this task?
Click to expand...
Click to collapse
Check PM

Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.

GrenadeofTacos said:
Try unlocking your bootloader using the unofficial way located in the Zenfone 3 forum. It should be doable because you only have to boot into your bootloader. You can then flash a custom recovery, such as TWRP, and go in and wipe data, cache + dalvik, and then install a custom ROM. In your case, it looks like the stock recovery can't detect the device model (WW_Phone), so it's most likely that something is wrong with the system partition.
Click to expand...
Click to collapse
No need. Flash RAW firmware is enough.

Just a quick follow up.
The owner decided to take it a local assist shop. I don't know what method they used, but they managed to reflash the stock firmware back into the device, and it's working fine again.
Thank you all for the tips. If this was my own device, I would be tinkering a lot more. But the owner decided to play safe and pay for repair in some authorized assistence shop.
Best regards all!

[Z00T/ZE551KL] Frustrating Bootloops -- Hardware issue?

Update: Someone suggested battery replacement. I installed my brother's phone "good" battery and it didn't fix the problem.
Having a weird situation with bootloops that worsened over time. I'm thinking it could be due to failed hardware? Maybe someone has experienced this and we can all benefit from this.
So, I kept going into random bootloops for the last 6 months. Happens during normal usage on lineage ROM AND stock ROM.
It boots into first boot screen, after ~10 seconds it blinks blue screen and reboots again.
Video:
https://youtu.be/4yCeb1J7jcs
I was sometimes able to get out of bootloop by placing phone in charger until the bootloop stops and the phone boots.
When this failed sometimes, I would go back to stock by either back2stock.zip by the great LuK1337 and sometimes from fastboot by doing the following:
While in fastboot I would boot into TWRP from adb >> wipe everything then flash stockrecovery.img >> boot into stock recovery >> while in stock recovery I flash oldest stockfirmware zip from there >> perform factory reset from within recovery then reboot.
It would always boot successfully.
Now my bootloop has worsened and no method is working out for me.
Is my phone defective? Any idea what part would be defective?
Note that it suffered from excessive heat in its recent months.
I can get into fastboot/TWRP/stockrecovery. But that's it.
Bootloader is apparently still unlocked:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks a lot.

Have you flash back to original Asus image & slowly up the firmware versions?
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that, you can them use custom roms to your pleasing.
Good place to start.
https://www.asus.com/Phone/ZenFone_Selfie_ZD551KL/HelpDesk_BIOS/

TroyBar said:
Have you flash back to original Asus image & slowly up the firmware versions?
Asus firmware updates hardware issues...after that you can them using custom roms to your pleasing.
Good place to start.
https://www.asus.com/Phone/ZenFone_Selfie_ZD551KL/HelpDesk_BIOS/
Click to expand...
Click to collapse
Which version should I install? I've tried it before and it didn't work.
Also should I install it via TWRP or via Stock Recovery?
Thanks very much!

Install latest TWRP
https://dl.twrp.me/Z00T/
A good start is follow the link of the back2stock.zip you posted, follow the instructions, zip it back up to back2stock.zip with the files mention & then flash it in TWRP.
https://asus.kremowka.xyz/categories/show/2
Zenfone 2 Selfie — ZD551KL
This will rule out any issues you have, as you will have the latest firmware from Asus.

TroyBar said:
Install latest TWRP
https://dl.twrp.me/Z00T/
A good start is follow the link of the back2stock.zip you posted, follow the instructions, zip it back up to back2stock.zip with the files mention & then flash it in TWRP.
Once done, check if your bootloader is still unlock if so you need to find out how to lock it to install Asus official firmware.
Continue the next firmware version above Version WW-21.40.1220.2056 2017/03/16 (from the posted link) located at above Asus website.
This will rule out any issues you have as you have the latest firmware from Asus.
Click to expand...
Click to collapse
The ROM you mentioned does not exist in the link you shared, maybe it's a regional effected page.
Screen of the webpage:
https://i.imgur.com/3WaSs5G.png
However, I downloaded the latest available ROM [Version WW_21.40.0.2214] from November 2017,,
I applied the back2stock steps and flashed via TWRP successfully.
After that I checked my bootloader via fastboot and it was still unlocked.
I could not re-lock it using any of the following commands:
fastboot oem lock
fastboot flashing lock
fastboot oem relock
Always gives me a "FAILED" message.
Also found this thread about "relocking" the bootloader:
https://forum.xda-developers.com/ze...guide-ze500kl-bootloader-unlock-lock-t3655340
I flashed "relock_bootloader.zip" via TWRP and it didn't lock bootloader.
Then I thought maybe it will would work if I flashed RAW rom via Asus Flasher [from same thread].. So I googled for a ZE551KL RAW firmware and found it here:
https://drive.google.com/file/d/0B43Ue6xY9MmdRVdDRWtSSVNUdDg/view
Tried flashing it via the Asus Flash Tool and got an error "Phone is protected". See screenshot:
What do you suggest we should try next?
The phone is still having the same bootloop.

So after a little digging, it appears that my Bootloader is *NOT* unlocked.
But how come it gives an *unlocked* result for the command "fastboot oem device-info" ???
Is it possible to have a "locked" Bootloader in reality and showing otherwise in fastboot checking command??
To add, I can't install TWRP from fastboot using:
fastboot flash recovery twrp.img
I can boot the img, then install it as recovery from within TWRP.
Is this also "locked" bootloader behavior?
So many questions.

Sorry was tired last night, not the below version as it is for ZE551KL
Version WW-21.40.1220.2056 2017/03/16
You need the one(s) for Zenfone 2 Selfie — ZD551KL
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that, you can them use custom roms to your pleasing.

TroyBar said:
Sorry was tired last night, not the below version as it is for ZE551KL
Version WW-21.40.1220.2056 2017/03/16
You need the one(s) for Zenfone 2 Selfie — ZD551KL
Procedures:
1st
Phone (old firmware) > unlock bootloader > install TWRP > install custom rom > issues/unstable/more issues.
2nd
Phone (latest firmware) > unlock bootloader > install TWRP > install custom rom >
If 1st step was performed you need to go back & lock up the bootloader in order to update the firmware to the latest.
Asus firmware updates security/unstable & another issues...after that you can them using custom roms to your pleasing.
Click to expand...
Click to collapse
So, I should install latest ZD551KL stock firmware on my ZE551KL ? Is that correct?
Could you please message me on Telegram? I have the same username.

shmaiz3r said:
So, I should install latest ZD551KL stock firmware on my ZE551KL ? Is that correct?
Could you please message me on Telegram? I have the same username.
Click to expand...
Click to collapse
Sorry is your phone ZD551KL (ZOOT) or ZE551KL, choose the one that is yours, mine is ZD551KL (ZOOT).

I have tried the above back2stock method, placed the files inside & also outside the meta-inf folder, re-zipped it up to back2stock.zip (2 separated folder zips (one for inside & other outside)) & flashed it (inside zip errors out, will outside zip works with update system, but is stuck there.
Another possibility below for an unlock bootloader, but requires you to have the stock OS installed, this has not work for me with a custom rom. I will need to find my ZD551KL (ZOOT) stock OS to try.
https://www.asus.com/support/FAQ/1009748?SearchKey=ota/

TroyBar said:
I have tried the above back2stock method, placed the files inside & also outside the meta-inf folder, re-zipped it up to back2stock.zip (2 separated folder zips (one for inside & other outside)) & flashed it (inside zip errors out, will outside zip works with update system, but is stuck there.
Another possibility below for an unlock bootloader, but requires you to have the stock OS installed, this has not work for me with a custom rom. I will need to find my ZD551KL (ZOOT) stock OS to try.
https://www.asus.com/support/FAQ/1009748?SearchKey=ota/
Click to expand...
Click to collapse
I tried flashing back2stock with both the New stock ROM and the Old stock ROM. No dice.
Thanks for your time.