Hello,
(how) can I get my Google Pixel to such a state where I choose in TWRP Slot A and I get a rooted system and if I choose Slot B in TWRP I get a stock unrooted version?
Reason behind is that I have some few apps that don't like the root like Banking Apps. This way I could do backups / restores with Titanium Backup but still use the TAN App after a simple reboot.
I installed today sailfish-nmf26u-factory, twrp-3.0.2-0-RC1 and SuperSU-v2.79-SR2. If I boot Slot A (was active during TWRP and SuperSU Install) then I can boot and have a rooted system. If I choose Slot B I get a bootloop. Luckily I can switch back to Slot A for the moment.
Cheers
Cheers. I did this days ago too, everything seems fine but for both system, I lost the ability to access developer option
bush911 said:
Cheers. I did this days ago too, everything seems fine but for both system, I lost the ability to access developer option
Click to expand...
Click to collapse
Have you tried tapping the build number repeatedly again until it shows up?
Yes I did. Something wrong with userdata, wipe userdata and fixed it
dtrud0h said:
Have you tried tapping the build number repeatedly again until it shows up?
Click to expand...
Click to collapse
There's already a few threads on here talking about it.
aholeinthewor1d said:
There's already a few threads on here talking about it.
Click to expand...
Click to collapse
Hey, don't want to complain but I could not find such a thread one week ago so I created this one. Can you give me a link?
Thank you!
KobiP
KobiP said:
Hey, don't want to complain but I could not find such a thread one week ago so I created this one. Can you give me a link?
Thank you!
KobiP
Click to expand...
Click to collapse
Totally understandable that these public forum threads can get jumbled up quickly. It's noone's fault; it's just the natural course of an ask-and-answer dialog. You'll find the discussions of your question loosely in just about every thread here -- mostly in the kernels threads, the TWRP thread, or the SU one, and many debates in every ROM discussion as well. I believe I demonstrated what you're trying to achieve in one of the first pages of the WETA ROM thread. There's also one fairly new specific thread on this on the Pixel XL side, but that one isn't very well-participated because I think most folks are tired of talks about the Pixel's dual slot system. However, I would look at the kernel threads, especially the Sakete one because Android Pay availability was the whole intention of his compiling that kernel. Or you can also compile your own kernel.
In practice, what you want to do is:
Make sure both slots are bootable.
In TWRP, know which slot you're on, install a kernel that is SafetyNet-patched in that slot, SU the other slot you wish to root. That's all.
You wrote slot B is boot looping. That indicates that you installed something that overwrote its boot image. Keep in mind that SU, TWRP, and kernel reside in Nougat's boot. To get slot B bootable again, I'd suggest you flash the stock boot.img back to that slot. Or you can use the flash-all.bat that's modified to skip restoring slot A.
Or, you can simply use the unmodified flash-all.bat to put everything back. Remove the -w switch if you don't want to lose data. Then install TWRP, boot the phone from both slots once. Install a new kernel to the slot you want to use AP. Root the other slot.
BTW, most banking apps work on rooted phones. They haven't jumped on the SafetyNet train yet. My PennyMac, PNC, Chase, Amex apps work.
quangtran1 said:
You wrote slot B is boot looping. That indicates that you installed something that overwrote its boot image. Keep in mind that SU, TWRP, and kernel reside in Nougat's boot. To get slot B bootable again, I'd suggest you flash the stock boot.img back to that slot. Or you can use the flash-all.bat that's modified to skip restoring slot A.
Or, you can simply use the unmodified flash-all.bat to put everything back. Remove the -w switch if you don't want to lose data. Then install TWRP, boot the phone from both slots once. Install a new kernel to the slot you want to use AP. Root the other slot.
Click to expand...
Click to collapse
Hey,
tnx for your advice. I think the Issue is somewhere else.
Try One, Slot A Active:
I executed flash-all.bat without the "-w" and then said fastboot set_active b and fastboot reboot bootloader. I can read "Boot-slot b". If I try to boot now I get a bootloop and after a few cycles I can boot. adb reboot bootloader and voila, back to "Boot-slot a". Now Slot B is broken
Try Two, Slot B Active:
Same, I executed flash-all.bat without the "-w" and then said fastboot set_active a. Reboot, see that slot A is active and then I get stuck in a bootloop. After a while I am booting to Android but this time in Slot B. Now Slot A is broken.
quangtran1 said:
BTW, most banking apps work on rooted phones. They haven't jumped on the SafetyNet train yet. My PennyMac, PNC, Chase, Amex apps work.
Click to expand...
Click to collapse
True, but my Push TAN App doesn't work, it simply crashes when starting the App and the Browser opens with a help page that says that I can't use this App on rooted phones... I tried to open the app now after the flash-all.bat and it opens just fine.
Cheers
Hello,
I tried again with sailfish-nof27b Version. This time I did not change the flash-all.bat so that it will reset my phone.
Then I flashed the latest SW to my phone (Slot A active). I can boot into Android and my phone is reset. Now I boot to the bootloader, switch to Slot B and get a bootloop. After a while it automatically switches back to Slot A and boots.
If I do run again flash-all.bat with Slot B active I can boot Slot B but not Slot A (bootlooping).
How can I get both Slots back to work on my phone?
Cheers
KobiP said:
Hello,
I tried again with sailfish-nof27b Version. This time I did not change the flash-all.bat so that it will reset my phone.
Then I flashed the latest SW to my phone (Slot A active). I can boot into Android and my phone is reset. Now I boot to the bootloader, switch to Slot B and get a bootloop. After a while it automatically switches back to Slot A and boots.
If I do run again flash-all.bat with Slot B active I can boot Slot B but not Slot A (bootlooping).
How can I get both Slots back to work on my phone?
Cheers
Click to expand...
Click to collapse
You can flash all the factory firmware u want if u don't use the modified command, like the guy said in the above post your not going to boot into that other slot.
Read this thread
https://forum.xda-developers.com/pixel/help/dual-booting-t3507924/post69834495#post69834495
mac796 said:
You can flash all the factory firmware u want if u don't use the modified command, like the guy said in the above post your not going to boot into that other slot.
Read this thread
https://forum.xda-developers.com/pixel/help/dual-booting-t3507924/post69834495#post69834495
Click to expand...
Click to collapse
Hey,
your linked post works amazing! Thank you very very much! Only thing to add is to flash a certain Slot (A/B) it must be active first. But now I can boot both Slots!
Related
I have flashed stock from googles web site and I have tried everything I can to get a custom rom back on this device. I have tried everything. every thing I do just boots to regular google. But I can flash twrp, and magisk on stock and it works. OEM is unlocked but as soon as I flash a rom then twrp and sign it, it says its successful for everything but when I boot to system it just reboots a couple times then boots but up to stock. Any one have any ideas?
KingAroan said:
I have flashed stock from googles web site and I have tried everything I can to get a custom rom back on this device. I have tried everything. every thing I do just boots to regular google. But I can flash twrp, and magisk on stock and it works. OEM is unlocked but as soon as I flash a rom then twrp and sign it, it says its successful for everything but when I boot to system it just reboots a couple times then boots but up to stock. Any one have any ideas?
Click to expand...
Click to collapse
This is normal. Your custom ROM is flashing to the opposite slot your on. When your done u need to reboot to bootloader and boot twrp then install TWRP again and install verified boot signer zip. If not just going to loop once and boot to the slot that works
mac796 said:
This is normal. Your custom ROM is flashing to the opposite slot your on. When your done u need to reboot to bootloader and boot twrp then install TWRP again and install verified boot signer zip. If not just going to loop once and boot to the slot that works
Click to expand...
Click to collapse
I will try that's next time. I just went through hell trying get back on the RR ROM and rooted with magisk. But I finally got it haha. Took about 20 stock flash's to get it finally working
KingAroan said:
I will try that's next time. I just went through hell trying get back on the RR ROM and rooted with magisk. But I finally got it haha. Took about 20 stock flash's to get it finally working
Click to expand...
Click to collapse
Yea once you do it a couple of times you will have it down. Just remember from May bootloader's on, you have to use that VBS zip. Also keep track of what slot your on when your flashing
mac796 said:
Yea once you do it a couple of times you will have it down. Just remember from May bootloader's on, you have to use that VBS zip. Also keep track of what slot your on when your flashing
Click to expand...
Click to collapse
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
KingAroan said:
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
Click to expand...
Click to collapse
No there the same. You can put whatever on either one. There for normal use. seamless updates they call it I believe.
KingAroan said:
I still don't get the slot thing. I was figuring that slot a was stock and slot b was any custom rom guess that wrong
Click to expand...
Click to collapse
The different slots are for seamless updates. If you're using the stock rom and taking OTA's, the OTA gets flashed to whatever slot is currently inactive. It used to be when you did an OTA, the OTA got downloaded and then you'd be prompted to reboot to install the update. When you rebooted, the update would get installed but you had to sit and wait for it to install before you could use your phone again. With the two slots, it now downloads the update and installs it to the inactive slot while you continue to use your phone. Eventually you get prompted to reboot but instead of having to wait for it to install, it just reboots like any other time you reboot the phone and there is no wait for the update to install. It's already installed. When it reboots, it switches to the slot that was previously inactive because that's where the update is installed to. So, if you're on slot A when the update is downloaded and installed, you'll be using slot B after you reboot. The next month when the update comes out, it will get installed to the other slot again and you'll once again be using slot A and so on and so on for every month after that.
For a custom rom, they can be installed on either slot. It just depends on which slot is currently active. If slot A is the slot that's currently active, TWRP will flash the rom to slot B. If B is active, the rom will get flashed to A. Anything else gets flashed to the slot that is currently active (SuperSU, Vendor files or what have you). That's why after flash the rom, you have to reboot the phone (either reboot to recovery or the OS) before flashing the rest of whatever it is you want to flash. If you don't reboot before flashing SuperSU or whatever, it won't get flashed to the same slot the rom got flashed to and obviously, this causes issues. Bottom line is, slot A or B, it has nothing to do with whether it's a stock or custom rom. Whichever slot is inactive when you flash a rom is the slot the rom will end up on.
robocuff said:
The different slots are for seamless updates. If you're using the stock rom and taking OTA's, the OTA gets flashed to whatever slot is currently inactive. It used to be when you did an OTA, the OTA got downloaded and then you'd be prompted to reboot to install the update. When you rebooted, the update would get installed but you had to sit and wait for it to install before you could use your phone again. With the two slots, it now downloads the update and installs it to the inactive slot while you continue to use your phone. Eventually you get prompted to reboot but instead of having to wait for it to install, it just reboots like any other time you reboot the phone and there is no wait for the update to install. It's already installed. When it reboots, it switches to the slot that was previously inactive because that's where the update is installed to. So, if you're on slot A when the update is downloaded and installed, you'll be using slot B after you reboot. The next month when the update comes out, it will get installed to the other slot again and you'll once again be using slot A and so on and so on for every month after that.
For a custom rom, they can be installed on either slot. It just depends on which slot is currently active. If slot A is the slot that's currently active, TWRP will flash the rom to slot B. If B is active, the rom will get flashed to A. Anything else gets flashed to the slot that is currently active (SuperSU, Vendor files or what have you). That's why after flash the rom, you have to reboot the phone (either reboot to recovery or the OS) before flashing the rest of whatever it is you want to flash. If you don't reboot before flashing SuperSU or whatever, it won't get flashed to the same slot the rom got flashed to and obviously, this causes issues. Bottom line is, slot A or B, it has nothing to do with whether it's a stock or custom rom. Whichever slot is inactive when you flash a rom is the slot the rom will end up on.
Click to expand...
Click to collapse
Holy ****, i didnt know that part, i just thought it flashed it to your current slot and when you rebooted into system, the slot didnt change.....brb but first a quick titanium backup
Guys need your expertise here..
During the process of unlock bootloader, root and finally Magisk..at certain point my phone enter a TWRP loop....
Almost without hope..om TWRP i saw a option to boot, if not im mistake, to opt from Partiton B, and then the phone boot normally..
Question:
Can i reverse this? Or is it normal? The phone works perfectly ok....but shouldn`t be on A?
Wait your expertize...
Mordorr
If it works, leave it.
Mord0rr said:
Guys need your expertise here..
During the process of unlock bootloader, root and finally Magisk..at certain point my phone enter a TWRP loop....
Almost without hope..om TWRP i saw a option to boot, if not im mistake, to opt from Partiton B, and then the phone boot normally..
Question:
Can i reverse this? Or is it normal? The phone works perfectly ok....but shouldn`t be on A?
Wait your expertize...
Mordorr
Click to expand...
Click to collapse
The purpose of A/B partition is seamless updates. You are on one partition while the seamless update does it update on the other partition. The normal Android user does not know what partition they are on, nor does it matter what partition the phone is on. Don't worry about it. It means nothing to the end user.
Thank you guys!
I feel more released now!
happy flashing!
Mord0rr said:
Guys need your expertise here..
During the process of unlock bootloader, root and finally Magisk..at certain point my phone enter a TWRP loop....
Almost without hope..om TWRP i saw a option to boot, if not im mistake, to opt from Partiton B, and then the phone boot normally..
Question:
Can i reverse this? Or is it normal? The phone works perfectly ok....but shouldn`t be on A?
Click to expand...
Click to collapse
The phone will switch the active slot every time you update or flash a full OOS zip. It sounds like at some point in rooting, you switched to the inactive slot. You're lucky it just bootlooped. Manually switching can put it into a state that only the unbrick tool will get it out of (as well as relocking and wiping your phone).
In general, you should not try to switch manually. Just let the system take care of that.
All you need to know about A/B can be found in this guide I wrote: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
Mord0rr said:
Guys need your expertise here..
During the process of unlock bootloader, root and finally Magisk..at certain point my phone enter a TWRP loop....
Almost without hope..om TWRP i saw a option to boot, if not im mistake, to opt from Partiton B, and then the phone boot normally..
Question:
Can i reverse this? Or is it normal? The phone works perfectly ok....but shouldn`t be on A?
Wait your expertize...
Mordorr
Click to expand...
Click to collapse
Whenever I flash a rom in twrp I always
Flash rom
Install twrp again
Reboot recovery
Install magisk
Reboot
That seems to take care of most of the a / B problems
Miss the old days without A/B crap......
Just nuke and install. Period.
Well, if you must know which slot, the DevCheck free app can tell:
https://drive.google.com/file/d/1DPUxg8khZLhsCVEIjg1zth5kChVTgl8N/view?usp=sharing
After successfully installing Magisk, I got 9.5.4 update. As my bootloader is unlocked, system forced full image update
Now, update install successfully through OTA updater but on reboot I get stuck in stock recovery. From there, I had to manually boot to fastboot and switch to slot b to boot OS, back. After spending an hour, couldn't get any leads. Any advice is appreciated..
arvindgr said:
After successfully installing Magisk, I got 9.5.4 update. As my bootloader is unlocked, system forced full image update
Now, update install successfully through OTA updater but on reboot I get stuck in stock recovery. From there, I had to manually boot to fastboot and switch to slot b to boot OS, back. After spending an hour, couldn't get any leads. Any advice is appreciated..
Click to expand...
Click to collapse
I think you've to flash magisk again after an update. I'm not sure though. Not taking responsibility for anything that'll happen if you do so.
icyfire said:
I think you've to flash magisk again after an update. I'm not sure though. Not taking responsibility for anything that'll happen if you do so.
Click to expand...
Click to collapse
Ofcourse I own the responsibility,
Yes tried flashing it seperately for slot a. Then seperately for slot b. Since nothing worked out, flashed twrp on slot a and still nothing.
Then, tried going to slot b 9.5.2 ROM, did local sys update then without reboot, inside Magisk flashed Recovery zip. Even then slot a ROM, doesn't boot
arvindgr said:
Ofcourse I own the responsibility,
Yes tried flashing it seperately for slot a. Then seperately for slot b. Since nothing worked out, flashed twrp on slot a and still nothing.
Then, tried going to slot b 9.5.2 ROM, did local sys update then without reboot, inside Magisk flashed Recovery zip. Even then slot a ROM, doesn't boot
Click to expand...
Click to collapse
Maybe try unrooting by flashing the stock boot.img. You can get the boot.img for 9.5.4 here.
I ran into a problem with my phone the other day. I ended up having the use the MsmDownloadToolV4.0InternationalVersionOxygenOS5.1.5 to restore to stock. After updating to 9.0.9, I kept having trouble installing TWRP. After messing with it for days, I discovered that though I have 9.0.9 installed on my phone, if I switch slots, I have 10 installed on that slot. I'm thinking that when I'm installing TWRP, it's having a problem because I have two different version installed on the phone. Is that possible? Some of the guides I've seen indicate that when you boot to TWRP, then flash it through recovery, it somehow flashes both slots. If that's the case, it would only be the right version of TWRP for one slot, not the other. I'm so confused.
I'm trying to get both slots to be 10 so I can try OmniROM or LineageOS. But at this point, I'd be happy if I could get twrp installed and my phone rooted. I've literally been trying to get TWRP installed for three days straight. It fails every time.
Try to flash OOS 10 with this tool https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
You can save your data by removing the "-w" from the bat file when flashing it but try the tool and it should install empty both slots and install OOS 10.
Xenomorphs said:
Try to flash OOS 10 with this tool https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
You can save your data by removing the "-w" from the bat file when flashing it but try the tool and it should install empty both slots and install OOS 10.
Click to expand...
Click to collapse
Thank you. I'll try that. I've already lost my data. Luckily, I made a backup not long before this.
Well, that worked, but.....
When I switched over to the other slot, that would no longer boot. Both slots did boot correctly right before I ran flash-all.bat. After doing that, the second one just sat on the spinning boot logo. I don't understand why what I do on slot B should impact what's going on with slot A.
Yippee38 said:
Well, that worked, but.....
When I switched over to the other slot, that would no longer boot. Both slots did boot correctly right before I ran flash-all.bat. After doing that, the second one just sat on the spinning boot logo. I don't understand why what I do on slot B should impact what's going on with slot A.
Click to expand...
Click to collapse
Did you try the flasher with "-w" or without? Also, see if you can uninstall magisk from your phone. And try to go into stock recovery mode and resetting the system data and stuff. (not your data)
So I've got a US unlocked device running firmware version KB2005_15_200918. I've rooted it with magisk.
Few days ago I got an update notification, to update to 11.0.1.2.KB05AA. So, thinking I could do it like a pixel, I unrooted, installed the update and re rooted installing to the inactive slot (per @topjohnwu's instructions). On reboot I got stuck on the qualcomm kernel crash screen, leaving my slot_A install hosed.
After some tinkering, I was able to get up and running on slot B. However, slot A is hosed up with the update. (system update says failed, reboot to try again, when i do, hoses back up. Probably because it's setting the active slot to A again).
I've tried re-flashing the KB05AA stock boot image someone dd' and shared on here with no luck. And I don't want to use the unbrick tool, and ending up having to backup/restore all my data.
What are my options at this point to fix slot A, and take the update again? I'm coming from a pixel 3, and know nothing about flashing the factory images on this device or the best way to recover from this. Any advice would be appreciated.
-Michael_ said:
So I've got a US unlocked device running firmware version KB2005_15_200918. I've rooted it with magisk.
Few days ago I got an update notification, to update to 11.0.1.2.KB05AA. So, thinking I could do it like a pixel, I unrooted, installed the update and re rooted installing to the inactive slot (per @topjohnwu's instructions). On reboot I got stuck on the qualcomm kernel crash screen, leaving my slot_A install hosed.
After some tinkering, I was able to get up and running on slot B. However, slot A is hosed up with the update. (system update says failed, reboot to try again, when i do, hoses back up. Probably because it's setting the active slot to A again).
I've tried re-flashing the KB05AA stock boot image someone dd' and shared on here with no luck. And I don't want to use the unbrick tool, and ending up having to backup/restore all my data.
What are my options at this point to fix slot A, and take the update again? I'm coming from a pixel 3, and know nothing about flashing the factory images on this device or the best way to recover from this. Any advice would be appreciated.
Click to expand...
Click to collapse
Use msm tool or reflash stock via fastboot. Either way you gotta wipe one way or another.
Or maybe..
Try fastboot erase boot_a
Then fastboot flash boot_a boot.img. With the kernel you had on slot_a. Hopefully you backed it up prior to this. If not, see my first recommendation.
Thanks, I'll give my kernel backup a shot.