Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
TheMadKing said:
Sorry if the question sounds weird, it's probably because I don't fully understand this. I know that the OnePlus 6 has two software slots, an A slot and a B slot, and I also have a vague idea about what those slots are doing during an update.
Looking around, I found a thread that recommends flashing software on both slots, saying that it could fix some issues. I'm currently on Oreo, and I'm planning to get back to 9.0.4., but I remember that during 9.0.2. I think, when I was upgrading from Oreo again, I locally installed the same update file twice. I installed it once, everything went well, I went back to the local upgrade menu after the restart, and installed it again. And the phone seemed to be faster for some reason, that's what I'm trying to achieve again.
The thread that I found mentioned how to flash the software on both slots while on TWRP, would locally installing it twice achieve the same effect? Or is there something else that I can do?
Thank you very much in advance
Click to expand...
Click to collapse
Yupp. Same effect ??
whizeguy said:
Yupp. Same effect ??
Click to expand...
Click to collapse
Thank you!
Hello all, I have a question about the active slot on this device. I just flashed the latest update from the Developers website and everything appeared to flash with no issue. However, I'm still not showing updated. When I flash the Magisk modified boot image, I have to include the script to flash to slot B. I'm assuming the OTA flashed to slot A. I looked around and found some commands to change slots, but none of them worked. I'm sure I'm missing something easy, but I'll take any advice you'll offer to get this thing updated. Thank you.
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
behel1t said:
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
Click to expand...
Click to collapse
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
azoller1 said:
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
Click to expand...
Click to collapse
Hi, correct I am not using twrp. I tried unlocking the boot loader and not rooting. Receiving an OTA works and I can reboot. But oddly enough if I do a --set-active=otherslot, i get a qualcomm crashdump.
It appears that whenever I or magisk force change the active slot, I get a crash dump.
EDIT - Still unsuccessful. I've tried numerous times using MSM Download and the fastboot unbrick method by coomac. I haven't been able to --set-active=b a single time, it always ends up in a qualcomm crash dump. I suspect slot is B is corrupt.
Try to restore both slots with an older version of rom using local update. Then take ota and try.
kjslabber said:
Try to restore both slots with an older version of rom using local update. Then take ota and try.
Click to expand...
Click to collapse
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
behel1t said:
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
Click to expand...
Click to collapse
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
kjslabber said:
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
Click to expand...
Click to collapse
Thanks for the reply. I do yes. I'll give this method a shot. Cheers
UPDATE - Just finished using msm download to restore OOS 11.0.5.6 and then used local upgrade to flash OnePlus8TOxygen_15.O.20_GLO_0200_2011132216 (both 11.0.5.6). I can now successfully boot both slots!
Now I am going to root. install riru and safetynet fix in magisk.
When I am ready to take an OTA, the correct process would be to uninstall the safetynet fix and riru. Then uninstall magisk using restore images, download and install OTA but do not reboot. Go into magisk and install to other slot. Then providing a successfully boot, reinstall safetynet and riru. Is this correct?
UPDATE 2 - Qualcomm crashdump happened after taking an OTA using the method I outlined above. So I reverted back to the previous slot and am in the process of doing a local upgrade again using 11.0.5.6 to hopefully restore that slot to working.
Something about magisk installing to the other slot and forcing a slot change is causing this crash dump.
I had 11.0.5.6 on both slots. I rooted. I then completely unrooted (not restore images). Took an update. That booted. I booted that. Rooted it. Then for testing, completely unrooted again. Then I received the latest OTA. That installed and booted. So I'm rooting now on the latest getting ready for daily use.
I have no idea why using magisk to install root to the other slot and forcing a slot change is not working. I'm grateful that, with extra steps, i can at least reliably receive OTAs and continue on living rooted life.
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
azoller1 said:
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
Click to expand...
Click to collapse
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
behel1t said:
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
Click to expand...
Click to collapse
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
azoller1 said:
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
Click to expand...
Click to collapse
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
behel1t said:
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
Click to expand...
Click to collapse
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
azoller1 said:
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
Click to expand...
Click to collapse
Thanks for bringing this to my attention. This is definitely what is happening. You just just saved me from spending any more time on this mess. Cheers!
I just wanted to add that I had same problem with my OP8T and couldn't reflash the ROM and had to send my phone to OP to get the ROM put back on. Slot B still doesn't work. You at least were able to get the phone back working with MSN.
Cant flash twrp nor the patched magisk boot img to both slot a and b.
Bootloader is unlocked.
Flashing scripts via .bat files for stock zips of both android 10 and 12 results in "FAILED (remote: Partition product not found)" or "FAILED (remote: variable not found)" respectively.
I have no recovery.
When I had twrp, I've made the mistake of wiping my whole android 12 data, storage, and system and flashing an android 10 rom without reading up of the separate a and b boot slots nor the effects of my actions leading to bootlooping. (I've done with this other devices before with no problems). This in turn wiped the twrp recovery I had flashed and left me only fastboot commands and a twrp version up to 3.3 and 3.2 with no hope of getting usb otg to work as it was only available with the later versions of twrp and since I and now technically on an android 10 bootloader, any attempt at that time to flash twrp 3.6 was met with a (remote: Error calling AvbLoadAndVerifyBootImages Load Error) or some kind of other error I have no logs for. Now I cant even tetherboot to twrp 3.2 nor 3.3 and I get that error regardless.
[Boots to bootloader no matter what. Shows as UFS:Micron, Error reason - reboot bootloader - bootloader version is b1c1-0-4-7617406]
I believe I can get access to internal storage to flash these updates once I get a recovery tethered from the bootloader. I do not know if its possible to boot to fastbootd or whatever its called (used for write permissions/sideload update zips) even if I hadn't gotten into this predicament. I will be buying another Pixel 3 in the meantime as I have money to burn and like to hurt myself financially, and emotionally to get to my goal with this device. ( Didn't buy another one, I was committed to the cause!)
I am not a noob nor a pro, but somewhere in between. My biggest point of failure is not reading up on how the partitions are set up and the various issues others had when flashing android 10 and 11 roms. Any suggestions other than "uPdAtE tHe fAsTbOoT aNd AdB dRiVeRs" are not welcomed. Thank you. I will update once I find a soluton to my problem Which I Will.
Again, my main concern right now is getting tethered twrp to work again and need suggestions. I have older versions of platform tools and the latest so please non of those comments I see on literally every other thread.
Edit: I didn't mention this before, but I did have the ability yo sideload when I had twrp at the time before crapping everything out the window, but nothing would work and gave up. Just wanted to add if anyone was wondering.
First update, I used the propriatary "Tool All In One Tool" and I was able to boot to fastbootd, and wipe my data and storage, while updating my stock zip to android 12. Now I can tetherboot twrp 3.6.1_11-0 with the option for usb otg, wish me luck boys. I'm in.
Second update. Still stuck on first update, but weighing my options in the meantime. I flashed twrp via the flash current twrp option, but when I boot to it, touch is disabled so thats great... I can fast boot to only the twrp versions after 3.6+, so not so bad. I have no os installed, but I will try my hand again at that tool all in one tool again. I'll update tomorrow if anything comes of it.
3rd update. FROM THE BRINK OF DEATH!!! WHOOOOOOOOOO!!!!! I got the pixeldust rom flashed and working like a BOSS!!!!! You won't believe the 2 days I've had trying to get this thing to work. All in all 1 out of my 3 flashdrives finally worked with otg. I had a windows recovery drive premade on it so I just copied and pasted the files there without a hitch! Thank you Google for having to make me miss work and actually do research to get this thing working again! Thank you for the guys at Tool All In One Tool for making this recovery possible, I will shout out your thread. If anyone who's in a similar situation needs any help from me or any info, I'll be glad to help. This will be the second to last update. I can also make phone calls and use data so Pixel Dust rom is good to go if that was one of your concerns. See ya!
Final update, I got crdroid flashed with root and safetynet passed, I just found out that google Pay was imbedded in gapps so now I don't need the pay app anymore to do transactions! My banking app also works, got vanced finally installed (couldn't do it on regular stock ROM) some glitches with the ROM here and there but no worries. For who ever reads this. There's hope. I fd up as bad as you can get shy of a hard brick. I still don't know too much but learned near twice as much as I knew just a few days ago. If you need help just DM me and I'll work my hardest to bring the light. This phone is absolutely amazing and on god wished google was a better company to praise. I have more plans for these phones and hope more Roms come out to support it.
I have one question however, how do I make a backup of my system/system_ext partitions? I can make a back up of everything else but that with these two Roms... I have a backup of it with my stock ROM, but it resumed to mount when I used otg... Didn't try internal yet but I'll assume the same, is it a glitch with current twrp?
Might be a noob question but can i flash Android 14 DP2 to an inactive slot and switch back to Android 13 stable on a current slot later? Will any of these steps require a data wipe, will switching back and forth android version cause any harm to apps and settings? Using Pixel flash tool, heard about interesting stuff on A14 and want to check it out by myself.
Diofyz said:
Might be a noob question but can i flash Android 14 DP2 to an inactive slot and switch back to Android 13 stable on a current slot later? Will any of these steps require a data wipe, will switching back and forth android version cause any harm to apps and settings? Using Pixel flash tool, heard about interesting stuff on A14 and want to check it out by myself.
Click to expand...
Click to collapse
You CAN'T.
Definitely no...
Diofyz said:
Might be a noob question but can i flash Android 14 DP2 to an inactive slot and switch back to Android 13 stable on a current slot later? Will any of these steps require a data wipe, will switching back and forth android version cause any harm to apps and settings? Using Pixel flash tool, heard about interesting stuff on A14 and want to check it out by myself.
Click to expand...
Click to collapse
The quoted post below may answer the question better as to why you wouldn't be able to pull this off...
badabing2003 said:
Thanks @simplepinoi177 for finding relevant posts.
What I want to add is that, although the initial thought process was to use the alternate slot as a fallback.
Unfortunately that only works with older devices, and does not work for newer ones.
Even for older devices one needs to remove system_other.img from the update image to get it to work.
I have posted about the details, unfortunately I'm not very good at finding my own posts.
The gist of the matter is that, factory images contain system_other which is flashed to the alternate slot's system partition, they contain the optimized dex files which are copied to the active slot after booting to system to save time.
This effectively deems the alternate partition's system unusable.
Removing system_other before flashing theoretically would get around that issue, at a small performance hit at first while the dex files are optimized on first use, and that works on older devices.
I managed to setup Pixel XL with both slots bootable, and alternate between them at will, even one was rooted and the other stock.
Sadly this no longer works on newer devices due to AVB.
Click to expand...
Click to collapse
simplepinoi177 said:
The quoted post below may answer the question better as to why you wouldn't be able to pull this off...
Click to expand...
Click to collapse
And even if AVB did not prevent booting on both slots and the user took care of the system_other, it is highly likely that he would encounter random crashes or worse, mainly because of two different versions of OS using the same data partition, (remember there is only one data partition).
This is one of the reasons why a downgrade of OS version causes such issues.
Okay, i had thoughts that this would end bad, decided to ask just to make it clear. Thank you for your responses.