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:
So, I have decided on rooting my Xperia Z3 Compact so that I can finally move OBB to SD card, however I have no knowledge of how roots work (not a programmer much), or which one to pick. I have seen quite a few options for different roots, and previously used Kingo root, but seeing the post about it I am avoiding it like a forest fire. Anyone got good suggestions on which one to pick for my Xperia z3 compact?
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
GarrusN7 said:
Erm can you explain it so that I will understand it? XD
I kind of understand what you mean but I am still confused here and there....
Click to expand...
Click to collapse
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
RealWelder said:
In modern Android the phone's security systems prevent rooting via one click apps unless the device is unlocked. The best/safest way to root is to flash custom recovery such as TWRP and then install SuperSU.zip from TWRP. Make sure you make a backup first just in case.
You will most likely have to unlock your bootloader before you can flash TWRP. SONY devices are usually pretty Dev friendly, so you shouldn't have too much trouble finding everything you need. Good luck.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
dev.kasibhatla said:
Your phone has a recovery. When you bought it, it came with the factory (or stock) recovery. Stock recoveries will only let you flash certain signed zip files and not all (for example - your ota updates). So you need to shift to a custom recovery that will let you flash any file you want. Custom recoveries are device specific. Search how to flash it in your phone. Common ones are - TWRP, cwm, philz.
Once you have your new recovery set up, you are ready to root it. All you have to do is use the recovery to flash the supersu file (i recommend chainfire). If you have twrp installed, the flashable su file is a part of it, and it will guide you.
Reboot after done, and supersu will prompt you to update your su binaries, done. you are all set. Dont forget to unlock the bootloader.
Your warranty will be void unless you revert all changes. Not at all complicated, you do it once and get the hang of it.
A short note on flashing: Flashing is replacing (or installing) certain system files. You can tweak your system in any way you like (overclocking, changing animations, installing apps or scripts, changing the os, etcetera ). Just make sure the zips you flash are compatible.
Click to expand...
Click to collapse
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
GarrusN7 said:
Is chain fire part of Super Su or do you mean instead of it? And what do you mean unlock bootloader???
Click to expand...
Click to collapse
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the mazimum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Thanks. Tho I am sure once I get hands on to it, I will know what to do. Can't wait to move those damned OBB Xd
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
fab_ben said:
Just be aware that by unlocking the bootloader you are going to lose camera quality. That's because the keys for image processing are deleted. I think it's only noticeable in low light situations, but still important to know, because once lost those keys will never come back. Therefore I'd rather recommend this rooting method:
https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Click to expand...
Click to collapse
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
What he/she says. Sorry, I totally forgot about that method, it's much easier, thank you!
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
Well ****....my root doesn't work. I am using SuperSu and TWRP but for some reason a ram disk extraction fails and no install...is it because I have systemless version of my phone or whatever keeps popping up???? And how do I fix that crap???
dev.kasibhatla said:
Chainfire made the root strategy. There are various strategies. Supersu is by chainfire. To change your recovery from stock to custom, you need to unlock the bootloader. It protects the current system by not letting unauthorized files overwrite or execute their scripts.
Not unlocking bootloader and flashing may lead to a brick. So
download platform-tools by google. (adb)
Extract it. Say at C:\
Now install drivers for your phone
open cmd and navigate to the folder where you extracted platform tools. Follow the code.
Enable usb debugging from developer options
Code:
cd C:\platform-tools
adb devices
a device and some number should show up with an online status
Code:
adb reboot bootloader
fastboot devices
again, a device and number should show
Code:
fastboot oem unlock
fastboot reboot
if it says success,bootloader is unlocked.
download a recovery.img specific to your phone. rename it to say twrp.img and place it in the same folder as platform tools.
Code:
adb reboot bootloader
fastboot boot twrp.img
the recovery will boot. this is a temporary boot and will wipe off on a reboot. Flash your supersu zip to root.
That's all. You have a rooted phone with an unlocked bootloader.
That is the maximum anyone would describe for you. Still confused, please do some research.
Hit thanks if i helped.
Click to expand...
Click to collapse
fluffi444 said:
I woundn't recommend this anymore...
Use this one from russel5 - this is for stock rom and locked bootloader - and for staying at looked bootloader...
https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
This is an noob-save tut which uses russel5's way...
https://forum.xda-developers.com/z3-compact/general/guide-newbshow-to-291-mm-z3clocked-t3536395
Click to expand...
Click to collapse
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
GarrusN7 said:
I unlocked the boot loader the official way (Sony guide and ****). I didn't want to brick my phone accidently.
Click to expand...
Click to collapse
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
dev.kasibhatla said:
You wouldn't have bricked your phone
If you followed instructions on their site and contacted them, like unlocking htc bootloader, congratulations, your warranty is officially void.
If you didn't contact them in any wau or uploaded your phone's mac/imei, if you re lock, warranty valid again.
Click to expand...
Click to collapse
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
GarrusN7 said:
At least I did this the safe way. Oh well, I never send my phones for repairs as the repairs are always overpriced, my dad fixes everything himself if actually fixable XD.
But my root issue still remains!
Click to expand...
Click to collapse
Here's a link from another post. Follow it and check. It should work.
(you've already performed a few of those steps)
link
Hey, so I am trying to follow the seemingly least invasive instructions for Magisk that involve patching the boot img.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
However, there's an obvious caveat: attempting to dd the boot partitions throws a permission denied without root.
dd if=/dev/block/mmcblk0p44 of=/sdcard/boot_a.img
dd if=/dev/block/mmcblk0p45 of=/sdcard/boot_b.img
Click to expand...
Click to collapse
What would you suggest is the most straight-forward way of getting those? I'd also like to have those dumps as a backup obviously, in case things go haywire.
birckston said:
Hey, so I am trying to follow the seemingly least invasive instructions for Magisk that involve patching the boot img.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
However, there's an obvious caveat: attempting to dd the boot partitions throws a permission denied without root.
What would you suggest is the most straight-forward way of getting those? I'd also like to have those dumps as a backup obviously, in case things go haywire.
Click to expand...
Click to collapse
boot twrp image. and then make a backup of boot.img. don't flash twrp.
kraatus90 said:
boot twrp image. and then make a backup of boot.img. don't flash twrp.
Click to expand...
Click to collapse
Oh perfect! Didn't know I could do that through TWRP boot. Thank you! :good:
Sorry if an obvious question, but I need to unlock my bootloader for this first, right? It's been some time since I've had an unlocked phone.
birckston said:
Oh perfect! Didn't know I could do that through TWRP boot. Thank you! :good:
Sorry if an obvious question, but I need to unlock my bootloader for this first, right? It's been some time since I've had an unlocked phone.
Click to expand...
Click to collapse
yep
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?
greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.
I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck
I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root
Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.
mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!
greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot
mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot
fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?
Alot of people still dont seem to understand or know how to root their devices and the help ppl find online can be misleading and sketchy. I just want to share this easy method to hopefully save some ppl from trying to do this or that and having bad results. This IS the common sense duh way to root. Use magisk to root it. Long as you got adb and fastboot on ur pc and the phone's bootloader is unlocked you can root like this...
1)download the magisk manager.
2)get the ota .zip file for the android version you are running.
3)get payload-dumperwin64.zip and unzip it.
4)unzip the ota.
5)put the payload.bin file from the ota into the input folder for payload dumper.
6)run payload dumper.
7)get the boot.img from the output folder of the payload dumper.
8)copy the boot.img to your phone.
9)open magisk manager.
10)press install, then install, then 'select and patch a file'.
11)select the boot.img
12)once the boot.img is patched it will be renamed magisk_patched.img, copy the magisk_patched.img to your computer.
13)start your phone in fastboot mode
14)on your computer open a command prompt and type 'fastboot flash boot (and the magisk_patched.img file location)'
15)once successful type 'fastboot reboot'
ROoT! Super easy right? And yes, it works with 10 stable. Just make sure to use magisk manager 20.1.
As far as twrp goes, you can try flashing it with magisk if you like, but I can't say whether or not it will work on 10 because I didnt bother. Twrp hasnt been very helpful to me on my 6T.
I know to a lot of us this is pretty common sense, but it looks like there are still a lot of ppl needing help getting rooted on 10 stable for some reason... Thats why I posted this. Don't hate. Help.
<Mod edit>
To install TWRP,
download - android Q twrp img and the installer zip. Place the TWRP installer zip in your phone storage.
download magisk installer zip into your phone storage.
1. boot in fastboot, open command line in your PC.
2. flash twrp img - fastboot flash boot <your twrp>.img. You lose root and custom kernel here.
(fastboot boot <your twrp>.img for android 9.)
3. Reboot to recovery from phone's fastboot menu
4. install the <TWRP installer>.zip file in TWRP.
5. Reboot TWRP to flash magisk.
6. Flash <magisk installer>.zip in TWRP
7. Reboot system. Exit your command line on PC.
The end.
Can't we just flash Magisk on TWRP?
yot2703 said:
Can't we just flash Magisk on TWRP?
Click to expand...
Click to collapse
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
e5p10nage said:
Yea, but you tend to lose twrp upgrading to 10. I've seen ppl report having problems when they try the twrp q img. This way, there is no need for twrp. But if you successfully got twrp workin w/ 10, by all means go that route. I decided not to bother with twrp for now after one of my backups failed to be recoverable. The last straw. Lol.
Click to expand...
Click to collapse
Seeing as how I haven't made a reliable backup in TWRP/custom recoveries in like two years, I appreciate this route. Swift Backup and frequent OTG backups are enough for me, I just want root.
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Striatum_bdr said:
There is a new version of twrp, build .27 that is meant to fix backup / restore issues
Click to expand...
Click to collapse
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
e5p10nage said:
Gud to know. Does 'fastboot boot twrp.img' work with android 10 now with .27? Cuz it wasn't lettin me do it after the updgrade.
Click to expand...
Click to collapse
No it doesn't work at all forever. Fastboot is modified in 10 you must write 'fastboot flash boot file.img'
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
UberFiend said:
Is losing WiFi one of the bugs on Q? I had WiFi, but it won't stay on after I used this to root.
Click to expand...
Click to collapse
I have heard of that being a bug with Q. Just look it up on google. Lots of pixel owners havin that same issue. I didnt have this problem, so I am not sure what caused it or how to fix it. You FOR SURE used the boot.img from the ota you currently have installed? Anyway, I think I saw someone say something about the throttling in the developer settings.. IDK if that really has anything to do with it though.. Im sorry that happened though.
greentag said:
Doesn't work. Made image with latest Magisk Manager. I suspect it might be existing Magisk modules that make my phone boot loop, but without root and TWRP I can't get rid of them without a factory reset, which is what is recommended in the first place when using this method on A10. So this does not work.
Click to expand...
Click to collapse
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
e5p10nage said:
If you dont have root how or why do you have modules? This wasnt meant for upgrading.. This is meant for AFTER you have upgraded. Im not sure I understand what you are saying. Oh, and make sure to use the same ota you upgraded with btw.
Click to expand...
Click to collapse
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
greentag said:
I upgraded from 9.17 to 10. I lost root and ability to flash Magisk, as I am not willing to factory reset, currently. When I was on 9, I had TWRP and root along with Magisk Modules. Just because you flash a stock boot image, doesn't mean that the folder Magisk modules are stored in doesn't exist. So when I upgraded, I had all those modules still stored.
When you try to patch and flash the stock boot image on 10, you're going to see allot of people complaining about boot loops. The current method to gain TWRP and root on 10 require you to factory reset, and my assumption is that it clears Magisk modules out. So if you use the method you posted, you're going to get boot loops, unless you factory reset beforehand. I tried the method posted before you made a post about it, and it is the same as now, boot loops, and being forced to flash stock 10 boot image.
Click to expand...
Click to collapse
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Tl;dr: this is not THE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
Tl;dr: this is notTHE root method IMHO.
I would advise everyone to stay away from this payload-dumperwin64.zip as it produces following Virustotal results (7 detections). Even if they are false positives, it's a needlessly complex method considering the alternatives out there. In comparison, Magisk is 100% clean while that is essentially one major hack. Let's not forget that the recent update of this TWRP recovery has tackled the decryption issue and grants us back all access to system manipulation and troubleshooting root problems. If you ask me, that still is the root method.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
e5p10nage said:
Not everyone wants to have to deal with twrp. Especially after being screwed over by it before the new .27 or whatever. Also, it doesnt have to be that specific payload dumper. Any payload dumper you decide to use is fine. Thats just the one I used. And actually I went and looked and found these instructions from the magisk gitHub:
https://github.com/topjohnwu/Magisk/blob/master/docs/install.md#boot-image-patching
Click to expand...
Click to collapse
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
e5p10nage said:
Heres what it says:
"Boot Image Patching
You would want to choose this method if either your device does not have custom recoveries, your device is A/B and you don't want to mix recovery and boot images, or your device is using system-as-root without A/B partitions.
To use this method, you are required to obtain a copy of the stock boot/recovery image, which can be found by extracting OEM provided factory images or extracting from OTA update zips. If you are unable to obtain one yourself, you might be able to find it somewhere on the internet."
Click to expand...
Click to collapse
The payload dumper thing I was talking about is a method of obtaining the boot.img from the ota on your own instead of looking for one on the web. Doesnt matter what payload dumper you use, that was just the one I found. Hopefully this makes it a lil more clear.
e5p10nage said:
This method I am talking about.. Should only be done after already successfully upgrading. Not as a method OF upgrading. What I mean is.. If youre tryin to do this on 10.. Then you need to upgrade to ten via the system update local upgrade method.. THEN patch the boot.img from the SAME exact ota.zip you used to local upgrade. If youre on 9.0.17 and you patch and flash a boot.img for 10, I would expect a boot loop. Maybe I am misunderstanding you.. IDK But for me, I HAD to factory reset to upgrade to 10. Im not sure why. I local upgraded with the ota, then my phone wouldnt boot up except into recovery mode. I hit factory reset, and it booted up fine. A couple days later I used the same ota to patch a boot.img and I fastboot flashed it, and it was smooth as butter. Root, no need to reset, no loss of data, no wifi issue... I am not sure what it is that is going wrong for some of you, but I wanna make sure you understand, this is not a way to keep root through the upgrade.. This is just a way to root without having twrp AFTER the upgrade. Or am I completely not getting what youre saying?
Click to expand...
Click to collapse
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
greentag said:
I said I upgraded. It's literally the first thing I said.
I upgraded the same way everyone else did. Using Oxygen Updater from the Playstore, then local upgrade. I did not factory reset, however, like you did.
The method you posted only works if you factory reset after the OS 10 upgrade.
There's already a method to upgrade and keep data, while also keeping TWRP and root, but there are a number of hoops to jump through.
Click to expand...
Click to collapse
I see. Well I am glad you pointed this out cuz I wasnt aware of the need to factory reset. The only reason I did is because after the local upgrade my phone wouldnt boot to anything but recovery UNLESS I reset it. So I didnt have an option not to really. I was rooted with twrp on 9.0.17, got the ota from oxy updater, local updated, just like ya said you did. Not sure why it wouldnt boot after that without the reset. Im not entirely sure that it is 100% needed to factory reset to root this way though. Ive talked to other people who tried this and said they had no problem. Then Ive also talked to other people who have. I feel like there are some variables we arent considering at work here. But thank you for pointing this out. The only goal I have here is to be helpful, so all problems with this method also need to be part of the conversation. So I appreciate it.