yashsingh1/xdaforums huggingface dataset:
[ASUS ZenFone 8] Adaoh:
Here is quick guide for

Flashing the Stock ROM (Android 11)​

Note: doing this will remove any data on your phone, back it up if it is important to you​

This also works if your phone is stuck in a boot loop or other problems of the sort

Scroll down to the bottom of the Android 12 beta page (How to opt-out and revert back to Android 11) and download the linked file at step 2. Keep it on your computer.

Turn off the phone

When the phone is off, press and hold the Volume Up key and the Power button until a screen pops up.

If the phone boots to Android, shut it back off, but this time try lifting the Power button before the Volume Up key, because the power button is like an Enter key, it will take it as if you clicked "yes, continue to android".

Plug the phone in your computer

Decompress the zip file you downloaded at step 1.

Find and execute the script file that is made for your computer, here are the files for the most popular desktop operating systems:

Windows: update_image.bat

Ubuntu: update_image.sh

MacOS: update_image_for_mac.sh

Wait for the process to finish, it'll take a while. You'll know it is done when the window that opened when you executed one of the script files says something along the lines of "Flashing done, press Enter to reboot"

I hope this helps!
[ASUS ZenFone 8] sabeltand:
Thanks for your help Adoah and topaza, i appreciate it very much. I have been running Cyanogen and Lineage for a decade on various devices, but because of a new digital method of signing into danish public systems (MitID), I need a "clean" phone.

I have installed LOS with the instructions on https://wiki.lineageos.org/devices/sake/install :

$ fastboot flash vendor_boot sake_vendor_boot.img

$ fastboot flash boot lineage-18.1-20211002-recovery-sake.img

Then reboot into recovery and apply update from adb

$ adb sideload lineage-18.1-20211002-nightly-sake-signed.zip

$ adb sideload open_gapps-arm64-11.0-nano-20210925.zip

Then reboot and everything works well.

Trying to apply the UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip in recovery from adb:

$ adb sideload UL-I006D-ASUS-30.12.112.72-1.1.31-user.zip

$ adb: failed to read command: Success

And nothing happens on the recovery screen. If i do the exactly same thing with the lineage zip it works perfectly.

Then over to the official Android 12 beta page with the opt-out option. I have downloaded the WW-ZS590KS-30.11.51.115-MR0-user_20210826-release.zip, extracted it and executed the update_image.sh:

$ sudo ./update_image.sh

$ Get hwid failed!

I have been trying to look into the update_image.sh script but my carpentry skills do not fully apply here, though it seems like to have something to do with this section:

"

fi

project=`grep -o "ZS590KS" get_prjtemp$SSN_ARG.txt`

rm -rf get_prjtemp$SSN_ARG.txt

sudo $FASTBOOT oem get-hwid > get_hwtemp$SSN_ARG.txt 2>&1

if [ $? != 0 ]; then

echo -e "${RED_COLOR}Get hwid failed!${RESET}"

exit 1

"

Then trying to check if the get-hwid works, but it seems not to:

$ sudo fastboot devices

$ M4AIB7625957YHL fastboot

So there i connection. Then

$ sudo fastboot oem get-hwid

$ ...

$ FAILED (remote: Unable to open fastboot HAL)

$ finished. total time: 0.000s

Is that the reason why the script does not work?
[ASUS ZenFone 8] topaza:
You might try to flash it with TWRP. If this leads to the same issue you might at least get an error message telling you what went wrong. But to be honest the zip/script that you found seems to be the better option anyway.

I checked the fastboot oem get-hwid on my device with stock rom. It returns the following:

(bootloader) HWID = 7

(bootloader) === ID Info List ===

(bootloader) -1 : UNKNOWN

(bootloader) 0 : EVB

(bootloader) 1 : EVB2

(bootloader) 2 : SR

(bootloader) 3 : preER/ER1

(bootloader) 4 : ER2

(bootloader) 5 : prePR/PR1

(bootloader) 6 : PR2

(bootloader) 7 : MP

OKAY [ 0.001s]

Finished. Total time: 0.001s

I checked the script. What it seems to be doing here is just checking that you have the right device before flashing. If really just the get-hwid does not work and you are sure that you have the right files, you could probably just remove that check from the script and it will start flashing. (on you own risk)

But lets check first if this is a general fastboot issue.

What operating system do you use? Seems to be a linux system? What distro?

What does the command "fastboot devices" return?

If that shows a device, what does the command "fastboot oem get-hwid" return?

Also try "fastboot oem device-info".
[ASUS ZenFone 8] sabeltand:
I am on Ubuntu:

morten@Lenovo720Y:~$ lsb_release -a

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 20.04.3 LTS

Release: 20.04

Codename: focal

morten@Lenovo720Y:~$ uname -r

5.4.0-94-generic

morten@Lenovo720Y:~$ fastboot --version

fastboot version 1:8.1.0+r23-5ubuntu2

Installed as /usr/lib/android-sdk/platform-tools/fastboot

morten@Lenovo720Y:~$ fastboot devices

M4AIB7625957YHL fastboot

morten@Lenovo720Y:~$ fastboot oem get-hwid

...

FAILED (remote: Unable to open fastboot HAL)

finished. total time: 0.000s

morten@Lenovo720Y:~$ fastboot oem device-info

...

FAILED (remote: Unable to open fastboot HAL)

finished. total time: 0.000s

I will try flashing TWRP recovery and flashing the zip again and be back to you.
[ASUS ZenFone 8] sabeltand:
Ok, I tried flashing TWRP the same way I think I did it the other night:

morten@Lenovo720Y:~/Zenfone 8$ sudo fastboot flash boot twrp-3.6.0_11-0-I006D.img

[sudo] adgangskode for morten:

target reported max download size of 268435456 bytes

sending 'boot_b' (98304 KB)...

OKAY [ 4.072s]

writing 'boot_b'...

OKAY [ 0.248s]

finished. total time: 4.320s

Right now I have a very expensive black mirror with the "ASUS" logo in the middle. No matter if I choose START or "Reboot to recovery" in the bootloader, it ends up displaying the ASUS logo and nothing else happens :(
[ASUS ZenFone 8] Adaoh:
LineageOS and TWRP caused me some trouble in the past. Exactly your issue with the Asus logo. What I did to get out of that was using the steps I posted in my other reply. Maybe your fastboot driver isn't working properly?
[ASUS ZenFone 8] topaza:
From my experience fastboot can be rather old in Ubuntu. I can remember that I had to update fastboot manually once in the past while I was using ubuntu because there was an issue.

Can you try the current Fedora version? In a VM or with live dvd?

Ok so the device is recognized but strange that the other commands fail. I still would suggest to try the newer version of fastboot.

Let´s try to fix fastboot and the script first.
[ASUS ZenFone 8] topaza:
Unfortunately two things went wrong here:

- booting the TWRP image instead of flashing it would have been the better option

- as stated in my last post it would have been better to check/fix fastboot issues first

Can you still access the device via fastboot?

//EDIT: Turn the device off and press VOL-UP + POWER. You should still be able to see a menu? If so, stay there and try "fastboot devices".
[ASUS ZenFone 8] sabeltand:
Success!

First things first I must state that I am an idiot :)

The problem seems to be that I always entered the lineage recovery and "Enter Fastboot" from there to end up in some kind of lineage fastboot mode, while just staying at the bootloader menu gives me fastboot connection too. Over a decade of fiddling with Cyanogenmod and LineageOS on various devices and now i get that I am a slow learner :)

So, just in the menu at boot the fastboot oem get-hwid also spits out the correct stuff.

sudo fastboot oem get-hwid

...

(bootloader) HWID = 7

(bootloader) === ID Info List ===

(bootloader) -1 : UNKNOWN

(bootloader) 0 : EVB

(bootloader) 1 : EVB2

(bootloader) 2 : SR

(bootloader) 3 : preER/ER1

(bootloader) 4 : ER2

(bootloader) 5 : prePR/PR1

(bootloader) 6 : PR2

(bootloader) 7 : MP

OKAY [ 0.002s]

finished. total time: 0.002s

And now I have successfully gone back to stock with the update_image.sh script. It stalled halfway through the first two tries, but after connecting the phone to the USB-A instead of the USB-C on the laptop, i ran all the way through.

Thanks for your help! I owe you guys a beer, or maybe 20 :)
[ASUS ZenFone 8] topaza:
Great to hear that everything is working again! :)

Does everything look like before unlocking the boot loader or is it still visible that the boot loader is unlocked?

What does "fastboot oem device-info" say?

If it still says that boot loader is unlocked, can you relock it with "fastboot oem lock"? (I think this will reset the device to factory defaults, so do not try this if you have data saved on the phone that you do not want to lose!)
[ASUS ZenFone 8] adam.718:
Phone not booting after installing the January 14th update.

Lineage 18 (Update January 14th, 2022) on Asus ZenFone 8 is not booting after installing the latest update.

Stuck on the Lineage logo loading screen.

Not sure what I need to do, Please help!!

@ZVNexus it's kinda urgent :(
[ASUS ZenFone 8] sabeltand:
Now the lineage recovery is gone and instead there is stock recovery. If I go into recovery and enter fastboot from that menu it seems like fastboot stil has some issues:

$ sudo fastboot devices
M4AIB7625957YHL fastboot
$ sudo fastboot oem device-info
...
FAILED (remote: Command not supported in default implementation)
finished. total time: 0.000s

But if I just stay at the bootloader menu and fastboot from there, it seems to work:

$ sudo fastboot devices
M4AIB7625957YHL fastboot
$ sudo fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL:
(bootloader) ABL: Post-CS3-1-WW-user
(bootloader) SSN: M4AIB7625957YHL
(bootloader) ISN: HB13EADEM04Y0DY009GA
(bootloader) IMEI: -
(bootloader) IMEI2: -
(bootloader) CID: ASUS
(bootloader) COUNTRY: EU
(bootloader) Project: ZS590KS
(bootloader) DT ID: 109
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 4
(bootloader) DMCounter: 4
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 0
(bootloader) LOCK_COUNT: 0
(bootloader) Check_APDP: 0
(bootloader) rawdump_en: false
(bootloader) Current Slot: a
(bootloader) Slot_a bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
OKAY [ 0.026s]
finished. total time: 0.026s

However, trying to relock with "fastboot oem lock" does not seem to work:

$ sudo fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
[ASUS ZenFone 8] KKF32:
kinda same problem here...

LOS stuck on boot animaiton

Today I tried a fresh install to my Zenfone 8 , flashed a new LOS4microg recovery, formated data and sidloaded a new LOS4microg image plus magisk zip.

Everything worked fine, no errors but at booting it stucks at boot animation.(waited 10 min)

Managed to get into recovery again, formated again and flash normal LOS this time, without magisk, but... same boot animation loop.

How to get out of this? Maybe temporary boot TWRP and advanced wipe?

I have no clue at this point, no real experience with TWRP, advice would be very welcome.
[ASUS ZenFone 8] kimiivanovic:
This might help you, at least it worked out in my case :)
[ASUS ZenFone 8] roomanus:
Hey there,

you have to read and execute the instructions regarding flashing twrp carefully:

ASUS ZenFone 8

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me

you have to boot it first, then when booted flash it via "Install Recovery Ramdisk option." this worked in my case.

But, before that, you'll need original vendor_boot.img and probably boot.img (not shure, i tried so many different things)...
[ASUS ZenFone 8] KKF32:
Yes, you are right, LOS4Microg "lineage-18.1-20211222-microG-sake.zip" worked fine the first try, no boot animation loop this time.

Last time I tried the latest LOS respectively LOS4microg...

Thank you!
[ASUS ZenFone 8] jaalai:
Same here :cry:
[ASUS ZenFone 8] jaalai:
Well not sure how, I tried to restart the phone several times, and the last one I kept VOL DOWN pressed => phone restarted to the previous build (20220107)
[ASUS ZenFone 8] topaza:
Actually I would just ignore this. There is no reason to access fastboot from the recovery. Recovery may fail like you already experienced. If you cannot even access the bootloader you have an expensive brick anyway ;) (but not seen a single phone where that ever happened) So if fastboot works in the bootloader everything is fine! :)

Thanks for testing. I read that ASUS is preventing relocking on other phones. So maybe they also do this here.

There are some other similar commands that you could try like "fastboot flashing lock" or "fastboot oem relock". But I think at least one of them is rather old and will probably not work. Maybe ASUS just wants us to stay unlocked so they can refuse warranty.
[ASUS ZenFone 8] ZVNexus:
That's how A/B works, if it fails to boot enough times it will switch to the previous slot, which for you had the previous build.

As for why the build is failing for people, it looks like it's broken on every single device, and only if the user never used ADB. It will be resolved in today's build: https://review.lineageos.org/c/LineageOS/android_system_core/+/321935
[ASUS ZenFone 8] jaalai:
new build installed, all good 👌
[ASUS ZenFone 8] topaza:
Did anyone try to get ASUS Cam from this Thread working with LOS + MicroG? (or GAPPS)

https://xdaforums.com/t/asus-stock-camera-app-please.4370033/post-86306327
[ASUS ZenFone 8] eVen123:
I can't for the life of me, get this to work.

Flashing the supplied sake_vendor_boot.img makes me unable to boot to TWRP at all (even by feeding it through "fastboot boot twrp.img" command). It just takes me to ASUS logo.

If I try to flash it without flasight the "vendor_boot", it just fails to install. Tried several versions, upgraded to 12 (didn't try to flash over android 12 though), downgraded back to android 11. Nothing works for me.

I got further trying to install LOS4microg - some errors during installation, got to the "white screen" after booting. I'll reattempt now, posting what I find after. Currently flashing fresh "WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google" version ("update_image.sh").

I am not confident this will work. I managed to install ArrowOS somewhat smoothly, but LOS is giving me a lot of issues.
[ASUS ZenFone 8] chrisrevoltes:
What boot.img are you refering to?

I tried flashing vendor boot (fastboot flash vendor_boot .\sake_vendor_boot.img) like stated here and than booting into twrp (fastboot boot .\twrp.img) like stated here. But after reboot it stucks at ASUS logo, till I hardrestartet it. Happens everytime. booting to TWRP without flashing vendor results in the same outcome.

Btw. I had the same outcome even bevor flashing LOS recovery and LOS.

Any ideas?
[ASUS ZenFone 8] roomanus:
Hey there,

so you havn't seen TWRP at all, right? Didn't boot, stuck immediatly?
[ASUS ZenFone 8] roomanus:
In my case, if i remember it right (it has been a while and a lot of trial and error trials):

1. Extract vendor_boot.img and boot.img from the latest official Asus release (in my case: UL-I006D-ASUS-30.12.112.72-1.1.31)

2. Flash both of them.

3. Sideload Lineage (and Gapps if you want them)

4. Start lineage and do first quick setup.

5. Reboot to bootloader

6. Again, do step 2.

7. then boot to twrp via fastboot boot

8. do the alternate Installation Method: Advanced>Install recovery Ramdisk.

9. Reboot Recovery, hopefully comes back.

Hope i remember right and it helps, tell me if you stuck somewhere, i'll try to help...

Cheers..
[ASUS ZenFone 8] chrisrevoltes:
Correct. It stuck at ASUS logo after fastboot boot twrp.

Interesting but strange.

Did you temp boot to TWRP via fastboot boot?

Edit: how did you get the vendor_boot and boot images? I cant extract them from the payload. Tried zip and some tools I found. But non worked.
[ASUS ZenFone 8] roomanus:
yes, sorry, Step 7. boot to TWRP via fastboot boot.

try this: https://github.com/ssut/payload-dumper-go

Fingers crossed...:)
[ASUS ZenFone 8] chrisrevoltes:
So first of all the payload dumper worked great. But unfortunatly that didn't helped much.

The main problem is, to flash everything to the correct partitions. But I have managed to flash TWRP directly to the boot partition like captain_throwback proposed:

But I'm still not sure if i flashed it correctly, because after switching the A/B partitions TWRP is gone again. On the other hand, as already written in the other thread, I have no idea how this works with A/B.

For the record:

fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot' (98304 KB) OKAY [ 2.380s]
Writing 'vendor_boot' OKAY [ 0.224s]

fastboot flash boot .\twrp.img
Sending 'boot_b' (98304 KB) OKAY [ 2.238s]
Writing 'boot_b'

As seen TWRP is always written to one partition only. But adb sideloading inside TWRP writes LOS to the other partition (as thought for an update) Btw. I tried the original vendor and the LOS vendor. Ill try again tomorow....
[ASUS ZenFone 8] chrisrevoltes:
I got it running. After a lot of try and error that's what I found:

Currently (Jan. 22) the LOS vendor image is NOT compatible with TWRP! If you first flash the vendor image and then ether flash or boot TWRP it will just stuck an the ASUS logo.

I don't know if that's could be a issue in future but for now, I reflashed the original vendor extracted from an update unsing this payload dumper. And then followed the TWRP instructions.

Here my steps:

With unlocked BL, booting to BL already done and working adb/fastboot drivers

(Reflashing original vendor (only needed on non stock devices))

fastboot flash vendor_boot vendor_boot.img

Booting TWRP:

fastboot boot <TWRP Image>.img

(Doing a faktory reset if needed)

Sideloading LOS (TWRP flashes it to the

inactive

slot)

In TWRP: Advanced -> ADB Sideload -> Swipe to Start Sideload

On PC: adb sideload <LOS Image>.zip

Let TWRP flash itself

In TWRP: Advanced -> "Flash current TWRP"

If further packages are needed (like gapps oder magisk)

Change slot (In TWRP: Reboot -> Slot x) or reboot to recovery

Either sideload them oder adb push them to sdcard and use TWRPs install method.

Sideload: see 4.

ADB Push: adb push <package> \sdcard

Reboot to system.

For reference: My images

LOS: 18.1-20220121 lineage-18.1-20220121-nightly-sake-signed.zip

TWRP: v3.6.0_11 twrp-3.6.0_11-0-I006D.img

Stock Rom: Version WW-30.12.112.72 from 2021/12/17

I believe the with every LOS update its required to let TWRP reflash itselve, otherwise the original LOS recovery will be used. I read somewhere that TWRP does this by itself when flashing, but I am not sure if this is really the case.

But as stated, I'm not sure if that's the correct way. Unfortunately didn't get answers till now.

-------

Edit: Format, links and commands
[ASUS ZenFone 8] Winnie_LD:
Vibration is now working, guess it was the last update from Friday, Feb 04?

Thank you anyway, @ZVNexus ! Great Work!
[ASUS ZenFone 8] ZVNexus:
Like I said earlier in the thread, just keep in mind I don't support or endorse using TWRP for LOS.
[ASUS ZenFone 8] chrisrevoltes:
Totally okay. Could you perhaps explain what the difference is between the (your?) LOS vendor boot image and the stock vendor?

Could it be that some functionalities did not work?

Does it make sense if I (and others of course) still give feedback, or does it not help you anymore?
[ASUS ZenFone 8] ZVNexus:
The vendor boot image is completely different from the vendor image, vendor_boot is for fstab in first stage ramdisk and recovery modules.
[ASUS ZenFone 8] igor47:
using this as my daily driver and loving it so far! main bugs that are affecting me:

* the full-screen flash when unlocking with fingerprint reader, which ZVNexus mentioned is unlikely to be fixed

* when I turn on Night Light nothing happens, same for any of the Color setting modes (natural/boosted/adaptive), or Reading Mode

* I have AccA installed with the ACC daemon, root through Magisk. the app reports that everything works fine, but charging control doesn't happen and the phone always charges to 100% when it's plugged in

i would love to get the second two issues fixed, let me know if i can help somehow -- beta-tester? contributing to a bounty?
[ASUS ZenFone 8] ZVNexus:
Night light was addressed in Lineage 19, the fix was backported in the build last Thursday.
[ASUS ZenFone 8] igor47:
i'm running the build from Feb 4th, and nightlight continues to be broken. is there anything i can do to prod it? maybe a hack like the toggle-always-show-time-to-fix-DTW one?

edit: i looked at the changelog for lineage-18.1-20220204-nightly-sake-signed.zip and the only relevant change seems to be this one but that still doesn't look particularly relevant. was the change you mention backported to 18.1 from 19? in any case, i grabbed a logcat from when i enable night mode. it looks like this:

with that last message repeating many times
[ASUS ZenFone 8] Sarum4n:
Fora such as this one are often full of problems and questions, and not so much the success stories (because what is there to tell, right?) So just as a counter point: three days ago I received my Zenfone 8 16/256, and I installed LOS18.1 nightly, including LOS Recovery and MindTheGApps, with no noteworthy problems. Works like a charm!
[ASUS ZenFone 8] Malko007:
Hello , sorry for asking but i see a lot of update on LOS ...but nothing recent on LOS4microg. Is this normal? When can we expect an update?
[ASUS ZenFone 8] NisseGurra:
los4Microg has slower updates, next should be up tomorrow
[ASUS ZenFone 8] ZVNexus:
yeah I'm dumb I didn't backport properly, should be fixed in tomorrows build
[ASUS ZenFone 8] eVen123:
Hello!

The thread is mostly about discussing issues and doesn't get the praise it deserves: I've been rocking this ROM for a while now as daily driver. Very stable, no crashes. Perfectly usable.

Some facts worth considering:

The fingerprint sensor doesn't work while screen is off. You have to wake the phone first (key or double tap if enabled)

The fingerprint sensor makes the screen go full brightness.

The fingerprint sensor is significantly faster than on stock ROM.

The app switching is significantly faster than on stock ROM.

The audio recording is not as good as on stock ROM. I tried installing default app, but it doesn't record as well - I think stock ROM does some automatic gain control. This is a significant loss for me, but I guess irrelevant for most.

There is no vibration intensity control and the stock vibration is very mild. If I have phone set to vibration and carrying it in pocket, I easily miss calls.

Due to the last issue, can this be solved with some external modifications perhaps? Magisk module? Some prop edits? If anyone knows, please @ me.
[ASUS ZenFone 8] igor47:
YES! installed the fresh build today, confirm all display features work now including night light and grayscale mode. i definitely still have to enable/disable "always show time and date" to get double-tap-to-wake enabled after every update, minor inconvenience, re-installing magisk after every update is much more annoying :p