Related
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:
Hello,
I have Oneplus 3 A3000 running on OOS 4.0.1 (Android 7.0). I also have official OP3 twrp recovery version 3.0.3-0 installed and root was done using supersu free v2.82.. It also has dm verity prompt which comes up during boot time because it is oem unlocked.
I want to know exact procedure to go to complete stock rom + stock recovery along with links to download stock recovery and rom. I saw different versions of stock recovery for different OOS. I don't care about device data as everything is on cloud and nothing on is on device. App list also I can get from google account history. Only thing I care is not to corrupt any system partitions. I also saw few posts that go into boot loop if incorrectly unrooted. I would not want that either.
Your help is greatly appreciated. Virtual beer for you ???. I am software engineer so even though I am noob in terms of hacking my android, I can follow the instructions properly.
Thanks again.
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
reyscott said:
You can flash official OOS Rom and just use TWRP, you can try using the current recovery you have. Allow it to boot after if it allows you then do not go back to TWRP, allow it to boot to its system and then normally it will just override TWRP with OOS stock recovery.
Click to expand...
Click to collapse
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
mit2nil said:
What about unroot and oem lock and dm verity? do I need to do all that before doing OOS update? I am getting OOS 4.1.6 in system update.
Click to expand...
Click to collapse
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
reyscott said:
you sure you want to be locked again ? i doubt..
dm verity is not a big deal for me.. i allowed it.. im ok with but if you want to remove it siankatbg has a guide on how to remove it..
Click to expand...
Click to collapse
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
mit2nil said:
I actually want to go to systemless su + magisk + xposed later on. This one didn't work well with some apps that can detect root. But before I do that I want to start fresh because things tend to go messy and i do not have a backup device right now
Click to expand...
Click to collapse
flash stock oos thats it.. you may leave the bootloader unlocked. better that way..
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
mit2nil said:
Sorry but I am still not sure about exact process. Here are my noob queries:
1. Should I update twrp to latest version before proceding? If so which one? currently it is 3.0.3-0. I remember running into encryption issue due to unsupported twrp when I did this last time.
2. Should I use wipe option to wipe anything before I update OOS? I want to do clean install. If so, what should I be wiping out of dalvik/system/data/internal storage/cache/usb otg?
3. To update, I should copy full ota zip on internal memory -> go to recovery -> install -> select zip file -> swipe to flash. Is that correct?
4. After that if I boot into recovery -> I will keep twrp and if I let it boot, it will replace twrp with stock recovery right?
5. Let say, I let it boot n install stock recovery, will I have dm-verity during next boot?
6. Will my superSU root be gone or still be there? If it is still there should I do complete unroot before starting this process?
7. If it is not gone, is it ok to do complete unroot after stock oos + recovery is installed?
8. I saw a dm-verity patch zip which can be used to patch dm-verity in bootloader mode if I do "fastboot oem disable_dm_verity and fastboot oem enable_dm_verity". Does it suppress the issue or it resolves it gracefully?
Thanks for the patience and help in answering the queries advance.
Click to expand...
Click to collapse
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
reyscott said:
1. Try the first the current TWRP that you have. If it work, then just reboot it on to the system and TWRP will be overwritten by Stock OOS recovery.
2. Wipe dalvik/system/data/cache ..
3. YES , if im not mistaken.
4. answered on question 1.
5. most probably. Try flashing a certain firmware (not sure which one would work) . This is what I did before. But cant be sure.
6. It will be gone.
7. gone.
8. You can try.
Click to expand...
Click to collapse
Thank you so much.
mit2nil said:
Thank you so much.
Click to expand...
Click to collapse
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
tnsmani said:
I will tell you what I do.
Flash the latest official TWRP which is 3.1.1-2
If you want a totally clean install, boot into recovery and wipe system data including internal storage, dalvik and cache.
Then without rebooting, push the ROM downloaded from the OnePlus site to the phone. Select the ROM in recovery and swipe to flash.
Otherwise you can copy the ROM to the phone, boot into recovery, wipe system, data, dalvik and cache and then in recovery, flash the ROM.
Wipe dalvik and cache and reboot into system.
Your root will be gone and along with it TWRP. You will be on stock ROM with stock recovery.
Leave the bootloader unlocked. If necessary, it can be locked at any time.
Most likely you will not get the dm verity error. If you do, simply flash the zip given in post #215 in siankatabg's thread on dm verity. It will merely remove the message as all such methods do.
Enjoy
Click to expand...
Click to collapse
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
mit2nil said:
Hi sorry I was afk for couple of weeks. So I started following this procedure. Very strangely, after I did a reboot post stock OOS (1.4gb zip) flash, twrp said no os installed, you are sure you want to reboot? I wasn't sure so I just said yes. Then I also so dm-verity coming back which was not the case when I started as I had disabled it using "fastboot enable_dm_verity" command.
Now, its been more than five minutes and my phone is stuck on the boot animation forever. (red dot in middle and two while dots rotating).
I am not sure what happened. Can someone please help me ?
Click to expand...
Click to collapse
Never mind. It booted to setup screen after few minutes. I guess I was in too much hurry.
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
danxtian said:
i just went to stock yesterday, i flash stock recovery followed by sideloading the Oxygen OS and after that relock the bootloader.. i kinda feel the battery is much better now compare to when it was rooted with OOS
Click to expand...
Click to collapse
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
There is a zip floating around XDA which I am not able to locate immediately. It may be on siankatabg's thread on dm verity. Simply flash it.
There is also another method I read about where you flash the 4.0.2 firmware, use the enable verity command on adb, boot the phone and then flash the current firmware.
Both methods are mentioned here in XDA. Search for it.
EDIT: One of them here: https://forum.xda-developers.com/showpost.php?p=72273041&postcount=215
See also the OP of the same thread for the other method.
mit2nil said:
Awesome. I am still getting safety net failure even after locking bootloader lock. Any ideas? It fails on CTS profile match. I even did factory reset. Only thing I can think of is the "dm verity" which is back for some reason even though I am on complete stock rom+recovery with no root or unlocked bootloader.
Any way to remove it from stock recovery?
Click to expand...
Click to collapse
i remember having the dm verity but i forgot what i did to make it disappear.. after that time ive been running OOS rooted with twrp until i decided to go back to stock locked
So, I stopped doing anything as I got busy with my life. Here comes the 4.1.7 OTA and my DM verity was gone. So, it seems like if you go to stock and if still dm verity exists, try to do ota update or go to one ota back for flashing.
Wow no need for custom recovery...
http://www.androidpolice.com/2017/0...hout-root-installing-without-custom-recovery/
@ultramag69 Maybe he doesn't follow Magisk closely? I know I don't. Magisk is only on used my stepmom's OP3T H2OS (which I update but don't look at the change log since it's only there in case I need it in the future), the other 2 phones I support don't use Magisk they use LOS su add-on. Not everyone who uses root cares about all the bloated/"nifty" features that come out, some just want plain old root.
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
I'm letting people know that with 14 they can keep stock recovery and take OTAs
ultramag69 said:
I only use for root too but every so often I open magisk manager as it updates both the manager app and magisk itself....
It's done that for ages... The only one I found that didn't was 13.1, that one needed TWRP.
Click to expand...
Click to collapse
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
lollyjay said:
Before you flame someone you should read the link. FOR THE FIRST TIME YOU CAN KEEP STOCK RECOVERY SO YOU CAN TAKE OTAS
Click to expand...
Click to collapse
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
ultramag69 said:
I have had stock recovery on more than one without having to reflash recovery with custom one .
If you use fastboot to flash the recovery, Instead of replacing with TWRP, you can use the command "fastboot boot TWRP.img" (TWRP.img being the name of the TWRP image you have such as twrp-3.1.1-0-oneplus5.img) , this will just boot you into TWRP where you can flash SuperSU or Magisk as you please but will revert back to stock recovery once you boot again while retaining root.
Click to expand...
Click to collapse
No need to do that now
Honestly, who roots a phone without flashing a custom recovery the very second after? Unless they are forced to use Flashfire without BL unlock, I guess.
lollyjay said:
No need to do that now
Click to expand...
Click to collapse
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
ultramag69 said:
Yeah, but using magisk to root my Axon 7 with unlocked bootloader didn't work...
There's still problems with some phones...
Click to expand...
Click to collapse
No problems at all with my OP5
Magisk 14.0 breaks XPosed so had to go back to Magisk 13.3
Now where can we obtain a copy of the stock boot.img?
almostthere said:
Now where can we obtain a copy of the stock boot.img?
Click to expand...
Click to collapse
What you're supposed to do is make a backup of your boot partition any time you update your rom. So if you didn't do that then you can dirty flash your current Rom and that would give you the stock boot.img and again, go into recovery and make a backup of your boot partition. then if you want to flash a custom kernel you can.
Help the noobs
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
s_ofer said:
Would any of you more experienced guys please post a step-by-step of how to do it?
From what Eric214 wrote I still don't understand where (or how) to get a copy of the stock_boot.img.
If you get the copy of the stock boot image, is it possible to do it without unlocking the bootloader?
I already installed everything before reading how to root - stupid me, and don't want to reinstall everything.
Click to expand...
Click to collapse
I have the stock 4.5.10 boot.img for download here:
https://drive.google.com/file/d/0B3gcDbDvV4Mkbm5EMEZ4dnpSbk0/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs
Thanks.
Do any of you think it is possible to FLASH anything without unlocking the bootloader?
There is a thread somewhere for OP3T that shows somehow that is possible to load TWRP on the phone without unlocking the bootloader or wiping data.
I only use for root too but every so often I open magisk manager as it updates also both the manager app and magisk itself. But using magisk to root my Axon 7 with unlocked bootloader.
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
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
There is no TWRP currently and no, you cannot do it without PC because of fastboot etc.
kouzelnik3 said:
There is no TWRP currently and no, you cannot do it without PC because of fastboot etc.
Click to expand...
Click to collapse
Thank you so much... Can you link a tutorial or something to show how to root my phone? I wanna use substratum and I read Andromeda no longer works I've been on iPhone too long I forgot all the cool things android can do
s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
OnePlus 10 Pro NE2215 ***ROOTED*** (EX01 Update! READ BEFORE UPDATING)
This is for the NE2215 Rom. Step 1: Unlock your bootloader. Step 2: Download and install Magisk Stable or Canary. Your choice, but I used Canary. https://github.com/topjohnwu/Magisk Step 3: You can use either patch the stock boot or use my...
forum.xda-developers.com
s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
You really don't need TWRP.
There's also a bunch of threads on rooting now.
Here's my one:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
It's based on the EU device so the images held here are for the NE2213 but the processes are valid for any OnePlus device.
All in thread if you need help
s_nieto said:
Can I root this device without a computer? I looked and can't find a twrp recovery file for this device sorry if I'm asking a stupid question Im new to this before I had an I phone I have the ne2215 unlocked version
Click to expand...
Click to collapse
You really don't need TWRP.
There's also a bunch of threads on rooting now.
Here's my one:
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
It's based on the EU device so the images held here are for the NE2213 but the processes are valid for any OnePlus device.
All in thread if you need help
Your first step will be to quickly set up the phone so your ready to handle the bootloader. Get past all set up, it doesn't matter what you do as your wipe the device anyway.
Second is going about the tackling the bootloader (oem unlocking) Plenty of guides however please use below Make sure your sat on the home screen (unlocked)
Bootloader link bro
(Once you have done this leave the terminal open, you need this again.)
Afterwards, do a quick setup, nothing major to this as your be wiping again anyway
g96818 was kind enough to post a quide here : Rooting
I will refer to his links shared from now however in such a way you can stay here.
Assuming bootloader unlocked, device setup, now download and install the apk :Magisk root
You will also want his stock boot file being this here : Boot.img
With magisk open go to 'install' and select the boot image to patch it. Once it is patched up, connect back to the PC and copy the file to the same folder as the bootloader/ADB files . (rename the file to "patched_boot")
*terminal used before*
\To Reboot to bootloader - this also checks connection indirectly ( Copy from here and right click in CMD/terminal to paste it in)
Code in terminal:
adb reboot bootloader
(after a minute for two)Followed by:
fastboot boot patched_boot.img
After, reboot the phone so it powers up, maybe takes a tad longer but it should actually be very quick. (This is known as a temporary boot)
Then simply, "Open Magisk and perform a direct install". Afterwards i personally would reset the phone and set it up again properly (accounts, email, porn ect). The files you need remain.
Once set up, just be sure to reactivate developer options (OEM will now remain unlocked however re-enable USB debugging (if you have any issues this will save you!!!!!!!)) you cannot perm brick this phone unless you miss this one critical step up.
Reinstall magisk (I found my phone kept it however i also have it naturally on my play account so i may have missed it installing) Just check its there, any concerns you can now just directly flash again with no need for the PC now. Otherwise use a root checker off the play store however just get magisk anyway.
I then updated to A12 from the settings update and afterwards just for peace of mind, i redid a direct install via magisk incase the boot.img differed. I booted up perfectly fine after my update but for peace of mind i would recommend it.