Related
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
jchen221 said:
Hey guys, I really need some help here, I'm not good at any of this stuff - my OPO just randomly got stuck on a boot loop, I have never played with the USB debugging or any of that or tried to flash anything else, I was using just stock cyanogen.
I've been reading around and I've downloaded all the drivers but still can't detect the device when I do the Shift + Right Click --> Run CMD "fastboot devices" or "adb devices".
I never enabled options such as the USB debugging or anything else, can someone please help me out? I'm really clueless to all of this stuff.
Click to expand...
Click to collapse
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Heisenberg said:
This, except that's the wrong button combo (power + volume down is for recovery). Use power + volume up to get to fastboot mode and then try the "fastboot devices" command.
Click to expand...
Click to collapse
I'm sorry for this mistake.
joanquro said:
You must first put your phone in fastboot mode.
To put your phone in fastboot mode, turn it off, and then hold power+volume down until you get a screen with only the cyanogenmod logo. If you get to this screen, you're in fastboot mode. If you have installed the proper drivers in your computer, you should be able to connect to the phone from your computer. Connect your usb cable to the phone and the computer, open a dos box and type "fastboot devices". If you get a series of letters and numbers then you're OK.
Click to expand...
Click to collapse
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
jchen221 said:
Thanks for your advice. This is the big problem I'm having, I've downloaded the SDK slim, and the driver manager and the 15 second installer things and installed all of them but still can't manage to detect my phone on fastboot.
Click to expand...
Click to collapse
What command are you using while in fastboot mode?
Heisenberg said:
What command are you using while in fastboot mode?
Click to expand...
Click to collapse
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
jchen221 said:
I'm using both
fastboot devices
adb devices
Fastboot devices comes back with nothing in the CMD box, ADB devices gives a message that says 'Devices:' but there are none listed.
Click to expand...
Click to collapse
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Heisenberg said:
There's no point in using adb commands in fastboot because only fastboot commands work. What drivers do you have installed?
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
jchen221 said:
I've looked around for all sorts of drivers, I have the universal ADB, android SDK slim or something, is there a specific one I need?
Click to expand...
Click to collapse
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install , reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
jchen221 said:
I tried that, but again no response in CMD when I type fastboot devices.
Although I just tried and am able to boot into recovery mode, would I be able to do some sort of factory reset there? I've already tried to wipe user data but I'm still getting a bootloop there.
Click to expand...
Click to collapse
Heisenberg said:
I can't remember what capabilities the stock recovery has, but if it's there it's worth trying.
Click to expand...
Click to collapse
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
I have the same problem.
jchen221 said:
I managed to get it to work after resetting a bunch of the options, thanks so much for your help with this (even if I didn't get it to fastboot mode)
Click to expand...
Click to collapse
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
pavanakshay said:
Hey bro, I have the same problem. Can you please explain me how did you resolve it? This would be of great help. Thanks.
Click to expand...
Click to collapse
for me too bro same problem please help me
---------- Post added at 08:28 AM ---------- Previous post was at 08:25 AM ----------
Heisenberg said:
Uninstall whatever drivers you have installed, reboot your PC, install these drivers, reboot your PC, connect your phone, test fastboot (fastboot devices).
Click to expand...
Click to collapse
i too having the same problem bro the driver link is not working please send me the link thankyou in advance
i am also facing the same problem that phone loops into fast boot mode whenever turned on i do totally every kind of drivers softwares and etc like tenorshare but all in vain i guess at last that phone must be enabled usb debuging in order to be detected as a active adb device,i pratically do this stuff by using another phone with enabled debuging and it was an active device andd can be processed further but when i disabled the usb debugging of same phone it was not working with adb interface i hope you understand,,,,but a miracle happenend i removed the battery for about a week and suddenly i pluged and try to turn it on hola it starts from roms boot logo
HELP!!!!! Stuck on bootloop and fastboot not working
i was flashing twrp on infinix s4 withfast boot. after flashing the device is stuck on bootloop. the recovery is not accessible (i press the key combo nothing happens) and fastboot combination is also not working. i tried connecting it with adb cmd and ran the command "adb reboot bootloader" but no device is detected.
ps: the link for drivers is broken
who can help me boot to EDL for Mi Note 3. Thank very much
Hello there. I was able to reboot in edl mode.
1. Enter in fastboot mode
2. connect pc usb cable to phone
3. in command prompt type fastboot oem edl
4. the phone will shut down and enter edl mode (phone will look like it's shut down)
5. use MiFlash to flash firmware (use a fastboot rom). I think this will flash every img in the images folder
Good luck, hope it helps!
I can not help myself
caoanhhiep27 said:
who can help me boot to EDL for Mi Note 3. Thank very much
Click to expand...
Click to collapse
Did you get friend?
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
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.
I can't get into MSM mode again, and there appears to be nothing else on the phone other than fastboot. I'd really appreciate any help.
https://imgur.com/RLwY0em
Have you tried reinstalling the Qualcomm driver so that you can get back into MSM?
BillGoss said:
Have you tried reinstalling the Qualcomm driver so that you can get back into MSM?
Click to expand...
Click to collapse
I did try this, but my problem was the fact that every time I tried to get into edl mode, it opened fastboot instead. The fastboot options were looping around really fast, like a volume key was stuck down.
I eventually got it into edl mode, making sure I held volume up+down for 10 seconds before plugging in to the pc with MSM already started.
Glad to hear you got back into EDL mode.
I've had the quickly changing state in fastboot happen also. I connected the phone to the PC and then used fastboot reboot bootloader to reboot the phone and that stopped the looping.
BillGoss said:
Glad to hear you got back into EDL mode.
I've had the quickly changing state in fastboot happen also. I connected the phone to the PC and then used fastboot reboot bootloader to reboot the phone and that stopped the looping.
Click to expand...
Click to collapse
ah thanks, good to know - i've used adb commands before but I was trying to use adb commands but with the fastboot suffix "fastboot reboot edl" - - rather than "adb reboot edl". From the many variations of this, it seems there isn't a way to get from fastboot to edl directly, which is slightly annoying because it would've saved me.
Hopefully i won't get there again, but maybe the "fastboot reboot bootloader" will help if I do. Cheers!
F311D0WN said:
ah thanks, good to know - i've used adb commands before but I was trying to use adb commands but with the fastboot suffix "fastboot reboot edl" - - rather than "adb reboot edl". From the many variations of this, it seems there isn't a way to get from fastboot to edl directly, which is slightly annoying because it would've saved me.
Hopefully i won't get there again, but maybe the "fastboot reboot bootloader" will help if I do. Cheers!
Click to expand...
Click to collapse
Yes, there's no simple way to get into EDL from fastboot.
The other way that works for me from bootloader is:
- start MSM tool
- connect phone to PC
- hold Power+Vol Up+Vol Down until it connects to MSM
Easy!