Database Develop

[Brick] Xiaomi Mi5 64GB (Locked BL, No EDL, No Recovery)

OK here is my problem,
I got a brand new Xiaomi Mi5 64GB and the first thing that I did was to connect it with Mi PC Suite to check for updates.
It found an update and started to update until it failed, after that the device couldn't normal boot or recovery boot (Vol+ and POWER went to a black screen with "mi logo" same as normal boot).
View attachment 3788573
I can only boot on fastboot mode, but can't do anything in the fastboot as BL is locked.
Official BL unlocking method can't work as device isn't linked to any Mi Account and MiFlashUnlock can't verify my device.
{
"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"
}
So my questions is, can I someway repair my phone with QPST or would you suggest another solution?

en.miui.com/thread-291785-1-1.html

wissou050987 said:
en.miui.com/thread-291785-1-1.html
Click to expand...
Click to collapse
in this guide have to boot into recovery, i CANT boot into recovery, got no recovery.

you have to flash with miflash tool booting into fastboot then

wissou050987 said:
you have to flash with miflash tool booting into fastboot then
Click to expand...
Click to collapse
MiFlash cant flash anything as bootloader is locked.

Try: http://en.miui.com/thread-291785-1-1.html
It works fine

tiflao said:
Try: http://en.miui.com/thread-291785-1-1.html
It works fine
Click to expand...
Click to collapse
Read OP again please.
1. I CAN'T boot into recovery.
2. I CAN'T boot EDL.
3. I CAN boot just into Fastboot, but Bootloader is Locked.
4. I CAN'T unlock BL via official methode as there is no linked Mi Account on Device.
I think that i need a hardware way to unlock BL.

Have you tried this method to see if it works?
http://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292

VirusPlus said:
Read OP again please.
1. I CAN'T boot into recovery.
2. I CAN'T boot EDL.
3. I CAN boot just into Fastboot, but Bootloader is Locked.
4. I CAN'T unlock BL via official methode as there is no linked Mi Account on Device.
I think that i need a hardware way to unlock BL.
Click to expand...
Click to collapse
You CAN boot into recovery, don't be silly. Have you read the instructions?
Hold volume up and power button and a MI logo should came up, that's the recovery.

abyssq said:
You CAN boot into recovery, don't be silly. Have you read the instructions?
Hold volume up and power button and a MI logo should came up, that's the recovery.
Click to expand...
Click to collapse
Recovery was a black screen with a white phone, not "mi".
Phone is not detectable anyway if i normally or vol+ boot.
Im not a noob i know what recovery is, so i need answers with the facts that i mention before, no recovery, no edl, unlockable bl.
Im gonna send it to repair shop anyway but still my situation is a big problem that xiaomi should look into it. I get bricked via official update tool, and i cant unlock bl cause xiaomi's unlocking tool stupidly requires linked mi account on device to verify.

When you boot into fastboot and update in mipc suite, it doesn't work ?
I don't understand why official tool need unlock bootloader, it's insane from Xiaomi

rcd1030 said:
When you boot into fastboot and update in mipc suite, it doesn't work ?
I don't understand why official tool need unlock bootloader, it's insane from Xiaomi
Click to expand...
Click to collapse
Mi PC Suite doesn't recognize device in fastboot mode, it returns a screen to connect in normal mode first.
Only MiFlash can see the device in fastboot but it needs unlocked BL to flash the Official fastboot ROMs. Madness!

Aarff just, you're right
Just speculation but maybe can you reboot in recovery with adb commands ? (adb reboot recovery)

Or maybe download twrp, run shell from where it is saved and run
Code:
fastboot boot twrp.img[
?

VirusPlus said:
Recovery was a black screen with a white phone, not "mi".
Phone is not detectable anyway if i normally or vol+ boot.
Im not a noob i know what recovery is, so i need answers with the facts that i mention before, no recovery, no edl, unlockable bl.
Im gonna send it to repair shop anyway but still my situation is a big problem that xiaomi should look into it. I get bricked via official update tool, and i cant unlock bl cause xiaomi's unlocking tool stupidly requires linked mi account on device to verify.
Click to expand...
Click to collapse
Oh yes sorry, it's a phone, my bad.
Then the recovery works fine for you, just the PC doesn't recognise it, which is driver or windows problem, not your phone.
SpinoRex: Fastboot doesn't work because of the locked bootloader. Only option is the official recovery with chinese mi pc suite.

check this post : en.miui. com/thread-299790-1-1.html
You need Engineering Flash Cable

They are in the same situation ... solved?

Mi suite in chinese
You may try to use MI SUITE in Chinese. I was in your exact situation trying to remove a fake rom from my MI5, but with this I solved all the issues.
Just one advice: don't use a pre-loaded ROM, let the program to download it from the internet.

you can boot your device into edl mode with a special fastboot
just type "fastboot reboot" to go to the Edl mode and flash rom with miFlash

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

Sony Xperia XA2 - Flashing TWRP stuck on "waiting for any device"

HELP!
I installed platform-tools_r33.0.2-windows and UniversalAdbDriverSetup, now i'm trying to flash TWRP on the XA2 Phone by using this cmd command:
adb devices
- daemon not running, starting now at xxx
adb flash recovery twrp.img
- waiting for any device
What am i doing wrong?? Please help!!
{
"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"
}

Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"

LR7875 said:
Boot phone in fastboot mode
Execute "fastboot flash recovery twrp.img"
Click to expand...
Click to collapse
How? Im pressing volume up and then connecting the phone to the pc, then i see a blue light. Is this fastboot mode? Thats what im already doing for 3 hours...

Yeah just did it again... volumeup+connect phone to pc, blue light appears on phone (fastboot mode i asume).
on pc in cmd i type adb devices, it starts the daemon.
then i type "fasboot flash recovery twrp.img"
result in cmd: "waiting for any device"
Wtf?

I swear this is so cancer can't handle this ****, the F is wrong with sony? This phone is buggy AF im trying to insall TWRP for like 4 hours now, this is a ****ing joke. What a waste of time.

Try the 15 seconds adb and fastboot driver if you haven't already

LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
This? https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
I doubt it will be any different from the platformtools adb? How could this help?

LR7875 said:
Try the 15 seconds adb and fastboot driver if you haven't already
Click to expand...
Click to collapse
You mean minimal adb ? or can you provide a link?

Connect the phone in fastboot mode (LED = blue) and open the device manager. Do you see the phone under "Other Devices" or "Android" with an exclamation mark? Then you need an ADB/bootloader interface driver. Get this for example:
https://developer.sony.com/file/download/xperia-xz2-driver/
(Yes, XZ2! There is no official XA2 driver)
Unzip it somewhere and force install the driver:
Right click on the device manager entry from above, "Update driver", "Browse my computer...", "Let me pick...", "List/show all...", "Have disk...", browse to the folder from above, open the selected .inf file and install.
Fastboot should work now. At least that's how I got it to work on a new PC.
BTW, just use "fastboot devices" to check whether it works. If your device doesn't appear, you don't need to try other fastboot commands - it won't work.

I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9

Carljaynp03 said:
I have this problem, when installing twrp to my Sony Xperia XA2 (H3123), I am trying to install several versions of Twrp, for example: twrp-3.2.2-0-pioneer.img, twrp-3.7.0_9-0 -pioneer.img, my Sony is on Android 9
Click to expand...
Click to collapse

Did you unlock the bootloader ?

Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
I agree with faraway, if i remember correctly when i had this issue i didn't unlock the bootloader.
I typed a specific number in the phone dial app and it said that the bootloader is unlocked, however there is another step you need to take that i had overlooked, you need a bootloader unlock code.
The code is free, not like with chinese spyware huawai they want your money for the code...
Unlock Bootloader - Open Devices - Sony Developer World
developer.sony.com
https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-4
and use one of these commands in cmd/adb
fastboot flashing unlock
fastboot oem unlock

Carljaynp03 said:
View attachment 5734133
Click to expand...
Click to collapse
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.

irgendwer2 said:
What is your end goal? To flash a custom ROM like LineageOS? Then you can temporarily flash a recovery image to the boot partition:
fastboot flash boot <recovery_filename>.img
You don't really need TWRP for this, just use the latest official LOS Recovery:
https://download.lineageos.org/pioneer
Also see: https://wiki.lineageos.org/devices/pioneer/install
Or do you want to "permanently" install TWRP on an existing system? Then you need to directly boot into TWRP and install it from its GUI:
fastboot boot <twrp_filename>.img
See: https://twrp.me/sony/sonyxperiaxa2.html
I haven't tried the latter on the XA2 yet though and don't know how permanent that installation really is. It maybe gone after an OTA update.
Click to expand...
Click to collapse
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.

Privacydroid said:
Booting a temprary image did not work when i tried it, most likely because the bootloader wasn't unlock.
Click to expand...
Click to collapse
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.

irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
follow the next steps you mentioned use: fastboot flash boot recovery from LineageOS, and my phone went into a constant boot shutdown and restart, then this message appeared

and the bootloader is open

Shutdown the phone after flashing the recovery image (it doesn't seem like you did that). Then hold Volume Down + Power to boot into recovery.

irgendwer2 said:
Independent from the bootloader status: you can't flash an image directly to the recovery partition on the XA2/Pioneer (like he tried, see screenshot) because such a dedicated partition doesn't exist on this and other A/B devices. Instead the recovery is built into the boot image.
That's why you have to use fastboot flash boot instead of recovery.
Click to expand...
Click to collapse
I get that the recovery is only for a temporary boot, when i tried it, it didn't work but i can't remember what the error was.

Question Oneplus 10 Pro stuck in Bootloop

So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
{
"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"
}

biglo said:
So I restarted my phone today and it just entered an infinite boot loop. Not sure what happened but that's all it's doing whenever I turn it on. I can enter the bootloader but other than that nothing is working. I noticed the bootloader and baseband are empty as well.
I wish this phone had an unbrick tool like the oneplus 7 devices but I don't know. I guess I may just have a brick until someone shakes.
View attachment 5694575
Click to expand...
Click to collapse
Are you rooted? Can you get in recovery? What model number?

twinnfamous said:
Are you rooted? Can you get in recovery? What model number?
Click to expand...
Click to collapse
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.

biglo said:
Was rooted, can get to recovery using the enhanced flash tool and model is 2210.
Click to expand...
Click to collapse
Have you tried flashing stock boot.img or factory resetting?

twinnfamous said:
Have you tried flashing stock boot.img or factory resetting?
Click to expand...
Click to collapse
Yes, I tried both options without success.

biglo said:
Yes, I tried both options without success.
Click to expand...
Click to collapse
That's not good usually one or the other fixes it. Only thing I can think of is flashing all images in fastboot. But try vendor_boot first

When this happened to me on my OP6 when I had it and when I couldn't recover it with MSM tools or boot.img, I decided it is motherboard failure.
But I would try fastboot ROM if I were you. If it doesn't help, I will send it to the service center.

You may have booted a patched yet not made it permanent so when you rebooted you lost it.
If that rings a bell then just boot a patched boot image. Not flash.. once you're booted and in the system just open magisk and click direct install..
Reboot and it should be permanent.
Beyond that you can go to recovery or fastboot to get back in business although you'll lose your data

My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b

unsafe8989 said:
My phone did this once when I accidentally changed A/B partition, try switching partition via fastboot
Do the following
fastboot getvar all
then you'll get somewhere the following
(bootloader) current-slot:A or B
then you should be able to do either
fastboot set_active other
or either
fastboot set_active a
fastboot set_active b
Click to expand...
Click to collapse
I tried switching slots the other day, it gave me the same results.

hello did you found any solutions?

biglo said:
I tried switching slots the other day, it gave me the same results.
Click to expand...
Click to collapse
That means you have no boot img on it

try to flash a boot img to slot a and slot b

Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.

dladz said:
Is this still ongoing?? Lol that's insanity.
The reason you cannot boot is 100% your boot image.
So either boot or flash a boot image (stock or patched)
If you'd like to reflash your whole phone then click on vol up and then recovery.
If you're looking for a tool then grab fastboot enhance, whilst in fastboot use it to remove the cow files, search for them, once that's done, flash a payload.bin and this will reload your whole OS.
There are guides for everything I've mentioned above, just search.
Click to expand...
Click to collapse
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.

*-MaCK-* said:
Hi,
I have the same problem. Never used the phone. Just to install Magisk and edit the payload.bin file. When I installed the new boot file via Fastboot it went wrong.
Tried everything but can't get the phone out of the loop. I don't have a recovery function!
You indicate that there are manuals for existing solutions everywhere. Do you have the links for me? Not very good at finding this.
Click to expand...
Click to collapse
Doesn't help that the forums went through a crap update that broke the sections.
That being said, you're looking for a guide so that's your key word.
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com
There's a good few of them, the screen shot is taken from the main OnePlus 10 pro forum section, I can see two. Mine and the 2215 one.
Also when you say 'installed' I hope you meant boot and not flash, booting is risk free.. Read my thread and it'll make sense.

I wish people would read more...cause it all here...just need to take the time and read alot of post...to find what they are looking for...lol

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!