How to install MAGISC without TWRP and locked bootloader?

[JRapsky]

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

 

[V1R4G3]

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.

 

[fake2die]

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

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

 

[veez21]

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..

Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.

 

[Sytis]

Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.

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.

 

[JRapsky]

There should be an option to install magisc like a systeme update with the stock recovery.

Gesendet von meinem XT1650 mit Tapatalk

 

[Sytis]

There should be an option to install magisc like a systeme update with the stock recovery.

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.

 

[COOLPLAY6FAN]

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.

but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?

 

[Didgeridoohan]

but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?

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).

 

[cutesniper22]

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

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.

 

[COOLPLAY6FAN]

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).

so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)

Thanks in advance

 

[Didgeridoohan]

so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)

Thanks in advance

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.

 

[Krystanos]

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.

 

[Didgeridoohan]

I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:

Let's see about answering those statements/questions.

* Unlocked bootloader is needed. Period.

Yes.

* A custom recovery is needed to flash Magisk. TWRP for instance.

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

Yes.

* But TWRP can flash OTA updates that can be downloader from XDA for example

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

Yes, that's all Magisk is about.

* This image has no impact on the OTA process at all

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).

Possibly. Depends on what you're talking about.

 

[Krystanos]

Great answers. It's more clear for me now. Many thanks sir!

 

[Galaxtracker]

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

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

 

[lefteriskmail]

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)

 

[Didgeridoohan]

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)

1. Install Magisk Manager.
2. Press install.
3. Select "Patch Boot Image File".
4. Select the stock boot image you've previously saved on your device.
5. Wait.
6. Flash the patched boot image to your device.
7. 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).

 

[Galaxtracker]

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

 

[flipmode_11]

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: