Already prompted to install 11.2.7.7. About to install/re-root.
Normal process for taking the OTA and keeping root worked without any issue.
are you doing both Direct & Inactive slot Install before Reboot?
dmarden said:
Already prompted to install 11.2.7.7. About to install/re-root.
Click to expand...
Click to collapse
where did you get it?
dmarden said:
Normal process for taking the OTA and keeping root worked without any issue.
Click to expand...
Click to collapse
Can you give me the kernel patch file? magisk
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Andrew8578 said:
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Click to expand...
Click to collapse
You don't need to restore anything in order to update to a New OTA. Simply disable any magisk module you use. Reboot your device then let the OTA install it self. Once done, DO Not reboot and just go to magiskmanager, and install magisk to the available slot. After what you can reboot your device, re apply your magisk modules. Et voilà
Fre$h said:
You don't need to restore anything in order to update to a New OTA. Simply disable any magisk module you use. Reboot your device then let the OTA install it self. Once done, DO Not reboot and just go to magiskmanager, and install magisk to the available slot. After what you can reboot your device, re apply your magisk modules. Et voilà
Click to expand...
Click to collapse
I just did that and nothing has changed. If someone can give the 11.2.7.7aa image, that would help alot
galaxys said:
are you doing both Direct & Inactive slot Install before Reboot?
Click to expand...
Click to collapse
Yes
vibrantliker said:
where did you get it?
Click to expand...
Click to collapse
Just through the normal system updater.
dimmed said:
Can you give me the kernel patch file? magisk
Click to expand...
Click to collapse
No, sorry, I don't do this.
Andrew8578 said:
Hey, I just got the update, and Restoring the boot image with Magisk no longer allows me to install the update without unrooting. at first it is downloading for a bit, then it goes to "installation problem", which is not something that happened last time
Is this normal?
Click to expand...
Click to collapse
I followed my normal process (I don't use any Magisk modules):
Magisk Uninstall->Restore Images (do not reboot)
Take OTA (do not reboot)
Install Magisk to both active and inactive
Reboot
Worked without issue, as always.
I found 11.2.7.7.LE15AA, disabled all magisk modules rebooted, installed update reinstalled magisk to other slot, rebooted now I'm boot looped and in recovery, set it back from A to B (was previously on B), as obviously slot_A is non-functional or something went wrong with the upgrade from 11.2.5.5.LE15AA to 11.2.7.7.LE15AA, same problem still boot-looped.
Maybe teh custom kernel was to blame, I'll try restoring boot image and try again
I'd so prefer a full zip if they every provide one for the LE15AA version, as this method is never easy
egandt said:
I found 11.2.7.7.LE15AA, disabled all magisk modules rebooted, installed update reinstalled magisk to other slot, rebooted now I'm boot looped and in recovery, set it back from A to B (was previously on B), as obviously slot_A is non-functional or something went wrong with the upgrade from 11.2.5.5.LE15AA to 11.2.7.7.LE15AA, same problem still boot-looped.
Maybe teh custom kernel was to blame, I'll try restoring boot image and try again
I'd so prefer a full zip if they every provide one for the LE15AA version, as this method is never easy
Click to expand...
Click to collapse
Yeah, I don't do any custom kernel stuff or magisk modules, I cannot personally comment. What I know, for me, is the process fails 100% of the time if I don't do the Magisk image restore and it succeeds 100% of the time if I do.
I am currently on 11.2.4.4 AA (Global), rooted. Can I upgrade to the EU ROM since they tend to get full updates while AA has not been? If so, do I just flash the 11.2.6.6 EU ROM or should I flash 11.2.4.4 EU ROM then flash a more up-to-date ROM? If I flash the EU ROM, would I loose anything?
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Fre$h said:
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Click to expand...
Click to collapse
Not sure if this was for someone specific for their unique circumstance. If this was just meant generally, then it is inaccurate.
I don't use Oxygen Updater. I just take the incremental OTA using the steps I mentioned.
Fre$h said:
As rooted you have to flash OTA using full OTA zip file that you can download using oxygen updater app. Incremental OTA method cannot work properly.
On Oxygen updater app, download the full zip file (it will detect Magisk and advise you to use that method.)
Once downloaded, be sure that every magisk module are disabled and reboot.
Now go to parameters/system/system update then click on the upper right icon and chose local update. If it's not already done, point to the full zip file location and let the update process run to the end.
Once done, do not reboot and use magiskmanager to reflash magisk to the available slot.
Click to expand...
Click to collapse
Just letting you know, Oxygen Updater is stuck on 11.2.4.4, as is the OnePlus website.
dmarden said:
Already prompted to install 11.2.7.7. About to install/re-root.
Click to expand...
Click to collapse
I am also in 7.7 NA, is it possible to root NA version. As NA use google services for updates. how to update, i heard no full zips updates in NA
Atul Menon said:
I am also in 7.7 NA, is it possible to root NA version. As NA use google services for updates. how to update, i heard no full zips updates in NA
Click to expand...
Click to collapse
Easy. You open magisk and restore stock boot. Don't reboot yet. Download and install update. Don't reboot yet. Open magisk and install to inactive slot. Reboot.
dmarden said:
Normal process for taking the OTA and keeping root worked without any issue.
Click to expand...
Click to collapse
you are saying taking this incremental ota worked for you? I did the exact same steps (restore images, install without rebooting, install to inactive slot) and my system is still stuck on 11.2.4.4, I do not know what the issue is
thirtythr33 said:
you are saying taking this incremental ota worked for you? I did the exact same steps (restore images, install without rebooting, install to inactive slot) and my system is still stuck on 11.2.4.4, I do not know what the issue is
Click to expand...
Click to collapse
Works for me every time...that way just post it.
netgar said:
Works for me every time...that way just post it.
Click to expand...
Click to collapse
yeah my system reports 11.2.4.4, yet have an incremental update for 11.2.7.7, which is odd for a number of reasons. long story short I'm sure it will cause me issues to try applying an incremental update that is not in order, but idk why 11.2.7.7 is showing up on my system, bc 11.2.6.6 never installed (or the system doesn't report it did)
Related
Hi dudes! Im trying to find a way to install Monthly Updates without loose the root and the custom recovery, some body can tell me how? Because im really want update to Oreo but i want be root user and dont have to make a clean install system every month... exist the way? Please help.... And Thanks!
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
You can use Flashfire.
nowster said:
What I do is flash all the updated partition images individually using "fastboot flash", then let it boot and settle for a few minutes (at the very least until the "performing updates" notification completes).
I then reboot into bootloader and from there boot into TWRP (without installing it) using "fastboot boot twrp.img" and then reinstall Magisk zip. None of Magisk's settings or modules are lost by doing it this way.
If you uninstall Magisk before updating the system, you risk losing its settings.
Click to expand...
Click to collapse
Okey, but using adb?
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
How dude? Can you tech me please?
Aijen said:
How dude? Can you tech me please?
Click to expand...
Click to collapse
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Yes, you can use TWRP's "Advanced" adb sideload feature to install Magisk zip.
"adb" only works when Android is running (or some recovery images are running). When the phone is in bootloader mode the tool you need is "fastboot".
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Thanks a lot! I will tried to do it!
fnldstntn said:
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
Are you do that method without problems?
Aijen said:
Are you do that method without problems?
Click to expand...
Click to collapse
Yes it worked for me. But if you have twrp make a nandroid backup.
fnldstntn said:
Yes it worked for me. But if you have twrp make a nandroid backup.
Click to expand...
Click to collapse
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
fnldstntn said:
https://youtu.be/WxWRYnzI1O4
Now it is competible with magisk and if you want magisk instead of supersu on installation process you can disabel the installation of supersu and ad magisk to flash afterwards. you can also use the factory images or full ota zips from googles website.
Click to expand...
Click to collapse
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Aijen said:
Another thing....the last. Did you maintain the Custom Recovery or Flash it again?
Click to expand...
Click to collapse
i dont remember
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk? THANKS A LOT WORKS!!!!
Click to expand...
Click to collapse
i dont know.
Aijen said:
dude! one last need reflash Magisk every time the OTA comes or Magisk survival the OTA flash with Magisk?
Click to expand...
Click to collapse
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
fnldstntn said:
You can use Flashfire.
Click to expand...
Click to collapse
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
zo1021 said:
Any ideas what will happen to ElementalX after flashing OTA using Flashfire?
Click to expand...
Click to collapse
Using the logic need to reflash it again
nowster said:
Magisk embeds itself in the boot partition. This prevents OTA from working.
Replacing the stock recovery partition also stops OTA from working.
The only reliable way to upgrade is by flashing the partitions again from the new factory image zip file, then reinstalling TWRP and Magisk afterwards.
Click to expand...
Click to collapse
Sounds logic to me....
FlashFire is saying that the update will likely fail because the OTA update is a block level update. Suggestions on how to get around this?
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.
Hey i share new update for op7t global.
I have not signal after the upgrade this are the specs that I followed
1 downloaded and installed from local upgrade
2 before reboot open magisk and install masgisk in the inactive partition
3 reboot and after my device first boot I got no signal and also the settings were kind of buggy, so I reboot like 3 times and everything is okey except for the missing signal
akuma48465 said:
I have not signal after the upgrade this are the specs that I followed
1 downloaded and installed from local upgrade
2 before reboot open magisk and install masgisk in the inactive partition
3 reboot and after my device first boot I got no signal and also the settings were kind of buggy, so I reboot like 3 times and everything is okey except for the missing signal
Click to expand...
Click to collapse
I use Oneplus 7T without root and everything is fine with the update. I have been using the update for a couple of hours and until now it seems that the heating that sometimes occurred with the battery was corrected.
akuma48465 said:
I have not signal after the upgrade this are the specs that I followed
1 downloaded and installed from local upgrade
2 before reboot open magisk and install masgisk in the inactive partition
3 reboot and after my device first boot I got no signal and also the settings were kind of buggy, so I reboot like 3 times and everything is okey except for the missing signal
Click to expand...
Click to collapse
What channel did you pull it from?
Sent from my HD1907 using Tapatalk
Hello guys, I also received the update via an external program to request updates, not through my device, and I am surprised that my device is slow to show updates, but I have a problem with the root file (OOS 10.0.9 magisk_patched.img) will it succeed this time because it no longer works for me after the last update I hope you answer my problem and thank you to everyone
Silly question, can an EU version of the phone (living in the UK) be transferred to the global ROM without losing functionality?
maddoguk said:
Silly question, can an EU version of the phone (living in the UK) be transferred to the global ROM without losing functionality?
Click to expand...
Click to collapse
Yes
Kollachi said:
Yes
Click to expand...
Click to collapse
Just straight forward flashing over the current ROM?
Karl said:
What channel did you pull it from?
Sent from my HD1907 using Tapatalk
Click to expand...
Click to collapse
Official update (stable) through settings
Use Canary
Sent from my HD1907 using Tapatalk
akuma48465 said:
I have not signal after the upgrade this are the specs that I followed
1 downloaded and installed from local upgrade
2 before reboot open magisk and install masgisk in the inactive partition
3 reboot and after my device first boot I got no signal and also the settings were kind of buggy, so I reboot like 3 times and everything is okey except for the missing signal
Click to expand...
Click to collapse
after apply the update once again without install magisk in the inactive partition I got my signal bars again, Im wating for the patched boot.img file of this oxygen os version to try to boot and directly install magisk
akuma48465 said:
after apply the update once again without install magisk in the inactive partition I got my signal bars again, Im wating for the patched boot.img file of this oxygen os version to try to boot and directly install magisk
Click to expand...
Click to collapse
were you have call recording module Installed ?
Snake.s9 said:
were you have call recording module Installed ?
Click to expand...
Click to collapse
yes
---------- Post added at 09:47 AM ---------- Previous post was at 09:17 AM ----------
Snake.s9 said:
were you have call recording module Installed ?
Click to expand...
Click to collapse
Now I understand Why ask that question
First I got the the magisk boot img of OS 10.0.11HD65AA and boot the file
I got root but without signal, also I update magisk to the canary channel
after turning of the call recorder module I got signal bars again thanks
I downloaded the update from the oxygen updater and installed locally, then after reading here I uninstalled the Recording module (because I had no signal) but I'm getting error when trying to access Settings (stop stopped working) I'm downloading the update file from here and reinstall it, any more guesses?
Thanks
I upgraded my wife's OnePlus 7T last night through the regular process right on the phone.
1. The phone has automatic system updates disabled through developer options.
2. Go to Magisk Manager click uninstall, select restore images, and do not reboot.
3. Go to settings on device, select system, system updates, let it update, do not reboot.
4. Got to Magisk Manager, select install next to Magisk, select install, install to Inactive Slot (after OTA), and now reboot phone.
It took a minute or so to reboot. The device booted up and everything works great, no issues at all. The only issue I have, my phone another 7T does not have the upgrade available.
Update: Forgot to mention, I am using regular Magisk 20.4 (20400) with Magisk Manager 7.5.1 (267).
agtsoul said:
I upgraded my wife's OnePlus 7T last night through the regular process right on the phone.
1. The phone has automatic system updates disabled through developer options.
2. Go to Magisk Manager click uninstall, select restore images, and do not reboot.
3. Go to settings on device, select system, system updates, let it update, do not reboot.
4. Got to Magisk Manager, select install next to Magisk, select install, install to Inactive Slot (after OTA), and now reboot phone.
It took a minute or so to reboot. The device booted up and everything works great, no issues at all. The only issue I have, my phone another 7T does not have the upgrade available.
Update: Forgot to mention, I am using regular Magisk 20.4 (20400) with Magisk Manager 7.5.1 (267).
Click to expand...
Click to collapse
Hi.
Can you explain step 2 in more detail? Is this step necessary? I have 10.0.9 rooted with Magisk 20.4 and several Magisk modules including Renovate Ice. Does step 2 delete all modules? Do I need to uninstall them manually before step 3? I read Renovate Ice hasn't been updated yet to be compatible with 10.0.11 yet.
Starzboy77 said:
Hi.
Can you explain step 2 in more detail? Is this step necessary? I have 10.0.9 rooted with Magisk 20.4 and several Magisk modules including Renovate Ice. Does step 2 delete all modules? Do I need to uninstall them manually before step 3? I read Renovate Ice hasn't been updated yet to be compatible with 10.0.11 yet.
Click to expand...
Click to collapse
From my understanding, step 2 just restores the patched boot image to the regular boot image. However, you still have root access because you have not rebooted yet. I did not delete or disable any modules on my wife's phone. She is only running systemless host for AdAway. I still have not received the update on my phone. But, the only modules I run on it are sytemless host and YouTube Vanced black themed v14.21.54.
Do you have new clocks in settings->lockscreen?
akuma48465 said:
after apply the update once again without install magisk in the inactive partition I got my signal bars again, Im wating for the patched boot.img file of this oxygen os version to try to boot and directly install magisk
Click to expand...
Click to collapse
I recently also got the 10.0.11 OTA update on the Global variant. While it was downloading and installing, a snuck a copy of it off the phone and extracted the image files from it.
the unpatched and Magisk Patch bootimage can be found here: Google Drive OnePlus 7T HD65AA Global v10.0.11
Note, this one was patched using the latest (at the time) canary build of Magisk (cd6eca1d) 20415.
Cyberstorm
arindam112 said:
Do you have new clocks in settings->lockscreen?
Click to expand...
Click to collapse
I don't see any new clocks.
Hi all I got a 7T in the US. I got an update notification, and i wanted to uninstall Magisk, perform the update, reinstall Magisk and reboot. In Magisk I get the message, "stock image does not exist." I never had this problem with my Pixel, how can I get Magisk to save an image after I update and reroot?
Thanks
Droid_Nut said:
Hi all I got a 7T in the US. I got an update notification, and i wanted to uninstall Magisk, perform the update, reinstall Magisk and reboot. In Magisk I get the message, "stock image does not exist." I never had this problem with my Pixel, how can I get Magisk to save an image after I update and reroot?
Thanks
Click to expand...
Click to collapse
Why do you want to uninstall magisk?
1. Install update and don't reboot.
2. Go to magisk and install after ota
3. Reboot
I don't know about restore stock image with magisk and never did that.
If you really want to unroot your phone now, download the correct boot.img and flash it. There are a few threads available here to find that image you need.
Also you can download the ota.zip and dump that payload.bin which is inside the zip.
Like kollachi said, you don't need to follow the standard pattern of uninstall/ota/install-inactive with the 7t. I imagine that's because with a rooted device, it pulls the full rom instead of a diff.
But it sounds like you directly flashed a rooted boot.img which is why magisk doesn't have a backup. Instead, you should have done a `fastboot boot patched_boot.img` and then done a magisk install. It would have taken a backup of your original boot.img and then installed a patched version.
So basically install the Ota right over root, open magisk manager and install root, then finally reboot?
With the pixels and others, you have to uninstall magisk with restore boot image, install the update, install magisk again, then reboot.
Thanks for all of the help.
ziddey said:
Like kollachi said, you don't need to follow the standard pattern of uninstall/ota/install-inactive with the 7t. I imagine that's because with a rooted device, it pulls the full rom instead of a diff.
But it sounds like you directly flashed a rooted boot.img which is why magisk doesn't have a backup. Instead, you should have done a `fastboot boot patched_boot.img` and then done a magisk install. It would have taken a backup of your original boot.img and then installed a patched version.
Click to expand...
Click to collapse
I installed magisk with twrp, the twrp that you boot off of pc into temporary memory.
it's the same procedure you're used to. you just don't need to uninstall first since it's a full ota instead of a diff
Just wondering, will it back up my new stock boot image after the update, and the install from Magisk Manager?
Droid_Nut said:
Just wondering, will it back up my new stock boot image after the update, and the install from Magisk Manager?
Click to expand...
Click to collapse
No I don't think so. I can't find anything on my phone.
Kollachi said:
No I don't think so. I can't find anything on my phone.
Click to expand...
Click to collapse
I guess it really does not matter, considering we don't have to uninstall root.
yes it does..
backups are saved to /data/magisk_backup_<hash>/boot.img.gz
I have one for every time I've (re)installed magisk
ziddey said:
yes it does..
backups are saved to /data/magisk_backup_<hash>/boot.img.gz
I have one for every time I've (re)installed magisk
Click to expand...
Click to collapse
I still do not have a backup I did the OTA, and then reinstalled Magisk "Direct Install (Recommended)", but I guess I should have picked "After OTA to slot A or B" as I had no root on reboot. So I had to TWRP it back to root.
Lots to learn, but I am gaining. :good:
Droid_Nut said:
I still do not have a backup I did the OTA, and then reinstalled Magisk "Direct Install (Recommended)", but I guess I should have picked "After OTA to slot A or B" as I had no root on reboot. So I had to TWRP it back to root.
Lots to learn, but I am gaining. :good:
Click to expand...
Click to collapse
Yep the correct way is install after ota.
Droid_Nut said:
I still do not have a backup I did the OTA, and then reinstalled Magisk "Direct Install (Recommended)", but I guess I should have picked "After OTA to slot A or B" as I had no root on reboot. So I had to TWRP it back to root.
Lots to learn, but I am gaining. :good:
Click to expand...
Click to collapse
I mean you did that last time and it didn't backup your boot. Fair to assume you'll get the same results if you do it again.
When you install to inactive next time, it should create a backup since the boot image will be intact
With the Pixel it always recommended install to inactive slot and I went with what was recommended.
With the Pixel it always recommended install to inactive slot and I went with what was recommended.
Hi,
I was trying to update my OnePlus 7t to 10.3.3HD65AA but I am not able to do it. This is what I am doing
1) downloading the update package from oxygen updater application
2) going to setting then in system update I am clicking on more option and then on selecting local update then selecting the package waiting for upgrade to complete.
3) now going to magisk manager and installing the manager in inactive slot and rebooting the device
The phone gets reboot but doesn't update also attaching my magisk log here
Hi,
I was trying to update my OnePlus 7t to 10.3.3HD65AA but I am not able to do it. This is what I am doing
1) downloading the update package from oxygen updater application
2) going to setting then in system update I am clicking on more option and then on selecting local update then selecting the package waiting for upgrade to complete.
3) now going to magisk manager and installing the manager in inactive slot and rebooting the device
The phone gets reboot but doesn't update also attaching my magisk log here
jazzy ╰_╯ said:
Hi,
I was trying to update my OnePlus 7t to 10.3.3HD65AA but I am not able to do it. This is what I am doing
1) downloading the update package from oxygen updater application
2) going to setting then in system update I am clicking on more option and then on selecting local update then selecting the package waiting for upgrade to complete.
3) now going to magisk manager and installing the manager in inactive slot and rebooting the device
The phone gets reboot but doesn't update also attaching my magisk log here
Click to expand...
Click to collapse
I used method 3 to root my 7T a while back and did the update from 10.0.9 to 10.0.11 this morning. Did you do the full update? AFAIK the incremental update won't work
Used Oxygen Updater to download the update (DO NOT FOLLOW THEIR INSTALLATION INSTRUCTIONS)
Did local upgrade from Settings/System/System updates (options wheel) DO NOT REBOOT
Opened Magisk Manager and did a direct reinstall of Magisk (not manager) then
Installed Magisk into inactive slot
Reboot.
Hello guys.
Unfortunately the today Magsik Update doesn't run very well on my Device. I did update to the available slot then reboot but the bootsplash now runs since 1H without being able to land on OOS. I'm on 11.2.5.5.LE15 BA + Omega Kernel latest build
Fastboot mode doesn't report any bootloader version nor baseband version.
What's the best way to repair that ? What was the mistake I did to prevent further error while I'm updating magisk or the Kernel ?
Ty @avid_droid but that's what I tried first. It leads me to the exact same type of Boot where nothing happens for 30 minutes excepts the bootsplash logo animation.
I did try to boot from the vanilla boot.img ... but that sent me directly to crashdump mode.
I then boot one last time to magisk_boot.img and .... it worked.
For some reasons everything was wiped on the device even if I never wipe anything from fastboot but no matter ... I'm now back in OOs and try to set it up completly
It's not Magisk, I updated to version 23 with no issues at all.
Also flashed the new Omega kernel afterward, no issues with that either, Magisk was still retained.
I would see if you can get into recovery, if you can then do a system reset and see if the phone will let you set it up again.
For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^
Fre$h said:
For my own knowledge, when you're on a custom Kernel, and want to update Magisk, do I need to make something specific ? Does the custom kernel need to be cleared or something like that ?
I jumped on Omega Kernel yesterday and everything was super fine.
The only thing I did this morning was to update Magisk : I choose to update to the available slot but maybe that was my error because this choice is more to use after an OTA update isn't it ?
Btw ty guys for your super clear answer. Coming from HTC where I did have every skill needed to figure everything, I have to learn a bit more to handle everything in the O+ world ^^
Click to expand...
Click to collapse
I did it the other way round, updated Magisk app, then Magisk itself, rebooted the phone. Installed the latest kernel using EX Kernel manager, it noted that Magisk was there so re-applied it on the new kernel, then rebooted and it was fine after that.
I'm not using any Magisk modules though, not going to risk that until we have a good recovery.
avid_droid said:
Same here. I keep magisk modules to a minimum. I am however playing with substratum and we know how that usually ends up haha. Giving it a go. Trying to remember the signal icons I used to use
Click to expand...
Click to collapse
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either
djsubterrain said:
I always use the substratum recovery zip that gets saved but we have nothing to flash that with yet either
Click to expand...
Click to collapse
Liv dark works now on op9pro OS11.. I'm using several different themes from livDark now
All I need to do here just hit "install"?
Ive never done it before so I just don't want to screw up.
First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update
Fre$h said:
First thing to do is to update the magisk manager itself. Once updated it will show you the magisk update 23. Click on install and chose the recommanded way, aka direct install.
My mistake was to chose install to the available slot which is more dedicated to reflash magisk after an OOs's OTA update
Click to expand...
Click to collapse
Thx bro...all good
This is particularly here we miss TWRP to flash magisk uninstaller properly. I like the way we can temporary boot from rooted boot.img but the disadventage is that we need a computer just near us to do that.
Hope everything is now fixed