Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Not to hijack your thread, so consider this a free bump, but I am also curious. Galaxy S7 G920T here and looking for the same options.
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Sent from my Redmi 2 using Tapatalk
fake2die said:
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Click to expand...
Click to collapse
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
veez21 said:
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
Click to expand...
Click to collapse
Right! So you can accomplish a Magisk install without a custom recovery for example using the Magisk Manager or Flashfire but as stated above, in order to boot a modified boot.img the bootloader needs to be unlocked or otherwise it will refuse to boot it.
There should be an option to install magisc like a systeme update with the stock recovery.
Gesendet von meinem XT1650 mit Tapatalk
JRapsky said:
There should be an option to install magisc like a systeme update with the stock recovery.
Click to expand...
Click to collapse
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Sytis said:
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Click to expand...
Click to collapse
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
COOLPLAY6FAN said:
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
Click to expand...
Click to collapse
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Actually you can boot into twrp rather than install/flash twrp which means u must use cmd to boot twrp everytime for flashing something~ As for locked bootloader, just like others said, you must unlock it.
Didgeridoohan said:
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
Click to expand...
Click to collapse
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
COOLPLAY6FAN said:
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
Click to expand...
Click to collapse
There are installation instructions on how to create the patched boot image with the Magisk Manager in the release thread.
When you have the patched_boot.img file, you'll need to flash it to your device. On most normal devices you can do this with fastboot. Check out your device's forums/DuckDuckGo/Google/Whatever-search-engine-you-use for instructions on that.
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
* Unlocked bootloader is needed. Period.
* A custom recovery is needed to flash Magisk. TWRP for instance.
* That custom recovery prevent the built-in OTA update to work
* But TWRP can flash OTA updates that can be downloader from XDA for example
Am I correct?
Also,
* Magisk needs a patched boot image
* This image has no impact on the OTA process at all
* There are encryption matters to take care of (I don't understand them yet though).
Is everything correct?
Thanks.
Krystanos said:
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
Click to expand...
Click to collapse
Let's see about answering those statements/questions.
* Unlocked bootloader is needed. Period.
Click to expand...
Click to collapse
Yes.
* A custom recovery is needed to flash Magisk. TWRP for instance.
Click to expand...
Click to collapse
Not necessarily. You can let the Magisk Manager patch your device's stock boot image and then flash it to your device with fastboot. See the installation instructions in the release thread.
* That custom recovery prevent the built-in OTA update to work
Click to expand...
Click to collapse
Yes.
* But TWRP can flash OTA updates that can be downloader from XDA for example
Click to expand...
Click to collapse
No. And yes. Official OTA files can (most of the time) not be flashed in TWRP. ROM zips and flashable firmware packages can.
* Magisk needs a patched boot image
Click to expand...
Click to collapse
Yes, that's all Magisk is about.
* This image has no impact on the OTA process at all
Click to expand...
Click to collapse
It definitely does. See the official docs
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips for more info on how to keep OTA capabilities for your device.
* There are encryption matters to take care of (I don't understand them yet though).
Click to expand...
Click to collapse
Possibly. Depends on what you're talking about.
Great answers. It's more clear for me now. Many thanks sir!
JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Hi!
There are good news for you, rooting with magisk is very easy that way . No bootloader unlocking, custom recovery,
adb and fastboot command, no sdk no mtk tool . NOTHING but Sp flashtool - our best friend. This method really works with mtk phones android 5.0+ .
What U only need is
Sp flashtool and its drivers /scatter file with the ROM/ -I think not mtk devices with their own flashtool will work too
the ROM of your device
Magisc manager app on the phone
First of all you need clear up the device / after backup somewhere if needed/with sp flashtool - flash the whole ROM in format+download mode.
Install Magisc manager app , it will load for U a zip file in the map of the app
Put the boot img file of your rom in that map too
Run install option - it will create a patched boot img file within the app s map
Run again sp flashtool with download mode , mark only the boot section , and flash that patched boot img in phone
After reboot phone it is rooted
best regards
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
lefteriskmail said:
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
Click to expand...
Click to collapse
Install Magisk Manager.
Press install.
Select "Patch Boot Image File".
Select the stock boot image you've previously saved on your device.
Wait.
Flash the patched boot image to your device.
Done.
All of this is covered in the installation instructions...
The folder being mentioned above is MagiskManager on your internal storage (where the patched boot image is also stored).
Magisc
Hi!
Magisc works fine for me from the first time. Excuse me I won't do installation again to see how it goes. Really it causes some hesitation but in the end it's clear.
I use Total commander, and magisc folder is on the external SD card after installing magisc manager app. Factory reset later will not clear the root. After installing manager it says "not installed" till the end of the rooting process. Opening the app it begins to look after the downloadable zip file, you have to wait and download it. This zip and the stock boot img must be in the same place in a folder, and the app itself makes the patched boot img but I don't remember what was the name of the option. This is the flashable img file. In the end after flashing with flashtool and rebooting, magisc manager says "installed". Good luck
Hi, I am trying to centralise this sort of information and am compiling it in another topic for Magisk and android-based media centres too.
Trying to properly document things (full sentences with references, links, and examples) rather than just writing some brief summarised steps that most people will not understand - not just for myself but to share should it assist others learn and understand the preparation and steps involved, plus consequences and ramifications of their actions (which never seem to be stressed enough).
Here is what I have compiled. Hopefully it will help and prevent you going loopy!? :silly:
- - - - - - - - - - - - - - - - - - - -
*** EXTREMELY CLEAR MAGISK ROOT INSTRUCTIONS ***
(Work In Progress! To Be Verified & Critiqued By Others)
Connect your WiFi so that all auxillary files can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free disk space. Allow for 1-2 hours to perform these steps. Do not rush!
Bootloaders come with every Android device, and give it all the instructions on how to boot and what to execute. If your Bootloader is locked, then you have not flashed anything like TWRP previously, or, you have re-flashed a stock Bootloader and Recovery, etc. The process is much easier when you have previously rooted the device using another method, and the Bootloader already unlocked.
To preserve your System partition, Magisk only modifies the unlocked Bootloader boot partition, which can easily* be restored and 'locked' later.
0. Before starting anything, always perform a FULL Backup (ADB) of your device, using a good quality USB cable and ADB FastBoot toolkit. Or on some devices you can use a Micro SD card with a TWRP recovery.img to boot into TWRP to perform a backup of partitions. Do both if you want! Make sure you search for the appropriate commands and usage of ADB FastBoot backup so that all data is backed up and included.
> ADB FastBoot: https://developer.android.com/studio/releases/platform-tools.html
> TWRP: https://dl.twrp.me/twrpapp/ \\ https://twrp.me/FAQ/
> Plus various other solutions...
1. Identify your device's firmware, build number, Bootloader, full unique model number, etc. Download any two of these apps:
a) AIDA64 ("System", "CPU" & "Android" tabs.)
b) Device Info HW ("General" & "System" tabs.)
c) DevCheck ("Hardware" & "System" tabs.)
2. Download the stock Bootloader, Recovery and Firmware (___.tar.md5) for your device model, variant and OS. (e.g. match your firmware, build number, bootloader, full unique module number, etc). Some sites will force you to pay to download - search around and you can get free download links, or sometimes from the manufacturer's site. From this firmware, we need to either extract or download the stock Bootloader.img image separately.
3. Install Magisk Manager v5.3-v5.6 as of 2017.02.22 ("Magisc" is typo by guy above).
4. Open Magisk and go to settings, adjust theme, change the language, enable notify for updates, change prompt timeout, etc.
5. On the home screen of the Magisk Manager app, click "Install" then in the pop-up select "Install" again.
a) If you have root access already, choose "Direct Method" - Select, wait, reboot and done (very easy!);
b) If you have stock recovery & locked bootloader, choose "Patch Boot Image File" - in the pop-up explorer, browse for the downloaded Bootloader Image.
c) ... I don't know about "Download ZIP Only" - I assume for flashing with Odin or ADB FastBoot from PC or existing root/unlocked user....?
NOTE: If you are being asked to browse and select a file, be aware that there is no confirmation! As soon as you click, that JPG or RAR archive will be used for patching (and result in an error if cannot be extracted!!!)
6. A file will likely be downloaded in the background (flashable ZIP), a black screen will pop-up processing etc. Wait.....
The processed Boot image will be processed and output to the /MagiskManager/ directory.
If you do NOT have root, or custom recovery, you will need to:
a) grab a PC, install the USB drivers for your device and confirm your device is fully recognised
b) then flash the "patched" Boot image from the Magisk Manager directory with ODIN for Windows or FastBoot on Windows via a good-quality USB cable.
7. ...
8. ...
I think that is it... I may have forgotten something. Please advise if something needs to be fixed or corrected. My Media Centre was already unlocked, so I did not have to unlock and flash the Bootloader.
9. Install free TWRP on your device, and choose to backup any partitions, should you wish to restore them later. Set an alarm to backup your device every few months! What are you prepared to lose if your device was lost/squashed/washed/crunched et al.???
Say thank you and donate to the amazing and all powerful Magisk developer 'TopJohnWu' and team!
Sweet! :fingers-crossed:
Related
TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root
I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, rooted with CF-auto-root, now has SuperSU installed, pure stock rom.
And I am wondering whether it will be possible to install Magisk (even if I have to uninstall SuperSU) without TWRP or any other custom recovery?
Will it also be possible to have full disk encryption (to be honest I don’t know whether my device is currently encrypted - is there a way to check this)?
orifori said:
I have a Samsung Galaxy S7 edge, international version, Android 6, unlocked bootloader, rooted with CF-auto-root, now has SuperSU installed, pure stock rom.
And I am wondering whether it will be possible to install Magisk (even if I have to uninstall SuperSU) without TWRP or any other custom recovery?
Will it also be possible to have full disk encryption (to be honest I don’t know whether my device is currently encrypted - is there a way to check this)?
Click to expand...
Click to collapse
Yes it is possible... Check the magisk release thread for the method applicable for you... About encryption, it works just fine...
Edit: here https://forum.xda-developers.com/showthread.php?t=3473445
Sent from my MI 5 using Tapatalk
Thank you! I need some help regarding the Installation Instructions.
The stock rom I have (which is to be patched by Magisk Manager) is a ZIP file with 5 .tar.md5 files in it...
1 - Where should I copy it - internal phone memory?
2 - Should I copy the ZIP file or the 5 files in it?
3 - Magisk Manager asks for .RAR or .IMG file while I have a .ZIP - should I simply rename the .ZIP to .RAR or...?
4 - Installing CSC_... would do a wipe while HOME_CSC_... would not - and I definitely do not want a wipe - so how to proceed?
5 - If I want full device encryption I just tick Preserve force encryption option (I don't know whether the phone is now encrypted)?
orifori said:
Thank you! I need some help regarding the Installation Instructions.
The stock rom I have (which is to be patched by Magisk Manager) is a ZIP file with 5 .tar.md5 files in it...
1 - Where should I copy it - internal phone memory?
2 - Should I copy the ZIP file or the 5 files in it?
3 - Magisk Manager asks for .RAR or .IMG file while I have a .ZIP - should I simply rename the .ZIP to .RAR or...?
4 - Installing CSC_... would do a wipe while HOME_CSC_... would not - and I definitely do not want a wipe - so how to proceed?
5 - If I want full device encryption I just tick Preserve force encryption option (I don't know whether the phone is now encrypted)?
Click to expand...
Click to collapse
You need to patch and flash the boot image only. That'll be inside the ROM zip. Don't forget to change the output format in the Manager settings to .img.tar.
It usually says under Android settings -> Security if your device is encrypted or not. But I've no idea if Samsung do that. I don't do Samsung.
This has been discussed a few times in the Magisk forums already, so if you search you'll be able to find more info on it. Always do your homework before flashing...
Examples of threads to search and/or read trough:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382
https://forum.xda-developers.com/apps/magisk/magisk-discussion-thread-t3467229
https://forum.xda-developers.com/apps/magisk/flashing-patched-boot-img-odin-t3670503
Worked like a charm, thank you! Extracted AP_... file from the zip archive, them extracted boot.img file from AP_... file and copied it onto the SD card of the phone, then Magisk modified it, I copied it to my laptop and flashed it in Odin (AP field).
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
orifori said:
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
Click to expand...
Click to collapse
In order to be able to take an ota, you need stock recovery, with unmodified system, and probably stock boot... (Magisk only touched the boot.img, so you just need to restore that)...
Sent from my MI 5 using Tapatalk
orifori said:
Everything works fine, except OTA updates - I try to download updates manually (About device -> Download updates manually) but I get a message "The operating system on your device has been modified in an unauthorized way."
So are OTA updates possible 1. without TWRP and 2. with preserved encryption - like in my case - and how is that possible? Maybe Magisk settings?
Click to expand...
Click to collapse
You can't update with OTA if you've modified /system or the boot image (Magisk). A custom recovery would also cause it to fail, but that's not an issue for you...
Since you've got a Samsung there are probably more checks as well (unlocked bootloader and such).
You might have to flash updates manually... Best place for answers would be your device's forum.
Didgeridoohan said:
You can't update with OTA if you've modified /system or the boot image (Magisk)
Click to expand...
Click to collapse
So there is absolutely no chance for OTA updates in case of installed Magisk? I have a pure stock rom and the only thing modified is the boot.img file (modified by Magisk in order to gain root).
orifori said:
So there is absolutely no chance for OTA updates in case of installed Magisk? I have a pure stock rom and the only thing modified is the boot.img file (modified by Magisk in order to gain root).
Click to expand...
Click to collapse
You could restore the stock boot image to get the OTA and then re-root.
Don't know if Samsung updates care about KNOX (which will be triggered). I don't think they do, but I don't do Samsung so I can't say for sure...
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware ?
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
???? Please help
Loku_kika said:
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware [emoji116]
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
[emoji120][emoji120][emoji120][emoji120] Please help
Click to expand...
Click to collapse
Try 7zip...
You have to have an unlocked bootloader and a working fastboot in order to root without custom recovery...
Sent from my MI 5 using Tapatalk
Loku_kika said:
I am trying to root my phone using magisk. I do not have any custom recovery. I was told that I can still root it by patching my stock boot image. But I couldn't find it anywhere. I do have my phone's stock firmware, and if I'm not wrong it Should be inside it, but the problem is that, the firmware file is in .nb0 format. I do not know how to open it and get access to the boot.img, can someone please help me.
My phone is Infocus m535
This is the firmware
mediafire.com/file/y2zru5gda08jder/Infocus_M535_G40-026P-0-00WW-A02.zip
Please help
Click to expand...
Click to collapse
For future references: Samsungs firmware files can be compressed with their LZ4 format and thus needs to be uncompressed again in the case of a boot.img.lz4 file so that you have boot.img file which magisk then can properly use. Otherwise you might get an error sating something like: unable repack boot image, when trying to patch the boot image with Magisk.
guys i have flash magisk patched image without custom recovery and via fastboot but now I am always boot to recovery.. Phone doesnt start at all.
In focus m535 magisk
OK bro I try it
Sorry
Hi, I try do to same thing on my S7 but with a Oreo 8.0 Android version.
Perhaps it's change something.
And each time I reboot after flash a boot.img patched or even patch TWRP, my phone don't boot and ask me to reset it (in French it write reinistialisation in an tactile screen).
If I reload with Odin a BL, AP ect... my phone restart and I didn't lose any data. But it is no root.
Could you help me please ?
Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
jdsmn21 said:
Sorry if this seems like a dumb question - I'm a little green on the phone modding (last phone was a S3, rooted with oneclickroot I think) I have a bootloader unlockable XT1775 owens (bought from retail, no carrier lock) that I have been planning to bootloader unlock and root with TWRP & Magisk. I just got a notification that update "NPR26-58-45" is available. I downloaded it, but haven't installed yet - for fear that it might affect what I want to do for root.
What should I do? ie: - install it, and go forward with the root process? Root first, and then install?
Click to expand...
Click to collapse
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
You do not want to root first. Update then root as doing an ota while rooted may loose your root status or worse!
Goose03 said:
Do NOT root first!
Edit: do me a favor and upload a system backup after you update, root and install twrp (if you do anyway), so I can make a twrp flashable ROM.
Edit-2: actually, if you could backup system before rooting or anything, that would be better.
Click to expand...
Click to collapse
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
jdsmn21 said:
Thanks Goose. I will gladly upload that, but I will have to get back to you after the weekend - I apologize, heading out of town after work.
To clarify on the process, I would go through the step to unlock the bootloader (using the code I will get from Moto website and "fastboot oem unlock CODE"). After that is the TWRP step, right? If so, which command do I use: "fastboot boot recovery.img" or "fastboot flash recovery recovery.img" ??
Click to expand...
Click to collapse
Np. Take your time. Thanks. Yes, that is what you do to unlock. Then for flashing twrp it's like you have but make sure to match the last part "recovery.img" to whatever the recovery is named. If your recovery is named twrp.img the command is:
fastboot flash recovery twrp.img
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
jdsmn21 said:
That's the one I had been following! I found that very helpful - that would make a good sticky post for guys like myself.
Since I have your attention too, I'd like to ask - is dmnoverity and phh's SU not needed at all? The only three files copied to the SD card (and then installed) are TWRP, Magisk zip, and Magiskmanager APK?
Click to expand...
Click to collapse
Phh SU is not needed since Magisk gives you all the necessary root and features. dmnoverity is not needed. I recommend you allow twrp system write access.
koop1955 said:
If it helps, I posted a step-by-step guide to unlocking, installing TWRP and rooting here: https://forum.xda-developers.com/moto-e4-plus/help/step-step-how-to-root-moto-e4-plus-t3752334
Click to expand...
Click to collapse
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
jdsmn21 said:
Well, I followed your instructions....with a minor tweak - and I'm having problems.
I unlocked the bootloader a couple days ago, but couldn't download the TWRP.bin file, so I used my phone through today. Formatted a 64gb card and loaded the magisk zip and apk on it. Flashed the TWRP on the phone, and used the wipe function to wipe data, cache, and dalvik, and then made a backup to my sd card. Flashed the magisk.zip, and then hit reboot "system". Now it just reboots to TWRP. I can reboot to bootloader, but hitting "start" goes to TWRP again.
What do I do? Where did I go wrong?
Click to expand...
Click to collapse
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
Try fastboot oem fb_mode_clear
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
jdsmn21 said:
Thank you. I tried the command, and it said OK, but it still boots to TWRP; i then reboot to bootloader, and select Start and it goes into the normal system. Is that how it is supposed to work?
Last night I was stuck in a TWRP loop, but i got it to go with formatting data and factory reset wipe in TWRP. After finally getting the system to boot, I installed the Magisk Manager and then Adaway. Now today I was playing with the Chase Pay app, which won't let me sign in due to being rooted. I then reverted my hosts file and uninstalled Adaway, and played with all the hide options in Magisk., to no avail. Root Checker app says that Safetynet is tripped.
Does Magisk effectively work for apps that look at Safetynet on this phone - apps like Chase Pay?
Click to expand...
Click to collapse
It is not normal to have it boot straight to twrp or the bootloader rather than the rom unless you do so manually.
Have you triedbplaying with the settings in Magisk Manager? There is an option to hide Magisk from your choice of apps. There is also a couple other options in the settings to hide things as much as possible. If you have Xposed installed it won't pass a safteynet check.
Sent from my Moto E (4) Plus using XDA Labs
XT1775 rom's is possible install on XT1776 ?
almao11 said:
XT1775 rom's is possible install on XT1776 ?
Click to expand...
Click to collapse
You could. I've flashed xt1775 firmware to my xt1776 to get a backup of the system to make a twrp flashable from. I don't recommend it, but if you only flash the system and not the modem and oem it should provision data services. Why do you ask exactly?
Sent from my Moto E (4) Plus using XDA Labs
$50 available via the crypto currency of YOUR choice.
Request: root. Tethered root is ok. Magisk systemless safteynet passing persistent root via zip flashing using persistent twrp is preferred, naturally.
This phone is AMAZING. Also the one sold from motorola.com is bootloader unlockable. The Amazon one is not.
To verify: if you got your z3 play from carrier or Amazon it is not bootloader unlockable.
If you bought from Motorola.com it is bootloader unlockable.
Battery without Moto mod is the best I have ever seen. Screen is amazing. Microsd slot, this is a really good feature. This is what my s9 plus should have been. No bloatware. I only want root for systemwide adblocking. (Adguard systemstore certificate)
With the Moto battery mod you can't run out of battery in a day. It's the best. Hopefully we will get unofficial custom rom someday so I can use Xposed and microg. You would be surprised how much telemetry even "stock like" roms have.
tomkleeeb said:
$50 available via the crypto currency of YOUR choice.
Request: root. Tethered root is ok. Magisk systemless safteynet passing persistent root via zip flashing using persistent twrp is preferred, naturally.
Click to expand...
Click to collapse
An attempt was already made. Using the firmware image someone linked here, I attempted to build and flash a TWRP for the Z3 Play I bought from Best Buy.
The result was a hard brick. Device would no longer power on. (Never seen this before, so it was definitely worth documenting for the TWRP chat)
Got a replacement Z3 Play, rebuilt TWRP but booted the firmware. Hard hang. Tried booting just the boot.img from the firmware image... also a hard hang.
So the software that we have now is not compatible with the Z3 Play.
Root and TWRP will come easily once we have an official image for the phone. It's unlocked, that's usually the hard part. Just gotta wait for Motorola to release the files or source first.
twelfth said:
An attempt was already made. Using the firmware image someone linked here, I attempted to build and flash a TWRP for the Z3 Play I bought from Best Buy.
The result was a hard brick. Device would no longer power on. (Never seen this before, so it was definitely worth documenting for the TWRP chat)
Got a replacement Z3 Play, rebuilt TWRP but booted the firmware. Hard hang. Tried booting just the boot.img from the firmware image... also a hard hang.
So the software that we have now is not compatible with the Z3 Play.
Root and TWRP will come easily once we have an official image for the phone. It's unlocked, that's usually the hard part. Just gotta wait for Motorola to release the files or source first.
Click to expand...
Click to collapse
Can you dump boot.img from the same devise, then fastboot boot boot.img?
If that works...
Could you then use magisk to add systemlessly root to the boot image
Then fastboot boot patched boot.img for tethered root?
This thread shows dumping partitions
https://forum.xda-developers.com/showthread.php?t=2450045
tomkleeeb said:
Can you dump boot.img from the same devise, then fastboot boot boot.img?
Click to expand...
Click to collapse
Not without root.
tomkleeeb said:
This thread shows dumping partitions
https://forum.xda-developers.com/showthread.php?t=2450045
Click to expand...
Click to collapse
Also from that thread:
TheThread said:
Pr-requirement:
- Rooted device.
Click to expand...
Click to collapse
You need root to get boot.img from a device to build TWRP.
or.
You need firmware images to be released by Motorola to build TWRP with the boot.img they release.
or.
You need source.
No way around it.
twelfth said:
You need source.
No way around it.
Click to expand...
Click to collapse
I made a thread on their official forums. https://forums.lenovo.com/t5/Moto-Z...this-phone-D/m-p/4176309/highlight/false#M200
This may seed things along.
if you boot into bootloader and run fastboot getvar all you'll see that our firmware is based on LA.UM.6.2.r1-07200-sdm660.0
so this should be our (incomplete) kernel source
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tag/?h=LA.UM.6.2.r1-07200-sdm660.0
search for LA.UM.6.2.r1 on https://wiki.codeaurora.org/xwiki/bin/QAEP/release and you'll see all the updates we're missing since march
frantisheq said:
if you boot into bootloader and run fastboot getvar all you'll see that our firmware is based on LA.UM.6.2.r1-07200-sdm660.0
so this should be our (incomplete) kernel source
https://source.codeaurora.org/quic/la/kernel/msm-4.4/tag/?h=LA.UM.6.2.r1-07200-sdm660.0
search for LA.UM.6.2.r1 on https://wiki.codeaurora.org/xwiki/bin/QAEP/release and you'll see all the updates we're missing since march
Click to expand...
Click to collapse
I posted on GitHub asking for source.
Anyone wanna bump it?
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165
i have patched boot.img for 1929-8 using magisk manager apk from magisk 16.7.
not tested, i have locked bootloader.
if you have unlocked bootloader you can try "fastboot boot patched_boot.img" first without flash to see if it even boots. if it does you can try to flash it, extract magisk 16.7 zip and install apk from common folder.
https://drive.google.com/open?id=1n7Wf8ekChsDIUFmya0yFIRFQ581EIQxZ
if you brick your device you're on your own.
also i have sent boot.img to TWRP Builder, hopefully guys there can make a port from it.
frantisheq said:
i have patched boot.img for 1929-8 using magisk manager apk from magisk 16.7.
not tested, i have locked bootloader.
if you have unlocked bootloader you can try "fastboot boot patched_boot.img" first without flash to see if it even boots. if it does you can try to flash it, extract magisk 16.7 zip and install apk from common folder.
https://drive.google.com/open?id=1n7Wf8ekChsDIUFmya0yFIRFQ581EIQxZ
if you brick your device you're on your own.
also i have sent boot.img to TWRP Builder, hopefully guys there can make a port from it.
Click to expand...
Click to collapse
I have 1929-4 and unlocked the bootloader, tried it all, it's useless. (I used the boot of course from my version) Also I tried to port twrp but beyond the splash screen with the inscription twrp it did not work, and my knowledge in programming is almost equal to 0.
thought so. stock boot.img should boot with locked bootloader and it didn't.
ok i'll try to capture OTA url when it's available.
And yet I managed to get the root of the right through the magic and actually boot it. It was necessary in the magic to choose options for patch boot as far as I remember with encryption related, and it worked out))
frantisheq said:
thought so. stock boot.img should boot with locked bootloader and it didn't.
ok i'll try to capture OTA url when it's available.
Click to expand...
Click to collapse
Moto asked what version I need.... What version do we need to build root? https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165
this looks looks like a bad joke. we don't even need to ask them, there's GPL
frantisheq said:
this looks looks like a bad joke. we don't even need to ask them, there's GPL
Click to expand...
Click to collapse
I don't know. I just want root.
I think they can get away with it because source is available upon request, but no one requests it. I am surprised their GitHub doesn't have 1000s of people clamoring for source code for root. This thing is on my short list of phones. Op6/6T would be my next choice but I like microsd more than I like root friendly warrenty.
tomkleeeb said:
I don't know. I just want root.
I think they can get away with it because source is available upon request, but no one requests it. I am surprised their GitHub doesn't have 1000s of people clamoring for source code for root. This thing is on my short list of phones. Op6/6T would be my next choice but I like microsd more than I like root friendly warrenty.
Click to expand...
Click to collapse
Try to boot from my boot (fastboot boot root.boot.img) and if the system boots,you will see in the manager of magics that you already have the root rights, then you can safely flash this boot to yourself (fastboot flash boot root.boot.img) and it will be your root. But twrp recovery I can not yet port unfortunately.(And of course you need to have a bootloader unlocked)
https://drive.google.com/file/d/1wwD4J3DN4sYqfD1hOe0uApHC9tgqKIfu/view?usp=drivesdk
Willy33 said:
Try to boot from my boot (fastboot boot root.boot.img) and if the system boots,you will see in the manager of magics that you already have the root rights, then you can safely flash this boot to yourself (fastboot flash boot root.boot.img) and it will be your root. But twrp recovery I can not yet port unfortunately.(And of course you need to have a bootloader unlocked)
https://drive.google.com/file/d/1wwD4J3DN4sYqfD1hOe0uApHC9tgqKIfu/view?usp=drivesdk
Click to expand...
Click to collapse
Have to buy the phone first lol.
No root = no buy
I just like the idea of the ga!epad controller mod $79.99
Android has no good game controller
kernel source should be released by tuesday
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/165#issuecomment-415027775
i have paid to download firmware for XT1929-8 and unlocked the bootloader.
the bad news, boot.img patched with Magisk won't boot, it just reboots.
the good news, stock boot.img worked so my phone works.
the best news, treble ResurrectionRemix system img for ARM64 a/b with gapps and su just booted up
https://forum.xda-developers.com/pr...pment/gsi-resurrection-remix-o-6-1-0-t3811299
i'm going to try pixel experience later
EDIT: sound works, dual sim works, wifi works, fingerprint works, navigation bar needs to be enabled in settings, battery moto mod seems to be not charging, unable to change display brightness
pixel experience won't boot (maybe it will, it's because i have downloaded a version instead of a/b). i'm back to stock ROM
EDIT2: got root working.
not sure if it's needed but i have used Magisk Manager from https://raw.githubusercontent.com/ianmacd/MagiskBuilds/master/updates/ianmacd.json
installed the apk
set up that URL as custom Update Channel in Magisk manager settings
patched boot.img with "Preserve force encryption" and "Preserve AVB2.0/dm-verity" checked
patched boot.img for xt1929-8 can be downloaded here https://drive.google.com/open?id=11CJ65ojDZmCQVZGSHXicfFSMaenFHiiv
now where is that $50? my donation button still works
EDIT3: got boot.img with working TWRP, but it won't boot Android just TWRP.
if you'd like to try fastboot flash boot_a recovery.img and choose recovery in bootloader menu.
be sure to have boot.img backup before flashing because it won't boot Android and TWRP is unusable as it is, it can't even mount data.
https://drive.google.com/open?id=1C3lcyK3y4RL1Ep56wqWpfw0VWIHuhiO0
Absolutely all the same thing I did with my 1929-4 three days ago ... with twrp the same situation unfortunately ...
i was able to flash magisk and boot.img so it works. still don't know why it won't boot android.
device/motorola/beckham - https://drive.google.com/open?id=1KQ8KFthPJzr1VXt41F9N7O7fY8IRzcb6
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.