Related
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!
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.bat WITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.bat WITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Anutter226 said:
I have re-flashed factory firmware multiple times now, but I'm still not 100% sure if both boot slots are 100% factory.
Usually after I execute flash-all.batWITH userdata format, it always reflashes slot A. (besides system_other) Does this mean that boot slot B is not "fresh"???
I'm assuming not because I was on NMF26Q and I wanted to flash Resurrection Remix, which is requiring NOF26V vendor image. After I executed flash-all.batWITH userdata format and flashing RR, I was on boot slot B and it showed that my vendor image was NMF26Q.
Is there a way to flash both boot slots in case of a RMA and I need to relock bootloader?
* Yes my platform-tools are up to date.
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
I imagine it's overkill but you could just switch the active slot and run flash-all again. As a precaution I would recommend booting into the OS after the first flash-all to make sure it flashed ok. If there happens to be some problem like a bad flash or wrong download you want to be sure that the "other" slot is bootable. Otherwise you might end up with a pair of unbootable slots which could get sticky.
Anutter226 said:
* Yes I watch it flash everything till the end with out fail.
Click to expand...
Click to collapse
then you saw that flash-all.bat flashed both slots
V40 said:
then you saw that flash-all.bat flashed both slots
Click to expand...
Click to collapse
Doesn't flash to both slots on mine
canemaxx said:
Doesn't flash to both slots on mine
Click to expand...
Click to collapse
I believe it flashes to one slot and deletes the data on the other as standard
If you guys would read your terminal output after flashing you would know what gets flashed where. People are making this way to complicated. It is a big change from previous devices but once you know the partitions its pretty easy.
One data slot shared by A + B
Slot A & B have separate partitions for
-Vendor
-Bootloader
-Radio
-Modem
-Boot
-System
Flashall.bat flashes your active slot and installs system_other.img to the inactive system partition and wipes data, unless you edit the flashall.bat and erase -w.
Thats it. Now, how people are handling the two slots is another story. I keep both slots identical. Having two different bootloaders is a recipe for bricks in my opinion.
FWIW, I endorse the post above this one. I would only add if you get in trouble flash all without the -w and then change the active slot and flash all without the-w again.
Golf c said:
Having two different bootloaders is a recipe for bricks in my opinion.
Click to expand...
Click to collapse
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
5.1 said:
Hello,
This makes me think:
With April stock on slot a for example, you accept May OTA... It will write the new bootloader to the inactive slot b.
So there will be two different bootloader anyway, no?
Cheers...
Click to expand...
Click to collapse
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Golf c said:
Yes but your not flashing custom roms and switching slots every flash. Flashing custom roms switches to the inactive slot. Food for thought. I don't know or want to know to much about hard bricking, but Afaik most of the hard bricks involve OTA's. Hence my best practices theory. Same bootloader in both slots. Somebody with more brick knowledge please correct me if I'm wrong?
Click to expand...
Click to collapse
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
5.1 said:
Hey,
I started fresh before Pure Nexus and flashed NHG47K to both slots.
Anyway, i wiped, reinstalled, a few times since. But the ROM keeps installing to the same slot. It doesn't switch. The second slot still has stock install.
Switched a to b and booted stock. Switch back on a and back to PN...
Of course i'm no expert or developer either.
Where I agree is that custom could create problems I don't know either.
Cheers...
Click to expand...
Click to collapse
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Golf c said:
Never heard of this. Some people are flashing the same slot on purpose by switching slots before they flash the rom. I have never had any rom I have tried not switch slots. I haven't been on stock since Dirty Unicorns came out in December.
Click to expand...
Click to collapse
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
5.1 said:
Hey,
Maybe I'm doing it the wrong way then
Well, I kept having a weird issue, so just rebooted to TWRP, wipe everything except internal storage and reinstall from here: ROM, TWRP zip, reboot TWRP > reinstall vendor, reboot... Never switched slot.
Check this: https://postimg.org/gallery/2muhcz91o/
Slot a is PN, slot b is stock NHG47K.
Cheers...
Click to expand...
Click to collapse
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Golf c said:
Somehow you must be switching slots before flashing PN. There is several ways to do it. I think as long as you know what's in the inactive slot, you should be good. My problem is the people that always flash to the same slot could have old bootloaders from who knows what build. You hit the wrong button and your dead.
Click to expand...
Click to collapse
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
5.1 said:
Hey,
If I do it, i sincerely don't know how or when...
By the way, i just noticed a few apps misbehaving when i manually switched slot from bootloader to boot stock... Now I'm back on PN, i see it kind of messed up some apps permissions. And my browser kept FC even though I wiped its data and cache. Had to reinstall it, lol.
Well, I guess I'll have to install my phone over again...
Cheers...
Click to expand...
Click to collapse
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Golf c said:
Delete
---------- Post added at 11:54 PM ---------- Previous post was at 11:48 PM ----------
Afaik you can't run two different roms on Pixel because of the shared data partition. Hence your app problems. I heard stories about people doing it with some quasi work arounds. I think you can run same rom, one rooted, one non rooted. Not worth the reboot for me.
Click to expand...
Click to collapse
Hey,
I did it just to show something to someone earlier. I don't need dual boot either...
One ROM is enough in my opinion.
Ok, time to hit the bed. See you later...
Cheers...
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
TonikJDK said:
People are looking at this setup like a dual boot computer setup. That isnt what it is or how it works. Its using the same data....which includes all your settings. Boot, kernel and ram disk are in one partition now. There are a ton of moving parts we don't even know about.
This is a fancy update system, just like Chromebooks and iPhones.
Click to expand...
Click to collapse
And I don't even use it because I have never taken an OTA. lol!
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
canemaxx said:
I'm glad I read this thread. I have just installed the L build and flashed the April bootloader. This took place on slot b and I want slot a to match ....what would the process be to do that? Any help is greatly appreciated
Click to expand...
Click to collapse
No need since it ia working but you get into Fastboot mode then
Fastboot set_active a
Flash L, flash April bootloadee.
Explain this to me.. I was having issue with my contacts stopping each time I opened it.. So I went into twrp and did a wipe of cache and data.. Then reboot and reset up phone.. Now I expected all the bloat to come back, but did not expect to find under about phone, the May 2018 Security patch. when I upgraded to the July 2018 security patch.. Is this because the bootloader is unlocked. Now stupid phone keeps telling me there is a system update... How can I get rid of the update message to disappear.
I followed Uzephi threat found here, then rerooted and did my thing... This crap happened after I went back to 100 percent stock, reinstalled twrp, and re-rooted.
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783
This is turning out by far to be my worst investment in phones...
Sounds like your a/b partitions got swapped. You can use fastboot to set which is active. You should read about a/b partitions. They are going to be the defacto standard for seamless updates for everything in the future. This just happens to be one of the first phones to use it.
pkgingo said:
Sounds like your a/b partitions got swapped. You can use fastboot to set which is active. You should read about a/b partitions. They are going to be the defacto standard for seamless updates for everything in the future. This just happens to be one of the first phones to use it.
Click to expand...
Click to collapse
Weird Slot B show the July 2018 patch. A slot May 2018 patch.. I thought when you installed the updates, both slots would have the same update.. Sounds like you have to do each separately.
doubledragon5 said:
Weird Slot B show the July 2018 patch. A slot May 2018 patch.. I thought when you installed the updates, both slots would have the same update.. Sounds like you have to do each separately.
Click to expand...
Click to collapse
Slotting is for fail over in case an update got botched. No other reason for two slots with one data partition. So it'd be illogical to flash the update to both slots unless you're flashing all back to stock, even then it is unnecessary.
doubledragon5 said:
This is turning out by far to be my worst investment in phones...
Click to expand...
Click to collapse
The screen resolution was for me the most important reason for this phone. Full HD looks bad against this Z2 Force quadHD. Now I can't see pixel anymore. Perfect for VR and watching movies, reading something. Much better than Z Play screen. There are not so many devices with quadHD and I want Motorola. Z3 Play has just Full HD and costs 500€. Absolutly to much. Z3 verizon just Full HD, too.
And what happend to you is A/B partition, normal.
allrightlite said:
The screen resolution was for me the most important reason for this phone. Full HD looks bad against this Z2 Force quadHD. Now I can't see pixel anymore. Perfect for VR and watching movies, reading something. Much better than Z Play screen. There are not so many devices with quadHD and I want Motorola. Z3 Play has just Full HD and costs 500€. Absolutly to much. Z3 verizon just Full HD, too.
And what happend to you is A/B partition, normal.
Click to expand...
Click to collapse
I flashed the phone back to 100% stock started it all over again. Then when I started rooting the phone and debloating the phone I was having issues with either Bluetooth not working or Wi-Fi not working. I was on the B slot doing this so I went ahead and went back in the recovery and switch to a slot. Then after I went ahead and rerooted and went back to the home screen once again I was back to the May 2018 security patch on the a slot and I was July 2018 on the B slot. This whole to slot BS drives me freaking crazy.
doubledragon5 said:
I flashed the phone back to 100% stock started it all over again. Then when I started rooting the phone and debloating the phone I was having issues with either Bluetooth not working or Wi-Fi not working. I was on the B slot doing this so I went ahead and went back in the recovery and switch to a slot. Then after I went ahead and rerooted and went back to the home screen once again I was back to the May 2018 security patch on the a slot and I was July 2018 on the B slot. This whole to slot BS drives me freaking crazy.
Click to expand...
Click to collapse
Maybe you have a hardware issue? Bluetooth and Wifi doesn't work? Sry, can't help you. Maybe you should go to a repair center in your next bigger city.
Here the July patched version is on slot a, no root here. Stock is pretty good and the phone is to expensive for me to risk the guarantee. For testing Android P I use an another cheaper phone.
Guys I have a problem.. When installing Magisk disk to slot A I get this error message. "Failed to Mount `/System` (Device or resource busy). When I boot it shows it is installed.. Now if I use Slot B my wifi down't work, but can install Magisk without issue.. Blue tooth is working again on both A B slots.
Uzephi said:
Slotting is for fail over in case an update got botched. No other reason for two slots with one data partition. So it'd be illogical to flash the update to both slots unless you're flashing all back to stock, even then it is unnecessary.
Click to expand...
Click to collapse
Does your flashall in the other thread include stock recovery?
doubledragon5 said:
Guys I have a problem.. When installing Magisk disk to slot A I get this error message. "Failed to Mount `/System` (Device or resource busy). When I boot it shows it is installed.. Now if I use Slot B my wifi down't work, but can install Magisk without issue.. Blue tooth is working again on both A B slots.
Click to expand...
Click to collapse
I've faced a similar issue. Make sure you use the older twrp. Also, after you install twrp make sure you reboot into the newly installed recovery as opposed to being booted into it. When I was flashing kernels I notice that if I flashed the recovery and rooted all in one go my wifi wouldn't work, I couldn't toggle it on. I thought the kernel might have been giving me trouble, but it was the way I was flashing. To avoid problems, flash recovery, reboot to newly install recovery, wipe dalvik and reboot to system. After the reboot, boot into recovery and flash magisk. That should keep your wifi intact.
I seemed to have more trouble with the new twrp when it came to mounting the system, but I never delved into it too much and just stuck with the older one. As for your other question about stock recovery, it's built into the boot.img, so if you need stock recovery or kernel for that matter, just flash the stock boot.img.
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.
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