Hello all,
I tried to upgrade from Pie to Android 10 with xXx NoLimits and SmurfKernel but I have run across an issue I've seen before. Anyway, when I reboot into Recovery, it says I have nothing on my storage (0MB).
Someone mentioned to flash OOS to the second slot but I'm not sure how to do that because on Slot A (current), it says 0MB and when I try to change to Slot B, it says unable to mount /data and still shows 0MB. They also mentioned it's because I'm not on the latest A10 supported TWRP but when I use that version, it never wants to decrypt my storage.
Here are the steps I took..
-Ran xXx NoLimits Uninstaller & Magisk Uninstaller
- Booted into TWRP
- Flashed A10 OOS Stable
- Flashed TWRP Installer
- Rebooted to Recovery
- Flashed Magisk v19.4
- Rebooted to System
- Flashed xXx via Magisk
All looked well. I then rebooted to Recovery but it's saying my storage is at 0MB (empty).
Any ideas? Thanks!
Update twrp to TWRP 3.3.1-70 Unified Unofficial Q by mauronofrio.
Toni Moon said:
Update twrp to TWRP 3.3.1-70 Unified Unofficial Q by mauronofrio.
Click to expand...
Click to collapse
That's the thing.. I've always had issues with his TWRP versions not decrypting my storage even when I completely remove all security settings and/or putting in my PIN I use to unlock my phone.
your sequence of flash it's wrong and xxx nolimits always must e flashed from twrp.
flash oos + twrp two times, reboot to twrp
flash magisk
flash smurf kernel
reboot to system to see if boots, reboot to twrp
flash xxx nolimits
Toni Moon said:
your sequence of flash it's wrong and xxx nolimits always must e flashed from twrp.
flash oos + twrp two times, reboot to twrp
flash magisk
flash smurf kernel
reboot to system to see if boots, reboot to twrp
flash xxx nolimits
Click to expand...
Click to collapse
I have to start from scratch with this though, right? The reason why I ask is because the way my TWRP is bugged right now, it's as if it doesn't have root access therefore I can't flash anything as it says it cannot mount /data.
Also, I am worried about using TWRP 3.3.1-70 Unified Unofficial Q by mauronofrio because as mentioned before, it doesn't decrypt my storage even with the correct information put in or security settings being completely disabled.
Related
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Post #3 has the instructions you need
Long story short you need to flash the update via TWRP.
unknown00 said:
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
Click to expand...
Click to collapse
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
RASTAVIPER said:
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
unknown00 said:
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
Click to expand...
Click to collapse
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Like above.
Flashing ROM Will also flash stock recovery so after ROM you need to flash twrp again,if you reboot without it it's lost.
Also why magisk isn't flashed right away is because: when you choose to reboot to twrp after the twrp flash it Will change slot, this way you Will get magisk on the correct slot.
All this can be done from the OS.
Install the ROM upgrade as usual,don't reboot.
Open magisk app
Search for a module a/b twrp (you Will only find one module) and install it.ndont reboot just yet.
Go to main screen of magisk
Press install, install, install to inactive slot (after OTA). After this install you can reboot.
Both works, I find the twrp way to be more convenient
I don't about stable i am on open beta 10 i root every beta without twrp using patch boot image i got update every time around 1.5 GB because i am rooted after update i just lose root everything same before update phone not wipe anything
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
akxak said:
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
Click to expand...
Click to collapse
No need to reinstall TWRP in the first method?
unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
I do not have TWRP installed, it is basically not necessary as OOS can be updated with the settings/manual update tool and Magisk can be reinstalled via Magisk manager.
I had to use TWRP solely to downgrade to Magisk 17.2 from Magisk 18 as this cannot be done with Magisk Manager. But for that purpose, it's enough to temporarly make TWRP available via fastboot boot command without permanently installing it.
If you have TWRP and want to keep it, that easy process doesn't work to upgrade the OS.
unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
If you wanna keep TWRP you do the way I described few posts up.....
tabletalker7 said:
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Click to expand...
Click to collapse
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
thejase said:
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
Click to expand...
Click to collapse
As promised, I'm writing back with my findings. I believe some enabled module in magisk was the issue. What I did was uninstall magisk 18 with the latest uninstaller. Thinking it was V18 itself that was the problem, I then proceeded to install v17.3 on both slots (reboot to recovery in betweene). This worked and booted! It started to occur to me that I had not disabled any of my modules before installation of the rom/magisk. This is a big mistake as a lot of magisk modules are still using old formatting and cause new installations to fail if left enabled. Since an uninstall also disables all modules, I believe using 17.3 was not necessarily the solution but rather either disabling modules before an install, or uninstalling whatever version magisk was installed to begin with (which essentially disables/uninstalls those modules anyway). After installing 17.3 and getting it to boot, I just updated via magisk manager to v18 with no issues to speak of! Now comes the part where I need to remember all the installed modules I had and test them one by one.
For uninstallation of modules in twrp, you can use https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 Or https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
I hope this helps someone!
Hi
In every rom thread I see about a million different answers on how to properly install the rom. Usually the official instructions are very vague. I've been flashing roms for years but this ab partition is very confusing to me. I just got my oneplus 6 a few days ago. It would be great if someone very knowledgeable in how to do this could make a how to guide for both stock and custom roms. I think it would really help everyone and threads for each rom wouldn't be full of people asking it over and over (and getting different answers). Thank you devs for all that you do.
Custom if you don't know if you have the recommend base installed to both slots:
Flash OOS
Flash twrp
Reboot to twrp
Flash OOS
Flash twrp
Reboot to twrp
Wipe data, dalvik cache
Flash custom
Flash twrp
Reboot to twrp
Flash gapps
Flash magisk
Boot system
Custom update:
Flash updated custom rom
Flash twrp
Reboot to twrp
Flash gapps (not needed, but updated gapps is most likely better to use anyhow..)
Flash magisk.
From custom back to OOS:
Info: Format data needed because you will trigger encryptionsince you're on different securety patch. This is also the same way to go from beta branch of oos to stable since the securety patches is lower (in general) on stable.
How to:
Boot twrp
Plug phone in to pc and take backup of everything
When done format data
Transfer oos, twrp, magisk to phone
Flash oos
Flash twrp
Reboot to twrp
Flash magisk
Update oos from... Let's say 9.0.4 to 9.0.5
From Twrp:
Flash oos
Flash twrp
Reboot to twrp
Flash magisk
Boot
From oos:
Use ota update, let it install until it asks you to reboot.. DON'T DO IT.
instead go to magisk and search for "a/b" one module will be found, install it. DON'T REBOOT
Go to main screen of magisk and press install, install, install to inactive slot (after ota) when it's done you can reboot.
General ****ups:
Don't boot after update?
Flash magisk uninstaller
Try to boot (yes.. Without magisk)
If it boots you know it was magisk issue, most likely you had substratum overlays installed or modules that messed it up.
Reboot to twrp and flash magisk again and set up your modules one by one or apply themes or whatever you do with your root.
Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Not sure what to do at this point. Any ideas?
Thanks!
mobbdeep said:
Hello,
I have come across an issue with my OP7Pro and Magisk/TWRP. I got a notice of an update for Magisk & Magisk Manager and instead of flashing the update, I just clicked "Update" inside the Magisk app. After I did that and rebooted the device, I noticed I can no longer select "Recovery Mode" in the side menu; it's there but when I click it, it reboots to the Bootloader/Fastboot Mode instead. My first instinct was just to go ahead and flash TWRP img which is all fine and good but still does not allow me to reboot into Recovery Mode. I took the extra step to sideload TWRP installer to see if that helps but nope, that causes my phone to get stuck on the stock OnePlus "Your device is unlocked etc etc" message and then I have to flash TWRP img > Restore > Restore Boot because it no longer wants to boot up. The strange thing about that though is when I am in TWRP, I can see everything on my phone, just not in the actual OS itself to where the phone is usable. It's almost like the phone is getting soft bricked.
Right now, I am using the phone fine now because I restored "Boot," but any attempt to reboot into Recovery Mode, it just goes straight to the Bootloader/Fastboot Mode. I have ensured USB File Transfer is enabled, OEM unlocking is ticked, and USB debugging is on.
Edit sorry I updated magisk and now I don't have twrp
Not sure what to do at this point. Any ideas?
Thanks!
Click to expand...
Click to collapse
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry
SirFronts said:
So that happened to my phone I used my computer to use the image file from twrp and tried the installer zip three times and then realized I was on slot b not slot a then I switched to slot a and then twrp was installed but would not open on slot b so I went from 9.5.11 to 9.5.13 and it put me back on slot a and then just rerooted with image of twrp and then installed twrp and migisk it was a pain so maybe you are on slot b as well try using the image file in fastboot and see what slot you are on if on be click switch slot a and see if it reboots into twrp without using the image twrp
Edit I saw a post saying magisk took twrp and well I guess that's true I don't have it anymore so IDK sorry
Click to expand...
Click to collapse
I guess I will just backup my phone completely, factory reset it, and re-root the device again.
mobbdeep said:
I guess I will just backup my phone completely, factory reset it, and re-root the device again.
Click to expand...
Click to collapse
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
I'll give that a try tonight.
I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?
SirFronts said:
I just used the TWRP image file to re-install 9.5.13 and then I installed the TWRP installer then magisk 19.4
Click to expand...
Click to collapse
alex.coffen said:
I encountered the same issue. Cannot get into twrp after upgrading to magisk 20.0.
But I am thinking that it should work if I restore boot partition that I did backup before when magisk was in 19.4, correct?
Click to expand...
Click to collapse
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Boot TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
I tried something and soft bricked my phone...
Anyway, lucky that I did a backup with twrp for boot when magisk was 19.3, then i can get into twrp by "fastboot boot" the twrp boot img temporarily and restored the boot.
Now everything works fine.
Ps: fastboot boot is not 100% safe...
mobbdeep said:
I noticed there is a Issue request on the Magisk Github.. https://github.com/topjohnwu/Magisk/issues/1920
This worked though.
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
My TWRP is gone too. But I can temporarily get in TWRP using my computer.
How do I flash OOS firmware? I am currently on PIE 9.5.13 intl. version. Should I download the full zip OOS and then flash it via TWRP ?
Then flash TWRP ?
And then flash Magisk 19.4 ?
Another question: DO you think uninstalling magisk via magisk uninstaller and installing the canary version of it would allow TWRP to stick ? There's threads that mention that the canary version doesn't erase TWRP.
mobbdeep said:
Flash TWRP img > Flash OOS firmware > Flash TWRP installer > Reboot to Recovery in TWRP > Flash Magisk 19.4 > Flash customer kernel (optional) > Reboot to Android.
Click to expand...
Click to collapse
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.
redpoint73 said:
Pretty sure you mean "Boot TWRP img" instead of the red highlighted text above. You can't flash the TWRP img on this device. Boot versus flash are very different things, and telling folks to do it is going to screw people up.
Click to expand...
Click to collapse
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh?
Dogstarlooma said:
After flashing magisk 20 my TWRP destroyed. I will try this later
Edit: reflashed stock oos TWRP and root magisk 19.4 and on xXx NoLimits running great again:laugh
Click to expand...
Click to collapse
I just read that Magisk 20 has a bug, that prevents TWRP from "sticking", and to use 20.1 (or in your case, looks like 19.4).
What I did:
Wiped all but data
Flashed latest OOS
Rebooted and lost TWRP
Booted to fastboot and booted from TWRP
Flashed TWRP
Rebooted to TWRP
Now all the data is encrypted (gibberish names)
How can it be?
What can I do now? from what I read I just lost all of my data... How do I proceed?
Now I'm attempting to sideload the official ROM... maybe after flashing the ROM, OOS will be able to read the files (I never activated any encryption on my device)
Alonzzo2 said:
Now I'm attempting to sideload the official ROM... maybe after flashing the ROM, OOS will be able to read the files (I never activated any encryption on my device)
Click to expand...
Click to collapse
How I install OOS.
Boot twrp
Flash OOS 10.3.6
Flash TWRP installer zip
Flash finalize
Format data
Reboot system.
On AB partition devices which is everything made now recovery and boot image are in same place so you must always install twrp installer zip when you flash a rom to have twrp otherwise it gets taken away. Formatting data when doing a clean installation at the end before you reboot system will allow you to then see your sdcard files afterwards..
Sent from my OnePlus6T using XDA Labs
Hey, after installing android 11 on my Oneplus 6 I have servere issues on getting root back.
Both methods I used result in a stuck boot.
Method 1: fastboot boot twrp, then install magisk.zip (tried with both 21.4 (last with a zip) and the renamed 23.0 (from apk to zip)
Method 2: Extracted boot.img from my OTA update, then patched with magisk 23.0.
Flashed the new boot.img -with fastboot -with twrp both result in a stuck boot.
Suprisingly flashing the extracted boot.img from the OTA boots fine, but that image is without magisk
Update: I have extracted the boot.img directly from the phone, patched it and it still doesn't work
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Thratchen said:
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Click to expand...
Click to collapse
twrp actually works, but after flashing magisk or flashing a magisk boot.img it breaks. I have a working version here
Ping me if you get magisk working
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
To remember!
Thratchen said:
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
Click to expand...
Click to collapse
Which installation method of magisk did you use?
How long did you wait after first boot?
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Thratchen said:
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Click to expand...
Click to collapse
Thanks for the reply, as a last question: Which magisk version did you use (could you link i?t). I assume you took the magisk v23 apk and renamed it to .zip? or what did you do?
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Thratchen said:
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Click to expand...
Click to collapse
Hmm, I perfectly copied your instructions and still get a bootloop. Even reflashed 11.1.1.1 again. Might be time for a reset
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
vkass said:
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
Click to expand...
Click to collapse
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp latest zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
tacohell said:
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp lat est zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
Click to expand...
Click to collapse
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
UraniumDonut said:
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
Click to expand...
Click to collapse
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
vkass said:
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
Click to expand...
Click to collapse
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
UraniumDonut said:
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
Click to expand...
Click to collapse
Thhank @UraniumDonut - that worked - I have never before used that method and honestly didn't even know about it. I use the official documented twrp way which is to first fastboot in to twrp and then install the zip file which has to be located on the phone file system. This method seems a lot easier!
As to magisk, I usually flash that from twrp using the zip file method and never have had any issues. But with all the issues surrounding oos 11 I am playing it safe as I don't want to get in to a boot loop. Will do some more research before I try something. But thanks to you I have made 1 step forward progress!
UraniumDonut said:
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
Click to expand...
Click to collapse
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
vkass said:
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
Click to expand...
Click to collapse
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Just for reference here
UraniumDonut said:
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Click to expand...
Click to collapse
I posted detailed steps if you want to give this a try @UraniumDonut: https://forum.xda-developers.com/t/how-to-root-op6-11-1-1-1.4344269/#post-85765879