Database Users

Asus Zenfone 2 | Resources all in one thread

Hello XDA brothers
First of all i want to thank all the devs for their efforts. I have collected & compiled all the info from various sources, credit as usual goes to original devs
PS: Ok guys this thread will be updated real soon as i was able to get some extra space... Will post the latest developments in the reserved area..I want to thank this really helpful mod @mark manning as this thread will remain active because of him only
*******************************************************************************************************************
INDEX​*******************************************************************************************************************
Drivers | ADB installer
Recovery Related Stuff (Entering Recovery|Stock Recovery | Custom Recovery)
Rooting | Flashing | Applying OTA
Changing from CN to WW version
Unlocking Bootloader (UNOFFICIAL METHOD)
Xposed Framework Installer
Viper4Android Related Stuff
Adjusting DPI without root
NTFS support for OTG devices
******************************************************************************************************************
1) Drivers | ADB installer:
ASUS USB DRIVERS (FOR INSTALLING THESE DRIVER SEE THIS https://software.intel.com/en-us/articles/installation-instructions-for-intel-android-usb-driver)
15 sec ADB installed
________________________________
2) Recovery Related Stuff (Entering Recovery| Stock Recovery | Custom Recovery)
2.1) Entering Recovery mode
​
Steps:
Turn off you Zenfone 2
Hold Power button + Volume up
When the phone is vibrating release power button
You can select Normal boot or Recovery boot by pressing Volume up/down button.. To enter Recovery mode choose recovery boot.
Then you will see sleeping android robot. Press power button + Volume up and release the buttons.
You are now in Recovery mode
NOTE: After rooting many users are not able to enter recovery..The dead android bot with error appears...To enter recovery follow these steps:
Method 1:​
Enter recovery as you normally do
When you see a dead android bot with an error press and hold power button, then (while holding power button) quickly press Vol up and release and then release power button..
NOTE: IF METHOD 1 FAILS try METHOD 2 it will definitely work
Method 2:​
Connect your device and open adb
In adb Type
Code:
fastboot erase cache
2.2) Stock Recovery
For STOCK recovery collection: http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
​
2.3) Custom Recovery
2.3.1) Tethered Recovery
​NOTE: YOU MAY STILL FACE SOME BUGS as this project is STILL IN DEVELOPMENT STAGE.. If you experience any bug please report to the OP at http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532 or at http://forum.xda-developers.com/devdb/project/?id=10167#bugReporter
credit goes to: TheSSJ , social-design-concepts , vampirefo
Steps:
Replace the recovery.zip in "CWM_Zenfone_2_IntelFB_RecoveryLauncher" from http://forum.xda-developers.com/devdb/project/dl/?id=13221
Start the procedure by using cai_dat_CWM.bat
Type ACCEPT (case sensitive!) and enter
Type T4 and enter
Set your timezone when booting the first time into the Recovery, maybe this fixes the backup and restore bug (needs to be done just once)
Unplug your USB cable from the device, too, before flashing, backing up and/or restoring
2.3.2) UN-Tethered Recovery
NOTE: YOU MAY STILL FACE SOME BUGS as this project is STILL IN DEVELOPMENT STAGE.. If you experience any bug please report to the OP at http://forum.xda-developers.com/zenfone2/development/alpha-tethered-twrp-asus-zenfone-2-t3123532 or at http://forum.xda-developers.com/devdb/project/?id=10167#bugReporter
​
Steps:
Method 1:
Root your device (See #3.1 in this thread)
Unlock your Bootloader (See this thread http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547)
Download twrp.img , unpack and put on sd-card
Open adb and type
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery
reboot recovery
Method 2:
Download twrp.img , unpack and put it in your adb/fastboot directory
Unlock your Bootloader (See this thread http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547)
Boot into bootloader
Open up fastboot on your PC and type:
Code:
fastboot flash recovery twrp.img
Reboot into Recovery
_____________________________​
3) Rooting | Flashing | Applying OTA
3.1) Rooting Zenfone 2​
NOTE:​If you root via METHOD 1 you can update SuperSu app as well as update binaries but PLEASE DON'T apply any OTA update as the phone WILL GET STUCK IN A BOOTLOOP...Manually flash the firmware via adb...
If you root via METHOD 2 you CAN UPDATE VIA OTA/NO BOOTLOOPS BUT YOU HAVE TO UNROOT FIRST BEFORE APPLYING OTA
If you root via METHOD 3 you CAN UPDATE VIA OTA/NO BOOTLOOPS AND UN-ROOTING BEFORE APPLYING ANY OTA IS NOT NECESSARY.
Method 1 (PRE-ROOTED SYSTEM.IMG) : ​
Credit goes to: shakalaca , keepfishes
First things first: (get this straight, don't download the wrong firmware and flash the wrong thing)
ZE550ML = Z008
ZE551ML = Z00A
Files Needed:
Drivers for Asus Zenfone 2 installed on PC
ADB installed on your PC (https://drive.google.com/file/d/0B0MKgCbUM0itVVFWRC02Q0VBQnc/view?usp=sharing)
Flash Tools (http://forum.xda-developers.com/attachment.php?attachmentid=3301263&d=1431011927)
Pre-rooted system.img and recovery (https://mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw) (Download the correct firmware according to your phone)
WinRar
Steps:
Download the pre-rooted system.img folder (Download the correct firmware according to your phone ZE550ML = Z008 , ZE551ML = Z00A )
Download and run WinRAR . Click on the '.zip' part of the system.img file. You will see that WinRAR puts all the parts together and offers you an option to extract the one big system.img. Go ahead and extract it to the folder the other parts of the ROM are in.
Unzip the FlashTools.zip and copy the following 4 downloaded files and paste it into extracted flashtools folder:
boot.img (~ 11MB)
droidboot.img (~ 13MB)
recovery.img (~ 11MB)
system.img (~ 2GB)
Disconnect your phone from PC/Laptop.. Power it off. Once it is off, hold down the volume up button and hold on to the power button until the phone vibrates. After the vibration stops, release the power button and continue pressing the volume up button until the green Android robot appears. You should see a blue line below saying "Waiting Fastboot command"
Now connect your phone via USB to your computer.
At the flashtools folder press Shift + Right Click.. Then select "Open command here"...
Copy and paste the following commands in the command prompt window (line by line) and press enter after each line. WAIT for the process to complete before copying and pasting the next line:
Code:
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
The last step will take quite a while before it returns to the blinking cursor. Once it does, it's done and you can plug out the USB and press the power button, reboot your phone and when it starts up, your phone is ROOTED! You should see a # sign in the status bar
Method 2 (ROOTING VIA TEMPORARY CWM): ​
Credit goes to: @29y6145 , social-design-concepts , Chinaphonearena
NOTE: This is a TEMPORARY CWM with the primary purpose of INJECTING SuperSU onto your Asus Zenfone 2. It doesn't permanently replace recovery and YOU CAN UPDATE VIA OTA USING THIS METHOD BUT PLEASE UNROOT FIRST BEFORE APPLYING ANY OTA...
Steps:
Download the Asus Zenfone temporary CWM package
Unzip the package
Copy SuperSU.zip to the base of your SD card
Enable USB debugging
With your phone on, attach it to PC via USB
Run 'cai_dat_CWM.bat' from the CWM package
In the black command window that opens, type ACCEPT
Type T4
Phone will reboot into fastboot and you'll see commands being issued from the PC cmd window copying the temporary recovery
You may see some funked up images on your display for a bit. Remove the USB cable and within 30 seconds should then see it booted into CWM
Select install update
Navigate to SuperSU.zip and install
Method 3 (1 CLICK ROOT TOOL): ​
credit goes to: shakalaca for this tool , saurabhrck for informing me about the updated tool
Note: You need Asus Zenfone 2 drivers and ADB installed on ur PC
Steps for rooting if you are a WINDOWS user:​
Download the 1 Click Root Tool for Zenfone 2 from https://mega.co.nz/#!R8k0zACY!xaiNnxyAijsUwJL3l9koo1Iyr-pIjQmwVkVE8A_lv8Y or from https://drive.google.com/file/d/0B936USMlQhtKbmZLZDE3N1JMazA/view?usp=sharing
Unzip and connect your phone to PC
Run CheckBeforeAction.bat .... You will get confirmation to proceed to next step
Now run Root_zenfone.bat
Your Device will be rooted automatically
Steps for rooting if you are a LINUX user:​
Download 1 Click root tool from MEGA https://mega.co.nz/#!R8k0zACY!xaiNnxyAijsUwJL3l9koo1Iyr-pIjQmwVkVE8A_lv8Y
or from Google Drive https://drive.google.com/file/d/0B936USMlQhtKbmZLZDE3N1JMazA/view?usp=sharing
Unzip and run root.sh
3.2) Flashing Zenfone 2 via ADB
Tools Required:
Asus USB Drivers
ADB installed on your PC/Laptop
Asus Zenfone 2 Firmware from the Official ASUS support website
Method:
Turn off your Zenfone 2
Go to recovery mode
Select apply update from ADB
Connect your zenfone 2 with USB cable to your PC/laptop
Open command prompt in Windows (in the same folder where ADB is located)
Check connection by typing adb devices in the command prompt.. If connection successful there will be a list of Zenfone 2 device.
Type
Code:
adb sideload file.zip (where file.zip is the file name of the Asus firmware)
Wait until the process is complete
3.3) Applying OTA​
credit goes to: ansebovi
For applying OTA please see this thread:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
_____________________________
4) Changing from CN to WW version
Credit goes to: vivix
Please follow these steps to change your firmware from CN version to WW version:
NOTE: PLEASE DOWNLOAD THE CORRECT RECOVERY IMAGE...
ZE550ML = Z008
ZE551ML = Z00A
Download the latest recovery image (For Z00A=2.19.40.22 , For Z008= 2.19.40.13) from http://www.mediafire.com/folder/setyy42t2cymy#dy87k1a0f8m81
Boot to fastboot mode (Power + Vol Up)
Using ADB command prompt flash files by using fastboot commands :
Code:
[/B][/FONT][CODE] [FONT=Century Gothic][B]fastboot flash recovery recovery.img
[/B][/FONT] [FONT=Century Gothic][B] fastboot flash boot boot.img
[/B][/FONT] [FONT=Century Gothic][B] fastboot flash fastboot droidboot.img
[/B][/FONT]
[*]Reboot phone
[*] Download the latest OTA... For Z00A= 2.19.40.22 click here ......... For Z008=2.19.40.13 click here
[*]FOR Z00A users: Rename OTA file from UL-Z00A-WW-2.19.40.22-user.zip to UL-Z00A-CN-2.19.40.22-user.zip to get notification about update available.
[*]FOR Z008 users: Rename OTA file from UL-Z008-WW-2.19.40.22-user.zip to UL-Z008-CN-2.19.40.22-user.zip to get notification about update available.
[*] Update via notification about new update available
[*] Wait till update will finish (approx 10 min)
​
_____________________________
5) Unlocking Bootloader (UNOFFICIAL METHOD)
Credits goes to: ravian29, shakalaca
NOTE: Please note that this method is not recommended by Asus and is the un-official method of unlocking bootloader...Please proceed at your own risk..
For unlocking your boot-loader please visit this thread: http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547
____________________________
​
6) Xposed Framework Installer
​
To install Xposed Framework on Zenfone 2 follow these steps:
Download Xposed Installer from https://drive.google.com/file/d/0B7ujzTEVERI_T3I4bUtrWUJlRzQ/view?usp=sharing
Connect your zenfone 2 with USB (USB debugging enabled)
Extract the downloaded folder and launch InstallXposedFramework.bat (phone will reboot)
Now launch InstallXposedInstaller.bat to install Xposed apk on your phone. Enjoy Xposed on your zenfone 2
_____________________________
7) Viper4Android Related Stuff
​NOTE: NEED ROOT FOR THIS, BUSYBOX INSTALLED AND SE-LINUX MODE SET TO PERMISSIVE
7.1) Installing Viper4Android on Zenfone 2​
Make sure you have rooted, installed busy box and set the SE-Linux to permissive on your phone
Download the Viper4Android zip file from http://www.mediafire.com/?cnqqdme51qy9ft4
Extract the zip file and copy "ViPER4Android_FX_A4.x.apk" on your phone
Install the apk and open it... You will be asked to install the drivers..Click "Yes" and reboot your phone
Enable Master switch for Viper4android on Headphones/Speaker/Bluetooth and tweak.
7.2) Enabling V4A on MXPlayer / PowerAmp / Youtube:​
credit goes to: KaiStone
To make V4A work on these apps just push this audio_policy file in " /system/etc/"
Alternatively you can also edit audio_policy file manually by searching and editing "/system/etc/audio_policy.conf" file
NOTE: Please double check before removing any code as removing codes other than these will cause the loss of sound
Find and Remove this code:
Code:
deep_buffer {
sampling_rates 48000
channel_masks AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_PCM_16_BIT
devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE|AUDIO_DEVICE_OUT_ALL_SCO
flags AUDIO_OUTPUT_FLAG_DEEP_BUFFER
}
Consider to Remove (Consider Only, NOT NECESSARY until you doubt that you are facing some difficulties)
Code:
[COLOR=Red][COLOR=Black]codec_offload {
outputs {
codec_offload {
sampling_rates 8000|11025|12000|16000|22050|24000|32000|44100|48000
channel_masks AUDIO_CHANNEL_OUT_MONO|AUDIO_CHANNEL_OUT_STEREO
formats AUDIO_FORMAT_MP3|AUDIO_FORMAT_AAC
devices AUDIO_DEVICE_OUT_EARPIECE|AUDIO_DEVICE_OUT_SPEAKER|AUDIO_DEVICE_OUT_WIRED_HEADSET|AUDIO_DEVICE_OUT_WIRED_HEADPHONE
flags AUDIO_OUTPUT_FLAG_COMPRESS_OFFLOAD|AUDIO_OUTPUT_FLAG_NON_BLOCKING
}
}
}
[/COLOR][/COLOR]
STOCK AUDIO_POLICY.CONF FILE IN-CASE YOU MESSED UP:
​
credits goes to: fuzzybuffalo
http://forum.xda-developers.com/attachment.php?attachmentid=3374586
7.3) Convolver Samples for Viper4android​ Here is the collection of Convolver Samples for Viper4android (around 390)..
http://forum.xda-developers.com/zenfone2/general/collection-convolver-samples-389-t3140299
​
______________________
8) Adjusting DPI without root
​
Credit goes to BurritoBashr
To adjust the DPI follow the steps below, THIS DOES NOT REQUIRE ROOT.
NOTE: I have used the DPI 250 here you can adjust the DPI according to your own taste. The default DPI is 480
1) Enable USB Debugging
2) Start ADB and check if you see your device by typing
Code:
adb devices
3) If you see your phone go ahead and type
Code:
adb shell wm density 250
4) Reboot your phone to apply the effects system wide.
_____________________________
9) NTFS support for OTG devices
Credit goes to sorg
NOTE: PLEASE BACKUP YOUR VOLD FILE BEFORE DOING ANYTHING.
Steps:
Click to download vold_with_NTFS
Unpack archive and replace /system/bin/vold
Set permissions 755 (rwxr-xr-x): chmod 755 /system/bin/vold
Reboot
STOCK VOLD FILE :​
credit goes to: GeneralPag for uploading the stock vold file
https://docs.google.com/uc?id=0B4lokICL3cTDaVVzRnBSOGdHcGM&export=download
​

reserved

reserved

reserved

Hi there,
In point 12, the links to the recovery images are dead....do you have an alternative location where they can be found?
Many thanks
*** Update ***
Sorry for the HUGE quote of the entire message I originally posted! I've now trimmed that out. And thanks again for the updated links.

vincexda said:
In point 12, the links to the recovery images are dead....do you have an alternative location where they can be found?
Many thanks
Click to expand...
Click to collapse
Link updated..Although you could also download the recovery images from point 8 Please check the link and press thanks if i helped

hi sorry im so noob..would like to know what does wiping cache partition do? do you have to do it every intall of root?tnx

Many thankK's for this, my CN ZF2 now running on WW! Great tutorial.

Can I root with pre-rooted image following the steps in this thread if I am already on the more recent firmware update version? And if you are rooted is it still possible to keep root and OTA if you don't upgrade SU and SU binaries?

upgrading chinese rom to ww rom - step 12.
could you explain how do i use adb? and where do i store the recovery images on my pc or phone?
is the CN version worthwhile after changing to ww rom? i got the 64gb for 337$, cancel the order or keep it?
thanks

kanagawaben said:
Can I root with pre-rooted image following the steps in this thread if I am already on the more recent firmware update version? And if you are rooted is it still possible to keep root and OTA if you don't upgrade SU and SU binaries?
Click to expand...
Click to collapse
For your second question, I know that one is correct. If you're on the most recent firmware update, then you'll need to flash the same pre-rooted firmware. Check out shacka's links to see if it's there, and if not then keep checking until he uploads it.
Sent from the Ace's MB865 using Tapatalk

Aceofzeroz said:
For your second question, I know that one is correct. If you're on the most recent firmware update, then you'll need to flash the same pre-rooted firmware. Check out shacka's links to see if it's there, and if not then keep checking until he uploads it.
Sent from the Ace's MB865 using Tapatalk
Click to expand...
Click to collapse
Thanks. Was actually able to get the earlier firmware version pre-rooted image flashed and working following the steps in this thread, although it didn't work properly first time of trying (kept getting some error message about android.media). Once I had deleted user data and reflashed the pre-rooted image it worked fine. However, when I tried to do OTA I got stuck in a bootloop despite not having updated su or binaries - I guess some legacy of having previously been on the latest firmware? Anyway, sorted it out and all working fine and fast now on rooted and debloated 2.14.30.11 so I'm happy to stick with that until a more major update comes along (Android 5.1 for example).

Error!
I followed the instructions on "3) Rooting Zenfone 2" to root my ZE551ML / Z00A, and rebooted the phone.
Now my phone is messed up:
- it wont take me to homescreen ("Unfortunately, System UI has stopped", "Unfortunately, the process android.process.media has stopped")
- i can get past lockscreen
- tried rerooting again to no success
- phone wont boot to recovery (error & dead android with red triangle)
Note that the phone isnt bricked, and Im not stuck in a bootloop.
What do I do? Please help..

Sounds similar to the problems I initially had. Try entering into fastboot mode then connect to your computer and do a fastboot -w command to wipe your cache and data. Then try to flash the images as per the root guide on this thread again.

>Note: You can adjust the DPI according to your own taste
What was the orig. DPI when i want back?

tasar said:
>Note: You can adjust the DPI according to your own taste
What was the orig. DPI when i want back?
Click to expand...
Click to collapse
I guess its around 300....try that and report back

Device info show me 480dpi and density unknown. I found no entry in build.prop

tasar said:
Device info show me 480dpi and density unknown. I found no entry in build.prop
Click to expand...
Click to collapse
Same here couldnt find any entry in build.prop.. But i checked via various apps it shows as u said 480dpi.. I have included the screenshot...

But was 250 (like the tut on opener) no to small? Don't trust to test ?

after doing #12, update CN version to WW version
is it possible to receive an OTA Update via wifi after i upgrade my CN version to WW version. 2.15.40.13 has been released and yet i cant receive that ota update. is it possible?

[ZE552KL/Z012DC] Canadian Thread - Unlock, Root, Update to Nougat

This thread will be for the Canadian version of ZE552KL, and will be updated with specific info relevant to Z012DC model found in Canada (Canada Computers, Staples, other retailers). It has WW SKU number.
It took me a while and some searching to figure all steps out. I also modified Asus N and M firmware to remove version checks. Without this step - i was stuck with error 7 in TWRP. The only difference between Z012D and Z012DC seems to be in Fastboot and ADB drivers, TWRP recovery, system images seem to work well so far.
Steps:
1. Download Fastboot and ADB Drivers. For me usb driver on ZE552KL Asus download page didn't work. Select "Only install driver", you do not need to update your drivers via DRP.
Fastboot driver (for Vendor VID_18D1&PID_D00D): http://drivers.drp.su/Telephone/Hua...03.00/Huawei-FORCED-Allx64-2.00.03.00-drp.exe
ADB Driver (for VID_18D1&PID_D002): http://drivers.drp.su/Telephone/Leshcat/WinAll/Leshcat-WinAll-drp.exe
2. Save the following files on your External SD Card:
Modified M image UL-ASUS_Z012D-WW-13.20.10.152-user.zip
Modified N image UL-ASUS_Z012D-WW-14.2015.1701.8-user.zip
SuperSU - latest version from here
no-verity-opt-encrypt-5-1.zip. Give thanks to @kaffeine1 , without him - we would all be stuck with black screens
3. Save ADB and Fastboot files on your computer, and extract; give thanks to @snowwolf725
4. Download newer recovery (TWRP 3.1.0) from here
5. Unlock bootloader via unofficial unlock method; give thanks to @snowwolf725
6. Get into fastboot by turning off the phone, and pressing volume up + power. Install recovery that you downloaded in step #4:
Code:
fastboot flash recovery twrp-3.1.0-0-Z012D.img
7. Follow the steps this guide by @kaffeine1 . Skip the steps of downloading Nougat and Marshmallow firmware from Asus site, as you have already downloaded and saved both firmwares in Step #2 . Also skip the last step - do not reboot into Nougat, but go back to fastboot mode.
8. Root Nougat - follow steps under #2 here:
https://forum.xda-developers.com/zenfone-3/how-to/twrp-recovery-3-0-2-root-zenfone-3-t3569926
How to update to the latest version of OS:
1. Go to Asus Site, download latest WW image UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
2. Extract UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip\META-INF\com\google\android\updater_script , edit, remove first two lines, and put back into the zip file (e.g. using 7zip)
3. Extract from above zip file boot.img , and flash it via: fastboot flash boot boot.img
4. Flash recovery: fastboot flash recovery twrp-3.1.0-0-Z012D.img
5. Reboot into recovery, and flash:
- Firmware that you modified in #2
- no-verity-opt-encrypt-5.1.zip
- Latest SuperSU
- Rooted.zip (from step #8 above)
6. Reboot mobile, and enjoy new version!
Phone info as purchased:
Model Number: ASUS_Z012DC
Android version: 6.0.1
Baseband version: M3.10.42-Libra_080001
Build number: MMB29P.WW_Phone-13.20.10.152-20161222
Manufacture date (on the box): January 2017
Latest version - UL-ASUS_Z012D-WW-14.2020.1703.28-user.zip
Model Number: ASUS_Z012DC
Android version: 7.0
Baseband version: M3.10.47-Libra_080001
Build number: NRD90M.WW_Phone-14.2020.1703.28-20170410
Special thanks to:
- @jcadduono for TWRP recovery
- @snowwolf725 for guide unlock bootloader
- @kaffeine1 for guide how to upgrade to N from M

Reserved for future use

can i follow this step for ZE520KL ?

I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks

lastremnant said:
can i follow this step for ZE520KL ?
Click to expand...
Click to collapse
no, I do not think so. these are different phones.

DilipRB said:
I got my self a canadian vertion ZE552KL, but i can´t seem to fully unlock the boot loader, it goes onto fastboot, but it does not allow me to flash anything it gives a permision denied .
when i tried to flash fw from sdcard gives a error: the the sku is "WW_" and mine is ""
have you came across this problem.
how can it be solved?
thanks
Click to expand...
Click to collapse
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.

anterus said:
no, I do not think so. these are different phones.
Click to expand...
Click to collapse
nevermind sir, it worked for me

Strange things do happen!!!
anterus said:
try first flashing 6.0.1 firmware from asus site and then modified 7.0 firmware. if the error is when flashing 6.0 fw - try modified 6.0. and do paste specific rrror.
Click to expand...
Click to collapse
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????

DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update

lastremnant said:
backup those zips, open with winrar or another app. open meta-inf/android/google/updater-script with notepad++ try deleting from ifelse until ) );
save and let winrar save new update
Click to expand...
Click to collapse
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks

DilipRB said:
Tryed that, and got footer error...
seems that to modifying the script file and then recompresing will change the compretion check algorithem. giving a footer error.
i should try pakaging the apk again...
there was a program to do so but i cant recall which...
thks
Click to expand...
Click to collapse
i found it ...
apktool from :
https://forum.xda-developers.com/showthread.php?t=1989533
Sorry this was for apks... but i guess same principle aplies... when i can i shall try and post the outcome

DilipRB said:
i was trying this because i wanted to upgrade fw to 7 and trying to unlock bootloader to flash twrp for backups...
I tried original Asus UL-ASUS_Z012D-WW-13.20.10.131-user and gave strange error after check... this fw is for "WW_Phone" and this phone is ""
but after reestart i got OTA updates... now my ZE552KL-Z012DC is in 7.0....
i can live with that, only problem for me is adb backups, i prefer twrp.
thanks
P.D. what pusles me is why getprop("ro.product.name") returns empty sting????
Click to expand...
Click to collapse
I noticed that in some cases TWRP doesn't "stick", and gets overridden by default bootloader. Specific check is essentially useless - just to prevent flash of improper image. Just remove the check in the new FW, or use modified FW that has the check removed. I think in your case you can just re-flash TWRP since your bootloader is unlocked?

I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens

DilipRB said:
I tryed several TWRP 3.02 and 3.10 if a boot imge ... if entered bootloader with volum key + power it says all ok but booting never happens... if i enter bootloader trough adb it stucks until i disconnect and reconnect usb cable. when trying to flash. fast boot returns error not have permision and side load error secttion 7 on UL modified or else footer w
error after passing check. i shall try modiffying UL 13.20.10 and see what happens
Click to expand...
Click to collapse
flash modified images through twrp - with links in OP

Well my wife liked the phone so much, that she "kindly requested" me to gift it to her... now she is the proud owner of a canadian vertion of ZE552KL and i got myself a ZS570KL
thanks a lot for all your help.
P.D. : i think she was not happy with the time i was spending with the device.

I know this is going to sound super dumb, but the unofficial bootloader unlock still triggers the bootup message and voids the warranty, right?

This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...

DilipRB said:
This might be even dumber... But my guess is that the official app to unlock boot loader, does more than unlock,
My guess is that it also register with asus mobile, the fact that for your device has been unlocked...
Click to expand...
Click to collapse
That's what some manufacturers do, like Motorola and HTC. But from back when I unlocked the BL on my Zenfone 2 Laser, I remember that all it did (as far as I could tell) was unlock the bootloader and set a flag in the bootloader that made it say it was unlocked that couldn't be reversed. No need for fancy registration systems when you can just boot up the phone and take a look.

What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?

Jarrick said:
What was modified in your N-image firmware file? There is now a newer version that I'd like to install. Can you provide an updated modified file for version WW-14.2020.1703.28 or give the steps needed to modify it myself?
Click to expand...
Click to collapse
Updated OP with instructions regarding how to upgrade to the latest version of N - just tested steps myself. Should be applicable to all future versions of N posted on Asus site. Enjoy!

[GUIDE] Unlock/Flash/Root for the Pixel 2 (walleye)

Introduction
Hello everyone, this is a guide to assist you with customizing your Pixel 2! I will be going over installing fastboot and adb, unlocking your bootloader, how to flash the factory images for clean flashes and upgrades, and how to root. Please feel free to ask any questions if you need clarification. Enjoy!
This information has been distilled from Google's official factory image site and the Magisk thread.
Installing fastboot and adb
Thankfully, Google has provided just adb, fastboot, and systrace as a simple zip file, making this process super easy. You MUST be on at LEAST 26.0.2 for the commands in this guide to work. When in doubt, grab the latest copy and install them using the following instructions.
SDK Platform-Tools for Windows
SDK Platform-Tools for Mac
SDK Platform-Tools for Linux
Windows:
Unzip the folder somewhere on your hard drive.
Go to the folder containing the adb and fastboot files and type "cmd" in the path bar at the top.
A command prompt should open with the current folder showing on the prompt.
Type the following commands:
Code:
adb --version
fastboot --version
You should see some information appear. If that is the case, you were successful!
Mac/Linux:
Unzip the folder somewhere on your hard drive.
Navigate to that folder with your terminal.
Run the following commands:
Code:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Type the following commands:
Code:
adb --version
fastboot --version
You should see the version information, along with telling you they are installed to /usr/local/bin. If so, you were successful!
Unlocking the bootloader
WARNING: This WILL wipe your entire phone. Please make copies or backups of any important data. This can also go wrong rendering your device inoperable. Proceed with caution.
On your phone, open Settings, navigate to "System" then "About phone", and tap on the build number 7 times.
Go one menu up, click on "Developer options", and turn on USB debugging and OEM unlocking.
In your terminal, type the following command:
Code:
adb reboot bootloader
Run the following command:
Code:
fastboot flashing unlock
Follow the prompts on your device then reboot!
Flashing factory images
NOTE #1: You CANNOT downgrade factory images. Google has prevented users from doing so to keep them safe from vulernabilities that were patched. You should only upgrade or reinstall the current image.
NOTE #2: If you have mounted /system as rw at any point (like in TWRP), you must upgrade using the factory image method. OTAs will fail because they cannot verify the integrity of the disk since its verity data has been changed.
NOTE #3: Flashing the factory images requires an unlocked bootloader. Flashing the OTA zips does not (but if anything goes wrong, you may not be able to recover without an RMA).
Updating to a new release (factory image):
Download the latest factory image from Google's website.
Reboot into the bootloader:
Code:
adb reboot bootloader
Unzip the factory image.
Inside you will see a bootloader image, a radio image, an image zip file, and a couple of flash scripts.
If you are on Windows, open the "flash-all.bat" file in a text editor. If you are on Mac or Linux, open the "flash-all.sh" instead.
Remove the "-w" flag before the fastboot command towards the end of the file. This will prevent fastboot from formatting your device.
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
Windows:
Code:
flash-all
Mac/Linux:
Code:
./flash-all.sh
Reboot once it is finished!
Updating to a new release (OTA zip):
Download the latest OTA zip from Google's website
Reboot into recovery:
Code:
adb reboot recovery
Hold down the power button and push volume up
Select "Apply update from ADB"
Run the following command from the folder containing the OTA zip:
Code:
adb sideload <zip_name>.zip
Reboot once it is finished!
Clean flashing a factory image (wipe everything):
Download the latest factory image from Google's website
Reboot into the bootloader:
Code:
adb reboot bootloader
Unzip the factory image.
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
Windows:
Code:
flash-all
Mac/Linux:
Code:
./flash-all.sh
Reboot once it is finished!
Rooting with Magisk
NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Installing TWRP
NOTE #5: If you just want to temporarily boot TWRP to flash Magisk and your custom kernel, you can just skip flashing the installer zip in this process.
NOTE #6: TWRP can be unstable at times given the way that security has been set up on this device (lack of decryption, failing to boot, etc).
Download both the TWRP image and zip installer from the official site.
Temporarily boot the TWRP image.
Code:
fastboot boot <path_to_twrp_image>
Flash the TWRP installer zip.
Reinstall Magisk and your custom kernel if you had them.
Reboot and profit!
Common issues
Outdated fastboot/adb: This device requires the latest fastboot and adb binaries to work properly. A lot of common quick adb/fastboot installation guides link to installers that are old. Please manually install the latest using the information at the beginning of the thread!
Using a USB-3.0 or USB-C port: Some newer USB ports do not work with fastboot. Issues manifest as weird errors during a flash. Use a different USB cable/port.
Closing statements
If there are any procedures you would like to see added (like flashing a custom kernel or booting TWRP), I am happy to add them if requested. Also, when requesting help, please be as specific as possible where you get confused. I want this guide to be clear as possible.

Reserved

Reserved

Stuck on this step
Run the flash all script! Open a command prompt, navigate to the folder with the script, and run one of the following commands:
How do I navigate in command prompt? When I typed flash-all, it said it is not a internal command etc. When I dragged and dropped flash-all into the command prompt, it said C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES>"C:\Users\****** Jim\Downloads\walleye-opd1.170816.025-factory-4752baae\walleye-opd1.170816.025\flash-all.bat"
error: cannot load 'bootloader-walleye-mw8998-002.0059.00.img'
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.004s
error: cannot load 'radio-walleye-g8998-00122-1708311414.img'
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.015s
W/ ( 6448): Unable to open 'image-walleye-opd1.170816.025.zip': No such file or directory
error: failed to open zip file 'image-walleye-opd1.170816.025.zip': I/O Error
Press any key to exit...

You are calling the flash-all.bat out of a differende directory (C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES) therefore it can't find the system image files since they are located under C:\U sers\****** Jim\Downloads\walleye-opd1.170816.025-factory-4752baae\walleye-opd1.170816.025. Make sure you extract your image to that directory, open up a command promt and navigate to it with "cd C:\Users\W Balls\Downloads\SAMPWND_SYSTEMROOT_ADB_FILES" and call the flash-all.bat from there.
Check out this for basic command line stuff https://www.digitalcitizen.life/command-prompt-how-use-basic-commands
---------- Post added at 10:58 AM ---------- Previous post was at 10:56 AM ----------
I tried this and it seems the magisk manager isn't able to download magisk on its own at least on my device:
Code:
DownloadManager: [356] Stop requested with status HTTP_DATA_ERROR: Unable to resolve host "forum.xda-developers.com": No address associated with hostname
DownloadManager: [356] Finished with status WAITING_TO_RETRY
EDIT: Seems like DNS66 was blocking the download patching was scucessfull now.
This is weird, can't I make 2 posts in a row??

Anybody figure out a solution for flashing when on MacOs High Sierra? Platform tools 26.0 1 was a fix for high Sierra, yet 26.0.2 seemed to have lost that commit, so fastboot doesn't work at all. Wondering if it's safe to use 26.0.1 on the pixel 2

nathanchance said:
Flashing factory images
Click to expand...
Click to collapse
First, thanks for putting this together. I've rooted using your method.
Regarding OTA updates: I've read that if we've rooted, we will need to un-root before we can receive an OTA update. Is this always true, or only if we've installed a custom recovery like TWRP? It would be really handy to have a guide on how to un-root, update, then re-root.
Related - let's say that for whatever reason, we have to flash an OTA update manually, rather than actually getting it OTA. Do we lose root by doing so?
Thanks!

JayBlack_686 said:
First, thanks for putting this together. I've rooted using your method.
Regarding OTA updates: I've read that if we've rooted, we will need to un-root before we can receive an OTA update. Is this always true, or only if we've installed a custom recovery like TWRP? It would be really handy to have a guide on how to un-root, update, then re-root.
Related - let's say that for whatever reason, we have to flash an OTA update manually, rather than actually getting it OTA. Do we lose root by doing so?
Thanks!
Click to expand...
Click to collapse
Magisk's OTA section should clear up some of your doubts: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

nathanchance said:
Magisk's OTA section should clear up some of your doubts: https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Looks really straightforward, thank you! Might be cool to point to it in the OP. I bet I'm not the only one who was only vaguely aware of the impact that rooting has on how we get OTAs. Then again, maybe everyone else wants to run custom ROMs.

JayBlack_686 said:
Looks really straightforward, thank you! Might be cool to point to it in the OP. I bet I'm not the only one who was only vaguely aware of the impact that rooting has on how we get OTAs. Then again, maybe everyone else wants to run custom ROMs.
Click to expand...
Click to collapse
Good point, I'll add it here in a bit
Sent from my Pixel 2 XL using XDA Labs

OTA vs factory image
Howdy,
really appreciate @nathanchance for putting this together. Would you mind adding a few lines about the differences between OTA and factory images. As a layman i haven't got the foggiest idea which route to go and would appreciate some wisdom. Thanks!

Thank you so much for this guide but can anybody please explain how you can tell which image to patch ?
I am unable to get this to work magisk is showing this message: stock kernel cannot be patched please use a custom kernel
i downloaded: walleye-opd1.170816.010-factory-63083164.zip
unsure as to whether this is correct for my phone as they are quite a few and its unclear how to tell
i have a pixel 2 from the UK that was factory unlocked and i unlocked the boot loader
what am i doing wrong please help

tango650 said:
Howdy,
really appreciate @nathanchance for putting this together. Would you mind adding a few lines about the differences between OTA and factory images. As a layman i haven't got the foggiest idea which route to go and would appreciate some wisdom. Thanks!
Click to expand...
Click to collapse
The primary difference is that the OTA can be flashed on an unlocked bootloader and is designed not to wipe your phone.
UpGrad3 said:
Thank you so much for this guide but can anybody please explain how you can tell which image to patch ?
I am unable to get this to work magisk is showing this message: stock kernel cannot be patched please use a custom kernel
i downloaded: walleye-opd1.170816.010-factory-63083164.zip
unsure as to whether this is correct for my phone as they are quite a few and its unclear how to tell
i have a pixel 2 from the UK that was factory unlocked and i unlocked the boot loader
what am i doing wrong please help
Click to expand...
Click to collapse
Are you supplying the boot image to Magisk? Show me a screenshot of what Magisk says when it tries to patch.

Thanks @nathanchance for this. I'm not a technical person, but can follow directions. This is the 4th phone that I've rooted following directions of some very smart and talented people here on XDA. I don't do this kind of thing everyday, and am not up on programming or coding or whatever you guys call it now days.
All I ended up doing is taking the OTA from Google to the .025. Then followed the Magisk rooting instructions to get root. I had Unlocked it the first day I turned the phone on, I haven't put my SIM in yet, but will play around with it a little more, and finish setting it up,
Again, thanks for the GUIDE to this Pixel 2 phone.

nathanchance said:
The primary difference is that the OTA can be flashed on an unlocked bootloader and is designed not to wipe your phone.
Are you supplying the boot image to Magisk? Show me a screenshot of what Magisk says when it tries to patch.
Click to expand...
Click to collapse
That is what i get. I have even flashed the whole factory image to the phone and still get this

@UpGrad3 you need to extract the boot.img out of your zip (walleye-opd1.170816.010-factory-63083164.zip) file and process this one, I'll guess you tried with the whole zip?? Also you can "attach" pictures to the post and not include the full res with the image tags...

@drmason I did extract the img from the zip. I followed the instructions exactly which is why im so confused as to what is going on ? Ok sorry i will do in future.
Amended post

UpGrad3 said:
@drmason I did extract the img from the zip. I followed the instructions exactly which is why im so confused as to what is going on ? Ok sorry i will do in future.
Amended post
Click to expand...
Click to collapse
You got the boot.img from the zip file that was inside the zip file?
from https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Step by step
1. Download and extract factory image. Mine was taimen-opd1.170816.010-factory-c796ddb4.zip
***2. Once extracted go into the folder and extract image-taimen-opd1.170816.010.zip.
There you will find the boot.img.
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
nathanchance said:
Good point, I'll add it here in a bit
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
@nathanchance, one more suggestion for the OP: at one point I was looking at using the stock boot img and couldn't figure out how to get it. Later, I found the below post, where the first two steps are essentially "open the zip inside the zip for the boot.img" to extract the stock boot image. Maybe it's really obvious, but I didn't get it.
https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90

@UpGrad3 you are using the latest Magisk Manager 5.4.1 for this?

JayBlack_686 said:
You got the boot.img from the zip file that was inside the zip file?
from https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Step by step
1. Download and extract factory image. Mine was taimen-opd1.170816.010-factory-c796ddb4.zip
***2. Once extracted go into the folder and extract image-taimen-opd1.170816.010.zip.
There you will find the boot.img.
---------- Post added at 08:36 AM ---------- Previous post was at 08:27 AM ----------
this is where i was going wrong i was using a file that had bootloader in the name rather than going into the second zip and finding boot
@nathanchance, one more suggestion for the OP: at one point I was looking at using the stock boot img and couldn't figure out how to get it. Later, I found the below post, where the first two steps are essentially "open the zip inside the zip for the boot.img" to extract the stock boot image. Maybe it's really obvious, but I didn't get it.
https://forum.xda-developers.com/showpost.php?p=74429474&postcount=90
Click to expand...
Click to collapse
drmason said:
@UpGrad3 you are using the latest Magisk Manager 5.4.1 for this?
Click to expand...
Click to collapse
yes i was
although im now stuck on the bootscreen with the G any suggestions ?
Fixed.
incase it happens to anyone else. i restored the factory image again then started the root procedure. im now rooted and fully working

update HWOTA to EMUI9 ?

Hi, is it possible to update HWOTA (Mate 9 rooted) to EMUI9 (MHA-L29C636-9.0.1.159 FullOTA-MF) with patch HWOTA8_2017110501 for Android 8 Oreo?

İ don't now
İ need answer to to trying this method
But my phone C185
And the update file in Firmware finder 2 file not 3

use Hrupdater

CouCouFR34 said:
Hi, is it possible to update HWOTA (Mate 9 rooted) to EMUI9 (MHA-L29C636-9.0.1.159 FullOTA-MF) with patch HWOTA8_2017110501 for Android 8 Oreo?
Click to expand...
Click to collapse
You would have to modify hwota script as Pie only uses 2 zips.
aureliomilitao said:
use Hrupdater
Click to expand...
Click to collapse
that's not recommended as Pie uses System as root.

ante0 said:
You would have to modify hwota script as Pie only uses 2 zips.
that's not recommended as Pie uses System as root.
Click to expand...
Click to collapse
how modify hwota script as Pie only uses 2 zips?>
same steps with 2 file works??

please my account HCU is block
need help for fix my IMEI with acount HCU via TeamViewer

Hi AnteO, I have the same question as Kilis ; how to modify the HWOTA script to use only the 2 zips ?

CouCouFR34 said:
Hi AnteO, I have the same question as Kilis ; how to modify the HWOTA script to use only the 2 zips ?
Click to expand...
Click to collapse
Remove the following line from update-binary in hwota8_update.zip and repack.
echo --update_package=/sdcard/HWOTA8/update_data_public.zip >> /cache/recovery/command
Or check out this post: https://forum.xda-developers.com/showpost.php?p=78962795&postcount=171

I want to patch new updates of emui 9 with latest google security patches so which no check recovery i use on emui 9.

OK it works very well and EMUI9 is ​​definitely better than version 8; on the other hand how to reinstall TWRP?

I found this post from anteO
https://forum.xda-developers.com/mate-9/help/twrp-emui-9-android-pie-decryption-t3894735
it seems that TWRP is not easily installable ; would there be a solution, especially to install MAGISK ?

CouCouFR34 said:
I found this post from anteO
https://forum.xda-developers.com/mate-9/help/twrp-emui-9-android-pie-decryption-t3894735
it seems that TWRP is not easily installable ; would there be a solution, especially to install MAGISK ?
Click to expand...
Click to collapse
You don't need TWRP to install Magisk; for that matter, they can't be installed simultaneously on EMUI 9 together anyway.
The EMUI 9 method for Magisk is to patch recovery_ramdisk.img extracted from update.app, flash the patched image, and boot to recovery from then on. (Huawei made it impossible to load a custom ramdisk on Pie otherwise.)

Thank you irony_delerium for info's, but is there not a tutorial explaining the steps of modification ?

CouCouFR34 said:
Thank you irony_delerium for info's, but is there not a tutorial explaining the steps of modification ?
Click to expand...
Click to collapse
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
2) Extract UPDATE.APP from the main update.zip file (the big one).
3) Using Huawei Firmware Extractor on your desktop (search on XDA for it), load UPDATE.APP and extract the recovery ramdisk image. It's going to be "RECOVERY_RAMDIS" in that app as I recall.
4) Put the image into your phone's internal storage (MTP works, though I've never used it, I usually use adb: adb push RECOVERY_RAMDIS.img /sdcard)
5) Install Magisk Manager on your phone. You want the current release (18.1) at the very minimum. Canary builds also work
6) Select the Install button in the Magisk interface. Select "Patch boot image". In the file browser that comes up, select the image you just transferred in #4.
7) When Magisk finishes, pull the image back to your PC (adb: adb pull /sdcard/Download/patched_boot.img)
8) Reboot to the bootloader and flash (fastboot flash recovery_ramdisk patched_boot.img)
9) Reboot to recovery (fastboot reboot, pull the USB cable and hold volume up).

Thank you irony_delerium ; very clear tutorial ; on the other hand, in UPDATE.APP there are 2 RECOVERY files : RECOVERY_RAMDIS.img and ERECOVERY_RAMDI.img which do the same weight; patching MAGISK with RECOVERY_RAMDIS.img I arrived at a system error and a dialogue asking me to either erase the data, or a factory restore; on the other hand with ERECOVERY_RAMDI.img it was installed alone? does it seem normal to you?

irony_delerium said:
1) Make sure you've got the stock firmware zip files. (I'm assuming you do.)
2) Extract UPDATE.APP from the main update.zip file (the big one).
3) Using Huawei Firmware Extractor on your desktop (search on XDA for it), load UPDATE.APP and extract the recovery ramdisk image. It's going to be "RECOVERY_RAMDIS" in that app as I recall.
4) Put the image into your phone's internal storage (MTP works, though I've never used it, I usually use adb: adb push RECOVERY_RAMDIS.img /sdcard)
5) Install Magisk Manager on your phone. You want the current release (18.1) at the very minimum. Canary builds also work
6) Select the Install button in the Magisk interface. Select "Patch boot image". In the file browser that comes up, select the image you just transferred in #4.
7) When Magisk finishes, pull the image back to your PC (adb: adb pull /sdcard/Download/patched_boot.img)
8) Reboot to the bootloader and flash (fastboot flash recovery_ramdisk patched_boot.img)
9) Reboot to recovery (fastboot reboot, pull the USB cable and hold volume up).
Click to expand...
Click to collapse
Hello
If you wouldn't mind confirming a few things from your post, as I'm trying to do this.
Is the sole purpose of extracting the big file to extract the recovery_ramdis ? You don't mention if anything is done with the big file.
The ADB commands didn't work for me, (error: push requires an argument).
But, I sent the recovery_ramdis via magisk manager, and it worked, then advised me that it put the image in /storage/emulated/0/Download/patched_boot.img but I can't find that location.
OK, edit ... I found the file and flashed it, rebooted into recovery and I get the message software installation failed.
I've had a whole lot of failures, phone won't root despite magisk giving no errors, dload won't work, superSU won't work.
Update .... root decided to work out the blue so I tried EMUI flasher and it looked like it was going to work ... but failed the update at about 10%.
Update - Bricked.

HOW TO: Android 10 Stock with Root via Magisk

Full disclosure- many of these steps are just copy/pasted from the Magisk install instructions and other areas online, just thought I'd post a full set of instructions for our device. There might be easier steps or I might have added additional unnecessary steps, please let me know and I can update. I'm just posting what worked for me. I also don't like installing things from sketchy fileshare sites, so I provide the way to get everything from official sources.
This is to get root via Magisk on a stock Moto Z4 (I have the Retail model, don't know anything about Verizon or other models). You will need to have a knowledge of how to do some advanced tasks, such as using ADB/Fastboot, installing APKs from unknown sources, and installing drivers on your computer. Google is your friend (or DuckDuckGo in my opinion) I am not responsible for bricked phones, thermonuclear war, etc. This is just a helpful guide.
You might as well start on the latest OTA since during the unlock process you'll have no choice but to erase all your data, make sure you're fully updated and backup your data.
HOW TO ROOT FROM STOCK:
First, you must unlock your bootloader. WARNING: THE UNLOCK PROCESS WILL ERASE ALL OF YOUR DATA!
Follow the instructions on the Motorola website to check if your bootloader can be unlocked and retrieve the ID codes
One step Motorola doesn't mention is that you must enable OEM unlocking from the Developer Options. If you don't know how to get to Developer Options, you'll need to google it. It's very easy, and I think it's a good "test" to figure out if you should even be trying to root your phone
Once you have your unlock code, unlock your bootloader according to the instructions here. EVERYTHING ON YOUR PHONE WILL BE DELETED AT THIS POINT!
Next, you must patch the stock boot image.
You will need to retrieve the boot image, please follow the instructions at the bottom of this post on how to download the full OTA archives.
Once you have the stock boot image, copy it to your phone's storage
You need to install Magisk Manager on your phone (it doesn't need to be rooted at this point- it's just needed to patch the boot image) Download the latest Magisk Manager from the official Magisk thread here
Tap "Advanced Settings" in Magisk Manager and check "Recovery Mode"
Press Install → Install → Select and Patch a File, and select your stock boot/recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Now, flash the modified boot image
Plug your phone in, make sure USB debugging is enabled, open a command line in the same folder that your patched image is in (or, you can put in the full path on step 3 rather than just the filename).
Easiest way to get to fastboot mode is the command (you can also use the volume key trick if you'd rather or if you're having trouble with ADB):
Code:
adb reboot bootloader
Then all you have to do is:
Code:
fastboot flash boot magisk_patched.img
To reboot:
Code:
fastboot reboot
You should be done now! You can check the status of root from Magisk Manager and refer to Magisk documentation for any help with that. You may also want to disable Automatic System Updates from Developer options to prevent issues when updates are released.
HOW TO DOWNLOAD STOCK OTA ZIP & RETRIEVE BOOT IMAGE:
First, you need to download LSMA, Moto/Lenovo's software for managing and recovering phones
Once the software is installed, open it and go to the "Flash" tab, hit "Switch to Upgrade", and connect your phone
When you connect, it will check for an update (Sometimes it will not have the latest update even if you are offered an update on your phone. You'll need to wait until it shows up here)
Download the update
LSMA will download a zip file to C:\ProgramData\LMSA\Download\RomFiles, and once completed it will automatically extract the ZIP. (If you want the full ZIP image for any reason, you must copy it to a different location before the extraction completes, LSMA deletes the zip once the extraction finishes. Just have the window open until the download completes, as soon as the ZIP file appears copy it to another folder, it will not interfere with extraction.)
Retrieve the boot.img from the download folder
HOW TO UPGRADE TO NEW OTA, PRESERVING ROOT & DATA:
Now you can try following the Magisk instructions since our device has an A/B partition layout, but I wasn't able to get it to work, usually the upgrade fails validating the current image so I have an alternate set of steps that did work for me. Backup your data just in case though.
First, you need to download LSMA, Moto/Lenovo's software for managing and recovering phones
Once the software is installed, open it and go to the "Flash" tab, hit "Switch to Upgrade", and connect your phone
When you connect, it will check for an update (Sometimes it will not have the latest update even if you are offered an update on your phone. You'll need to wait until it shows up here)
Download the update, but don't install it yet. The program will download a zip file to C:\ProgramData\LMSA\Download\RomFiles, and once completed it will automatically extract the ZIP.
Retrieve the boot.img from the download folder and copy it to your phone
Patch the boot.img in Magisk Manager per the steps above
Now proceed with installing the update in LSMA (It will say it's going to erase your data, but it does not).
Your phone will reboot to the bootloader and LSMA will flash the update
Once the update is finished and your phone reboots for the final time, close LSMA.
Reboot to the bootloader again:
Code:
adb reboot bootloader
Flash boot:
Code:
fastboot flash boot magisk_patched.img
Reboot:
Code:
fastboot reboot
Upon reboot, you're now updated, and root & data is preserved.

hey there i cant download the recovery.img for get mod
when triying to flash and download it said device incompatible
anyone have the moded recovery already patch that can share if can of course
I have Android 10 already

Need some help I conect my phone tomthe app for downloading the full ota file but gives me an error. The recognize the phone but I can't download the img file can some one share me the .img patched.
Can I use a .img that some in this forum did ?

I read Android has new fastbootd and I had to manually install ROM and root using fastbootd on One Hyper
Z4 doesn't need fastbootd, does it?

mingkee said:
I read Android has new fastbootd and I had to manually install ROM and root using fastbootd on One Hyper
Z4 doesn't need fastbootd, does it?
Click to expand...
Click to collapse
No, the Z4 does not use fastbootd.
Running this command with the device connected in fastboot mode will return yes if it uses fastbootd and no if it doesn't
Code:
fastboot getvar is-userspace
https://source.android.com/devices/bootloader/fastbootd

Do I have to download LSMA or can I use the boot.img from the Android 10 firmware I got from lolinet?

G.I. Jew said:
Do I have to download LSMA or can I use the boot.img from the Android 10 firmware I got from lolinet?
Click to expand...
Click to collapse
The firmware packages from lolinet are identical to the ones downloaded by LMSA

Sigh, not possible on verizon due to the locked bootloader

zander21510 said:
Full disclosure- many of these steps are just copy/pasted from the Magisk install instructions and other areas online, just thought I'd post a full set of instructions for our device. There might be easier steps or I might have added additional unnecessary steps, please let me know and I can update. I'm just posting what worked for me. I also don't like installing things from sketchy fileshare sites, so I provide the way to get everything from official sources.
This is to get root via Magisk on a stock Moto Z4 (I have the Retail model, don't know anything about Verizon or other models). You will need to have a knowledge of how to do some advanced tasks, such as using ADB/Fastboot, installing APKs from unknown sources, and installing drivers on your computer. Google is your friend (or DuckDuckGo in my opinion) I am not responsible for bricked phones, thermonuclear war, etc. This is just a helpful guide.
You might as well start on the latest OTA since during the unlock process you'll have no choice but to erase all your data, make sure you're fully updated and backup your data.
HOW TO ROOT FROM STOCK:
First, you must unlock your bootloader. WARNING: THE UNLOCK PROCESS WILL ERASE ALL OF YOUR DATA!
Follow the instructions on the Motorola website to check if your bootloader can be unlocked and retrieve the ID codes
One step Motorola doesn't mention is that you must enable OEM unlocking from the Developer Options. If you don't know how to get to Developer Options, you'll need to google it. It's very easy, and I think it's a good "test" to figure out if you should even be trying to root your phone
Once you have your unlock code, unlock your bootloader according to the instructions here. EVERYTHING ON YOUR PHONE WILL BE DELETED AT THIS POINT!
Next, you must patch the stock boot image.
You will need to retrieve the boot image, please follow the instructions at the bottom of this post on how to download the full OTA archives.
Once you have the stock boot image, copy it to your phone's storage
You need to install Magisk Manager on your phone (it doesn't need to be rooted at this point- it's just needed to patch the boot image) Download the latest Magisk Manager from the official Magisk thread here
Tap "Advanced Settings" in Magisk Manager and check "Recovery Mode"
Press Install → Install → Select and Patch a File, and select your stock boot/recovery image file
Magisk Manager will patch the image, and store it in [Internal Storage]/Download/magisk_patched.img
Copy the patched image from your device to your PC. If you can’t find it via MTP, you can pull the file with ADB:
adb pull /sdcard/Download/magisk_patched.img
Now, flash the modified boot image
Plug your phone in, make sure USB debugging is enabled, open a command line in the same folder that your patched image is in (or, you can put in the full path on step 3 rather than just the filename).
Easiest way to get to fastboot mode is the command (you can also use the volume key trick if you'd rather or if you're having trouble with ADB):
Code:
adb reboot bootloader
Then all you have to do is:
Code:
fastboot flash boot magisk_patched.img
To reboot:
Code:
fastboot reboot
You should be done now! You can check the status of root from Magisk Manager and refer to Magisk documentation for any help with that. You may also want to disable Automatic System Updates from Developer options to prevent issues when updates are released.
HOW TO DOWNLOAD STOCK OTA ZIP & RETRIEVE BOOT IMAGE:
First, you need to download LSMA, Moto/Lenovo's software for managing and recovering phones
Once the software is installed, open it and go to the "Flash" tab, hit "Switch to Upgrade", and connect your phone
When you connect, it will check for an update (Sometimes it will not have the latest update even if you are offered an update on your phone. You'll need to wait until it shows up here)
Download the update
LSMA will download a zip file to C:\ProgramData\LMSA\Download\RomFiles, and once completed it will automatically extract the ZIP. (If you want the full ZIP image for any reason, you must copy it to a different location before the extraction completes, LSMA deletes the zip once the extraction finishes. Just have the window open until the download completes, as soon as the ZIP file appears copy it to another folder, it will not interfere with extraction.)
Retrieve the boot.img from the download folder
HOW TO UPGRADE TO NEW OTA, PRESERVING ROOT & DATA:
Now you can try following the Magisk instructions since our device has an A/B partition layout, but I wasn't able to get it to work, usually the upgrade fails validating the current image so I have an alternate set of steps that did work for me. Backup your data just in case though.
First, you need to download LSMA, Moto/Lenovo's software for managing and recovering phones
Once the software is installed, open it and go to the "Flash" tab, hit "Switch to Upgrade", and connect your phone
When you connect, it will check for an update (Sometimes it will not have the latest update even if you are offered an update on your phone. You'll need to wait until it shows up here)
Download the update, but don't install it yet. The program will download a zip file to C:\ProgramData\LMSA\Download\RomFiles, and once completed it will automatically extract the ZIP.
Retrieve the boot.img from the download folder and copy it to your phone
Patch the boot.img in Magisk Manager per the steps above
Now proceed with installing the update in LSMA (It will say it's going to erase your data, but it does not).
Your phone will reboot to the bootloader and LSMA will flash the update
Once the update is finished and your phone reboots for the final time, close LSMA.
Reboot to the bootloader again:
Code:
adb reboot bootloader
Flash boot:
Code:
fastboot flash boot magisk_patched.img
Reboot:
Code:
fastboot reboot
Upon reboot, you're now updated, and root & data is preserved.
Click to expand...
Click to collapse
for those who try to install security patch...
I recommend you do the following in case you wish to keep your root and others in the phone.
as usual, back it up in case...
connect to the lenovo software (above) and download the security patch (you can do it thru the rescue step as the program will prompt "no new software" if you try to check "upgrade software".
once the security patch download is complete, keep a copy of the boot.img and load it on the phone to do usual magisk thing.
but be patient...
keep this new magisk edited boot elsewhere and reflash the original boot to your phone so that the error message in making the patch update disappears.
once you reverted to the original boot (it goes without saying the usual fastboot reboot), make the OTA security patch update.
you will find that the root is gone but the phone (everything).
now is the time to flash the magisk edited boot (the new boot from the update patch) to your phone and voilaaaaa!
your root is back + the security patch applied.

beefytr said:
for those who try to install security patch...
I recommend you do the following in case you wish to keep your root and others in the phone.
as usual, back it up in case...
connect to the lenovo software (above) and download the security patch (you can do it thru the rescue step as the program will prompt "no new software" if you try to check "upgrade software".
once the security patch download is complete, keep a copy of the boot.img and load it on the phone to do usual magisk thing.
but be patient...
keep this new magisk edited boot elsewhere and reflash the original boot to your phone so that the error message in making the patch update disappears.
once you reverted to the original boot (it goes without saying the usual fastboot reboot), make the OTA security patch update.
you will find that the root is gone but the phone (everything).
now is the time to flash the magisk edited boot (the new boot from the update patch) to your phone and voilaaaaa!
your root is back + the security patch applied.
Click to expand...
Click to collapse
Hey, I found that using root on the latest security patch makes the WiFi stop working. Like the switch won't even turn on, and it can't scan for new networks. I know that it's not a hardware problem, because I reverted to the March security update and WiFi works. Is anyone else having the no WiFi issue on the latest security patch while using root?

Fazwalrus said:
Hey, I found that using root on the latest security patch makes the WiFi stop working. Like the switch won't even turn on, and it can't scan for new networks. I know that it's not a hardware problem, because I reverted to the March security update and WiFi works. Is anyone else having the no WiFi issue on the latest security patch while using root?
Click to expand...
Click to collapse
Nope!