Database Develop

Unbrick Xiaomi Mi A2 [jasemine]

Hello,
i have bought a new Xiaomi Mi A2 and thought it would be a really nice idea to flash magisk on it. First everything was alright. I unlocked my bootloader in fastboot with "fastboot oem unlock" and flashed twrp on the b partition. Unfortunately my device broke (don't know why... maybe the unofficial twrp with some bugs or...). So now i have a really big problem, because my twrp recovery is missing as well as the stock recovery. When i try to switch on the mobile i am stuck in bootloop (with the mi logo). Not even the bootloader warning is shown.
Fastboot mode is working but not really nice. Not even the mitu appears, no the display is black (or doesn't show anything.. The device's display is on).
My Mi A2 is recognized by the computer so I considered to flash the stock rom with fastboot.
I thought it would work, but in the mi flash programm i got the erorr: flash devcfg_a error.
Now i can't switch my mobile off, because when I'm holding the power button, it restarts and restarts and restarts...
I know i am stupid and maybe have done something wrong, but i would be soooo happy to get some help
Thank you so much!

Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot

Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?

MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used.... ?
Click to expand...
Click to collapse
what's the exact command you used?

Nebrassy said:
what's the exact command you used?
Click to expand...
Click to collapse
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MardukPVP said:
In minimal ADB and Fastboot I used: fastboot flashing unlock_critical
Click to expand...
Click to collapse
Don't use minimal adb, use this https://developer.android.com/studio/releases/platform-tools

Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!

Not receiving updates
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:

jdivya524 said:
I need help i recently flashed fastboot rom on mi A2 Oct patch firmware.I can't receive any Ota Updates,How to get in phone on original state? With working online updates in settings PLEASE HELP!!:crying::crying:
Click to expand...
Click to collapse
So you have flashed this rom https://en.miui.com/download-353.html ?

Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
I promised I would create an account here just to thank you if your method worked!
After doing something dumb (I typed some wrong commands I think) my A2 got into the infinite reboot, never got out of the android logo, I tried everything and literally thought I lost my phone for good ;n;
I downloaded "jasmine_global_images_V10.0.2.0.PDIMIFJ_20181206.0000.00_9.0_02b8deeb6d.tar" and flashed that on miflash and watched my phone come back from the dead like frankestein or something. He's doing great and is in top shape, thanks to your advice! THANK YOU VERY MUCH! Hope you have a wonderful 2019!
Click to expand...
Click to collapse

MardukPVP said:
Okay, i've got no words. You saved my life. It worked. Thank you sooo much !!!
Click to expand...
Click to collapse
Hey Did Your smartphone works fine I mean did you get every Updates from Stock

error
Nebrassy said:
Fastboot flashing unlock_critical
(It will wipe /data)
then flash with mi flash
But before doing that, try just flashing stock boot
Fastboot flash boot_a boot.img
Or boot_b if that's your active slot
Click to expand...
Click to collapse
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you

[email protected] said:
When i try it shows the error remote error flashing partition , how to solve that help please my email is [email protected] , replay there if possible thank you
Click to expand...
Click to collapse
Try flashing through edl mode

I think I bricked my mi a2 please help me.
MardukPVP said:
Thank you very much for your answer.
Unfortunately i have wiped everything in twrp before (when it worked) so there's nothing stored on the device.
When i type in critical unlock only a big list of commands appears which can be used....
Click to expand...
Click to collapse
I have a mi a2 and it's stuck on Android logo screen. It has an unlocked bootloader and maybe it's rooted too. While I thought I rooted it.. It went into bootlooping.. Only fastboot and android logo can be accessed. I tried flashing it with stock rom but mi flash tool goes like 3500+ sec. Please tell how to fix this.

same issu
okay i hav the same problem, can't fix it
whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown"
is there any solution? it will me life saving.

anikapproe said:
...whenever i try to use any command in cmd during the device is in fastboot mode, my phone screen go to the black, and it says in a liitle, "press any key to shutdown" is there any solution?
Click to expand...
Click to collapse
I have the same issue in PC I'm writing this from (in USB3.1 Gen2 and Gen 1 ports, and even in USB 2.0 ports), but have no problems in 2 other PCs I currently have access to.
For non-universal solution with my current PC please see more info in my answer in neighbouring thread: https://forum.xda-developers.com/showpost.php?p=81693759&postcount=28.

Stuck in fastboot

Yes, it is my own fault. I rooted yesterday, and installed a kernel today. All was fine until I tried to update to to the November update, never got that far.
I made sure to use the correct factory image for Magisk.
In adb i typed fastboot recovery, and my is now stuck on the google splash screen.
I can boot to fastboot, with the power button, and down arrow, and that's it.
fastboot devices, in adb does return the serial number.
I am unable to get beyond that. I know I'm softbricked.
Any suggestions would be appreciated.

Seems like you should be able to side load factory image

After about 20 tries, I was finally able to boot to recovery. I'm going to factory reset, and redo. Thanks for the help, though.

mimart7 said:
After about 20 tries, I was finally able to boot to recovery. I'm going to factory reset, and redo. Thanks for the help, though.
Click to expand...
Click to collapse
https://forum.xda-developers.com/pi...-10-q-root-t3996969/post80774791#post80774791

Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
View attachment 4873031

mimart7 said:
Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
Click to expand...
Click to collapse
In adb mode in the OS, try typing..adb kill-server...
Then allow your device to always communicate with your pc, your having a driver issue. Your readout for your factory image is correct. There is no recovery anymore, it's tied in with the boot.img

mimart7 said:
Here is an update:
When I run adb devices, the serial number is not returned.
When I run fast devices, the serial number is returned.
I have extracted all the files from the zip, for the image, there is no boot.sig, recovery.img, system.sig, or vendor sig.
Click to expand...
Click to collapse
@mimart7
If you booted fastboot mode, fastboot devices is all that is needed to insure your phone is communicating with your computer.
Are you using the latest SDK platform-tools 29.0.5?
If yes, is the Platform-tools, and the extracted factory image files in this folder C:\Platform-tools\New folder?

I've got it working, thanks to all.

mimart7 said:
I've got it working, thanks to all.
Click to expand...
Click to collapse
How did you git it working if you dont mind coming to talk to me please.
https://discord.gg/XnMeYF6

DemonicMurderer said:
How did you git it working if you dont mind coming to talk to me please.
https://discord.gg/XnMeYF6
Click to expand...
Click to collapse
Did you have:
USB Debugging enabled?
Do you have Platform Tools?
https://developer.android.com/studio/releases/platform-tools
When in fastboot, and your phone is attached to your computer, and you type fastboot devices in adb, do you get your the serial number of your phone?

I'm in this situation and yes I have the lastest platform-tools. I do get the serial number back when I type fastboot devices. My folder location is C:\Platform-tools

Caselka said:
I'm in this situation and yes I have the lastest platform-tools. I do get the serial number back when I type fastboot devices. My folder location is C:\Platform-tools
Click to expand...
Click to collapse
What situation? SDK Platform-tools r29.0.6?
What are you trying to do?

Homeboy76 said:
What situation? SDK Platform-tools r29.0.6?
What are you trying to do?
Click to expand...
Click to collapse
Yup SDK r29.0.6.
I was soft-bricked and stuck in a boot loop.
I managed to get to recovery mode but only by flashing all the files then holding the power button & volume up button.
Once in recovery, I tried a million things to figure out how to get it back to a clean slate.
After hundreds of tries, I managed to sideload flame OTA.
The phone's bootloader is now unlocked.
Now going to focus on what I did wrong originally when trying to get Magisk on the Pixel 4 :laugh:

Caselka said:
Yup SDK r29.0.6.
I was soft-bricked and stuck in a boot loop.
I managed to get to recovery mode but only by flashing all the files then holding the power button & volume up button.
Once in recovery, I tried a million things to figure out how to get it back to a clean slate.
After hundreds of tries, I managed to sideload flame OTA.
The phone's bootloader is now unlocked.
Now going to focus on what I did wrong originally when trying to get Magisk on the Pixel 4 :laugh:
Click to expand...
Click to collapse
Search the pixel 4 thread.

Homeboy76 said:
Search the pixel 4 thread.
Click to expand...
Click to collapse
All done. Managed to successfully complete it

stuck in fastboot
Caselka said:
All done. Managed to successfully complete it
Click to expand...
Click to collapse
hi im also stuck in fastboot but no serial coming up under fastboot devices. was doing a flash-all.bat when it stopped halfway through and has been stuck ever since. cant go into recovery or anything. Any help would be appreciated.

[SOLVED] Can't using LGUP now. bootloop with 9008 mode. (V409N)

Hello!
I unlocked the bootloader first.
However, after rebooting, the twrp failed to flash.
and I got a message to re-lock the bootloader.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After that, I checked several guides and tried.
but now, never can't boot and can't use LGUP.
Any method to restore stock rom via 9008 mode? please help.
PS :
I think download mode is also broken.
Please let me know if there's any way to recover the download mode.

1688_ said:
Hello!
I unlocked the bootloader first.
However, after rebooting, the twrp failed to flash.
and I got a message to re-lock the bootloader.
View attachment 5211369
After that, I checked several guides and tried.
but now, never can't boot and can't use LGUP.
View attachment 5211375
View attachment 5211379
Any method to restore stock rom via 9008 mode? please help.
PS :
I think download mode is also broken.
Please let me know if there's any way to recover the download mode.
Click to expand...
Click to collapse
I'd suggest looking at this thread. Also, the screen telling you the bootloader is unlocked is normal, when you have a device that has it unlocked, you *always* see it when you boot up.
cheers

AsItLies said:
I'd suggest looking at this thread. Also, the screen telling you the bootloader is unlocked is normal, when you have a device that has it unlocked, you *always* see it when you boot up.
cheers
Click to expand...
Click to collapse
Very thank you!
but Unfortunately, it didn't work for me.
I forgot what i did, but maybe I modified xbl_a, xbl_b, etc.
and try below method it didn't work, too.
I've touched too many things....
I'd like to know if there's a way to force the use of LG Flash Tool or something like that.

1688_ said:
Very thank you!
but Unfortunately, it didn't work for me.
I forgot what i did, but maybe I modified xbl_a, xbl_b, etc.
and try below method it didn't work, too.
I've touched too many things....
I'd like to know if there's a way to force the use of LG Flash Tool or something like that.
Click to expand...
Click to collapse
Follow this post. (Don't speak Spanish so have no idea what the above video is doing, can't help there).
Essentially, when you flash an image to a partition it doesn't belong in, you run the risk of overwriting into nearby partitions (because image is bigger than partition size). If you do that, then the only solution is what's in the post above. It basically restores the entire device using qfil. Because when you start overwriting partitions (and possibly the partition table), there's no way of knowing what is messed up and what isn't.
cheers

AsItLies said:
Follow this post. (Don't speak Spanish so have no idea what the above video is doing, can't help there).
Essentially, when you flash an image to a partition it doesn't belong in, you run the risk of overwriting into nearby partitions (because image is bigger than partition size). If you do that, then the only solution is what's in the post above. It basically restores the entire device using qfil. Because when you start overwriting partitions (and possibly the partition table), there's no way of knowing what is messed up and what isn't.
cheers
Click to expand...
Click to collapse
thank you !!
I'll try this right now and report

you
AsItLies said:
Follow this post. (Don't speak Spanish so have no idea what the above video is doing, can't help there).
Essentially, when you flash an image to a partition it doesn't belong in, you run the risk of overwriting into nearby partitions (because image is bigger than partition size). If you do that, then the only solution is what's in the post above. It basically restores the entire device using qfil. Because when you start overwriting partitions (and possibly the partition table), there's no way of knowing what is messed up and what isn't.
cheers
Click to expand...
Click to collapse
You are my hero!! So many thank you!!
I've only tried 3 and 4.
download mode has come alive.
btw, why my v40 has fail to install twrp?
my system is LMV409N(SKT)
Maybe I should give up custom rom for a while.
many thanks!!!

1688_ said:
you
You are my hero!! So many thank you!!
I've only tried 3 and 4.
download mode has come alive.
btw, why my v40 has fail to install twrp?
my system is LMV409N(SKT)
Maybe I should give up custom rom for a while.
many thanks!!!
Click to expand...
Click to collapse
good that it worked. Follow this link and in the folder find boot_20n_magisk.img and use it (assuming you're on kor 20n), use qfil to flash it to boot_a and b.
It has both magisk and twrp in it. Remember, after flashing it in qfil (save original first of course), you need to hold vol - and pwr for a few seconds (until u hear windows chime meaning disconnect), to exit qfil.
But! and this is important, we don't want the device to boot, we want to go directly to recovery. So keep both buttons pressed but when LG logo appears, release pwr and then re-apply it, which then goes to recovery.
in recovery, u have to format data, then reboot recovery and flash dm_verity.
cheers

AsItLies said:
good that it worked. Follow this link and in the folder find boot_20n_magisk.img and use it (assuming you're on kor 20n), use qfil to flash it to boot_a and b.
It has both magisk and twrp in it. Remember, after flashing it in qfil (save original first of course), you need to hold vol - and pwr for a few seconds (until u hear windows chime meaning disconnect), to exit qfil.
But! and this is important, we don't want the device to boot, we want to go directly to recovery. So keep both buttons pressed but when LG logo appears, release pwr and then re-apply it, which then goes to recovery.
in recovery, u have to format data, then reboot recovery and flash dm_verity.
cheers
Click to expand...
Click to collapse
Thank you very much for your follow-up.
I succeeded in entering the twrp.
But I got screen asking password, there's default password or something?

1688_ said:
Thank you very much for your follow-up.
I succeeded in entering the twrp.
But I got screen asking password, there's default password or something?
View attachment 5213013
Click to expand...
Click to collapse
There's no password, you just cancel out of that but be sure to do the 'swipe' to make it modifiable. The key after that is to format data, then reboot recovery and flash dm_verity, then encryption won't exist and no longer asked for pw.
cheers

AsItLies said:
There's no password, you just cancel out of that but be sure to do the 'swipe' to make it modifiable. The key after that is to format data, then reboot recovery and flash dm_verity, then encryption won't exist and no longer asked for pw.
cheers
Click to expand...
Click to collapse
OK, Thank you!!
I followed the guide below and no more password message!!
How to use decrypted stock by @Xsavi : https://forum.xda-developers.com/lg-v40/how-to/guide-twrp-data-access-stock-t3970149
I think everything's finally settled.
I'll try my best to enjoy the v40 now.
Thank you so much for your help.
many many thank you!!!!!!!

Phone stuck at black Mi logo

Hello, I never experienced this before so here I am trying to find some explanation, hopefully it's the right place... I have a Xiaomi Mi 5 Pro, few years old, sometimes slow but otherwise perfect, I changed the battery couple times.
Today I noticed it was at around 20% charge, I plug it to the wall, and leave it on the bed (turned on). After a few hours I go back to check on it and found the 100% indicator, but the phone was turned off.
I obviously try to turn it back on, but it gets stuck at the Mi logo (black screen with "unlocked" text below). I have installed a MIUI.eu rom ver. 11, twrp 3.2.3-0 recovery, and everything has been fine for years. I tried several times, still Mi logo (it's not bootloop, it's just stuck).
Suprised, I try to boot into recovery, and there I noticed that all the partitions are marked empty 0 bytes. I tried several things like backup, switching file format, restoring file system, etc., but it just won't work. It's like it has all been wiped and can't be mounted again.
I connected it to my desktop, MTP enabled from twrp, device recognized, storage completely empty. I remember I could see files there just the other day...
I tried all possible wipes, they won't work, either can't mount the partitions or other errors.
I already asked for suggestions elsewhere, which pointed me to fastboot flash using the adb/fastboot tools on Windows.
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Also if I boot in recovery, I can see it detected in the adb/fastboot tools screen, the scary part is that there it says "Bootloader: locked" (but it has been unlocked for years, and it even says unlocked in the black Mi screen!)
I'm lost, I never had anything like this, any suggestions to save the device? I would be really grateful

ZexDC said:
Well it says "Looking for devices...", the fastboot screen on the phone stays there for about 30 seconds, then it goes to the black Mi logo and then it shuts down.
Click to expand...
Click to collapse
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.

Indie Zex said:
You probably don't have proper drivers for Mi 5 installed, download MIFLASH UNLOCK 3.5.1108.44 from here https://xiaomifirmware.com/downloads/download-mi-unlock-3-5-1108-44/
Double click on MiUsbDriver and install fastboot driver. Then phone will stay in fastboot mode when connected to PC, so you can try to install some original fastboot rom. I don't know what is the problem.
Click to expand...
Click to collapse
Thanks it was the driver stopping the fastboot.
Now I still cannot flash anything though, I get the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tried different roms, different MiFlash, from terminal, but same error.
From recovery I still see empty not mounted partitions.
Any other suggestions?

Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.

Indie Zex said:
Well I don't know. Have you tried to format data in TWRP? Go into Wipe/Format Data/type yes (this will wipe EVERYTHING on phone) then from main menu reboot into recovery again and see if things changed.
Click to expand...
Click to collapse
Yes that was the first thing I tried unfortunately that's where I found out something was off... I can't wipe any partition, I can't mount any partition, I tried to switch filesystem but no luck.
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...

ZexDC said:
I was reading in the forums here about "sudden death" and it kinda feels that's what happened. Phone fine one day, dead the next with no real explanation...
Click to expand...
Click to collapse
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...

Indie Zex said:
That's a bummer. I don't think that phone is dead, but it looks that it somehow locked itself. According to this guide https://flash-er.com/xiaomi-mi-5-flash-file/ you can flash fastboot roms only on unlocked devices. But you can't unlock it now in this state...
Click to expand...
Click to collapse
It's very weird, I've been flashing lots of stuff in the past but I've never been locked out like this.
And the joke is that the black Mi logo screen still says "unlocked" as it should be... no idea, maybe it is programmed to just give up after some years.

Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.

Indie Zex said:
Could be that your TWRP recovery is corrupted. You can install new one from a fastboot mode:
1. Copy latest twrp-3.5.2_9-0-gemini.img to your fastboot tools location on PC
2. Put the phone in fastboot mode (power + volume down) and connect it to the computer
3. Enter these commands in cmd prompt:
fastboot flash recovery twrp-3.5.2_9-0-gemini.img
fastboot boot twrp-3.5.2_9-0-gemini.img
Then the phone will boot into new TWRP so you can check if it's ok.
Click to expand...
Click to collapse
I tried that, it gives the following error:
I noticed that even from MiFlash the device id sometimes disappears, not sure if that's the no link error

I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)

Indie Zex said:
I really don't know what's going on. Maybe you can try this tutorial (it is for Mi 9, but can be applied to all Mi phones)
Click to expand...
Click to collapse
Thanks for trying I really appreciate. I did follow the tutorial, same error.
It's like the internal storage got fried or something? I have no clue

Question help - qualcomm crash dump

Hi,
had a rooted 2213 OP10 Pro.
Tried to update it to the latest C26 update locally. after it extracted, just rebooted without permission and I lost root.
opened magisk and there no option to inactive slot after ota.
booted into fastboot and flashed magisk patched boot. when it booted, opened magisk and there an option to write to inactive slot. did it.
after that, the phone is in qualcoom crash dump mode.
Can I recover it somehow ? what should i don next ?
please any advice, this is my work phone.

Lior84 said:
Hi,
had a rooted 2213 OP10 Pro.
Tried to update it to the latest C26 update locally. after it extracted, just rebooted without permission and I lost root.
opened magisk and there no option to inactive slot after ota.
booted into fastboot and flashed magisk patched boot. when it booted, opened magisk and there an option to write to inactive slot. did it.
after that, the phone is in qualcoom crash dump mode.
Can I recover it somehow ? what should i don next ?
please any advice, this is my work phone.
Click to expand...
Click to collapse
Can you go into bootloader mode?

TheNewHEROBRINE said:
Can you go into bootloader mode?
Click to expand...
Click to collapse
yes

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is probably the cause of the issue. Magisk switched your active slot to the previous one which becomes unbootable after the update completes successfully. You should be able to switch back to your working slot by doing fastboot --set-active=other, although I'm not 100% sure this is right solution I think it's a reasonable one. I'm always a bit scared suggesting solutions to people who have a recent OnePlus phone since they can't unbrick it if they end up in a hard brick.

TheNewHEROBRINE said:
View attachment 5847335
This is probably the cause of the issue. Magisk switched your active slot to the previous one which becomes unbootable after the update completes successfully. You should be able to switch back to your working slot by doing fastboot --set-active=other, although I'm not 100% sure this is right solution I think it's a reasonable one. I'm always a bit scared suggesting solutions to people who have a recent OnePlus phone since they can't unbrick it if they end up in a hard brick.
Click to expand...
Click to collapse
did't understood the command that you suggested.
did copy paste to it and it says unrecognized option

Lior84 said:
did't understood the command that you suggested.
did copy paste to it and it says unrecognized option
Click to expand...
Click to collapse
Is your phone in bootloader mode and recognized by fastboot? Can you send a screenshot of the command + error?

TheNewHEROBRINE said:
Is your phone in bootloader mode and recognized by fastboot? Can you send a screenshot of the command + error?
Click to expand...
Click to collapse
ok, opened updated platofrm tools and did what you said...
it's worked !!!
now is the only problem that I have no root
How I bring it back ? my version is NE2213_11_c.26

Lior84 said:
ok, opened updated platofrm tools and did what you said...
it's worked !!!
now is the only problem that I have no root
Click to expand...
Click to collapse
Boot the Magisk patched boot.img (don't flash it!). Then go into Magisk and do a direct install (DON'T do install to inactive slot). Then reboot and check if root is still there.

TheNewHEROBRINE said:
Boot the Magisk patched boot.img (don't flash it!). Then go into Magisk and do a direct install (DON'T do install to inactive slot). Then reboot and check if root is still there.
Click to expand...
Click to collapse
where to get it ? or how to make it ?

Lior84 said:
booted into fastboot and flashed magisk patched boot.
Click to expand...
Click to collapse
You can use the one you already have, you just need to do fastboot boot magisk_patched.img (or whatever it's called) instead of fastboot flash.

TheNewHEROBRINE said:
You can use the one you already have, you just need to do fastboot boot magisk_patched.img (or whatever it's called) instead of fastboot flash.
Click to expand...
Click to collapse
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)

Lior84 said:
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)
Click to expand...
Click to collapse
Are you sure you're in bootloader mode and not fastbootd?

Lior84 said:
i did this. it sending it and succeeded. then says boot failed ( remote unrecognized command)
Click to expand...
Click to collapse
adb reboot fastboot reboots you to fastbootd, not bootloader mode! You need to do adb reboot bootloader.

TheNewHEROBRINE said:
adb reboot fastboot reboots you to fastbootd, not bootloader mode! You need to do adb reboot bootloader.
Click to expand...
Click to collapse
OK, finally everything worked. I'm a little bit rusty (my first android was HTC desire back in 2010).
Thank you very much, You really saved me a lot of time and frustration !!! I already started to think how to get all the data back.
I really appreciate your help !!!
THank you again.
Lior

You're welcome!