As title states, I have converted to international version from t mobile. I put the phone into fast boot to try and OEM unlock. but on PC , in command prompt, it doesn't show up. I've been searching for hours through posts on here, but haven't found an answer to why. I've already gone through and done the conversion with the tools, but now that its converted, I've gone back into developer options, clicked OEM unlock, and as I read in another post, clicked USB debugging. But still nothing. When its not in debugging mode, it shows in task manager when phones on, but when I put into fast boot, it does not show in PC. But, either way, and through any USB port, it does not come up in fast boot devices in command prompt. Can anyone help with this issue.
Samwest1 said:
As title states, I have converted to international version from t mobile. I put the phone into fast boot to try and OEM unlock. but on PC , in command prompt, it doesn't show up. I've been searching for hours through posts on here, but haven't found an answer to why. I've already gone through and done the conversion with the tools, but now that its converted, I've gone back into developer options, clicked OEM unlock, and as I read in another post, clicked USB debugging. But still nothing. When its not in debugging mode, it shows in task manager when phones on, but when I put into fast boot, it does not show in PC. But, either way, and through any USB port, it does not come up in fast boot devices in command prompt. Can anyone help with this issue.
Click to expand...
Click to collapse
you have to be booted in bootloader for fastboot to work.
Related
I'm currently attempting to root my atrix but I've come across a problem that I can't seem to be able to solve through googling or otherwise.
I'm using the tutorial stickied on the Atrix homepage labelled [HOWTO MAY16].
I got as far as step 8 and my phone passed the sbf flash using RSD lite but continuing on with the process to step 13 where it is asking me to type "fastboot oem unlock" into cmd I get an error message telling me that cmd is waiting for my device but nothing seems to happen.
I've tried reinstalling drivers (64 bit), restarting computer, restarting phone, trying different leads/usb sockets with no change to my result.
The exact thing that I'm doing with cmd is to navigate to the platform-tools folder, open adb, open flashboot and then attempt fastboot oem unlock.
Additional information:
UK Orange Atrix 4G running 3.4.4
using IHOP sbf file
running windows 7 64-bit, using the 64-bit drivers.
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
pre4speed said:
Do you have access to win 7 or xp? Win 8 is really new and possibly that could be the problem. Worth a shot.
Click to expand...
Click to collapse
Ops, typo. I'm running Windows 7 64-bit. I'll edit my post when xda allows me to.
Unlock
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
fdaconta said:
Enter the bootloader program by powering off the phone, Hold the volume down key and the power at the same time. The phone will be in the bootloader program when it powers up, use the volume down key to scroll through bootloader menu options. the second option will be fastboot program. Select the fastboot option with the volume up key, this will enter the fastboot mode of operation. Connect the phone to the PC via USB cable. Enter the directory where the fastboot program resides on the PC. Type the Fastboot oem unlock command. If sucessful a message will display on PC retuned by the phone. Reboot phone and unlocked will display in the upper left corner of the phones display. Continue to follow the original post, flash recovery, root phone, flash custom ROM. Happy Flashing, Enjoy! :fingers-crossed:
Click to expand...
Click to collapse
I just gave it another try and it gets stuck after I type fast boot oem unlock. I definitely have the right directory but I still get stuck here. Cmd just tells me it's waiting for my device and stops there. I think it's a driver issue after a bit of googling but the official drivers aren't working. This socks.
I had a similar problem with my device not showing up. There wasn't really a big fix for it but I just waited longer before trying to execute the command. I'm not sure if you're experiencing the same thing I did but when it couldn't detect my device it just hadn't been recognized by the computer yet. Make sure your drivers are working (connect usb and select every option on the pull down menu and are sure the device gets installed). After that do the same thing as before for fastboot but make sure you securely plug it in and wait for the computer to detect your phone before you move forward
Sent from my MB860 using xda app-developers app
Hi all,
I am trying to root my phone, following this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
However, I am stuck at entering 'fastboot devices' into the command prompt. It will not return my device's serial number. I know this is supposed to be becuase I don't have the correct drivers installed - but I'm pretty sure I do! I've spent hours scouring the internet for solutions and I can't find anything to help. So now I turn to you, please help me
I'm running windows 10.
I've double checked the google usb driver is installed.
I've manually installed the android bootloader interface driver.
The bootloader screen says on my phone says 'Connect USB data cable'. It is already connected and I have tried connecting it to all the ports on my laptop. I'm using the original cable that came with the phone.
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Eric214 said:
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Click to expand...
Click to collapse
I did indeed. And I also fixed it! I just needed to do some more tinkering. I set the fastboot.exe to recommended defaults. Not sure why it was not already but there you go. You can lock or delete this thread now, thanks!
I have adb and the needed drivers installed on my Windows PC, my phone is a Huawei P9 Lite and im trying to unlock the bootloader but the phone isnt beening detected when its in the fastboot mode. I have looked on XDA forums and nothing has helped so far. When i enter "fastboot devices" into CMD nothing comes up but when i enter "adb devices" my phone comes up so its not being recognised by fastboot. I put my phone into fastboot mode and tried "fastboot devices" and still nothing came up. I need to flash a ROM on it because the EMUI skin is really bad, could someone give me sugestions for a working ROM (I heard that using Cyanogenmod will remove a lot of features like camera and fingerprint)
I know, it's basic, but ( from XDA Forum )
Now we must activate the OEM Unlock option on your phone, go under Settings/Developer Options and tick the "Enable OEM unlock" option. In the same menu check if USB Debbuging mode is enabled, if not do it !
And for the rom, I don't like EMUI very much but Stock Rom with Nova Launcher give a good result
Double check drivers, setting, USB cable etc (Hisuite installed on PC and phone).
On the phone check if USB Debugging and OEM Unlock is cheeked and if USB debugging authorized is accepted.
If the phone is ok, untuched, is no reason for what you say...
sonneper said:
I know, it's basic, but ( from XDA Forum )
Now we must activate the OEM Unlock option on your phone, go under Settings/Developer Options and tick the "Enable OEM unlock" option. In the same menu check if USB Debbuging mode is enabled, if not do it !
And for the rom, I don't like EMUI very much but Stock Rom with Nova Launcher give a good result
Click to expand...
Click to collapse
OK I did that now and when im in fastboot mode the "FRP Unlock" text is now red, before it was green. I wrote "fastboot oem unlock CODETHINGHERE" and its still waiting for device. "fastboot devices" still shows nothing.
I'm not sure I did iy by the same way, I've just follow EXACTLY, step by step this how to :
http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701
I did it two times ,the only issu I had was because I forgot OEM unlock.
Read carrefuly the how to from the link, you 'll find what you need
That's most likely because you are on Windows 8.1+. Use the file from this thread - download, remove ".txt" and double-click. Don't worry about the KB update, with 99.99% certainty, you have it installed already. The .reg file will change something in your Windows Registry (no worries, it's safe). Reboot your PC and your phone should be detected by your PC after running fastboot commands Let us know if it helped!
Hey man probably you need to installa manual driver from pc. Connect you phone (in fastboot & and rescue mode) to the PC, than click with right button on Computer ( icon on desktop) and then click on "management" form here try to understand this image: http://prnt.sc/czanve
It's in italian made by me for a friend, I think you can easly understand just look images.
PS. for the moment I think you can find that driver in "kedacom usb device" and not "Android phone" as in picture
Still doesnt work
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
might be a long shot but i read somewhere else that a person had to type
fastboot -i 0x2e17 < zip/file here >
sorry ; all i know to try.
good luck
maybe @IronRoo can help.
I had the same issue but installed the driver from here and it worked.
https://essentialsupport1493251565....015490828-Windows-Drivers-for-Essential-Phone
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
Connect in fastboot mode and then restart phone with plugged in condition, see if it gives any driver notification.. if dosent then connect the pbone as media device it would show driver disk, you may install driver from there.
Talnoy said:
Hello there,
I've got a spare essential that I'd like to try getting Lineage on, or one of the other ROMs but today when I tried to do the unlock process as detailed here: https://android.gadgethacks.com/how-to/unlock-bootloader-essential-ph-1-0187597/ the device won't unlock as it can't be seen by fastboot.
I've installed systemwide adb/drivers, and the phone is listed as "Essential Phone Fastboot" but it just refuses to show under the "fastboot devices" command and I only get a 'waiting for device' when I try to run the fastboot unlock commands.
I've also installed essential's driver package but something seems to be missing? I'm really confused.
Click to expand...
Click to collapse
If non of the above work uninstall all phone drivers & or any other phone connection software that installs phone drivers also eg Samsung Kies/Connect then reinstall Essential drivers, though haven't read about conflicts in recent years ....(Also try different USB ports pref on direct to mother board, people have suggested in the past)
Hey, I just bought an S7 Edge SM-G950U, the att&t version, SM-G950A. I heard some say that it's not possible to unlock its bootloader, but the OEM unlock option turned out to be available in developer options. However, I'm having a hard time properly installing its drivers, whichever adb driver I use, the driver still shows a yellow warning and the error is that the device can't be started. The device shows up with adb devices when the device is on, but it doesn't neither with fastboot devices nor adb devices when it's in download mode. I'm trying to install TWRP, the hero 2 version. Any help would be appreciated. Thanks in advance
If you in Windows Device Manager find any device with yellow mark right on the device, then the driver installed for it isn't suitable: uninstall it, get Samsung USB Driver and install it.
Samsung devices don't know of a Fastboot mode: there it's called Download mode. You can't run any Fastboot command in this mode.
ADB operates on Android OS, not on device's bootloader, hence it's not working when running the device in Download mode.
Thanks for the prompt reply. I used a different laptop and managed to install the drivers properly, no warnings. However, the result is the same. You mention how I can't run fastboot commands in Download mode, where can I run them? Only Odin is working in that mode now, but I gotta try to unlock the bootloader. A lot of people are saying that this model can't be unlocked, even though the OEM unlock checkbook in the Developer settings is there. Any advice is appreciated
Up
Gearninja said:
Up
Click to expand...
Click to collapse
Down