I am planning to root and use api2 for gcam. Will I receive updates after that? Also would those updates install successfully if rooted? If not any idea on how to just get api2. Can I UNROOT the device and will that install updates successfully?
No.
The thing you can do is that you install September ROM with MiFlash, then you get update. (You can install September ROM without loosing data.)
At the moment there is no way to keep root after update using current tools.
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Ex-Hunter said:
[*]Download the latest Magisk Manager and install. DO NOT update Magisk.
Click to expand...
Click to collapse
Hi, i have some mistake at this point, if i try to install newer magisk manager i cant because "i have another app with the same name", so what? using magisk 13.3 with the manager 5.1.1 provided by itself to active the cameras module? thanks
---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------
[/COLOR]
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
-----------------------------------------------------------------------------------------------------------------------
just a question: it's possible to edit build.prop via adb with twrp "live" without installing it?!
in this case, I could just edit it to enable camera2 api without rooting or installing twrp..
Click to expand...
Click to collapse
How to enable Camera2api after rooting with magisk? Please inform
n6i5k7h5 said:
I am planning to root and use api2 for gcam. Will I receive updates after that? Also would those updates install successfully if rooted? If not any idea on how to just get api2. Can I UNROOT the device and will that install updates successfully?
Click to expand...
Click to collapse
I just got a MiA1.I know how to root it with magisk but don't know how to enable camera2api.Will you please help me?
Flare_91 said:
Hi, i have some mistake at this point, if i try to install newer magisk manager i cant because "i have another app with the same name", so what? using magisk 13.3 with the manager 5.1.1 provided by itself to active the cameras module? thanks
Click to expand...
Click to collapse
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
Chazy12 said:
just a question: it's possible to edit build.prop via adb with twrp "live" without installing it?!
in this case, I could just edit it to enable camera2 api without rooting or installing twrp..
Click to expand...
Click to collapse
It should be possible. But I am wary of editing system partition because it might interfere with OTA updates and SafetyNet check.
Take a backup of system partition using TWRP just to be safe and proceed with editing.
Kindly report here if it works. Goodluck!:fingers-crossed:
Kripacharya said:
I just got a MiA1.I know how to root it with magisk but don't know how to enable camera2api.Will you please help me?
Click to expand...
Click to collapse
Sure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
Ex-Hunter said:
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
It should be possible. But I am wary of editing system partition because it might interfere with OTA updates and SafetyNet check.
Take a backup of system partition using TWRP just to be safe and proceed with editing.
Kindly report here if it works. Goodluck!:fingers-crossed:
Sure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
Click to expand...
Click to collapse
Thanks for the answer.
It's only a line of code.. I hope there'll be not a problem for just one line..
Inviato dal mio Mi A1 utilizzando Tapatalk
Ex-Hunter said:
Yure, just follow the steps I have written above. You'll definitely be able to enable camera2 api and more!
Click to expand...
Click to collapse
Ok, so I have Magisk 13.4 and manager app 5.4.0, and when I install camera module and restart it doesn't get that line written in build.prop so it doesn't work. In magisk it says that is installed. Is there something additional that has to be done or ?
Ex-Hunter said:
You should use Magisk 13.4 for pixel not Magisk 13.3. Download it from here.
After flashing install this.
If you get any error, uninstall Magisk Manager--just the manager and install the downloaded apk. There shouldn't be any problems.
Click to expand...
Click to collapse
Yes, my mistake i was already on 13.4 so i have unistalled magisk manager and then i have installed the latest version.
NITRO_100 said:
Ok, so I have Magisk 13.4 and manager app 5.4.0, and when I install camera module and restart it doesn't get that line written in build.prop so it doesn't work. In magisk it says that is installed. Is there something additional that has to be done or ?
Click to expand...
Click to collapse
Me too and i have add the lines manually then its ok for me.
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
So the only difference for now (hope the good guys here will solve this) is that we can use twrp but only in temporary way using " boot" command and not "flash" then use the known progress and install root etc etc etc... Can this guide work in a vanilla out of the box phone with the October patch on it ?
To reboot to bootloader then boot to twrp install root then reboot then all ok ? Or you have to set a partition first
Thanks again for the help
nikkpap said:
So the only difference for now (hope the good guys here will solve this) is that we can use twrp but only in temporary way using " boot" command and not "flash" then use the known progress and install root etc etc etc... Can this guide work in a vanilla out of the box phone with the October patch on it ?
To reboot to bootloader then boot to twrp install root then reboot then all ok ? Or you have to set a partition first
Thanks again for the help
Click to expand...
Click to collapse
Yes it will work. No need to set a partition.
enricogrim said:
Hi, I followed your guide but when I boot to TWRP I can see only empty folder in the internal memory and I can't select the sd card. What was my mistake?
thank you very much
Click to expand...
Click to collapse
Do you use any PIN/password? If so, you have to input it when the TWRP boots up.
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
Hi,
Have you tried using the newer Magisk V14.2 (1420) to root MI A1?
Thanks and best regards!
William
cmk7128 said:
Hi,
Have you tried using the newer Magisk V14.2 (1420) to root MI A1?
Thanks and best regards!
William
Click to expand...
Click to collapse
Yes, but unfortunately it doesn't work and the device will be stuck in a bootloop. @topjohnwu is working towards a fix. I'm sure we'll get the official Magisk on our device pretty soon.
Ex-Hunter said:
Yes, but unfortunately it doesn't work and the device will be stuck in a bootloop. @topjohnwu is working towards a fix. I'm sure we'll get the official Magisk on our device pretty soon.
Click to expand...
Click to collapse
Thanks for the feedback, much appreciated. BTW, do we have to fastboot flash the original/unpatched boot image before we proceed to download and install the new security update patch (eg. Oct to Nov 2017 update)?
Thanks!
William
cmk7128 said:
Thanks for the feedback, much appreciated. BTW, do we have to fastboot flash the original/unpatched boot image before we proceed to download and install the new security update patch (eg. Oct to Nov 2017 update)?
Thanks!
William
Click to expand...
Click to collapse
No, no need to flash the original boot img if you are already rooted with Magisk. Just download and install the update normally, but make sure to flash Magisk afterwards to get root back.
Ex-Hunter said:
No, no need to flash the original boot img if you are already rooted with Magisk. Just download and install the update normally, but make sure to flash Magisk afterwards to get root back.
Click to expand...
Click to collapse
Yes, I am rooted with Magisk v13.4 as per your steps. Thanks again.
Best regards!
William
Ex-Hunter said:
You will receive updates after root. I was on rooted September patch and I have successfully installed October OTA update. Just follow these steps and you'll be good to go.
Download TWRP and Magisk from here or you can download this package, I have included recovery and Magisk. Copy Magisk-v13.4.zip to your device.
Enter fastboot mode on your device. I am assuming you know how to unlock your bootloader and you have all the ADB drivers installed.
I suggest you NOT to flash TWRP but boot to it instead. To do so type
Code:
fastboot boot recovery.img
In a few secs you should be in TWRP. If you're not booting into TWRP disconnect the device and switch off; While pressing vol down button connect the USB cable. You should now be in fastboot mode. Try typing the cmd again and it should work.
Flash Magisk-v13.4.zip via TWRP and reboot to system.
Download the latest Magisk Manager and install. DO NOT update Magisk.
Use this module to get camera2 api.
Download and install normally when the next OTA update arrives. You will lose the root when you reboot. But no worries, just reflash Magisk-v13.4.zip via TWRP and you will be good to go.
P.S. @ topjohnwu is working to get official magisk on our device. When that arrives you will be able to patch Magisk to the OTA update without going to TWRP.
Click to expand...
Click to collapse
Just asking after rooted, can I re-lock the bootloader again? In order to pass safetynet?
soralz said:
Just asking after rooted, can I re-lock the bootloader again? In order to pass safetynet?
Click to expand...
Click to collapse
If I'm not mistaken it will pass safetynet if you are rooted with magisk.
Sent from my Mi A1 using Tapatalk
Related
So today with some testers i managed to make root on OnePlus 7T, I want to specify that 95% of the work was done by @topjohnwu (Magisk creator). For now you should use only Magisk Canary files
I will explain 2 different guides:
First Root Guide:
This guide is for a specific rom version, so you will need to use a specific patched boot.img
- Download the patched_boot.img
- Reboot your device in bootloader-fastboot mode
- Flash the patched_boot.img in the boot partition:
Code:
fastboot flash boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
Second Root Guide:
This guide is more generic than the first one, you should use this one if you are unable to find a specific patched boot.img
- Download a patched_boot.img (you should try with the latest one)
- Reboot your device in bootloader-fastboot mode
- Boot the patched_boot.img:
Code:
fastboot boot boot.img
replace "boot.img" with the patched_boot.img path
- Reboot the device
- Install Magisk Manager
- Click on Install, then direct install and wait the end of the process
- Reboot the device
Third Root Guide:
Guide by @gpz1100
TIPS:
Actually you should use only Magisk canary files Magisk 20.3
You can get the stock boot images from the fastboot rom: https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
Actually i'm using magisk manager canary and magisk canary debug to patch the boot.img, I don't recommend updating magisk, if you don't want to see the updates install the normal magisk manager
Magisk 20.3 fully support OnePlus 7T and 7T Pro
HOW TO UPDATE a ROM and KEEP ROOT:
Before all Disable all magisk modules
Be sure to use Canary Magisk Manager and Canary Magisk (debug)
You can update a stock rom from phone settings with local upgrade:
- Update the Rom WITHOUT REBOOT;
- Open Magisk Manager;
- In Magisk Manager, click on Install/Install/Direct Install;
- Again in Magisk Manager, click on Install/Install/Inactive Slot;
- Reboot.
Download:
Patched/Stock Boot Images: https://www.androidfilehost.com/?w=files&flid=300177
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Donations:
Credits:
@RohanAJoshi
Flashed and working flawless.
Really thanks for this.
Awesome work bro.
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
nick_22 said:
Can you please upload the patched boot.img please? I dont see it in the above folder at all.
Click to expand...
Click to collapse
Done, i uploaded them using ftp and i forgot to move the files in the right folder
Working, thanks a lot @mauronofrio
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
See OP, its clearly mentioned there. You have to flash this via fastboot and not any custom recovery. Firstly setup adb on your PC and then check the commands. Its very easy. Do some googling and still if its difficult for you, come back and ask.
jesrani said:
I am on 10.0.3 begin so i should flash the magisk patched boot image of this version, is that correct? With what should i flash, sdk tools or any other specific tool? Is there any portable adb toolkit and do i need to copy the not image in the same folder as adb?
Edit : I tried but the device was locked so unlocked it after finding instructions on xda. Never knew it would wipe everything including internal storage also
Need to install everything again and have lost data of last few days. But I got root so that's the only consolation. Also a lesson never to make unnecessary haste. But it's fine. Won't repeat the mistake again.
Click to expand...
Click to collapse
Welcome to the android scene, reminds me of the old psx scene
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
Get your stock boot.img from 1st post.
Reboot to bootloader.
And do this command
fastboot flash boot boot.img
fastboot reboot
Device will boot unrooted.
---------- Post added at 05:58 AM ---------- Previous post was at 05:55 AM ----------
jesrani;80464121 [user=4712355 said:
@mauronofrio[/user], thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
RohanAJoshi said:
1. Yes, always wipe
2. Just update as usual, let update go, after installation complete, don't reboot device. Go to magisk, install, install on inactive slot. Reboot. You will be rooted (Warning : this is not tested on 7T, this method from 7)
3. TWRP will be developed but some good dev like @mauronofrio need device for this, as of now, no hopes for twrp. We are lucky that we got root.
Click to expand...
Click to collapse
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Thanks. Yes, root is good enough right now.
By "update as usual", do you mean through OTA? I think the phone reboots after update is downloaded and then installs the update but not sure. So once it reboots after updating, should I go to Magisk and install root?
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
In older devices like OP5T it happens like this, not in newer devices. OP7T has seamless updates, its installs while device is turned on in second partition.
nick_22 said:
I installed some rogue module, that was not supposed to be installed on OP 7T. Due to this, now I am not able to boot into patched boot. I had to re-flash my stock boot.img to boot into my phone. Can you please help? I want to uninstall that particular module thats all. Tried doing something with your TWRP, but it wont show my system or storage at all.
Click to expand...
Click to collapse
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
jesrani said:
@mauronofrio, thanks so much for this. I had some queries :
1) Is the internal storage always wiped when bootloader is unlocked or did I do something wrong?
2) I have switched off auto-download of updates and also disabled automatic system updates in Developer settings. Is this correct? How to proceed when an update is available in future?
3) Will TWRP be developed or is it not useful for OP7T?
Click to expand...
Click to collapse
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
jesrani said:
Should I keep Magisk update channel to Canary or Canary(Debug)? It's already showing an update as available. Should I update it?
Click to expand...
Click to collapse
Canary debug, don't update it
Help please. I have returned to Android after 5years with OnePlus 7t and trying to root it. I am trying this method but not being able to successfully root it. Steps I have tried
Went to fastboot mode by restarting the phone but I don't get an option to install the patched image file. And even boatloader is locked. Do I need to unlock the bootloader. And I unlock will I loose my data. Sorry for silly question I have completely forgot about Android.
Thanks, rooted successfully
?
To be honest need video tutorial asap?
mauronofrio said:
So, modules are saved in /data , the only way to remove them without root actually is wiping data, if you can't now, you can just flash the stock boot.img because without root the modules can't work. Usually you can remove all magisk stuff using magisk uninstaller.
1) yes
2) for rom updates i will pubblish a guide in the first post in some minutes
3) yes it will be developed but actually is needed a bit of time because twrp is not working for op7t (due to android 10)
Click to expand...
Click to collapse
Ok. Got it. So, I have already booted back to unrooted mode now. And I cant wipe my data again. Thanks for your response.
Resources:
1. TWRP img: https://drive.google.com/open?id=1M04t6uspBLDJfHXFfJQeOzqDRSk56UMF
2. TWRP zip: https://drive.google.com/open?id=16IbNJJspaqqimqdLeNGBnkRoj3rZ0zcR
Copy all into adb folder
Proceed:
1. Connect the device in fastboot mode, enter the command cmd: fastboot boot TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.img (boot, not flash boot, I do not write missing)
The machine will automatically boot into twrp
2. In Twrp choose Advanced => ADB sideload, enter the command: adb sideload TWRP-3.3.1-1004-ASUS_ROG2-CN-wzsx150.zip
3. Reboot into Twrp, select Advanced => Install root
Done, start and enjoy!
My telegram
https://t.me/rogphonevietnam2
That's work only on CN rom or also on WW?
dracoolia said:
That's work only on CN rom or also on WW?
Click to expand...
Click to collapse
All
Any other tested this method? Could someone else confirm this. Ty
iampatricktan said:
Any other tested this method? Could someone else confirm this. Ty
Click to expand...
Click to collapse
Working well
This works great! Thanks!
You install root or flash zip magisk 20?
dungnghien said:
You install root or flash zip magisk 20?
Click to expand...
Click to collapse
You just helped me on Telgram...Im rich...LOL. Im thinking magisk 20 should work. What do i know though?
suzook said:
You just helped me on Telgram...Im rich...LOL. Im thinking magisk 20 should work. What do i know though?
Click to expand...
Click to collapse
Oh. You can try 20!
suzook said:
I tried this...it booted fine with root, and wifi working, but the next reboot, slot was corrupt. I will try again
Click to expand...
Click to collapse
I think i will let someone else try 1st....LOL
dungnghien said:
Oh. You can try 20!
suzook said:
I tried this...it booted fine with root, and wifi working, but the next reboot, slot was corrupt. I will try again
Click to expand...
Click to collapse
Click to expand...
Click to collapse
my pc dont find fastboot mode
i try connect my rog phone 2 to pc and tell me waiting a device, anyone know how fix? thks
I have same pronlem, when I connect my phone on my laptop in adb that's work but when I'm in fastboot mode that's not find my phone any one can hepl, thx a lot
thermaldude said:
i try connect my rog phone 2 to pc and tell me waiting a device, anyone know how fix? thks
Click to expand...
Click to collapse
dracoolia said:
I have same pronlem, when I connect my phone on my laptop in adb that's work but when I'm in fastboot mode that's not find my phone any one can hepl, thx a lot
Click to expand...
Click to collapse
You guys using the side usb port?
suzook said:
You guys using the side usb port?
Click to expand...
Click to collapse
For me that's work well now I forget to edit PATH??, but I have a question when I install TWRP I dont active SU in advanced in TWRP, I install magisk zip to root my phone, but... because of that I lost TWRP, if I install again TWRP in fastboot I loose my root or not? Because both are boot image
dracoolia said:
For me that's work well now I forget to edit PATH??, but I have a question when I install TWRP I dont active SU in advanced in TWRP, I install magisk zip to root my phone, but... because of that I lost TWRP, if I install again TWRP in fastboot I loose my root or not? Because both are boot image
Click to expand...
Click to collapse
You lost twrp after flashing magisk.zip? That doesnt make sense
suzook said:
You lost twrp after flashing magisk.zip? That doesnt make sense
Click to expand...
Click to collapse
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.
sesz said:
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.
Click to expand...
Click to collapse
What you did is something different....you absolutely will lose twrp with an ota
Yeah same message, when I have installed zip of magisk with TWRP everything work well with magisk, but now when I want to boot on recovery I have big message in red
ERROR UNBOOTABLE SLOT
dracoolia said:
Yeah same message, when I have installed zip of magisk with TWRP everything work well with magisk, but now when I want to boot on recovery I have big message in red
ERROR UNBOOTABLE SLOT
Click to expand...
Click to collapse
Get back to Fastboot and run this command
fastboot set_active other
^ Then hit enter.
You can go back to recovery by
fastboot reboot recovery
sesz said:
I was on ww 1908.12 with twrp installed. I then updated to magisk 20.0 by flashing the zip through twrp. This caused me to lose twrp and I get an error unbootable slot when trying to enter into recovery now. Since there is no dev support I figure I'm not missing much without it. I was able to update to the latest firmware ww1908.25 by downloading the file from the op gdrive link. Moving it to root then apply update. Go to magisk install to inactive slot and reboot.
Click to expand...
Click to collapse
can you provide me with a link for the version 25 for ww?
and also i tried the method given in the first post but i still cannot connect wifi on my phone. I am on verion 21
Hello,
I have seen few requests about providing pre-rooted boot image file for OP7T Global (not Indian or European) version for firmware 10.0.6 so here you go.
Steps :
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
Also attaching the stock boot file in case anything goes wrong.
P.S : I don't own Global OP7T.
Link : https://androidfilehost.com/?w=files&flid=302500
has anyone tried this one yet?
xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?
damn i want to do it but i am afraid some of my apps will stop working cause idk if magiskhide will work at current time
xrelic7 said:
has anyone tried this one yet?
Click to expand...
Click to collapse
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.
23333 said:
Yes, I tried on my 7t and it booted successfully!Thanks OP's work!!! By the way , I also flash Blu kernel via fk app and it also worked fine. But I don't test any magisk mondule.
Click to expand...
Click to collapse
ty for the reply i might grow a few and give it a shot hopefully magiskhide is working so certain apps cant detect that i am rooted
I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure
xrelic7 said:
I tried the method above it booted the first time without problems however when i installed magisk canary and tried it did not have the option to direct install idk if i did something wrong not sure
Click to expand...
Click to collapse
Are you using Global or Indian HD65AA ? Not getting an option to directly install means somehow the patched image did not boot and the original imaged booted.
imakul8 said:
I would if I could update to the Global rom. Local update fails on rooted Indian 10.0.6. Anyone can advise me on this?
Click to expand...
Click to collapse
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.
zeusofyork said:
You need to download the global 10.0.6 OTA not fastboot image in order to do the local update.
Click to expand...
Click to collapse
Yes, that's what I have.
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
Click to expand...
Click to collapse
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?
ricksrod said:
1) Reboot your phone in bootloader mode (fastboot mode).
2) Execute command fastboot boot magisk_patched.img
3) Reboot the device
4) Install Magisk Manager
5) Click on Install, then direct install and wait the end of the process
6) Reboot the device
I've followed the above steps exactly but when I reboot the device it and open MAgisk Manager it shows that MAgisk is not installed. Any ideas?
Edit: I'm on Hd1900 Chinese variant running 10.0.6 global ROM
---------- Post added at 02:02 AM ---------- Previous post was at 01:18 AM ----------
When you run step 2, it boots the phone. Step 3 says to reboot. Not sure if that is correct? Rebooting would just boot to the stock boot image again?
Click to expand...
Click to collapse
You're right. Just skip that step 3.
imakul8 said:
You're right. Just skip that step 3.
Click to expand...
Click to collapse
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.
ricksrod said:
I did assume that so that's the step I followed.
Just to confirm, when I boot the patched image and install Magisk Manager and launch it, it should show that it is already installed? So I press "install" next to Magisk and direct install, this looks like it works. Then I reboot and I am not rooted, if I open Magisk Manager it shows that Magisk is not installed.
Click to expand...
Click to collapse
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you. ?
imakul8 said:
Right. Magisk said it was installed. I direct installed again, rebooted and Magisk was still installed. No idea to help you.
Click to expand...
Click to collapse
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?
ricksrod said:
I've tried extracting the boot_img from my device and then patching that directly in Magisk and that does not work also, even though it reports a success, it doesn't appear to work.
When you install Magisk, what do you have ticked in the Advanced Settings out of:
Preserve Force Encryption
Preserve AVB 2.0/dm-verify
Recovery Mode
?
Click to expand...
Click to collapse
Just the first two. Not recovery mode.
imakul8 said:
Just the first two. Not recovery mode.
Click to expand...
Click to collapse
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?
ricksrod said:
I've got it working now by using the Canary version of Magisk. I thought the stable version was now working?
Click to expand...
Click to collapse
Stable is working for me, but good that you got it working. ?
Can someone check if magisk hide is working properly? Thanks
Jeens99 said:
Can someone check if magisk hide is working properly? Thanks
Click to expand...
Click to collapse
It works. Snapchat and my banking app don't like root. They're working fine.
Hello i found a little way for have root & and working xposed with no bug on last firmware WW_17.1810.1910.73 & WW_17.1810.1911.110
Stock Recovery
You need adb drviers and unlocked ZenFone 6 on WW_17.1810.1910.73 or WW_17.1810.1911.110
First install last Magisk Manager
Open setting of Magisk and add custom update channel https://github.com/solohsu/magisk_files#custom-update-channel
Download ZenFone6RootXposed-10.73.img or ZenFone6RootXposed-11.110 (i have add stock boot11.110.img, we will need it for next update)
http://www.mediafire.com/folder/skzceszqu8d3j/AsusZenFone6
Now reboot device to bootloader
Code:
adb reboot bootloader
And boot with ZenFone6RootXposed-10.73.img or ZenFone6RootXposed-11.110 (not flash it, your device have a chance to bootloop)
Code:
fastboot boot ZenFone6RootXposed-10.73.img
Code:
fastboot boot ZenFone6RootXposed-11.110.img
The devices reboot automaticly
Go to Magisk and install Magisk, choose direct install
Reboot and Enjoy root
if you want Xposed flash it with magisk :
Riru Core
I use YAHFA
Android 10 ElderDrivers Xposed
And the manager
Xposed Installer​
Good morning
I have tried several times root for Android 10
The Magisk part works smoothly, but the Xposed part never works, producing a bootloop
I have extracted the boot and applied magisk, loaded the Riru Core module, but when loading ElderDrivers, the phone stays in bootloop
Do you know what the reason may be?
Works splendid, great guide!
Tried to use Sandhook first, but ended up with YAHFA instead due some xposed problems (xposed not detected).
Had an old version of Android 9, so i first upgraded it to "UL-ASUS_I01WD-ASUS-16.1220.1909.194-1.1.1" (only supported upgrade path - 9 to 10), then to "UL-ASUS_I01WD-ASUS-17.1810.1910.73-1.1.1-user" (your specified .73)
- Later patching with your img
Thanks
it is impossible
Starting with .73 stock
at the moment I install Riru Yahfa, following the manual, it does not start again, unless install the official boot
the device stays on the Zenfone boot screen without doing anything else
I have tried the version supplied by Magisk, I don't know if you have tried another version
Why will we need the stock boot for the next update? We can't make menully update after root? I just want to make root not install xposed.
Sent from my ASUS_I01WD using Tapatalk
thanks a lot, this a really easy way to get root, but i have a little issue, i had my phone with NO pin code or fingerprint before using this method, and now if i want to ad a pin, password or gesture it simply does not get saved, every time i do the procedure to set the pin it does like if i did nothing, anyone has this issue, or know how to fix it, is there a problem if i hard reset?
any help will be good
In the latest build .110 ctsprofile is false while basicintegrity is true. Is it due to the root or the rom has not been signed by google?
Rom1995 said:
In the latest build .110 ctsprofile is false while basicintegrity is true. Is it due to the root or the rom has not been signed by google?
Click to expand...
Click to collapse
https://zentalk.asus.com/en/discussion/comment/35355/#Comment_35355
baster72 said:
Why will we need the stock boot for the next update? We can't make menully update after root? I just want to make root not install xposed.
Sent from my ASUS_I01WD using Tapatalk
Click to expand...
Click to collapse
just flash ZenFone6RootXposed-10.73 or ZenFone6RootXposed-11.110 and you willl have it
hdsporty50 said:
Good morning
I have tried several times root for Android 10
The Magisk part works smoothly, but the Xposed part never works, producing a bootloop
I have extracted the boot and applied magisk, loaded the Riru Core module, but when loading ElderDrivers, the phone stays in bootloop
Do you know what the reason may be?
Click to expand...
Click to collapse
hdsporty50 said:
it is impossible
Starting with .73 stock
at the moment I install Riru Yahfa, following the manual, it does not start again, unless install the official boot
the device stays on the Zenfone boot screen without doing anything else
I have tried the version supplied by Magisk, I don't know if you have tried another version
Click to expand...
Click to collapse
Don't flash Xposed using Magisk Download, flash it manualy :
EdXposed v0.4.6.0_beta
You will always get bootloop with v0.4.5.1_beta
_______________________________________
UPDATE for 11.110
flash boot.10.73.img for update safe
And do the same with 11.110 files.
Don't forget to add custom update channel in Magisk
And use v0.4.6.0_beta for xposed
Why can't we have any YouTube guides for anything related to this phone?
vernj123 said:
Why can't we have any YouTube guides for anything related to this phone?
Click to expand...
Click to collapse
I want to do it but I don't have another device to record.
Someone try this method to install xposed? I afraid to get bootloop.
Sent from my ASUS_I01WD using Tapatalk
Hi everyone, I hope somebody can help me out to solve an issue I just got with my zenfone,
After using an advise from DaConcho for getting back screen lock after unlocking bootloader I got in another situation.
I followed the instructions from the post and everything was going fine, I boot thought adb with the provided patched boot for Q .110 and that far no issues , when I open magisk manager to download magisk from the alternative source magisk manager prompt to complete the installation downloading some necessary files, not the magisk version, just said some files, and I click yes, then it installed something and reboot, phone started fine, but when I wanted to start the process again I found out that I loose PC connectivity.
I have no connection at all, even if I manually boot in bootloader I can't connect to PC, so no adb commands,
Please can someone help
does someone has the patched boot image for new .119 firmaware, i updated and losee magisk
baster72 said:
Someone try this method to install xposed? I afraid to get bootloop.
Click to expand...
Click to collapse
Don't be afraid just flash stock boot if you get bootloop
joesa said:
does someone has the patched boot image for new .119 firmaware, i updated and losee magisk
Click to expand...
Click to collapse
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
MystikMan97130 said:
Don't be afraid just flash stock boot if you get bootloop
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
Click to expand...
Click to collapse
Thanks a lot !!! You really help a lot with this method
MystikMan97130 said:
Don't be afraid just flash stock boot if you get bootloop
I update my links you can get stock boot here Boot & RootedBoot ZenFone6
Click to expand...
Click to collapse
can you please check link, it is not working, i can see folder but can not download
Hello, direct link:
ZenFone6RootXposed
Nice, thanks a lot for this! Rooting on stock with unlocked bootloader worked for me perfectly (did not check xposed)!
est-ce que l'on perd ses données en faisant le root ?
merci!
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!
Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?
posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.
thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.
thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.
Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you