Related
Hi all,
I've updated my 3xl to the december update like usual, flash-all.bat without -w. Afterwards, it boots fine, and in settings it clearly states that I'm running the December security patch.
However, when I boot into twrp (not installed) and flash magisk, android boots to just before asking my SIM PIN, says "Shutting Down", then reboots and gives me the message "Can't load Android System. Your data may be corrupt." etc. inside stock recovery.
Did the December update somehow break magisk? Anyone gotten it to work? I'd rather not do a factory reset if it's not needed.
Works fine for me.
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Working fine for me as well.
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
mikepopo99 said:
Try re-flashing the December update with the - w deleted see if it boots up. Then try flashing magdisk manually on bkth a and b partitions
Click to expand...
Click to collapse
jd1639 said:
I would try flashing the stock boot and system images to both slots. It probably won't work but worth a try before doing a factory reset.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
TonikJDK said:
You have a corrupt backup copy of boot.img, Magisk grabbed that and used it for root.
Flash the stock boot.img to both slots and reroot.
Click to expand...
Click to collapse
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Flash the stock boot.img to both slots.
Reboot and check it.
Copy the Magisk zip to your phone.
Fastboot boot the TWRP img file, don't install it.
Use TWRP to install the Magisk zip, and you are done.
RogerXIII said:
First off, thanks for trying to help!
Flashing the stock boot.img "solves" the problem, I can boot and use the phone like normal, but without root obviously. Using the stock boot.img inside magisk manager to patch it with 17.3 and flashing that boot image to both partitions gives me this error again. I've also tried re-applying the December update at least 3 more times, with the same result. Any other ideas?
Click to expand...
Click to collapse
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
RogerXIII said:
Thank you so much, this worked!
Instead of going back an Android version, I used this script, uninstalled all modules and re-flashed Magisk. It works perfectly now. Thanks again!
Click to expand...
Click to collapse
Good deal. That is why I always keep a copy of the Magisk uninstaller on the phone itself. As long as I can get to BL/temp TWRP .img, the worst I am out is the time it takes me to reconfigure Magisk.
RogerXIII said:
However, when I boot into twrp (not installed)
Click to expand...
Click to collapse
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Shaftamle said:
What do you use to get TWRP going when it's not permenantly installed? Just curious?
Fire Hound 8.1
Click to expand...
Click to collapse
The TWRP image from the official website, and then simply fastboot boot twrp.img
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
Ok cool. Wasn't sure if there was an app like fashify or something.
Fire Hound 8.1
sliding_billy said:
Do you have the previous version of Edge Sense Plus module installed? That sounds exactly like what happens if you install Magisk with that module still there. He put out a new one today.
Click to expand...
Click to collapse
you are godsend my friend.
Touz604 said:
you are godsend my friend.
Click to expand...
Click to collapse
Glad you got it figured out.
RogerXIII said:
The TWRP image from the official website, and then simply fastboot boot twrp.img
Click to expand...
Click to collapse
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
You ca't yet.
bbs3223474 said:
How can we boot the twrp from fastboot?
The one from official website doesn't support Android 10 I believe and I failed with the info says "too many links".
Click to expand...
Click to collapse
Thread is from 2018
I am gonna check the official TWRP website for the workable TWRP for my Pixel 3 till I see your post
wangdaning said:
Thread is from 2018
Click to expand...
Click to collapse
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!
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
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)