I am trying to unlock the xoom (best-buy, wifi only - in Canada).
I have adb and fastboot installed.
I have been developing apps on it all week (direct from eclipse, by pushing, by adb shell, by adb install etc).
I am using ubuntu 10.10
Rebooting to bootloader runs properly using
Code:
adb reboot bootloader
when I try
Code:
fastboot oem unlock
it says
Code:
'< waiting for device >'
and does nothing (I have been waiting for 10 minutes now).
Code:
adb devices
does not show the xoom listed (it did before rebooting to bootloader)
Code:
fastboot devices
also does not list any devices
I have tried rebooting with the hardware method as well (plugged into the computer and not plugged into the computer.
Killing and starting the adb server doesn't help either.
I would appreciate any guidance on the issue. I will post if I find a fix somewhere else.
CoatedMoose said:
I am trying to unlock the xoom (best-buy, wifi only - in Canada).
I have adb and fastboot installed.
I have been developing apps on it all week (direct from eclipse, by pushing, by adb shell, by adb install etc).
I am using ubuntu 10.10
Rebooting to bootloader runs properly using
Code:
adb reboot bootloader
when I try
Code:
fastboot oem unlock
it says
Code:
'< waiting for device >'
and does nothing (I have been waiting for 10 minutes now).
Code:
adb devices
does not show the xoom listed (it did before rebooting to bootloader)
Code:
fastboot devices
also does not list any devices
I have tried rebooting with the hardware method as well (plugged into the computer and not plugged into the computer.
Killing and starting the adb server doesn't help either.
I would appreciate any guidance on the issue. I will post if I find a fix somewhere else.
Click to expand...
Click to collapse
Did u try to do a adb remount then try adb devices
Thanks for the help, I had not tried to remount.
If I remount before booting to bootloader it tells me that the operation is not permitted (Expected - I haven't been able to unlock it yet)
if I try it while I am waiting for fastboot to connect, it it says
Code:
error: device not found
.
CoatedMoose said:
Thanks for the help, I had not tried to remount.
If I remount before booting to bootloader it tells me that the operation is not permitted (Expected - I haven't been able to unlock it yet)
if I try it while I am waiting for fastboot to connect, it it says
Code:
error: device not found
.
Click to expand...
Click to collapse
Did u download motohelper drivers so your adb will recognize the device
if the xoom is in fastboot adb wont recognize it hold power and volume up to reboot and try again
The xoom is recognized already. I am able to send the adb reboot bootloader command. When the xoom is trying to load into fastboot, it is not visible, which makes it impossible to enter the oem unlock command.
I gave up on the device, I was having issues with geolocation as well which didn't exist on another device. I returned the device and am waiting to receive the 3g version from the US.
I have the same problem. Does anyone know how to get around this?
Sent from my Xoom using XDA Premium App
If when you can run the adb reboot bootloader command and don't get fastboot to work, then as yet I have not found a solution. Instead I just returned it and ordered the 3g version from verizon and had it shipped. The commands worked fine. If you cannot use the adb command to reboot, then check the instructions for installing adb and fastboot and/or post the error messages you are getting.
On a side note, where did you get your xoom (country/store etc). I wonder if it is a problem with a certain batch, or all the Canadian ones etc. I my wifi only version from bestbuy in Canada.
I'm having the same problem right now on my xoom.
I was preordered on Amazon and delivered to New York 3 weeks ago...
no solution as for now..
returning isn't an option for me, since I live in Poland :/
ok,
I've made two thing, not sure which one worked
1) added /etc/udev/rules.d/11-android.rules file with :
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
2) performed fastboot as root (I hate such obvious solutions)...
I'm not sure if you're using Windows or not but I didn't had any issues when I used fastboot. Just need to make sure you have the drivers installed, and when you do adb reboot bootloader check the device list to make sure it still shows your device listed in there and not as a question mark. If you don't see your device listed in the Device List or does show but with a question mark, double check to make sure you have the drivers installed or else fastboot will not work.
And don't bother trying to use adb when you're in the bootloader since adb will not work.
*** edited: just noticed now that you are using ubuntu 10.10 (I need to stop over reading stuff). Can't remember how the drivers aspect works in Linux since it's been forever since I've used a Linux flavor but you will still want to make sure you have the correct drivers installed or make the changes that niematunikogo did and see if that worked.
niematunikogo said:
ok,
I've made two thing, not sure which one worked
1) added /etc/udev/rules.d/11-android.rules file with :
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0666"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
2) performed fastboot as root (I hate such obvious solutions)...
Click to expand...
Click to collapse
niematunikogo,
I am having the same problem you had but I don't understand exactly what you did here. Is there any way you can explain this for me? Thanks
rrainz said:
niematunikogo,
I am having the same problem you had but I don't understand exactly what you did here. Is there any way you can explain this for me? Thanks
Click to expand...
Click to collapse
before typing all the commands, first type "sudo su". adb and fastboot both need to be executed as root (adb actually works without root in case you already edited the USB rules before)
I had same problem but just returning device was not what I intended to do
niematunikogo said:
2) performed fastboot as root (I hate such obvious solutions)...
Click to expand...
Click to collapse
This worked for my Ubuntu, thanks!
I've unlocked the bootloader through the official HTC Dev website, and attempted to follow the procedure here: http://forum.xda-developers.com/showthread.php?t=1341127, however, ADB doesn't work very well.
I attempted to run "adb devices", and it recognises the phone, but says it's offline. When I tried to run zurgRush, it starts up the ADB daemon, and just sits there. Device manager doesn't show anything ADB related, I have unknown sources and USB Debugging enabled too... I have no idea how to get it working. My HD2 is much more well behaved... any suggestions would be welcome!
My XT912 recently experience an unfortunate drop and the interior display cracked but it seems to me that it still maintains digitizer functionality. I am currently running a custom ROM, eclipse 5.1 (http://forum.xda-developers.com/showthread.php?t=2434629) and am struggling to successfully use android screencast to operate my device.
To the best of my knowledge USB debugging should still be on with this device, I can't think of any reason why I would have disabled it since flashing the ROM a few months ago. However 'adb devices' just returns 'list of devices attached'. I have tried "adb kill-server" and "adb start-server" as well as different USB ports so this has led me to believe that USB debugging is disabled. (?)
When in recovery adb devices shows that i am in fact in recovery and i have full adb shell usage. I'm not sure if there is a way where i can use adb to turn on debugging or where my issue is.
Whether My phone is booted and running or if it is in recovery, screencast just gives me a white screen.
Any help is appreciated.
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
lolkidz said:
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
Click to expand...
Click to collapse
What is the phone booted into when you're entering the adb command? The phone is booted into Android or in recovery? If you're in bootloader you'll need to use fastboot commands. Such as fastboot devices
lolkidz said:
i have stock rooted moto g 4.4.2 i want to restore it to stock so i can update but it doesnt appear in adb devices. it does show up in device manager as motorola adb interface. adb is enabled on the phone. ive spent 2 nights googling and trying different stuff. i cannot get it to work. i have the same problem for a kindle fire 1st gen. but thats an unrelated note.
Click to expand...
Click to collapse
What os are you using on your PC? I had similar problems on Linux mint until I firgured out I had to add a line of code with the adb install
Sent from my Moto G using XDA Free mobile app
It doesnt show up when its booted into android, recovery or bootloader. I am running windows 7 home premium. Ive tried many different driver installers and nothing has worked.
ive just noticed also that when i have it connected and booted into recovery the driver "Android" couldnt be installed, but if its booted into android or bootloader the drivers are fine. i dont know what driver i should be installing for that, i went back and reinstalled my moto g drivers completely, i have philz touch recovery 6.55
lolkidz said:
ive just noticed also that when i have it connected and booted into recovery the driver "Android" couldnt be installed, but if its booted into android or bootloader the drivers are fine. i dont know what driver i should be installing for that, i went back and reinstalled my moto g drivers completely, i have philz touch recovery 6.55
Click to expand...
Click to collapse
I would suggest uninstalling whatever drivers you have installed. Disconnect your phone, uninstall drivers, restart, install drivers and connect your device then try again. When the phone is connected as mtp, adb, fastboot, it will install drivers for each type.
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/97326/p/30,6720,9050
i have done so and still to no avail. everything driver wise is working, but still the driver "Android" when in recovery could not be installed. still no trace of phone in adb devices when booted or fastboot devices when in bootloader.
lolkidz said:
i have done so and still to no avail. everything driver wise is working, but still the driver "Android" when in recovery could not be installed. still no trace of phone in adb devices when booted or fastboot devices when in bootloader.
Click to expand...
Click to collapse
Where did you DL the adb thing at? You could have a faulty adb download or just didn't install your correct api in the adb suite
Sent from my Moto G using XDA Free mobile app
Hi. This is the original HTC EVO 4G that I got from Sprint.
Model PC36100
Android 2.3.5 with, I think, HTC Sense, though it doesn't say that.
Baseband version 2.15.00.01.15
Kernel version 2.6.36.10-g8b16b68 [email protected] #1 (9/4/12)
Build number 5.07.651.6 71ORD
My goal is to install basic stock Android on it. Whatever version will work, be stable, and run smoothly, support basic wifi, social media, email, camera.
It runs pretty nicely as is, really. But I imagine it'd be cleaner with basic android and not all the Sprint and HTC stuff on it.
I'm trying to unlock the bootloader using a Windows 10 PC.
I have tried various sources for the drivers. Currently trying HTC Sync for the drivers but have tried all the others.
What I'm observing currently is this: In DEVICE MANAGER, the phone when running in its normal Android mode, it shows up as ANDROID USB DEVICES > MY HTC. and it's running cleanly (no yellow exclamation point). IN that mode, I can open my COMMAND prompt and use ADB DEVICES and ADB finds the device HT06MHL01565.
In order to do the UNLOCK BOOTLOADER, you have to connect the phone to the PC in Fastboot mode. When the phone is on the Fastboot screen, Windows Device Manager, adds a yellow exclamation point to "MY HTC" device. At that point using the command ADB DEVICES yields no devices found. So I cannot proceed to FASTBOOT OEM GET_IDENTIFIER_TOKEN. Windows isn't seeing the device when it's in Fastboot mode.
I do have USB Debugging enabled and have tried it with Fastboot both checked and unchecked in the Settings >> Apps page of Android on the phone.
So, to recap, when the phone is in Fastboot, the PC doesn't correctly identify it and the ADB DEVICES command yields nothing.
Hi,
XDA Assist is here to help navigate the site, not for support... And see you found your way already... http://forum.xda-developers.com/showthread.php?p=63479581#post63479581
:good: So I will close this thread.
Good luck!