Mi A2 Stuck in Boot loader. How can i fix it? - General Questions and Answers

Hello wonderful xda peeps,
My
-
Mi A2
Running Android 10
xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.5.0.QDIMIXM
is stuck in bootloop, how can I fix it or at least how do extract my files?
Thank you kind regards!

Micklo said:
Hello wonderful xda peeps,
My
-
Mi A2
Running Android 10
xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.5.0.QDIMIXM
is stuck in bootloop, how can I fix it or at least how do extract my files?
Thank you kind regards!
Click to expand...
Click to collapse
What did you do before this happened? Is it your bootloader locked? Can you enter to recovery and/or fastboot?

SubwayChamp said:
What did you do before this happened? Is it your bootloader locked? Can you enter to recovery and/or fastboot?
Click to expand...
Click to collapse
Yes, I can enter Android Recovery and Fastboot.
Yes, the bootloader is locked.
I mistakenly clicked on "Run Graphics Test" in android recovery and it installed some update and my phone has been stuck eversince

Update
I've wiped my phone to factory reset and it is still stuck in bootloop

Micklo said:
Update
I've wiped my phone to factory reset and it is still stuck in bootloop
Click to expand...
Click to collapse
If you have enabled USB debugging and OEM unlock then you can unlock bootloader to get an easy way to send it to EDL mode and you can flash the stock ROM using MiFlash tool.
For future reference this is the first that any user have to do before to "play" with the device so you have more ways to recover it.
There is some probability that your device is trying to boot to the wrong slot, first update your platform-tools if needed https://developer.android.com/studio/releases/platform-tools then see if these commands work:
To identify your current slot type
Code:
fastboot getvar current-slot
then set as active the opposite slot with
Code:
fastboot --set-active=a
changing a for b as opposite slot
Also it exists this tool that can help you but you would need to previously enable USB debugging: https://www.xiaomitool.com/V2/ this tool allows adb (disabled by Xiaomi) to work through recovery stock.
In the case you can't unlock bootloader cause your USB debugging and OEM unlock were not previously toggled then you should have to use MiFlash tool through EDL mode using test point, also there is other tool called QFlash/Qfil.

SubwayChamp said:
If you have enabled USB debugging and OEM unlock then you can unlock bootloader to get an easy way to send it to EDL mode and you can flash the stock ROM using MiFlash tool.
For future reference this is the first that any user have to do before to "play" with the device so you have more ways to recover it.
There is some probability that your device is trying to boot to the wrong slot, first update your platform-tools if needed https://developer.android.com/studio/releases/platform-tools then see if these commands work:
To identify your current slot type
Code:
fastboot getvar current-slot
then set as active the opposite slot with
Code:
fastboot --set-active=a
changing a for b as opposite slot
Also it exists this tool that can help you but you would need to previously enable USB debugging: https://www.xiaomitool.com/V2/ this tool allows adb (disabled by Xiaomi) to work through recovery stock.
In the case you can't unlock bootloader cause your USB debugging and OEM unlock were not previously toggled then you should have to use MiFlash tool through EDL mode using test point, also there is other tool called QFlash/Qfil.
Click to expand...
Click to collapse
Thank you for your kind assistance.
Before it was stuck in boot loop:
- I enabled USB Debugging
- I did not enable OEM Unlocking
Using:
Code:
fastboot getvar current-slot
returned
Code:
current-slot: a
Now running
Code:
./fastboot --set-active=b
i got the following:
Code:
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed

Micklo said:
Thank you for your kind assistance.
Before it was stuck in boot loop:
- I enabled USB Debugging
- I did not enable OEM Unlocking
Using:
Code:
fastboot getvar current-slot
returned
Code:
current-slot: a
Now running
Code:
./fastboot --set-active=b
i got the following:
Code:
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using PowerShell, try to switch firstly to CMD and then type the commands but open it as admin, and check if you have the latest platform-tools.
Also check if the tool provided with link works for you and report back.

SubwayChamp said:
You are using PowerShell, try to switch firstly to CMD and then type the commands but open it as admin, and check if you have the latest platform-tools.
Also, check if the tool provided with link works for you and report back.
Click to expand...
Click to collapse
I am using the correct code because that's how you run the command on Linux or Mac. I'm on a Mac.
The tool did not work for me.
I can't upload an image here

Micklo said:
I am using the correct code because that's how you run the command on Linux or Mac. I'm on a Mac.
The tool did not work for me.
I can't upload an image here
Click to expand...
Click to collapse
I know this is the correct command just I thought you used PowerShell from a Windows some times give errors.
The tool by Francesco Tescari works either through recovery or fastboot so you can try flashing a ROM.
But if for some reason the tool doesn't work your last chance it's either MiFlash tool or Qfil using a Windows machine.

SubwayChamp said:
I know this is the correct command just I thought you used PowerShell from a Windows some times give errors.
The tool by Francesco Tescari works either through recovery or fastboot so you can try flashing a ROM.
But if for some reason the tool doesn't work your last chance it's either MiFlash tool or Qfil using a Windows machine.
Click to expand...
Click to collapse
Thank you for your time and assistance, I eventually got a windows laptop to try it out, I got the Same Error.
I have tried MiFlash tool and I keep getting
Code:
error:"Flash bluetooth_a_error"
or
Code:
error:FAILED (remote: Flashing is not allowed in a Lock State)
I have tried XiaoMiTool V2 and it straight up didn't work.
Let me look up Qfil.

Micklo said:
Thank you for your time and assistance, I eventually got a windows laptop to try it out, I got the Same Error.
I have tried MiFlash tool and I keep getting
Code:
error:"Flash bluetooth_a_error"
or
Code:
error:FAILED (remote: Flashing is not allowed in a Lock State)
I have tried XiaoMiTool V2 and it straight up didn't work.
Let me look up Qfil.
Click to expand...
Click to collapse
It seems you are trying MiFlash tool in fastboot mode but while your device is locked fastboot mode won't work, you have to open the back cover and try test point method to send device to EDL (Emergency Download mode).

SubwayChamp said:
It seems you are trying MiFlash tool in fastboot mode but while your device is locked fastboot mode won't work, you have to open the back cover and try test point method to send device to EDL (Emergency Download mode).
Click to expand...
Click to collapse
Thank you very much, for still staying put.
I just did.
I downloaded the official Mi A2 fast boot ROM from https://bigota.d.miui.com/V11.0.14.....QDIMIXM_20200928.0000.00_10.0_62d0264480.tgz
I entered EDL mode following this guide: youtube.com/watch?v=34Zoevm-Wxc
I flashed it successfully but my phone is still stuck in the boot loop

Micklo said:
Thank you very much, for still staying put.
I just did.
I downloaded the official Mi A2 fast boot ROM from https://bigota.d.miui.com/V11.0.14.....QDIMIXM_20200928.0000.00_10.0_62d0264480.tgz
I entered EDL mode following this guide: youtube.com/watch?v=34Zoevm-Wxc
I flashed it successfully but my phone is still stuck in the boot loop
Click to expand...
Click to collapse
Use this link, there are other ways to unbrick it https://youtu.be/-B_YseC5kLk
Download from the official site linked in the video guide the recovery stock ROM, you can put it in some place in your PC and use the ADB sideload option through recovery to flash it or also you can use an USB OTG. Additionally try with other firmware, taking care to not downgrading it.
And if this doesn't work you should use other Windows version, some users report better results on Windows 7. And keep trying to switch slot.
Edit: before all try if this command work on fastboot mode: https://forum.xda-developers.com/showpost.php?p=75963934&postcount=25

Related

Possible Way to Unlock Bootloader?

I wrote this earlier in the Bounty page for the bootloader unlock, but just so other people can see this as well, here is it in post form! This is the way to unlock bootloader on G3 so if anyone is on lollipop and is rooted, could they try it?
-- STEP 1: Remove LG Download mode (laf)
Important! You’ll need root access to remove (laf), so make sure you’ve rooted before proceeding with the steps below:
Download ADB files:
Prepare your phone:
Enable developer options: Go to your phone’s Settings » select About phone » Scroll to the bottom and tap on “Build number” seven times to enable developer options
Enable USB Debugging: Open phone’s Settings » select Developer options » Tick the “USB debugging” checkbox (under Debugging section)
Connect your phone to PC with a USB cable and if/when a pop-up screen shows up on Phone asking you to ‘Allow USB debugging?‘ for the computer, make sure you tick the checkbox and tap OK
Now type/paste the following ADB commands to backup LG Download Mode (laf), so you can restore it later when necessary
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/sdcard/laf.img
Now run the following command to remove laf and reboot your phone
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
exit
adb reboot
Your phone will now reboot
Now to go into fastboot
adb reboot bootloader
Unlock bootloader!
fastboot oem unlock
or
fastboot flashing unlock
I took this info from original source listed below and made a few changes..
http://forum.xda-developers.com/tmobile-lg-g3/general/how-to-boot-lg-g3-fastboot-mode-t3087445
Good..but there is no fastboot in g flex 2.. Even if there was no fastboot commands would work..
So thats that
adds08 said:
Good..but there is no fastboot in g flex 2.. Even if there was no fastboot commands would work..
So thats that
Click to expand...
Click to collapse
My point is that the G3 also can't go into fastboot until you do this. So I just want people to see if it'll work, cause I'm on Linux and marshmallow so I can't test it. I think the G Flex 2 is more similar to the G3 than the G4 so that's why I'm asking for people to try it out
People already managed to enter fastboot, but no fastboot commands works.
I m going to try it but I need the commands to reflash download mode.
And then how do I know I succeeded?
I mean,with bootloader unlock,is there any way to flash a custom recovery to see if it works?
Pungasul said:
I m going to try it but I need the commands to reflash download mode.
And then how do I know I succeeded?
I mean,with bootloader unlock,is there any way to flash a custom recovery to see if it works?
Click to expand...
Click to collapse
Checking Bootloader Unlock : fastboot oem device-info
reflashing download mode : dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
adds08 said:
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
Click to expand...
Click to collapse
Just out of curiosity, but what commands did you use?
adds08 said:
Aboot fastboot commands are all disabled.. For g3 wasnt it bump tht unlocked the bootloader?
Bt i have already tried nuking the laf and using fastboot commands many months ago..
Click to expand...
Click to collapse
Because the Nexus 6P is known for saying unknown command if you type fastboot oem unlock instead of fastboot flashing unlock
Try it... But dont forget to backup laf in case of failure .. I have done every possible commands new or old
Hi,
I tried this and erased the LAF. Then when you hold "Vol+" and plug-in USB cable you will see "[310] Fastboot mode started".
In Windows device manager I got "Marshall London Bootloader Interface" ... can't remember that I installed any driver but this is the LG G Flex 2.
Unfortunately it seams that there are no fastboot commads are working. I tried this with Android 5.0.1 because this was the only version I got rooted.
So this looks good to me but also it seams an dead end at the moment.
Best regards
CryptMan said:
Hi,
I tried this and erased the LAF. Then when you hold "Vol+" and plug-in USB cable you will see "[310] Fastboot mode started".
In Windows device manager I got "Marshall London Bootloader Interface" ... can't remember that I installed any driver but this is the LG G Flex 2.
Unfortunately it seams that there are no fastboot commads are working. I tried this with Android 5.0.1 because this was the only version I got rooted.
So this looks good to me but also it seams an dead end at the moment.
Best regards
Click to expand...
Click to collapse
i have a 950 that died on me some months ago and now i get Fastboot mode started but no commands work .
maybe if i put the LAF back on it it will boot ?
caesar170988 said:
maybe if i put the LAF back on it it will boot ?
Click to expand...
Click to collapse
I don't think so.
But with LAF back and started you should be able to use "LG UP" to flash a new firmware.
I can't tell you how you will be able to do that if it is not booting.

[solved] Stuck at boot (even recovery), only fastboot works

I've tried to flash MIUI9 over LineageOS 14 with full formating.
After flashing I'm stuck at boot logo MI. Even if I try to boot into recovery.
Fastboot works, but I'm unable to change anything
Code:
$ fastboot boot recovery.img
> FAILED (remote: unlock device to use this command)
$ fastboot oem unlock
> FAILED (remote: Token verification failed, reboot the device)
The thing is, I remember unlocking bootloader when flashing original ROM with LOS. How is it locked again?
How to get out of this situation? I don't care about any data on the phone.
Thank you.
xda-lukasik said:
How to get out of this situation? I don't care about any data on the phone.
Thank you.
Click to expand...
Click to collapse
In this situation only EDL-mode flashing is possible, but no worries, you can unlock it and get MIUI again at the same time...
https://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
xda-lukasik said:
When i type
Code:
$ fastboot oem edl
the phone is no longer listed in
Code:
$ fastboot devices
Also, I don't have a windows pc but i found this tool: XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan (unable to post link)
but it also doesnt list my device after fastboot oem edl (because it uses fastboot devices)
Click to expand...
Click to collapse
You aren't reading the guide correctly, but for a Linux user I will clarify a few things.
- look, in the guide "Command: fastboot oem edl (this brings your device in a kind of emergency recovery state) -> the device does only show a black screen" - it means fastboot and "fastboot devices" do not exist anymore and your device enters QUALCOMM HS-USB QDLOADER 9008 mode
- run lsusb on Linux in fastboot and then in EDL/9008 mode - the IDs will be different and there is no Linux driver for 9008
- the Linux tool you mentioned is just a script to automate some trivial tasks which can be done manually in fastboot mode. I checked the source code and note "sudo apt-get install android-tools-fastboot", it pulls the fastboot app from a repo and works on it. The tool is completely useless for this job.
- your only option is MiFlash which runs on Windows
- you can get Windows 10 evaluation ISO from Microsoft and get rid of it later
- you can get Windows running in a much easier way but we are forbidden to talk about it on this forum
:good:
Good luck!
Tried and failed.
After oem edl there is no device listed in miflash and "flash" does nothing.
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
cybercruizer said:
I got same problem last month. I tried using miflash with stock firmware and change the stock recovery with twrp img. Hope this can solve your problem.
Click to expand...
Click to collapse
I'm unable to flash anything
Ugh, when you enter edl mode it becomes different device in virtual box and you need to add it again.
But I tried it several times with real windows machine and it didnt show up either (??)
It still didnt worked, I got errors such as:
Failed to hello message
Ping failed
Solution was to use older MiFlash tool (2015).
Thanks all for your help.

Please help (remote: unknown error)

Guys , I am new on Op7 , I had a stuck in fastboot because of unable to use boot command, then using msm tool I went back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
U can only install twrp through booted TWRP
also pie and q version of OOS need proper boot.img TWRP from this thread https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
new_world_2006 said:
Guys , I am new on Op7 , I had a stuck in fastboot because of unable to use boot command, then using msm tool I went back to 9.5.3 . I re did the unlock and then whenver I tried to install twrp using fastboot , it shows remote : unknown error
How I can install twrp and magisk ?? And update to 10 ?
I need step by step please . Considering I am on 9.5.3 OEM unlocked but I am unable to use fastboot boot option.
Click to expand...
Click to collapse
Upgrade to 10, then Root.
blas4me said:
Upgrade to 10, then Root.
Click to expand...
Click to collapse
So how i can root, if i have damaged fastboot boot command?
new_world_2006 said:
So how i can root, if i have damaged fastboot boot command?
Click to expand...
Click to collapse
First thing is to OTA update to anything other than 9.5.3. Seemed to me I remembered when I first got the device (many months ago) somebody mentioned there was a fastboot issue on 9.5.3. So just take whatever OTA is availabe to you. Probably 9.5.13
If you still can't boot the twrp.img after that then try manually changing the active slot in fastboot;
fastboot getvar current-slot *(take note of the current slot this command returns)*
fastboot --set-active= *(=a or =b to change slot to the opposite the first command returned)*
fastboot reboot bootloader
So you should end up with something like this;
fastboot --set-active=a
fastboot reboot bootloader
fastboot boot "C:\Adb\twrp-3.3.1-4-guacamole.img"
new_world_2006 said:
So how i can root, if i have damaged fastboot boot command?
Click to expand...
Click to collapse
Bootloader is not damaged, did you enable usb debugging.
Please read, most of us have been there, and a lot of us are coming from some other OnePlus device. Project treble was discussed a lot on 5T forums. If your bootloader detects custom firmware while locked, it will lock the phone. You can't run fastboot commands because you missed a step somewhere.

Oneplus 8 bricked after rollback from OxygenOS 11 (MSM tool doesn't work)

Yestaday I upgrade Oneplus 8 IN2010 OxygenOS International to 11 and working just fine
But I regret it because there is no root
So I flash official rollback package from:https://forums.oneplus.com/threads/oxygenos-11-for-the-oneplus-8-pro-and-oneplus-8.1312654/
After local package flash,I reboot my phone and this thing happened
When it displays the oneplus logo, it becomes a black screen instead of a boot animation
I tried using twrp to flash OxygenOS,no error but still black screen
I tried many different versions with MSM tool
But there is no way to solve my problem
I tried to talk to oneplus service staff online
But because I was in Taiwan, they couldn’t perform the session with China region?
Taiwan is not even part of China!(Digress
Anyway, I regret disappointed and sad now
I really hope I can save my phone :crying:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
djmcnz said:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
Click to expand...
Click to collapse
Thanks for your help but MSM tool locked my bootloader
I don't know what to do now
Maybe wait for OxygenOS 11 MSM tool have the opportunity to fix it
oliver802 said:
Thanks for your help but MSM tool locked my bootloader
I don't know what to do now
Maybe wait for OxygenOS 11 MSM tool have the opportunity to fix it
Click to expand...
Click to collapse
Can you access fastboot? If so...
Code:
command: [I]fastboot oem unlock[/I]
First of all there is root on oos11, there is a magisk guide here on the forum, i did it myself & flashed magisk & was able to gain root access & installed custom kernel too
luscharsch said:
First of all there is root on oos11, there is a magisk guide here on the forum, i did it myself & flashed magisk & was able to gain root access & installed custom kernel too
Click to expand...
Click to collapse
I know but too late
djmcnz said:
I had a similar problem and fixed it this way, you can check if you have a bootable image in the alternative 'slot' (A/B):
Code:
1. start in fastboot mode
2. command: [I]fastboot getvar current-slot[/I]
3. note current slot (A or B)
4. change slot
5. command: [I]fastboot --set-active=a[/I] [B]OR[/B] [I]fastboot --set-active=b[/I] <- you want to change from your current slot
6. command: [I]fastboot reboot[/I]
You need an unlocked bootloader to change slots manually.
Click to expand...
Click to collapse
Thanks, I can boot to slot b and have crash dump on slot a, can't recognise in MSM and reluctant to use it after doing the rollback from A11 as afraid to lock the bootloader without successfully restoring as happened to OP
xdtyui said:
Thanks, I can boot to slot b and have crash dump on slot a, can't recognise in MSM and reluctant to use it after doing the rollback from A11 as afraid to lock the bootloader without successfully restoring as happened to OP
Click to expand...
Click to collapse
If you can boot for either slot you're fine, don't worry about the other, if you have a bootable slot you can recover to a factory image from it, you don't need to rely on the other (non-bootable) slot.
djmcnz said:
Can you access fastboot? If so...
Code:
command: [I]fastboot oem unlock[/I]
Click to expand...
Click to collapse
FAILED (remote: 'Flashing Unlock is not allowed')
djmcnz said:
If you can boot for either slot you're fine, don't worry about the other, if you have a bootable slot you can recover to a factory image from it, you don't need to rely on the other (non-bootable) slot.
Click to expand...
Click to collapse
Yeah thanks, I have a factory image on b so is it alright that a boots to crash dump? Could that be a problem in the future?
xdtyui said:
Yeah thanks, I have a factory image on b so is it alright that a boots to crash dump? Could that be a problem in the future?
Click to expand...
Click to collapse
That's okay. Often the alternative slot is unbootable. The next time you do a system update it will make the alternative slot bootable and boot from there.
---------- Post added at 12:59 ---------- Previous post was at 12:56 ----------
oliver802 said:
FAILED (remote: 'Flashing Unlock is not allowed')
Click to expand...
Click to collapse
Okay, if you can't unlock the bootloader, can't get into EDL mode and you can't use ADB then you need to chat with OP technical support again and hope they can help.
djmcnz said:
That's okay. Often the alternative slot is unbootable. The next time you do a system update it will make the alternative slot bootable and boot from there.
---------- Post added at 12:59 ---------- Previous post was at 12:56 ----------
Okay, if you can't unlock the bootloader, can't get into EDL mode and you can't use ADB then you need to chat with OP technical support again and hope they can help.
Click to expand...
Click to collapse
I can get into EDL mode and no error on MSM tool
But I have tried flashing with MSM tool, it shows that the flashing is successful and the Bootloader is also locked.
But I still can’t enter the system
In addition, flashing the version before instantnoodle_15_O.20_200716 will enter Qualcomm Dump mode
I used to suffer like you on oxygenos 11. Maybe you haven't installed Qualcomm HS-USB correctly. You should reinstall many times to wish you success.
Make sure it's latest MSMtool, that was the issue for me. Also can you get to the other slot? If so you can boot there and enable OEM unlocking from there, than unlock in fastboot.
greendragon527 said:
Make sure it's latest MSMtool, that was the issue for me. Also can you get to the other slot? If so you can boot there and enable OEM unlocking from there, than unlock in fastboot.
Click to expand...
Click to collapse
Unfortunately, because the bootloader of my device is locked by MSMtool, I can't switch partitions
Not sure if this is helpful, but I had trouble getting MSM to work after upgrading to OOS11 because I couldn't get into EDL mode. Something changed with boot in OOS11 so the normal up+down key combination didn't work it just always put me into fastboot. 'adb reboot edl' didn't work either it just went into fastboot. What I finally found that worked was a patched version of fastboot.exe that has the reboot-edl command. After that I was able to MSM successfully.
Here's the patched fastboot I used: https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
I used the MSM tool of OxygenOS 11 to successfully repair my device
Thanks to everyone who helped me
oliver802 said:
I used the MSM tool of OxygenOS 11 to successfully repair my device
Thanks to everyone who helped me
Click to expand...
Click to collapse
Can you share the lino to MSM for 11 please
firoz3321 said:
Can you share the lino to MSM for 11 please
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877
I'm having same issue only fastboot and crashdump mode lol msm don't spot my phone probably too many other drivers I hold volume up and down for crash dump any ideas I've tried 11 no luck I updated to 11 using the oxygen updater

my phone is hardbricked

i am stuck in qualcomm crash dump mode.i cant boot to edl mode. i tried flashing the global software on my T-mobile branded phone. the only thing that is available to use is fastboot. the key combos to boot in edl mode isnt working for me. thank you guys
Flashr416 said:
i am stuck in qualcomm crash dump mode.i cant boot to edl mode. i tried flashing the global software on my T-mobile branded phone. the only thing that is available to use is fastboot. the key combos to boot in edl mode isnt working for me. thank you guys
Click to expand...
Click to collapse
If you can get to fastboot, make sure you have fastboot set up on your computer and try the following series of commands it might work...
Code:
fastboot getvar current-slot
Note slot a or slot a
Code:
fastboot --set-active=[B]?[/B]
Where "?" is the slot that's NOT currently active, e.g. fastboot --set-active=b
Code:
fastboot reboot
If that works then great, if that doesn't work you can swap the slots back if you wish and continue trying with edl mode (if that doesn't work then raise a support ticket with OnePlus and they can take remote control of your phone to try and fix it).
djmcnz said:
If you can get to fastboot, make sure you have fastboot set up on your computer and try the following series of commands it might work...
Code:
fastboot getvar current-slot
Note slot a or slot a
Code:
fastboot --set-active=[B]?[/B]
Where "?" is the slot that's NOT currently active, e.g. fastboot --set-active=b
I got android sdk tools and just to be doubly sure I double checked my fastboot tools. I copied and pasted the command you wrote but when I tried to change the active slot, I got "C:\adb\fastboot.exe: unknown option -- set-active=a"
Any clue where Im screwing up?
Click to expand...
Click to collapse
Arkasia said:
djmcnz said:
If you can get to fastboot, make sure you have fastboot set up on your computer and try the following series of commands it might work...
Code:
fastboot getvar current-slot
Note slot a or slot a
Code:
fastboot --set-active=[B]?[/B]
Where "?" is the slot that's NOT currently active, e.g. fastboot --set-active=b
I got android sdk tools and just to be doubly sure I double checked my fastboot tools. I copied and pasted the command you wrote but when I tried to change the active slot, I got "C:\adb\fastboot.exe: unknown option -- set-active=a"
Any clue where Im screwing up?
Click to expand...
Click to collapse
Remove the --.
Code:
fastboot set-active a
See all commands here:
https://source.android.com/devices/bootloader/fastbootd
Click to expand...
Click to collapse
Interesting, I've never had a problem with --set-active=a/b (e.g. https://www.androidexplained.com/change-active-partition-slot/).
@op - make sure you're using the latest version of the Android Platform Tools.
You can also 'fastboot -aa' or 'fastboot -ab' but I prefer explaining longhand because shorthand commands are easier to get wrong.

Categories

Resources