Database Develop

how to flash NEXUS 6 XT1103 ROM, BOOTLOADER LOCKED, CAN'T GET INTO PHONE, PLEASE HELP

PROBLEM -
I can not get into phone settings or ANYTHING ELSE because it keep SHOWING this error and LOADS NO OS or any icon THING AFTER BOOT
{
"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"
}
I tried from adb and it didn't work :-
<<< C:\adb>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
- I have downloaded rom from google for my phone model
- I can not ENABLE OEM unlock because I can not get into phone.
- I have tried wiping CACHE AND FACTORY RESET from recovery but it does not LOAD anything after boot and shows error I posted in image above.

lol!
first off, you posted in the wrong nexus 6 forums, as you arent developing anything(besides a headache). secondly, adb and fastboot are different. fastboot is not an adb command! fastboot is a different tool, like adb but different, and you can only use fastboot while you are in the bootloader. secondly, go back for a little and do a little more reading please, then try again.
edit.. good, this thread got moved to the right place.

"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?

Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/

dahawthorne said:
"Administr4tor, Account currently disabled on Today, 20:48"
Interesting. Why? Is this thread dead now?
Click to expand...
Click to collapse
no, its not dead though I was dead for couple days.

Administr4tor said:
Looks like there is no way to reinstall rom again.
what I am trying to say here is
- I can not get into phone
- I can not enable USB DEBUGGING
- I CAN NOT enable OEM UNLOCK.
tell me yes or no if I can reinstall factory image. is it not simple/
Click to expand...
Click to collapse
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.

thatkindaguy said:
You're trying to unlock the bootloader, which requires fastboot, using ADB. Do you have fastboot drivers installed? Or you could just unlock the boot loader with nexus root toolkit.
Click to expand...
Click to collapse
Thank you for reply,
- I have adb and fastboot drivers installed from xda when I connect the phone it shows connected, Please check the screenshot.
- I just want to flash stock rom, even if its possible to do it without unlocking bootloader, please let me know.
_ i have already tried NEXUS TOOLKIT and tried to unlock bootloader but it failed to unlock it.
Regards

You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?

geokhentix said:
You can't install a factory image without a locked bootloader. What did you do to make settings force close on boot?
Click to expand...
Click to collapse
oh, I didn't do anything, I wokeup and charged it after it went dead, and it all happened,
also sometimes I get this error too if I am not getting those "unfortunate error"

Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue

Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.

vicks1008 said:
Tried that.
Verifying update package. . .
E: failed to verify whole-file signature
E: signature verification failed
Restarting adbd. . .
Installation aborted.
Click to expand...
Click to collapse
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example

Vivjen said:
Sure. You have no possibility to push current version installed as OTA update. Try to push beta Android N for example
Click to expand...
Click to collapse
My Nexus 6 is stuck at LMY48M & I tried pushing the latest Marshmallow OTA build MMB29X.

You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?

Why is your Nexus reported in Device Manager as a Samsung device? As someone who owns a Galaxy S4 as well as a Nexus, you cannot use the Samsung driver in place of the Nexus USB driver.
Change your driver to the Google-provided version and try again.

Vivjen said:
You need to flash OTA with newer bootloader. Not each OTA contain newer version. Anything else will not help. Have you tried to push N?
Click to expand...
Click to collapse
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.

Nexus root toolkit
this toolkit will do all the work for you. from wugfresh development

vicks1008 said:
I can't even sign up for the Nexus Beta Program. I have to sign up from the Nexus 6.
Click to expand...
Click to collapse
No. Just download OTA from PC and push it to N6 via adb sideload

joseppa87 said:
this toolkit will do all the work for you. from wugfresh development
Click to expand...
Click to collapse
Absolutely. It washed my dishes, took the dog for a walk, and helped me with my homework.

Vivjen said:
Push OTA. It works with locked bootloader. Recovered N6 from the same state (Your device is corrupt. Visit g.co/ABH), but now I have FRP issue
Click to expand...
Click to collapse
sIR, How did you push STOCK OTA and where did you get it from, Can you please tell me steps you followed in details?
Thank you for reading.

my problem

hi
my problem is
I tried to downgrade my phone
android 6 to 5
My phone was incomplete downgrade
And now when turned off and turned on
Stuck on the
{
"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"
}
Please tell me what is the alternative
No option is not enabled
no recovery
no Emergency Updates
only fastboot mod

the fastboot mode is worked

rezaghaedamini said:
the fastboot mode is worked
Click to expand...
Click to collapse
Take it to Huawei customer service center. I lost one of my phones coz it had the same problem. Tried everything but couldn't revive it.
Took it to a shop to repair and he messed it up.

Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.

Krish93 said:
Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.
Click to expand...
Click to collapse
My bad, should have asked him to do this first. Mine was error 3 and wasn't revivable.
This error is different. Thanks for the help.

You need to unlock your device.
https://www.gizdev.com/install-twrp-3-0-root-honor-4x-emui-4-0/
1-unlock your device
2-run bootloader
3-install twrp
4-extract the honor firmware
http://forum.xda-developers.com/honor-4x/how-to/roll-to-emui-cm13-honor-4x-che1-l04-t3507998
5-follow the instructions as above link.

Krish93 said:
Connect to pc or laptop and open command prompt to adb folder and type fastboot devices if devices detected then we proceed http://forum.xda-developers.com/general/general/guide-flash-variant-version-firmware-t3506404.
Click to expand...
Click to collapse
i did
My phone did not change

dopserver said:
You need to unlock your device.
https://www.gizdev.com/install-twrp-3-0-root-honor-4x-emui-4-0/
1-unlock your device
2-run bootloader
3-install twrp
4-extract the honor firmware
http://forum.xda-developers.com/honor-4x/how-to/roll-to-emui-cm13-honor-4x-che1-l04-t3507998
5-follow the instructions as above link.
Click to expand...
Click to collapse
my phone is unlocked
and All these things did
Did not alter

rezaghaedamini said:
my phone is unlocked
and All these things did
Did not alter
Click to expand...
Click to collapse
Connect your phone to PC and keep device manager opened and see if device manager registers your phone.
Report back please...

muradulislam said:
Connect your phone to PC and keep device manager opened and see if device manager registers your phone.
Report back please...
Click to expand...
Click to collapse
MY English is not good please tell me What do you mean
device manager to phone
or to pc

rezaghaedamini said:
MY English is not good please tell me What do you mean
device manager to phone
or to pc
Click to expand...
Click to collapse
Keep your PC device manager open and connect your phone to PC, does it register as a new device...

not big deal ,
Do The following
Install Fastboot files .
Download TWRP .
Connect Ur Device with Fastboot ,
Flash Ur TWRP Throw Fastboot .
Boot To TWRP
FLASH STOCK img Files One By one
This Step Not Recommended but also :
Throw Fast-boot Flash UR Stock .img files .

Romiui said:
not big deal ,
Do The following
Install Fastboot files .
Download TWRP .
Connect Ur Device with Fastboot ,
Flash Ur TWRP Throw Fastboot .
Boot To TWRP
FLASH STOCK img Files One By one
This Step Not Recommended but also :
Throw Fast-boot Flash UR Stock .img files .
Click to expand...
Click to collapse
tnk not work

rezaghaedamini said:
tnk not work
Click to expand...
Click to collapse
it should otherwise there is an wrong step u did ! .

rezaghaedamini said:
tnk not work
Click to expand...
Click to collapse
If your PC does not make a sound when you connect your phone to it then you have to first install drivers.
I am sure that is the case here, your PC is not recognizing your phone.

muradulislam said:
If your PC does not make a sound when you connect your phone to it then you have to first install drivers.
I am sure that is the case here, your PC is not recognizing your phone.
Click to expand...
Click to collapse
I have installed drivers
And when I connect the phone to the sound system
Only through the Fast Boot

rezaghaedamini said:
I have installed drivers
And when I connect the phone to the sound system
Only through the Fast Boot
Click to expand...
Click to collapse
So fastboot is working... Do you have an unlocked bootloader?
Fastboot screen is simple or with red error message?

muradulislam said:
So fastboot is working... Do you have an unlocked bootloader?
Fastboot screen is simple or with red error message?
Click to expand...
Click to collapse
yes i am bootloader unlocked
Both options
Red and simple
i can Write files via Fast Boot
and write android 4 5 6
5 file
boot
system
recovery
cust
userdata
and not work
and write twrp recovery
and not work

rezaghaedamini said:
yes i am bootloader unlocked
Both options
Red and simple
i can Write files via Fast Boot
and write android 4 5 6
5 file
boot
system
recovery
cust
userdata
and not work
and write twrp recovery
and not work
Click to expand...
Click to collapse
Make a dload folder in SD card And copy update.app of the latest firmware to it.
Then, flash only recovery and boot of the latest firmware for your phone. (Extracted from update.app which you copied to SD)
After flashing above image files, type
Fastboot reboot
Quickly disconnect from pc and press and hold power + vol up + vol down until screen turns on. Let go of power but keep other two pressed for five, six sec more.
Lemme know how it works.

if stock wont work then try custom rom , install custom recovery and install custom rom .

Bricked Mi 8

Hello and sorry for new thread if this was already discussed.
I have Chinese Mi 8 with Global unlocked ROM.
I tried to flash Chinese developer ROM on it in hopes of locking bootloader.
Flash started but in status I see
|| echo Mismatching image and device
Click to expand...
Click to collapse
I let it run for 30 minutes but nothing was happening
Then I decided to flash back my Global ROM but every time I hit refresh in MiFlash it looked like phone disconnected from PC and instead of Fastboot on screen I only saw "Press any key to shutdown" in top left corner.
MiFlash would recognize the phone if I restarted back to Fastboot but same problem - || echo Mismatching image and device
THis happens on both Chinese and Global versions now, it acts like it's flashing but I do not see any progress.
I also tried to remove these lines
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || exit /B 1
Click to expand...
Click to collapse
from .bat files as some users suggested but it just got stuck on "fastboot %* erase boot" and not move further
any suggestions how to unbrick my phone?
{
"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"
}
EDIT: tried to flash TWRP Recovery into my phone, it gets recognized as connected but when I try to load .img I get only "< waiting for device >"

Your bootloader is unlocked?

:crying:

DimitrisVerlis said:
Your bootloader is unlocked?
Click to expand...
Click to collapse
as I mentioned, yes
from what I can tell it seems Fastboot is not working properly.
I get the logo and I get audible signal from Windows upon connecting the phone but when I try to do anything with it via MiFlash or install TWRP either nothing happens or phone just reboots

try with miui flash tool downgrade firmware

Hi flash in edl mode
Hi You have to flash the fastboot rom (Chinese/global) starting with test point method. (EDL method). You can google how to do. Suggest take it to authorized center as it involves opening the phone and connecting through EDL method. Otherwise If you can find somebody who can do this , then you can do - but still will ask for authentication code - while flashing. You can get the same with s-unlock.com for a charge...

dorello said:
try with miui flash tool downgrade firmware
Click to expand...
Click to collapse
you mean XiaoMiTool? same behaviour as MiFlash - device detected, when I try to send command to it it disconnects and XiaoMiTool says to allow usb debugging which is not possible
same issue was reported here
https://forum.xda-developers.com/redmi-note-5-pro/help/help-press-key-to-shutdown-fastboot-t3816021
so I tried using different USB 2.0 port and even installed Windows 7 virtual machine to try it in Win 7 - same result

change usb port to 2.0 and try flash again in fastboot mode

santycs31 said:
Hi You have to flash the fastboot rom (Chinese/global) starting with test point method. (EDL method). You can google how to do. Suggest take it to authorized center as it involves opening the phone and connecting through EDL method. Otherwise If you can find somebody who can do this , then you can do - but still will ask for authentication code - while flashing. You can get the same with s-unlock.com for a charge...
Click to expand...
Click to collapse
that's what I was afraid of - I'll probably have to do that/get it done
change usb port to 2.0 and try flash again in fastboot mode
Click to expand...
Click to collapse
tried this, didn't change anything but thanks for suggestion

djpsycho666 said:
well if you need edl authorized account to flash,you can pm me
Click to expand...
Click to collapse
thank you! I will sure contact you once I do my research and have everything I need.

Ask for help someone who has better knowledge about computers. You must change drivers manually at device manager. Watch some videos on YouTube how to do it. Connect your phone in fastboot mode any check device manager. It's not allowed any exclamation mark at the ADB device

mar.ur said:
Ask for help someone who has better knowledge about computers. You must change drivers manually at device manager. Watch some videos on YouTube how to do it. Connect your phone in fastboot mode any check device manager. It's not allowed any exclamation mark at the ADB device
Click to expand...
Click to collapse
I'm not complete computer noob, I tried several different drivers I could find online and I get always same behaviour
this is current driver:
https://pasteboard.co/IEPolh4.png
at this point I will try installing Linux and test it there
if this won't work then EDL it is

Give more informations
What version of miflash?
Did you use proper fastboot_rom.tgz?
Did you unpack it directly to c:?
What is inside an unpacked folder?

mar.ur said:
Give more informations
What version of miflash?
Did you use proper fastboot_rom.tgz?
Did you unpack it directly to c:?
What is inside an unpacked folder?
Click to expand...
Click to collapse
MiFlash v2018.5.28.0 but also tried older versions as well as XiaoMiTool
Tried latest available Fastboot ROMs:
CN developer dipper_images_9.8.22_20190822.0000.00_9.0_cn_acf57fcb3b
CN stable dipper_images_V11.0.3.0.PEACNXM_20190929.0000.00_9.0_cn
Global dipper_global_images_V10.3.5.0.PEAMIXM_20190912.0000.00_9.0_global
I've unpacked and installed it from my Desktop and Documents folder
This is inside unpacked folder of all 3 versions
https://imgur.com/zywnpM7

All look good. Do you have Ryzen?

mar.ur said:
All look good. Do you have Ryzen?
Click to expand...
Click to collapse
Yes, 1st Gen

marcos49 said:
Yes, 1st Gen
Click to expand...
Click to collapse
Ohh, there are some issues with fastboot mode and Ryzen. Try to another PC with Intel and I sure you will be able to flash rom with miflash. You don't need edl method.

mar.ur said:
Ohh, there are some issues with fastboot mode and Ryzen. Try to another PC with Intel and I sure you will be able to flash rom with miflash. You don't need edl method.
Click to expand...
Click to collapse
thanks for info
will have to ask some friends for help as I only have systems with Ryzen(1st and 3rd Gen)
I'll try over next week and update if I'm successfull or not.

So I just tried to flash from Intel system and guess what?
IT WORKED - well, partially
After all the trouble I wanted to just flash Global ROM but that kept failing(too many links) after various amount of time
So I tried Chinese developer ROM and that one worked
Took a while to understand what it asks from me in Chinese but it was just my account password
So for now I'll keep this ROM, see what's the difference, what I cannot use, try to unlock bootloader officially and then flash Global ROM(if possible)
Thanks all for your help!

A friend had the same problem with ryzen CPU, we tried on my intel laptop and everything works okay!

General [Camellia/Camellian/Any other MTK devices] Bootloader Unlock Exploit Tool

[READ BEFORE USE]
1st Disclaimer: This tool is exploring a known security flaw to unlock the device. THEREFORE IT IS NOT CONSIDERED SAFE TO USE, IF YOU USE IT, YOU'RE DOING AT YOUR OWN RISK. Nor me or the tool's creator are responsible for what you do with this tool or it's consequences. Your warranty is null and void.
You've been warned.
Click to expand...
Click to collapse
2nd Disclaimer: I'm not this tool's creator. All credits goes to them, I'm just posting it here for convenience.
Click to expand...
Click to collapse
We usually have to wait 7 days to unlock the bootloader of Xiaomi devices, right? Well, with this tool, you can cut off that timer on MTK devices, such as Poco M3 Pro/Redmi Note 10 5G.
How to Use:
1st: Download and unpack the 7zip file.
2nd: Install the drivers inside, both mtk drivers AND USB DK (x86 for 32-bit OS and x64 for 64-bit OS)
3rd: Reboot PC and turn off the device to be unlocked.
4th: Run UnlockBootloader.bat, it'll keep attempting to link, that's normal
5th: Connect your device. Either on pre-loader mode (completely off) or BROM mode (Hold Vol- while connecting the cable)
6th: Upon estabilishing a successful link, the tool will unlock your phone.
And voila, quick-unlocked.
In case of dm-verity corruption, just do this:
fastboot reboot fastboot
fastboot --disable-verity --disable-verification flash vbmeta_a [insert the vbmeta's path here]\vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b [insert the vbmeta's path here]\vbmeta.img
Click to expand...
Click to collapse

Unlock bootloader.bat is just opens and closes immediately....anything I'm missing here ?

nanchilanto said:
Unlock bootloader.bat is just opens and closes immediately....anything I'm missing here ?
Click to expand...
Click to collapse
Have you installed usbdk for your PC?

Gio1906 said:
Have you installed usbdk for your PC?
Click to expand...
Click to collapse
Yep , I installed the drivers , restarted the laptop. Tat unlock.bat is just opening and closing.

nanchilanto said:
Yep , I installed the drivers , restarted the laptop. Tat unlock.bat is just opening and closing.
Click to expand...
Click to collapse
Phyton installed as well?

Gio1906 said:
Phyton installed as well?
Click to expand...
Click to collapse
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it

Hi, I' ve just tested it now and here what I have :
{
"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"
}
Anyone know how to solve that ?
Thank in advance

asen26 said:
Hi, I' ve just tested it now and here what I have :
View attachment 5624033
Anyone know how to solve that ?
Thank in advance
Click to expand...
Click to collapse
I should have added: Phyton is needed as well.

nanchilanto said:
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it
Click to expand...
Click to collapse
As for you, I forgot to reply, my apologies... So, let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?

nanchilanto said:
Yep I tried tat too.... But no luck , anyways thanks mate. I appreciate it
Click to expand...
Click to collapse
As for you, I forgot to reply, my apologies... let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?

Gio1906 said:
As for you, I forgot to reply, my apologies... let's recap: mtk drivers, usbdk, phyton... I suppose libusb libraries and device hook are installed as well, right?
Click to expand...
Click to collapse
Everything installed , i read another article about unblocking mtk devices and followed the detailed steps by installing python etc.. Problem from my side is tat .bat file just opens and closes it's not stable at all... Anyways thanks again I have already unblocked my device through miui unlock ..

How to unlock Mediatek bootloader using mtkclient
This guide will explain how to unlock a Mediatek device's bootloader using MTKclient. This will come in handy for those who can't unlock bootloader using fastboot . This was tested on the LG K51 Warni
www.hovatek.com

wetito said:
How to unlock Mediatek bootloader using mtkclient
This guide will explain how to unlock a Mediatek device's bootloader using MTKclient. This will come in handy for those who can't unlock bootloader using fastboot . This was tested on the LG K51 Warni
www.hovatek.com
Click to expand...
Click to collapse
MY HERO!!! thank you so much!!!!

Here, i also using this tools when unlock or locked back bootloader

Hi everyone, so is it possible to unlock the bootleader without ereasing personal data using this method?

Yes, no need erase personal data.

But i see in the guide linked by @wetito that one of the steps is
python mtk e metadata,userdata,md_udc
Isn't this going to delete user data? Can i just skip thiis step?

use the tools I pinned above.

Saracawalk said:
Here, i also using this tools when unlock or locked back bootloader
Click to expand...
Click to collapse
Requirements :
• pc/laptop
• Windows 10/11 (8/8.1 possible but not tested) 64bit
• Internet connection
Material :
• mtkclient-gui + driver (fix all errors)
Steps:
1. Download the material above
2. Extract the driver
3. Go to the extracted driver folder
4. Right click android_winusb.inf and select install, then restart your pc
5. After restarting extract mtclient-gui
6. Go to the extracted folder mtkclient-gui
7. Double click on start.bat
8. turn off the cellphone
9. back to the laptop, select Unlock bootloader
10. Type y, then enter
11. press and hold vol up + vol down (approximately 5 seconds then connect to pc (still hold down the volume button)
12. release if the cellphone has been detected in cmd
13. wait for it to finish

berttest123123 said:
But i see in the guide linked by @wetito that one of the steps is
python mtk e metadata,userdata,md_udc
Isn't this going to delete user data? Can i just skip thiis step?
Click to expand...
Click to collapse
Both the tools I and wetito posted require userdata wipe. Saracawalk's one doesn't require it.

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!