I just screwed up when attempting an update. I had the update downloaded but did not install it.
Then I continued to install the A/B retention script and Magisk to the inactive slot and rebooted.
Now my phone fails to boot, and gets stuck continuously loading.
Is there something I can do in TWRP to resolve this?
You can try to flash the Magisk uninstaller in TWRP and see if it fixes your issue. Maybe you lost root on one partition and some Magisk modules that are still installed are putting your phone into a bootloop.
I'm unable to mount any partitions to get the uninstaller zip on my device. I was able to sideload the zip however the Magisk Installer was also unable to mount partitions.
Edit: I changed the slot from B -> A in TWRP then rebooted and it resolved this!
Mgssidley said:
I'm unable to mount any partitions to get the uninstaller zip on my device. I was able to sideload the zip however the Magisk Installer was also unable to mount partitions.
Edit: I changed the slot from B -> A in TWRP then rebooted and it resolved this!
Click to expand...
Click to collapse
Was just about to suggest that, glad you resolved it but you still have a broken slot, you should be able to fix it by flashing the rom, flashing TWRP and magisk, change slot and repeat. You might need a usb drive attached as changing the slot will usually made the data partition not visible so you won't see your files if they're on the phone.
To be honest, I thought flashing the stock rom will flash it to both slots (it shows this during flash) so I'm not sure what you did that broke it.
djsubterrain said:
Was just about to suggest that, glad you resolved it but you still have a broken slot, you should be able to fix it by flashing the rom, flashing TWRP and magisk, change slot and repeat. You might need a usb drive attached as changing the slot will usually made the data partition not visible so you won't see your files if they're on the phone.
To be honest, I thought flashing the stock rom will flash it to both slots (it shows this during flash) so I'm not sure what you did that broke it.
Click to expand...
Click to collapse
I'm actually on stock and doing an OTA update. After it booted up I was able to install the update, A/B retention script, and Magisk (to inactive slot). It rebooted successfully after that, should I still be concerned about a broken slot?
Edit: On closer look, Magisk did not install properly and I'm unable to access internal storage from TWRP to reinstall it.
Mgssidley said:
I just screwed up when attempting an update. I had the update downloaded but did not install it.
Then I continued to install the A/B retention script and Magisk to the inactive slot and rebooted.
Now my phone fails to boot, and gets stuck continuously loading.
Is there something I can do in TWRP to resolve this?
Click to expand...
Click to collapse
You didn't install the ota but you installed magisk to inactive slot?
Related
After successfully installing Magisk, I got 9.5.4 update. As my bootloader is unlocked, system forced full image update
Now, update install successfully through OTA updater but on reboot I get stuck in stock recovery. From there, I had to manually boot to fastboot and switch to slot b to boot OS, back. After spending an hour, couldn't get any leads. Any advice is appreciated..
arvindgr said:
After successfully installing Magisk, I got 9.5.4 update. As my bootloader is unlocked, system forced full image update
Now, update install successfully through OTA updater but on reboot I get stuck in stock recovery. From there, I had to manually boot to fastboot and switch to slot b to boot OS, back. After spending an hour, couldn't get any leads. Any advice is appreciated..
Click to expand...
Click to collapse
I think you've to flash magisk again after an update. I'm not sure though. Not taking responsibility for anything that'll happen if you do so.
icyfire said:
I think you've to flash magisk again after an update. I'm not sure though. Not taking responsibility for anything that'll happen if you do so.
Click to expand...
Click to collapse
Ofcourse I own the responsibility,
Yes tried flashing it seperately for slot a. Then seperately for slot b. Since nothing worked out, flashed twrp on slot a and still nothing.
Then, tried going to slot b 9.5.2 ROM, did local sys update then without reboot, inside Magisk flashed Recovery zip. Even then slot a ROM, doesn't boot
arvindgr said:
Ofcourse I own the responsibility,
Yes tried flashing it seperately for slot a. Then seperately for slot b. Since nothing worked out, flashed twrp on slot a and still nothing.
Then, tried going to slot b 9.5.2 ROM, did local sys update then without reboot, inside Magisk flashed Recovery zip. Even then slot a ROM, doesn't boot
Click to expand...
Click to collapse
Maybe try unrooting by flashing the stock boot.img. You can get the boot.img for 9.5.4 here.
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
what method did you use (there are a million rooted guides)? did u get the correct OS OTA for you model phone? provide us more info please.
Looks like i forgot to turn off the magisk modules. I had to go into twrp and delete them all and re download the modules. silly me
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
jakemaxfield said:
I'm having a similar issue. I can't figure out what to do, but I i went and deleted all the zip files for magisk but after reinstalling magisk thru twrp, I get stuck booting to recovery everytime. I can someone help point me in the right direction?
Click to expand...
Click to collapse
I stuck at the same situation. Can you flashboot flash boot.img and then it can boot normally?
Same problem here.
Situation before flash: stock 9.5.8, Magisk, a number of Magisk modules
What I did:
* downloaded 9.5.9 with Oxygen Updater
* disabled Magisk modules
* rebooted
* installed 9.5.9 from the builtin System Update
* went to Magisk, installed it with After OTA
* rebooted to recovery
* installed TWRP and Magisk
* cleared Dalvik
* rebooted to system
The phone seems to start normally, but when it reaches the unlock screen it immediately goes to Power Off, then it reboots to TWRP (not power off). From TWRP I can decrypt data ok etc.
I tried reinstalling the boot loader, OTA image, TWRP, Magisk - same result. Rebooting to system from TWRP just goes back to Power Off then TWRP.
equlizer said:
I followed the previously rooted guide to update to 9.5.9 and now when the phone reboots, it gets to the unlock screen and immediately tells me its shutting down and reboots back into twrp again. How do i fix this? Please help and thank you.
Click to expand...
Click to collapse
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
manor7777 said:
If this is any help in the future, whilst I don't have twrp, I install the updates via local update in settings > system > updates and then before reboot I go to magisk manager, and install magisk to second slot and reboot. Never had a problem and I'm on 9.5.9 now. The only modules I disable, update, or remove are the magisk ROMs available here such as no limits, as they are usually version specific.
Click to expand...
Click to collapse
That's exactly what I did. It landed me to the bootloop.
All you guys had to do is,
Install the full uddate zip in twrp,
Install the latest twrp zip,
Reboot recovery,
Install latest magisk,
Reboot system,
Hope this helps, cheers
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
lcd047 said:
Update: I can break out of the loop from TWRP > Advanced > Fix Recovery Bootloop. That lets me boot normally, but loses root. As soon as I reinstall Magisk I get back to the bootloop.
Click to expand...
Click to collapse
I'm in the same boat.
My twrp doesn't offer to decrypt partition_b so I cannot manually install Magisk on the new partition.
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
sapalot said:
This seems to be a common problem when updating rooted Oneplus 7 pro and I haven't found a update guide which actually works every time. Last update to 9.5.8 I had the same issue where I couldn't get into oxygen os because it turned itself off and when twrp opened I couldn't decrypt the data. I couldn't find a solution last time and I had to full wipe and start from scratch. Now I don't want the same to happen so I hope someone can post a guide how to do the update successfully.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
It worked for me for 9.5.8, got the bootloop this time around. I guess this means I'm not the Chosen One.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
djsubterrain said:
Sometimes you might be on the wrong active slot, you can change this by using fastboot set_active a or fastboot set_active b. TWRP seems to like changing your slot but will tell you when it does. If you're getting stuck try changing slot and booting.
Click to expand...
Click to collapse
I tried that too. When I switch to the other slot I get to a menu where I can only wipe data, reboot to boot loader, or reboot to recovery. Not particularly useful.
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
mkos86 said:
Hey guys!
I'm having the same problem. No matter how I try to update it will reboot to stock recovery.
I was wondering if any of you have /Data converted to f2fs? Maybe it could be culprit...
Click to expand...
Click to collapse
What I had to do here was go to fastboot mode and flash twrp img. Then in TWRP I flash the TWRP zip file and magisk and rebooted. All good
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
jakemaxfield said:
Alright so I fixed mine. I went and just removed all the modules while I was in twrp. To do that go to Advanced, then file manager or whatever it says, find the adb folder and from there look for a folder named Modules and just delete them all. From there just reinstall magisk through twrp and it should all work.
Click to expand...
Click to collapse
Thank you sir, this fixed it for me, too. So the missing link was that Magisk modules have to be removed completely, not just disabled, before upgrading. Removing all directories except .core from /data/adb/modules allows the phone to boot normally, with Magisk enabled.
schmeggy929 said:
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414.
Works every time, the same way I have been doing for both 6T and 7 Pro.
Click to expand...
Click to collapse
Thats the way i tried that time and got stuck in bootloop.
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again​
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
I totally know that feeling. I started with a tmo op7p, flashed international, unlocked bootloader, try to boot TWRP, and nope. Switch slot, it works. Flash it, great. Make a backup with TWRP of my working system, flash ROMaur, won't do anything but boot to TWRP. Open TWRP file manager and every file on internal storage is a ton of folders with jumbled strings of letters and numbers for names. MSM tool back to intl stock, try lineage... Nope. Keeps telling me to do a factory reset. I did, but I do another and still boot loop. MSM to intl, try other roms, same outcome.
I can unlock my bootloader and root it and run intl stock but that's it.
oxadedzn said:
Hey guys,
so first of all I wanna let you know that my device is not bricked or something (it was a couple of times though).
But let's get started with my issue. For me, personally, I have experienced that the slot system (A/B Slot) doesn't work that good. I had a OnePlus 3T before and I never had any problems with flashing, but now...
My impression is that it's a lot easier to brick its' device than before. Every time I want to flash a new OS I gotta use the msmtool.
1. I boot to recovery mode through the OS
2. I boot to fastboot trough the OOS stock recovery
3. I try to flash TWRP to erase the system
4. Flashing works, but I can no longer boot into recovery mode
5. I have a bootloop (fastboot mode only)
6. I have to use that msmtool
7. I have some old OOS (9.5.5 or something)
8. I unlock the bootloader through the OS & fastboot
9. I boot into TWRP, delete everything and flash another ROM
10. Everything works and the cicle begins again
I really don't know why I'm always stuck in that bootloop... Maybe you guys could help me and give me your personal opinion on the slot system?
Click to expand...
Click to collapse
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
tech_head said:
Doing it wrong.
If you are currently rooted and a new OS comes out you can do the following and you don't need to flash with TWRP or use a computer.
1. Download the full OTA. You can use Oxygen updater to do that or use a link in the stock ROM section on this site.
2. Make sure you have the Magisk and the TWRP zip on the phone.
3. Do a local update in the system area but do not reboot.
4. Launch Magisk manager and select install.
5. Use the OTA install option to inactive slot.
6. Now you can reboot. You have installed the new OS and root also.
7. Once rebooted do another local install. This will install in the slot that you were just running. It will fail the first time, but work the second time.
8. Repeat 4.
9. Repeat 5.
10 . Repeat 6.
You now have both slots with the same OS and rooted.
If you want to install TWRP.
Launch Magisk and install the TWRP zip.
Reboot into recovery. This is important because you cannot boot in slot with TWRP unless Magisk in installed.
Now flash the Magisk image file.
Now in TWRP select the other slot and reboot into recovery.
In recovery install Magisk image to this slot.
Now you have TWRP and Magisk in both slots.
I have done it that way since 9.5.7 and have not had an issue.
Click to expand...
Click to collapse
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
JhinCuatro said:
Irrelevant ISH, but ever had that one bootloop where it only bootloops at the "Warning Bootloader unlocked screen" constantly? When I try to access fastboot, it'll just go straight to recovery without even waiting for input (to my luck, of course, until I had to uninstall magisk in full, reinstall, make sure TWRP was reflashed and did the "Fix recovery bootloop", though that wasn't the seemingly the issue). The issue got resolved, but it was very scary for that to have happened as soon as i enabled sudohide (I always had it work, but with huge problems, but never enough to bootloop me to death)
Click to expand...
Click to collapse
If you install TWRP on a 7 Pro without installing Magisk you will absolutely boot loop. If you wipe the system in one slot and have a differing ROM from the active slot you can in fact boot loop. Although the systems are different, the settings between the systems are shared.
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Arden144 said:
Sorry to say, but nothing about those steps is correct. Follow some guides in the guides section to get aquatinted with the A/B system
Click to expand...
Click to collapse
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
You can also install TWRP if you like.
No computer needed.
This works.
tech_head said:
You are absolutely incorrect.
When going from 9.5.10 to 9.5.11 and all my previous upgrades it has been:
1. Local install of the new OS with a full OTA since I am rooted.
2. Do not reboot.
3. Install Magisk to inactive slot.
4. Reboot (Slot will automatically switch to the one recently updated).
5. Local install of OS into the other slot, fails first time, do it again.
6. Install Magisk into inactive slot.
7. Reboot. (Slot will switch to recently updated slot).
8. Both slots now have latest OS and are rooted.
This works.
Click to expand...
Click to collapse
That's completely unnecessary and just avoiding the purpose of the a/b system.
All it would take is:
1. Local install
2. Install magisk to inactive slot
I was trying to update my OP6 to OOS 9.0.8.
I downloaded the full OTA and booted into TWRP, flashed the new update img, and forgot to flash TWRP and rebooted to system. No worries, I went to fastboot and installed TWRP via adb. All was good until this point. But after I flashed Magisk zip in one slot B, slot A files all appear gibberish.
I don't know how to proceed. The device proceeds to boot on slot B all fine, latest OOS, and rooted. But booting to slot A always loops to TWRP.
I'd appreciate any help. Thanks in advance!
It's possible it's because you have a different ROM (or version) installed on slot B. The userdata partition is shared between slots so trying to boot into the "unused" slot could potentially cause a boot loop.
But otherwise I'd guess your B slot has become corrupted somehow. I had a similar problem recently. You can fix it by reflashing both slots, see this thread.
Hey
My phone dont detected sim card in custom rom Havoc 3.0.
My phone: OnePlus
Guide install ROM:
https://forum.xda-developers.com/oneplus-7-pro/development/rom-havoc-os-2-6-t3942337
Hope this can help
I had similar issues flashing the rom in slot b instead of slot a fixed it for me
Kreiden_123 said:
I had similar issues flashing the rom in slot b instead of slot a fixed it for me
Click to expand...
Click to collapse
How do you choose slot b while flashing on TWRP?
This seems really convoluted to me, but it totally worked:
Boot TWRP (from fastboot)
Install TWRP from phone storage
Reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into system and wait for something like 5 minutes while it sat on the "Your bootloader is unlocked!" screen.
I believe that installed into both slots for me.
I also had to ADB push the install files after the first ROM install because my encrypted data all got lost. This was all SUPER inconvenient, but it ended up working for me.
jfsat said:
This seems really convoluted to me, but it totally worked:
Boot TWRP (from fastboot)
Install TWRP from phone storage
Reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into recovery
Install ROM, gApps, TWRP, and Magisk
reboot into system and wait for something like 5 minutes while it sat on the "Your bootloader is unlocked!" screen.
I believe that installed into both slots for me.
I also had to ADB push the install files after the first ROM install because my encrypted data all got lost. This was all SUPER inconvenient, but it ended up working for me.
Click to expand...
Click to collapse
Love it, I'm going to try it tonight