yashsingh1/xdaforums huggingface dataset:
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] trachyte:
I think the instructions at https://twrp.me/asus/asuszenfone62019.html should say to use Install -> Install Image -> Install Recovery Ramdisk.

I keep choosing "Boot" because that's what I've always chosen on other (non a/b) phones. Took me a while to figure out why it wasn't working.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Thanks, I updated the install instructions with your input.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] _jis_:
That's not true.

https://www.phonearena.com/news/Goo...ts-the-difference-and-should-you-care_id93938
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] S4turno:
You are right. 3MP is a limit of the "express backup" option, not the regular backup option, my bad.

I'll update my post.

cc [MENTION=10085708]JonWallsten[/MENTION]
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Mishuletz:
Hello guys!

It happened that I've got stuck in fast fastboot mode while trying to install twrp recovery.

I've tried everything and I can't come in recovery mode just to fresh install stock rom . I may erased everything..

The bootloader is unlocked.

Please if you can help me I will be very grateful!!
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] isthisadagger:
If you were on stock, flash stock boot.img in fastboot.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Mishuletz:
It won't work, I tried unpack stock rom and take the boot.img to flash it. It came everytime with an error.

☹
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Mishuletz:
It came with this error..
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] GSPD:
fastboot flash boot boot.img
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
You are using an incorrect syntax. Use:

fastboot flash boot boot.img
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Mishuletz:
Thank you! I did that and it passed. It worked to flash boot.img, but nothing changed. I can't boot recovery.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Are you using the fastboot screen to boot recovery?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Mishuletz:
I tried to boot recovery from both my PC and from the phone and didn't succeed..
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Mishuletz:
Any idea? What can I do? Please, I need help..☹
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] -SUM1-:
Despite this being an "official" release, I see a lot of people have had issues with it. Is it no longer safe to flash? If so, can you update the original post to reflect this?

I've been debating whether to flash this TWRP, flash the unofficial one or go for a non-TWRP install of Magisk. TWRP makes it so much easier. But if this one is not stable, can you please give an estimate as to when it might be?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] papete:
Yes, things are still a little green here (all development). In my case I used unofficial TWRP (official was not available yet) and flashed magisk zip. No problems at all.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] -SUM1-:
I went that route and it seems to have all worked out fine. Even installed EdXposed and XInsta with SafetyNet passed. Thank you.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
The only problem as far as I am aware with the official version I am supporting, is that the repack tools in TWRP to install the ramdisk for a permanent TWRP install isn't always working. The other issue is PIN/Pattern doesn't work. You can boot via fastboot if you are worried about the permanent ramdisk install until I have some time to get it worked out. I suppose I can post an unofficial installer tonight for ramdisk and attach it to the first post. This would use dd to re-flash the repacked image in the installer zip.

If you have a repack issue, then reflash stock boot.img and try re-installing the repacked image. I think for some reason our built in function we use for image writing isn't writing the data correctly on repack. It's hard to debug on this phone because once you have an improper boot of a bad ramdisk, it won't let you fastboot anymore until you re-flash the boot partition through fastboot.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] ChthonVII:
Hi everyone, I'm in desperate need of help:

I tried using this recovery to flash the microg fork of lineage, and now I seem to have a hard brick. I flashed the file from SD card. It reported success, though the log contained errors that /system and /vendor were busy (which I assumed were post-flash and unimportant), then I selected the reboot option. The phone never came back up. It appears to be off, and no combination of buttons seems to do anything.

Does anyone have any ideas on how to fix this?

Is there a button combo other than volume up + power that's supposed to do anything?

Will it sort itself out if the battery is allowed to fully drain?

How the heck did flashing a rom manage to take out the bootloader? Would Asus be able to figure this out if I RMA'ed it?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] :
Try Volume Down + Power (10 seconds). It should either hard-reboot or hard-shutdown the phone.

If you do not notice any difference after 10-15 seconds, try to boot to bootloader with VolUp + Power again.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] ChthonVII:
Thank you very much for your suggestion. Unfortunately, it didn't help. Hold power -> nothing. Hold vol up + power -> nothing. Hold vol down + power -> nothing. Permutations involving that other button -> still nothing. Plug or unplug power cable -> no charge screen, no LED, nothing. It truly appears to be hard bricked.

I've been deeply troubled by the question of how this could even happen in the first place. In my (admittedly limited) understanding, the bootloader and fastboot binaries live in a distinct partition that the flashing process never touches, so they should be intact no matter how badly you f- up /system and /boot. Further digging turned up this report (I can't post links so: https colon slash slash www dot androidpolice.com/2019/08/06/latest-zenfone-6-update-causing-crashes-asus-blames-motherboard-malfunction/) that Asus has acknowledged some units have a hardware defect in the motherboard that manifests after a firmware update leading to spontaneous reboots, bootloops, and something hard brick. That sounds like the most plausible explanation for the given facts. (Someone please jump in and tell me if I'm barking up the wrong tree here.) In which case I am right and truly f-ed, and my only option is to send it to Asus and hope they can't tell the bootloader is unlocked or they decide to (obey the law rather than their corporate policy and) fix the hardware defect because it was already defective independent of the software modifications.

Any advice on how to proceed? Any suggestions for how to fix this without going to Asus?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] papete:
To be honest, if you can't get to fastboot mode, I don't see many options
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] :
I agree to that. (Does plugging in usb-cable while holding either volUp or volDown do anything ? It's the only thing you didn't mention explicitly.)

In your position I would try to file an rma at Asus, I guess.

Good luck.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Chapi666:
Did you try to long press power + Vol up + Vol down ? Just try...

If you can't boot into fastboot mode, your last choice is to return your phone to ASUS.

I had problem like yours and even if my bootloader was unlocked, Asus changed the mother board of my phone.

Now everything works well and I'm rooted.

Good luck.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Sounds like hardware failure. I agree with RMA process.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] aleksander002:
I've used to think flashing /system can't brick anything other than system itself too but I know from experience that unskilled flashing or wrong zip can brick a phone badly regardless of what you were doing. If your Zenfone has never rebooted by itself before, it's improbable that's a motherboard failure. There is a chance they'll fix it on warranty but if they refuse you'll have to pay for it. Where are you from? If it's the EU there's a directive mentioning firmware alteration - it can't void one's warranty unless service can provide a proof that damage is caused by messing with fw. That won't be hard if they have some proper tools to read directly from UFS so I don't think this law would save you anyway.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
I was stuck into Zenfone 6 logo after inatlling Xuimod Xposed module, so I rebooted but now I am stuck on Fastboot, can't even enter TWRP to restore my backup:

FAILED (remote: Failed to load/authenticate boot image: Load Error)

How to get into TWRP again?

I have searched google but I only found instructions for OnePlus devices.

Edit:

Ok i could access recovery again by flashing images one by one but even after that, I can just access stock recovery and when I reboot, the device bootloops on Asus logo...
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
I would try booting the fastboot installer image and see if you can restore from there. The ramdisk modifications can be tricky because if they are too big, the phone won't boot.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Hello, all. I posted a 3.3.1-1 release.

- added dtbo partition - allows you to backup the avb signature and dtbo related to the installed system

- replaced installer image with zip - provides more reliable installation until I can figure out what is going on with twrp repacking

It will be up on the site when the next index job runs.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] papete:
Thanks a lot for your work bigbiff... I guess the only major bug left is the pattern recognition. Keep it up!!!
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] S4turno:
On TWRP 3.3.1-1 (installed with the provided zip) + stock ROM, both /system and /vendor can't be mounted (device or resource busy). Pin was removed and I'm able to see the phone's storage, transfer files, etc. Any idea of how to fix this?

Apologies if the answer to this is obvious, this is my first device with A/B partitions and I'm still trying to learn how things work.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] wreid23:
This happened to me as well repair the file system in twrp or fastboot into the twrp fastboot installer and reflash stock fw from asus & wipe data cache system. I wasted a long night before learning still not able to do lineage setup yet..
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] S4turno:
I don't know if it works with TWRP, but it works if you use their recovery (and their installation instructions).
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Can you check if they were already mounted using adb shell df?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] S4turno:
adb shell df:
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] progman32:
Hi! Thanks for your work on this. I'm trying to wipe system in preparation for LineageOS, but I'm running into trouble - the FS is refusing to be created. Full logs here, excerpt below:

I:Set page: 'wipe'
I:Set page: 'advancedwipe'
I:Set page: 'action_page'
I:operation_start: 'Format'
I:Unable to find a directory to store TWRP logs.I:wipe list '/system;'
I:wipe_path '/system'
Formatting System using mke2fs...
I:mke2fs command: mke2fs -t ext4 -b 4096 /dev/block/bootdevice/by-name/system_a 917504
mke2fs 1.43.3 (04-Sep-2016)
/dev/block/bootdevice/by-name/system_a is mounted; will not make a filesystem here!
mke2fs -t ext4 -b 4096 /dev/block/bootdevice/by-name/system_a 917504 process ended with ERROR: 1
Unable to wipe System.
Unable to wipe /system.
Updating partition details...
Failed to mount '/system' (Device or resource busy)
I:Actual block device: '/dev/block/bootdevice/by-name/system_a', current file system: 'ext4'
I:Unable to mount '/system'
I:Actual block device: '/dev/block/bootdevice/by-name/system_a', current file system: 'ext4'
Failed to mount '/vendor' (Device or resource busy)
I:Actual block device: '/dev/block/bootdevice/by-name/vendor_a', current file system: 'ext4'

If I manually try an umount, the kernel just says "invalid argument" and nothing happens:

ASUS_I01WD:/ # umount /dev/block/bootdevice/by-name/system_a
umount: /dev/block/sda16: Invalid argument
ASUS_I01WD:/ # mount|grep system
/dev/block/sda16 on /system_root/system type ext4 (ro,seclabel,relatime,block_validity,delalloc,barrier,user_xattr,errors=remount-ro)

Kind of at a loss on what to do. Will probably try unofficial TWRP, will update with findings.

Edit: Unofficial TWRP worked to format but wouldn't flash Lineage. Rebooted into official TWRP, which could flash Lineage but failed out on gapps. Rebooted again into unofficial TWRP, flashed gapps and Magisk. I'm in Lineage now, phone's convinced it needs an old PIN of mine to boot but I think that's a PEBKAC.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
I might know the issue. Will look into it tonight.

It was a pretty dumb issue, a fix has been published and will be available in the next few hours on twrp.me.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] ChthonVII:
Following up on this:

I got the phone back from Asus yesterday. It was some kind of hardware fault. They replaced the motherboard. Unfortunately, that's about all I know because the paperwork is in Japanese, written by a Taiwanese tech, and the fault is described with a super generic term that translates as something like "electronic problem" or "bad electricity." My best guess is that it's the same issue described in this news article (I can't post links here, so: https colon slash slash www dot androidpolice.com/2019/08/06/latest-zenfone-6-update-causing-crashes-asus-blames-motherboard-malfunction/).

As for the warranty:

The bootloader unlocking program ratted me out. The Asus phone reps could tell from the serial number that the bootloader had been unlocked. (Aside: Someone ought to try intercepting that traffic at the router and see if it's feasible to impersonate that server.)

The Asus phone reps were insistent that unlocking the bootloader voided the entire warranty, even if the defect was unrelated to my modifications. (AFAIK my local law is functionally the same as U.S. law: manufacturers can only void warranties with respect to problems caused by the user's modifications; the warranty still stands for unrelated defects.)

Nevertheless, the paperwork from the Asus repair facility says it was covered under warranty, and they did not charge me.

So... I'm not sure what Asus's real policy is here. Maybe I just got lucky -- they meant to treat the warranty as void, but that wasn't communicated to the repair facility. Or maybe the policy is that phone reps lie about the warranty to discourage RMA's, but the repair facility follows the law if you RMA anyway. I don't know.

I guess the only useful advice I can offer as a result of this experience is that you should probably take at least one stock OTA before unlocking the bootloader. As per the news article above, installing an update seems to be the thing that triggers the hardware fault, and Asus is much easier to deal with when there're no questions about your warranty status.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
Flashed twrp-3.3.1-2-I01WD.img from fastboot. TWRP is loaded and I can access files on the phone if I connect to the PC.

But I can't swipe to unlock. The screen touches are not recognized. So there's no way for me to actually wipe/install/etc.

Is there any workaround for this? Or alternatively, can I wipe/install using adb commands in this state?

Thanks.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
Have you tried disabling all security like password fingerprint etc.. in system?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
Thanks for the suggestion, but as far as I can see, I don't have anything loaded in system.

I used Lineage recovery, I wiped everything and tried to install LOS. The install gave errors and didn't finish, so I have no OS now.

Right now, only TWRP successfully boots, Lineage recovery just bootloops. Fastboot is still working, thankfully.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
Then I think you only can flash ROM via ADB or SDcard. You will loose all your data. Hope you have made backup.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
Yup, I backup the photos before doing this. I never take chances on the first install.

Could you point me in the right direction on how to flash via ADB/SD? Thanks a bunch, mate.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
For adb sideload you can see that:

https://android.gadgethacks.com/how-to/sideload-flashable-zips-android-with-twrp-0176529/

For install from the Sdcard you'll need to save the ROM on the Sdcard with another phone and then choose "install" like you regularly do and navigate into your sdcard to the ROM.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
Thanks but I can't get past the swipe to unlock screen on TWRP. So I can't click on the "Advanced" tab in TWRP to start the adb process.

Anyway to control the entire thing from the terminal window in PC as if my screen was broken?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
When I couldn't enter TWRP the only way I could make my phone work again was by flashing every image one by one in fastboot (that is boot, system, and others).

Here is where you can find them:

https://xdaforums.com/zenfone-6-201...ne-6-proton-kernel-v1-0-t3963948/post80405617

You have to do "fastboot flash thing thing.img" for each image.

---------- Post added at 12:37 PM ---------- Previous post was at 12:32 PM ----------

Have you tried booting in TWRP with

fastboot boot twrp.img like you did first time before you did everything?

If not, try this first.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
Yes, I just tried fastboot boot twrp.img

It's the same, it loads but touch is not responsive. When plugged in to the PC, I can actually navigate files and see the TWRP backups.

I guess I'll try flashing the boot, system one by one. Thanks.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
OK so try the images flashing.

But if I was you I would transfer my TWRP backups into my computer since you can access them.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
Yup, I transferred out the backups just in case. And I've downloaded all the .img files and the official firmware.

I saw your posts in the other threads, can you tell me if you flashed all the .imgs or just a few(eg. boot, system)?

I'm hoping to flash just enough to get the stock bootloader working so I can flash the full firmware zip and get back to stock, so I can start over. I would really prefer not to manually touch things like modem.img unless really necessary.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
I have flashed everything.

I don't know if you could ignore some of them.

Edit: and I flashed to both slots, just in case.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
So it would be:

fastboot flash boot_a boot.img

fastboot flash boot_b boot.img

fastboot flash system_a system.img

fastboot flash system_b system.img

Are the commands for the remaining items the same as the filename? Would it then be:

fastboot flash asusfw_a asusfw.img

Thanks for all the help so far, mate.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
Yes but I did all a then all b.

Don't know if it matters.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Interesting, I wonder why input device isn't registering on your phone. Can you post the results of

adb shell dmesg

here?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
A partial flash got the stock OS booting but again the touch wasn't responsive. A full flash as you suggested(Full A partition first, then B) worked.

I now have a fully functioning stock OS. Many thanks, mate.

I'm back to stock now, do you still want me to dump the dmesg? If it helps, the touch wasn't recognized in the stock OS either, and stock/Lineage recovery didn't even boot.

Also, any advice before I flash your recovery again? It should work now I reckon, since the firmware is now updated.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
OK, that's weird that it wasn't working in stock, maybe something was wrong in vendor or something? It should be OK to reinstall TWRP. Try the fastboot image first and make sure touch still works.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
Tried the fastboot image as you suggested, it worked. Thanks mate.

But is that the mistake I've been making? That I've been flashing "twrp-3.3.1-2-I01WD.img" instead of "twrp-installer-fastboot-3.3.1-0-I01WD.img" just because the former is the latest version?

Anyway, here's what I did in case someone else has the same problems:

fastboot boot twrp-installer-fastboot-3.3.1-0-I01WD.img

Make a backup

Wipe Dalvik, System, Data

Install Lineage.zip

Reboot to System

2 bootloops happen and we end up in Lineage recovery

It asks to factory reset, do it

Successfully boots to Lineage
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Sorry, you should use the 3.3.1-2 image to fastboot, and install the zip for permanent installation in the boot partition ramdisk.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] papete:
I'm wondering how "fastboot boot twrp-installer-fastboot-3.3.1-0-I01WD.img" worked...
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Satoso:
Strange, because that's what I flashed last time and it didn't work. Of course, the error could be entirely unrelated to TWRP, but somehow the fastboot installer img worked.

Is it not supposed to? Just to be safe, I did just check my bash history and the SHAsum of the file, and it is indeed "twrp-installer-fastboot-3.3.1-0-I01WD.img" that I used.

It also asked if I want to install the TWRP app, which 3.3.1-2 didn't ask, if that's any indication.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Not sure if it was related or not to TWRP, but if you are having the problem with the 3.3.1-2 image, please let me know. If it doesn't ask to install the TWRP app, I think it's able to read your TWRP settings file to indicate you already selected never to show it again.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] MirkoMirko9:
Hi guys, just a question: we still need to disable lockscreen, pin etc. Or we can use without problem also with password security and it will decrypt successfull when we will enter in recovery mode ? Because last time i installed removing lock screen and after i set it again, but when i rebbot in recovery i forgot to remove lockscreen and so bye bye, i had a bootloop. Thanks in Advance
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] bigbiff:
Yes, you have to remove the pin/pattern before starting recovery. Unfortunately I can't figure out why the gatekeeper blob won't receive the pin/pattern from TWRP. It just hangs and strace isn't helpful at debugging the issue. I am hoping to check the blob in Q and see if it performs different.
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] EMJI79:
It's strange because the pin works on unofficial twrp 3.3.1-19

:confused:
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Xandros97:
not work with latest build with android 10 (WW_ZS630KL-17.1810.1910.63).

can't load with command "fastboot boot *********"
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] meplur:
Yup, stuck on Asus logo after running:

fastboot boot twrp-3.3.1-x-I01WD.img
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] Xandros97:
can you post the "boot.img" of 17.1810.1910.63?
[ASUS ZenFone 6 (2019) ROMs, Kernels, Recoveries, &] SirLoinOfBeef:
Here is the unpatched original WW_ZS630KL 17.1810.1910.63 boot.img.

https://filebin.net/41qg55pwzls43uzr