PROBLEM SOLVED
My version is Kb2003, and i can't enter EDL mode, nothing will connect to device manager nor msm tool when I'm trying to enter edl. The phone connects only when I'm in fastboot.
I tried fastboot boot twrp, fastboot flash recovery twrp, fastboot oem unlock, trying to connect to adb when the device is booting. https://prnt.sc/ssdOX4J2QXRt here is the things that i've downloaded.
https://prnt.sc/d1ykZOXlB8Mn Here is MSM Tool, and device manager when I'm in fastboot, i have updated my windows but still my phone can't enter EDL Mode...
EDIT: https://prnt.sc/a9Y0R9wWbMWX which qualcom driver should i choose? i can't find qloader 9008 ( I'm in fastboot mode rn)
I have searched for two days straight the xda forums, reddit, youtube, and other forums, please help me...
Related
Hi,
I've an honor 4c which I recently updated to Marshmallow. I'm trying to unlock bootloader for it and I've got an unlock code. But the problem is, when I enter in Fastboot and Rescue mode (I heard only about fastboot mode only but it opens Fastboot and rescue mode), the device isn't connected to pc. It does open the hisuite on PC when I connect usb cable but it doesn't connect the device. When I enter command, 'adb devices' in Fastboot cmd, it doesn't give any result. I've used ADB drivers, Universal ADB drivers and so on, they work and connect the phone to pc when the phone is switched on but when it goes to fastboot and rescue mode, the phone doesn't connect to hisuite. In device manager it remains present but it doesn't connect to hisuite in fastboot mode. What's the problem and what I'm supposed to do in order to overcome it?
Thanks
jaribhai said:
hi,
i've an honor 4c which i recently updated to marshmallow. I'm trying to unlock bootloader for it and i've got an unlock code. But the problem is, when i enter in fastboot and rescue mode (i heard only about fastboot mode only but it opens fastboot and rescue mode), the device isn't connected to pc. It does open the hisuite on pc when i connect usb cable but it doesn't connect the device. When i enter command, 'adb devices' in fastboot cmd, it doesn't give any result. I've used adb drivers, universal adb drivers and so on, they work and connect the phone to pc when the phone is switched on but when it goes to fastboot and rescue mode, the phone doesn't connect to hisuite. In device manager it remains present but it doesn't connect to hisuite in fastboot mode. What's the problem and what i'm supposed to do in order to overcome it?
Thanks
Click to expand...
Click to collapse
lol if it opens fastboot n rescue mode then dont worry just look at the bottom it will show phone lock or unlock if phone unlock its mean bootloader is unlock
My one plus is stuck in Qualcomm crash dump mode, It won't boot into recovery mode, but id does boot fastboot mode, I cant use adb to flash it because my bootloader is locked, adb cant recognize my device. I have tried QDL mode to use Guac msm download tool but it does no good, Can someone tell me what am I doing wrong?
Your best bet is to read up on the msm tread. A lot of answers can be found there.
With a locked BL , I can only suggest msm tool. Personally never got it to work myself but I unlocked my BL as soon as I got my phone so I used fastboot ROM to fix it. Best of luck
Hi
I have problem with fastboot mode.
My pc dont recognize anything in vivonex A fastboot mode. Anything not a single sound of connected disconnected device. And fastboot shows wating for device. Adb also dont show device in fastboot mode and recovery mode.
Drivers is ok and installed and adb recognize phone when it's on.
I unlocked bootloader in developer option i checked that fastboot mode with check and uncheck of "unlock bootloader". Same result and nothing showed in pc.
I wanna root and i tested kingoroot and that couldnt do it.
Plz help me.
Is Anyone here who could see fastboot device without any problem??
I have the nex chinese version
I just purchased a OnePlus Nord N10 5G (BE2026)
Originally it was running OxygenOs 10.x.x.x
Following guides from oneplus website and here on XDA I was able to successfully unlock the bootloader and of course ADB worked fine as well as Fastboot in the bootloader etc...
After unlocking the bootloader I realized that OxygenOs 11.0.2.BE86AA was available via OTA. Which is now what the phone is currently running.
***MAIN ISSUE***
after unlocking the bootloader in order to gain root access via TWRP and Magisk my PC fails to find any devices while the phone is in Fastboot mode... ADB still works just fine but as soon as I run "adb reboot bootloader" or boot to bootloader via buttons the PC will not detect the phone any longer while in the bootloader or Fastboot mode...
I have triple checked that:
SDK USB drivers
ONEPLUS USB DRIVERS
Windows Universal USB drivers
USB Debugging
OEM Unlocking
PC is granted developer access
newest version of ADB & Fastboot
and everything else I can find on this issue searching Google & XDA for the past 3 days
* one issue that I found strange, only when the phone was booted into the bootloader Windows device manager showed Android as an unknown device. Which I could only solve by using Zadig and installing Winusb driver... but still running "fastboot devices" while phone is in bootloader / Fastboot mode still shows no devices....
I've been trying to solve this about 4 days now scouring the internet for any information I could find and nothing seems to work. But everything worked just fine before I unlocked the bootloader / flashed OxygenOs 11 via OTA and now windows to see the phone while in the bootloader....
When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.
jwoegerbauer said:
When phone is got booted into bootloader / fastboot mode then phone can't get seen / accessed by ADB. Point.
Click to expand...
Click to collapse
@jwoegerbauer not entirely sure what you are trying to imply with your message...
If you are trying to point out that ADB doesn't work in bootloader / fastboot mode, I am completely aware of this. And never mentioned otherwise in my original message.
With my phone booted up into Android
And I run "adb fastboot bootloader" the phone will reboot into bootloader mode but my PC still shows waiting for devices... Or if I boot into bootloader / fastboot mode manually and run “fastboot devices" it shows no connected devices. And no fastboot Commands work either... I am not trying to run ADB Commands in fastboot mode.
AFAIK starting with Android 10 the command sequence should be as this
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
...
fastboot reboot
because fastbootd got moved to Android's userspace.
I was on A12 beta1, so I decided to go back to older firmware, I unlocked my bootloader and wanted to flash fastboot rom. When I tried it it says "Flashing not allowed for Critical partition" and when I try command:
fastboot flashing unlock_critical
It says failed, device already unlocked.
So I gave up and wanted to try MSM Tool, downloaded it and after literally 2hrs of looking for a proper driver somehow got it to work and see my device in EDL mode, but when I start flash it says "Param Preload Fails".
I have no idea what should I try next, tried everything in past 3/4 hours.
Device stuck in Fastboot mode, no booting, bootloader unlocked, any suggestions are welcome..