Database Info

Can't switch boot partition without a bootloop

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!

Problem Flashing Factory Images

Wondering if many others of you have run across this, what causes it, and how to avoid it. Basically, I download the factory image from google's image page, flash-all using adb/fastboot. All looks good, every part of installation says OKAY, no fails. Then upon reboot it goes back to bootloader, but now with a yellow banner at the bottom - ERROR: LoadImageAndAuth Failed: Load Error. Sometimes the banner reads ERROR: Slot Unbootable: Load Error. (see attached pictures)
There's no way out of it, flashing images, bootloader or boot.img or whatever separately, flashing twrp, switching between a/b partitions, nothing changes it. Adb/fastboot is current. It's happened after regular flash-all, it's happened when "-w" is removed. It's happened with and without twrp installed. This last time I tried to avoid it by updating without flashing the image, removed twrp and tried to sideload the OTA in stock recovery, which also landed me in the same spot, in the bootloader with that yellow banner of death. Been hit by this using Dec., Feb., and March updates. I stayed on the Dec. update for a while because I've been afraid of it happening again... sure enough it did.
I've replaced a few pixel 2's because of this, every time Google willingly stands by their product and replaces it. One google worker told me this is a known issue they were working on, others said it isn't, and none have provided an explanation for why it happens or how to avoid it. I assume it's some kind of instability with the a/b partition system. I did the same process with my N5x a couple days ago (flashed image then added twrp, magisk, all that stuff) and as usual everything went swimmingly. Tried just flashing current image on p2 the next day and another one bit the dust. Another replacement is on its way now.
So I turn to you. Any of you run into this? What causes it? How can I flash updates without this happening again?

As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.

deepdvd said:
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
Click to expand...
Click to collapse
Tried boot.img but not working for me, still stuck in bootloader. But good to know, I didn't realize that was a possibility. Sucks having to be tethered like that though. I backed up double before messing with it, both nandroid and titanium, expecting I might run into this again.
The replacement process is relatively painless, only takes like 3 days to get a new one. Just be sure to do it while covered under warranty.

Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.

clcdev said:
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
Click to expand...
Click to collapse
Thanks man, seems like it since not many people are experiencing this. Can't think of what external issue it could be other than something with my computer, but im sure not having any troubles doing the same stuff and more on my nexus.

@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.

craigacgomez said:
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
Click to expand...
Click to collapse
Well I tried flashing the ota in recovery and that's what triggered it this last time. But I didn't try doing each partition, maybe that's where it went wrong

Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.

COMpulse said:
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
Click to expand...
Click to collapse
That's what gets me, can't simply fastboot the image to recover, that fail-safe isn't reliable for me.
Got the replacement and set it up so I can update normally. Just booted twrp but didn't install, so I could flash magisk. With no twrp and easily uninstall magisk I can just update via regular OTA when it shows up. Then temporarily boot twrp again to reinstall magisk. Just did that for the March update and worked fine.
A little inconvenient of a workaround but I'm updating without concern about this image flashing problem.

I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.

kkjb said:
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
Click to expand...
Click to collapse
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.

kkjb said:
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
Click to expand...
Click to collapse
Wow great to hear it worked! I tried the deuce script but couldn't get it to work either. I heard there was an issue with the bootloader in December and was supposed to have been fixed in January. But that bootloader error was one that I was also getting after the yellow banner started showing up, even on this last go around. Just before the initial bricking fastboot was reporting all successful on the flash.

More of my troubles
I have twrp 3.2.1-2, Magisk v16.1(1610) Jan 18 8.1.0. The device is working as before. So to recap...first post is what I HAD. My bootloader is stuck on 002.0059.00 this is the one from opd1.170816.025 which is 8.0.0 Nov 17. This some how flashed through Deuce's script and stuck. Now of course nothing will flash with Factory images because I have a botched up Boot.img. From looking back the trouble started with going to update to P. Removed Magisk through manager. It "patched" boot but some how on mine (with flashed twrp) recovery caused a flag I guess to set.
So some point I'm going to get Magisk to patch current Factory Boot.img 002.0067.00 which is in Feb, Mar 18 and P.
Need time to read though Magisk or wait for others to experience. I believe this is the warning message of TWRP and Pixel 2 A/B slots.

update to my troubles
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....

kkjb said:
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
Click to expand...
Click to collapse
That's pretty slick that you got it working again, especially with the bootloader error. I didn't think you could get the current OS working with an old bootloader at all. Hopefully at some point you will be able to update it all the way.

I soft bricked it..so don't do this.
See previous to catch up. Since I pulled the plug and had a Google Warranty phone in hand...21 hours later!
I decided to do all the things NOT TO DO.
Pulled factory Image file from last bootloader with 0059 bootloader.. Nov 17
Flashed tdbo.img, boot.img.
Didn't change same Flash failure device return message. Had to boot TWRP, flash twrp to get working again. Since phone needs to return for credit.
Nothing to lose, I have been on slot = A always. Moved to slot = B....
Now it is a brick.
First couple of power cycles, one line flash, vibrate. Then after 3-4 more cycles no more vibration. longer time to one line flash.
Warm to touch, overnight charge. Same.
So message is to keep backup of files used in first portion of Magisk and twrp installs. Must follow instructions if want to remove Magisk root.
Somehow my problem is a weird one off with the bootloader oddity.

LoadImageAndAuth Error after flashing clean AOSP build on Pixel 2

Bootloader: mw998-002.0072.00
Product Revision walleye MP1
I have been trying, unsuccessfully, to flash a clean build (no changes) of AOSP 9.0.0_r10 (walleye) for the Pixel 2. I'm not building any differently for the Pixel 2 than when I was building for the Pixel so I doubt this is a build problem.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash vendor vendor.img
After finishing the flashing I reboot and the phone goes back to the bootloader and displays an error in yellow at the bottom:
ERROR: LoadImageAndAuth Failed: Load Error
Happens every time. I have no trouble going back to the Factory image but when I try to flash this AOSP one I get the error.
I've done some reading both on XDA and elsewhere and I know other people have run into this error message, though for different scenarios (custom ROM flashing, Android 8 flashing, OTA side loading, etc) but I haven't seen anyone report a problem flashing straight unmodified AOSP builds.
I tried switching boot partitions. Didn't help. I tried both Lunch options for Walleye builds. Didn't help. I haven't been able to side load any build/zip file...not without getting this error.
One thing I did discover this morning. I was cleaning up the Pixel 2 and putting Factory back on it since I had run out of ideas on getting around this issue. I was on Partition A at the time. I flashed the Factory on to A and set it up the device. I then remembered I had the busted AOSP on B so I switched to B and flashed Factory on that partition. I rebooted and set up the device. Then just for giggles I switched back over to A again (which I had already set up for Factory) and rebooted. BANG! I got that error. I had successfully put Factory on A but after switching to B and putting Factory on there and then switching back to A and rebooting, A was now failing. I have no idea of the significance, if any, of this but I thought I would mention it.
Using TWRP or Magisk is not a path I want to go down if at all possible. By rights, flashing AOSP should work on an unlocked non carrier Pixel 2. I've heard that flashing on the Pixel 2 is more convoluted than on the Pixel and I believe it. Hopefully Pixel 3 won't be even worse.
As always if anyone has any ideas or guidance, I'm all ears. Thanks in advance.

I'm so confused. Two version of OOS installed

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)

Fastboot loop/No TWRP on default slot but can change slot and access TWRP.

New to the A/B slot root scene, apologies. I also searched but couldn't find an answer for something matching this exact specificity . I know its fixable but I cant figure out what would be best to do.
I am (or was) running TWRP/Magisk on 10.3.4 Stock OOS. broke the OS boot and it will only goes right into fastboot, no TWRP anymore, doesn't even show the warning from OP when booting a rooted OP device.
Weighing my restore options, I changed the active slot with the fastboot command and that slot was able to boot into TWRP just fine, however, the mounting folder that's usually emulated/o (SDcard) was just a bunch of folders with random text and capitalization.
I have a TWRP backup (around 8GB) . Can i just change the active slot back to the non active one and restore to the other? I am concerned i will break it worse or restore it to the wrong slot somehow. If i restored it to both slots, would that be ok?
edit: I connected my TWRP backup and wasn't able to force the restore to another slot. The backup includes Boot, System, Data (excluding storage) and EFS. I could "swipe to restore" at any moment but unsure how that would effect everything seeing as the backup was done on Slot A and now I am on slot B.
I read you should flash the 10.3.4 full while staying on the same slot but was having issues getting it to upload to the phone (no drive mounts on my computer OS on the default slot, only can do so when i change slots) I have a very recent titanium backup i can restore once i am back in, either way.
I am just not 100% exactly how to get myself back up and running.
Lastly, i only started rooted again after a 10-15 year break because I got real sick of the background data the official OOS build was sending. I was interested in converting to LineageOS with gapps form Micro (if it can pass safetynet) but Open to any ROM that could assist in stopping the official background activity. I would love a ROM that can pass safetynet, help with the battery life on my aging OP6 and hopefully keep rocking on Android 10.
Thank you to everyone or anyone that reads this and assists. I know it must be annoying to read what may just be the same question over and over but this exact issue was hard to find another experiencing with the latest OOS.
Take care.

I ended up trying to restore the TWRP backup to the different slot, this put both slots in a fastbootloop. i then flashed all partitions with a fastboot image of 10.3.4 and this fix my phone and got it back up in running. i rooted again, flashed twrp and then tried to restore the TWRP backup again and it completed successfully, however, both slots were back to bootlooping.
i will just wipe all again, root/magisk and then install titanium to restore my full backup of that. Im sure ill be coming to a new issue trying that too, but who knows.

I fixed it the way i wanted (off the backup i made with TWRP) by restoring my backup (without EFS this time, per the tips on the devs website, rebooted into fastboot, flashed the OOS 10.3.4 fastboot image (WITHOUT -w to keep my user files), let it run. when it rebooted i had everything back from the TWRP backup!.
all i did then was boot the TWRP image, flash its zip, then flashed magisk again and rebooted.
All is well! (until Slot B issues rear their ugly head) I really hope to flash both and move to a custom ROM but saying encrypted is more important to me than I thought it was.
I hope anyone who finds themselves in the same stupid situation is helped by this come day.
PS. titanium backup is really not a system restore feature like I thought it would be when you are encrypted. TWRP was my only viable solution and so happy this worked. Ill be running that weekly, for sure.