Database Info

[Q] Rooting stuck at fastboot on xoom

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!

[Q] Help

I'm comming from the Samsung vibrant so im fairly new to nexus community. However I did find a couple tut. that were very good, I followed everything exactly as the person in the video. By the way the tutorial i used was from the Unlockr. But anyways i followed everything i set up adb my device appeared in the command prompt. However the next step once your phone is recognized when setting up adb is to power off and get into "fastboot". I did that, plugged the usb in and opened another command prompt. When i type in "fastboot oem unlock" it just hangs on the "waiting for device" part forever. Can someone please help me out thankx

You should really use a more descriptive title. I had no idea what this was about until the last sentence.
If you closed your terminal, than adb probably closed as well. Open up the cmd window while the phone is in fastboot and type
adb devices
Click to expand...
Click to collapse
That should start adb back up and let you know if the phone is detected in one command. It should then be ready for
fastboot OEM unlock
Click to expand...
Click to collapse
Sent from my Nexus S 4G "Lore"

[Q] problem with rooting and drivers

Hi,
I'm kind of a noob at this rooting stuff. I've looked ariund, done my research and everything but it never seems to go smoothly??..
I think the main problem is with the drivers. After following instructions the android drivers still said 'Android 1.0'. So I installed Pda net and then I got 'Android ADB Interface' drivers. Soo the thing is, after searching for 'adb devices' in cmd prompt, It says 'list of devices' but there's nothing in the list....?
For some reason it won't do any commands like 'adb reboot bootloader' or 'fastboot oem lock'. It says not found. I have installed all the sdk and packages...
Would really appreciate some help from you guys. I didn't think rooting would be so complex??...
Thanks

can you post screenshot??

Ok for some reason, after starting the cmd again today and typing adb devices, it has listed my device. But when I type 'fastboot oem lock' (because my bootloader is already unlocked) it says not found as shown in the screenshot.
Am I doing something stupid??...

70 views?... cant anyone help ... please..

soulja786 said:
70 views?... cant anyone help ... please..
Click to expand...
Click to collapse
If adb devices lists your device you're not in the boot loader, the ONLY place fastboot will recognize your device and function or you have a driver issue. You're either in recovery or booted up. Reboot into the boot loader to use fastboot.
If you get into the boot loader and fastboot still doesn't show your device it's a driver issue. Update the driver manually and point it to the SDK USB driver provided with the SDK.
For reference....
Booted into boot loader:
Fastboot OK
ADB NO
Recovery / Fully booted
Fastboot NO
ADB OK

Hi guys,
I really do think this is a driver issue... any idea on how to solve it? I do have PDA Net installed... ?
@krohnjw ... could you please clarify.. Im a bit lost.
Thanks!

Did you try something like oneclickroot?
http://forum.xda-developers.com/showthread.php?t=1138755

Well I also had a lot of issues trying to root my i9020t so let me try to help..
Phone will be recognized with ADB when u select enable debug on developer options. You ll see "Android ADB Interface" on SYS DRV.
On other hand , when U start phone on fasboot mode, it should install something like "Android Bootloader Interface " , if U keep seeing "Android ADB Interface" , its wrong, but took some time to realize that.
That happened to me when I was using WinXP x32 to root my phone, ironically thinking it would be more compatible an less prone to bugs... When done it on W7 x64 , my fastboot driver was discovered correctly (Android bootloader Interface) using x64 PDA drivers, and all went good then!
Hope this may help!

[Q] Fastboot problem

hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!

I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk

Did you try a fastboot command like fastboot devices?

Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.

Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz

ADB not seeing phone when in recovery

Hey everybody. I'm back from a long hiatus from rooting phones. I'm wanting to root my OP 8T, and adb is not seeing the phone when in recovery mode, so I can't even begin.
Win10, pretty sure drivers are up to date, adb up to date.
Computer and adb both see the phone when it's powered on normally, but I have to choose usb mode every time I plug it in. I suspect the adb not seeing it in recovery mode may have something to do with this, but I'm just guessing. I'm not sure how to overcome this. I know plenty of people have rooted this phone, so I don't get it.
Would be happy for any input on this issue. Idk where to go from here, and it's really frustrating, bc I'm excited to switch to this phone.
TIA

Have you tried checking Windows update when the phone is plugged in and in recovery mode? Do you have the Google fastboot drivers? Qualcomm drivers? OnePlus drivers? Are you using CMD or PowerShell for adb?

Zamkat said:
I'm wanting to root my OP 8T, and adb is not seeing the phone when in recovery mode, so I can't even begin.
Click to expand...
Click to collapse
yes, why should you? adb not available in recovery mode, expected behaviour.
Zamkat said:
I know plenty of people have rooted this phone, so I don't get it.
Click to expand...
Click to collapse
sure not from adb or recovery. did you mean fastboot? then boot phone into bootloader mode and install Android Bootloader Interface drivers.

alecxs said:
yes, why should you? adb not available in recovery mode, expected behaviour.
sure not from adb or recovery. did you mean fastboot? then boot phone into bootloader mode and install Android Bootloader Interface drivers.
Click to expand...
Click to collapse
It's been so long since I did this...I don't remember much about the procedure. I was just following the instructions. It said to turn it off, and then hold down and power to boot into fastboot mode. Then to connect it and type the reboot bootloader cmd.
I am using powershell.
These instructions aren't very good, I realize now. -_-
I guess I don't have the fastboot drivers...I'll try to get those and make another attempt. Thanks, I'll get back to you.

the driver is included in the same android_winusb.inf where the ADB driver is. you just need to disable windows driver signature enforcement before trying to install.
once you see device in 'fastboot devices' proceed with bootloader unlocking.
T-Mobile get Unlock Code to Submit to OnePlus for unlock token
This took me way too long to figure out so Hopefully this will make it quicker for someone: OnePlus Help Page Dr. Mario said: fastboot oem get_unlock_code (Found ten pages in at...
forum.xda-developers.com

Okay, well, this will make things difficult. Am I missing something here...???

Okay, hang on, I think I found the right instructions to install the sdkmanager... Ugh.

not sure what you are trying, but to run fastboot commands either navigate with cd into platform-tools directory from cmd.exe or in powershell type the path to file like this:
Code:
.\fastboot devices

Zamkat said:
Okay, hang on, I think I found the right instructions to install the sdkmanager... Ugh.
Click to expand...
Click to collapse
So, I followed these instructions exactly, and it's saying that sdkmanager is not a thing that exists.
Awesome. Super useful instructions. I never thought simply putting the tools needed to root my phone on my computer would be such a colossal pain in the ass.

I have never used sdkmanager and I don't know how that would involved in bootloader unlocking or rooting. It is also not mentioned anywhere in this device forum.

Zamkat said:
So, I followed these instructions exactly, and it's saying that sdkmanager is not a thing that exists.
Awesome. Super useful instructions. I never thought simply putting the tools needed to root my phone on my computer would be such a colossal pain in the ass.
Click to expand...
Click to collapse
Please go back to post #6. as we can see you're in folder "platform-tools" (left side of the cursor in your PowerShell window). This folder contains the files "adb.exe" and "fastboot.exe" and some more.
As a normal Windows user you would try to start these .exe files with a double click. Don't try it because it won't start anything. These .exe files are not executables, they are binaries. To run them you need to enter "adb" or "fastboot". That's all.

You need to use this: https://developer.android.com/studio/releases/platform-tools
And LineageOS have a great installation document: https://wiki.lineageos.org/adb_fastboot_guide

According to the instructions, I need to use the Sdk manager to install the fastboot drivers.
In order to get that, I apparently need the command line tools.
In order to get those enabled/installed in sdk, I need the Sdk manager...??? I'm so confused.

BillGoss said:
You need to use this: https://developer.android.com/studio/releases/platform-tools
And LineageOS have a great installation document: https://wiki.lineageos.org/adb_fastboot_guide
Click to expand...
Click to collapse
Holy ****, thank you.
Okay, I am in Fastboot mode, and I'm getting ready to install Twrp, but...it says my Device State is locked. Does that mean my bootloader is not unlocked? Because it is supposed to be.

alecxs said:
I have never used sdkmanager and I don't know how that would involved in bootloader unlocking or rooting.
Click to expand...
Click to collapse
The Platform Tools are part of the Android SDK. But Google offers them also as a single download, excluded from the Android SDK:
It's not wrong to install the whole SDK. But it's too much if only 2 binaries are being used.

how did you unlock the bootloader without fastboot?

alecxs said:
how did you unlock the bootloader without fastboot?
Click to expand...
Click to collapse
I'm an idiot. I need to do that still.

Device isn't being seen by adb in fastboot. Any suggestions?

Fyi, you shouldn't have posted the question in this forum but in the q&a forum https://forum.xda-developers.com/f/oneplus-8t-questions-answers.11583/

@BillGoss thread is moved soon, thx for reporting.
@Zamkat no device is seen by adb in fastboot.