Develop Bugs

[Q] Galaxy Nexus Bootloader Unlock [HELP]

Hi all, Purchased my Galaxy Nexus today - First thing on the list; Unlock and Root.
I have downloaded all of the necessary files but cmd is stuck on < waiting for device >
My phone is in fastboot mode but i cannot get this command to work to unlock the bootloader - I have installed the Samsung drivers... Is there anything I am missing here?
Any help or suggestions welcome, Thanks!

Try with a different USB cable if you can.
I had the same issue (device not being found) using the cable that came with it, so I swapped it for the one that came with my Desire and it worked fine.
Worth a shot.

Cheers! I'll give it a try!

Just tried my original Nexus One USB cable but no luck - I'm thinking it could be something to do with the drivers?

lexarjump said:
Hi all, Purchased my Galaxy Nexus today - First thing on the list; Unlock and Root.
I have downloaded all of the necessary files but cmd is stuck on < waiting for device >
My phone is in fastboot mode but i cannot get this command to work to unlock the bootloader - I have installed the Samsung drivers... Is there anything I am missing here?
Any help or suggestions welcome, Thanks!
Click to expand...
Click to collapse
If you run "fastboot devices" and there's nothing found, then you need to install the fastboot drivers (these are not the same as the USB debug drivers from the zip).
I've found the easiest way to get the drivers is to install pdanet - as part of the installation process you install all needed drivers. You can then uninstall pdanet (or in my case, have the installer crash), leaving just the fastboot driver for you to carry on your rooting

lexarjump said:
Just tried my original Nexus One USB cable but no luck - I'm thinking it could be something to do with the drivers?
Click to expand...
Click to collapse
mybe, you can try fastboot devices and check if the device is found.

Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers

braingravyuk said:
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
Click to expand...
Click to collapse
Honestly, not willing to check this one after spending today setting up my device, and no custom recovery available yet.
But given it's a Nexus device, and noting the ease with which we can unlock, then I'd say it's a pretty surefire bet that relocking will be just as easy.

Thanks alot! It worked

I'm looking to just unlock the bootloader of my Galaxy Nexus which will hopefully arrive tomorrow morning. I currently have AndroidSDK and samsung drivers both installed on my pc as well as a file called fastboot.exe. my question is do I need both the Samsung Drivers as well as AndoidSDK installed for this?

rock7632 said:
I'm looking to just unlock the bootloader of my Galaxy Nexus which will hopefully arrive tomorrow morning. I currently have AndroidSDK and samsung drivers both installed on my pc as well as a file called fastboot.exe. my question is do I need both the Samsung Drivers as well as AndoidSDK installed for this?
Click to expand...
Click to collapse
I think PDAnet should be sufficient

Proyoyo said:
I think PDAnet should be sufficient
Click to expand...
Click to collapse
okay thanks

I tried all day yesterday to unlock bootloader with no success. I installed the latest sasmsung usb drivers for mobile (released on 31/10/2011). This allowed the PC to recognise the phone installing the drivers properly. But then starting the phone in recovery mode (power+up+down bottons) I get the android 1 not recognised in device manager.
I then saw this thread and decided to install pdanet 3.02 client on the pc. I couldn't complete that step as pdanet cannot see the phone.
I gave up in the end. If you manage to do it successfully could you please tell me the step you did?
I am going to try tonight on my mac as apparently on mac you do not have this drivers issue. Will post with my results.
---------- Post added at 10:41 AM ---------- Previous post was at 10:34 AM ----------
By the way the latest samsung usb drivers can be found here:
http://forum.xda-developers.com/showthread.php?t=961956
---------- Post added at 11:39 AM ---------- Previous post was at 10:41 AM ----------
Forget my previous post.
Installing pdanet and saying no to install the usb drivers (as part of pdanet install) everything should be fine.
Done mine and working fine.
Thanks.

braingravyuk said:
Just along the lines of using fastboot oem unlock... is the Galaxy the same as the Nexus S in that you can relock the bootloader again?
Cheers
Click to expand...
Click to collapse
yes
fastboot oem lock will lock it

Hey I seem to be having some troubles as well,
windows 7 recognizes it as an ADB device and when I use - adb reboot bootloader
it takes me to the fastboot screen that it should.
but once I'm there it doesn't recognize any fastboot devices.
And yes I have reinstalled the SDK, Samsung drivers, and Android ADB driver
Would it matter that I had previously done a bunch of messing around with my ASUS transformer on this computer?
under device manager it says:
ASUS Android Devices - Android ADB Interface
I'm going to try it on another computer tomorrow but I'm curious if that should make a difference.

The driver failed to install on my phone...when I reboot into my bootloader it looks a bit different from in the video. Mine just has an android and it says start above it. The oem unlock command fails to do anything as well.
Why is nothing ever simple?
Does your phone need to be connected when you install the samsung drivers on it? Or does it install these drivers after booting into the bootloader?
When I install the samsung drivers on my computer with the phone connected, it says the following:
Android phone: No drivers found
Samsung Mobile USB Composite Device: Ready to use
Samsung Mobile MTP Device: Failed
Samsung Android ADB Interface: Ready to use
When I hold the volume buttons and power it on now, it just goes straight to the google logo...not even getting the android logo with the start option anymore. I think I might have accidentally uninstalled the ADB drivers in my device manager because I saw 2 copies and thought I installed it twice...

[Q] root android pro

has anyone tried the root android pro for the t mobile galaxy note 2? i tried rooting my phone on my mac and can't seem to do it, and have never rooted a phone before. i don't have access to a pc which i can try rooting my phone from but really want to do this. any tips on the root android pro or any suggestions on what i can do?

i think Heimdall will work on Mac AFIK
or use Odin with Windows in virtual machine

yahyoh said:
i think Heimdall will work on Mac AFIK
or use Odin with Windows in virtual machine
Click to expand...
Click to collapse
thanks yahyoh. i tried the heimdall on my mac from the tutorial on this site, but when i tried the commands for the terminal server i think it was, the computer didn't recognize my device. even copy and pasting the next 4 lines as said in the tutorial didn't work. i can't find anyone who will loan me a pc for a long enough period and majority of my friends have mac or iphones so they can't help me. i ran across the root android pro on a link from this forum and was wondering if anyone tried it or had any other suggestions on how to root

I want too

well, apparently this can't be used on a mac anyway. any other hints on how i can root using a macbook?

sniper910 said:
thanks yahyoh. i tried the heimdall on my mac from the tutorial on this site, but when i tried the commands for the terminal server i think it was, the computer didn't recognize my device. even copy and pasting the next 4 lines as said in the tutorial didn't work. i can't find anyone who will loan me a pc for a long enough period and majority of my friends have mac or iphones so they can't help me. i ran across the root android pro on a link from this forum and was wondering if anyone tried it or had any other suggestions on how to root
Click to expand...
Click to collapse
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-galaxy-note-2-on-mac-osx/
hope this helps

thanks chocolateboyctg, this is the one i tried, and when i had to the command terminal, i couldn't input the commands needed. the computer wouldn't recognize my device. that's where i got stuck and couldn't proceed

Trying ti fix a bricked Kindle Fire HD 8.9 for a friend

Hey Guys,
OK, so I have spent about 5 hours scouring this forum and google and am in need of some help. I am trying to fix a kindle for someone and I really dont have much experience with Kindle at all but have rooted most of my android phones with no problem and flashed different roms etc... Well this thing seems a little hosed. When I turn it on, it shows the kindle splash screen then goes directly to the red screen. I wanted to use fastboot but device manager doesnt even show the device. When I power on the kindle, it will flash the jem device (Jem-PVT PROD-04) and then it goes right away so I dont really have any opportunity to install the drivers. WIth that being said, I cant use fastboot (just is stuck at waiting for device) or adbdriver.
My buddy attempted to root the kindle and was able to using yeymasterroot or something like that then proceeded to use fireflash and using freedom boot and twrp.
Has anyone gone through this and fixed it? How can I get fastboot to work (I tried installing the USB drivers and also installed the Android sdk). Is this thing just hosed and I should give up? I really dont want to and look at it as a challenge and was hoping maybe someone has had the same thing and figured it out? Oh, and I asked what version it was on before and he said 8.5.1.
Thanks in advance.

The key is the fastboot driver. I've read if you are quick to right click in the display manager you can get the fastboot driver installed. Another method is to use a ubuntu live cd and use that to get into fastboot.

macman005 said:
The key is the fastboot driver. I've read if you are quick to right click in the display manager you can get the fastboot driver installed. Another method is to use a ubuntu live cd and use that to get into fastboot.
Click to expand...
Click to collapse
Thank you.
Just an FYI for anyone that runs into the same issue. I absolutely tried every method I could find (I must have spent probably 15 hours or so researching) to use WIndows and finally gave up. I tried the most recent version of Ubunto live and this did not work as well. Soupkit would not install, I had to use Ubunto 12.04. Once I loaded this, I installed soupkit then tested fastboot and was good to go. Once in fastboot, I used the followink step by step wiki (follow every step to a T):
wiki.cyanogenmod.org/w/Install_CM_for_jem
Now, I have it working and it is fast and nice (albeit a bit heavy).
I hope this helps someone avoid wasting all of the time that I did for this but I am glad it is finally working. Next I will install Lollipop.

Trick how to fix this
maybe it is too late but it will help someone else probably if they face the same issue, first you will need to reboot windows with drivers signature disabled and then install these drivers who was made compatible with the jem model (the only one that worked for me) you can install them by just right clicking the .inf file after extracting the archive, or by going to the device manager and then make it show the hidden devices and you will see the Jem-PVT PROD-04 fadded in the devices list, you can right click on it and access to properties and from there you can install drivers via update (I guess you have the minimal windows knowledge to do this)...

[Q] HTC One not recognized in fastboot mode

As the title says, basically I want to unlock my HTC One V's bootloader, and to do so I have a minimal adb thing folder, HTC Sync Manager, I have USB debugging enabled, and so I reboot to Fastboot mode with "adb reboot bootloader" however my windows 10 PC pops up a message that the phone wasn't recognized. I realize that Fastboot and adb use different drivers, however when I have it in the bootloader area where I can select Fastboot, and where adb "should" work (If I'm correct) but "adb devices" pulls up nothing.
Thanks for your help in advance, I've already Custom Rommed my Nexus S and Amazon Fire HDX 7" (Amazon is waaay to protective of they're bootloader ) so if you see that there is missing info, I should be able to supply it.
Thanks
-AnyAndroidOSRomWins

I have the same problem!!! Please, help to solve it.

Haven't figured it out yet.
P.S. I really like te camera on this thing even with the HTC sense bloat.

I am also having this problem also windows 10. but when i used fastboot on my window 7 laptop the last time it worked fine maybe its the way windows 10 handles the drivers? idk

This guide for the Wildfire S worked for me. Got Fastboot working on Windows 10.

chemimoco said:
This guide for the Wildfire S worked for me. Got Fastboot working on Windows 10.
Click to expand...
Click to collapse
Hey, thanks so much for this! I spent tons of time googling and finding no answer when none of my windows (10) PC's (or my arch linux partition) would recognize my HTC One V, but thanks to you Registry file, It does, thanks again!

AnyAndroidOSWins said:
Hey, thanks so much for this! I spent tons of time googling and finding no answer when none of my windows (10) PC's (or my arch linux partition) would recognize my HTC One V, but thanks to you Registry file, It does, thanks again!
Click to expand...
Click to collapse
You are welcome. Its amazing there is still active development for this device.

No fastboot devices but can use adb devices.

Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks

I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

ELoTRIX said:
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Yeah me too, same ROM and PC OS. Very strange

CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10

But phone starts ok in OOS system?
If, yes, download TWRP 3.0.2.1 original & TWRP 3.0.2.1-19 modified. Put them in phone sd card. Download FLashify from Play store and flash recovery .img. Then go recovery to test if it works.
One of those will work.

inflames19 said:
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
Click to expand...
Click to collapse
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....

Thanks for the different solutions, I'll try it for myself.
But I'm still wondering why the unlock worked because there it used fastboot too

1
me too its says : Witting for devices !!!
Rom: OOS 3.2.7
PC: Windows 10

CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.

1
rpsgrayfox said:
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
Click to expand...
Click to collapse
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem

Since there are a lot of people complaining I think the problem is bigger than we think :/ My OP3 nor OPO are seen

CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Sir Mohd said:
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Click to expand...
Click to collapse
I'm sorry to hear it didn't work, I'd try to reinstall adb and fastboot then using Minimal Adb and Fastboot found in this thread http://forum.xda-developers.com/showthread.php?t=2317790

ELoTRIX said:
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Click to expand...
Click to collapse
Please tell us how you did That ,
Ty.

Sir Mohd said:
Please tell us how you did That ,
Ty.
Click to expand...
Click to collapse
I have just installed on my Windows 10, a Virtual Machine (VMware) with Windows 7 installed all driver oneplus 3 and adb+fastboot and it works

I have the same issue. Got my OP3 yesterday and have been trying in vain to get my Windows 10 install to recognise the phone in fastboot mode, but to no avail. I am unable to unlock my bootloader.

I think the problem is with Windows 10. My laptop did an update yesterday, I think that's the problem.

Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help

It appears to be an issue with Windows 10 drivers. I have used an ancient install of Xubuntu on an older EeePC in order to unlock the bootloader and flash TWRP and SuperSU. I've still had no luck getting fastboot to be recognised on Windows 10, though on Xubuntu, it is recognised instantly with no issues.

inflames19 said:
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
Click to expand...
Click to collapse
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u

Sir Mohd said:
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Click to expand...
Click to collapse
I'm not at my pc atm but I'll try my best:
If you plugin your op3 there will be a cd mounted with the setup for the driver.
I just installed this driver with the setup.exe (on a complete new instance of Windows 7).
After the installer was finished, I opened cmd.exe and could use adb and fastboot.