Related
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!
Hi all,
I have unlocked my HTC ChaCha with htcdev but i cannot root it.
I followed this tutorial : http://forum.xda-developers.com/showthread.php?t=1525404
But when typing adb devices nothing appear
list of devices attached is empty
I have googled it and tried several solutions but still not work
1- update usb driver
2- enable disable enable debugging mode
3- adb kill-server then adb start-server
4- use pdanet and unlockroot software
nothing happened
when I connect the phone while it is switched on
i see :
SH19kv... device
any help.
I have headache from this problem.
OK solved
OK
I solved it
Thanks
not show chacha in when i type the adb list
DrZIZO said:
OK
I solved it
Thanks
Click to expand...
Click to collapse
please how did you solve it?
mohashyne said:
please how did you solve it?
Click to expand...
Click to collapse
I just continue as if it appears in the list and it did work!
sorry for the late reply.
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
Turn on developer mode
Turn on OEM unlock and USB debugging
Install LG drivers
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
Type adb devices and authorize your computer on the phone
Type adb reboot bootloader
Type fastboot devices and make sure your phone shows up
Type fastboot oem unlock
Type fastboot getvar all
Should say (bootloader) unlocked:yes
Type fastboot reboot
What's the purpose for an Unlock bootloader?
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
At this point, nothing. It's a prelude to rooting.
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
Try fastboot devices and reinserting the usb cable. Doesn't make sense that adb sees it but fastboot does not unless it's a different driver. I think fastboot driver differs actually so do that driver too.
Ubuntu
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
You can also load Ubuntu on a flash drive and boot your computer from the flash drive. Then run the commands.
https://www.ubuntu.com/
Cheers
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
cordell12 said:
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
Click to expand...
Click to collapse
Do you guys have the oem unlock option at least?
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
wing_addict_usa said:
Do you guys have the oem unlock option at least?
Click to expand...
Click to collapse
yup, even warns us that certain things won't work if we enable it. adb works just fine too
cordell12 said:
yup, even warns us that certain things won't work if we enable it. adb works just fine too
Click to expand...
Click to collapse
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
wing_addict_usa said:
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
Click to expand...
Click to collapse
It's quite possible the process of rooting will wipe the phone anyway.
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Click to expand...
Click to collapse
power device off, hold volume up and keep it down and plug in USB cord while it's connected to PC. I tried fastboot from download mode though. the logs do look interesting, wonder what a T-MOBILE device says
Double0EK said:
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
Click to expand...
Click to collapse
Yup, I did that. And then I get an error. Well, not an error, just a lack of response. fastboot devices returns nothing. I'm currently downloading the full sdk, on the theory that perhaps it's a problem with the installation of 'minimal adb and fastboot' I have.
---------- Post added at 08:07 PM ---------- Previous post was at 07:36 PM ----------
manufan721 said:
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you do anything specific after installing Android Studio to get it to install the drivers? Cos I've installed Android Studio, but am still having the same problem-fastboot devices returns nothing, and fastboot oem unlock hangs on <waiting for device>. I went into device manager and had it search the entire C: for drivers for the android bootloader interface, and it gave the same 'already up to date drivers' message as before I installed Android Studio.
EDIT- Even after installing the Google usb driver, no luck. Giving up for the weekend.
I'm a newbie, may I know have to fastboot from download mode?
having same issue just hangs at Fastboot oem unlock if anybody can help thanks in advance
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
Click to expand...
Click to collapse
[ 0.711817] ro.oem_unlock_supported=1 1=YES
did some digging into last_kmsg while trying to boot into bootloader (AT&T device) and found a reason it may not be allowing it.
http://forum.xda-developers.com/showthread.php?t=2708466
Its a start :good:
of course we need root in order to dd anything
LG issued a new driver update for the v20. Driver version is 4.1.1+. You can get the driver from the website.
Hi everyone,
Does anyone know how to open diagnostic mode on Moto G Stylus?
Unlike elder Moto devices there is not BP tool in recovery.
I also tried adb code
adb shell
su
until here worked fine and I granted permission from my phone.
setprop sys.usb.config diag,adb
this code did nothing.
My device is rooted btw.
barisny said:
Hi everyone,
Does anyone know how to open diagnostic mode on Moto G Stylus?
Unlike elder Moto devices there is not BP tool in recovery.
I also tried adb code
adb shell
su
until here worked fine and I granted permission from my phone.
setprop sys.usb.config diag,adb
this code did nothing.
My device is rooted btw.
Click to expand...
Click to collapse
Up!
noone?
Up!
Still couldn't find any solution.
This worked for me! Non rooted metro
Go into fastboot mode, then do ' oem config bootmode factory'
Hi guys,
Bit stuck, couldnt find a google thingy to help me out.
Setup:
W10 (also tried on Arch)
Latest version of platform tools
Tried multiple cables
No hub between computer and phone, straight to back of the motherboard
OEM Unlock > Enabled
USB Debugging > Authorised and remembered
adb devices gives a valid output
adb reboot bootloader > reloads to Fastboot Mode (the one with the red exclamation mark)
> bootloader version s5-0.2-6539975
NOS Production: yes
Device state: locked
on computer:
fastboot flashing unlock
< waiting for any device >
No prompt on phone, at all.
Also not working in fastbootd menu.
I followed along with the guides I found online, but no luck. Am I forgetting something stupid?
Any help would be appreciated.
Thanks ever so kindly.
Hi, I have had similar in the past when not using the latest ADB version.
Just double check you are up to date
To add: fastboot devices does not give output, however the computer does chime when connected.
minty1978 said:
Hi, I have had similar in the past when not using the latest ADB version.
Just double check you are up to date
Click to expand...
Click to collapse
Yeah, I'm on version 30.0.5 (November 2020)
I just had to ask nicely.
sudo fastboot flashing unlock worked.
This can be closed:
Lesson: run fastboot as root or as admin.