Root [TUTORIAL] ADB Workout Tutorial for Linux+Windows (100% working)

[ninadchaudhari]

in windows,
when i go to users/Name/ and try to create a folder named ".android"
it says u need to enter a name !

 

[akshaybz]

in windows,
when i go to users/Name/ and try to create a folder named ".android"
it says u need to enter a name !

.android should already be created by SDK Manager...
Btw, I saw stuff for mac on xda...
Don't remember the actual thread but try searching

 

[ninadchaudhari]

.android should already be created by SDK Manager...
Btw, I saw stuff for mac on xda...
Don't remember the actual thread but try searching

For mac i figured it out !
now its working

I asked the question for Windows this time

EDIT : Done

It did not work as while creating a virtual machine, Parallels created a user as "Ninad.Ninad-pc"
that "." is the problem !
you cannot have a dot or space in username ! lol hence all things over windows were unstable
I think, mastermind must add this

Btw i am feeling like a fool
All my developed stuff never worked ! I got frustrated and now i realize it was the Parallels fault

 

[ninadchaudhari]

BTW
@mastermind !
For mac i got it working

when i saw ur post ,
I felt one thing in common the adb_usb.ini folder !

I just entered the folder name in Spotlight and it found the folder !!
after watchhing in Finder, added the vendor number !
and it started working !

 

[mastermind1024]

in windows,
when i go to users/Name/ and try to create a folder named ".android"
it says u need to enter a name !

Windows don't allow to have a "." in file/folder name...
.android folder will be there already when u install sdk.
N like I said key point is adb_usb.ini file.!!!

 

[ninadchaudhari]

Windows don't allow to have a "." in file/folder name...
.android folder will be there already when u install sdk.
N like I said key point is adb_usb.ini file.!!!

Plz refer to few of my previos posts ...

 

[mastermind1024]

Plz refer to few of my previos posts ...

I don't get it...what u trying to convey???i have seen all previous posts then only replied.

 

[ninadchaudhari]

BTW
@mastermind !
For mac i got it working

when i saw ur post ,
I felt one thing in common the adb_usb.ini folder !

I just entered the folder name in Spotlight and it found the folder !!
after watchhing in Finder, added the vendor number !
and it started working !

I don't get it...what u trying to convey???i have seen all previous posts then only replied.

I think u can add this !
as I a going to refer this thread to any one !!!
on other forums !even

 

[ninadchaudhari]

Windows

Windows 7 -64Bit,
Yup i entered the unsecured stuff thing ...

 

[mastermind1024]

May be of 64bit only...i don't see that on my win7 32bit.may be Varun can help on this,he has win7 64bit.

 

[ninadchaudhari]

May be of 64bit only...i don't see that on my win7 32bit.may be Varun can help on this,he has win7 64bit.

Yup it is

lol

 

[mastermind1024]

Yup it is

lol

Try this drivers..I just checked them on my win7 64 bit n it got installed correctly without that error msg u posted above(screenshot)...
Original driver files from mmx did give me that error...
Try this n report back..
A70_Win7_64bit.zip

 

[sourru250]

was trying to install adb on ubuntu 12... text given by u for 99-android.rules didnt work for me,
so i referred other tutorial and filled it with following ...

SUBSYSTEM=="usb", ATTRS{idVendor}=="1d91:0009", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"

and it worked for me....

 

[mastermind1024]

was trying to install adb on ubuntu 12... text given by u for 99-android.rules didnt work for me,
so i referred other tutorial and filled it with following ...

SUBSYSTEM=="usb", ATTRS{idVendor}=="1d91:0009", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"

and it worked for me....

Well its obvious because whatever written in OP is for Ubuntu 11 or previous.
12 comes out just a month back so u need newer android rules.
Btw thanks for the update, i will add that to OP.

EDIT:
I have added udev rule for 'fastboot' too.As u r on ubuntu 12 can u just test it?

 

[sourru250]

I have added udev rule for 'fastboot' too.As u r on ubuntu 12 can u just test it?

yes tht worked...
i checked with d command "fastboot devices" ...
btw is it of any use for a70 except for installing recoveries ?

 

[D3odex3DAyusH]

Recently one of my friend asked for help about adb setup.....
I succeed in setting it up on his PC, but noticed one thing that adb doesn't recognize phone in recovery mode! Drivers are latest, sdk is updated too and everything is fine except this.......
Does any hv similar problem?? It just says device not found no matter however times you kill and recreate server!! It may be a problem with drivers, or with the cwm recovery, not supporting such functionality??

 

[urilabob]

Thanks, that was really helpful - I didn't find the key point,

mkdir -p ~/.android && echo 0x1d91 > ~/.android/adb_usb.ini && adb kill-server && adb devices

in any of the other places I checked. So I now have adb working, can get an adb shell etc. But I can't get

fastboot oem unlock

working - it just hangs <waiting for device>. Do you have any thoughts on this? I'm at my wit's end - the tablet goes into fastboot mode OK, but nothing comes up on the linux shell.

 

[mastermind1024]

Recently one of my friend asked for help about adb setup.....
I succeed in setting it up on his PC, but noticed one thing that adb doesn't recognize phone in recovery mode! Drivers are latest, sdk is updated too and everything is fine except this.......
Does any hv similar problem?? It just says device not found no matter however times you kill and recreate server!! It may be a problem with drivers, or with the cwm recovery, not supporting such functionality??

adb don't work on cwm recovery of A70...it's a recovery bug.

 

[mastermind1024]

Thanks, that was really helpful - I didn't find the key point,

mkdir -p ~/.android && echo 0x1d91 > ~/.android/adb_usb.ini && adb kill-server && adb devices

in any of the other places I checked. So I now have adb working, can get an adb shell etc. But I can't get

fastboot oem unlock

working - it just hangs <waiting for device>. Do you have any thoughts on this? I'm at my wit's end - the tablet goes into fastboot mode OK, but nothing comes up on the linux shell.

"fastboot oem unlock" is supported only on Google Nexus devices...
For fastboot u need to add another udev rule specific for tablet's fastboot hardware id...see the OP for reference, change hardware id in the rule with ur tablet's one.

 

[merryos]

Works on Ubuntu 12.04.4 LTS with a Xolo phone. Thanks!