All I get is the option to patch boot img and the option to install the zip.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can only do direct install if the Manager has superuser access. In other words, if you already have Magisk installed and want to install an update. First install you need to patch the boot image and flash manually, or download the zip and flash in recovery.
Didgeridoohan said:
You can only do direct install if the Manager has superuser access. In other words, if you already have Magisk installed and want to install an update. First install you need to patch the boot image and flash manually, or download the zip and flash in recovery.
Click to expand...
Click to collapse
Thanks so much! boot image has been patched, i think. Now, how do i install magisk via stock recovery? how do i navigate to the
magisk manager folder?
fwng said:
Thanks so much! boot image has been patched, i think. Now, how do i install magisk via stock recovery? how do i navigate to the
magisk manager folder?
Click to expand...
Click to collapse
You can't install it with a stock recovery.
Depending on your device you need to use fastboot, ODIN or whatever is applicable.
If it's a non-Samsung device fastboot usually works. While booted to bootloader and with your device hooked up to your computer:
Code:
fastboot flash boot patched_boot.img
If you don't have adb and fastboot installed, get it here:
https://developer.android.com/studio/releases/platform-tools.html
If you can't get it to work, there's usually plenty of help and info in your device's forum.
Didgeridoohan said:
You can't install it with a stock recovery.
Depending on your device you need to use fastboot, ODIN or whatever is applicable.
If it's a non-Samsung device fastboot usually works. While booted to bootloader and with your device hooked up to your computer:
Code:
fastboot flash boot patched_boot.img
If you don't have adb and fastboot installed, get it here:
https://developer.android.com/studio/releases/platform-tools.html
If you can't get it to work, there's usually plenty of help and info in your device's forum.
Click to expand...
Click to collapse
That worked! thanks so much! sorry to trouble you!
fwng said:
That worked! thanks so much! sorry to trouble you!
Click to expand...
Click to collapse
Awesome! And it's no trouble... I'm here because I like to help. :good:
Hi,
I'm facing a strange issue. My note 8 exynos INS dual SIM has the Ironman rom installed and running. I had magisk root selected and installed. These days I get a notification about a magisk update (v16.0) when I tap the notification it takes me to magisk start screen where it shows magisk as not installed with the option to download the boot image or patch the boot file.
I then download the new zip, get into twrp recovery, flash the zip and reboot. After thd phone starts up and i click the magisc app icon magisk opens and shows me that the latest version is installed.
However in a random duration which can be 15 min or 1 hrs or 3 hrs, the update notification pops up again and tapping it shows magisk as not being installed with an older version in red below the latest version in green.
I have been using magisk on my devices for long and this is the fifth device SM-N950FD that I'm using it now and have seen this the first time on nougat 7.1.1.
Can I get some help regarding this. Apologies for this if it is a noob question or a duplicate but I couldn't find this anywhere so decided to post.
Thanks centaur31
centaur31 said:
Hi,
I'm facing a strange issue. My note 8 exynos INS dual SIM has the Ironman rom installed and running. I had magisk root selected and installed. These days I get a notification about a magisk update (v16.0) when I tap the notification it takes me to magisk start screen where it shows magisk as not installed with the option to download the boot image or patch the boot file.
I then download the new zip, get into twrp recovery, flash the zip and reboot. After thd phone starts up and i click the magisc app icon magisk opens and shows me that the latest version is installed.
However in a random duration which can be 15 min or 1 hrs or 3 hrs, the update notification pops up again and tapping it shows magisk as not being installed with an older version in red below the latest version in green.
I have been using magisk on my devices for long and this is the fifth device SM-N950FD that I'm using it now and have seen this the first time on nougat 7.1.1.
Can I get some help regarding this. Apologies for this if it is a noob question or a duplicate but I couldn't find this anywhere so decided to post.
Thanks centaur31
Click to expand...
Click to collapse
Does the ROM come with Magisk pre-installed? If so, I'd reflash the ROM without Magisk, if possible, make sure that there are no traces of Magisk on the device (Manager included) and install Magisk manually.
A better place for this post would have been the general support thread.
H
fwng said:
All I get is the option to patch boot img and the option to install the zip.
Click to expand...
Click to collapse
How do I install a zip?
Related
So Guys ROM twrp Root etc Now available for MI max 2. [oxygen 2]
You can Download official ROM from http://en.miui.com/a-234.html
and Flash it with MI flash.
or if you have dead Device follow deep Flashing Guide Here.https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055
twrp ported From mido Download Here
Flash with fastboot
Code:
fastboot flash recovery recovery.img
Flash magisk From here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
in trouble watch video-
Thank you! TWRP worked as intended, installed root manually. Donated as well.
TiMbl4 said:
Thank you! TWRP worked as intended, installed root manually. Donated as well.
Click to expand...
Click to collapse
ok thanks for Donation..
Lineage OS available https://forum.xda-developers.com/mi-max-2/development/linageos-14-1-mi-max-2-t3634864
Great toolkit but I have a couple questions. In the instructions on your site and youtube video it has a step to flash noverity. Is this really needed or is it just a precaution? Also, could I just flash the recovery via fastboot and then just pull noverity and magisk from their source and flash them? I always like to flash things myself the normal way so I understand what's going on.
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
XN Logos said:
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
Click to expand...
Click to collapse
Thanks for the quick response. I have one more question. Can I substitute SuperSU in place of magisk? After using the toolkit, I tried to update magisk to the latest version (13.2) using magisk manager but instead it gave an error. It didn't brick my phone or anything but when I rebooted and went into magisk manager it showed the phone was still properly rooted but reported that magisk wasn't installed. Not sure if it's a compatibility issue or not. I also tried flashing the latest version of magisk using twrp and got the same error in magisk manager upon reboot.
At any rate, do you see any problem with using SuperSU instead?
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
XN Logos said:
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
Click to expand...
Click to collapse
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Did you have to unlock the bootloader for installing twrp?
ikecomp said:
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Click to expand...
Click to collapse
unlock with developer rom
XN Logos said:
unlock with developer rom
Click to expand...
Click to collapse
Since 5 days i have been trying to unlock bootloader. Every time I get "Device not bound to account". I have tried everything. Can you help me?? I am already on developer rom..
yes that means You have not applied for unlock, First of all apply for unlock then when you receive Confirmation msg wait 72 hrs, then login mi unlock app with same account and then try to unlock
Magisk not detect root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow all instruction,i flash no verity and flash xnmagisk.zipafter reboot magisk appear like that? Have format but still not detect root, can root manually flash superusu but i want magisk to for hide root. So what next stepp for solve this problem? Let me know. Thanks
Hi guys, any idea why when I flash magisk 14.0 over a fresh 7.9.7 global developer rom I get CTS profile mismatch? It still shows safetynet as passing but android pay refuses to work. Also, is it safe to install OTA updates with magisk flashed?
How to root after flashing the official miui9 ? (my device is rooted miui 8.5)
please help (Device Mi Max 2 )
Hi Guys,
I've been using sokkoban's B596 ROM for a while now and it had Magisk 12 installed already.
Today I got a notification from magisk to update to new version, I downloaded it from app and it installed and prompted for reboot.
After reboot the phone got stuck on Boot Logo for a couple of seconds and then my phone started. I opened magisk to see what's new but what I saw was the old version of Magisk was also uninstalled and now its saying me to download and install magisk 13. When I touch the download button a zip file just got downloaded and nothing else happened.
Can someone please assist me on how to install it again ??
Any help would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hbilalshah said:
Hi Guys,
I've been using sokkoban's B596 ROM for a while now and it had Magisk 12 installed already.
Today I got a notification from magisk to update to new version, I downloaded it from app and it installed and prompted for reboot.
After reboot the phone got stuck on Boot Logo for a couple of seconds and then my phone started. I opened magisk to see what's new but what I saw was the old version of Magisk was also uninstalled and now its saying me to download and install magisk 13. When I touch the download button a zip file just got downloaded and nothing else happened.
Can someone please assist me on how to install it again ??
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Magisk 13.1 or 13? 13.1 isn't working on stock roms, only 13.
D1stRU3T0R said:
Magisk 13.1 or 13? 13.1 isn't working on stock roms, only 13.
Click to expand...
Click to collapse
13.1 is showing up
hbilalshah said:
13.1 is showing up
Click to expand...
Click to collapse
I know, but it's not working
hbilalshah said:
13.1 is showing up
Click to expand...
Click to collapse
Let me be clear. The new stable version of Magisk (v13.1) doesn't work on the stock ROM. For me it does boot, just takes a long time, but there's no Magisk Manager and if installed it lets you know Magisk is not installed. Get one of the betas that work (the last one does for me) or v12
Just installed last beta (c4377ed) and all works fine. SN passes and Play Store says my device is certified
Sonofapo said:
Just installed last beta (c4377ed) and all works fine. SN passes and Play Store says my device is certified
Click to expand...
Click to collapse
Link please..??
And a little bit guide on how to install as I have never installed it before
hbilalshah said:
Link please..??
And a little bit guide on how to install as I have never installed it before
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 download last zip file (c4377ed)
Installation is pretty simple restore boot image from recovery to do a clean install and flash this zip file from TWRP. Then download Magisk manager apk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) and install it.
Sonofapo said:
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 download last zip file (c4377ed)
Installation is pretty simple restore boot image from recovery to do a clean install and flash this zip file from TWRP. Then download Magisk manager apk (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) and install it.
Click to expand...
Click to collapse
Restore boot image..??
How to do that
hbilalshah said:
Restore boot image..??
How to do that
Click to expand...
Click to collapse
if you have never installed any other root method (for example Chainfire's SuperSu zip) you can avoid this step. Otherwise it is safer to restore a stock boot image via TWRP backup or extracting a new one from your rom file (UPDATE.APP or whatever) and flashing it via Fastboot. Make sure to install the correct boot image according to you current rom installed on your device
Sonofapo said:
if you have never installed any other root method (for example Chainfire's SuperSu zip) you can avoid this step. Otherwise it is safer to restore a stock boot image via TWRP backup or extracting a new one from your rom file (UPDATE.APP or whatever) and flashing it via Fastboot. Make sure to install the correct boot image according to you current rom installed on your device
Click to expand...
Click to collapse
I want to add you can flash images in TWRP
JpegXguy said:
I want to add you can flash images in TWRP
Click to expand...
Click to collapse
I don't think web have the dame rom version... Mine is b598 Sokkoban's rom
Go to this link and download the required firmware
After that extract the boot.img from update.app file and flash it... that should do
amageek said:
Go to this link and download the required firmware
After that extract the boot.img from update.app file and flash it... that should do
Click to expand...
Click to collapse
I always recommend this site
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
Sonofapo said:
I don't think web have the dame rom version... Mine is b598 Sokkoban's rom
Click to expand...
Click to collapse
Sokkobans ROM is stock with some more apps and settings changed. You can use the boot image from stock.
You can always get the FULL (and OTA, but we want full to extract) from here: http://hwmt.ru/oth/HWFF/info/view.php?find_model=ale-l21
UPDATE: Magisk v13.2 has been released, it works fine for me
Yes I can confirm it too, magisk 13.2 is all good.
D1stRU3T0R said:
Magisk 13.1 or 13? 13.1 isn't working on stock roms, only 13.
Click to expand...
Click to collapse
Thats why do never update this crap?
Magisk 13.1 doesn't work, but 13.2 and 13.3 works very good
RootingPro-18 said:
Thats why do never update this crap?
Click to expand...
Click to collapse
But 13.2 and 13.3 works
RootingPro-18 said:
Thats why do never update this crap?
Click to expand...
Click to collapse
If you want SafetyNet to pass you should update. Also changes are coming to modules... Anyhow 13.3 passes fine on B602 I presume. Not on B604 because it's not August 1st yet
Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted earopean OP6T consumer ever.
If you need any help ask me on my telegram group: https://t.me/xOP6T
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
..
mingo_mgx said:
Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted OP6T user ever.
Click to expand...
Click to collapse
Can i ask you a little help to make a dedicated and better twrp?
mingo_mgx said:
Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted OP6T user ever.[/QUOTE
Is it possible..
After boot the twrp> flash twrp zip> boot on twrp> flash magisk> boot to OOS..?
Click to expand...
Click to collapse
you can also ROOT OP6T with the magiskmanager to patch the boot.img
Can we skip the second install (adb sideload twrp zip) to just sideload Magisk and keep stock recovery for now
Can confirm, this works on my 6T also.
Striatum_bdr said:
Can we skip the second install (adb sideload twrp zip) to just sideload Magisk and keep stock recovery for now
Click to expand...
Click to collapse
Auto answering, it works without flashing for good twrp, just adb sideload Magisk zip once you've booted into temporary twrp img
Don't forget to install Magiskmanager apk then.
Will evidently need to be repeated at each OOS update if boot is replaced
What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?
Striatum_bdr said:
Auto answering, it works without flashing for good twrp, just adb sideload Magisk zip once you've booted into temporary twrp img
Don't forget to install Magiskmanager apk then.
Will evidently need to be repeated at each OOS update if boot is replaced
Click to expand...
Click to collapse
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?
iaTa said:
What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?
Click to expand...
Click to collapse
You need to keep stock recovery to be able to use OTA, To use TWRP you'll have to download the whole oos ROM, flash it and then you need to reflash TWRP and magisk as there is no separate recovery partition on op6 /6t
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
cultofluna said:
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?
Click to expand...
Click to collapse
Because it's temporary you have to use sideload, as TWRP is present only in ram, and it seems that the op6 version have difficulties to decrypt op6t data partition if I understood correctly. And because I didn't want to flash for good TWRP on the phone to keep stock recovery.
cultofluna said:
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?
Click to expand...
Click to collapse
Well when we boot the op6 twrp on our op6t's it doesnt ask to decrypt, so everything is in jibberish.
iaTa said:
What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?
Click to expand...
Click to collapse
When you get an OTA update it will download the full rom so it will be around 1,5gb. Just install it when you recieve it, and after that do the steps again to get root again.
mingo_mgx said:
I'm the first rooted OP6T user ever.
Click to expand...
Click to collapse
Doubt it.
feimummy said:
you can also ROOT OP6T with the magiskmanager to patch the boot.img
Click to expand...
Click to collapse
can u please elaborate sir ??
freakzapster said:
can u please elaborate sir ??
Click to expand...
Click to collapse
It's not very easy as you need to extract boot.img from the full oos zip(or extract it from your phone with fastboot), patch the boot img, then fastboot flash it back. Far more simple to to it as explained. And you need a computer anyway.
And with the new slot A/B architecture you need anyway a computer each time you flash a ROM, as you need to reinstall TWRP each time, due to the lack of recovery partition here (it's been 'replaced' by vendor partition necessary for Treble compatibility) .
@mingo_mgx: I have done a post here
Thanks for sharing the info :good:
ABotelho23 said:
Doubt it.
Click to expand...
Click to collapse
Yes he is, he was one of the few getting a Oneplus 6T on the 31st of October, and if there's no Guide to root yet, most of the users won't bother with unlocking BL
I had rooted my 6T and was installing midnight core magisk module. After flashing it in magisk i rebooted the phone and now im stuck in bootloop. I tried sideloading Magisk Uninstaller, But it gives me some error. Tried sideloading magisk, but still stuck in bootloop. Any suggestions?
Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 | 9.0.6 | 9.0.7 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image 9.0.5 here.
[*]Download the patched boot image 9.0.6 here.
[*]Download the patched boot image 9.0.7 here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot <filename>.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your device, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.
delete
Dark Nightmare said:
You should probably remove your telegram chat link, don't think it's allowed.
Click to expand...
Click to collapse
That's only for random links i think. i use a op6 kernel (smurf kernel) and he has his telegram chat open up for a long time.
mingo_mgx said:
That's only for random links i think. i use a op6 kernel (smurf kernel) and he has his telegram chat open up for a long time.
Click to expand...
Click to collapse
Oh okay, then disregard my comment, sorry.
mingo_mgx said:
Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot patched_boot905.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your dervice, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.
Click to expand...
Click to collapse
Worked perfectly, thank you.
Sorry if this is super noob question, but you still have to unlock the bootloader to do this, correct?
Mdaly001 said:
Sorry if this is super noob question, but you still have to unlock the bootloader to do this, correct?
Click to expand...
Click to collapse
Yes
Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!
YrrchSebor said:
Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!
Click to expand...
Click to collapse
Perhaps you're not seeing the link highlighted in the OP on mobile or for whatever reason.
Anyhoo,click on the word "here",Step 2 under the "How To" sub-heading & the "here" Magisk link in the following sub-heading.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or,just click on this link,where it resides:
https://androidfilehost.com/?fid=11410963190603844693
As for the rest,perhaps someone else will chime in soon,I'm still stock/locked,last device I rooted was an Honor View 10 a few months back,have since sold.......
KOLIOSIS said:
Perhaps you're not seeing th link highlighted in the OP on mobile or for whatever reason.
Anyhoo,click on the word "here",Step 2 under the "How To" sub-heading & the "here" Magisk link in the following sub-heading.
Or,just click on this link,where it resides:
https://androidfilehost.com/?fid=11410963190603844693
As for the rest,perhaps someone else will chime in soon,I'm still stock/locked,last device I rooted was an Honor View 10 a few months back,have since sold.......
Click to expand...
Click to collapse
Whoa, there's a couple lines there that aren't showing up in the XDA Android app, one of them being the here button to download the image. of course I have to download them on my laptop but I have a Chromebook right now running Android apps, including XDA. Anyway, thank you for posting it for me ?
Ah ok, do you just not find root necessary? I am basically fine without it, especially when there is no root or it is kind of a hassle. But somehow I can't help but tinker when it's as easy as it is on this phone ?
YrrchSebor said:
Whoa, there's a couple lines there that aren't showing up in the XDA Android app, one of them being the here button to download the image. Thank you for posting it for me
Ah ok, do you just not find root necessary? I am basically fine without it, especially when there is no root or it is kind of a hassle. But somehow I can't help but tinker when it's as easy as it is on this phone
Click to expand...
Click to collapse
I plan on rooting eventually,to disable apps/services that ping back info to who knows where, & using AdAway,that's about it for the main points.
As for ROMs,the choices are awesome once all the different teams get on board,my favorite being either RR Remix or Lineage,otherwise stock/rooted OOS is just as good.
Yeah,root is easy w/this phone,even the T-Mobile version isn't all that bad.
This phone is a good bang for the buck,but,if rooting/ROMs weren't part of the eventual equation,I'd pass on it & opt for a mid-tier phone,as this is my secondary device (Note9 is my DD).
One nice thing about OnePlus phones is the past four models have been one of the better SIM/Carrier free phones to use on T-Mobile US,as they've had the latest LTE Bands & WI-FI Calling & VoLTE work.
VVM probably works as well,but,I have never used it on any phone & probably never will.
KOLIOSIS said:
I plan on rooting eventually,to disable apps/services that ping back info to who knows where, & using AdAway,that's about it for the main points.
Click to expand...
Click to collapse
I logged all the DNS lookups, and I was shocked at how much ET was phoning home.
I black-holed all the bullsh!t telemetry and analytics calls with my DNS server and in the 6T hosts file.
Thank you, works like a charm.
Couldn't we just use the magisk manager app to patch our boot image ourselves and flash it?
YrrchSebor said:
Hi, I must be missing it but where can I download the patched boot image? Also, is this the same as rooting by flashing Magisk in TWRP? I was rooted that way before but I had that bug where the phone gets stuck on the bootloader is unlocked screen, seems to be a bug in the latest Magisk so I uninstalled it and was holding off for the time being. Thx!
Click to expand...
Click to collapse
In this way did you resolve the problem?
Is there an advantage to this method, like being able to get system updates without having to flash them urself?
From a security perspective, how can we trust any images like these?
Unless the file has a digital signature from Google or OnePlus, or a least we can verify the hash, how do we know there is no 'rootkit' or some other backdoor?
No offense intended to OP.
mingo_mgx said:
Root the OnePlus 6T with no TWRP.
Required:
[*]Latest ADB/Fastboot.
[*]Have OOS 9.0.5 in place.
[*]Unlocked bootloader.
How to:
[*]Boot into bootloader
[*]Download the patched boot image here.
[*]Drop the Patched boot image file inside your ADB/Fastboot folder.
[*]Open up a CMD window in the folder location.
[*]Type this command in CMD:
Code:
fastboot boot patched_boot905.img
[*]When the phone got booted download magisk manager here and install it.
[*]Open Magisk Manager and you'll see that it says that you're rooted.
[*]Make sure you checked "Preserve force encryption" and "preserve AVB 2.0/dm-verity".
[*]Click on Install and select Direct Install (Recommended)
[*]Wait till it's installed and ask you to reboot your dervice, reboot it.
Your'e now rooted.
If you need any help here is my telegram chat for support, or if you want to chat. here.
Click to expand...
Click to collapse
Works like a charm thank you! Would you provide us with an updated patched boot file when there is an update to Oxygen OS?
I assume all of you are on tmobile OP 6t since non tmobile would get their updates via OTA, correct? Also, does applying the update in this manner wipe the existing programs on the phone, again, I assume it does since bootloader has to be unlocked and Magisk is reporting root?
And lastly, Magisk Manager newest update is 6.0.1 so is there a reason you state to download 5.8.1 in the OP? Just curious, could be just incidental...?
free4flight said:
I assume all of you are on tmobile OP 6t since non tmobile would get their updates via OTA, correct? Also, does applying the update in this manner wipe the existing programs on the phone, again, I assume it does since bootloader has to be unlocked and Magisk is reporting root?
And lastly, Magisk Manager newest update is 6.0.1 so is there a reason you state to download 5.8.1 in the OP? Just curious, could be just incidental...?
Click to expand...
Click to collapse
For OTA, remove root in current slot within magisk manager, install OTA (full zip) within OOS, don't reboot, then apply root with magisk manager on the other slot (the one where OTA have been flashed) then only you can reboot. Root is preserved.
According to this thread: https://forum.xda-developers.com/t/...1-legendarypixieos-4-1-for-galaxy-m21.4379385
Flashing 25.x with that certain rom bootloops, and I have that version of Magisk flashed and installed to my device, but the app is bothering me to download the latest version of it.
Should I continue? Since this is after the fact?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Magisk stopped patching avb and some other stuff since 25.0 so some roms and kernels that need it wont work anymore. But if you already had v24 installed everything should be already patched. I've noticed that if you're only flashing v25*, flashing dmverity disabler along with it fixes bootloops.
So in theory it should be okay if you already have magisk installed. However, dont forget to take a backup of your boot before doing anything.
Alright, I'll update the thread if everything goes well.
Thank you!
Whelp, it is bootlooping with no access to twrp and shutdown.
I'll try to turn it off by removing the battery and reflashing back the working 24.3.
Note to future-self:
You can uninstall the newer magisk version by renaming the APK of the version you updated to by renaming it to `uninstall.zip` and flashing it.
You can also get an infinitely bootlooping device to odin mode by holding the power up and down keys while being connected to a computer when the boot cycle starts.
I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.
newt23 said:
I have successfully managed to update to v25.x. It seems patching the whole AP file causes issue related to vbmeta. Assuming you're on unmodified stock firmware, the solution is to only patch and flash the boot image. If you're installing/on a GSI, you'll also need to flash dmverity disabler.
Tne process that worked for me was:
1. Flash latest stock firmware.
2. Install Magisk Manager, patch boot image and flash it. Check Magisk Manager to ensure Magisk is installed.
3. Flash TWRP, perform factory reset from TWRP and flash GSI and dmverity disabler.
Click to expand...
Click to collapse
Greetings Friend,
Can you attach the Dmverity Disabler zip?
OldNoobOne said:
Greetings Friend,
Can you attach the Dmverity Disabler zip?
Click to expand...
Click to collapse
Greetings Friend newt23,
Can you also elaborate on the exact steps you did to get the GSI to boot.
I mean steps like which GSI booted? & did you put the GSI in sdcard then use terminal commands like- { mount partition system, cd documents, super flash system.img etc., did you use chodoe flasher, gapps }?
Thanks in advance.
Also, Magisk 26.1 seemed more stable on stock rom without the addon.d script ability on stock but some devs insisting on staying with 24.3 stable even though 26.1 has better SafetyNet but. What would be your advice?