Database Info

ADB from Linux

I just got a refurbished Xoom wifi from woot.com. I am trying to access it via adb from my Ubuntu PC, but it doesn't seem to recognize it. I have followed the guides for the udev rules, and it works (to a degree). It seems that my PCIIDS may be different, and this may be the problem.
I previously owned a g-tablet and a Zenithink epad, and was able to access them through adb, after changing the udev rules.
I also want to root it, and I understand that it must be able to recognize it to do that. There seems to be three modes that you can start it up in, RSD, Fastboot and Android Recovery. I'm not sure if I should be in RSD or Fastboot for adb to work, but each mode gives a slightly different PCIID.
I do have a fastboot binary for Linux, but it too needs the PC to first "see" the Xoom.

For me, in opensuse
lsusb to see the constructor and id ( be careful the id change between normal mode, recovery and fastboot)
mine is :
In normal mode
Bus 002 Device 006: ID 22b8:70a8 Motorola PCS
with debug on
Bus 002 Device 006: ID 22b8:70a9 Motorola PCS
In Bootloader
Bus 002 Device 006: ID 18d1:708c Motorola PCS
In bootRSD
Bus 002 Device 006: ID 22b8:70a4 Motorola PCS
Edit or create your /etc/udev/rules.d/92-motorola-xoom.rules
to reflect the id's of your xoom
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a8", MODE="0666" SYMLINK+="xoom"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a9", MODE="0666" SYMLINK+="xoomdebug"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="18d1", SYSFS{idProduct}=="708c", MODE="0666" SYMLINK+="xoombootloader"
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", SYSFS{idVendor}=="22b8", SYSFS{idProduct}=="70a4", MODE="0666" SYMLINK+="xoombRSD"
Click to expand...
Click to collapse
restart udev or reboot
sudo /etc/init.d/boot.udev restart
And normally you should see your device with
adb devices

Thanks for the reply.
I have been trying something very similar. I don't believe that I can directly copy a SuSE version to use on Ubuntu, but it gives me some ideas.
Here is what worked for my g-tablet:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"
I think that was for mounting it to transfer files. I tried something like that for the Xoom IDs, but it didn't give me adb access.
I'll keep plugging away!

I finally got it to find it in adb. I'm not sure what did it, but rebooting the PC may have helped.
I am still not getting it to be seen by fastboot. I am following a How-To for rooting that first requires unlocking the bootloader. That is why I am trying to get fastboot to work.
If you know of a better way to root it, please advise me.
Thanks.

Just plug it when in fastboot and note the ID and constructor (mine change from 22b8 to 18d1 depending of the state) in that state and add it to your rules
reboot and try again

I've done that, with and without USB debugging enabled.
I think that the Linux versions of fastboot that I am trying may not be working. I am currently trying to install everything needed on my Win 7 laptop. The windows SDK includes fastboot, where the Linux version doesn't.

Ran it in windows and it is now performing the unlocking. It's disappointing that it isn't working in Linux.

I found another copy of Linux flashboot, from somewhere on the web. That one seems to work if I run it with root permissions (sudo). Otherwise I get this:
Code:
$ fastboot devices
no permissions fastboot
I'm not sure if tweaking the udev rules will fix this, but running it with sudo is no big deal. I'm just glad I got it to work.

[Q] Linux ADB and my GT 7+

For whatever reason, my GT 7+ is showing: ????????? offline/device when I run adb devices. I've tried running adb kill/start as root, still nothing. I've cycled "USB debugging". I'm running ubuntu 10.10. Every thing but adb is working but adb
Any insight or help would be helpful.

udev.
See: http://wiki.cyanogenmod.com/wiki/Udev

Answered
Here's the rule I put up in /etc/udev/rules/98-android.rules:
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666" #all samsung devices
Then restart udev and then restart adb and it's up!

This method is hard to remember. You can also start adb as root with:
adb start-server
and it should work that way, at least until adb is closed. You do not have to do all the adb commands as root, only the start.

Jason_25 said:
This method is hard to remember. You can also start adb as root with:
adb start-server
and it should work that way, at least until adb is closed. You do not have to do all the adb commands as root, only the start.
Click to expand...
Click to collapse
Why do you need to remember it? Create a udev rule once and you never have to deal with it again.
Running things as root should be avoided if possible.

I have found that there may be an issue with ubuntu 10.10 and this tablet. For me, it seems that the MTP crud is interfering with adb. If I freeze the MTP application on the tablet, I have no problem.
...and now it gets even stranger: If I boot ubuntu 10.10 in a virtual machine (vmware 8.x), its fine even with mtp enabled.
I haven't had any issue at all with my gentoo boot. (However, I've been trying to do the android development with ubuntu as it appears to be directly supported by google.)
(This really isn't an issue for me, as I actually prefer to keep MTP disabled so I don't get popups.)

Entropy512 said:
Why do you need to remember it? Create a udev rule once and you never have to deal with it again.
Running things as root should be avoided if possible.
Click to expand...
Click to collapse
Because I work on computers other than my own?
Because I have more than one computer?
Because I sometime reinstall the OS?
Because I don't have magical fail-proof hardware?
Because udev gets messed up and apt-get replaces the rules file?
This method is simpler for new users. The adb tools are straight from google so can be trusted and the udev approach just adds a lot of complexity.
edit:
garyd9 said:
I have found that there may be an issue with ubuntu 10.10 and this tablet. For me, it seems that the MTP crud is interfering with adb. If I freeze the MTP application on the tablet, I have no problem.
Click to expand...
Click to collapse
I do not seem to have any problem using 64-bit debian, which you probably know Ubuntu is based on. I have even built the AOSP with it without much trouble. Though, deploying it to a device is a different matter for me.

Fastboot does not find device [Zync Z930 tablet]

Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
Verifying connectivity with lsusb results in:
Code:
[email protected]:/home/badday/Downloads# lsusb
(...)
Bus 002 Device 011: ID [B]1b3f[/B]:8300 Generalplus Technology Inc.
So the device seems to be present. I also added /etc/udev/rules.d/51-android.rules with
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1b3f", ATTRS{idProduct}=="8300", MODE="0666", OWNER="badday"
and made sure that rights are correct:
Code:
[email protected]:/home/badday/Downloads# chmod a+r /etc/udev/rules.d/51-android.rules
[email protected]:/home/badday/Downloads# service udev restart
However, fastboot does not find the device:
Code:
[email protected]:/home/badday/Downloads# ./fastboot devices
[email protected]:/home/badday/Downloads# ./fastboot -i 0x1b3f getvar VERSION
< waiting for device >
As you can see I am running it as root. When booted normally, device is recognized (of course with different vendor ID etc.) with adb and I can make it boot to recovery mode, but not to bootloader mode. Trying to do so will result in a normal reboot (from what I can see).
Anyone having some idea?
Thanks a lot,
badday

root
badday2 said:
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
Verifying connectivity with lsusb results in:
Code:
[email protected]:/home/badday/Downloads# lsusb
(...)
Bus 002 Device 011: ID [B]1b3f[/B]:8300 Generalplus Technology Inc.
So the device seems to be present. I also added /etc/udev/rules.d/51-android.rules with
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="1b3f", ATTRS{idProduct}=="8300", MODE="0666", OWNER="badday"
and made sure that rights are correct:
Code:
[email protected]:/home/badday/Downloads# chmod a+r /etc/udev/rules.d/51-android.rules
[email protected]:/home/badday/Downloads# service udev restart
However, fastboot does not find the device:
Code:
[email protected]:/home/badday/Downloads# ./fastboot devices
[email protected]:/home/badday/Downloads# ./fastboot -i 0x1b3f getvar VERSION
< waiting for device >
As you can see I am running it as root. When booted normally, device is recognized (of course with different vendor ID etc.) with adb and I can make it boot to recovery mode, but not to bootloader mode. Trying to do so will result in a normal reboot (from what I can see).
Anyone having some idea?
Thanks a lot,
badday
Click to expand...
Click to collapse
Hey can you please guide me how did you root this device? I am having the same and I need to root it. Thanks.

badday2 said:
Hi there,
I am trying to access my device (Zync Z930 tablet) in fastboot mode. Therefore I started it by pressing Vol Up + Power until blue light appears and connect it to the PC (running Lubuntu 64bit).
... [CUT FOR SPACE] ...
Thanks a lot,
badday
Click to expand...
Click to collapse
I have the exact problem badday has, but with the Ainol Novo7 Paladin. Any help will be appreciated in my corner as well!

Unable to root Zync z930
I have the same need to root the Zync z930 tab, currently there is nothing available on the internet to root this tab. If anyone of you manages to crack it please let me know, thanks!
---------- Post added at 08:27 PM ---------- Previous post was at 08:22 PM ----------
I have the same need to root the Zync z930 tab, currently there is nothing available on the internet to root this tab. If you managed to crack it please let me know, thanks!

To clarify things: I did not root my device so far.

Some additional information I found out:
Try to reboot in adb via "reboot-bootloader" results in normal startup. Furthermore, booting to fastboot mode (with vol-up-button down) with Micro-SD-Card inserted makes the device not to appear any more in lsusb.
Anyway, that made me having even less clues than more :crying:

This is cheap chinese phone with an equally defective android implementation. The battery just lasts about an hour, I am sick of it.

abdulmomin said:
This is cheap chinese phone with an equally defective android implementation. The battery just lasts about an hour, I am sick of it.
Click to expand...
Click to collapse
Anyone found any method to root z930?

I'm not sure for linux but I think you will have to download drivers ,,,,,,,I had to do this for my computer (running win 7) to read my phone in fast boot
I downloaded an app called driver tools and that fixed it ....hope this helps
Ps : It maybe that your running 64 bit Os

@abdulmomin, jaydeepkhalpada: Rooting thread can be found here: http://forum.xda-developers.com/showthread.php?t=2028740
@fredworxz: Yes, I use a 64bit OS. However, for GNU/Linux drivers should not be needed as adb runs out of the box (please correct me if I am wrong).

Resolved! - See my post! http://forum.xda-developers.com/showthread.php?t=2045173
I've not only installed JB in Z930 but also successfully ADB'd it to root it
Here:
http://forum.xda-developers.com/showthread.php?t=2045173

Actually I cannot install the driver which might be some problem as I use 64bit OS and have no 32bit available. Anyhow, according to the name scheme, there should also be a 64bit version included.
Apart from that I have also problems with this Chinese software, does it need adb drivers to be installed? Actually when I boot in this mode with vol-up-button, there appears absolutely nothing in the device manager.
Would be great if you could help me out as I need this tablet for some sort of NGO project.
Greetings from Delhi,
badday

This is not fastboot mode
as your trying to unlock fastboot ,but this is not fastboot mode
this is for flashing firmware through G+massprotection tool..
There is no fastboot mode in Z930..
but you can goto recovery menu by pressing
1st press & release Power button then press and hold vol+ button

[Q] [ubuntu]Fastboot MotoG XT1033?

Android Noob here
I want to use fastboot on a softbricked Moto G (XT1033 last running OTA 5.0.2) on an Ubuntu 15.04 64 bit. However, I am not showing USB connected on the device in fastboot mode, and fastboot devices gives blank output (i.e. no devices detected), while it's recognized on Windows. The device is unlocked.
I have already installed fastboot using sudo apt-get install android-tools-fastboot
Created an anroid.rules file named ##-android.rules in /etc/udev/rules.d/. A persistent.rules file already existed with ##=70, so I used the same number for the android.rules file first. I also tried with ##=91, ##=50 and ##=51 after deleting the old files. None worked.
Tried all these variants in the android.rules file
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666", OWNER="plugdev"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", ATTRS{idProduct}=="2e76", MODE="0666", OWNER="plugdev"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="22b8", MODE="0666"
Restarted udev using service udev restart. Rebooting yeilded same effect.
using mfastboot v2 (found on xda forums) didn't help. Device was still undetected
Device doesn't show USB connected when connected to Ubuntu while in fastboot. It connects when using Windows.
How do I get fastboot working with my XT1033 on Ubuntu?
I did not enable USB debugging before the boot issues so I cannot use ADB. I just want to flash recoveries using fastboot/mfastboot.

tf300t fastboot vs usb cable

My problem is my tablet is visible in normal mode on my pc. Bootloader 4.2.1, The Device is unlocked ok. adb devices: #serie ok, and adb reboot-bootloader function works. The tablet will reboot into fastboot mode, but I am unable to find a driver that works on my pc. I installed 1.97 pc asus sync, google sdk, minimal adb fasboot driver, all indicates error code 10
"fastboot devices" does not work. Rck is on and the icon does not flashes, the fastboot reboot feature is '' Waiting for device ". So if I disconnect and reconnect the USB cable, the tablet will restart on the OS...
Even tried with a live linux cd and still the same problem...
Note my usb cable has been replaced by a generic for my original cable had become unstable.
It can be the cause of my problem. Of course I tested with 2 cables? Factory reset and unlocke with v7 and v8 apk, and also an OEM recovery to latest firmware 10.6.1.27.5-20130902
I would like to set up a recovery to try others Roms,
Thanks for your help.

cyborg3691 said:
I would like to set up a recovery to try others Roms,
Click to expand...
Click to collapse
First of all, your boot loader must end with 27.5. Check it out when you are unsure before you do anything more.
Then try to flash Kang TWRP from your SD Card with Terminal Emulator using the following code:
dd if=/sdcard/ twrp_tf300t_kang_2.8.7.2.img of=/dev/block/mmcblk0p4
For more information have a look at Josh’s thread http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479

For this soluce the tablet need to be root...
I have make this but not working, the terminal not see the file on sd card....
On terminal i see
[email protected]:/ $ su
[email protected]:/ # dd if=/sdcard/foo.img of=/dev/block/mmcblk0p4
/sdcard/foo.img cannot open for read: no such file or directory
1 [email protected]:/ #
help me

SOLUCE With another computer...
My problem was my computer z87 motherboard with incompatible usb port? I try front and rear usb ports,
with a generic usb cable, I have solutioned this problem, with a other old computer and minimal adb fastboot v. 1.3.1 with a netbook msi wind u100 runing xp and now, tf300t was detected in adb and fastboot mode the command devices works fine. I intall twrp and intall and try another rom.
Thanks for your help.