Database Info

solution for slot unbootable load error

Help please. Is there a solution for slot unbootable : load error. My device is pixel 2. I try to flash factory image. But it keep show warning about no boot.sig,recovery.img. ,System.sig. please help???

Always show this when i try to flash-all.bat

If you use the main search and search 'pixel 2 unbootable slot error' it should list up a few threads with some info on it and how others have recovered from that problem.
Hope that helps

junglism93 said:
If you use the main search and search 'pixel 2 unbootable slot error' it should list up a few threads with some info on it and how others have recovered from that problem.
Hope that helps
Click to expand...
Click to collapse
Yes, i have use the main search. But i can't find a solution yet. I try all of them but i can't find the worked one. My device is unlocked. But i always failed to flash factory image. But thanks for the respond. I'll keep serching???

boku45 said:
Yes, i have use the main search. But i can't find a solution yet. I try all of them but i can't find the worked one. My device is unlocked. But i always failed to flash factory image. But thanks for the respond. I'll keep serching???
Click to expand...
Click to collapse
Fair enough mate, sorry that was no help. When you run the flash-all does it complete the flash other than the sig errors which if I remember right is normal (been a while since I flashed a factory image) or does it throw an error up? If it does then maybe post up the error so someone may have a better idea of what's needed to get you up and running, it's not something I've run into as yet so no real answer to it from me.
Only thing I could suggest is as you seem to have a working adb you could try to swap off the slot that is non bootable to the other slot via fastboot with fastboot --set-active=a or b at the end, that will swap you to the inactive slot that should have a working system on it and see if that boots you up and then flash the factory image or an ota image and see if that resolves it. Oh, make sure your platform tools are up to date, that can cause issues (had issues flashing stuff with my pixel using out of date platform tools)
Good luck

junglism93 said:
Fair enough mate, sorry that was no help. When you run the flash-all does it complete the flash other than the sig errors which if I remember right is normal (been a while since I flashed a factory image) or does it throw an error up? If it does then maybe post up the error so someone may have a better idea of what's needed to get you up and running, it's not something I've run into as yet so no real answer to it from me.
Only thing I could suggest is as you seem to have a working adb you could try to swap off the slot that is non bootable to the other slot via fastboot with fastboot --set-active=a or b at the end, that will swap you to the inactive slot that should have a working system on it and see if that boots you up and then flash the factory image or an ota image and see if that resolves it. Oh, make sure your platform tools are up to date, that can cause issues (had issues flashing stuff with my pixel using out of date platform tools)
Good luck
Click to expand...
Click to collapse
Thank you so much. You are right. I use out of date platform tools. My pixel alive again now, after i use latest platform tools. Thanks again for your help. ???

boku45 said:
Thank you so much. You are right. I use out of date platform tools. My pixel alive again now, after i use latest platform tools. Thanks again for your help. ???
Click to expand...
Click to collapse
You're welcome mate and at least it was a simple fix ?

Booting from Slot B

Hi - I recently tried to boot from Slot B, and it didn't go well. My OP7P appeared to be boot-looped from Slot B, with a very slow "circling electron" animation. I thought Slot A and Slot B pretty much mirrored each other.
Is there anything I should do to make both Slot A and Slot B bootable?
Thanks,
¿GJ?

[RECOVERY][DUALBOOT][MAGISK][3.3.1-79][Unified]Unofficial TWRP for OnePlus 7/7 Pro/5G
If you want to make something like this for your device, check out this guide here Since I no longer have an OP 7 series device, this mod is now deprecated and won't be receiving any more updates. invernomut0 has made a continuation of this mod...
forum.xda-developers.com
;-)

Thanks, @ghost323 - I installed mauronofrio's TWRP from above, but I'm not seeing any difference.
One thing that I maybe should mention is that when I boot into Recovery Mode after swapping to Slot B, I don't get prompted for my device encryption password, and nothing is mounted by TWRP. I expect that is why I am going into a bootloop.
¿GJ?

Did you read the thread carefully? At least some pages?
There is a description of what to do.
I thought about it a year ago. In the end I decided against it.
You should also look at the basics of a / b devices. Many of your questions are answered there.
Reading something into these topics doesn't hurt ;-)

In fastboot type fastboot --set-active=a

How to sideload into OP 8T (KB05AA)? Help!

My current OxygenOS is the latest "12" version which after the OTA, OnePlus has strangely removed from their support site. It has some issues I don't like as well as many others who have posted on the OP Community board. The inactive partition is corrupted and I'm not sure what happened except I was rooted and tried to use Magisk protocol to keep root, but I got a bootloop afterwards. I changed the active slot to the old slot and got the new "12" version running. The inactive slot is corrupted and I get a Qualcom error message.
I want to go back to the previous ver "11" or LineageOS 18.1. However, I cannot get anything to allow me to sideload to the inactive partition or any partition. If I use adb while the phone is in normal operation, I get adb to show devices so I know I have a link. However, I cannot do adb sideload from the normal booted phone. So I have to reboot it to recovery where it looses it's connection to the adb command on the PC. It sees the phone but says it is unauthorized. It is a loop where adb works while phone is booted but not when I am in recovery. I have USB debugging set on and have revoked usb debugging and reset the whole scenario many times to see if different sequences might work so that I can do a sideload. Nothing has gotten me past this yet. I have even tried the Oxygen Updater app but OxygenOS system update won't let you install a prior version if you have the current one.
Any suggestions. Thanks

zzjea said:
My current OxygenOS is the latest "12" version which after the OTA, OnePlus has strangely removed from their support site. It has some issues I don't like as well as many others who have posted on the OP Community board. The inactive partition is corrupted and I'm not sure what happened except I was rooted and tried to use Magisk protocol to keep root, but I got a bootloop afterwards. I changed the active slot to the old slot and got the new "12" version running. The inactive slot is corrupted and I get a Qualcom error message.
I want to go back to the previous ver "11" or LineageOS 18.1. However, I cannot get anything to allow me to sideload to the inactive partition or any partition. If I use adb while the phone is in normal operation, I get adb to show devices so I know I have a link. However, I cannot do adb sideload from the normal booted phone. So I have to reboot it to recovery where it looses it's connection to the adb command on the PC. It sees the phone but says it is unauthorized. It is a loop where adb works while phone is booted but not when I am in recovery. I have USB debugging set on and have revoked usb debugging and reset the whole scenario many times to see if different sequences might work so that I can do a sideload. Nothing has gotten me past this yet. I have even tried the Oxygen Updater app but OxygenOS system update won't let you install a prior version if you have the current one.
Any suggestions. Thanks
Click to expand...
Click to collapse
I've tried to sideload OOS 11 using Los recovery, but it doesn't work. And, since OOS recovery doesn't support sideloading I'd say that sideloading isn't an option.
However, using payload dumper and fastbootd may be an option. I would have tried this but I'm on 12 and there's no full install zip. But you're going back to 11 so this is a possibility.
But I wouldn't make these changes in the current working slot - don't break what's working.
I'm also not sure whether to use the OOS recovery for the fastbootd stuff or use one from a custom rom.
As you can gather, I've not done this. So you have to work out the details yourself and be prepared to be a guinea pig for the process.
If you do go down this path I'd be very interested in the outcome.
Of course, you could always use the MSM tool to go back to an older version.

Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks

zzjea said:
Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks
Click to expand...
Click to collapse
I presume that A and B slots are partitions
Code:
lrwxrwxrwx 1 root root 16 1970-01-03 04:30 /dev/block/bootdevice/by-name/boot_a -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 1970-01-03 04:30 /dev/block/bootdevice/by-name/boot_b -> /dev/block/sde35
So try using MSM tool to restore them or find a copy of that partition from a working phone and flash on yours.
Maybe this can help you as well.

zzjea said:
Since there is no TWRP for OP8T and recovery is non-existent on it, how is anyone installing ROMs on this device. I have just jumped from my original purchase of OnePlus One that still works except for the power button (it is current with LineageOS 18.1 and rooted), to the OP8T over a month ago and a lot has changed since the OPO. I have looked up fastbootd but still don't understand the differences. Comments about installing ROMS are made all over this forum but most assume you know how to do it. I have gotten spoiled with TWRP on the OPO and can flash a new ROM in around a minute almost with my eyes closed. This is getting confusing. I successfully rooted this OP8T after I got it and that was a very touchy thing having to jump through a bunch of hoops to get it done. I was surprised that it worked after all the steps that were required. It used to be that there was info on how to do this kind of thing on this forum, but now it seems that most everyone thinks you should already know the basics. Well the basics are part of my problem right now. A and B slots are new to me and I think I understand that but have not seen an explanation of how that all works when loading ROMS. I have a working phone at the moment in the active slot, but the "other" slot is corrupted. I tried to duplicate the active slot to the inactive slot and of course I can't get adb to work.... Isn't anyone else having these issues? I will look into the MSM tool again.
If you know where the info is that I'm looking for is, please give me the links. Thanks
Click to expand...
Click to collapse
Here's some information that I found helpful:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
Dynamic Partitions | Android Open Source Project
source.android.com
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Here's a couple of ways to get one partition to look like another one:
1. The Los pre-installation instructions have instructions on how to sync the partitions. Note: it doesn't sync boot, dtbo, or vbmeta.
2. If you're rooted you can copy one partition to the other using
Code:
dd if=/dev/block/by-name/xxxx_(active-slot) of=/dev/block/by-name/xxxx_(inactive-slot)
For example:
Code:
dd if=/dev/block/by-name/boot_b of=/dev/block/by-name/boot_a
Note that you can find out which is the active slot using getprop ro.boot.slot_suffix
I've written a shell script based on the Los zip in 1. (see attachment) that will do all partitions - use at your own risk. Don't run it unless you understand what it's doing.

[BOOTLOADER] Error: Unable to boot from 2nd slot! [QUALCOMM CrashDump 0x00007f00]

Hi all,
trying to boot form second slot ends up in QUALCOMM CrashDump 0x00007f00 and I have no idea how to fix it.
Edit: Booting from slot A & recovery works fine. Only trying to boot from B ends up in this error.
I own a new 8T, currently with stock OxygenOS 11.0.11.11, TWRP installed and wanted to prepare it to install a custom rom.
So according to https://lineageosroms.com/kebab/ I used copy-partitions-20210323_1922.zip, to sync slots.
After syncing, trying to change to 2. slot (used TWRP to change slot) ended up in error above.
On 2. slot I was not even able to mount /data...
Tnx to @BillGoss I could fix an issue - partitions boot_a|b, dtbo_a|b, vbmeta_a|b did defer.
Now all AB-partitions are identical, but still booting in 2. slot ends up in CrashDump.
(Anyway, after syncing all deferring partitions, mounting /data in TWRP now works on both slots.)
What else could be wrong, that I am not able to boot to 2. slot?
How can I fix this problem?
Edit: I have no Windows machine - Linux only, so using MSM tool would be a big issue for me...
Help is really appreciated.
Tnx in advance,
Enkidu

Use the MSM tool to get your device bootable again...
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

Ramme said:
Use the MSM tool to get your device bootable again...
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Great! Tnx for fast reply!
Hmmm... I do not own a Windows system.
May there be a different way to fix my problem?

Download what you want, you can Update later to the Last Version , all MsM Work fine

Ramme said:
Download what you want, you can Update later to the Last Version , all MsM Work fine
Click to expand...
Click to collapse
Tnx. I needed a second to understand it.
But next problem is, I do not own a Windows system. Linux only...
May there be a different way to fix my problem?

Sorry, I'm out of that one. I'm sure there is a command method, but your bootloader is crashed, so you don't have a command option, so the only thing left is the MSM tool.

Ramme said:
Sorry, I'm out of that one. I'm sure there is a command method, but your bootloader is crashed, so you don't have a command option, so the only thing left is the MSM tool.
Click to expand...
Click to collapse
Maybe I was not clear enough. Only booting for slot A does not work. Booting from B or recovery works fine.

I think you can use fastboot mode from one of the working slots to flash oos into both the slots using Linux. Guide attached.
upfiles - Make Money by Sharing Files!
upfiles is a file-sharing platform that allows users to make money by sharing files. We offer the best storage and payout rates ever!
upfiles.com

@enkidu70 you shouldn't care about not being able to boot into one of the slots.
The A/B configuration is specifically designed for dealing with seamless updates. These (updates) result in only one of the slots being bootable at any one time.
Since you have one slot that works fine, that's good. And don't bother with trying to restore your phone to its original setup - that will still leave you with one bootable slot!
If you're planning to install a custom rom using TWRP, then have a look at how things get flashed: https://forum.xda-developers.com/t/...ect-8t-kebab-2021-09-04.4302449/post-85910241

BillGoss said:
@enkidu70 you shouldn't care about not being able to boot into one of the slots.
Click to expand...
Click to collapse
Tnx. Tried it. Works!
(For some reason, It was a bit tricky to get /data formatet - but now everything seems fine!)
Tnx for your great support!

Did you ever get both slots to work? I have the same problem. I can go into fastboot to change the active slots to boot into Slot b, but Slot A is still not working. Will it ever work?

Duplicating my B partition of my OP 7Pro onto my A partitiion?

I'm running OOS 10.3.8 on my OP 7Pro (GM1917). Currently, I boot into that OS via the B partition.
I'd like to duplicate everything in the B partition and install it on the device's A partition, so that I can switch between the A and B partition and boot up identically, no matter which partition I choose.
In the past, I did what is described in the two following posts in order to duplicate B onto A:
https://forum.xda-developers.com/t/...droid-device-partitions.2450045/post-83339451
https://forum.xda-developers.com/showpost.php?p=83389563&postcount=2818
I could do that again, but I'm wondering if perhaps a newer way of accomplishing this might have been developed since back then.
Thanks in advance for any thoughts or suggestions.

HippoMan said:
I'm running OOS 10.3.8 on my OP 7Pro (GM1917). Currently, I boot into that OS via the B partition.
I'd like to duplicate everything in the B partition and install it on the device's A partition, so that I can switch between the A and B partition and boot up identically, no matter which partition I choose.
In the past, I did what is described in the two following posts in order to duplicate B onto A:
https://forum.xda-developers.com/t/...droid-device-partitions.2450045/post-83339451
https://forum.xda-developers.com/showpost.php?p=83389563&postcount=2818
I could do that again, but I'm wondering if perhaps a newer way of accomplishing this might have been developed since back then.
Thanks in advance for any thoughts or suggestions.
Click to expand...
Click to collapse
Well, I got impatient, and I just re-ran what I described above, and it worked.
I'm still wondering if there might be a better way to do this, however.