Database Info

[Q] Stuck booting

Hello, my name is Shagington
I have been slowly unlocking the potential of my tf700t, yet I have come to a point where I am stuck loading the android OS. The problem started when I installed xposed to gain the ability to modify the permission of apps. Now it just sits with the loading circle spinning around and 'round. I tried wiping from the bootloader yet the same thing happens. While looking into the bootloader more, I found twrp installed after what I thought were many failed attempts. I tried a wipe from that as well and the same thing happens. I was thinking about just flashing a stock (rooted) rom with twrp but I am afraid of getting into a worse spot than I already am in, any help is appreciated.
Thanks, Shag

You need to post your bootloader version (read the tiny script when you boot with Power and Volume Down) and your recovery version.
That will determine what you can flash or what type of repair you can try.
Do you have fastboot and adb setup on your PC?
Check if you have a fastboot connection when booted into the bootloader and adb when booted into recovery.
See if you can capture a logcat of the boot process in adb.
Then report back.
Whatever you do, do not use the Wipe Data option from the bootloader!!!!!!!!!

Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)

shagington said:
Thank you for the quick reply berndblb, it seems im on build us 10.6.1.14.8-20130514. I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb but I will give it a go tomorrow. Will any custom rom work with the current build i have?
Thanks again, Shagington (Newbington)
Click to expand...
Click to collapse
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.

berndblb said:
Yes, there are. You are one version behind to the latest (and last) bootloader 10.6.1.14.10. Might be a good idea to update to the latest while you're at it...
Which recovery and version thereof did you flash?
Once we are sure that you have compatible software installed you can flash a bootloader/TWRP package to get you up to date, but let's resolve your current pickle first.
Click to expand...
Click to collapse
Thanks again for responding good sir, I am on twrp 2.8.5.0, which still loads just fine.
-shagington

When you install xposed it puts an emergency uninstall zip on the internal sdcard partition. Try flashing that from twrp to reverse it out.
Be careful with xposed it can sofbrick easily as you have found out.

shagington said:
I just reformatted my pc to windows 10 tech preview so im not quite sure how that will work with adb
Click to expand...
Click to collapse
I tried the first Win10 preview, and I just had to connect the tablet and run adb.exe - it worked fine with the automatically installed drivers.

Thanks for the replies guys, I couldnt find any zips on my internal, I looked through almost every folder. After looking through the adb tutorials, it is a little to intimidating for me. Kinda sad, I was under the impression that now I have twrp I could just throw some other rom on quickly or even a download a backup from someone else with the same versions to recover and be done with it. I think im just going to leave it soft bricked for a while and use my nexus 7 for now. Appreciate the help guys, it's just a little over my head.
-Shag

Bootloop 2013 Moto G Boost Mobile XT1031 8GB

Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.

blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.

I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.

You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!

_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?

blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).

_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.

@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!

stuck in fastboot mode: error boot prepare

stock rooted pixel4a (from google directly) running root.boot.sunfish-qd4a.200805.003.img iirc.
just hit the upgrade magisk button as i always do (yes, i unhid the app back to normal) but it failed. directly following this, it rebooted and i am now stuck inside fastboot mode without access to ADB. fastboot commands work but ADB do not. is there a way to upload a boot image to get me back to where i was? OR at the least, backup my phone before a full wipe. thanks in advance!

xxTECRAxx said:
stock rooted pixel4a (from google directly) running root.boot.sunfish-qd4a.200805.003.img iirc.
just hit the upgrade magisk button as i always do (yes, i unhid the app back to normal) but it failed. directly following this, it rebooted and i am now stuck inside fastboot mode without access to ADB. fastboot commands work but ADB do not. is there a way to upload a boot image to get me back to where i was? OR at the least, backup my phone before a full wipe. thanks in advance!
Click to expand...
Click to collapse
adb commands don't run on fastboot.
You must flash stock boot.img or magisk patched boot.img using fastboot flash boot "the_boot.img_file_you_want_to_flash"

should i flash this image "root.boot.sunfish-qd4a.200805.003.img"? or do you know where i get a patched magisk boot image? i've looked through magisk github as well as here but i may not be looking for the right stuff. i get the idea of what needs to be done. how i do it exactly is a little stretch, outside the obvious command "fastboot flash boot.img"
little more push in the right direction, please?
EDIT:
reviewing this https://forum.xda-developers.com/t/guide-unlock-root-safetynet-for-pixel-4a.4153773/
and this https://forum.xda-developers.com/t/help-access-internal-storage-from-fastboot.4221223/#post-84332187

the fastboot mode screen displays the following for the bootloader version: s5-0.2-6281315 and i do have a bootloader that matches that. going to give that a whirl

making headway but not booting still

xxTECRAxx said:
making headway but not booting still
Click to expand...
Click to collapse
Judging by the screens you've shared, you've just tried to flash bootloader into boot partition. DON'T DO THAT.
If I were you I would just download the complete fastboot ROM and would run flash-all.bat.
In order to retain your data, before running the bat, open it and remove the "-w" you'll see on the update command line.
This will flash the hole ROM and firmware, thus making your device to achieve boot.
Afterwards you may try to root it again.

THANK YOU!

hey @Typhus_ wanted to say thank you again! i was not only able to get back to norm, i was also able to root back to where i was, with the exception of not passing SafetyNet. been reading about it and what all is available to use with HidePropCconfig module. the pixel4a was passing prior to this riggamaroll but not really concerned about that issue at this time.
i just noticed i am not seeing the full 128gb disk. about 6 months ago i had an issue with root and went full retard, re-formatting the phone and throwing commands at it with ADB. i really couldn't tell you exactly what i did as i don't remember but i can confirm i messed with the partitions and this has obviously effected me adversely.
being that you had efficiently helped me with my bootloader and your experience here at XDA, i thought maybe you had some thoughts on the disk not being 128gb and how i might repair that. i have since backed up and in a position to go full retard
please see attached screenshots of disk analyzer, sdmaid, and a windows shared drive mount

xxTECRAxx said:
hey @Typhus_ wanted to say thank you again! i was not only able to get back to norm, i was also able to root back to where i was, with the exception of not passing SafetyNet. been reading about it and what all is available to use with HidePropCconfig module. the pixel4a was passing prior to this riggamaroll but not really concerned about that issue at this time.
i just noticed i am not seeing the full 128gb disk. about 6 months ago i had an issue with root and went full retard, re-formatting the phone and throwing commands at it with ADB. i really couldn't tell you exactly what i did as i don't remember but i can confirm i messed with the partitions and this has obviously effected me adversely.
being that you had efficiently helped me with my bootloader and your experience here at XDA, i thought maybe you had some thoughts on the disk not being 128gb and how i might repair that. i have since backed up and in a position to go full retard
please see attached screenshots of disk analyzer, sdmaid, and a windows shared drive mount
Click to expand...
Click to collapse
That storage space values are just... weird. Can't quite find another word for it.
If I ran into that kind of problem I would completely clean flash the stock ROM again, this time keeping the "-w" flag. You see, that flag completely cleans the user data partition and creates it again as soon as the flashing procedure ends. Most likely, and by doing so, your storage space values will be correct again. Obviously this will wipe everything so, if you decide to do so, please backup manually all your important stuff.
As for SafetyNet fix, you may use kdrag0n module (he made and shared one universal mod that fixes it) or you may flash my addon features module (link on my signature) that, not only, fixes SafetyNet, but also, adds several cool mods.
Cheers!

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?