General Boot / DTBO Images [Root / Stock] - 5 / Pro / Ultimate (NOT S)

[twistedumbrella]

These images are NOT built from source.

These are the stock images from the firmware provided by Asus that are extracted with payload dumper and uploaded without modification.

18.0840.2202.231

18.0840.2201.226

18.0840.2112.211

18.0840.2111.200

18.0840.2111.196

18.0840.2109.188

18.0840.2109.176

18.0840.2107.151

18.0840.2106.86

18.0840.2104.56


You must have already unlocked the bootloader to flash these images. If you have not unlocked the bootloader, you will need to install and run the Unlock Device App from Asus before continuing.

You will also need fastboot to install these images. If you do not wish to install the Platform Tools Package, there is a portable package available. Extract the archive and move the images to the same folder as fastboot.

Each folder on AndroidFileHost contains the stock boot image, stock vendor_boot image, and stock DTBO named by firmware.

fastboot flash boot [/path/to/image]

fastboot flash vendor_boot [/path/to/image]

fastboot flash dtbo [/path/to/image]

Root images have been removed due to misuse. As a reminder, do NOT lock your bootloader without restoring stock images FIRST.

If you want a rooted device, the stock boot image can be used with the "Select and Patch a File" install option in Magisk.

If you have wiped your device or uninstall magisk, even with a rooted image, root will not work until the app is installed again.

The vendor_boot and dtbo are flashed when restoring from a custom kernel. They are not required to (un)root your device.

 

[JazonX]

Can the Vendor Boot image (Patched) give read/write access to system via root explorer ?

May sound stupid, But I was wondering.. ^^

I used to patch the hosts file manually, and replace it in system,
Now I need the magisk hosts module, and the adaway app both.

 

[twistedumbrella]

Can the Vendor Boot image (Patched) give read/write access to system via root explorer ?

May sound stupid, But I was wondering.. ^^

I used to patch the hosts file manually, and replace it in system,
Now I need the magisk hosts module, and the adaway app both.

Doubtful. The new Android layout is a mess. The actual purpose of the vendor image is for Google to make generic base kernels and have all the customization as an overlay. It isn't the vendor making the system read only. That is part of the partition layout and firmware structure.

They use images that are much larger than the partition size, but compressed and mounted like a virtual machine. Even though the old "Ubuntu on Android" mods did much the same thing and allowed editing, I believe they locked these up to prevent issues with changing the compressed size or flat out lack of necessity to write the code.

 

[twistedumbrella]

https://xdaforums.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/

Leaving this here for anyone that ends up using these images to root the device

 

[JazonX]

Doubtful. The new Android layout is a mess. The actual purpose of the vendor image is for Google to make generic base kernels and have all the customization as an overlay. It isn't the vendor making the system read only. That is part of the partition layout and firmware structure.

They use images that are much larger than the partition size, but compressed and mounted like a virtual machine. Even though the old "Ubuntu on Android" mods did much the same thing and allowed editing, I believe they locked these up to prevent issues with changing the compressed size or flat out lack of necessity to write the code.

Did you come across this tool ?

 

[twistedumbrella]

Did you come across this tool ?

Neat party trick, but fundamentally just piece of mind. You end up using a bunch of space that could just as easily be a fraction with modules. We have a super partition, but no custom recovery. You will be running it with a live install, which is a whole lot of risk for partition corruption. The partitions on this seem a little too finicky. I couldn't bring myself to try.

https://xdaforums.com/t/script-android-10-universal-mount-system-read-write-r-w.4247311/

(For our friends that prefer the preview panel)

 

[twistedumbrella]

Added V18.0840.2109.176

 

[twistedumbrella]

2109.176 and 2109.188 may be interchangeable. There appear to be no kernel changes.

 

[twistedumbrella]

Added V18.0840.2109.188

 

[twistedumbrella]

Added V18.0840.2111.196

payload_dumper is returning an empty image for vendor_boot, so it was not uploaded. I am not sure if this is because it is a legitimately empty image or some other issue. If anyone happens to have different results, please let me know. I will investigate further.

 

[arctic4x4]

Added V18.0840.2111.196

payload_dumper is returning an empty image for vendor_boot, so it was not uploaded. I am not sure if this is because it is a legitimately empty image or some other issue. If anyone happens to have different results, please let me know. I will investigate further.

the vendor_boot.img I have extracted is 98,304 kb which I just downloaded yesterday.

 

[twistedumbrella]

the vendor_boot.img I have extracted is 98,304 kb which I just downloaded yesterday.

It extracted fine today. Who knows.

 

[starshina1976]

it boot patched magisk, or stock pulled from the firmware?

 

[twistedumbrella]

it boot patched magisk, or stock pulled from the firmware?

I don't know what you're asking, but both are provided.

 

[starshina1976]

I mean, is the kernel stock, or patched? Sorry, I'm using a translator.

 

[starshina1976]

I need it for firmware 196. Rog phone 5.

 

[twistedumbrella]

I mean, is the kernel stock, or patched? Sorry, I'm using a translator.

boot-(version),img is stock
boot-(version)-magisk.img is patched.

 

[starshina1976]

Thanks, I will try.

 

[messhary]

I just load the boot.img you posted it for
root.

18.0840.2111.196 for my same firmware and relocked my bootloader

So now I'm Stucked on bootloader i can't even go recovery

 

[messhary]

So after you ruined my experience on mobile any help can help me with