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.
Related
i'm in the process of re-locking my bootloader in order to send it to Samsung for repair (home button not working). when i run the command line "fastboot oem lock", it just keeps hanging at "waiting on device" and nothing happens. i have the correct drivers installed. when i run "adb devices", it shows up the device. however, when i run "fastboot devices", it does not show up anything. any help on relocking my bootloader would be appreciated. Thanks!
Probably shouldn't be answering this here buuuuut...
adb reboot bootloader
and THEN
fastboot oem lock.
See what happens. You have to be in boot loader mode. Please move your questions to the Q&A section sir.
i did enter that command in order to get into fastboot. after that , i ran the command "fastboot oem lock" but it gets stuck at "waiting on device"
Update your drivers
Yea at this point I'd say its a connectivity problem. Drivers and or cable, but since you are getting adb devices to recognize, its not your cable. You should really use ubuntu, you would save yourself a lot of time, because you don't really have to deal with drivers like windows.
'sudo fastboot oem lock'
You need to be super user.
sure you went into bootloader and not recovery? because adb is seen in recovery and doesnt work in bootloader!
I'm trying to unlock the bootloader of my U8650. When i run adb devices i see it so i can say that the driver are correctly installed. i run adb reboot bootloader anf here i get stuck, since the phone restarts but hangs on the huawei logo and if i try to run fastboot oem unlock it says <waiting for devices>...this is done becouse the phone is not recognized by windows anymore, i have a yellow triangle on the Fastboot interface in my devices.
Could somebody tell me why?
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
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.