Develop Bugs

ASUS Zenfone 5/6 CN, CUCC, TW to WW

After many many tries i found a way to convert my CUCC edition to WW.
This way should work for any Edition.
1.) Install ADB & USB Drivers
2.) Download recovery image (version should be smaller or equal to desired rom)
3.) Boot to fastboot mode (Power + Vol Up)
4.1) flash fastboot.img from original desired rom zip (fastboot flash fastboot fastboot.img)
4.2) flash recovery image (fastboot flash recovery xyz.img)
5.) reboot to fastboot again
6.) launch recovery from fastboot
7.) upload firmware (adb sideload xyz.zip)
8.) wipe cache
9.) reboot
Your phone should now have the desired ROM & SKU (even future OTA updates should work)
Dowloads for Zenfone 5
Recovery images:
https://www.asuswebstorage.com/navigate/s/644D9E0A19714899974C75FC4B6C87EDY
https://www.mediafire.com/folder/cq6wwpya68azb/ZenFone_5_recovery
ROMs:
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+ZenFone+5
Downloads for Zenfone 6
Recovery Images:
https://www.asuswebstorage.com/navigate/s/DF5630C78E42431AB3043153CD59A3F3Y
https://www.mediafire.com/folder/4lo1w7qe30kdk/ZenFone_6_recovery
ROMs:
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+ZenFone+6
Credits:
Recovery Images: shakalaca

cant even enter recovery/fastboot after fastbooting the image ...
cant even enter recovery/fastboot after fastbooting the image ...

demonfruzz said:
cant even enter recovery/fastboot after fastbooting the image ...
Click to expand...
Click to collapse
Fot me it worked, the only thing I can think of that I made additionally was to flash ww fastboot image from desired ww original zip.

fastbone said:
Fot me it worked, the only thing I can think of that I made additionally was to flash ww fastboot image from desired ww original zip.
Click to expand...
Click to collapse
hmmmp not sure ,all i know was after i loaded the recovery ,then usb logo came up ,i rebooted from there on my recovery partition dissapeared.now i finally got a way to enter recovery again ,using quickboot app but i still cannot excess fastboot mode
---------- Post added at 08:26 AM ---------- Previous post was at 08:19 AM ----------
so all you did was flash the img file ,
then you flash the newest WW rom
regardles of your phone's SKU image
meaning if my phone is cucc i can just straightaway flash WW newst rom?
thankyou

demonfruzz said:
hmmmp not sure ,all i know was after i loaded the recovery ,then usb logo came up ,i rebooted from there on my recovery partition dissapeared.now i finally got a way to enter recovery again ,using quickboot app but i still cannot excess fastboot mode
---------- Post added at 08:26 AM ---------- Previous post was at 08:19 AM ----------
so all you did was flash the img file ,
then you flash the newest WW rom
regardles of your phone's SKU image
meaning if my phone is cucc i can just straightaway flash WW newst rom?
thankyou
Click to expand...
Click to collapse
Yes i flashed fastboot.img with adb fastboot flash fastboot fastboot.img (from original WW Zip)
than i flashed a WW recovery from the download archive
than i started recovery via fastboot
than i flashed original WW zip via sideload.
DONE WW edition phone

It works ... thx u
Fastbone, just wanted to say a big thanks, your advice worked fine for me, up and running with the latest WW rom .. :good:
Cheers
Phuketmark...

hi everyone
In this video explain the full story : flash cn/tw to ww
but i have three question
one of them that; the guy in this video when goes to adb command window and want to flash fastboot&boot ,the device is in the fastboot mode or android mode ??
Second question is that when he restart phone after flash fastboot&boot and restart ; is he restart phone to normal mode ot fastboot again ???
im not understood these parts.
And the last question is : my rom is cucc version ; so am i allow to use this rom ( cn version ) in this method or not ?
Thank u in advance..

lexiamen said:
hi everyone
In this video explain the full story : flash cn/tw to ww
but i have three question
one of them that; the guy in this video when goes to adb command window and want to flash fastboot&boot ,the device is in the fastboot mode or android mode ??
Second question is that when he restart phone after flas fastboot&boot and restart ; is he restart phone to normal mode ot fastboot again ???
im not understood these parts.
And the last question is : my rom is cucc version ; so am i allow to use this rom ( cn version ) in this method or not ?
Thank u in advance..
Click to expand...
Click to collapse
from android mode you can simply boot to fastboot by issuing following command: "adb reboot fastboot"
or to recovery: "adb reboot recovery"
and it should not matter which version you convert to which version as long as you choose the right fastboot and recovery image (the edition you want to have as a result)

doesn't work with CUCC firmware
I tried this method. My fimware is ASUS_T00G_CUCC_user_1.17.40.17_20140812_9510.
At step adb sideoad : Error : "E:signature verification failed. Installation aborted. Can't open /tap/update-script.log. E:Cannot load volume /sisc!"
I used these : 1.17.40.16_ww_recovery.img and UL_ASUS_T00G_WW_1_18_40_11.zip.
Any idea please ?

johnlamarck said:
I tried this method. My fimware is ASUS_T00G_CUCC_user_1.17.40.17_20140812_9510.
At step adb update : Error : "E:signature verification failed. Installation aborted. Can't open /tap/update-script.log. E:Cannot load volume /sisc!"
Click to expand...
Click to collapse
have you unlocked your bootloader via official ASUS unlock tool?

Done !
fastbone said:
have you unlocked your bootloader via official ASUS unlock tool?
Click to expand...
Click to collapse
I managed to update by changing the name of the WW rom into CUC. Thanks for your help.

cucc 1.96 to ww 1.18
my way to update from cucc 1.96 (!!) to ww 1.18
was
adb + driver
adb sideload 1.14cn firmware (cn original without rename)
reboot
adb sideload 1.14 ww firmware
reboot
adb sideload 1.16 ww
reboot
adb sideload 1.18 ww
bye

helping those failed cuz they dint manage to flash fastboot
fastbone said:
After many many tries i found a way to convert my CUCC edition to WW.
This way should work for any Edition.
1.) Install ADB & USB Drivers
2.) Download recovery image (version should be smaller or equal to desired rom)
3.) Boot to fastboot mode (Power + Vol Up)
4.1) flash fastboot.img from original desired rom zip (adb fastboot flash fastboot fastboot.img)
4.2) flash recovery image (fastboot flash recovery xyz.img)
5.) reboot to fastboot again
6.) launch recovery from fastboot
7.) upload firmware (adb sideload xyz.zip)
8.) wipe cache
9.) reboot
Your phone should now have the desired ROM & SKU (even future OTA updates should work)
Dowloads for Zenfone 5
Recovery images:
https://www.asuswebstorage.com/navigate/s/644D9E0A19714899974C75FC4B6C87EDY
https://www.mediafire.com/folder/cq6wwpya68azb/ZenFone_5_recovery
ROMs:
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+ZenFone+5
Downloads for Zenfone 6
Recovery Images:
https://www.asuswebstorage.com/navigate/s/DF5630C78E42431AB3043153CD59A3F3Y
https://www.mediafire.com/folder/4lo1w7qe30kdk/ZenFone_6_recovery
ROMs:
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+ZenFone+6
Credits:
Recovery Images: shakalaca
Click to expand...
Click to collapse
thank you for your post.
i have manage to update from cucc to ww
your procedure is definitely correct.
on your 4.1 procedure is got mistaken command
4.1) flash fastboot.img from original desired rom zip (adb fastboot flash fastboot fastboot.img)'
when you want to flash it. please do (fastboot flash fastboot fastboot.img)
for some newbie they dint know that by typing adb fastboot wont be able to flash
and they would thought they have flashed it since there is alot of words coming out from the cmd. but its just adb information.
after this point.
do exactly like above.
you will manage to get it done correctly like i am.
just write it for hope to help newbie on flashing.

Thanks, changed at first post....

Question.?
Is This Wright??
2.) Download recovery image (version should be smaller or equal to desired rom) = cucc version??
4.2) flash recovery image (fastboot flash recovery xyz.img)= cucc version??
7.) upload firmware (adb sideload xyz.zip)= version 2.19 ww??

ali3993 said:
Is This Wright??
2.) Download recovery image (version should be smaller or equal to desired rom) = cucc version??
4.2) flash recovery image (fastboot flash recovery xyz.img)= cucc version??
7.) upload firmware (adb sideload xyz.zip)= version 2.19 ww??
Click to expand...
Click to collapse
no ... you need to choose the target region (eg. CUCC->WW choose WW)

unsuccessful!!!
my rom: cucc 1.17.40.17
desired rom: ww 1.16.40.7

ali3993 said:
unsuccessful!!!
my rom: cucc 1.17.40.17
desired rom: ww 1.16.40.7
Click to expand...
Click to collapse
so you chose recovery from ww 1.16.40.7 ?

fastbone said:
so you chose recovery from ww 1.16.40.7 ?
Click to expand...
Click to collapse
yes
no comment?
adb original zip rom" or " extract zip and adb ..user file ?

help
I follow the instruction, after flash fastboot.img and revovery.img, I choose reboot fastboot
now I cant enter fastboot mode, I press and hlod vol up and power, it turn on into normal mode. Please help. How can I enter fastboot mode again

[NOT WORKING] ReLock bootloader for ZE551ML

After some research on internet and xda i decided to try to relock my bootloader with the information provided by RealYoti, and this is how i did without causing a war conflict a Cthulhu evocation or a burning Zenfone
Anyway follow this guide at your own risk, turn on your brain and everything will be fine (hopefully)
Download these files
AFT: https://mega.nz/#!LcwhXDLZ!PN1jzQ0hD...QyvMzN8VK4fVBU
RAW: https://mega.nz/#!7cA3nTZC!NiHOzVoVP...axpE2es7lrwGpI
Install the Asus flash tool
Reboot your zenfone to bootloader
Open the asusflash tool
Select your model in the drop-down menu (under the button settings)
Choose if you want to keep the data or to wipe it all (i wiped)
Click on the box and the select the raw file you just downloaded
Connect your phone to the pc with the original usb cable
Now you should see your phone in the device list, check if all is ok and then start the flash clicking the green button on the top
Wait for 6-7 minutes and your phone should boot to android but now is recognized as ZE550ML, we have to fix this
Reboot to bootloader
Download from here (thanks to Shaka Huang) the last recovery set for the ze551ml (recovery.img droidboot.img boot.img)
Flash it from cmd:
Code:
fastboot flash fastboot droidboot.img
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash boot boot.img
Now we are ready to flash the ZE551ML firmware download the last one from the asus support site
From the bootloader enter in the recovery
Apply update from adb/sideload
From the pc CMD type
Code:
adb sideload thezipyoujustdownloaded.zip
Wait
Wipe data/cache factory restore
Reboot
Enjoy your warranty
Let me now if there is any unclear passage
Thanks to:
RealYoti
Shakalaca
I Tried to flash twrp after this procedure and it worked so the bootloader even with this method remains unlocked, it only reverts to stock

this is awesome in case you need to regain warranty!!

I Updated the first post, the bootloader after a deeper research remains unlocked, so the method with the raw file reverts only to stock
Inviato dal mio ASUS_Z00AD utilizzando Tapatalk

Very strange

To be frank, i didn't even gave a thought that it will work

In this way can I return to stock rom ?
I cant download the files from mega.
Waiting for an other method for relock the bootloader.

How To Unlock Bootloader Of Vivo Phones ?

Hi!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I’ve seen a lot of users struggling around the internet to find out the way to root vivo phones.
And, Yeah, There are a lot of tutorials available explaining how to unlock bootloader and root vivo phones, but , nearly all of them do not work.
So, After a bit of research, here’s what I got :-
Vivo developers modified there bootloader to used a different command for bootloader unlock/relock than the the stock android commands.
Also, On some phones like vivo y51l (Upgrade to PDF1510_2.6.7), you'll need to upgrade to the latest version available.
And That’s Why we need a modified fastboot binary to unlock bootloader of vivo.
vivo_fastboot on Github
WARNING! It’ll void your warranty.
Follow the below steps to unlock bootloader of vivo phones :-
I've compiled fastboot binary with necessary modifications which you can download from below
Download vivo_fastboot For Windows
Downloadvivo_fastboot For Linux
Download : Vivo_fastboot_v2 :- Linux Windows
Extract the downloaded files on your Computer and open Terminal/Command Prompt in the extracted directory
Now power off your vivo phone and enter fastboot mode by pressing power+ vol – buttons simultaneously.
If you are using linux then type
sudo ./fastboot bbk unlock_vivo
If you are using Windows then type
fastboot bbk unlock_vivo
Voila ! Your Vivo Phone is now Unlocked.
If You Want to lock it again then just type
fastboot bbk lock_vivo
In case Of linux type
sudo ./fastboot bbk lock_vivo
UPDATE :- I discovered a new command for some Vivo phones, it isn't working for me but many user asked to make a fastboot binary with that command.
The new command is fastboot vivo_bsp unlock_vivo (Type fastboot help to get list of supported commands.) If this method isn't working for you, don't worry, I have another working method ( posting soon...)
Now you can port and flash twrp recovery and Custom Roms on your vivo devices.
YouTube Video for unlocking vivo bootloader :
Bingo......
UNOFFICIAL CM 12.1 for Vivo y51l is out, Have a look :
Original Thread Here
UPDATE :-​[/
I discovered a new method few months ago, & it works well on new vivo devices:-
This method is unofficial & may brick your device (in 1% cases)
I'm not responsible for any loss or harm done to your device, sdcard, PC, home, ferrari etc.
If You are using this method to unlock bootloader, use at your own risk !
Downloads :-
BLUnlocker_v1.zip
QDLoader_HS_USB_Driver.7z
Steps to unlock bootloader :-
1. Extract the BLUnlocker_v1.zip (You have done this already, trust me, i know you did it
2. Install Qualcomm USB Driver for Qdloader 9008 mode.
3. Get your phone, press vol up & down buttons together & connect USB at the same time.
4. Extract your firehose file from your stock firmware (It's usually named like 'prog_emmc_firehose_****.mbn') & place it in the current directory.
5. Check the port number your device is connected to in WIndows Device Manager. (Looks like COM*)
6. Double Click the 'dump_devinfo.bat' file.
7. Enter the port number (from step 5) & press enter
8. Edit your devinfo.img using HxD Hex Editor as shown in my video (Or you can comment on my channel with a link to your devinfo.img)
9. Double click 'unlock.bat'
-:Video:-​
If all went good, your bootloader is unlocked now!
Thanks me later, go break some eggs !
Peace !
vivo fastboot binary sources ( My GitHub ) :- https://github.com/Naveen3Singh/vivo_fastboot
! GIVE CREDITS IF YOU ARE USING MY WORK !

unknown command or device is lock
when i try to unlock bootloader on Vivo v5 Plus(1611) error comes unknown command or device is lock
please help me.
Naveen Singh said:
Hi!
I’ve seen a lot of users struggling around the internet to find out the way to root vivo phones.
And, Yeah, There are a lot of tutorials available explaining how to unlock bootloader and root vivo phones, but , nearly all of them do not work.
So, After a bit of research, here’s what I got :-
Vivo developers modified there bootloader to used a different command for bootloader unlock/relock than the the stock android commands.
And That’s Why we need a modified fastboot binary to unlock bootloader of vivo.
WARNING! It’ll void your warranty.
Follow the below steps to unlock bootloader of vivo phones :-
I've compiled fastboot binary with necessary modifications which you can download from below
Download vivo_fastboot For Windows
https://drive.google.com/open?id=0BwcKR-Av9XBcVGRRYTJkWXAzcUU
Download vivo_fastboot For Linux
https://drive.google.com/open?id=0BwcKR-Av9XBcc0VKd3JKai1oQnM
(I'm a new member so i can not post links :laugh::laugh: )
Extract the downloaded files on your Computer and open Terminal/Command Prompt in the extracted directory
Now power off your vivo phone and enter fastboot mode by pressing power+ vol – buttons simultaneously.
If you are using linux then type
sudo ./fastboot bbk unlock_vivo
If you are using Windows then type
fastboot bbk unlock_vivo
Voila ! Your Vivo Phone is now Unlocked.
If You Want to lock it again then just type
fastboot bbk lock_vivo
In case Of linux type
sudo ./fastboot bbk lock_vivo
Now you can port and flash twrp recovery and Custom Roms on your vivo devices.
If You have any confusion or question, leave a comment.
Click to expand...
Click to collapse

Enable Oem unlock from developer options
First You have to enable oem unlock from developer options
Then download the vivo fastboot from the link above
And follow the steps above.

Doesn't work on my vivo 1611. [VIVO V5 PLUS]
Naveen Singh said:
Hi!
I’ve seen a lot of users struggling around the internet to find out the way to root vivo phones.
And, Yeah, There are a lot of tutorials available explaining how to unlock bootloader and root vivo phones, but , nearly all of them do not work.
So, After a bit of research, here’s what I got :-
Vivo developers modified there bootloader to used a different command for bootloader unlock/relock than the the stock android commands.
Also, On some phones like vivo y51l (Upgrade to PDF1510_2.6.7), you'll need to upgrade to the latest version available.
And That’s Why we need a modified fastboot binary to unlock bootloader of vivo.
WARNING! It’ll void your warranty.
Follow the below steps to unlock bootloader of vivo phones :-
I've compiled fastboot binary with necessary modifications which you can download from below
Download vivo_fastboot For Windows
https://drive.google.com/open?id=0BwcKR-Av9XBcVGRRYTJkWXAzcUU
Download vivo_fastboot For Linux
https://drive.google.com/open?id=0BwcKR-Av9XBcc0VKd3JKai1oQnM
(I'm a new member so i can not post links :laugh::laugh: )
Extract the downloaded files on your Computer and open Terminal/Command Prompt in the extracted directory
Now power off your vivo phone and enter fastboot mode by pressing power+ vol – buttons simultaneously.
If you are using linux then type
sudo ./fastboot bbk unlock_vivo
If you are using Windows then type
fastboot bbk unlock_vivo
Voila ! Your Vivo Phone is now Unlocked.
If You Want to lock it again then just type
fastboot bbk lock_vivo
In case Of linux type
sudo ./fastboot bbk lock_vivo
Now you can port and flash twrp recovery and Custom Roms on your vivo devices.
If You have any confusion or question, leave a comment.
Click to expand...
Click to collapse
Unknown error comes. And all fastboot options come up.???

amangupta711 said:
Unknown error comes. And all fastboot options come up.???
Click to expand...
Click to collapse
Download the modified fastboot instead of using an official version.
For windows : https://drive.google.com/open?id=0BwcKR-Av9XBcVGRRYTJkWXAzcUU
For linux : https://drive.google.com/open?id=0BwcKR-Av9XBcc0VKd3JKai1oQnM

Naveen Singh said:
Download the modified fastboot instead of using an official version.
For windows : https://drive.google.com/open?id=0BwcKR-Av9XBcVGRRYTJkWXAzcUU
For linux : https://drive.google.com/open?id=0BwcKR-Av9XBcc0VKd3JKai1oQnM
Click to expand...
Click to collapse
Not Working For Me!
This comes up..
https://ibb.co/b7N4T6
PLZZZ HELP...

amangupta711 said:
Not Working For Me!
This comes up..
https://ibb.co/b7N4T6
PLZZZ HELP...
Click to expand...
Click to collapse
You are using some "vivo bootloader unlock by Hakkim.exe"
Please download the fastboot from this link
Google Drive

Its just the folder name..
Naveen Singh said:
You are using some "vivo bootloader unlock by Hakkim.exe"
Please download the fastboot from this link
Google Drive
Click to expand...
Click to collapse
The content are yours only.
See this..
https://ibb.co/bUoED6
I think this doesn't work with VIVO V5 PLUS [VIVO 1611].

amangupta711 said:
The content are yours only.
See this..
https://ibb.co/bUoED6
I think this doesn't work with VIVO V5 PLUS [VIVO 1611].
Click to expand...
Click to collapse
It seems like you have already installed fastboot systemwide.
To use the fastboot binary in current directory
Use this command : .\fastboot bbk unlock_vivo
Or just use command prompt instead of powershell on windows.

NEW ERROR
Naveen Singh said:
It seems like you have already installed fastboot systemwide.
To use the fastboot binary in current directory
Use this command : .\fastboot bbk unlock_vivo
Or just use command prompt instead of powershell on windows.
Click to expand...
Click to collapse
Now I got a new error..
See this...
https://ibb.co/kNbpwR

amangupta711 said:
Now I got a new error..
See this...
https://ibb.co/kNbpwR
Click to expand...
Click to collapse
It looks like something is wrong with the bootloader or the firmware version installed in your phone is not supported (unlocking) yet.
As mentioned in the post some phones need to be upgraded (like vivo y51l).
If you have time and patience, try using different software version from vivoglobal or just reflash the current one.
Is oem unlock enabled from developer options ?

YES OEM Unlocking is enabled....
Naveen Singh said:
It looks like something is wrong with the bootloader or the firmware version installed in your phone is not supported (unlocking) yet.
As mentioned in the post some phones need to be upgraded (like vivo y51l).
If you have time and patience, try using different software version from vivoglobal or just reflash the current one.
Is oem unlock enabled from developer options ?
Click to expand...
Click to collapse
Yes I also think it is unsupported.
Tried many s/w, nothing works.
No other option than waiting..

Doesn't work on vivo Y53.

Shiki Shiori said:
Doesn't work on vivo Y53.
Click to expand...
Click to collapse
Error??
Tell me...

Naveen Singh said:
Error??
Tell me...
Click to expand...
Click to collapse
...
FAILED (remote: unclock fail.)
finished. total time: 0.001s

Shiki Shiori said:
...
FAILED (remote: unclock fail.)
finished. total time: 0.001s
Click to expand...
Click to collapse
try on other s/w versions and enable oem unlock from developer options.

Naveen Singh said:
try on other s/w versions and enable oem unlock from developer options.
Click to expand...
Click to collapse
oem unlock is enabled.
what is s/w?

Shiki Shiori said:
oem unlock is enabled.
what is s/w?
Click to expand...
Click to collapse
Use the Linux version of fastboot if u use Linux
and install latest software (s/w) version from vivo global

Naveen Singh said:
Use the Linux version of fastboot if u use Linux
and install latest software (s/w) version from vivo global
Click to expand...
Click to collapse
Well... this is linux version. Also, this is the latest update.
---------- Post added at 11:55 AM ---------- Previous post was at 11:45 AM ----------
would you be willing to do this step, but instead of oem, get bbk?
https://www.xda-developers.com/how-to-discover-hidden-fastboot-commands/

Plz help rooting vivo v7 1718.
Thanks in advance

How To Guide Flash/Install TWRP on Realme GT Master Edition RMX3360 (Indian variant)

TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?

aprilfoo said:
I am getting an error in the last step (Flash current TWRP): "failed to create ramdisk to flash". Any idea?
Click to expand...
Click to collapse
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.

aprilfoo said:
Maybe more help for the issue i just mentioned above: in the temporary TWRP, the file ramdisk-files.txt contains a line for "mnt/vendor/persist", which does not exist, and thus the cpio command fails.
Click to expand...
Click to collapse
Screenshot can help better, try taking and sending it here.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hello sir is it compatible with rmx3363 ?

Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.

xeltos said:
Okay Stupid question: Has Realme officially released bootloader unlock tool? I know they have released kernel and drivers.
Click to expand...
Click to collapse
well yes for some phones but deeptest somehow works for others if your lucky test them all and see ^^

pkm774 said:
TWRP flashing guide for Realme GT Master edition RMX3360​
Flash at your own risk. You might LOSE all data on your phone.
( I will be not responsible for any damage to your device )​
Prerequisites :
Your Bootloader Should be Unlocked. Click Here For Instructions.
First Back up all of your data and files present on the phone because the phone might be erased from the process.
Install Minimal ADB and Fastboot tool from here: LINK
Get the A.09 vbmeta.img files for the Stock firmware. If you are using A.09 firmware then vbmeta.img is needed from A.09 firmware file. LINK
Get the TWRP image file and rename it to twrp.img . Unofficial TWRP Link
The process to disable verity/Verification (Important for Flashing TWRP Recovery):
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that vbmeta.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img in the cmd terminal.
Reboot the phone again to fastboot mode.
Follow the further process.
The process to install TWRP :
Reboot the phone to fastboot (Vol Down + Power ).
Connect the phone to the computer using an USB data cable. Preferred to use the stock USB cable.
Search for Minimal adb and fastboot icon in the 'Windows search' and right-click for 'Locate file location' option.
Copy and Place that twrp.img in the Minimal adb and fastboot folder.
Hold Shift and Right-click in that directory and click on the options 'open cmd terminal there'.
Type fastboot boot twrp.img in the cmd terminal.
The phone will boot in TWRP recovery and after that go to Advanced > Flash Current TWRP.
Done you have installed TWRP in your device.
TWRP flashed now Enjoy Flashing Custom files and ZIPS.​
Click to expand...
Click to collapse
hello sir is it compatible with rmx3363 ?

is this method work for latest Android 12 for installing twrp ?

pankaj9pankaj9334 said:
is this method work for latest Android 12 for installing twrp ?
Click to expand...
Click to collapse
Currently, A12 Twrp is under development by twrp team. So you have to wait.

ites working with rmx3363 finally i got twrp to work ^^ thanks

NextB said:
ites working with rmx3363 finally i got twrp to work ^^ thanks
Click to expand...
Click to collapse
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?

guizzzmo said:
Allright, you are the best.
Without any modification of twrp.img ?
On Android 11 Firmware ?
Click to expand...
Click to collapse
without any

NextB said:
without any
Click to expand...
Click to collapse
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above

guizzzmo said:
I can boot this twrp with fastboot boot twrp.img
but if i try to do Advanced > Flash Current TWRP
i have the same error than as @aprilfoo above
Click to expand...
Click to collapse
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)

aprilfoo said:
Actually i found a workaround but i prefer not even to share it because of a bigger issue: the OP forgot to mention that: 'Installing Magisk is must if you are planning to press "Flash Current TWRP" when flashing alongside stock ROM'. I did not install Magisk and ended up with a completely dysfunctional phone and had to flash again the stock OS.
So i suggest to wait a bit more (some ROMs are in release candidate in the Telegram group)
Click to expand...
Click to collapse
ok thanks for the reply. wich telegram group?

guizzzmo said:
ok thanks for the reply. wich telegram group?
Click to expand...
Click to collapse
@realmegtmasterupdates - telegram channel publications statistics Realme GT Master | UPDATES
telegram channel publications statistics of Realme GT Master | UPDATES telegram channel. All about Realme GT Master - RMX3366 ROMs, Kernels, Guides, Mods, NEWS, everything. Stay up-to-date with us! Official Group: @RealmeGTMaster Photography : @RMGTMasterPhotography Gaming : @RMGTMasterGaming...
telemetr.io

Use This
https://www.getdroidtips.com/twrp-recovery-realme-gt-master-edition/

Oh i see the problem, it's because the new partition slot A/B.
Ok i have magisk installed on stock rom but i think i will waiting. I stay on UI 2.0 with full root, magisk, lsposed, safetynet, and no bugs

Asus ZenPad Z8s P00J / ZT582KL - Lost Android 8.0 Oreo Update Discovered

Recently I came across a string "pub/ASUS/LiveUpdate/Debug/ZenPad/ASUS_P00J.idx" when searching inside v3.7.4 aboot binary (emmc_appsboot.signed.mbn) in an attempt to find root method for this aging but still capable 8" 2048x1536 Android 7 tablet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Out of curiosity I put it after Asus download server https://dlcdnet.asus.com to build a download URL (The domain dlcdnlpdv.asus.com shown above no longer exists), and inside downloaded ASUS_P00J.idx there are 3 firmware packages listed: v3.7.3, v3.7.4, and unknown to virtually all Z8s owners, a v5.1.5 firmware.
- The "Release" ASUS_P00J.idx file has fewer firmwares in it (only v3.7.3).
It came as a surprise as the version 5 indicates something big. I combined it with dlcdnet.asus.com into download URL (https://dlcdnet.asus.com/pub/ASUS/EeePAD/Zenpad/ZT582KL/VZW_ZT582KL_V515_all_user.zip), extracted .raw firmware file, unpacked it with https://github.com/Yoti/unraw and the extracted build.prop in system.img proves it is indeed Android 8.0.0, the lost Oreo build of Z8s released in May 2018 but for unknown reason, never pushed by Verizon as OTA update.
I successfully flashed the .raw firmware to my Z8s tablet with Asus Flash Tool v1.0.0.45 under fastboot mode (adb reboot bootloader, or volume down + power buttons when turned off). Theoretically it can also flash by simply copying downloaded .zip file to root of internal storage (/sdcard folder). Now it brings native split-window and 8.0+ app support to our forgotten gem Z8s!
Potentially to root and unlock bootloader:
The new Oreo aboot no longer verifies integrity of boot.img and recovery.img. Flashing to Z8s is already possible with an extra command in fastboot mode:
fastboot getvar sofia_support
fastboot flash boot <path-to-boot.img>
# or: fastboot flash recovery <path-to-recovery.img>
Click to expand...
Click to collapse
With Nougat bootloader, you have to flash the officially signed image from extracted .raw firmware or it will refuse to boot ("Start Up Failed").
Now with Oreo it lets you to boot even with a modified boot.img, displaying a "Your device has loaded a different operating system" screen but allows continuing to boot into OS.
- After that I made it past Verizon splash screen, got "To start Android, enter your password" message and cannot enter OS with a Magisk-patched boot.img flashed.
- Going back by flashing stock boot.img returned it to normal with no data loss.
- UNTESTED: a factory reset (after logging out all Google accounts) can potentially remove the encryption and grant root access.
"fastbook oem unlock" is also possible with new bootloader, but there's no OEM Unlock option available inside Settings -> Developer options.
- UNTESTED: with root you can flip several bits in devinfo partition to achieve direct bootloader unlock (see https://forum.xda-developers.com/t/...vices-devinfo-partition-modification.4100897/, unfortunately there's no firehose / ZT582KL_EMERGENCY_DLOAD.zip publicly shared yet)
- Also UNTESTED and requires root: or toggle the value of sys.oem_unlock_allowed from 0 to 1 (stored in last byte of config partition), which then allows fastboot oem unlock command inside fastboot mode.
Enjoy!

Hello, this is great news! I have a couple of these Z8s devices laying around.
I am curious about how you pulled this off.
I downloaded the zip file, extracted it and opened the flash tool updater.
The 1.0.0.45 asus flash updater tool does not list the ZT582KL device.
I found a newer version of this tool but it does not start (failed to download version control file via ftp).
I can not find a way to bypass this version check.
I tried to install the update as a zip file on an sd card by using android recovery mode. Unfortunately I got an error saying:
can't open /tmp/update-script.log
So I think it has to be updated in fastboot mode. If you could show the steps you performed, I would be most grateful.
Thanks in advance and kind regards!

edzehummel said:
Hello, this is great news! I have a couple of these Z8s devices laying around.
I am curious about how you pulled this off.
I downloaded the zip file, extracted it and opened the flash tool updater.
The 1.0.0.45 asus flash updater tool does not list the ZT582KL device.
I found a newer version of this tool but it does not start (failed to download version control file via ftp).
I can not find a way to bypass this version check.
I tried to install the update as a zip file on an sd card by using android recovery mode. Unfortunately I got an error saying:
can't open /tmp/update-script.log
So I think it has to be updated in fastboot mode. If you could show the steps you performed, I would be most grateful.
Thanks in advance and kind regards!
Click to expand...
Click to collapse
I flashed the zip file under fastboot and the latest Asus Flash Tool version 2.x never worked for me, only 1.0.0.45 could process the firmware .zip file successfully.
Attached is a patched version of ASUS Flash Tool 1.0.0.45 binary, replacing all reference of ZT581KL with ZT582KL (they have the same SoC, I tried with this patch and it worked).
1. Install ASUS Flash Tool 1.0.0.45 (I got it from https://www.gsmofficial.com/asus-zenfone-flash-tool-v1-0-0-45/)
2. Extract the attached AsusFlashTool_ZT582KL.exe into "C:\Program Files (x86)\ASUS\ASUS Flash Tool" folder
3. Run AsusFlashTool_ZT582KL.exe
4. Select device model ZT582KL
5. Select ZT582KL_all_VZW_user_V5.1.5.zip (or .raw) by clicking on the box icon
6. Connect the tablet in fastboot mode (adb reboot bootloader, or volume down + power buttons when turned off)
7. Click on Start button (wipe data is not required) and wait for flash to complete

satelliteseeker said:
I flashed the zip file under fastboot and the latest Asus Flash Tool version 2.x never worked for me, only 1.0.0.45 could process the firmware .zip file successfully.
Attached is a patched version of ASUS Flash Tool 1.0.0.45 binary, replacing all reference of ZT581KL with ZT582KL (they have the same SoC, I tried with this patch and it worked).
1. Install ASUS Flash Tool 1.0.0.45 (I got it from https://www.gsmofficial.com/asus-zenfone-flash-tool-v1-0-0-45/)
2. Extract the attached AsusFlashTool_ZT582KL.exe into "C:\Program Files (x86)\ASUS\ASUS Flash Tool" folder
3. Run AsusFlashTool_ZT582KL.exe
4. Select device model ZT582KL
5. Select ZT582KL_all_VZW_user_V5.1.5.zip (or .raw) by clicking on the box icon
6. Connect the tablet in fastboot mode (adb reboot bootloader, or volume down + power buttons when turned off)
7. Click on Start button (wipe data is not required) and wait for flash to complete
Click to expand...
Click to collapse
Hello satelliteseeker,
Thank you for your effort, detailed and clear description and the shared asustool files. I performed the steps and it worked flawlesslly. I have successfully updated my Asus Zenpad Z8s to Android 8.0 and it works perfectly!!
I am very happy with it!! Thanks again and kind regards!
Edze.

I just achieved root doing nothing more than following your clearly defined advice above
1. applied the oreo update with your modded AFT
2. extracted boot.img from the oreo update .zip
3. patched boot.img with the newest magisk (25.1)
4. flashed patched boot.img using fastboot
5. factory reset
6. ¿???
7. profit
Hope this helps.
Much thanks to you brother for all your work at getting this device a working root. Finding this lost/unreleased update for our device was nothing short of an act of genius

Sneaky.Ninja said:
I just achieved root doing nothing more than following your clearly defined advice above
1. applied the oreo update with your modded AFT
2. extracted boot.img from the oreo update .zip
3. patched boot.img with the newest magisk (25.1)
View attachment 5642587
4. flashed patched boot.img using fastboot
5. factory reset
6. ¿???
View attachment 5642583
7. profit
View attachment 5642585
Hope this helps.
Much thanks to you brother for all your work at getting this device a working root. Finding this lost/unreleased update for our device was nothing short of an act of genius
Click to expand...
Click to collapse
Hi @Sneaky.Ninja ,
Weird, I couldn't get pass step #6 and it is prompting me for decryption password like what satelliteseeker mentioned. Do you know if I have missed any steps in between?

I'm going to try to be thurough but to be honest I'm kind of scratching my head coming up with a list of possible actions that we could of performed different. So my apologies if some of these suggestions are obviously pointless or need to be performed in any combination/order other than what's implied below but these are all things I had done
-------------------------------------------------------------------
* Did you go through the device's initial set-up/ log into a google account/ update all apps while still on V3.7.4 (nougat) before updating to V5.1.5 (oreo)
* Did you use the latest version of Magisk Manager (25.1)
* When patching boot.img did you select all three options
Preserve AVB/dm-verity
Preserve forced encryption
Patch vb meta in boot image
* Factory reset after receiving the 'type password to decrypt storage' prompt at boot
* Boot into recovery (adb reboot recovery / fastboot reboot-recovery) and wipe cache partition
* From the fastboot menu select USB debug mode (Enables USB debugging/ADB)
********CAUTION*********
Proceed with caution. I've soft bricked this device in the past using one or more of these commands
**************************
You could try messing around with these fastboot oem commands that I found in the update.raw binary. I included the whole list but seperated what I feel could make any difference
Some commands don't seem to work and others need you to enter a variable such as 1 or 0 (on/off).
oem verity
oem adb_enable
oem CTS_Auto
oem ffu_unlock
oem reset_root
**************************
oem device-info
oem frp_status
oem enter_method
oem get_baseband
oem get_build_version
oem get_device_model
oem get_device_name
oem get_debug_idx
oem get_debug_status
oem get_IMEI
oem get_model
oem get_release_idx
oem get_release_status
oem get_sua_server
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel
oem EnterShippingMode
oem reboot
oem reboot-recovery
oem reboot-bootloader
oem lock
oem unlock
oem unlock-go
oem flashing lock
oem flashing unlock
oem flashing lock_critical
oem flashing unlock_critical
oem flashing get_unlock_ability
oem emmc_info
oem emmc_show_partitions
oem emmc_read_modemst
oem emmc_read_partition
oem emmc_read_userdata
oem resize_partition_table
oem hash
oem preflash
oem continue
oem flash_all_start
oem flash_all_end
Keep the thread updated on any progress or lack of.

Sneaky.Ninja said:
I'm going to try to be thurough but to be honest I'm kind of scratching my head coming up with a list of possible actions that we could of performed different. So my apologies if some of these suggestions are obviously pointless or need to be performed in any combination/order other than what's implied below but these are all things I had done
-------------------------------------------------------------------
* Did you go through the device's initial set-up/ log into a google account/ update all apps while still on V3.7.4 (nougat) before updating to V5.1.5 (oreo)
* Did you use the latest version of Magisk Manager (25.1)
* When patching boot.img did you select all three options
Preserve AVB/dm-verity
Preserve forced encryption
Patch vb meta in boot image
* Factory reset after receiving the 'type password to decrypt storage' prompt at boot
* Boot into recovery (adb reboot recovery / fastboot reboot-recovery) and wipe cache partition
* From the fastboot menu select USB debug mode (Enables USB debugging/ADB)
********CAUTION*********
Proceed with caution. I've soft bricked this device in the past using one or more of these commands
**************************
You could try messing around with these fastboot oem commands that I found in the update.raw binary. I included the whole list but seperated what I feel could make any difference
Some commands don't seem to work and others need you to enter a variable such as 1 or 0 (on/off).
oem verity
oem adb_enable
oem CTS_Auto
oem ffu_unlock
oem reset_root
**************************
oem device-info
oem frp_status
oem enter_method
oem get_baseband
oem get_build_version
oem get_device_model
oem get_device_name
oem get_debug_idx
oem get_debug_status
oem get_IMEI
oem get_model
oem get_release_idx
oem get_release_status
oem get_sua_server
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel
oem EnterShippingMode
oem reboot
oem reboot-recovery
oem reboot-bootloader
oem lock
oem unlock
oem unlock-go
oem flashing lock
oem flashing unlock
oem flashing lock_critical
oem flashing unlock_critical
oem flashing get_unlock_ability
oem emmc_info
oem emmc_show_partitions
oem emmc_read_modemst
oem emmc_read_partition
oem emmc_read_userdata
oem resize_partition_table
oem hash
oem preflash
oem continue
oem flash_all_start
oem flash_all_end
Keep the thread updated on any progress or lack of.
Click to expand...
Click to collapse
Hi @Sneaky.Ninja,
Thanks for the guide, actually I have managed to root it by myself.
I noticed that on every new reboot upon factory reset, the tablet will first attempt to erase the device followed by encrypting it. If you proceed with flashing the patched boot.img AFTER the encryption, you will most likely hit the 'type password to decrypt storage' prompt. Thus, my speculation is that the encryption seems to be tied with which boot.img you were having at that time.
So, I then tried reflashing the original boot.img, getting back into the Setting UI once again and factory reset it, except for I was holding the Volume down button this time and it gets me straight into fastboot mode again. Then I flashed the patched boot.img once again, and viola... everything was working as expected (erasing, encrypting and booting into the device initial setup menu) with ROOT!

@satelliteseeker ,
With root, I then tried to play around with the config partition like you mentioned, flipping the last 00 to 01.
- Also UNTESTED and requires root: or toggle the value of sys.oem_unlock_allowed from 0 to 1 (stored in last byte of config partition), which then allows fastboot oem unlock command inside fastboot mode.
However, it seems like I'm still unable to proceed with fastboot oem unlock.. Actually, come to think about it, what's the point even if you have unlocked the bootloader but there are no custom roms for it.

s03191 said:
@satelliteseeker ,
With root, I then tried to play around with the config partition like you mentioned, flipping the last 00 to 01.
- Also UNTESTED and requires root: or toggle the value of sys.oem_unlock_allowed from 0 to 1 (stored in last byte of config partition), which then allows fastboot oem unlock command inside fastboot mode.
However, it seems like I'm still unable to proceed with fastboot oem unlock.. Actually, come to think about it, what's the point even if you have unlocked the bootloader but there are no custom roms for it.
Click to expand...
Click to collapse
Asus might have a different strategy to handle bootloader unlock (maybe it has to be devinfo partition?)
With a preceding command fastboot getvar sofia_support (more details in https://forum.xda-developers.com/t/...-z10-zt500kl-and-zenpad-3s-10-z500kl.4067617/), it's already possible to flash any firmware to boot / recovery / system partitions, so it's not required to achieve a full unlock to tinker with system, especially with root.
Again without debrick tools any such hack has a chance to brick the device. If it fails to enter fastboot, there's minimal chance for a recovery.

I am a Linux user and want to install this on my ZS8. I fired up a windows computer, downloaded the AFT above, unzipped it, and tried to run it, but it complains "The code execution cannot proceed because mfc110u.dll was not found. Reinstalling the program might fix this problem." I then read online that this is a Microsoft library, and installing their development tools might fix it, and some other things, but nothing is working. Any suggestions?

Just successfully upgraded my z8s to 8.0, Thank you so much for your information and tutorial. Really appreciate it.

After upgrading to 8.0, I tried to make a custom TWRP recovery migrated from Zenfone 3 ultra, which uses the same CPU model to Z8s, and successfully fastboot flashed it according to OP's guide. It initially worked well right after the flash, but after a reboot, the system wouldn't boot to the system but stopped at 'Your device is corrupt' as you can see from the pics below.
It seems like I could continue to boot by pressing the volume up button, but unfortunately, the volume up button has just been broken during my disassembly previously... So I'm wondering if anyone knows that everything will be fine as long as the volume up button is pressed, or if there is something wrong that needs to be fixed in the bootloader/recovery?
Thank you in advance.
Note: I managed to flash back the official boot.img and recovery.img, but the system still won't boot up. Also used Asus Flashtool and flashed the official .raw back but had no luck.

First off, I was able to get 8.0 install, amazing job!
When I run through the standard magisk steps though I'm clearly missing something. I'm pulling the boot.img file from the Zip->Raw file to feed to magisk and it's complaining with Unsupported\unknown image format. I use this method for other devices, so I'm generally used to how this should go. Did I miss something on how I should be sourcing the boot.img file.

satelliteseeker said:
I flashed the zip file under fastboot and the latest Asus Flash Tool version 2.x never worked for me, only 1.0.0.45 could process the firmware .zip file successfully.
Attached is a patched version of ASUS Flash Tool 1.0.0.45 binary, replacing all reference of ZT581KL with ZT582KL (they have the same SoC, I tried with this patch and it worked).
1. Install ASUS Flash Tool 1.0.0.45 (I got it from https://www.gsmofficial.com/asus-zenfone-flash-tool-v1-0-0-45/)
2. Extract the attached AsusFlashTool_ZT582KL.exe into "C:\Program Files (x86)\ASUS\ASUS Flash Tool" folder
3. Run AsusFlashTool_ZT582KL.exe
4. Select device model ZT582KL
5. Select ZT582KL_all_VZW_user_V5.1.5.zip (or .raw) by clicking on the box icon
6. Connect the tablet in fastboot mode (adb reboot bootloader, or volume down + power buttons when turned off)
7. Click on Start button (wipe data is not required) and wait for flash to complete
Click to expand...
Click to collapse
Thanks a bunch. This process worked for me. [edit: not so much, see next post] Couple points to add...
First, I did have issues getting communication to work reliably until I updated the driver in Windows Update. Other than that, the steps above worked as advertised (thanks!).
Second, for whatever reason when you flash to Oreo the z8s is no longer Play Protect certified. Because of that, I am (so far) unable to download the Netflix app from Playstore. I did go to my original z8s and verify it WAS Play Protect certified. Maybe not a huge deal. I can still watch Netflix through the web.
Lastly, my motivation wasn't to get to Oreo necessarily. My issue was battery drain due to Android OS and System running all the time. This happened on my 'backup' preowned z8s that I just got out of the box. Google searches pointed toward 'clear system cache' from bootloader to solve this. I couldn't make that happen with z8s. My understanding is it's locked. Soooo... I hoped that flashing to Oreo would also clear the system cache. It did (yay!). Battery usage is back to normal. Note that I did check the box to erase data in the Asus flash tool.
thanks again!

Update. It seems this was not so successful. To be clear, I do have Oreo running. However, I have a few issues now that make the tablet much less useful:
- Can't load Netflix app. Can't watch through Chrome either.
- Spectrum TV app no longer works.
- Battery drain issue is back.
Oh well. Time to move on I guess. My time is worth something, so maybe I'll pony up and buy something else.

tblount70 said:
Update. It seems this was not so successful. To be clear, I do have Oreo running. However, I have a few issues now that make the tablet much less useful:
- Can't load Netflix app. Can't watch through Chrome either.
- Spectrum TV app no longer works.
- Battery drain issue is back.
Oh well. Time to move on I guess. My time is worth something, so maybe I'll pony up and buy something else.
Click to expand...
Click to collapse
Weird about the play protected issue. mine didn't run into that, but you could probably download the Netflix APK directly from one of the various APK mirror sites, I'v done this with various Android devices over the years.

If i have bricked it with update Magisk and direct install kernel how to repair? Only edl mode with Qualcomm HS-USB Diagnostics 900E ?

Thank you Sneaky.Ninja
I have updated the p00j tablet
but how
Extract from raw file
correct boot.img
(ZT582KL_all_VZW_user_V5.1.5 extracted 39.boot.img is not the correct file)

Could this be used to potentially port to the zen pad z10? I just got one for free I’d love to have a custom OS on this Bad boy! Lol my buddy has six in a stack he got from a school they are workable but it would be nice to make them up to date ect. What an awesome find!! I was thinking about taking the url you had and using the 500kl sku would that work do you think to see if there’s maybe a hidden Oreo for us?