Database Info

Request for a Guide

I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.

prestonmcafee said:
I'm not so happy with EMUI 8/Oreo on my Mate 9. Several widgets don't update, requiring me to change the screen resolution during the day (weird temporary fix). I'd rather run Nova but EMUI pushes against that. I have a pretty good backup phone (ZTE Axon 7) so I thought I would give a generic system image a try. The last time I rooted and installed an alternative ROM was 2014, so I'm rusty. I successfully put minimal fastboot on a PC, unlocked the bootloader and installed TWRP 3.2.1-0 (something may have gone wrong already at this point since I accessed it by vol up + power, rather than vol up + vol down + power). Then I installed the generic system image. It booted, but gave error messages at boot. Perhaps all I needed to do was install it a second time, but instead I tried installing a different image, achieved bootloop, made matters worse, and was rescued by the amazing and wonderful FunkyHuawei.
I am thinking about trying again, but I wondered if an expert would write a more patient guide that provides the exact steps to flashing a generic system image. By the exact steps, I mean with links to files and what you type in minimal fastboot (if indeed that is the right program), or when it is best to install from an SD card. I'm sure such a guide would get more people to try other ROMs besides the generic ROM.
Click to expand...
Click to collapse
By a generic system image, you are referring to wanting to install an aosp image (treble ROM), correct?

Yes.

prestonmcafee said:
Yes.
Click to expand...
Click to collapse
And obviously you still have your bootloader unlock code?
Also what Mate 9 version do you have and what exact firmware is it running?
I can help ya out no problem. Just obviously want to make sure you avoid going through that again

Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.

Sorry, MHA-L29 8.0.0.360 (C567)

prestonmcafee said:
Thanks, Wirmpolter! I have the unlock code, but it shows as unlocked, at least I get the dire warning about the device being unsafe on boot. I have the US model, build number MHA-L29 9.0.0.360 (C567), with both Android and EMUI versions listed as 8.0.0.
Click to expand...
Click to collapse
Oh...You're already bootloader unlocked that makes it even easier.
I'm using the system.IMG form the thread below this paragraph. Tried a few different aosp ROMs and it seems to be the best so far. Aside from a couple things of course. And the honor 8 Pro is the same CPU, GPU found in the mate 9.
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564.
In the main post of that thread, just follow step 2 and 3 and you'll be good to go for having an aosp ROM.
As for magisk/root... You can follow my guide below that I posted the other day. Just let the aosp ROM boot up once first. Also I can extract the ramdisk.IMG you'll need if you can't once you check it over.
https://forum.xda-developers.com/mate-9/how-to/guide-install-magisk-mate-9-running-t3773878
Basically in a nutshell to get setup on an aosp ROM is as follows
1 Download the ROM from the first thread i posted
2 Extract the system.img to where your adb folder is
3 Run command prompt from there
4 With your phone powered off. Hold the volume up button and connect it to your computer (fastboot screen)
5 Run command fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset
8 Reboot the phone and should be good to go
Need to do first boot on its own before rooting

Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?

prestonmcafee said:
Thanks!!!
It will be about a week before I can try again but I'm looking forward to it. Are you pretty happy with it?
Click to expand...
Click to collapse
Yeah, fairly happy about it. A few bugs though but nothing major. Get better standby drain and about the same SOT time as EMUI. The only thing that is lacking is the camera in aosp doesn't use both cameras.
There is the stock camera port (works with magisk) but it's lacking a few things like video recording doesn't work... And umm not sure what else.

I needed to install an update, enable developer options and enable OEM unlocking (which was greyed out) before it would install. Here is my earlier post:
Dang, didn't work. Here is what I did.
-reset phone, but did not enable developer options.
-extracted and placed system.img in the minimal fastboot and adb folder. Ran a command prompt with administrative rights (win 10)
-shut off and connected Huawei mate 9 by USB, holding vol up
-vol up brought the EMUI restore screen. Shut off and tried again, same outcome. So shut off and tried vol down, and that brought up the fastboot screen. It reported phone unlocked but FRP locked.
-ran command "fastboot flash system system.img" and get:
target reported max download size of 471859200 bytes
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 11.167s]
writing 'system' 1/4...
FAILED (remote: Command not allowed)
finished. total time: 11.183s
I suspect this is due to the FRP locked condition.

Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!

prestonmcafee said:
Now I've run into a different problem: the EMUI screen gives me the options of
Download latest version and recovery
Reboot
Shutdown
It does not give me the option of a factory reset. What seemed to work was holding volume down through a couple of boots, when EMUI gave me the option of a factory reset. This gave me what appears to be a fully functioning system!
Click to expand...
Click to collapse
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?

OK, now that I have it up and running, here is the procedure I used, fixing what are either typos or variations because my system was slightly different. I unlocked the bootloader using instructions from:
http://www.teamandroid.com/2017/04/08/huawei-mate-9-unlock-bootloader/
I used Minimal ADB and Fastboot from
https://forum.xda-developers.com/showthread.php?t=2317790
I downloaded and extracted the system image from the link Wirmpolter provided:
https://forum.xda-developers.com/honor-8-pro/development/rom-t3758564
Here is a slightly edited set of instructions that worked for me:
a. unlock bootloader
b. reset phone
c. enable developer mode (settings/system/about phone tap on build number until developer mode is enabled), enable OEM unlock and USB debugging
d. check that FRP unlock and bootloader unlock worked by booting into fastboot screen (for me, hold VOL DOWN while booting)
1 Download the ROM from the thread above
2 Extract the system.img to where your adb folder is
3 Run command prompt from there (or use MA&F's desktop icon, which does the same thing)
4 With your phone powered off. Hold the volume DOWN button and connect it to your computer (fastboot screen)
5 Run command: fastboot flash system system.img
6 Then type fastboot reboot but when you goto run this command get ready to hold the volume up button when the screen goes off so you can get the phone into stock recovery
7 Once in the recovery, perform a factory reset [eRecovery didn't have this option, so I rebooted a couple of times while holding vol up and it eventually gave me the option to factory reset]
8 Reboot the phone and should be good to go

Up and Running!
Wirmpolter said:
Yeah, the FRP lock would prevent fastboot commands from working.
So, your system is back up and running?
Click to expand...
Click to collapse
I'm up and running. Thanks! So far, the only glitches are:
While Android can see and format the SD card (a Samsung 64GB), the SD card is invisible over a USB connection and Google Maps and my music player can't see it. File explorer and copy files to the SD card, so the SD card works.
The camera is terrible, but you have a fix for that.

I'm quite lost about how to install Magisk and a camera module
At the risk of asking too much, I have another request. I'm looking at how to install the stock camera on my Mate 9 with the AOSP, and here is my pathetic understanding of the steps.
First, I looked at your (Wirmpolter) instructions:
1. Install latest Magisk Manager from the Official Thread: https://forum.xda-developers.com/app...mless-t3473445
Follow the instructions of "Install Via Magisk Manager" in the main thread, but instead of providing the boot image (which these devices do NOT have), provide the stock ramdisk.img extracted from your Update.app using Huawei Update Extractor.
2. If you are using Mate 9 with model MHA-L29636 running on firmware ending in B362, you can download the stock ramdisk.img I extracted from official OTAs in the attachments
If you have stock ramdisk images for other devices, please share them and I'll add them to the OP.
3. Pull the patched image with adb pull /sdcard/MagiskManager/patched_boot.img, and flash the patched ramdisk via fastboot:
fastboot flash ramdisk patched_boot.img
Reboot and you shall have a properly rooted device passing SafetyNet, start playing with some Magisk modules!
Here are some questions:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and you also have to be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager -- this is an android app? Do I sideload it?
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Copy the patched boot image to your PC. If you can't find it via MTP, you can pull the file with ADB:
adb pull /sdcard/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Here is the command if using fastboot:
fastboot flash boot /path/to/patched_boot.img
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Finally, the camera image is here:
https://forum.xda-developers.com/showpost.php?p=75848917&postcount=2
It isn't clear to me how to flash using Magisk, but perhaps that will be obvious once I have magisk operating.

prestonmcafee said:
1. Huawei update extractor
https://forum.xda-developers.com/showthread.php?t=2433454
I probably need help using this. The item I need extracted is the update.app, but where do I get the update.app that I extract from? And I'm extracting ramdisk.img?
2. download file for my phone that will be the source of the update.app in #1 (MHA-L29 8.0.0.366(C567)) from FunkyHuawei? Firmware finder? or from the phone itself? (see, I'm pretty lost)
Click to expand...
Click to collapse
Firmware Finder (they have Windows desktop and Android apps for it, and there's also http://pro-teammt.ru/firmware-database/ which does the job just as well, though it's all in Russian.)
Find the FullOTA-MF firmware that corresponds to your model, download the 'update.zip' that goes with it - on the website, it's under the link 'update' in the same row. If you do it on your phone in the Firmware Finder app, hit "Download" on the relevant detail screen and it'll prompt you for which files you want.
Once you've got the update.zip, extract it, you'll find a file UPDATE.APP, which is what the extractor wants. If it throws up an error, disable CRC checking of the extracted content. (I don't recall what the label for it is and I don't have it installed on the machine in front of me...); and yes, you'll want RAMDISK.img from it.
prestonmcafee said:
3. install magisk manager (from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445):
Magiskmanager is an android app. How do I install on my phone? I was expecting this to be a windows app that would install magisk on my phone, so was thrown when it was an .apk.
Click to expand...
Click to collapse
Magisk Manager wants to create a patched ramdisk image. When it updates, it'll want to update the ramdisk image on your device (which it'll be able to do since it's running with root privileges itself anyway), but for the first pass, it needs that image provided and for you to manually flash it.

Thanks!
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.

prestonmcafee said:
That is perfect. I downloaded the correct file from FF and I will try installing Magisk tomorrow or Sunday.
Click to expand...
Click to collapse
The magisk manager app apk you just run on your phone to install it, no side loading required.

Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?

That worked
prestonmcafee said:
Thanks! Magisk installed! To flash the camera app, I first extract and flash kernel.img from update.app with fastboot, put the camera zip (extract first?) in the magisk folder on the phone to install it with magisk?
Click to expand...
Click to collapse
That seems to have worked.

Root Guide

Found this while trolling through the Chinese forums, none of this is my work, I have translated the instructions as best I can.
Disclaimers; I have not tried this, it may brick the global rom, the custom recovery is likely only in Chinese language.
You need:
Boot Loader unlock code (currently probably not possible to get)
Huawei USB drivers
Recovery image (attached)
Magisk package (attached)
files: https://mega.nz/#!PM0EmYLA!384hZjmJ9ExNc7Q8rSqssHunWSO7AxQ3GA4qet6RX4E
Extract files to a folder, open command prompt and change into this folder.
Unlock bootloader (BL unlock will clear the phone data, please do a backup)
- Obtain an official unlock code
- double-click to open the "Huawei Toolbox.exe"
- click "unlock bootloader "
- enter the unlock code in the pop up window , click OK, and wait for the phone to unlock complete restart.
Flash the third-party recovery
- Turn off the phone and connect the computer. Press and hold the “Volume Down” button and “Power button” until the phone displays the android page and release your finger.
- open command prompt and run:
fastboot flash recovery_ramdisk twrp.img
- after seeing the two OKAY feedback from the command line, the flash is successful.
Enter recovery to flash root image (this step will clear all data of the mobile phone including memory card, please make a backup in advance)
- long press “Volume Up” and “Power” ", until you see the a twrp logo, release the keys and wait to enter recovery mode
- After entering recovery, click the second item “Clear”, click “Format Data Partition” in the lower left corner, slide the slider to enter the clear, wait for the progress bar to complete
- Return to the recovery homepage, click on the last item "Advanced", select the last item "Remove data forced encryption", slide the slider to release, wait for completion
Copy the root package to the phone
- In Command Prompt type or copy the following commands
adb push magisk-installer.zip /sdcard
adb push magisk.apk /sdcard
Install Image
- Whilst still in recovery mode, click the first item to install the magisk-installer.zip package from the sdcard , slide the slider to install, wait for the flash to complete, and restart the phone
- After reboot is complete, click “File Manager”, select the apk file “magisk.apk” just copied from the memory card when install is finished, open the magisk app and click “No, thank you” in the pop-up window
- Return to the command line tool, type the code to execute, and wait for the phone to automatically restart
Fastboot reboot recovery
- after the restart, open "magisk", it should show that the installation is complete, that is, ROOT is achieved.

Anything in that forum on how to manually update phone?

technotika said:
Anything in that forum on how to manually update phone?
Click to expand...
Click to collapse
That is actually what I was looking for
But none, problem is the v20 (china version) seems to get OTA way before us, they all got v143 2 weeks ago.
I did find the menu to do it, but it only supports if the image is stored on an sdcard, and when I click it it says no sdcard found. so its impossible.

Tried same with similar results. One day eh? ?

İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader

greenblueye said:
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
Click to expand...
Click to collapse
If you read what I wrote in the first post you would see you cannot root without a bootloader unlock code.

Tested! Work bootloader code on Russia services (Cost 20USD)

belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Nice! Did unlocking bootloader factory reset your device?

Yes of course. All new Huawei and Honor do a reset after unlocking

i get bootloader unlock code from funkiehuwai for 20$
any one tried this instructions and have success?
I just wonder comments below will work?
*adb push magisk-installer.zip /sdcard
*adb push magisk.apk /sdcard
because there is no sd card support for view20?
when i opened huawei-toolbox.exe its in chinese and im afraid to continue other instructions

Did anyone use TWRP and which version?
Did the View 20 Boot correctly?
I read in a Forum, that with the view 20 doesn´t boot correctyl with TWRP. The reason should bei the Storage...
Best regards

Unlocked Bootloader
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Does that mean you rooted you device (with the files from above) or you just unlocked the bootloader?
I was able to unlock my bootloader with a code from funkyhuawei (about 18 €, site seems to be down currently). I did not use the unlock tool above, mainly because its chinese
- Enabled "USB debugging" and "OEM unlock" in developer settings
- Connected phone to PC, opened adb and used "adb reboot bootloader"
- Unlocked via "fastboot oem unlock *16digit code*"
This worked out fine. However, as far as i understand it magisk is installed over twrp (recovery_ramdisk), removing twrp but granting you root. This makes me kind of nervous since twrp has been a nice safety net on several occasions. This is why I stopped after unlocking the bootloader. Maybe someone has more experience on this? Why is there so little interest in rooting this phone?
Regards

root achieved
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards

garris_bibop said:
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
Click to expand...
Click to collapse
Well done good job:good:
İ have chinese version PCT-AL10 9.0.1.144 right now. Do you think i can use the same way? İ wonder from which version to extract recovery_ramdis.img

I have my view20 rooted
Thanks for the instructions.

greenblueye said:
I have my view20 rooted
Thanks for the instructions.
Click to expand...
Click to collapse
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?

garris_bibop said:
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
Click to expand...
Click to collapse
I get recovery-ramdisk from firmware PCT-AL10 9.0.1.129 . my phone is on version 9.0.1.144 but it worked:good:

After root i can not auto update software. 9.0.1.166 version is seen on ota but after download it says update is unsuccessful. Do you have any suggestion?

I think thats to be expected when rooted. Go for manual update I guess (https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). Personally I wouldn't bother with every update unless theres interesting new features and/or security updates. just to be on the safe side I would reflash the original recovery_ramdisk before updating! And backup your data!

NM Card
Hello !
Unless I'm mistaken, the View20 must be able to use nano sd cards (NM Card)

The Complete Pixel 3 How-To Guide (newbie friendly!)

There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623
Download: https://dl.twrp.me/crosshatch/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone

Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules

I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?

Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?

farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april

farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
1.) If you somehow have an unlocked bootloader, yes, it would work for the Verizon Pixel 3 XL. However, I was under the impression that Google will not unlock the BL for the Verizon variant and there is currently no way to "hack" it.
2.) It should work the same whether you're on P or Q, though if you want to remain with Q, make sure you download the beta files directly from Google (rather than the P images) and use Magisk 19.0 instead of 18.1.
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
You can force it to check for updates; when you unlocked the BL shouldn't matter if you're using a patched boot image.

HACK3DANDR0ID said:
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
Click to expand...
Click to collapse
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.

farfegnugen said:
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
Click to expand...
Click to collapse
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz

Homeboy76 said:
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Click to expand...
Click to collapse
Thanks so much for the info! Its difficult trying to find the current status of all the diff devices' root statuses.

Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?

CadTechBGMC said:
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
Click to expand...
Click to collapse
yes, if you are flashing with wipe all option (without removing -w) it does flash to both slots.

Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.

EMJI79 said:
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
Click to expand...
Click to collapse
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
what i do normally is to power off the device first wait for few seconds then then use key combination to get it to fastboot from power-off state. Booting from fastboot to twrp never had any issues unless i had messed up the twrp installation due to some mess i did.

SacredDeviL666 said:
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
Click to expand...
Click to collapse
I have to press the keys 40 seconds even from power off.

EMJI79 said:
I have to press the keys 40 seconds even from power off.
Click to expand...
Click to collapse
definitely not 40seconds from power off state for me. not sure whats happening there

Maybe a short video would be a help to some of us newbies

Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!

Drashnar said:
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Click to expand...
Click to collapse
That is correct. I made the same switch from an OG Pixel and Pixel XL to P3 and P3XL right after release. Unlock the bootloader before you mess around a lot since it will do a factory reset.

How about backups? Does anyone backup and restore, or not?
If so, how do you do it with this 2 partition system?

installed and I like it. I cant get the clock off the lock screen. all settings says it is off.
wished it had MicroG installed instead of gapps

How To Guide Asus ROG phone 5: unlock bootloader and root guide

Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations

Check pm's.

m8822 said:
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
Click to expand...
Click to collapse
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.

also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help

sabnack said:
also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help
Click to expand...
Click to collapse
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill

hilary trump said:
Do you know any module to hide that pill
Click to expand...
Click to collapse
I'm sorry i don't know but i will gladly look into that issue as soon as i can boot my phone, currently i'm stuck in a bootlop and my phone doesn't get recognised. i put all my hopes in the unbrick tool at this point, whenever it will be out.
I will let you know

hilary trump said:
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill
Click to expand...
Click to collapse
the root guide worked on another rog 5, however mine is completely nricked and i myslef is waaiting for unbrick tools

sabnack said:
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.
Click to expand...
Click to collapse
Connect your phone with the side port it will work.

sorankira said:
Connect your phone with the side port it will work.
Click to expand...
Click to collapse
yes it did work, i flashed every partition and now i'm locked again, recovery doesn't work, could you please dump yours and post it ? hope i'm not asking too much.
EDIT: nevermind i finally solved it, i flashed a raw img of the system, it works now, thanks for your time

m8822 said:
Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations
Click to expand...
Click to collapse
Mine causes bootloop

sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
What ? Why!
what happened? Did you get this after unlocking the bootloader or after boot.img?
My troubkeshooting will consiste of flashing raw, but i am not sure if that will lock your bootloader

sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.

sabnack said:
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.
Click to expand...
Click to collapse
I fixed the bootloop but without root access

sorankira said:
I fixed the bootloop but without root access
Click to expand...
Click to collapse
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.

sabnack said:
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.
Click to expand...
Click to collapse
Yes i used this method, and causes bootloop sadly.

sorankira said:
Yes i used this method, and causes bootloop sadly.
Click to expand...
Click to collapse
oh ! dammit it's weird... you could try to patch the boot image with another phone.
or maybe the update file isn't right for your phone. i don't get it

Somebody successfully succeeded with the bootloader & Rooting this Asus ROG 5 phone?

my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)

miguel.jackass said:
my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)
Click to expand...
Click to collapse
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money

m8822 said:
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money
Click to expand...
Click to collapse
I updated the firmware to the latest official version, extract the boot.img from the last official firmware, and installed the official unlock tool from the ASUS website, I just had to follow the tutorial.

How to root Ulefone Armor 11 5G

I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
adb reboot bootloader
Click to expand...
Click to collapse
- When done verify the connection with the phone:
fastboot devices
Click to expand...
Click to collapse
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
fastboot flash vbmeta vbmeta_null.img
Click to expand...
Click to collapse
If you receive a positive answer we can go to next step
- Install patched Boot Image:
fastboot flash boot magisk_patched_xxxxx.img
Click to expand...
Click to collapse
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
fastboot reboot
Click to expand...
Click to collapse
Done now your phone should be now rooted.
Enjoy.
Have fun

Thanks for this, I was missing the vbmeta_null.img and was getting a boot cycle. Works perfectly.

Harlock1978 said:
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
- When done verify the connection with the phone:
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
If you receive a positive answer we can go to next step
- Install patched Boot Image:
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
Done now your phone should be now rooted.
Enjoy.
Have fun
Click to expand...
Click to collapse

it works for me ... thanks!!!!

They will release an update with Android 11 for Armor 11 this summer, should i wait for that or is it just to root on? Sincerly the n00b

morwlin said:
They will release an update with Android 11 for Armor 11 this summer, should i wait for that or is it just to root on? Sincerly the n00b
Click to expand...
Click to collapse
Did you update to android11. What are your findings? Android 11 good? bugs?

So let's say I tried the steps above and I somehow ended in a boot loop. For reference, I removed the OS and had TWRP Recovery installed. I restarted while on TWRP Recovery from the phone and I been stuck on Boot Loop since. For whatever reason, for the life of me, I can't remove the battery or figure out how to enter Recovery Mode (I tried so many combinations).
Anyone know how to get into Recovery Mode or find a way to get out of this boot loop? =(
PS: These were the last steps I did:
1) adb reboot-fastboot
2) --- Reboot to bootloader
3) fastboot flash vbmeta vbmeta_null.img
4) fastboot flash recovery recovery.img (The TWRP img)
5) fastboot flashing unlock
6) - Reboot from TWRP on phone after browsing around

dummiedroid said:
So let's say I tried the steps above and I somehow ended in a boot loop. For reference, I removed the OS and had TWRP Recovery installed. I restarted while on TWRP Recovery from the phone and I been stuck on Boot Loop since. For whatever reason, for the life of me, I can't remove the battery or figure out how to enter Recovery Mode (I tried so many combinations).
Anyone know how to get into Recovery Mode or find a way to get out of this boot loop? =(
PS: These were the last steps I did:
1) adb reboot-fastboot
2) --- Reboot to bootloader
3) fastboot flash vbmeta vbmeta_null.img
4) fastboot flash recovery recovery.img (The TWRP img)
5) fastboot flashing unlock
6) - Reboot from TWRP on phone after browsing around
Click to expand...
Click to collapse
Well since this post, I just basically let my phone battery die. With a clear mind, and some help from here (https://forum.xda-developers.com/t/...h-stock-unlock-boot-loader-root-twrp.4297803/) I was able to save the phone (yay!).
I got the ROM and MPD from here: https://www.ulefone.com/support/software-download.html which lead me to their drive for Ulefone Armor 11 5G here: https://drive.google.com/drive/folders/12N1nQVACM4noSO4klyrOk0-sfEnTWMRN
1) Download ROM, SP_MDT_AFterSale_20.32.rar and PDF (RAR and PDF in the "Upgrade tools and USB driver" folder)
2) Follow the steps on the PDF which basically said to scan the port, add the scatter file then start the update. (Read full PDF before trying it)
Hopefully if anyone is frustrated out there, this helps. (I know I was not thinking rationally... lol)
PS: The drive said it might brick your phone with Android 11 but mine worked with Android 11. No issues. So good luck!

Harlock1978 said:
I'm pleased to report I've successfully done systemless root with MAGISK on the Ulefone Armor 11 5G. Turns out the process is nearly identical to the Armor 10.
Most of the information I found on this thread
First of all you need to unlock the bootloader, you can found how to do it on my previous post. Unlocking the bootloader will erase all of your data and will probably void your garanties.
I'm not responsable of any damage your phone can receive doing this procedure.
After unlocking the bootloader, everytime you switch on the phone there will be a message informing you that the bootloader is unlocked and so the phone not safe anymore.
Assuming you have done it without problem you need:
- The latest SDK Platform Tools to download Adb and Fastboot. Remember that are command line software, so the run only through command prompt
- The latest version of Magisk, in this moment is the 22.1.
- The USB driver, but you should already have downloaded it to unlock bootloader
- The latest ROM version, that you can download from Ulefone Site, here the UE and Not-UE version
- A copy of vbmeta_null.img as found here. VERY IMPORTANT
Let's start rooting your phone.
- Extract boot.img from the ROM and copy it on your phone in a directory you can easily remember (i.e. Download, Bluetooth...)
- Download or copy Magisk on the phone and install it. If it ask to install from unknown source accept it.
- Open Magisk app and choose Install Magisk NOT the App. When prompted for the method, choose "Select and patch a file". It will ask you to indicate where you have stored the copy of boot.img that you have previously stored on the phone. It will produce a file magisk_patched_xxxxx.img where xxxxx is a casual number.
- Copy magisk_patched_xxxxx.img on your PC, I will suggest the same location of Adb
- Now you have to reboot in bootloader mode by opening command prompt in adb location and run:
- When done verify the connection with the phone:
If you have received a positive answer we can go further otherwise check that you have the right driver installed.
- Let's assume you have received a positive answer. Now you have to disable the safety check of the boot.img otherwise you will have a bootloop:
If you receive a positive answer we can go to next step
- Install patched Boot Image:
naturally, replace the X's with whatever string of characters Magisk supplied
- Assuming everything went good you can reboot your phone:
Done now your phone should be now rooted.
Enjoy.
Have fun
Click to expand...
Click to collapse
Hi, does the VBmeta work for all models? I am trying to root my Ulefone Power Armor 13.

It should, because iy's an empty file.

Harlock1978 said:
It should, because iy's an empty file.
Click to expand...
Click to collapse
Just tried it and it works great! Any idea anyone where I can get TWRP for Ulefone Armor 13? This phone has the recovery in the boot partition

Will this work with Android 11?

I forgot to update my progress. Works great on R (11) so far. Lots of modules seem to be updated too. I am considering using a custom ROM and finally disconnecting from GMS though I would like to retain the customised camera app for,the night vision. I will find a thread that might have a way to do this though if anyone here can help me or point me to the right place, would be much abliged. Also, any ROM recommendations, that are working best?