Ok so I was on oxygen 5.1.6 and I downloaded the update for 5.1.7. I booted into twrp flashed it booted up and was in 5.1.7. I boooted back to twrp and made a backup. I booted after backup and phone went back to 5.1.3. WTF?! I had to reflash the update, reinstall the twrp installer zip and root once again. I also noticed that If u change slots you will boot into the unrooted version of your rom and the other is the rooted version. What's the deal with the two slots in twrp. I can see where in the future this will have advantages but it's kind of confusing at the moment. Does anyone know why my phone went back to 5.1.3 after a backup and can anyone explain why there is two slots now and the sole purpose of them within twrp.
I thought twrp and magisk flashed both slots?
a/b partition is just for /system iirc
a/b partition exists for all the partitions as seen in /dev/block/platform/soc/1d84000.ufshc/by-name. When you updated from 5.1.3 (let's say slot a) to 5.1.6, it updated 5.1.6 to slot b and set it as the active slot. When you updated 5.1.7 via twrp, I think it just writes over your current active slot (which is also b), so my guess is you updated slot b to 5.1.7 and slot a is still 5.1.3. Not sure how your active slot switched after booting into 5.1.7, but that's my best guess as to what happened.
If you take the OTA normally, the phone will write to the inactive slot and overwrite boot.img as well as all the other partitions, then set the active partition to the new slot
Related
I have flashed stock from googles web site and I have tried everything I can to get a custom rom back on this device. I have tried everything. every thing I do just boots to regular google. But I can flash twrp, and magisk on stock and it works. OEM is unlocked but as soon as I flash a rom then twrp and sign it, it says its successful for everything but when I boot to system it just reboots a couple times then boots but up to stock. Any one have any ideas?
KingAroan said:
I have flashed stock from googles web site and I have tried everything I can to get a custom rom back on this device. I have tried everything. every thing I do just boots to regular google. But I can flash twrp, and magisk on stock and it works. OEM is unlocked but as soon as I flash a rom then twrp and sign it, it says its successful for everything but when I boot to system it just reboots a couple times then boots but up to stock. Any one have any ideas?
Click to expand...
Click to collapse
This is normal. Your custom ROM is flashing to the opposite slot your on. When your done u need to reboot to bootloader and boot twrp then install TWRP again and install verified boot signer zip. If not just going to loop once and boot to the slot that works
mac796 said:
This is normal. Your custom ROM is flashing to the opposite slot your on. When your done u need to reboot to bootloader and boot twrp then install TWRP again and install verified boot signer zip. If not just going to loop once and boot to the slot that works
Click to expand...
Click to collapse
I will try that's next time. I just went through hell trying get back on the RR ROM and rooted with magisk. But I finally got it haha. Took about 20 stock flash's to get it finally working
KingAroan said:
I will try that's next time. I just went through hell trying get back on the RR ROM and rooted with magisk. But I finally got it haha. Took about 20 stock flash's to get it finally working
Click to expand...
Click to collapse
Yea once you do it a couple of times you will have it down. Just remember from May bootloader's on, you have to use that VBS zip. Also keep track of what slot your on when your flashing
mac796 said:
Yea once you do it a couple of times you will have it down. Just remember from May bootloader's on, you have to use that VBS zip. Also keep track of what slot your on when your flashing
Click to expand...
Click to collapse
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
KingAroan said:
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
Click to expand...
Click to collapse
No there the same. You can put whatever on either one. There for normal use. seamless updates they call it I believe.
KingAroan said:
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
Click to expand...
Click to collapse
The different slots are for seamless updates. If you're using the stock rom and taking OTA's, the OTA gets flashed to whatever slot is currently inactive. It used to be when you did an OTA, the OTA got downloaded and then you'd be prompted to reboot to install the update. When you rebooted, the update would get installed but you had to sit and wait for it to install before you could use your phone again. With the two slots, it now downloads the update and installs it to the inactive slot while you continue to use your phone. Eventually you get prompted to reboot but instead of having to wait for it to install, it just reboots like any other time you reboot the phone and there is no wait for the update to install. It's already installed. When it reboots, it switches to the slot that was previously inactive because that's where the update is installed to. So, if you're on slot A when the update is downloaded and installed, you'll be using slot B after you reboot. The next month when the update comes out, it will get installed to the other slot again and you'll once again be using slot A and so on and so on for every month after that.
For a custom rom, they can be installed on either slot. It just depends on which slot is currently active. If slot A is the slot that's currently active, TWRP will flash the rom to slot B. If B is active, the rom will get flashed to A. Anything else gets flashed to the slot that is currently active (SuperSU, Vendor files or what have you). That's why after flash the rom, you have to reboot the phone (either reboot to recovery or the OS) before flashing the rest of whatever it is you want to flash. If you don't reboot before flashing SuperSU or whatever, it won't get flashed to the same slot the rom got flashed to and obviously, this causes issues. Bottom line is, slot A or B, it has nothing to do with whether it's a stock or custom rom. Whichever slot is inactive when you flash a rom is the slot the rom will end up on.
robocuff said:
The different slots are for seamless updates. If you're using the stock rom and taking OTA's, the OTA gets flashed to whatever slot is currently inactive. It used to be when you did an OTA, the OTA got downloaded and then you'd be prompted to reboot to install the update. When you rebooted, the update would get installed but you had to sit and wait for it to install before you could use your phone again. With the two slots, it now downloads the update and installs it to the inactive slot while you continue to use your phone. Eventually you get prompted to reboot but instead of having to wait for it to install, it just reboots like any other time you reboot the phone and there is no wait for the update to install. It's already installed. When it reboots, it switches to the slot that was previously inactive because that's where the update is installed to. So, if you're on slot A when the update is downloaded and installed, you'll be using slot B after you reboot. The next month when the update comes out, it will get installed to the other slot again and you'll once again be using slot A and so on and so on for every month after that.
For a custom rom, they can be installed on either slot. It just depends on which slot is currently active. If slot A is the slot that's currently active, TWRP will flash the rom to slot B. If B is active, the rom will get flashed to A. Anything else gets flashed to the slot that is currently active (SuperSU, Vendor files or what have you). That's why after flash the rom, you have to reboot the phone (either reboot to recovery or the OS) before flashing the rest of whatever it is you want to flash. If you don't reboot before flashing SuperSU or whatever, it won't get flashed to the same slot the rom got flashed to and obviously, this causes issues. Bottom line is, slot A or B, it has nothing to do with whether it's a stock or custom rom. Whichever slot is inactive when you flash a rom is the slot the rom will end up on.
Click to expand...
Click to collapse
Holy ****, i didnt know that part, i just thought it flashed it to your current slot and when you rebooted into system, the slot didnt change.....brb but first a quick titanium backup
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.
Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!
format data when switching to different roms
JohnnyMwanza said:
format data when switching to different roms
Click to expand...
Click to collapse
Now if i format my data, will i be able to boot back to my current rom, evo x? (Sorry, but im a noob)
Backup your data and then oxygen os via fastboot....this worked for me.
MAX TEN said:
Backup your data and then oxygen os via fastboot....this worked for me.
Click to expand...
Click to collapse
You mean, boot to "twrp.img" and then flash oos?
Anmol45 said:
Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!
Click to expand...
Click to collapse
That's actually your internal storage still encrypted, this is a common issue, my recommendation is to try to boot normally after flashing the zips with adb sideload, if your internal storage is still intact then there you go, otherwise reboot to twrp and format internal storage.
Anmol45 said:
Yesterday, I wanted to switch from Evolution X rom to Pixen os on my OnePlus 6. So, I was following the normal procedure .i.e., Flash oos and twrp on both slots, reboot, and then flash pixen. Okay. I successfully flashed oos and twrp on one slot. But, when i rebooted to recovery to flash it again in the other slot, when I went to the "Install" section, I wasn't able to find any of my files! It showed all weird folders like "HGgjajhzYHjwg" . Luckily, since I wasn't able to flash oos on the other slot, I was able to boot to system on the other one, which booted to evolution x (Now I'm currently booted in slot B). What should I do? (I have seen many threads like this, but haven't found a thread on OnePlus 6). Please Help!!
Click to expand...
Click to collapse
Always remove your phone password when changing rom...and always keep backup on your pc or hard drive or somewhere else...and avoid going from one security patch to another... especially when going from new security update to an old one...but mainly remove your password...imo that should help avoiding the data encryption and file corruption
New to the A/B slot root scene, apologies. I also searched but couldn't find an answer for something matching this exact specificity . I know its fixable but I cant figure out what would be best to do.
I am (or was) running TWRP/Magisk on 10.3.4 Stock OOS. broke the OS boot and it will only goes right into fastboot, no TWRP anymore, doesn't even show the warning from OP when booting a rooted OP device.
Weighing my restore options, I changed the active slot with the fastboot command and that slot was able to boot into TWRP just fine, however, the mounting folder that's usually emulated/o (SDcard) was just a bunch of folders with random text and capitalization.
I have a TWRP backup (around 8GB) . Can i just change the active slot back to the non active one and restore to the other? I am concerned i will break it worse or restore it to the wrong slot somehow. If i restored it to both slots, would that be ok?
edit: I connected my TWRP backup and wasn't able to force the restore to another slot. The backup includes Boot, System, Data (excluding storage) and EFS. I could "swipe to restore" at any moment but unsure how that would effect everything seeing as the backup was done on Slot A and now I am on slot B.
I read you should flash the 10.3.4 full while staying on the same slot but was having issues getting it to upload to the phone (no drive mounts on my computer OS on the default slot, only can do so when i change slots) I have a very recent titanium backup i can restore once i am back in, either way.
I am just not 100% exactly how to get myself back up and running.
Lastly, i only started rooted again after a 10-15 year break because I got real sick of the background data the official OOS build was sending. I was interested in converting to LineageOS with gapps form Micro (if it can pass safetynet) but Open to any ROM that could assist in stopping the official background activity. I would love a ROM that can pass safetynet, help with the battery life on my aging OP6 and hopefully keep rocking on Android 10.
Thank you to everyone or anyone that reads this and assists. I know it must be annoying to read what may just be the same question over and over but this exact issue was hard to find another experiencing with the latest OOS.
Take care.
I ended up trying to restore the TWRP backup to the different slot, this put both slots in a fastbootloop. i then flashed all partitions with a fastboot image of 10.3.4 and this fix my phone and got it back up in running. i rooted again, flashed twrp and then tried to restore the TWRP backup again and it completed successfully, however, both slots were back to bootlooping.
i will just wipe all again, root/magisk and then install titanium to restore my full backup of that. Im sure ill be coming to a new issue trying that too, but who knows.
I fixed it the way i wanted (off the backup i made with TWRP) by restoring my backup (without EFS this time, per the tips on the devs website, rebooted into fastboot, flashed the OOS 10.3.4 fastboot image (WITHOUT -w to keep my user files), let it run. when it rebooted i had everything back from the TWRP backup!.
all i did then was boot the TWRP image, flash its zip, then flashed magisk again and rebooted.
All is well! (until Slot B issues rear their ugly head) I really hope to flash both and move to a custom ROM but saying encrypted is more important to me than I thought it was.
I hope anyone who finds themselves in the same stupid situation is helped by this come day.
PS. titanium backup is really not a system restore feature like I thought it would be when you are encrypted. TWRP was my only viable solution and so happy this worked. Ill be running that weekly, for sure.
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?