I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
itscryptic said:
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
Click to expand...
Click to collapse
If you originally patched the Samsung firmware and rooted under OneUI, that same version of Magisk will show up once you flash any GSIs.
Besides that, there's no other way that I know of since you can't simply sideload Magisk through TWRP for this device
You'll have to start over by patching the firmware and flashing through Odin to get back to stock. From there, set up Magisk like you'd normally do. Once that's done, you can proceed and use the same guide to get LOS back and be fully rooted with Magisk
itscryptic said:
I used this to install lineage and it worked out great – the tablet runs a lot better. But I have an app I'd like to use that requires root, and this unofficial version of lineage does not come with a boot.img to patch with magisk. Is there some other way to root this that I'm missing, or is it not possible?
Click to expand...
Click to collapse
You just need to install the magisk apk and run it. There is no need to patch anything.
lewmur said:
You just need to install the magisk apk and run it. There is no need to patch anything.
Click to expand...
Click to collapse
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
itscryptic said:
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
Click to expand...
Click to collapse
Simply installing the Magisk APK is not the same. To install Magisk completely to your system you must patch the image.
For this device, you need to complete the patching process first with Samsung's firmware under OneUI. Once that's done, you can return back to LOS and a patched version of Magisk will be waiting for you to install
itscryptic said:
I have the magisk apk installed, but not sure what you mean by run it. I open it and it shows N/A for installed.
Click to expand...
Click to collapse
Yes, but with stock, your only option is to patch a file. But with LOS you also have the option to install direct. Choose that and it will root.
lewmur said:
Yes, but with stock, your only option is to patch a file. But with LOS you also have the option to install direct. Choose that and it will root.
Click to expand...
Click to collapse
I didn't root initially when installing LOS. So it appears I need to restart the process, which isn't that big of a deal. But I don't know how to get back to stock to perform the patch. It's been almost a year since I originally installed LOS so I'm a little rusty with how everything works again
itscryptic said:
I didn't root initially when installing LOS. So it appears I need to restart the process, which isn't that big of a deal. But I don't know how to get back to stock to perform the patch. It's been almost a year since I originally installed LOS so I'm a little rusty with how everything works again
Click to expand...
Click to collapse
Again!!!! There is no need for that. LOS has replaced stock. Just do as I said, run Magisk but instead of choosing a file, choose the DIRECT install option. LOS doesn't need to be patched and stock didn't need to be rooted before flashing LOS. I just happened that I did root stock first but that was just to test if it worked with the latest stock ROM. But there is no need to do it if you are going to flash a GSI.
lewmur said:
Again!!!! There is no need for that. LOS has replaced stock. Just do as I said, run Magisk but instead of choosing a file, choose the DIRECT install option. LOS doesn't need to be patched and stock didn't need to be rooted before flashing LOS. I just happened that I did root stock first but that was just to test if it worked with the latest stock ROM. But there is no need to do it if you are going to flash a GSI.
Click to expand...
Click to collapse
I do not see a direct option, it is only showing select a file to patch when I tap install...
itscryptic said:
I do not see a direct option, it is only showing select a file to patch when I tap install...
Click to expand...
Click to collapse
If you are only seeing "Select a file", something is wrong but it has nothing to do with needing to patch. Try uninstalling magisk and then flashing the apk with TWRP.
lewmur said:
If you are only seeing "Select a file", something is wrong but it has nothing to do with needing to patch. Try uninstalling magisk and then flashing the apk with TWRP.
Click to expand...
Click to collapse
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
itscryptic said:
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
Click to expand...
Click to collapse
That's normal. Ignore it.
itscryptic said:
That did the trick, thanks a bunch! I keep getting this message though, even after rebooting, and I'm not sure if it makes a difference since the root checker shows my device is rooted.
Click to expand...
Click to collapse
How did you flash the Magisk.apk with twrp?
gguman said:
How did you flash the Magisk.apk with twrp?
Click to expand...
Click to collapse
Use the "Install" button to flash as if it were a zip file.
lewmur said:
Use the "Install" button to flash as if it were a zip file.
Click to expand...
Click to collapse
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
gguman said:
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
Click to expand...
Click to collapse
So long as you know where it is, you should be able to browse to it. You might have to "Select storage" to switch between Internal and Micro SD. If it doesn't show, try renaming it from .apk to .zip.
gguman said:
I didn't find the apk file in the tablet when I push the Install button in the twrp... .Should the file be in a specific path?
Click to expand...
Click to collapse
You have to rename it as a ZIP, you cannot flash APK files
kevinco1 said:
You have to rename it as a ZIP, you cannot flash APK files
Click to expand...
Click to collapse
Not necessarily so. I've installed apk files in TWRP many times. It depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
lewmur said:
Not necessarily so. I've installed apk files in TWRP many times. I depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
Click to expand...
Click to collapse
Just curious, what other apps can you do this besides Magisk?
lewmur said:
Not necessarily so. I've installed apk files in TWRP many times. I depends upon the version of TWRP. Some will, some won't. Most later versions will. I have v 3.7.0_12.2 on mine and it installs the apk just fine.
Click to expand...
Click to collapse
Successfully installed apk:
0) stock firmware
1) install TWRP
2) Formated data
3) Wipe all data
4) adb push magisk.apk to /
5) Install apk from TWRP
6) reboot to fastboot
7) flash LOS20
Related
Just successfully installed Supersu 2.81 (2.81 because the guide I used said it's the most stable version) when my phone rebooted the playstore promted me to update Supersu so. being the clueless noob that I am I updated it. Now it keeps failing when it's trying to update binaries. I can still use supersu and still have root access though. It's just annoying seeing that message to update binaries.
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
fajner said:
I have the same problem, I've even tried flashing the SuperSU .zip manually using TWRP! It reboots my phone before it finishes the flashing process. Does anyone know how to update it?
Click to expand...
Click to collapse
I already fixed mine.
blitzball said:
I already fixed mine.
Click to expand...
Click to collapse
How did you fix it?
fajner said:
How did you fix it?
Click to expand...
Click to collapse
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
blitzball said:
Open Supersu, navigate to the settings, scroll down and do a full unroot. Your phone will reboot so make sure you activate twrp before your phone boots fully otherwise you'll have to reinstall twrp again via adb cause your phone will overwrite twrp after it boots.
Download Supersu 2.82 here (the one I have is the no additive version just root) and just flash it with twrp. Done. Easy.
https://forum.xda-developers.com/p9/development/root-supersu-2-81-emui-5-t3612258
Click to expand...
Click to collapse
Sorry for late reply, I've tried uninstalling supersu/unrooting but neither did work or help. I finally ended up rebranding my phone to AL10 and installing the Chinese Oreo rom which works great.
How to root any version of the OnePlus 7T Pro!
1. Make sure your bootloader is unlocked!
2. Once you're unlocked enter the following ADB commands to extract your current boot image (Your phone needs to be on)
adb shell dd if=/dev/block/bootdevice/by-name/boot_a of=/boot_a.img
adb pull /boot_a.img pathinyourpc
Click to expand...
Click to collapse
3. Download & install Magisk Manager on your phone
4. Put the boot_a.img file on your phone
5. Open the magisk manager app and click the "Advanced Settings" button, then enable "Prserve AVB 2.0/dm-verity & Preserve force encryption", then select the top "Install" button and select "Patch to boot image" and select the boot_a.img
6. Now magisk will create a magisk patched boot image file, put that on your computer
7. Now enter the following ADB command
adb reboot fastboot
fastboot --set-active=a
fastboot boot pathtomagiskpatched.img
Click to expand...
Click to collapse
8. Now you'll boot into the system, reopen the magisk app and click the top install button again and select "Direct install", then reboot
Congratulations you've now successfully rooted your phone!
EDIT: This guide is wrong.
Check these references for the proper guide to root. OP refuses to acknowledge it's wrong even when I pointed it out to him with proof.
https://forum.xda-developers.com/showpost.php?p=81023631&postcount=144
^^^
Mainly this one.
https://forum.xda-developers.com/showpost.php?p=81105485&postcount=171
https://forum.xda-developers.com/showpost.php?p=81106827&postcount=173
-----
Now I have something so do for the weekend, thanks
Just a question, have you tried Viper4Android (if your use it)?: Use 2.7.1.6 stable version.
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Dukynuky said:
hi,
tryed it out.. When i boot your patched image.. there is no install button in magisk. It tolds me that i am already on the newest version.
Second.. WLAN isnt working any more. Cant enable wlan. When i reboot with stock img. everything is fine.
Click to expand...
Click to collapse
Yes it says its installed thats correct but you need to install it again in the magisk app so it stays after restarting the phone. I don't know about WLAN tho
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
I can confirm I have successfully rooted using this method, and WIFI is working fine. Thank you very much, OP and everyone involved, no wits time to set up my device
Ah! Will do this immediately when I get home.
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
Click to expand...
Click to collapse
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Dukynuky said:
did you install modules ? try booting the patched boot image from here and then, uninstall the modules again...
Click to expand...
Click to collapse
please see my edited reply, i installed directry through viper4android app, no the module
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
got ist working.. layer 8 error.. didnt had the ota update installed.
Updated oxygen os.. then wifi is working. also used canary magisk files.. works perfekt.. thanks
Dukynuky said:
Can you turn on Wifi ?
When i turn it on. It is disabled at the end.
There are similar problems in the 7t forums. Seems a problem with the used magisk version for the boot image.. did you use the canary magisk files ?
and yes.. I know why i need to install. But the linked version of magisk says only.. uninstall..
Edit: i have a european version of the oneplus 7t pro .. and can you provide the original boot image.
Click to expand...
Click to collapse
my wifi works perfectly fine, I have the EU version too.
I attached screenshots of what to do with the installed, please select the direct install option and then reboot!
droidvark said:
Works like a charm!
Minor thing you may want to clarify (I know you know, but to prevent confusion for readers), you give a warning that this will wipe all data, but that is not exactly true. Unlocking the bootloader wipes all data, but that step is not part of your instructions. Just following your steps on an already unlocked phone does not wipe the phone.
Thanks to everyone who made this possible so soon!
Click to expand...
Click to collapse
I have a warning above the instructions already, I think you might have missed it
Lossyx said:
I tried magisk and now it loops to fastboot, does anyone know to recover from this? Does the msm tool for OP7T Pro?
edit: flashed the original boot img and boots fine, whever i try to boot magisk patched it bootlops because faulty drivers
to clear up, i tried installing viper4android driver directly from the app, so i guess theres residue left
Click to expand...
Click to collapse
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Lossyx said:
please see my edited reply, i installed directry through viper4android app, no the module
Click to expand...
Click to collapse
Use the module next time!
HolyChickenGuy said:
I have a warning above the instructions already, I think you might have missed it
Click to expand...
Click to collapse
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
droidvark said:
I'm not sure where the misunderstanding is coming from, I know that you give that warning. What I mean is that strictly speaking following your steps does not wipe the phone, unlocking the bootloader wipes the phone. But you don't have that step in your instructions. See what I mean? .
When I read your steps, I was like "wipes my phone how?" Maybe booting your image would wipe my phone or something? I'm glad it didn't .
I just thought for clarity's sake it would be good to make that clear in the steps that's all!
Click to expand...
Click to collapse
Oh sorry, yeah I rewrote it to make it clearer. Unlocking the bootloader will wipe your data
Sent from my HD1913 using Tapatalk
HolyChickenGuy said:
I also bootlooped as well, I tried to install liveboot and i guess that didnt work lol
anyways, I fixed my bootloop by booting the unpatched boot img and then doing a factory reset in the settings, after that you can just boot to the magisk boot img again!
Click to expand...
Click to collapse
Damn, you are my hero. Did a factory reset and followed the OP again, now everything is fine and I'm rooted. Thank you again.
edit: also, for safety precaution, disable automatic updates in Developer options
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Great, I'll check back in on this tomorrow and see how everyone is getting on before I try. Had a skim through here this morning before mine arrived and didn't see anything so set up as is.
Just got notified of the update.
Downloading the update now & will share the file in later post for you guys.
Uploaded the file to android file host.
Incremental update file:.
https://www.androidfilehost.com/?fid=4349826312261819958
Full update file:
https://www.androidfilehost.com/?fid=4349826312261819976
https://briw.me/10.3.3/OnePlus7ProOxygen_21.P.27_OTA_027_all_2005192132_076a8e3.zip
@red rocket, here is the full update for 10.3.3 hosted on my server (feel free to add to OP if you'd like):
OnePlus7ProOxygen_21.P.27_OTA_027_all_2005192132_076a8e3.zip
MD5
a63548 said:
@red rocket, here is the full update for 10.3.3 hosted on my server (feel free to add to OP if you'd like):
OnePlus7ProOxygen_21.P.27_OTA_027_all_2005192132_076a8e3.zip
MD5
Click to expand...
Click to collapse
Thanks I'm on my way to upload the file to my android file host account as well. Appreciate the quick upload
I'm not unable to get into settings now after updating through magisk. Weird. I did disable the magisk modules.
JDROIDS said:
I'm not unable to get into settings now after updating through magisk. Weird. I did disable the magisk modules.
Click to expand...
Click to collapse
Is this still an issue for you? I haven't taken it yet, and your comment froze me. Your signature says OP 5T..
It's been a while since the last OTA, so I ask to reconfirm. I need to:
1) Uninstall RICE in Magisk and other modules
2) Uninstall XXX or not? That thread stated long ago that the module can be left installed since it's not version-dependent.
3) Uninstall twrp a/b retention script
4) DOwnload full update using oxygen updater.
5) Install update using settings/local upgrade. DO NOT REBOOT
6) Install Magisk. DO NOT REBOOT
7) INstall TWRP a/b retention script in magisk. DO NOT REBOOT
8) Install Magisk to inactive slot. NOW REBOOT
Is that right?
Is this twrp flashable.
rowdy_83 said:
Is this twrp flashable.
Click to expand...
Click to collapse
Yes
liam_davenport said:
Yes
Click to expand...
Click to collapse
Why would we chose to flash it via twrp? Is it easier or faster or better? I ask to learn since all guides mention the use of the update app
Sent from my OnePlus7Pro using XDA Labs
nabril15 said:
Why would we chose to flash it via twrp? Is it easier or faster or better? I ask to learn since all guides mention the use of the update app
Click to expand...
Click to collapse
So you don't overwrite TWRP with the stock recovery, and reflash Magisk while in recovery.
AarSyl said:
So you don't overwrite TWRP with the stock recovery, and reflash Magisk while in recovery.
Click to expand...
Click to collapse
Got it. Or, use the update method that has a step where a twrp retention script is installed in Magisk. They both sound like similar methods
Sent from my OnePlus7Pro using XDA Labs
nabril15 said:
Got it. Or, use the update method that has a step where a twrp retention script is installed in Magisk. They both sound like similar methods
Click to expand...
Click to collapse
They are, but for the old-time root users (like myself), flashing from TWRP is the simplest way.
Mind you, I'm not old (32yrs), but I've been rooting since the HTC Evo, and flashing ROMs and updates from TWRP is the most straightforward method.
AarSyl said:
They are, but for the old-time root users (like myself), flashing from TWRP is the simplest way.
Mind you, I'm not old (32yrs), but I've been rooting since the HTC Evo, and flashing ROMs and updates from TWRP is the most straightforward method.
Click to expand...
Click to collapse
I totally understand. Easy is good. I've been flashing a long time as well, and this TWRP approach appeals to me.
What are the steps? Boot to twrp, flash update, reboot? And twrp and magisk will be kept? I assume that before flashing, I would need to remove all magisk modules - RICE, XXX, and whatever else is in there. No?
These update logs has been pretty lame lately. Shuffling same BS around.
AarSyl said:
They are, but for the old-time root users (like myself), flashing from TWRP is the simplest way.
Mind you, I'm not old (32yrs), but I've been rooting since the HTC Evo, and flashing ROMs and updates from TWRP is the most straightforward method.
Click to expand...
Click to collapse
Lol same here but IAM little older.i install through Twrp after format .so it's installed clean.
mholloway said:
Lol same here but IAM little older.i install through Twrp after format .so it's installed clean.
Click to expand...
Click to collapse
Can you kindly elaborate or expand, if you will, on the steps that you followed?
Sent from my OnePlus7Pro using XDA Labs
nabril15 said:
Can you kindly elaborate or expand, if you will, on the steps that you followed?
Sent from my OnePlus7Pro using XDA Labs
Click to expand...
Click to collapse
Same as flashing a rom. In TWRP went to wipe.choose format ,type yes it deleted everything..
Reboot recovery
Connect to computer
Click on your device ,then internal storage,then TWRP.
Copy this rom OOS10 and TWRP zip and magisk zip to TWRP file.
Install OOS10,then flash TWRP
Reboot to TWRP,flash OOS10 again,then TWRP
reboot recovery flashed OOS10 again and TWRP
then reboot system
Don't forget to flash TWRP right after flashing rom or you will have the stock recovery..
After set up boot TWRP and flash magisk.
Anyone facing battery drain issue after updating to 10.3.3? also i m facing slow charging issue
Anyone else or its just me?
Is this for Europe?
Psyscope said:
Is this for Europe?
Click to expand...
Click to collapse
10.0.6 is for eu but still not out
Rocket Powered Oneplus 7 Pro
here is the full update for 10.3.3 hosted on my server (feel free to add to OP if you'd like):
https://pan.daxiaamu.com/一加手机官方ROM/...en_21.P.27_OTA_027_all_2005192132_076a8e3.zip
I understand there is no TWRP recovery for Zenfone 8 yet, but according to other posts, their are other ways to root the phone, e.g. using Magisk boot image patch method.
I tried, but I'm not able to flash the boot image in fastboot. I'm able to boot to fastboot mode, but it's showing no device when I use "fastboot devices" with USB connection. If I enter recovery mode, "adb devices" is showing unauthorized.
I don't know how to proceed. Appreciate your help!
It's solved by plugging the USB cable to USB 2.0 port on the PC
Good to hear it worked out. I was going to suggest installing a driver when in fastboot mode.
How did you get the boot image btw? I've never tried for anything other than a Lineage OS device, for which all the files are easily accesible.
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?
DerSteppo said:
After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?
Click to expand...
Click to collapse
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
OK thanks for the information!
dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.
dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
Ah, thanks that did help. I didn't know the full firmware was available from the site.
yunyou said:
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.
Click to expand...
Click to collapse
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.
dohanin said:
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.
Click to expand...
Click to collapse
I found ota's solution. Download the "WW-30.11.51.67" firmware from the official website and move it to the main storage directory of the phone. Then the phone should detect the update file, but if the phone does not prompt, then try to restart the device. When the phone restarts and enters the system again, the system will detect the update, and there will be an update launcher notification in the notification bar!
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.
grootzy said:
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.
Click to expand...
Click to collapse
yes, it's showing L1 in Widevine CDM
dohanin said:
yes, it's showing L1 in Widevine CDM
Click to expand...
Click to collapse
Thanks, great news that ASUS are not being dicks with the bootloader unlocking.
For anyone else who isn't too clear on the steps (like me!) - After patching the boot image with magisk you then can use adb to pull that image to a PC and then use adb reboot bootloader and then fastboot boot patched-image.img to check the rooting works without flashing anything and then use adb reboot bootloader again and then fastboot flash boot patched-image.img to write it to the flash memory if everything went smoothly. This worked for me and everything seems great. Obviously you need adb and fastboot set up on your PC for this to work. I'm not sure if this was the intended method but it is what I did.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know
fatjoez said:
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know
Click to expand...
Click to collapse
hi, yes i tried but while most apps are working fine, some banking apps can still detect root. however, for those apps, if i disable the magisk app beforehand, then it can be passed. i could not figure why since the magisk app is already with a random package name. i posted my query in the magisk forum too.
anyway, with this method, i don't need to use work profile now.
Hi everbody.
I hope someone can help me out.
I unlocked my Zenfone 8 with the official unlock tool and i want to relock the bootloader back.
I was using commands like fastboot oem asus-lock, fastboot flashing lock, but nothing works.
Did Asus changed something in Android 11?
In Android 10 the first command was working without problems.
Thanks
You can't lock it back.
Only to change motherboard.
dron39 said:
You can't lock it back.
Only to change motherboard.
Click to expand...
Click to collapse
Oh that's bad news. Thank you very much for your fast answer.
yunyou said:
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.
Click to expand...
Click to collapse
Can you explain further on this? Are you saying to install the firmware to an unused slot? What exactly is an unused slot? I haven't seen anything like this in magisk.
I'm running NE2215_11_C.26. Its rooted. I let the OTA updater do its thing but it just gives me a generic error message with no information about what is wrong. Is it because I'm rooted? Could it be a region problem since this is a North American device in India?
yes. read the proper root thread.
DiGtal said:
I'm running NE2215_11_C.26. Its rooted. I let the OTA updater do its thing but it just gives me a generic error message with no information about what is wrong. Is it because I'm rooted? Could it be a region problem since this is a North American device in India?
Click to expand...
Click to collapse
Easiest / Fastest way to solve this issue is to unroot fully through Magisk (disable all modules too), reboot. Take the update. Reroot with booting a patched boot image. That will always be the most fool proof way to update this phone, even cross region from my knowledge.
if you are rooted you don't have to update via OTA but you have to use localupdate.apk after disabling magisk modules and uninstalling images from magisk! operations: disable magisk modules and reboot/uninstall magisk image/oxygen updater download OTA to root directory/install localupdate.apk and update from there without reboot/done update open magisk and click install reboot after OTA!
morgan76 said:
if you are rooted you don't have to update via OTA but you have to use localupdate.apk after disabling magisk modules and uninstalling images from magisk! operations: disable magisk modules and reboot/uninstall magisk image/oxygen updater download OTA to root directory/install localupdate.apk and update from there without reboot/done update open magisk and click install reboot after OTA!
Click to expand...
Click to collapse
Android 12 Local update will allow you to update with no need to disable or unroot.
Just pull the update file to the pc, Payload it for the Boot.img and flash the Boot.img back though magisk.
Pull the flashed file back to the pc, do the local update and boot up fully.
ADB Boot the now flashed Boot.img Via the PC it and then direct install
FKX1997 said:
Android 12 Local update will allow you to update with no need to disable or unroot.
Just pull the update file to the pc, Payload it for the Boot.img and flash the Boot.img back though magisk.
Pull the flashed file back to the pc, do the local update and boot up fully.
ADB Boot the now flashed Boot.img Via the PC it and then direct install
Click to expand...
Click to collapse
not true for this model
g96818 said:
I literally did it 3 hours ago
Click to expand...
Click to collapse
@FKX1997 Prove it. C30 full rom doesn't exist for this model.
FKX1997 said:
Android 12 Local update will allow you to update with no need to disable or unroot.
Just pull the update file to the pc, Payload it for the Boot.img and flash the Boot.img back though magisk.
Pull the flashed file back to the pc, do the local update and boot up fully.
ADB Boot the now flashed Boot.img Via the PC it and then direct install
Click to expand...
Click to collapse
you can't extract boot.img from update you need full rom
morgan76 said:
you can't extract boot.img from update you need full rom
Click to expand...
Click to collapse
Local update is a full rom installation. OTA is a partial update
FKX1997 said:
Local update is a full rom installation. OTA is a partial update
Click to expand...
Click to collapse
Still waiting for you to prove the c30 full rom for this model exists.
g96818 said:
Still waiting for you to prove the c30 full rom for this model exists.
Click to expand...
Click to collapse
Considering you can install 2213 on 2215, that would be why
FKX1997 said:
Considering you can install 2213 on 2215, that would be why
Click to expand...
Click to collapse
Op never asked to change regions, so therefore you're a liar trying to confuse people. You should apologize to the op and hope he didn't brick his phone following your lie
g96818 said:
Op never asked to change regions, so therefore you're a liar trying to confuse people. You should apologize to the op and hope he didn't brick his phone following your lie
Click to expand...
Click to collapse
Dude, it just seems you have a problem. Pipe it please
FKX1997 said:
Dude, it just seems you have a problem. Pipe it please
Click to expand...
Click to collapse
You're the one that came in with an attitude, been proved wrong, now in denial, and trying to pass the blame.
Go figure for someone who shoots from the hip.
I have a patched boot.img that I used to root C.26. Will it work on this one too? What's the location of the boot.img on the phone? I could get that via file manager since I'm rooted. Does the android 12 localupdate work for android 13 as well?
What's the latest full OTA version? Does payload dumper still work? I'm going to try to get the stock boot image just in case.
DiGtal said:
I have a patched boot.img that I used to root C.26. Will it work on this one too? What's the location of the boot.img on the phone? I could get that via file manager since I'm rooted. Does the android 12 localupdate work for android 13 as well?
What's the latest full OTA version? Does payload dumper still work? I'm going to try to get the stock boot image just in case.
Click to expand...
Click to collapse
Best not to mismatch revisions. You can find a pre patched NE2115 C.30 in @g96818's thread. Otherwise you can make your own.
I personally pull them from the NE2213 full zips (since we don't get full releases at NE2215 anymore) and patch that via magisk, it works fine cross region as long as you ONLY boot it once for the magisk install. Never had any issues with this method.
How do I make my own boot.img? Does the payload dumper still work? The go version does not work with deltas. While I can use the easier methods I want to try making my own boot.img as a learning exercise.
DiGtal said:
How do I make my own boot.img? Does the payload dumper still work? The go version does not work with deltas. While I can use the easier methods I want to try making my own boot.img as a learning exercise.
Click to expand...
Click to collapse
I, personally, extract boot.img from NE2213 full Zip using FBE. This is the ONLY thing to use this tool for. Then transfer that to phone, disable all modules, unroot, reboot. Take the next OTA, reboot. Then go into Magisk, patch the new boot image you xfer'd earlier, copy that back to computer. Use ADB Fastboot to BOOT the image, and finally go into Magisk for a direct install. Reboot, and you're done.