Has anyone with a magisk rooted stock firmware for the OP8 global had issues with the latest incremental update? I did the usual, restore images in magisk, install update, flash to inactive slot. But when it tries to reboot, it only gets to the oneplus logo then a blank screen, and reboots 3 times before ending up in the recovery. Switching back to the previous slot boots up just fine.
I tried it twice, same thing both times. Wasn't able to try without patching for magisk I just decided to hold off on updating till I could figure out what was going on.
Related
Ok, so I had to reinstall my OS through TWRP (2GB Full update)... and rebooting to the Bootloader to reinstall TWRP and rebooting again, I want to install Magisk again.
When I install Magisk through TWRP and reboot, the boot animation is stuck forever and animates very slowly. The only way to get out is to press VOL UP + POWER and inmediately VOL DOWN + POWER to enter TWRP. To fix the stuck boot animation I have to reinstall the full OxygenOS update and reinstall TWRP.
My problem is that I'm in this vicious cicle where if I install Magisk it doesn't work and I have to reinstall the OS and TWRP.
What am I missing? Why Magisk is making my device stuck on the boot screen?
Any help will be appreciated. Thanks!
I had that earlier today. For me I switched to the other partition from twrp and rebooted and it worked fine. Guess I'll flash ROM and magisk to both partitions next time
skymera said:
I had that earlier today. For me I switched to the other partition from twrp and rebooted and it worked fine. Guess I'll flash ROM and magisk to both partitions next time
Click to expand...
Click to collapse
So let me make sure I understood you. I need to switch to Slot B and also install the OS and Magisk?
OK, an update. After trying to switch slots, install the OS in both of them and Magisk and all the possible permutations, I tried flashing 19.4 and it worked flawlessly first time.
Now I'm going to update it!
Update 2: I'm finally running the latest version! Updating Magisk through Magisk Manager worked fine.
Deses said:
OK, an update. After trying to switch slots, install the OS in both of them and Magisk and all the possible permutations, I tried flashing 19.4 and it worked flawlessly first time.
Now I'm going to update it!
Update 2: I'm finally running the latest version! Updating Magisk through Magisk Manager worked fine.
Click to expand...
Click to collapse
I have the same issue with the slow boot animation and the endless loading. I tried to install the OTA again, TWRP again and magisk 20.1, 20.0, 19.4 ...
Sadly the animation stays that slow and my OP7Pro doesnt boot up. How exactly did you get rid of that problem? I feel like I tried every combination of flashing
dennisgrue said:
I have the same issue with the slow boot animation and the endless loading. I tried to install the OTA again, TWRP again and magisk 20.1, 20.0, 19.4 ...
Sadly the animation stays that slow and my OP7Pro doesnt boot up. How exactly did you get rid of that problem? I feel like I tried every combination of flashing
Click to expand...
Click to collapse
I had this with PA. Not sure what caused it as my flashing process is the same every time.
In the end I gave up and formatted /data
skymera said:
I had this with PA. Not sure what caused it as my flashing process is the same every time.
In the end I gave up and formatted /data
Click to expand...
Click to collapse
I decided to give up too... Was a bad mistake. I accidentely rebooted the phone after the update today. I will never do that mistake again
That dreadful moment when you have this problem again and googling points you to your own thread with no solutions.
UPDATE: Oh I think I got it! I had to uninstall Magisk Manager AND flash Magisk Uninstaller zip, reboot to OS, reboot to Recovery again and flash Magisk 20.3 again and it finally worked! No more stuck slow boot animation.
Probably the two reboots aren't needed, but I like doing things slow.
I've just updated my Oxygen OS to 10.0.2 by flashing the OTA via TWRP.
I was following the guide found here https://forums.oneplus.com/threads/...10-0-1-update-keep-twrp-magisk-guide.1118577/
However, after flashing Magisk I get stuck in endless loading on the Oneplus boot screen. It seems like I can get out of it by switch boot slots, either A or B depending on which slot I was on when I flashed the OTA.
The end result when I get back into the system is always no root, I've either had no Magisk manager installed, or if I do have a Magisk Manager, Magisk is not installed and I cant seem to flash it via the manager.
I am at a total loss, this whole Slot A nd B thing confuses me and I've got no idea what I'm doing wrong... Should the OTA be on slot A and Magisk on B, or is it both?
Hoping someone can guide me in the right direction, wish I never updated at this point.
I do the updates through regular OTA and magisk so no clue if it relates but the only time it bootlooped for me was when i had my magisk modules still enabled before updating. There are a few that cause issues there.
There are plenty of guides here as well that should cover these kinds of issues
Pretty sure that updates go to the slot that is inactive at the time if installing the update
I screwed something up updating to 10.0.2 as well. I've messed it up a couple times so I can't remember if I fixed it or just started from scratch with the msm tool.
I would go to twrp and make sure you are on the same slot that boots.
Flash magisk and reboot. Now hopefully it boots with root.
Download the full update and install it via local update, don't reboot. Go to magisk and install on other slot (after ota).
Or backup everything you can and start from scratch.
Thanks all, I got it to work by simply flashing the Factory image and restarting from Scratch.
In doing so I think I was able to re-create my issue, after re-rooting and installing my apps... It seems like my Magisk module Pix3lify was not playing nicely, and once removed the endless rotating circles went away and the system booted normally and with root.
As I had this module installed while trying to upgrade, I suspect that this was always the root cause.
The lesson here is to disable or remove your Magisk modules while you're updating!
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
kold11 said:
Hi all,
update: I made update at the end.
My OP7 version is GM1900, so far I was on build 10.0.6GM57BA with Magisk 20.4, but for some time I had 10.0.8 update notification.
Today I decided to update build.
I consider myself as medium experienced user the type that is using rather step by step guides.
But this time I thought I don't need guide cause I should remember how I did update last time. In the meantime I help my son to make homework what was an additional distraction.
I always download full OTA from oneplus.com support but it turned out there was no 10.0.8 (instead there was/is 10.0.7). So I tried to search for 10.0.8 and I found this xda news. As there is a mess with versions and links and I was doing it on mobile Chrome I accidentally tapped Global/India Full OTA
Steps I made:
1.1. Downloading file OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.2. Downloading official TWRP twrp-installer-3.4.0-0-guacamole.zip
1.3. Boot into TWRP.
1.4. Flash twrp-installer-3.4.0-0-guacamole.zip
1.5. Restart to TWRP
1.6. Flash magisk uninstall
1.7. Flash 10.3.5 (India & Global) - OnePlus7Oxygen_14.P.29_OTA_029_all_2009152124_ba2424a.zip
1.8. Flash magisk 20.1 (but forgot to reboot after flashing TWRP it was first mistake I think)
1.9. Ended with 10.3.5 (India & Global) build with stock recovery and without Magisk.
Next I tried to return to GM57BA.
Then the steps I made:
2.1. Downloading official build 10.0.7.GM57BA from oneplus support site.
2.2. Downloading Mauronofrio's TWRP twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img and twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.3. Boot OP7 into fastboot then command "fastboot boot twrp-3.4.0-0-guacamole-unified-Q-mauronofrio.img"
2.4. After phone booted into TWRP I flashed twrp-3.4.0-0-guacamole-unified-installer-mauronofrio.zip
2.5. Restart to TWRP
2.6. Flashed magisk uninstall.
2.7. Flashed 10.0.7.GM57BA
2.8. Flashed magisk 20.4
2.9. Only then I rebooted to TWRP (I think it was mistake).
2.10. Then I saw first problem - there was no lockscreen security with TWRP (unlock pattern).
2.11. Restarted to TWRP again - the same no unlock pattern screen, no access to data partition
2.12. I started to panic and restarted into system.
2.13. I ended with hard bootloop - I mean I can't even do force reset (force reboot) by pressing and holding the Power and Volume down buttons at the same time :crying:
I'm sorry for this long description but I thought it will be helpful to diagnose what I messed up.
Questions and my thoughts:
1. Did I messed up by not restarting after last magisk flash?
2. What to do now? Do I need to wait for battery discharge? Then unbrick using MSM tool?
3. Is there any chance to repair and preserve personal data? I have TWRP backup about 3 months old. Maybe after battery discharge I should go to TWRP and then sideload this backup? Maybe magisk uninstall or stock boot image flash?
Please help
Update:
After battery discharge I managed to boot into TWRP recovery (Mauronofrio's 3.4.0.0)
Then couldn't access /data
But when I switched to Slot B and reboot to recovery situation is back to normal (I guess).
I'm still in recovery scared to boot into system.
What to do now?
Click to expand...
Click to collapse
To force restart I need to use power button and both volume keys..
To keep TWRP you need to flash rom, then without restart flash TWRP again, then restart TWRP, then flash Magisk.
Likely the r reason why your system doesn't boot is because it can't decrypt your data.
Why this happens I don't know, maybe in the upgrade they changed something related to the exception and then by downgrading again it isn't able to read it anymore.
I would suggest to:
Flash the latest rom.
Flash TWRP
Reboot TWRP
If TWRP then doesn't ask for PIN or password, then I'm afraid you have lost your data. I hope you have a backup.
I'm that case format (not just clear) data -> yes
Reboot TWRP
Then flash Magisk.
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
kold11 said:
Thanks for reply.
Like I wrote in update after changing slot to b I managed to run TWRP with decrypted data, made even new new backup.
I also restarted into system and it occurs I'm still 10.3.5 (India & Global) GM57AA, so everything I flashed in with build 10.0.7.GM57BA was unsuccessful.
I think I messed with changing inactive slot procedure. Noob mistake I need to read about it.
Click to expand...
Click to collapse
I would suggest do restore your device with msm unbrick tool.
1. From recovery, turn off (i noticed, that when tried to turn off from somewhere else, the device would auto reboot later in downlaod mode)
2. In windows, turn off the connection & open device manager: Get this driver http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab
3. Press volume/down + volume/up, after about 5s connect to pc
4. Your device should show up in device manager, open it and install the driver manuell from step 2 (keep device options open... if fail you need to uninstall the driver before trying again)
5. Now wait for about 40s, if your device stays in download mode, you can open & start the msm tool (leave the options in msm as they are)
6. It will take about 280s, then the device will reboot.... (its normal that it stays longer at the oneplus logo at first start)
MSM Thread: https://forum.xda-developers.com/oneplus-7/how-to/op7-unbrick-tool-to-restore-device-to-t3954325
I've also uploaded the 10.0.5OOS Unbrick tool on mega, because android file hosted downloads are so terrible: https://mega.nz/file/ArZFkYpS#Z_rOIwZeYN27IG6L8rOi-yfw8wXGiwvK-uWVDlsmvTI
Hello, I recently got an update on my OnePlus 7T Pro. I dowloaded the update and I forgot to install it before installing magisk to the inactive slot via the magisk app.
Now my phone won't boot. It just boots up reboots and then goes into like recovery or some black screen with white text and minimal options.
Does anyone know how I can fix this?
At first I tried to flash a new boot.img because I thought it might be wrong. But that didn't fix it. Instead I had to flash the stock rom again to make everything work. And now my phone has booted up again with all data still there since I leave my bootloader unlocked.
I followed this tutorial:
[ROM][STOCK][FASTBOOT][OP7TP] Stock Fastboot ROMs for OnePlus 7T Pro
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com
For the last couple years I've been following this process to retain root using the TWRP A/B Retention Script and installing Magisk to the inactive slot after OTA and everything been fine and dandy. However, after the last time I performed this process Magisk would immediately crash when I tried to launch its app. Upon investigating I noticed that the file it downloaded for flashing was suspiciously small, so I suspect it flashed a corrupted file. I had already successfully rebooted my phone several times after the OTA, so I figured it was just Magisk that got corrupted and TWRP must be fine. I recently tried to reboot into recovery and discovered that TWRP is broken too. My phone briefly flashes the TWRP logo before the screen goes black and it tries to reboot into recovery again.
I've been able to get into fastboot by simultaneously holding down the power button and both volume buttons. However, none of the options in fastboot actually get my anywhere. Choosing start, recovery mode, or power off just get me back into the TWRP bootloop, and restart bootloader obviously just keeps me in fastboot.
I assume I need to reflash TWRP and Magisk, but I'm not sure how to go about that. Can someone point me in the right direction? Thanks.
This is how I proceeded:
Downloaded the latest TWRP image (twrp-3.6.2_11-0-guacamole.img) from here: https://dl.twrp.me/guacamole/
Verified the md5sum to ensure the download wasn't corrupted.
fastboot boot twrp-3.6.2_11-0-guacamole.img
In TWRP, Advanced > Flash Current TWRP
Now I have a working recovery, but I still can't boot into my system. When I go to Reboot > System in TWRP it just boots back into recovery.
I enabled MTP in TWRP and copied off all the data I cared about, then used the "Flash Factory Images" option in the TOOL ALL IN ONE to flash 9.5.13-GM21AA-OnePlus7ProOxygen_21.O.16_OTA_016_all_1908281716_b2bb5-FASTBOOT.zip. I tried it without checking the box to erase everything, hoping I could keep my data, but that didn't work. With that box checked though I was able to boot again, but I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue. Does anyone know how to get WiFi working again or why it may have stopped working?
altayh said:
I cannot turn on WiFi for some reason. I'm hoping the OTA will fix that issue.
Click to expand...
Click to collapse
Fortunately enough the first OTA did indeed solve the WiFi issue. Now I've applied all of the OTAs and finally have my phone in a proper working state again.