Question Magisk Update doesn't run very well :(

Question Magisk Update doesn't run very well :( - OnePlus 9 Pro

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

Related

Nexus 5X bricked trying to root via TWRP (SuperSu)

Hi,
Googled a while and looked around in the forum but did not find anyone with the exact same issue as me so here goes.
Maybe someone could tell me where exactly I am doing wrong.
I have a LG Nexus 5X, latest Oreo 8.1 official update.
I want to install a custom kernel to improve performance and/or battery life.
Never rooted or anything like that so I googled around to know what to do.
So I unlocked the bootloader and flashed the latest TWRP custom recovery (v3.2.1-0).
The first strange thing unlike what I kept reading in tutorials and forums is that, although I did reboot directly into recovery after flashing TWRP, and completed flashing TWRP using its interface, I was never able to reboot into TWRP unless I flashed it again. As if TWRP could not avoid being overridden by the stock recovery. So to get back to TWRP I always have to:
reboot into the bootloader: adb reboot bootloader
flash TWRP: flash recovery twrp-3.2.1-0-bullhead.img
reboot bootloader: fastboot reboot
immediately start into to bootloader (power + vol down)
choose 'Recovery Mode' from there
Which seemed odd, that TWRP wouldn't 'stick', although I was not root yet.
Which gets me to the second part. All I wanted was to root my phone.
So after not finding a consistent way to do it - it seemed every website I visited gave me slightly different instructions to do so, I took the chance and did the following:
download latest SuperSU flashable zip file (v2.82) and copy it to internal storage
go through the process I describe in the list above to get into TWRP
install SuperSU zip file (via Install TWRP option, logs seemed ok, warned me it would take a while to boot again)
reboot, wait until it boots
But the phone got stuck in the boot screen - OS does not start to load - for at least half an hour.
Luckily, probably because the OS did not load, TWRP was not overridden and so I have access to it.
My main problem at this point is that, as a newbie on this, I am not sure what can I do in TWRP to try to restore the OS.
I have tried to restore a Nandroid backup I performed before all this, and also tried to Wipe Data / Cache and Dalvik.
Both did not work - OS still won't load.
What can I do at this point? Wipe System partition? Wouldn't that delete my Nandroid backup?
Maybe 'sideload' (not sure if the right term) an official google image for my Nexus?
Sorry again if questions like this can be easily found around the forum, but from the threads I checked I did not bump into the exact same scenario...
Thank you in advance

So in the meantime I have wiped system partition, no success either.
Ended up restoring my Nandroid backup and sideloading the latest OTA from Google, which successfully restored my phone.
Of course TWRP was overridden once again.
So back to the start: can anybody help me out on the best way to permanently flash TWRP and root the phone?
Thanks!

Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)

jbaumert said:
Forget SuperSU - Use Magisk to root your phone. As for TWRP getting overwritten - any time you take an update from Google, it will generally (if not always) restore the stock recovery. The way to get around that is to download the entire current update from Google and then use fastboot to flash the individual parts (system.img / boot.img / radio.img / vendor.img)
Click to expand...
Click to collapse
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?

disacrol said:
Well yes, the last time I expected TWRP to be gone since I have applied the whole image, and I wouldn't expect otherwise. My problem is that TWRP is always getting overridden each time I reboot my phone. Do you have any idea why?
Regarding Magisk, I will look around to see how to use it. Could you point me in the right direction?
Also I think I read somewhere that the kernel I wanted to flash in the end - Franco's Kernel - required SuperSU and did not work with Magisk. Am I wrong?
Click to expand...
Click to collapse
Here's the guide stickied that should walk you through the TWRP install. https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
As for Magisk. There is a whole forum dedicated to it - https://forum.xda-developers.com/apps/magisk - Short story install the latest stable version (16.0) and call it good. I haven't had any issues with recent kernel builds including Franco, EX, etc.... One thing to keep in mind is that Magisk always gets flashed after the kernel install as it does some patching of the boot.img as part of its process.

jbaumert said:
Just curious you are using "fastboot flash recovery ....." and not "fastboot boot recovery...."? The "boot" method doesn't do the install.
Click to expand...
Click to collapse
Yes, flash, not boot.
Thanks a bunch for all your help. I didn't meant to be lazy to start by reading sticked topics, but it's so much new information for a newbie that I didn't exactly know where to start. Thanks again for sharing the links.

I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'm not sure if you got this fixed. But if not, first fastboot boot twrp. Then flash supersu or magisk. Then boot back into the bootloader from twrp and fastboot flash twrp. That'll solve the problem.
Click to expand...
Click to collapse
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..

disacrol said:
I tried that but I'm getting no luck with SuperSU, always gets me in a bootloop (actually, technically not a loop since it remains Frozen with the Google logo)
I'll give magisk a try and come back with feedback. Maybe it has something to do SuperSU incompatibility with Oreo 8.1..
Click to expand...
Click to collapse
What version of super su are you using? Use 2.82 SR 3 or 5
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
What version of super su are you using? Use 2.82 SR 3 or 5
Click to expand...
Click to collapse
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.

disacrol said:
V2.82 Stable, not Service Release. Is the last stable not compatible with Oreo? Official website is not specific about it, so I just assumed it was ok.
Click to expand...
Click to collapse
3 or 5 work on Oreo. I'm not sure about stable. I don't use it.
Sent from my [device_name] using XDA-Developers Legacy app

SR5 worked like a charm. I just wish there was a compatibility matrix somewhere in their website to avoid so many forum threads and misinformation on the subject and avoid all the hustle. The whole process is dead simple but it took me days and tailored help from you guys to figure this one out.
Thanks again to all of you for your assistance.

i had that issue with a nex 6 and flashing supersu fixed it. when i got a 6p i tried the same and get stuck on the boot logo and had to sideload factory firmware to get back to go. i have a 5x on the way maybe i will try magisk.

so after i flash twrp reboot the bootloader, i open twrp and flash supersu sr5 and all is well, no more disappearing act for twrp and no more stuck on the "google"?

Root & Xposed on WW_17.1810.1910.73 & Update WW_17.1810.1911.110

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!

Can Android 10 beta be rooted?

If it can, how? I'm having bootloop issues trying to do that. Thank you.

Bootloop in logo S9

RpRAUC said:
Bootloop in logo S9
Click to expand...
Click to collapse
follow up

Piereligio said:
If it can, how? I'm having bootloop issues trying to do that. Thank you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s9/how-to/one-ui-2-beta-rooting-installing-twrp-t4012961

https://forum.xda-developers.com/ga...rooting-installing-twrp-t4012961/post81084623
The patched kernel contained here was the solution for me

S9 ROOT
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q

viktorvlahov11 said:
I did it.I flashed twrp format data and and installed SoldierR9312 mod. lock screen,samsung account and magisk root all work
http://www.renovate-ice.com/soldier9312/#stable_g96x-q
Click to expand...
Click to collapse
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.

it stucks for me on the samsung logo

aidenpearce296 said:
it stucks for me on the samsung logo
Click to expand...
Click to collapse
Try flashing the twrp flashable firmware it may fix your problem
---------- Post added at 08:41 AM ---------- Previous post was at 08:37 AM ----------
viktorvlahov11 said:
Try flashing the twrp flashable firmware it may fix your problem
Click to expand...
Click to collapse
Piereligio said:
This worked great, thanks. Only issue I met was that I couldn't see the OEM unlock switch, so it didn't let me to flash TWRP from Odin (even though it was already unlocked), giving me "only official released binaries are allowed to be flashed(recovery)" error.
The solution for that was following these steps: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
EDIT: no wait, maybe it's bootlooping.
EDIT2: yes it is. I'm using italian carrier, you?
EDIT3: at the end I created a custom boot.img by using Magisk and I flashed it. In this way I kept encryption and stock recovery, but this doesn't give me write permissions in /system. But I do have root.
Click to expand...
Click to collapse
I got it to work on a Bulgarian unlocked model
Maybe try flashing the twrp flashable firmware after the mod

omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it

viktorvlahov11 said:
omg it was so easy!
after you flashed twrp and formated data you just have to flash magisk and that's it
Click to expand...
Click to collapse
I done that, but still stuck on SAMSUNG logo, no boot loop or what. I was waiting 10min, nothing happened.
Any advice?

Hi there,
after having tried different methods to root my S9, which has updated to Android 10 One UI 2.0 this morning, maybe the solution that finally worked for me will help you too.
First I tried to root just like in Pie, as found on the net: flashed TWRP 3.2.3 via Odin, then flashed Magisk with TWRP plus this no-verity-opt-encrypt. Got stuck in bootloop, tried different no-verity/dm-verity versions, Magisk 18.x and Magisk 20.1. Nothing worked, got stuck again every time i rebootet the system again.
Then, after realising that I CANT get back to Android 9 (old rom wasnt Odin flashable anymore, phone didnt boot, BSoD), I first downloaded the new stock rom and bootloader as zip, got it from here:
https://forum.xda-developers.com/showpost.php?p=81615561&postcount=1830.
You have to check if that fits with your version / phone. Once downloaded, I copied both onto my SD card. So now I was able to install at least the new clean stock rom. Oh, and now I used the TWRP version 3.3.1.
Then I found this:
https://forum.xda-developers.com/galaxy-s9/development/root-s9plus-exynos-android10-t4065343
At first I tried to root without the SoLdieR9312's mod, only with MAGISK 20.3 and no-verity. Stuck again, it only bootet to download mode, nothing else. So flashed again the clean stock rom, and after first not keeping the right order (I suppose) I finally followed EXACTLY the instructions 1 - 4 in above manual including SoLdieR9312's mod (I highly recommend first a complete Wipe, format data, and then flash the clean new Rom with Android 10 and bootloader from above link).
Now, to save you the time I spent today: once your phone is bootet (and succesfully rooted via Magisk 20.3, which will happen automatically due to the SoLdieR9312's mod), DONT LET MAGISK UPDATE TO VERSION 20.4!!!! Magisk Manager asks you to update, but when I did update to 20.4, everything fell apart again, it only bootet to download mode.
Now I seem to have it stable and running with 20.3 and the [email protected]. I rebootet 5 times so far just for the sake of it, and it works fine and rootet.
If I can be of further help, please let me know. I spent the last 12 hours on this matter, so dont hesitate.
Greetz from me minus a bunch of nerves
PS: After I wrote the above, I deleted the Knox family in the rootet system, and then it collapsed again and, after BSoD, it only rebootet into download mode. I can not exclude the possibility, that this might have been the reason for some system breakdowns before, as I had to re-do the wipe-clean-install-then-root-then-customize worksteps aroung 8 times yesterday before it was stable as it is now. Now I´ll leave Knox on it, though that itches me a bit. But I´m exhausted for now
PPS: IMPORTANT when I try to create a PIN or a pattern for the lock screen, phone reboots to SIM card PIN screen and then keeps rebooting and rebooting. It looks like there are some interferences with root and PIN / security. I did NOT create a Samsung account, only a google one, cause in the beginning i suspected it might have been a Sam acct problem (I constantly couldnt log into it on the phone). Turns out that might not have been the case, rather a prob between root and setting a lock screen security.

TWRP temporary?

I'll have my new OP7T by Friday, coming from OP5T. I've been reading through some of the threads. Is it correct that TWRP doesn't survive a reboot? Or is that old news?
That might be fine for me. I don't flash roms nearly as much as I used to and I think stock rooted is the way I'll go from now on.
So if I unlock the bootloader, install TWRP and root... can I then receive Ota updates?
That'd be pretty awesome.
***Also I'm tempted to flash a custom rom despite what I said . So if anyone knows of a stable one that performs well as a daily driver, please respond. Thanks

KLit75 said:
I'll have my new OP7T by Friday, coming from OP5T. I've been reading through some of the threads. Is it correct that TWRP doesn't survive a reboot? Or is that old news?
That might be fine for me. I don't flash roms nearly as much as I used to and I think stock rooted is the way I'll go from now on.
So if I unlock the bootloader, install TWRP and root... can I then receive Ota updates?
That'd be pretty awesome.
***Also I'm tempted to flash a custom rom despite what I said . So if anyone knows of a stable one that performs well as a daily driver, please respond. Thanks
Click to expand...
Click to collapse
Hi! If you BOOT twrp it will not survive a reboot, if you FLASH twrp it will still there till you reflash stock recovery or rom update. You can't receive OTA "upgrade" package with root, only full rom, maybe through oxygen updater.
And last, i've flashed Resurrection Remix this saturday, and it's amazing. Battery performance like stock oos (about 5/5:30h sot against the 4h sot of my previous op6), 90hz display and infinity customization to choose from. You're not going wrong if you try RR, trust me. RR on my "old" oneplus 6 was not like this. Here there's no bug at all and you can customize everything. Only thing that i miss is Dolby Atmos (it's still there but you can't personalize sound effect WIP in next release) and per-app lock with FP (not really a great miss).
I hope to be proved helpful

Hitman478™ said:
Hi! If you BOOT twrp it will not survive a reboot, if you FLASH twrp it will still there till you reflash stock recovery or rom update. You can't receive OTA "upgrade" package with root, only full rom, maybe through oxygen updater.
And last, i've flashed Resurrection Remix this saturday, and it's amazing. Battery performance like stock oos (about 5/5:30h sot against the 4h sot of my previous op6), 90hz display and infinity customization to choose from. You're not going wrong if you try RR, trust me. RR on my "old" oneplus 6 was not like this. Here there's no bug at all and you can customize everything. Only thing that i miss is Dolby Atmos (it's still there but you can't personalize sound effect WIP in next release) and per-app lock with FP (not really a great miss).
I hope to be proved helpful
Click to expand...
Click to collapse
Thanks for the explanation!
Sorry I'm still unclear on TWRP. I remember years ago I had a device that would not allow TWRP to stick. If you needed to flash a rom or make changes to system, you'd hook it up to your computer and use adb to boot TWRP one time.
But that was because twrp wouldn't stick. Why would you boot TWRP if you are able to make it permanent by flashing it?
I'm sure there's a simple explanation but I can't think of it...
Ideally I think I'd keep the stock recovery with root, then remove root for an update and root again. But pretty sure the only way to root is to have TWRP installed.
Thanks again for the info!

KLit75 said:
Thanks for the explanation!
Sorry I'm still unclear on TWRP. I remember years ago I had a device that would not allow TWRP to stick. If you needed to flash a rom or make changes to system, you'd hook it up to your computer and use adb to boot TWRP one time.
But that was because twrp wouldn't stick. Why would you boot TWRP if you are able to make it permanent by flashing it?
I'm sure there's a simple explanation but I can't think of it...
Ideally I think I'd keep the stock recovery with root, then remove root for an update and root again. But pretty sure the only way to root is to have TWRP installed.
Thanks again for the info!
Click to expand...
Click to collapse
With oos I was usually boot with twrp only for flashing magisk, in that case i don't really need it beside for flashing root. With RR I keep twrp flashed only "to have it" not really useful. I understand what you said, with old partition system root gone away without twrp because recovery.img was inside boot.img (magisk destination partition, and for decryption things) but with Android 10 these partitions are separated again, like old times.

Hitman478™ said:
With oos I was usually boot with twrp only for flashing magisk, in that case i don't really need it beside for flashing root. With RR I keep twrp flashed only "to have it" not really useful. I understand what you said, with old partition system root gone away without twrp because recovery.img was inside boot.img (magisk destination partition, and for decryption things) but with Android 10 these partitions are separated again, like old times.
Click to expand...
Click to collapse
I think I'm following you. So if I want to remain stock but rooted, I would just boot twrp, root it, then repeat that if I want to take a stock update?
To simplify, I guess, is it possible to run a rooted stock with a stock recovery?
Sorry. I've been tinkering with my phones less and less, and some things have changed in that time.

Take the update, DO NOT REBOOT YET! Then install Magisk from the Magisk manager. When it says to select method, choose to "Install to Inactive Slot (After OTA)" , then reboot.
No TWRP needed after an update to install root.

KLit75 said:
I think I'm following you. So if I want to remain stock but rooted, I would just boot twrp, root it, then repeat that if I want to take a stock update?
To simplify, I guess, is it possible to run a rooted stock with a stock recovery?
Sorry. I've been tinkering with my phones less and less, and some things have changed in that time.
Click to expand...
Click to collapse
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files

Hitman478™ said:
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files
Click to expand...
Click to collapse
Thanks. I used to change roms constantly a few years back. Now my phone has become something I can't get by without, for even a matter of hours on some days. So as much as I love trying things out, I just want a stable driver with little fuss. But I don't think I can go without root. I haven't since 2013.
OOS was good enough for me, though I heard theyre becoming more bloated and I hate the gestures in Android 10. It's those little things that I want to be able to change.
Do you use the modified magisk boot image to root?

KLit75 said:
Thanks. I used to change roms constantly a few years back. Now my phone has become something I can't get by without, for even a matter of hours on some days. So as much as I love trying things out, I just want a stable driver with little fuss. But I don't think I can go without root. I haven't since 2013.
OOS was good enough for me, though I heard theyre becoming more bloated and I hate the gestures in Android 10. It's those little things that I want to be able to change.
Do you use the modified magisk boot image to root?
Click to expand...
Click to collapse
Yes I'm just like you, I use my phone constantly for work, I can't accept a rom with FC and other bugs.. I need that things working properly and RR it's exceptional.
Yes I was using modified boot.img for rooting OOS, selfmade with guide in the thread because my phone is the BA version (europe) and everytime no one post boot.img ready for this. But it's not really complicated to DIY

Hitman478™ said:
Yes it's possible to run rooted stock without twrp, I was like that before flashing RR
If you want to root still after ota don't reboot when it had finished to install, instead go to magisk and choose "install on inactive slot after ota" then reboot.. But with this process I highly suggest you to disable and uninstall all module first, because sometimes, when you reboot you got problems if you don't remove modules, and for "problems" I mean like instant reboot after phone boot up, forcing you to uninstall magisk via recovery or reflashing stock boot.img
Btw, twrp is useful on custom because if you go in boot loop you can access your internal storage through it and eventually make a backup of all your files
Click to expand...
Click to collapse
I do not disable or uninstall modules with this method. But I will in the future, it only takes one OH SH!T moment, before you wish you did. My luck is bound to run out.

Droid_Nut said:
I do not disable or uninstall modules with this method. But I will in the future, it only takes one OH SH!T moment, before you wish you did. My luck is bound to run out.
Click to expand...
Click to collapse
:laugh: I've passed too much "bad moments" with update and magisk, so now prevention is my cure

General 11.2.7.7.LE15AA Rolling Out

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)

Develop Bugs

welcome