Related
Got my Pixel XL and updated to NMF26O 7.1.1 by OTA. Then, unlocked bootloader, flashed TWRP RC1 and SuperSU V2.79 SR1. Worked no problem as well as did TWRP backup twice. I noted that Slot B is being used when I rebooted from TWRP.
Tonight, I flashed custom kernel, FK-R6, by using "fastboot flash kernel fk-r6". It said flashing ok and I rebooted. Surprisingly, the Pixel boots back to its former version of NDE63H 7.1, as well as the kernel is remain stock. Of course, the root was gone, but, all app and data are kept.
Booted TWRP and found Slot is A is being used. So, I changed back to Slot B. Rebooted and it still remains NDE63H.
My question is how to keep boot Slot B and in case I can keep boot with Slot B, does the custom kernel keep? I read something about a setting in TWRP to keep the Slot. But, I am not experience to make sure what to do next.
And any possible cause the change the boot to Slot B?
One more dumb question, what if I flash bootloader, recovery, kernel and etc to both Slots to ensure the system and setting keep to the same?
Million Thanks
CK WONG
I'm not familiar with Franco's kernel, I use ElementalX. I've never had a problem with it and I like that it can be flashed from TWRP.
As far as the OTA, everytime you flash an OTA, it will be flashed to the opposite Slot so you may want to try starting in Slot B, sideload the OTA from within TWRP RC1, reinstall TWRP, SU and kernel to see it it works.
lightning413 said:
I'm not familiar with Franco's kernel, I use ElementalX. I've never had a problem with it and I like that it can be flashed from TWRP.
As far as the OTA, everytime you flash an OTA, it will be flashed to the opposite Slot so you may want to try starting in Slot B, sideload the OTA from within TWRP RC1, reinstall TWRP, SU and kernel to see it it works.
Click to expand...
Click to collapse
Thanks for your quick reply.
It seems setting the slot by TWRP cannot make the change stayed. As, I have flashed custom recovery, I would think of a fresh install by fastboot commends. At this time, I can only think of three options:
1. Try the "fastboot --set-active=_b". But, I am not sure the Slot B is okay or not. Perhaps, the bootloader detects something wrong on Slot B, then, it automatically changes to Slot A;
2. Restore the nandroid of NMF26O to slot A by using TWRP. But not sure it will restore to Slot A as wish; or
3. Update the NDE63H to NMF26O by using fastboot commend that equal to a fresh install of which is my last resource.
I hope some of you can enlighten me comments.
CK
P.S. Just tried using TWRP to set to Slot B. Reboot to bootloader and read boot to Slot B. However, the phone restarted three times and goes back to Slot A boot. I wonder whether the flashing of kernel on Slot B was unsuccessful or not.
Anyone know the any command to check the Slot contents by using fastboot?
smallvan said:
Thanks for your quick reply.
It seems setting the slot by TWRP cannot make the change stayed. As, I have flashed custom recovery, I would think of a fresh install by fastboot commends. At this time, I can only think of three options:
1. Try the "fastboot --set-active=_b". But, I am not sure the Slot B is okay or not. Perhaps, the bootloader detects something wrong on Slot B, then, it automatically changes to Slot A;
2. Restore the nandroid of NMF26O to slot A by using TWRP. But not sure it will restore to Slot A as wish; or
3. Update the NDE63H to NMF26O by using fastboot commend that equal to a fresh install of which is my last resource.
I hope some of you can enlighten me comments.
CK
P.S. Just tried using TWRP to set to Slot B. Reboot to bootloader and read boot to Slot B. However, the phone restarted three times and goes back to Slot A boot. I wonder whether the flashing of kernel on Slot B was unsuccessful or not.
Anyone know the any command to check the Slot contents by using fastboot?
Click to expand...
Click to collapse
Tried flashing the stock boot.img and set to Slot B by using:
fastboot flash boot_b boot.img
fastboot set_active_b
But, still booted with Slot A of previous 7.1. It seems something really bad in Slot B.
Anything I can do to reactive the Slot B?
smallvan said:
Tried flashing the stock boot.img and set to Slot B by using:
fastboot flash boot_b boot.img
fastboot set_active_b
But, still booted with Slot A of previous 7.1. It seems something really bad in Slot B.
Anything I can do to reactive the Slot B?
Click to expand...
Click to collapse
Use Google's flashall bat. That should flash both slots.
Sent from my Pixel XL using XDA Labs
smallvan said:
Tried flashing the stock boot.img and set to Slot B by using:
fastboot flash boot_b boot.img
fastboot set_active_b
But, still booted with Slot A of previous 7.1. It seems something really bad in Slot B.
Anything I can do to reactive the Slot B?
Click to expand...
Click to collapse
Use a modified flash all so that you tell it to skip slot A. Should put slot B back to stock
aholeinthewor1d said:
Use a modified flash all so that you tell it to skip slot A. Should put slot B back to stock
Click to expand...
Click to collapse
Thanks you guys kind words. Just reflashed back to stock 7.1.1 with user data erased. Have to re-do root and settings from the beginning.
On Nougat, doing fastboot boot twrp.img would work as expected. Now, on Android O DP3, TWRP goes into a bootloop. It flashes the bootup screen and then going to black in an infinite loop. Anyone know how to solve this issue?
O doesn't work with twrp. I never got it too even if you downgrade for twrp to work you have to flash N on both partitions just to get it to temp boot
Sent from my Pixel XL using Tapatalk
bennyboy2120 said:
O doesn't work with twrp. I never got it too even if you downgrade for twrp to work you have to flash N on both partitions just to get it to temp boot
Click to expand...
Click to collapse
Not true in every case. I used flash all to upgrade to O beta. Then I used flash all to go back to N. I've done this multiple times. I'm able to boot twrp fine after using flash all to get back to N. I don't need to flash it to both slots. I know of a few other people that use the same exact method as me. I think where people are running into issues is when they take the OTA to upgrade to the O beta. Taking an OTA swaps the current boot slot. I haven't tried taking an OTA for the O beta to test this out though.
toknitup420 said:
Not true in every case. I used flash all to upgrade to O beta. Then I used flash all to go back to N. I've done this multiple times. I'm able to boot twrp fine after using flash all to get back to N. I don't need to flash it to both slots. I know of a few other people that use the same exact method as me. I think where people are running into issues is when they take the OTA to upgrade to the O beta. Taking an OTA swaps the current boot slot. I haven't tried taking an OTA for the O beta to test this out though.
Click to expand...
Click to collapse
Weird maybe I just go overkill I never knew what exact step I did that got it to work but all I know is when I do that it works fine lol
TWRP just gets stuck on the boot screen after reflashing Nougat. I don't know how to switch slots in fastboot, because it looks like the required command is removed.
EDIT: It turns out the fastboot and adb from apt aren't up to date, so now I can swap the boot slot once updating it.
khang06 said:
TWRP just gets stuck on the boot screen after reflashing Nougat. I don't know how to switch slots in fastboot, because it looks like the required command is removed.
EDIT: It turns out the fastboot and adb from apt aren't up to date, so now I can swap the boot slot once updating it.
Click to expand...
Click to collapse
I don't really understand the dual slots yet. How does switching slots help you avoid a boot loop when installing TWRP?
No idea, I flashed Nougat on one slot and TWRP bootlooped, but after flashing it to both slots, it worked perfectly.
khang06 said:
No idea, I flashed Nougat on one slot and TWRP bootlooped, but after flashing it to both slots, it worked perfectly.
Click to expand...
Click to collapse
That's good to know if I ever get the courage to flash on this phone. Thanks.
Hello!
I just flashed the newest TWRP for Google Pixel, and everything seems to be going fine except a few things..
When I attempt to change slots within TWRP I get "E:Error getting bootctrl module" but I can switch active slots via bootloader fastboot... but for convenience sake, I'd like to know why I cant do that from recovery..
First thing I did was completely go back to stock on slot a and b, then I fastbooted the twrp image, installed it, then I rebooted into bootloader, changed slots, flashed recovery, went back to slot A, installed rom which is the LineageOS 14.1 from: https://forum.xda-developers.com/pixel-xl/development/rom-lineageos-14-1-nightlies-google-t3601893 because I dont want Oreo yet..too buggy imho, afterwards I flashed Magisk after initial boot...
I also noticed that the rom installed in slot B when I was in Slot A, not sure why?
I'm also having issues with having Elementalx Kernel + Magisk installed at the same time, Youtube wont work at all, and causes a kernel panic after sitting on the Youtube screen (frozen) for awhile.. so right now everything is working with just Magisk and the ROM, but I'd really like to use Elementalx and also be able to change slots from TWRP...
Please let me know what I did wrong!
Thanks.
No one ?
If I were you I would reflash the phone to stock then use fastboot format userdata to erase everything on it and install twrp again using latest zip from twrp website. Running 8.0 + EX kernel and magisk no bugs no crashes smooth stable. Also make sure to use magisk 14.2
george241312 said:
If I were you I would reflash the phone to stock then use fastboot format userdata to erase everything on it and install twrp again using latest zip from twrp website. Running 8.0 + EX kernel and magisk no bugs no crashes smooth stable. Also make sure to use magisk 14.2
Click to expand...
Click to collapse
I've already done all that.
Why are you changing slots ? Is there a necessity you can just flash your rom and magisk on the default slot.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
I would try not changing slots while flashing recovery.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
I think because you flashed recovery on slot b rom got installed on slot b.
KeithGS said:
No one ?
Click to expand...
Click to collapse
Twrp flashes to both boot partitions. You don't need to flash it twice. All custom roms switch slots when flashed. Welcome to Pixels. Something appears broken in new Twrp 3.1.1-0 for switching slots in Twrp. I am experiencing the same thing with the E. Boot control error.
Golf c said:
Twrp flashes to both boot partitions. You don't need to flash it twice. All custom roms switch slots when flashed. Welcome to Pixels. Something appears broken in new Twrp 3.1.1-0 for switching slots in Twrp. I am experiencing the same thing with the E. Boot control error.
Click to expand...
Click to collapse
Ok, so it's not just me, good... thanks man.
KeithGS said:
Ok, so it's not just me, good... thanks man.
Click to expand...
Click to collapse
Yes, now there is 3 of us can't switch slots in Twrp. Just have to do it in fastboot for now.
Golf c said:
Yes, now there is 3 of us can't switch slots in Twrp. Just have to do it in fastboot for now.
Click to expand...
Click to collapse
Anything I can do about the EX problem?
KeithGS said:
Anything I can do about the EX problem?
Click to expand...
Click to collapse
Im running Sharkey R2. But Ex flashes the same.
Did you
1. Flash stock boot image
2. Flash Ex
3. Flash Magisk
Golf c said:
Yes, now there is 3 of us can't switch slots in Twrp. Just have to do it in fastboot for now.
Click to expand...
Click to collapse
Add me to the list. Whenever I try to flash xposed, it tries to boot into the last ROM I installed. Would it be worth going back to RC2?
Akomack said:
Add me to the list. Whenever I try to flash xposed, it tries to boot into the last ROM I installed. Would it be worth going back to RC2?
Click to expand...
Click to collapse
Twrp 3.1.1.1 fixes the slot switching. I don't know about your exposed problem.
Golf c said:
Yes, now there is 3 of us can't switch slots in Twrp. Just have to do it in fastboot for now.
Click to expand...
Click to collapse
Golf c said:
Twrp 3.1.1.1 fixes the slot switching. I don't know about your exposed problem.
Click to expand...
Click to collapse
After I posted I was going to try going back to RC2 and noticed that 3.1.1.1 was up. I didn't know of the update. All is well.
After installed xposed, it gave me a twrp bootloop, switched slots in twrp and it works great.
It's really weird, I never noticed an issue with switching slots until I tried a Ground Zero ROM.
this happens to me for the 2nd time, i clean reflashed factory image of android 10, then installed a kernel, twrp and magisk, after installing some magisk mods device bootloops in restarts directing me to twrp recovery, i deleted them using file manager but still the device bootloops and they are not the reason behind the bootloop as they we working before,
something to add is that device selinux is set to permissive and not enforcing, idk if this is the case or no
Fastboot image first then boot the OS. Get back to the bootloader then fastboot twrp image. Flash the twrp installer zip when booted in the twrp image. Reboot to recovery and then flash kernel and magisk last.
wolfeyes30 said:
Fastboot image first then boot the OS. Get back to the bootloader then fastboot twrp image. Flash the twrp installer zip when booted in the twrp image. Reboot to recovery and then flash kernel and magisk last.
Click to expand...
Click to collapse
not working still bootloops
something causing the device to bootloop even enabling core mode only in twrp doesnt work, im fed up i reclean flashed sotfware dozen times, when there was no twrp installed the device bootloops then returns you to stock reocvery or twrp, once i didnt flashed twrp yet so in factory recovery the error was that system cant read data partiton or something like that
latest canary build bootloops after installing any modules and if i installed twrp
im using the version before the latest i made the same behaviour after installing some modules
bootlogs attached in here
Nightf0x_007 said:
not working still bootloops
something causing the device to bootloop even enabling core mode only in twrp doesnt work, im fed up i reclean flashed sotfware dozen times, when there was no twrp installed the device bootloops then returns you to stock reocvery or twrp, once i didnt flashed twrp yet so in factory recovery the error was that system cant read data partiton or something like that
latest canary build bootloops after installing any modules and if i installed twrp
im using the version before the latest i made the same behaviour after installing some modules
bootlogs attached in here
Click to expand...
Click to collapse
I don't know how to read android logs but my IT experience is telling me the OS is having problems with the hardware for some reason, lots of errors at the end freaking out about sensors and hardware.
I would suggest a clean start with just the OS to see if it bootloops before adding twrp or magisk. Use Deuces script to flash the factory image to both slots and get everything setup. Run that way for a day then move on to adding one or the other and gradually add things to see where the loops start. Also, be careful with modules since they aren't all updated for 10 yet.
wgrant said:
I don't know how to read android logs but my IT experience is telling me the OS is having problems with the hardware for some reason, lots of errors at the end freaking out about sensors and hardware.
I would suggest a clean start with just the OS to see if it bootloops before adding twrp or magisk. Use Deuces script to flash the factory image to both slots and get everything setup. Run that way for a day then move on to adding one or the other and gradually add things to see where the loops start. Also, be careful with modules since they aren't all updated for 10 yet.
Click to expand...
Click to collapse
this happens after installing modules they was working before, before all this happens
how to flash factory image to both slots using deuces
Nightf0x_007 said:
this happens after installing modules they was working before, before all this happens
how to flash factory image to both slots using deuces
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...tloop-recovery-flashing-t3704761/post74507988
Download the script, put it in your adb tools folder with the factory image then run it. It'll launch and proceed through the steps to flash the image. If you boot to bootloader before running the script you can hit enter when it says it can't find any adb devices, that's normal because you'll already be in fastboot which it checks next.
Also, I saw in your other thread that you're using the Canary builds. I'm using magisk 19.3 without issue and twrp 3.3.0 with the system mount error that comes up but it still flashes what ask it to. For twrp I flashes the img file to the recovery partition and it's working just fine, no need to use the zip.
wgrant said:
https://forum.xda-developers.com/pi...tloop-recovery-flashing-t3704761/post74507988
Download the script, put it in your adb tools folder with the factory image then run it. It'll launch and proceed through the steps to flash the image. If you boot to bootloader before running the script you can hit enter when it says it can't find any adb devices, that's normal because you'll already be in fastboot which it checks next.
Click to expand...
Click to collapse
yes i know all this and i used the script, but im asking about flashing to both slots should i do something in here or it is automatically done by the script
Nightf0x_007 said:
yes i know all this and i used the script, but im asking about flashing to both slots should i do something in here or it is automatically done by the script
Click to expand...
Click to collapse
The script flashes to both slots instead of just the active slot like the flash-all file Google offers. They're essentially the same thing but Deuces automates a lot of the commands you would need to know and instead let's you reply yes or no to questions. I find it super handy and saves me time.
wgrant said:
The script flashes to both slots instead of just the active slot like the flash-all file Google offers. They're essentially the same thing but Deuces automates a lot of the commands you would need to know and instead let's you reply yes or no to questions. I find it super handy and saves me time.
Click to expand...
Click to collapse
the script only flashes slot B in here is that normal ?
Nightf0x_007 said:
the script only flashes slot B in here is that normal ?
Click to expand...
Click to collapse
No, it's not. The script should flash your active slot then switch to flash the other. You could manually flash using the flash-all that Google gives and manually switch to the other slot. I believe the command is set active slot - a or set active slot - b then run the script while in each one. You may have to Google that command since I don't use it.
wgrant said:
No, it's not. The script should flash your active slot then switch to flash the other. You could manually flash using the flash-all that Google gives and manually switch to the other slot. I believe the command is set active slot - a or set active slot - b then run the script while in each one. You may have to Google that command since I don't use it.
Click to expand...
Click to collapse
Yes i did this but then got error device is corrupted and wont boot, so i flashed the flash all file in the factory image it flashed slot b and flashed one thing only (system) in slot a, so thats right?
Or should i manually switch between slots and run the flash all ?
Nightf0x_007 said:
Yes i did this but then got error device is corrupted and wont boot, so i flashed the flash all file in the factory image it flashed slot b and flashed one thing only (system) in slot a, so thats right?
Or should i manually switch between slots and run the flash all ?
Click to expand...
Click to collapse
It seems like you're misunderstanding. The flash-all file that Google provides will only flash to one slot. So if you wanted to flash to both you have to switch slots manually then run it again. Deuces script does both slots, it won't do only one of them because of the way it is written. Since you can get into fastboot I would just use what comes from Google and flash it then switch and flash again. This should put you in a clean OS on both slots so no matter where you boot from its good. Once that is taken care of you can move on to other twrp and magisk.
All of this sounds like you have old stuff on one slot and keep ending up on there. The A/B structure of the pixel phones is supposed to allow see less updating of the OS so when an update is installed switches you to the new slot for active booting and then the next update it switches to the other slot so on and so on.
wgrant said:
It seems like you're misunderstanding. The flash-all file that Google provides will only flash to one slot. So if you wanted to flash to both you have to switch slots manually then run it again. Deuces script does both slots, it won't do only one of them because of the way it is written. Since you can get into fastboot I would just use what comes from Google and flash it then switch and flash again. This should put you in a clean OS on both slots so no matter where you boot from its good. Once that is taken care of you can move on to other twrp and magisk.
All of this sounds like you have old stuff on one slot and keep ending up on there. The A/B structure of the pixel phones is supposed to allow see less updating of the OS so when an update is installed switches you to the new slot for active booting and then the next update it switches to the other slot so on and so on.
Click to expand...
Click to collapse
this is what i did, i flashed factory image in slot b then manually switched to slot a as active and reflashed image without -w, when booting os, phone shows corrupted device message and wont boot, reset active to b slot phone boots
i will try something now, will flash .019 in slot a then adb sideload .20 ota afaik it should install in opposite slot (b), and will see what happens
Nightf0x_007 said:
this is what i did, i flashed factory image in slot b then manually switched to slot a as active and reflashed image without -w, when booting os, phone shows corrupted device message and wont boot, reset active to b slot phone boots
i will try something now, will flash .019 in slot a then adb sideload .20 ota afaik it should install in opposite slot (b), and will see what happens
Click to expand...
Click to collapse
You data partition may be corrupt and needs to be wiped.
wgrant said:
You data partition may be corrupt and needs to be wiped.
Click to expand...
Click to collapse
i flashed .19 to slot b with wipe userdata, then boot twrp sideloaded ota .20, then erased all data factory reset, setuping device now will see what happens
Nightf0x_007 said:
i flashed .19 to slot b with wipe userdata, then boot twrp sideloaded ota .20, then erased all data factory reset, setuping device now will see what happens
Click to expand...
Click to collapse
Did you manage to get it to work?
leqacy said:
Did you manage to get it to work?
Click to expand...
Click to collapse
Yes, i flashed .19 image then sideloaded .20 ota, tell now things good returning my data step by step
But after i did this intalling twrp after that when i boot os then reboot phone bootloops so i didnt install twrp after that (reflashed .19 ........)
Since the oneplus 7T has two slot a and b. Is it possible to load another rom onto slot b? Depending on which slot is active could we boot into the rom in that slot? Thanks for your reply.
tknguyencsu said:
Since the oneplus 7T has two slot a and b. Is it possible to load another rom onto slot b? Depending on which slot is active could we boot into the rom in that slot? Thanks for your reply.
Click to expand...
Click to collapse
Possible if decrypted, but it's very likely you run into issues and mess your /data partition up.
I thought the "new" (version 11?) was suppose to take advantage of that a/b partition and when an update comes along,
it installs in the b partition, the a being the old backup in case something happens during the update. Then when another
new update comes along, it installs in the a partition, and the b becomes the backup and so on?
p51d007 said:
I thought the "new" (version 11?) was suppose to take advantage of that a/b partition and when an update comes along,
it installs in the b partition, the a being the old backup in case something happens during the update. Then when another
new update comes along, it installs in the a partition, and the b becomes the backup and so on?
Click to expand...
Click to collapse
This has been the case for Android for a few years now. The system is installed on either A or B.
p51d007 said:
I thought the "new" (version 11?) was suppose to take advantage of that a/b partition and when an update comes along,
it installs in the b partition, the a being the old backup in case something happens during the update. Then when another
new update comes along, it installs in the a partition, and the b becomes the backup and so on?
Click to expand...
Click to collapse
I think you are right. When I mess up the 7T in version 10.0.9 and it get stuck in fastboot mode. I tried to boot into twrp.img hopefully to flash the stock rom again, instead the phone some how reboot itself into the previous version 10.0.8 and I need to update it to version 10.0.9.
tknguyencsu said:
I think you are right. When I mess up the 7T in version 10.0.9 and it get stuck in fastboot mode. I tried to boot into twrp.img hopefully to flash the stock rom again, instead the phone some how reboot itself into the previous version 10.0.8 and I need to update it to version 10.0.9.
Click to expand...
Click to collapse
Why would you even use TWRP? It's not working and has nothing do to with what he mentioned.
Sent from my OnePlus7TPro using XDA Labs
---------- Post added at 03:26 PM ---------- Previous post was at 03:12 PM ----------
The system still resides on the super partition, and its read only which means you cannot flash it. One of, if not the main reason why TWRP is not here.
It would be very risky and hard to do it without a working TWRP.
Sent from my OnePlus7TPro using XDA Labs
To answer the OP's question: if you were to be able to stay decrypted, you could flash two ROMs via fastboot. Once the first is flashed, you could switch to the B partition via "fastboot --set-active=", reboot to the bootloader and then flash the second fastboot ROM.
However, it is not recommended, might not work and I'm not sure whether an available custom ROM is decrypted by default. Also not sure if you can decrypt properly as there is no no-verity.zip flashable right now.
Macusercom said:
To answer the OP's question: if you were to be able to stay decrypted, you could flash two ROMs via fastboot. Once the first is flashed, you could switch to the B partition via "fastboot --set-active=", reboot to the bootloader and then flash the second fastboot ROM.
However, it is not recommended, might not work and I'm not sure whether an available custom ROM is decrypted by default. Also not sure if you can decrypt properly as there is no no-verity.zip flashable right now.
Click to expand...
Click to collapse
I don't think that's possible. The super (read only) handles the slots internally and it's the OTA that takes care of 'filling' the other slot up dynamically, meaning you can only flash the slot a system, not slot b.
In order to dual boot, you would need some risky repartitioning and could mess your device up.
(Not an expert of course, so I might be wrong)
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
I don't think that's possible. The super (read only) handles the slots internally and it's the OTA that takes care of 'filling' the other slot up dynamically, meaning you can only flash the slot a system, not slot b.
In order to dual boot, you would need some risky repartitioning and could mess your device up.
(Not an expert of course, so I might be wrong)
Click to expand...
Click to collapse
If you use fastboot to flash the ROM you can flash it to a particular slot. You can then flash different .img files to A or B. But if they would boot is another question, yes. So in general I do not consider it working.
Lossyx said:
Why would you even use TWRP? It's not working and has nothing do to with what he mentioned.
Sent from my OnePlus7TPro using XDA Labs
---------- Post added at 03:26 PM ---------- Previous post was at 03:12 PM ----------
The system still resides on the super partition, and its read only which means you cannot flash it. One of, if not the main reason why TWRP is not here.
It would be very risky and hard to do it without a working TWRP.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
I boot into TWRP to change slot, even though you can do it through fastboot. The point I would like to make is that when I mess up my stock rom version 10.0.9 in slot A and when I boot into TWRP it somehow get me boot into slot B with the stock rom is still in version 10.0.8. I later tried to load two different roms into two slots A and B using fastboot command to flash all the necessary images. You need to make sure you are in fastbootd (I used the recovery image from the MSM extended rom that clearly tell whether you are in fastboot or fastbootd). It turned out that I can boot into different rom in each slot. However each time I need to format the data partition again for it to boot. It was not worth the trouble unless you want to try two different roms. Now I have the stock rom in slot B and the AOSiP rom in slot A. I am now in slot B with stock rom 10.0.9.
tknguyencsu said:
I boot into TWRP to change slot, even though you can do it through fastboot. The point I would like to make is that when I mess up my stock rom version 10.0.9 in slot A and when I boot into TWRP it somehow get me boot into slot B with the stock rom is still in version 10.0.8. I later tried to load two different roms into two slots A and B using fastboot command to flash all the necessary images. You need to make sure you are in fastbootd (I used the recovery image from the MSM extended rom that clearly tell whether you are in fastboot or fastbootd). It turned out that I can boot into different rom in each slot. However each time I need to format the data partition again for it to boot. It was not worth the trouble unless you want to try two different roms. Now I have the stock rom in slot B and the AOSiP rom in slot A. I am now in slot B with stock rom 10.0.9.
Click to expand...
Click to collapse
Oh, so you're having two different ROMs installed?
Then Macusercom is right, if we're able to decrypt then we should be able to boot into the other ROM without formating?
Sorry if I'm confused btw, I'm still also new to this whole thing.
Sent from my OnePlus7TPro using XDA Labs
Lossyx said:
Oh, so you're having two different ROMs installed?
Then Macusercom is right, if we're able to decrypt then we should be able to boot into the other ROM without formating?
Sorry if I'm confused btw, I'm still also new to this whole thing.
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Even if we 're able to decrypt I still think we need to format the data since the two different roms will not have the same apks in them. The two slots A and B share the same data partition (even though they have their own recovery) so we cannot have two independent roms.
interesting topic!
I was on Global 10.0.7 on my HD1900... was able to boot into my HydrogenOS on the other partition...
After updated to 10.0.9, I can't boot into the other paertition anymore... I got boot loop. ?
Silly me... suppose go update the HydrogenOS first... now 10.0.9 refused to let me update to the other partition of HydrogenOS 10.0.8.
Fun to have 2 systems... maybe moving forward it's impossible.