Develop Bugs

Proper way to setup slot A and Slot B

Hey Guys
With the new ROM's recently released, I wanted to setup the multiple slots.
Currently on stock rooted with elemental x kernel.
I have played around with the slots, but notice that when I switch to slot B, and boot, the data part is the same, but there is no root. For a while I was ok with this but want to get full use out of both.
Can someone advise what is best way to properly utilize both slots for testing (2) different ROM's?
Thanks

docluv01 said:
Hey Guys
With the new ROM's recently released, I wanted to setup the multiple slots.
Currently on stock rooted with elemental x kernel.
I have played around with the slots, but notice that when I switch to slot B, and boot, the data part is the same, but there is no root. For a while I was ok with this but want to get full use out of both.
Can someone advise what is best way to properly utilize both slots for testing (2) different ROM's?
Thanks
Click to expand...
Click to collapse
What Im hearing is you have to set up both roms separately and back up data. Then set up your slots with both roms. When you switch you wipe and restore data. Sounds alot like the previous method of just backing up and restoring with just a little time savings.

Yeah, you can't have two data partitions. The slots are just for the system partition so unless you do the restore/wipe method above, you can only have two "roms" installed with the same data set.
Until someone figures out how to split data partition so work with each slot...

xocomaox said:
Yeah, you can't have two data partitions. The slots are just for the system partition so unless you do the restore/wipe method above, you can only have two "roms" installed with the same data set.
So using the same ROM on both Slot A + B should be fine. And I guess SuperSU is flashed to each slot individually so should be ok to have one Slot Root and one not, with Safetynet covered by custom Kernel.
Is there anywhere this is being discussed more in depth? I'd love to try it but I'm not brave enough to do it with my limited know how!
Click to expand...
Click to collapse

557953 said:
xocomaox said:
Yeah, you can't have two data partitions. The slots are just for the system partition so unless you do the restore/wipe method above, you can only have two "roms" installed with the same data set.
So using the same ROM on both Slot A + B should be fine. And I guess SuperSU is flashed to each slot individually so should be ok to have one Slot Root and one not, with Safetynet covered by custom Kernel.
Is there anywhere this is being discussed more in depth? I'd love to try it but I'm not brave enough to do it with my limited know how!
Click to expand...
Click to collapse
Yes, that is how you could do it. It would work okay.
Click to expand...
Click to collapse

557953 said:
xocomaox said:
Yeah, you can't have two data partitions. The slots are just for the system partition so unless you do the restore/wipe method above, you can only have two "roms" installed with the same data set.
So using the same ROM on both Slot A + B should be fine. And I guess SuperSU is flashed to each slot individually so should be ok to have one Slot Root and one not, with Safetynet covered by custom Kernel.
Is there anywhere this is being discussed more in depth? I'd love to try it but I'm not brave enough to do it with my limited know how!
Click to expand...
Click to collapse
Unfortunately not. These discussions or scattered over many threads. I really don't need dual boot. It would be nice to understand as much as we can about the slots and flashing to those slots.
Click to expand...
Click to collapse

I am dual booting now, but really limited value. I just have stock on both slots, TWRP and elemental X with on side rooted. The idea is just to use Android Pay on the non-root slot. It works, but really not worth your time except as an exercise
Sent from my Pixel XL using Tapatalk

yearn2burn said:
I am dual booting now, but really limited value. I just have stock on both slots, TWRP and elemental X with on side rooted. The idea is just to use Android Pay on the non-root slot. It works, but really not worth your time except as an exercise
Click to expand...
Click to collapse
Thats the best use case for dual booting I have seen yet. For Android pay, bank apps, Pokémon go, etc...

yearn2burn said:
I am dual booting now, but really limited value. I just have stock on both slots, TWRP and elemental X with on side rooted. The idea is just to use Android Pay on the non-root slot. It works, but really not worth your time except as an exercise
Click to expand...
Click to collapse
Would you mind giving us a quick run down on how you did it. I assume manually flashing everything except user data?

I'm keen to know how also, it's worth it for me and probably quite a lot of others here

TonikJDK said:
Would you mind giving us a quick run down on how you did it. I assume manually flashing everything except user data?
Click to expand...
Click to collapse
Really easy. When you initially install TWRP from the fastboot boot /path/to/TWRP.img process, that installs TWRP to both slots. However, when you reboot to TWRP, you're booting to whatever slot was active last. When you install SuperSU and a kernel, they install to that slot. The other is still stock except TWRP.
To set up the other slot, within TWRP simply tap reboot to see which slot is active. Tap the other slot to make it active, back out and install (or not) whatever you want.
One catch is that second slot may not be updated. Let's say you're booting on slot A. If you take an OTA update, it will simply update slot B and then reboot to slot B leaving A unchanged.
To find out if you're ready in the alternate slot, simply try to reboot to system after switching slots. Three possible results. One, it boots up fine. Check settings/about phone shows the current version. Second, it boots fine, but about phone shows the prior build. In that case, you need to ADB fastboot flash system_x path/to/system.img and maybe vendor.img. Not sure about flashing updated bootloader but try going without it to see if you boot correctly. Final scenario which I got the first time I tried booting to the second slot, it boot loops a couple times and finally boots to the previously active slot. That means something is missing that you need to fastboot flash as in second scenario.
The main thing for me is it's very informative just going through the exercises of dual booting. Give it a go.
Sent from my Pixel XL using Tapatalk

yearn2burn said:
Really easy. When you initially install TWRP from the fastboot boot /path/to/TWRP.img process, that installs TWRP to both slots. However, when you reboot to TWRP, you're booting to whatever slot was active last. When you install SuperSU and a kernel, they install to that slot. The other is still stock except TWRP.
To set up the other slot, within TWRP simply tap reboot to see which slot is active. Tap the other slot to make it active, back out and install (or not) whatever you want.
One catch is that second slot may not be updated. Let's say you're booting on slot A. If you take an OTA update, it will simply update slot B and then reboot to slot B leaving A unchanged.
To find out if you're ready in the alternate slot, simply try to reboot to system after switching slots. Three possible results. One, it boots up fine. Check settings/about phone shows the current version. Second, it boots fine, but about phone shows the prior build. In that case, you need to ADB fastboot flash system_x path/to/system.img and maybe vendor.img. Not sure about flashing updated bootloader but try going without it to see if you boot correctly. Final scenario which I got the first time I tried booting to the second slot, it boot loops a couple times and finally boots to the previously active slot. That means something is missing that you need to fastboot flash as in second scenario.
The main thing for me is it's very informative just going through the exercises of dual booting. Give it a go.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thanks for posting this info had no idea it will be essentially be possible just with TWRP!

Both result one and third happened to me ever.
For result one, I can boot to the other slot, in which system unroofed, safety net patched kernel indtslled, can use bank apps but can't access quick settings and developers option etc. Finally, had to wipe userdata to fix it.
For result third, I have no idea how to figure out.
To sum up, two slots give us the possibility of dual booting.
But still a little way to go. Hope the distinguished developers can make this easier and useful in the near future.
yearn2burn said:
Really easy. When you initially install TWRP from the fastboot boot /path/to/TWRP.img process, that installs TWRP to both slots. However, when you reboot to TWRP, you're booting to whatever slot was active last. When you install SuperSU and a kernel, they install to that slot. The other is still stock except TWRP.
To set up the other slot, within TWRP simply tap reboot to see which slot is active. Tap the other slot to make it active, back out and install (or not) whatever you want.
One catch is that second slot may not be updated. Let's say you're booting on slot A. If you take an OTA update, it will simply update slot B and then reboot to slot B leaving A unchanged.
To find out if you're ready in the alternate slot, simply try to reboot to system after switching slots. Three possible results. One, it boots up fine. Check settings/about phone shows the current version. Second, it boots fine, but about phone shows the prior build. In that case, you need to ADB fastboot flash system_x path/to/system.img and maybe vendor.img. Not sure about flashing updated bootloader but try going without it to see if you boot correctly. Final scenario which I got the first time I tried booting to the second slot, it boot loops a couple times and finally boots to the previously active slot. That means something is missing that you need to fastboot flash as in second scenario.
The main thing for me is it's very informative just going through the exercises of dual booting. Give it a go.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse

bush911 said:
Both result one and third happened to me ever.
For result one, I can boot to the other slot, in which system unroofed, safety net patched kernel indtslled, can use bank apps but can't access quick settings and developers option etc. Finally, had to wipe userdata to fix it.
For result third, I have no idea how to figure out.
Click to expand...
Click to collapse
If you have a custom ROM on one slot and stock on the other, you best not dual boot. In essence, it's like one or both slots will be the equivalent of a dirty flashed ROM.
To reiterate for third result where you switch slots (slot X to slot Y.) Boot system on slot Y results in a few boot loop cycles before finally booting into slot X again. You need to flash system.img to slot Y then try again.
Sent from my Pixel XL using Tapatalk

Well noted, never used custom ROM on Pixel. Will try dual boot again by chance.
yearn2burn said:
If you have a custom ROM on one slot and stock on the other, you best not dual boot. In essence, it's like one or both slots will be the equivalent of a dirty flashed ROM.
To reiterate for third result where you switch slots (slot X to slot Y.) Boot system on slot Y results in a few boot loop cycles before finally booting into slot X again. You need to flash system.img to slot Y then try again.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse

yearn2burn said:
Really easy. When you initially install TWRP from the fastboot boot /path/to/TWRP.img process, that installs TWRP to both slots. However, when you reboot to TWRP, you're booting to whatever slot was active last. When you install SuperSU and a kernel, they install to that slot. The other is still stock except TWRP.
To set up the other slot, within TWRP simply tap reboot to see which slot is active. Tap the other slot to make it active, back out and install (or not) whatever you want.
One catch is that second slot may not be updated. Let's say you're booting on slot A. If you take an OTA update, it will simply update slot B and then reboot to slot B leaving A unchanged.
To find out if you're ready in the alternate slot, simply try to reboot to system after switching slots. Three possible results. One, it boots up fine. Check settings/about phone shows the current version. Second, it boots fine, but about phone shows the prior build. In that case, you need to ADB fastboot flash system_x path/to/system.img and maybe vendor.img. Not sure about flashing updated bootloader but try going without it to see if you boot correctly. Final scenario which I got the first time I tried booting to the second slot, it boot loops a couple times and finally boots to the previously active slot. That means something is missing that you need to fastboot flash as in second scenario.
The main thing for me is it's very informative just going through the exercises of dual booting. Give it a go.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Just 2 quick question's, I assume will be easy one's
So running, Pure Nexus on Slot A and just flashed same rom in Slot B with TWRP, I got a message saying unable to mount system.img so I assume I'll need to flash system.img from Pure Nexus payload.bin? Thing is I cannot extract payload.bin, Power ISO says it is unsupported so I'm at a bit of a loss!
I assume the Bootloader is active to both Slots A + B? I don't wanna boot to Slot B and end up with a paperweight!
Thanksagain for your info

This stuff is confusing lol. If I wanted to treat it just like the old partition setup couldn't I theoretically just install TWRP on the primary slot, root and ROM that same slot, and backup just that slot and just leave the other slot alone completely?

gmac1990 said:
This stuff is confusing lol. If I wanted to treat it just like the old partition setup couldn't I theoretically just install TWRP on the primary slot, root and ROM that same slot, and backup just that slot and just leave the other slot alone completely?
Click to expand...
Click to collapse
That is what I would suggest you do.

TonikJDK said:
That is what I would suggest you do.
Click to expand...
Click to collapse
A lot of people seem to be doing the dual slot thing. Is there a benefit or is it almost a requirement?

I basically installed the factory image without the -w flag, turn booted in TWRP (without flashing TWRP) and installed kernel, then flashed super SU then rebooted. Didn't work so I rebooted in TWRP and flashed TWRP and then flashed SuperSU. Note that I had SuperSU installed in 7.1.1 so I assumed it would overwrite. It didn't work so I uninstalled old SuperSU and re-flashed SuperSU 2.79. it still didn't work so I downgraded SuperSU and TWRP one release and reinstalled. Still no go. And that's where I'm at.
---------- Post added at 09:18 AM ---------- Previous post was at 08:47 AM ----------
Better question is, how do we select what slot stuff gets installed in? It doesn't seem to be clear, more like a game of chance!

Factory Reset

Can we factory reset one slot only? or does it do both?
I've got stock/root/magisk/elx on slot A, and thinking of trying a custom ROM on slot b.
could I reset slot B only to do this without upsetting slot A?
or would it be total reset, then install ROM on slot B and then redo stock on slot A?
I have a feeling it's the total reset, but would prefer not to lose what I have on slot A if possible

My understanding is that a factory data reset primarily affects userdata, since changes to other partitions were typically unaffected by a factory data reset on my prior phone. As noted in the following link, this phone only has one userdata, which is shared by the two slots. If you factory data reset the Pixel my expectation is for the userdata partition to be reset, so you will lose user apps, app data, and other user settings. I'd expect the slots to likely to be largely unaffected by a factory data reset, so whatever you have on slots A and B will probably remain through a factory data reset. I'm not familiar enough with Magisk and ElementalX to know if there are any parts of either install that goes to userdata, which might be wiped out with a factory data reset.
http://www.androidpolice.com/2016/1...-partition-changes-and-new-fastboot-commands/

I don't think slots A and B allow you to run different Roms on each slot like dual booting on a computer because when you install a Rom on one slot it also installs some information on the other slot. They weren't really designed for what you want to use the slots for. It's possible you would be able to boot into different Roms if you installed one in slot a and a different one in slot b but I suspect there would be other problems once you did so. If you try this you should post your results.

jhs39 said:
I don't think slots A and B allow you to run different Roms on each slot like dual booting on a computer because when you install a Rom on one slot it also installs some information on the other slot. They weren't really designed for what you want to use the slots for. It's possible you would be able to boot into different Roms if you installed one in slot a and a different one in slot b but I suspect there would be other problems once you did so. If you try this you should post your results.
Click to expand...
Click to collapse
I've got non rooted stock on slot b and slot a has rooted stock.
I'm sure i've read previously that someone has a rom on one slot and stock on the other, but it's hard to narrow that down in the search...
if anyone does have a dual booted pixel/xl then that would be great to know

y2grae said:
I've got non rooted stock on slot b and slot a has rooted stock.
I'm sure i've read previously that someone has a rom on one slot and stock on the other, but it's hard to narrow that down in the search...
if anyone does have a dual booted pixel/xl then that would be great to know
Click to expand...
Click to collapse
I believe you can only run the same base on both slots due to the fact that they share a data partition. I don't think you can run stock on one and aosp on the other.

y2grae said:
I've got non rooted stock on slot b and slot a has rooted stock.
I'm sure i've read previously that someone has a rom on one slot and stock on the other, but it's hard to narrow that down in the search...
if anyone does have a dual booted pixel/xl then that would be great to know
Click to expand...
Click to collapse
Yea I'm setup to dual boot. You have to have same in each slot. So you can have pn rooted in one and pn unrooted in other. Or stock and stock rooted. Anything different and u get errors like crazy.

mac796 said:
Yea I'm setup to dual boot. You have to have same in each slot. So you can have pn rooted in one and pn unrooted in other. Or stock and stock rooted. Anything different and u get errors like crazy.
Click to expand...
Click to collapse
Cheers Mac, was thinking of trying either unholy or one of the other slightly different varients, but if it's going to error to hell and back... not worth it

y2grae said:
Cheers Mac, was thinking of trying either unholy or one of the other slightly different varients, but if it's going to error to hell and back... not worth it
Click to expand...
Click to collapse
It'll work with Unholy it should work with any of them just got to make sure and have that same one in the other slot

Here's what the modified flash all bat looks like. Sorry not the best picture. After u flash just change everything from a to b. Then after you flash stock to both slots , you can boot TWRP and flash whatever custom ROMs u want to both slots

mac796 said:
Here's what the modified flash all bat looks like. Sorry not the best picture. After u flash just change everything from a to b. Then after you flash stock to both slots , you can boot TWRP and flash whatever custom ROMs u want to both slots
Click to expand...
Click to collapse
Ah, no. I want to keep my rooted/stock/elemental on slot A and put a custom Rom on slot B
slot B is currently just stock. (probably/possibly without ele as it should only flash to the slot in question from my understanding)

y2grae said:
Ah, no. I want to keep my rooted/stock/elemental on slot A and put a custom Rom on slot B
Click to expand...
Click to collapse
I have not seen anyone pull that off. They are not fully seperate slots, its not a full dual boot system. Quite a few items a common between the two slots.

TonikJDK said:
I have not seen anyone pull that off. They are not fully seperate slots, its not a full dual boot system. Quite a few items a common between the two slots.
Click to expand...
Click to collapse
that's a shame, but thanks for the response.
what's the "shared" area of it then?
i know user data would be, as i've got the same info on both boots

My bootloader keeps relocking itself!

I have been trying to flash Lineage 15.1 (or any rom for that matter!) and the bootloader keeps relocking itself. I am at my the end of my patience. After I think everything goes fine, the initial what I think to be the 1st boot comes up with the "Your device software is corrupt and cant be started" message and I boot to bootloader and sure enough, "oem locked" is BACK AGAIN. What could be causing this? I am far from new to flashing roms but damn this thing is kicking my tail. The stock rom seems to boot fine now, but its sooo buggy and most importantly of why Im trying to rom, the phone bootloops with an SD card inserted.
EDIT: Maybe it has something to do with the 2 different slots, A and B? Ive never delt with this kinda thing before.
I really hate the stock rom with it being so buggy and it wont read my SD cards correctly but Im about to stick with it cause of this. Any help will be appreciated!!

Josh McGrath said:
I have been trying to flash Lineage 15.1 (or any rom for that matter!) and the bootloader keeps relocking itself. I am at my the end of my patience. After I think everything goes fine, the initial what I think to be the 1st boot comes up with the "Your device software is corrupt and cant be started" message and I boot to bootloader and sure enough, "oem locked" is BACK AGAIN. What could be causing this? I am far from new to flashing roms but damn this thing is kicking my tail. The stock rom seems to boot fine now, but its sooo buggy and most importantly of why Im trying to rom, the phone bootloops with an SD card inserted.
EDIT: Maybe it has something to do with the 2 different slots, A and B? Ive never delt with this kinda thing before.
I really hate the stock rom with it being so buggy and it wont read my SD cards correctly but Im about to stick with it cause of this. Any help will be appreciated!!
Click to expand...
Click to collapse
I'm not sure about Los, a quick look shows it has a different flashing process than DU or Aosip, so I can't comment on that. I know that when you flash DU or Aosip from stock #1 there is a 27.1 tmo/sprint pre flash zip that must be flashed or you'll fail, #2 you have to fastboot -w at the end to erase userdata and such, which I believe is shared between both slots but only used by the currently active. The bootloader re-lock is weird, but as far as the corrupt software, it does sound like a discrepancy between the two slots. That's what the 27.1 pre flash zip is for, it flashes both slots with the same base so they don't trip over each other. You might even need to flash it before you install Los, I haven't tried that one yet, just DU and Aosip so far. Aosip was the first one I tried, and the guide works perfectly, and the same guide works for DU as well. Have you flashed the pre flash zips before trying any roms?

Your bootloader is locking itself because you didn't flash the firmware. Flash the firmware in AOSiP thread to stop that from happening.

41rw4lk said:
I know that when you flash DU or Aosip from stock #1 there is a 27.1 tmo/sprint pre flash zip that must be flashed or you'll fail, #2 you have to fastboot -w at the end to erase userdata and such, which I believe is shared between both slots but only used by the currently active. The bootloader re-lock is weird, but as far as the corrupt software, it does sound like a discrepancy between the two slots.
Click to expand...
Click to collapse
Yes. If you're on a device with Oreo on one slot and Nougat on another, flashing the ROM will make the device fall over on it's heels and smack it's face on the pavement. (Relock itself to prevent damage).
Yes, /data doesn't have a second slot, only firmware files, OEM and system are two slotted.

Uzephi said:
Yes. If you're on a device with Oreo on one slot and Nougat on another, flashing the ROM will make the device fall over on it's heels and smack it's face on the pavement. (Relock itself to prevent damage).
Yes, /data doesn't have a second slot, only firmware files, OEM and system are two slotted.
Click to expand...
Click to collapse
Well this is my 4th replacement which the 1st one was the only one that was my fault as I didn't install aosip correctly and it said "no os installed" and I rebooted anyway, insta 9008 brick.
All of them shipped with Oreo on them so I assume they would be on both slots
Sent from my [device_name] using XDA-Developers Legacy app

Josh McGrath said:
Well this is my 4th replacement which the 1st one was the only one that was my fault as I didn't install aosip correctly and it said "no os installed" and I rebooted anyway, insta 9008 brick.
All of them shipped with Oreo on them so I assume they would be on both slots
Click to expand...
Click to collapse
You give Motorola too much credit. Flash the firmware and you'll be golden. I know this. I recovered from that brick.

Uzephi said:
You give Motorola too much credit. Flash the firmware and you'll be golden. I know this. I recovered from that brick.
Click to expand...
Click to collapse
How did you recover from the 9008 brick? My screen wouldn't even come on.
I feel like I am asking for someone to hold my hand with this device but when you say flash the firmware, do you mean flash twice, one to slot a and one slot b?
Also, does oem need to be wiped in twrp? I can't find any info on that either.

41rw4lk said:
Have you flashed the pre flash zips before trying any roms?
Click to expand...
Click to collapse
I actually have not flashed any firmware files when I tried any roms. I'm running stock rom now and the texting bugs are making me lose my mind.
Thanks for the help, I really appreciate it. This phone confuses me ?

Josh McGrath said:
How did you recover from the 9008 brick? My screen wouldn't even come on.
I feel like I am asking for someone to hold my hand with this device but when you say flash the firmware, do you mean flash twice, one to slot a and one slot b?
Also, does oem need to be wiped in twrp? I can't find any info on that either.
Click to expand...
Click to collapse
There is a blank flash floating around somewhere. It's on Invisiblek's site. It was the only way to fix the issue. It put me back on nougat and had to take Oreo OTA again.
Edit: the .bat file that flashes the firmware will flash it to both slots

Uzephi said:
There is a blank flash floating around somewhere. It's on Invisiblek's site. It was the only way to fix the issue. It put me back on nougat and had to take Oreo OTA again.
Edit: the .bat file that flashes the firmware will flash it to both slots
Click to expand...
Click to collapse
Wow. I'm impressed with Motorola that they actually made it fixable with the 9008 mode. I have that flash all so I guess if I screw up it's not the end of my phone at least.
Sent from my [device_name] using XDA-Developers Legacy app

How do I change to older version???

I want to test something by going from May patch back to March without wiping data.
Can I just flash-all (without -w) or do it manually with selected files.
If I go manually is it enough to do the following? bootloader, boot, radio, recovery, system and vendor
Thanks

I would do the whole flash all bat with -w removed.

wangdaning said:
I would do the whole flash all bat with -w removed.
Click to expand...
Click to collapse
Tried it again and does not work. Does the same as the first time. I get a white screen with a big G and moving bar underneath and nothing happens.
Reflash the current and it boots fine but does seam to work this way.

Probably something with the A/B partition scheme. Maybe you have to apply it to both slots for it to work, though I would be careful with that.

wangdaning said:
Probably something with the A/B partition scheme. Maybe you have to apply it to both slots for it to work, though I would be careful with that.
Click to expand...
Click to collapse
If I do that would I do it this way?
flash-all in slot a, then since it wont boot, change active slot to b then flash-all again in this this slot
Shouldn't I be able to change slot and it would boot normally? Because right now when I change slot it does not work. I either have to got back to original slot or flash again in that new slot. I did not try flashing old version in both slots yet.

You are getting the white screen because you didn't wipe data. You will need to do a full wipe to go backwards.

TonikJDK said:
You are getting the white screen because you didn't wipe data. You will need to do a full wipe to go backwards.
Click to expand...
Click to collapse
darn it. I'll take your word on this one because it just makes sense with all the testing I've done.
I'll ask this again. If I change active slots, shouldn't it just boot up normally?
With all the reading I did on slots one thing I got is that I thought we would be able to do that. Like installing 2 different roms and dual booting.

Ok so I did some more reading on a b slors to refremy memory and you can't dual boot...
But I still think i should be able to boot when choosing the other slot.

I think the issue is that going back it checks the other slot and if they don't match it will not boot. I am not 100% for that though.

Normally the active slot always has the newer version. When there's an update it installs in the inactive slot which has the older version. Booting the slot with the older version should not be a problem because it there ia a problem with the update on tje other slot then it reverts back to the slot with the older version.

Question reason for partition not flashing in fastbootd

so I used fastboot to attempt to recover slot B on my phone (slot A is fine and boots) by dumping oos 11.2.7.7AA and manually flashing each and every partition, which goes fine except when switching over to fastbootd (via fastboot reboot fastboot) it will not flash odm, product, system_ext, or vendor, it reports that the partition cannot be found/no such file or directory. I mean I am attempting to flash those partitions so I do not understand how it cannot be found because I am flashing them. this is preventing me from restoring oos to slot B. does anyone know if I can force flash those partitions, or why fastbootd will not flash those four? I would be up and running if I could just flash those four so I can have a functional slot B.

I also tried this last night and had the same result on my slot b. I thought maybe it was because a file was consumed from my payload dump (since I had used the same files for slot a) but if you had the same issue then maybe slot b doesn't contain all partitions. Wish I knew how to check that though

shmallow said:
I also tried this last night and had the same result on my slot b. I thought maybe it was because a file was consumed from my payload dump (since I had used the same files for slot a) but if you had the same issue then maybe slot b doesn't contain all partitions. Wish I knew how to check that though
Click to expand...
Click to collapse
so you were unable to flash via fastbootd the product, system_ext, odm partitions either? interesting, but how did you get up and running then, did you fastboot flash all those files to slot A? I have been searching for a week for a solution to repair slot B, every forum, every thread, even asking in random telegram groups on how to fix this, but can't find anyone that knows what to do

If you are in twrp what does it say when you try to mount the partition? I had this issue on my old oneplus 3t, ended up having to follow a guide where I changed the filesystem of the partition to one, then back. I'm not even sure if that's possible with the current version of twrp we have.

thirtythr33 said:
so you were unable to flash via fastbootd the product, system_ext, odm partitions either? interesting, but how did you get up and running then, did you fastboot flash all those files to slot A? I have been searching for a week for a solution to repair slot B, every forum, every thread, even asking in random telegram groups on how to fix this, but can't find anyone that knows what to do
Click to expand...
Click to collapse
First I had done this procedure to slot a. Figured I probably needed to do the same to slot b so I switched to slot b through TWRP, ran the script and yup product, system, system_ext, vendor and odm failed to flash. At that point I just switched back to slot a and breathed a sigh of relief that it didn't mess with that.

Haunt3r said:
If you are in twrp what does it say when you try to mount the partition? I had this issue on my old oneplus 3t, ended up having to follow a guide where I changed the filesystem of the partition to one, then back. I'm not even sure if that's possible with the current version of twrp we have.
Click to expand...
Click to collapse
yeah I thought of that too, so before flashing oos in twrp I tried to mount odm, product, and system_ext, but none will mount and it errors out saying unable to mount partition - not found. thing is I am only using twrp to flash (or attempting to) because I get 'installation failed' in local update in system.

shmallow said:
First I had done this procedure to slot a. Figured I probably needed to do the same to slot b so I switched to slot b through TWRP, ran the script and yup product, system, system_ext, vendor and odm failed to flash. At that point I just switched back to slot a and breathed a sigh of relief that it didn't mess with that.
Click to expand...
Click to collapse
yeah those partitions flash on slot A no issue, but it is slot B that I get the error as well. I hate giving up and not fixing things, that is why I am trying so hard. I just do not understand how my phone boots fine on slot A yet I do not have those partitions

thirtythr33 said:
yeah those partitions flash on slot A no issue, but it is slot B that I get the error as well. I hate giving up and not fixing things, that is why I am trying so hard. I just do not understand how my phone boots fine on slot A yet I do not have those partitions
Click to expand...
Click to collapse
I feel you, that's why I was trying to get it back up too. At this point I think it might be a rabbit hole for me. Until someone proves to me that slot b is actually a full mirror of slot a, I'm just going to assume it's a partial mirror. As it is, as long as I can boot into the bootloader I should always be able to recover slot a. So I'll just pretend b doesn't exist XD

shmallow said:
I feel you, that's why I was trying to get it back up too. At this point I think it might be a rabbit hole for me. Until someone proves to me that slot b is actually a full mirror of slot a, I'm just going to assume it's a partial mirror. As it is, as long as I can boot into the bootloader I should always be able to recover slot a. So I'll just pretend b doesn't exist XD
Click to expand...
Click to collapse
haha yeah I'm stuck with a functioning slot A and a borked B. wait so did you update your oos via fastboot? in other words, I am on 11.2.4.4AA on slot A, I wonder if I can fastboot flash 11.2.7.7AA just like an update would
ok so you ran the fastboot script on slot A. ok well that is what I'll have to try.

thirtythr33 said:
haha yeah I'm stuck with a functioning slot A and a borked B. wait so did you update your oos via fastboot? in other words, I am on 11.2.4.4AA on slot A, I wonder if I can fastboot flash 11.2.7.7AA just like an update would
Click to expand...
Click to collapse
I was coming from LOS so I definitely wasn't on an older version of OOS. I can't quite remember if I wiped beforehand; I think I must have because I don't think it would have worked otherwise. I don't see why you wouldn't be able to flash 11.2.7.7AA on top.. but if its a functional rom it's probably safer to just run their updater instead.

shmallow said:
I was coming from LOS so I definitely wasn't on an older version of OOS. I can't quite remember if I wiped beforehand; I think I must have because I don't think it would have worked otherwise. I don't see why you wouldn't be able to flash 11.2.7.7AA on top.. but if its a functional rom it's probably safer to just run their updater instead.
Click to expand...
Click to collapse
yeah I am on stock oos 11.2.4.4AA, trying to update to 11.2.7.7AA, so even if I switch to slot B in twrp then try to flash oos it still errors out with missing those partitions, so essentially there is no way to update my oos/rom the normal way, twrp or local update, so I am stuck with fastboot flashing all the partition imgs in order to update. fml

thirtythr33 said:
yeah I am on stock oos 11.2.4.4AA, trying to update to 11.2.7.7AA, this is even if I switch to slot B in twrp then try to flash oos it still errors out with missing those partitions, so essentially there is no way to update my oos/rom the normal way, twrp or local update, so I am stuck with fastboot flashing all the partition imgs in order to update. fml
Click to expand...
Click to collapse
Good luck!! Hopefully it works out. I think the only risk is you may lose data, but just doing the same fastboot flash to slot a should work i think. I did it multiple times on a. the second time was because I was going to try a second time to flash onto slot b but forgot to change to slot b... that's when i realized i probably should stop going down that rabbit hole lol.

shmallow said:
Good luck!! Hopefully it works out. I think the only risk is you may lose data, but just doing the same fastboot flash to slot a should work i think. I did it multiple times on a. the second time was because I was going to try a second time to flash onto slot b but forgot to change to slot b... that's when i realized i probably should stop going down that rabbit hole lol.
Click to expand...
Click to collapse
yeah thanks man. the thing is I can prevent fastboot from wiping by just running the flash commands manually, and leaving out the fastboot -w command. but yeah this is a nightmare

thirtythr33 said:
yeah thanks man. the thing is I can prevent fastboot from wiping by just running the flash commands manually, and leaving out the fastboot -w command. but yeah this is a nightmare
Click to expand...
Click to collapse
If you are on oos use local update in system and do full update should fix your inactive slot. At least did for me on my 6t

toolhas4degrees said:
If you are on oos use local update in system and do full update should fix your inactive slot. At least did for me on my 6t
Click to expand...
Click to collapse
yeah man if only I could, I get installation failed in local update, which is the reason why I then tried twrp, but that gives me the partition missing errors, so essentially I cannot flash/update oos/rom

thirtythr33 said:
yeah man if only I could, I get installation failed in local update, which is the reason why I then tried twrp, but that gives me the partition missing errors, so essentially I cannot flash/update oos/rom
Click to expand...
Click to collapse
Did you try multiple times I had it fail on the first time and go through on the 2nd. If that doesn't work look to the msm tool

toolhas4degrees said:
If you are on oos use local update in system and do full update should fix your inactive slot. At least did for me on my 6t
Click to expand...
Click to collapse
this fixed my slot b issues. slot b now boots to OOS. good to know, thanks for that

toolhas4degrees said:
Did you try multiple times I had it fail on the first time and go through on the 2nd. If that doesn't work look to the msm tool
Click to expand...
Click to collapse
hm yeah I did, I attempt to local update with official full AA (11.2.7.7) and it gives me installation failed as soon as I start the process, it actually doesn't even progress at all. that is the most frustrating part (well, all of it is actually)
thing is I have been doing it this way since my 6T, and never had an issue.

thirtythr33 said:
hm yeah I did, I attempt to local update with official full AA (11.2.7.7) and it gives me installation failed as soon as I start the process, it actually doesn't even progress at all. that is the most frustrating part (well, all of it is actually)
thing is I have been doing it this way since my 6T, and never had an issue.
Click to expand...
Click to collapse
Did you try doing local update with 11.2.4.4AA? It might at least give you a solid 11.2.4.4AA b slot

shmallow said:
Did you try doing local update with 11.2.4.4AA? It might at least give you a solid 11.2.4.4AA b slot
Click to expand...
Click to collapse
yep I did, which makes me want to explode with frustration lol. both 11.2.4.4 (my current rom on slot A) and the new 11.2.7.7 will not flash in local update or twrp. so yeah fml