yashsingh1/xdaforums huggingface dataset:
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Error-404-Go-Home:
Well, uh, that might be a good thing or a bad thing. Let me check...

Edit:

I have attached screenshots verifying the core clocks.

I haven't even installed a kernel manager up to this point (I have never been able to completely lock the CPU to a specific frequency like this anyway, it always seems like the kernel takes it as more of a suggestion). I had only checked the performance and frequncies of the device with the app 'CPU Throttling Test' and noticed significantly lower numbers.

I don't know how I accomplished this, but I think I might leave it this way since my phone lasts about 4 times as long on a charge with my regular daily use

Thanks for letting me know this wasn't intended functionality though; I'll definitely let you know if I figure out what's going on with this!

BTW, is the USB 3.0 bug a me-specific issue as well, or have you seen it replicated? I am starting to consider a clean flash again

Edit 2: CPU clocks were fixed when I flashed the latest update (May 22, 2022)
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Shreyash_drogon:
@aleasto hello , i was using the latest build and noticed that the touchscreen gestures not fully working.

W S E are not working

Others are working. please look into it
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Timmmmaaahh!:
Remember when people used to logcat issues? Good times...
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Shreyash_drogon:
gestures in your phone working?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Error-404-Go-Home:
How?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Timmmmaaahh!:
I don't own this device; just looking around :)

If you can't find out how to logcat, you probably shouldn't be flashing ROMs. But it's a free world; do as you please. On this forum it's just important to provide solid feedback in development sections. Saying "it doesn't work" is not constructive. It can still be valuable I guess, depending on how much work the dev is willing to invest into troubleshooting issues. It's a heck of a lot easier to them when logs are provided.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Shreyash_drogon:
Yes

Sorry i should have provided the logs
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] SpoonPants:
Hey @aleasto Thanks for all your hard work keeping my ROG3 running Lineage. Much appreciated.

I noticed one issue. When I make a phone call and hold the phone to my ear, the screen does not turn off. This leads to my cheek opening other apps and changing settings.

Is there a setting I can change to fix this? Or is this caused by something else?

Thanks
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Shreyash_drogon:
proximity sensor doesnt work in LOS
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] SpoonPants:
That explains it. Thanks for the quick response
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] amr elfiky:
Are there plans for Lineage OS 19 ?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Hentacler:
I am using this ROM on a daily basic, but... it is a shame that just two flaws turned it from perfect to barely usable:

- The proximity sensor doesn't work. I lost count of how many times I had my calls interrupted or toolbar buttons accidentally clicked during a call.

- Camera stabilization doesn't work and gives a green screen. At least, I found no camera app where it works.

To some degree, stabilization can be performed later using ffmpeg, but this is not the same.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] amr elfiky:
Anybody else experiencing the phone not unlocking and keeping asking for pin number but not unlocking after inserting it ?

It continues a few times unless you reboot or it unlocks sometimes eventually.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] ariewahyu:
Please update the lineage os 19.1
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] amr elfiky:
There is a a warning on the official website saying it's no longer maintained.

Info about obiwan | LineageOS Wiki

wiki.lineageos.org
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] SpoonPants:
Good catch. I was wondering why there were no updates the last few months. Aleasto we had a good run with official support.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tonyxboy09:
is the aero cooler working on this rom???thanks!!!!
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Tried 3 versions of stock raw firmware, all flashed fine without showing any errors on terminal. So download seems fine.

Someone on reddit suggested to a person with similar problem(getting bootloop on downgrading from android 11 to 10) on pixel 4 that updating android platform tools to latest helped him. But the raw firmware zip already include all the files in platform tools. So updating platform tools means replacing files in raw firmware zip? Is it useful/safe to try?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
What is this raw firmware zip?

And how did you flash it?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Used the raw firmware zip files from this thread - https://xdaforums.com/t/unbrick-raw-revive-your-bricked-asus-rog-phone-3-05-dec-2020.4151443/

Tried .99 ,.98, .58 versions from there.

Flashed them from command prompt on PC by running *flashall.bat from the extracted raw firmware zip folder.

Used the raw firmware files as trying to flash normal Asus ROM zips failed on twrp.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
I updated lineage recovery in my download folder to let you flash stock zip from there, if you want to try.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Thanks a lot for the fast update

But it didnt solve the issue. After installing this new recovery i was able to flash .99 full rom zip from twrp . I formatted the data before flashing the rom. On rebooting got bootloop again. so next tried flashing full rom zip on both a and b slots from twrp after formatting data. still stuck on bootloop.

so Installed 18.1 again (without issues)

Also would like to report a small bug i found on 18.1 earlier today. Bluetooth audio seems to output no sound, while bluetooth calls are working fine.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
it's not twrp, but ok.

you flashed some real bad firmware then...
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Oh sorry, meant los 18.1 recovery you posted.

Firmware I flashed was from official Asus link and from links in the deadlyindian's forum I posted earlier. So you mean the firmware file I used was corrupt?

Even then flashing raw firmware must have fixed it right? Flashing of raw firmware from PC terminal showed no errors so far and completed fine on about 10 times I did it so far. Also 18.1 is working totally fine.

Please also see the small bluetooth bug ( I edited in) I mentioned in my last post.

Thanks
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
There's no reason for 17.1 or omni to not work then.

For omni you do have to make sure to have stock vendor/odm on the inactive slot before flashing, because omni doesn't ship its own and it won't work with lineage 18.1 vendor (and maybe with 17.1 vendor either).

Will look into bluetooth.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Both 17.1 los and omni went into bootloop on flashing directly after stock raw firmware flash. Think the issue maybe the vendor partition is not getting restored on flashing stock firmware from recovery or PC.

Anyway to restore stock vendor partition alone or make sure vendor partition is getting flashed?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] yidu92:
only 18.1 ROM works on my ww rog3 , all other ROMs are bootlooping even flashing the Asus raw firmware is resulting in bootloop
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
2/2 issues with "asus raw firmware". Sounds like you shouldn't be using that.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
@yidu92 @tuxing mind sharing the output of

fastboot getvar all after flashing stock, from Lineage Recovery > Advanced > Enter fastboot ?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
"Unfortunately" that looks good to me.

I'm confident it doesn't have to do with lineage-18.1; but I cannot explain why you can only boot this.

Fwiw I can switch between 17.1, 18.1 and stock without issues.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Flashing raw, boot to recovery, FORMAT data. That should fix your issue
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
To stress it further, make sure that if using TWRP you use FORMAT and not WIPE data
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] yidu92:
But it still doesn't work，I'm going to crash

:cry:
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
It would be fastboot format userdata anyways.

Try booting up 18.1, enabling adb + rooted debugging

Then dirty flash 17.1 and see if you get adb while "bootlooping"
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
New build out

2020/12/22

Fixed bluetooth audio

Moved framerate settings to Settings > Display > Advanced > Minimum refresh rate
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Thanks aleasto

Just upgraded to new build and Bluetooth audio is working fine. First flashed ROM alone from los recovery, then got google play services error. Then rebooted and flashed nikgapps core, had to enter google accounts again and also contacts option is not present in sync. Think there is a better way and I am doing it wrong.

About unable to go to any other ROM issue @bs3pro yes I have made the mistake of wiping data than formating data in the past , so I am aware of that common error we make. I had tried formatting data from stock recovery after flashing raw firmware at least 5 times. Phone gets stuck and reboots on republic of gamers screen if I don't switch off(then if can enter recovery from bootloader), if I switch off and restart , phone gets stuck at bootloader/fastboot screen and will not even enter recovery.

Some person on reddit had talked about warning in @yidu92 s screenshot( first screenshot marked 1 flash raw) of not formatting raw data and someone suggested solution as updating android platform tools.

@aleasto what other method do you suggest to return to stock ROM than flashing raw firmware file as you clearly seems to dislike raw firmware flash? Yes I was able to flash stock ROM from the los recovery you provided, but if that doesn't help isn't flashing stock raw firmware the only option? Is there any other option to return to stock and get partitions back to stock? The source of stock raw firmware files is not clear, is there a better source? If its a bad firmware flash , what is the option out?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
If you don't do anything stupid you don't ever need to touch all those partitions. Non a/b partitions are never updated by stock or any custom rom. You just replaced what came preinstalled to your phone with some random dude's on the internet and you have no way of going back.

Even flashing official stock zip now you'll only replace partitions that are a/b.

Actually looks like it doesn't do too bad stuff, other than rewriting gpt
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
I had linked you to the xda forum from which i got the files . As its on xda and many people was reporting to have used it successfully i used the files.

Now some curious thing happened after i made the last post. I again flashed .98 stock firmware zip from los 18.1 recovery after formatting data. got the same bootloop , but the i again formatted data from stock recovery some 3 more times and let the phone bootloop. After some time lineageos animation started to come up, show for some 30-60 seconds, then the animation gets stuck and phone restarts. Does this mean stock rom is not getting flashed?

sorry for being naggy , just want to find a solution.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Your phone probably switched the active slot back to lineage's
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
You sure your letting raw finish? It takes a while to flash super. Maybe your not letting it completely flash. Either that, or your data is booked.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Want to try https://drive.google.com/file/d/1IwgNlWwMpt3UZbxu_ZI3QBQkWtvpRKkj/view?usp=sharing ?

Lineage Recovery > Advanced > Enter fastboot

fastboot wipe-super super_empty.img

Then format data and flash lineage 17.1 zip in recovery
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Attaching the full terminal output of flashing raw .99 firmware. @bs3pro

@bencozzy where can i find the EDL flashable firmware? is the file ROG_PHONE_3_ZS661KS_UNBRICK_EDL.7z from deadlyindian s forum the one to use? or is there a separate recovery tool that can be used with newer firmware?

How can we enter edl mode?

Thanks a lot for the help

edit: reattaching file as earlier the file failed to attach
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Thanks , shall try that and report back.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Tried Lineage Recovery > Advanced > Enter fastboot from both los 17.1 and 18.1 recovery, in both no fastboot device is detected on pc and on entering fastboot wipe-super super_empty.img it showed "waiting for any device"

i used the side usb c port and on connecting the phone in this mode to pc showed asus_xx device detected but no fastboot device was shown on fastboot devices sommand.

Can this fastboot command be tried from normal fastboot than fastboot in los recovery?

Also secure boot is shown as yes on this enter fastboot screen . is that ok after unlocking?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Side port is correct.

No, you cannot use bootloader fastboot.

Update your fastboot client.

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com

Secure boot is fine.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Downloaded the platform tools in the above post and ran the wipe-super command using fastboot.exe from the new platform tools folder. no fastboot device is detected and still only gets "waiting for any device" on running the wipe command.

sorry for being a noob , any other way to use updated platform tools?

had used minimal adb and fastboot earlier.

Thanks again for helping patiently , shall continue with your suggestions tomorrow , its 2 am at my place , need to catch some sleep before going for duty. see you tomorrow.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Try installing these drivers https://github.com/koush/UniversalAdbDriver

Or a different OS.

Or a different computer.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
just did this and flashed lineageos 17.1 , still getting bootloop

terminal output had errors, but think it was not significant , its given below.

c:\platform-tools>fastboot.exe wipe-super super_empty.img

Sending 'super' (392 KB) OKAY [ 0.010s]

Writing 'super' OKAY [ 0.005s]

fastboot.exe E 12-23 13:52:54 6044 4756 file.cpp:192] unlink C:\Users\***\AppData\Local\Temp\TemporaryDir-a04756/super.img: Permission denied

fastboot.exe E 12-23 13:52:54 6044 4756 file.cpp:180] rmdir C:\Users\***\AppData\Local\Temp\TemporaryDir-a04756: Directory not empty

Finished. Total time: 0.043s
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Ok then I'm out of ideas. See if you can grab a logcat:
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Dirty flashed 17.1 but no adb was detected by "adb devices" while bootlooping

after some bootlooping ,Phone rebooted to los 18.1 , Tried dirtyflashing 17.1 again two times and some more bootlooping and back to 18.1. The recovery stayed at 18.1.

Forgot to mention , dont know whether its important - Very First time while i installed 18.1 , i had also rooted the rom with magisk 21.1, later uninstalled it from magisk manager which resulted in a bootloop then.

yes , running cmd as admininstrator

@aleasto about 18.1 rom - sometimes on rebooting mobile data gets randomly disabled. Speakers sound good, but at near full volume bass overpowers and causes distortion.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] yidu92:
My problem is solved and it can be used normally，（Android bottom partition）
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Please elaborate how you fixed the problem. Will be of great help.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] yidu92:
Remotely processed by my friend.He uses the script to flash the img.and then it can boot normally.

You can try.(https://drive.google.com/file/d/1zDv4lt6nHl7BPQnsEWAhm7KrVCSsCCQn/view?usp=sharing)
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Tried the link, but can't access file as it tells access is denied and asks me to request access(I have requested access). Please make file accessible and share again.

Can you elaborate about the script & which .IMG was used.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
{Mod edit: Quoted post deleted!}

Think it will be beneficial to have the solution here as we both( me and @yidu92 ) possibly made some mistakes the other users of this ROM may make. :)
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
New build out

2020/12/23

Updated kernel and proprietary files to UL-ASUS_I003_1-ASUS-17.0823.2012.122-1.1.86-user

Make sure you update firmware to the same version, since it fixes VoLTE being lazy on automatic network selection.

You can grab it from here, and flash it in recovery to both slots:

flash recovery -> flash zip -> reboot fastboot -> reflash recovery -> flash zip

or flash it once, reboot, and use copy-partitions.zip like suggested for other a/b devices
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Unable to access the file. Please share details over PM. I have PMed you.

Please help.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] yidu92:
@Echo off

color 3f

adb push 1.img /temp/1.img

pause

adb shell dd if=/temp/1.img of=/dev/block/by-name/persist
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Thanks a lot yidu92.

@aleasto yidu is suggesting restoring persist partition with the above script (He also shared a 32 mb .img file of persist partition) helped to revive his rog 3. I Had a twrp backup of persist partition(shows to be 2mb in size) from earlier stock rom, but trying to restore persist partition failed in twrp with partition is read only error.

what do you think , can persist partition be the cause of the issue? Just wanted to take your opinion before flashing the 32 mb .img file.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Yep, probably some selinux context changed which Android 10 roms don't recognise.

It's among the reasons why you shouldn't downgrade.

Beware that the shared 1.img will make your device WW on stock (it's already on lineage though it doesn't matter)

Using a persist image from someone else will break your fingerprint reader indefinitely.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Thanks , shall try to flash persist 1.img and report back. Hope the persist partition is not individual device specific and is common to all ww devices. Is there anyway to try restoring my twrp backup(tried in twrp, giving error partition is mounted read only) of persist before trying flashing yidus 1.img ? The 1.img file is 32mb , my twrp persist backup is only 2mb , is the sizes OK?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
32MB is the full size of the persist partition. 2MB sounds like it could be the occupied size

Using a persist image from someone else will break your fingerprint reader indefinitely.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Thanks a ton @yidu92. Flashed the persist 1.img with the 1.bat script (above) you provided. Then flashed raw stock firmware .99. VOILA - the phone is back. no more bootloops on stock rom.

Thanks a lot @aleasto for being very patient with me & my stupid questions.

Thanks @bencozzy

Later updated to .122 stock rom. Has a minor issue , can't setup fingerprints. On fingerprint enrollment screen, message enrollment not complete pops up and nothing can be done.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
PSA: Using a persist image from someone else will break your fingerprint reader indefinitely.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] tuxing:
Lesson learned.

Precious words from a rom developer who was constantly nagged by a noob.

"su

dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img"

Always have an original working persist backup ready before diving into rom flashing.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Captain_Throwback:
You'll be able to back it up properly in TWRP with the official release.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] AdheRamaID:
my Fingerprint on display not working after back on android 10 stock rom , any solution ?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Reading 3 posts above yours and OP
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] moslondon:
This device might be my next phone if LOS works properly with VoLTE in the US. Any AT&T or Tmobile user in this forum?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Yes, dont bother. Its broken
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
I think ASUS had issues getting the device certified for VoLTE on Tmobile on stock, but it should work under Lineage.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] lou_lou_boy:
Hello! I’m not at all trying to rush you or nag, I’m generally curious why the fingerprint is not working on this Rom? This seems to be an issue with a lot of phones. Any help is appreciated, thank you!
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] darudedudedocta:
Hi

first to the dev..thanks for your efforts..

secondly ..how is the battery life on the rom as I am thinking of switching over

thirdly.. does the face unlock work? is the rom daily driver material?

Thanks in advance
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Non standard interfaces

No face unlock, we don't do fake biometrics yet
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
New build out

Fixed video recording

Fixed crash in Android Auto (and likely more apps)
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Error-404-Go-Home:
Spoiler content hidden.

Edit: Never mind, Question has already been answered.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Volte works perfectly fine on stock.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Error-404-Go-Home:
I have spent the majority of the last two days getting my phone back to stock. I found out the way I was restoring my persist partition was wrong. I backed it up with TWRP as a .ext4.win and cannot restore it using dd as yidu92 did it. I ended up using the 1.img provided by him, but, of course, cannot use the fingerprint sensor. Does anyone know of a way I could convert the TWRP backup file to a flashable image, or a way to allow TWRP to flash the persist partition (it is mounted as read-only)?
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] aleasto:
Share your perskst backup with me, I'll make a working persist.img for you. I still don't know why me and others don't hit this issue...
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] bs3pro:
Wondering the same thing. Why is ANYONE messing with their persist partition? BTW, will lineage ever add weather to AOD again? I miss that feature.
[ASUS ROG Phone 3 ROMs, Kernels, Recoveries, & Othe] Error-404-Go-Home:
Here you go (I added .img to the end so that it could be uploaded) Thanks! : )

Edit: File removed for security reasons.