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 ?

No wifi and cant activate simcard

Hello! I got a huge problem, i cant activate the wifi or the mobile functions on my phone after flashing it. Also in abote phone it says its a oneplus 7t (not pro)
May i have flashed a oneplus 7t firmware? I have tryed the volte fix with no ressults.. When i bricked the phone i did an flashall using fastboot, but culdent flashs system and vendors. Please help me!

I did the same thing as well. I ended up using the msm tool to flash the 9.5.3 gmba software then downloaded and updated to the 10.0.3. after that finished I downloaded the 10.3 global update and went smoothly. Then go to bootloader and flash twrp and root. First time you flash twrp make sure you check the box for ramdisk otherwise recovery won't stay as twrp, it will just keep going back to stock recovery. Also before you restart your device you have to flash magisk otherwise your phone will not boot. Also if you restart and their is no cell reception or cannot turn on wifi you will either have to go back and uninstall magisk then reinstall or do the process all over again. I did the 9.5.3 because I tried others and failed to reflash. The 9.5.3 seems to always work for many people

Knorrigbollen said:
May i have flashed a oneplus 7t firmware?
Click to expand...
Click to collapse
Impossible to tell what you've done. You haven't given sufficient info. Only you know what has been done to the phone so far. Where did you get the file, what is the file named, etc.
You have 3 threads going, none of which have sufficient info for anyone to provide proper help. Making multiple threads is not the right way to get help. Just confuses those trying to help you, and will make the situation worse. Stick to one thread, and give as much specific info as possible, as I've noted here: https://forum.xda-developers.com/on...ease-soft-bricked-phone-t4044311#post81668605

Im sorry im panicing

I tryied to flash the stock rom from this site after failed to root. THe fastboot one, when flashing it fails to flash system a and b, says partion not found

Hello again!
Ive been trying the msm tool, i downloaded it from here
https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909
It says it shuld support my version (hd1913) but MSM tool says "unsupported Target EU)
HOw can i fix this?

Also, ive flashed a oneplus 7t image, shuld i flash a new image and brick it then use msm tool?`
now it says Devices not match image. The post says it shuld support my model.

how to unbrick a pixel 4a anyone need help

flashed from graphene os and back to stock during stock flashing something failed and gives me a black screen and goesinto the screenshot provided

You can try to go through the applicable steps in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Like installing the USB drivers, and SDK platform tools.
Then put the phone in fastboot mode and download an image from google and do a "flash-all.bat"

JohnC said:
You can try to go through the applicable steps in this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
Like installing the USB drivers, and SDK platform tools.
Then put the phone in fastboot mode and download an image from google and do a "flash-all.bat"
Click to expand...
Click to collapse
it wont work , that is what caused the issue, there is no adb or fasboot commands as the phone has nothing to load or read, it was flashing the official latest stock firmware using the flash-all.bat, then after the first rebbot and waiting for devices it goes to a black screen and shows what i put in the screen shot,(i believe the battery died during flashing) there is two modes it goes into the qusb which is the qualcomm download mode and some other mode i cant tell neither can the pc device find drivers to read the phone, techinically this phone is not fixable using normal methods , but i believe there is a way to flash to firmware back on,i have looked into using edl and qspt flashing but it still doesnt read the phone, any help would be greatful i have device protection but they are sending me a refurbished phone i would rather try to fix this before i do get the replacement, as it was a new and working device

i have been able to find a working qualcomm driver is there anyway to edl or msm file for the pixel 4a to fix this, now that the phone is being read properly it should be able to take commands as it is reconized as a modem driver or port

Any Ideas Why Its Failing , says sahari protocal failed

files needed to repair phone, anyone able to extract or have files
RAM file (MPRGXXXX.mbn), e.g: MPRG8916.mbn
Boot file (XXXX_msimage.mbn), e.g: 8916_msimage.mbn

miko12312 said:
files needed to repair phone, anyone able to extract or have files
RAM file (MPRGXXXX.mbn), e.g: MPRG8916.mbn
Boot file (XXXX_msimage.mbn), e.g: 8916_msimage.mbn
Click to expand...
Click to collapse
I did the same thing as you trying to got back to stock. Still trying to find those files to unbrick myself.

vabeachboy0 said:
I did the same thing as you trying to got back to stock. Still trying to find those files to unbrick myself.
Click to expand...
Click to collapse
I believe Qualcomm is the ones that obtain these files not Google , only other way is to dump the files from download mode on a working device

I'd like to help by dumping the required files, I didn't know anything about EDL before doing research for this thread, but as I understand using EDL mode require a device-specific non-free "loader".
I'm trying to use B. Kerler's EDL tool (https://github.com/bkerler/edl) but fail because it doesn't have the proper loader file in its database.
If anyone come across the loader for the Pixel 4a (000e60e10066000a_3ef72a02fb931be1_fhprg.bin), I'd be happy to share boot and memory dump from my phone.

I encountered the same situation as you, did you solve it?

Older thread I know, but I've used EDL mode (on LG phones) to save partitions and write partitions.
But you have to have a 'programmer file' for the specific device for it to work. Aka a 'firehose' file for the specific device / chip.
Some mfg's make this available, some don't. Google does not. So, even having the file(s) you want to flash won't help, not if you don't have the firehose file.
sorry, cheers

Has anyone figured this out? Could really use some help. Thank you

Did anyone managed to unbrick phone? I bricked my phone. Now it's just black screen.

mizzunet said:
Did anyone managed to unbrick phone? I bricked my phone. Now it's just black screen.
Click to expand...
Click to collapse
Only suggestions are the go to software of choice,, pixel flasher or android flash tool, both need bootloader unlocked

@hammered58 Gladly, I was able to get it back. I was trying to relock bootloader with custom ROM. But failed.
Has anyone relocked bootloader with LineageOS/custom ROM?
I was following https://forum.xda-developers.com/t/signing-boot-images-for-android-verified-boot-avb-v8.3600606/ to sign boot and recovery images. Then flashed and relocked bootloader. But phone stuck at black screen. Has anyone managed to self...
forum.xda-developers.com

mizzunet said:
@hammered58 Gladly, I was able to get it back. I was trying to relock bootloader with custom ROM. But failed.
Has anyone relocked bootloader with LineageOS/custom ROM?
I was following https://forum.xda-developers.com/t/signing-boot-images-for-android-verified-boot-avb-v8.3600606/ to sign boot and recovery images. Then flashed and relocked bootloader. But phone stuck at black screen. Has anyone managed to self...
forum.xda-developers.com
Click to expand...
Click to collapse
Glad u got it going, the only time I relock is when I sell the phone, otherwise I have no need as all my apps work with unlocked

hammered58 said:
Glad u got it going, the only time I relock is when I sell the phone, otherwise I have no need as all my apps work with unlocked
Click to expand...
Click to collapse
Right. Every apps working even on unlocked state. But would be nice to get rid of the warning while booting.

mizzunet said:
Right. Every apps working even on unlocked state. But would be nice to get rid of the warning while booting.
Click to expand...
Click to collapse
I will second that, unfortunately I don't think it's possible, at least not that IAM aware of

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.

Question Your device is corrupt. Oneplus 9

I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9

Flash by edl if you can't do it then pm I'll fix it by tv

Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck

applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day

SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above

rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.

I had this problem because I flashed a custom kernel on a custom rom today

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.