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
Related
After messing around with my shield last night and not being able to get root access on cm12. I tried to reinstall one of the ota updates from a while back. Now I am bootlooping and when I try to boot into CWM it looks to be corrupted and doesn't load. I cant use ADB because usb debugging is no longer active. Does anybody have any suggestions to re-install recovery or somehow enable debugging or am I dead in the water here? Any help would be greatly appreciated
Is your bootloader unlocked?
Can you get into fastboot mode?
HW method:
Turn off the device
Press and hold "Back"+"Home"+"SHIELD" buttons till device boots
Click to expand...
Click to collapse
If you can get into fastboot mode and your bootloader is unlocked, you can use a command like "fastboot boot recovery.img" to have the device boot a recovery.img from your computer without flashing anything.
If you can get into fastboot mode, but your bootloader isn't unlocked you could try unlocking your bootloader, but this will wipe your data - so only try this if you don't have anything important saved. The command is "fastboot oem unlock".
~Troop
The bootloader is unlocked Whenever I try fastboot mode the device is not recognized because USB debugging is disabled .
Update: Fixed
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
Guys,I was using Miui now I wish to unlock the boot loader and install custom
But the mi unlock tool is not detecting the device
Tried adb devices..it's detecting the phone but the fastboot devices is not detecting the phone..and the device manager either in when phone is in fastboot
Help guys
Nb:installed latest drivers,windows 10
Did you find any solution?, i am stuck in a similar situation please help me out
1st of all: To unlock the bootloader you have to accept the OEM unlocking from the developer settings (if you dont know how to access them google it)
2nd: while in fastboot on the fastboot driver execute the command " fastboot devices"
the output should be something like xxxxxxxx fastboot
If the pc or mi unlock tool doesnt see the phone the change your fastboot &/or adb drivers
If it still doesnt recognise it then you should change cable or go to a technician to fix the phone.
Good Evening,
I am trying to unlock the bootloader on my Nokia C5 Endi via ADB. I have USB Debugging turned on as well as OEM Unlocking. While by device is turned on in regular use mode ADB recognizes my device perfectly. Once I enter "adb reboot bootloader" It places my phone into Fastboot Mode. I then enter "fastboot flashing unlock" and I get stuck on "Waiting for Devices" I have downloaded nearly every driver I can find on the internet since Nokia does not have a Driver Installation Page and I still continue to fail. My PC recognizes my device perfectly when it not in Fastboot Mode.
One Click Root site said my phone could be rooted. So I went through their process just for them to tell me it cant be rooted. They said it cant be rooted because the Bootloader cant be unlocked because its a Cricket Phone.
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.