Related
Since there seems to be a number of people fighting to get ADB working with the NC on Win7-64 machines, I thought I'd start a dedicated thread to get to the bottom of this issue.
In my case, ADB is working from my laptop but not my desktop. At various stages I have different devices, including an "Android Composite ADB Interface" and and "Android ADB Interface". At no point does `adb devices` return anything.
Here's some bits that will hopefully be helpful in troubleshooting.
Without the drivers installed (more accurately, with them uninstalled and deleted), I have the following devices in Device Manager:
Code:
Other devices -> Nook
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_01
USB\VID_2080&PID_0002&MI_01[/INDENT]
Universal Serial Bus controllers -> USB Composite Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002[/INDENT]
Universal Serial Bus controllers -> USB Mass Storage Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_00
USB\VID_2080&PID_0002&MI_00[/INDENT]
Could someone with a working ADB under Win7-64 uninstall their drivers and post the above information? If it's the same, could you zip your usb_drivers dir and upload that?
ADB version from SDKr08:
Code:
C:\>adb version
Android Debug Bridge version 1.0.26
ADB logcat with debug all:
Code:
C:\>set ADB_TRACE=all
C:\>adb -d logcat
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
_adb_connect: shell:export ANDROID_LOG_TAGS="" ; exec logcat
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x28dcd2 4: 30303132 0012
writex: 101 ok
writex: 101 0x28dc92 18: 686f73743a7472616e73706f72742d75 host:transport-u
writex: 101 ok
Switch transport in progress
readx: 101 0x28dc57 4
readx: 101 ok: 4641494c FAIL
readx: 101 0x28dc57 4
readx: 101 ok: 30303130 0010
readx: 101 0x4221a0 16
readx: 101 ok: 646576696365206e6f7420666f756e64 device not found
adb_close: 101(lo-client:5037)
Switch transport failed
- waiting for device -
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 102
writex: 102 0x28baf7 4: 30303063 000c
writex: 102 ok
writex: 102 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 102 ok
readx: 102 0x28ba77 4
readx: 102 ok: 4f4b4159 OKAY
readx: 102 0x28bb34 4
readx: 102 ok: 30303034 0004
readx: 102 0x28bb34 4
readx: 102 ok: 30303161 001a
adb_close: 102(lo-client:5037)
_adb_connect: host-usb:wait-for-usb
socket_loopback_client: port 5037 type tcp => fd 103
writex: 103 0x28baf7 4: 30303135 0015
writex: 103 ok
writex: 103 0x28cc01 21: 686f73742d7573623a776169742d666f host-usb:wait-fo
writex: 103 ok
readx: 103 0x28ba77 4
readx: 103 ok: 4f4b4159 OKAY
readx: 103 0x28bb97 4
Again, if we can get a working environment's output, that would be great.
Those who are having the same problem, post the results of the above command here, too. Don't forget the `set ADB_TRACE=all`. We can see if there's any differences in the behavior in the non-working envs.
I should note that some people have been successful by removing and deleting the drivers, un/re-plugging the NC and letting Windows auto-install the drivers (if I'm understanding the process).
edison said:
Since there seems to be a number of people fighting to get ADB working with the NC on Win7-64 machines, I thought I'd start a dedicated thread to get to the bottom of this issue.
In my case, ADB is working from my laptop but not my desktop. At various stages I have different devices, including an "Android Composite ADB Interface" and and "Android ADB Interface". At no point does `adb devices` return anything.
Here's some bits that will hopefully be helpful in troubleshooting.
Without the drivers installed (more accurately, with them uninstalled and deleted), I have the following devices in Device Manager:
Code:
Other devices -> Nook
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_01
USB\VID_2080&PID_0002&MI_01[/INDENT]
Universal Serial Bus controllers -> USB Composite Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002[/INDENT]
Universal Serial Bus controllers -> USB Mass Storage Device
[INDENT]Hardware Ids:
USB\VID_2080&PID_0002&REV_0216&MI_00
USB\VID_2080&PID_0002&MI_00[/INDENT]
Could someone with a working ADB under Win7-64 uninstall their drivers and post the above information? If it's the same, could you zip your usb_drivers dir and upload that?
ADB version from SDKr08:
Code:
C:\>adb version
Android Debug Bridge version 1.0.26
ADB logcat with debug all:
Code:
C:\>set ADB_TRACE=all
C:\>adb -d logcat
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
_adb_connect: shell:export ANDROID_LOG_TAGS="" ; exec logcat
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x28dcd2 4: 30303132 0012
writex: 101 ok
writex: 101 0x28dc92 18: 686f73743a7472616e73706f72742d75 host:transport-u
writex: 101 ok
Switch transport in progress
readx: 101 0x28dc57 4
readx: 101 ok: 4641494c FAIL
readx: 101 0x28dc57 4
readx: 101 ok: 30303130 0010
readx: 101 0x4221a0 16
readx: 101 ok: 646576696365206e6f7420666f756e64 device not found
adb_close: 101(lo-client:5037)
Switch transport failed
- waiting for device -
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 102
writex: 102 0x28baf7 4: 30303063 000c
writex: 102 ok
writex: 102 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 102 ok
readx: 102 0x28ba77 4
readx: 102 ok: 4f4b4159 OKAY
readx: 102 0x28bb34 4
readx: 102 ok: 30303034 0004
readx: 102 0x28bb34 4
readx: 102 ok: 30303161 001a
adb_close: 102(lo-client:5037)
_adb_connect: host-usb:wait-for-usb
socket_loopback_client: port 5037 type tcp => fd 103
writex: 103 0x28baf7 4: 30303135 0015
writex: 103 ok
writex: 103 0x28cc01 21: 686f73742d7573623a776169742d666f host-usb:wait-fo
writex: 103 ok
readx: 103 0x28ba77 4
readx: 103 ok: 4f4b4159 OKAY
readx: 103 0x28bb97 4
Again, if we can get a working environment's output, that would be great.
Those who are having the same problem, post the results of the above command here, too. Don't forget the `set ADB_TRACE=all`. We can see if there's any differences in the behavior in the non-working envs.
I should note that some people have been successful by removing and deleting the drivers, un/re-plugging the NC and letting Windows auto-install the drivers (if I'm understanding the process).
Click to expand...
Click to collapse
Attached is my usb_drivers folder from my working Windows 7 Pro x64 installation.
Note that this is the same usb driver zip from the nookcolor portal (http://nookdevs.com/NookColor_USB_ADB) under the 'windows' section, just with the necessary B&N product lines already added.
It's working!
Unfortunately, I'm not 100% sure which step I did make it work, but I list everything I can recall.
I'll first answer a few of my own questions in the hopes it'll help others.
Output of `adb -d logcat`:
Code:
C:\>adb -d logcat > logcat.txt
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
_adb_connect: shell:export ANDROID_LOG_TAGS="" ; exec logcat
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x28dcd2 4: 30303132 0012
writex: 101 ok
writex: 101 0x28dc92 18: 686f73743a7472616e73706f72742d75 host:transport-u
writex: 101 ok
Switch transport in progress
readx: 101 0x28dc57 4
readx: 101 ok: 4f4b4159 OKAY
Switch transport success
writex: 101 0x28dcd7 4: 30303265 002e
writex: 101 ok
writex: 101 0x28dde1 46: 7368656c6c3a6578706f727420414e44 shell:export AND
writex: 101 ok
readx: 101 0x28dc57 4
readx: 101 ok: 4f4b4159 OKAY
I had to redirect to the txt file because the screen was filled with a bunch of the following lines:
Code:
I/ActivityManager( 822): Starting activity: Intent { flg=0x10000000 cmp=android/com.android.internal.app.UMSServerActivity }
D/DeviceManagerBroadcastReceiver( 1011): action (android.intent.action.BATTERY_CHANGED)
D/WifiService( 822): ACTION_BATTERY_CHANGED pluggedType: 0
I've attached the usb_drivers I used, although I can't see any difference in them and the ones I had before.
Now for the stuff I did in-between my first post and this one (from memory).
I plugged the USB cable directly into the ports on my motherboard, instead of my PCI-X internal USB2.0 card. This was in response to suggestions on the other Win7 thread that you remove USB hubs from the mix. I'll try again with it plugged into the card later and report back.
I should note that in order to do this, I had to unplug my HP Deskjet which has a card reader slot. I had two USB Mass Storage and USB Composite devices listed in Device Manager prior to removing this - one each for the NC and the HP. After the removal, only a single set. Dunno if it made any difference, but it's worth mentioning. I'll try it with that plugged in, too, and report back.
I uninstalled the 'Android Composite ADB Interface' from under 'Android phone' from Device Manager, without checking the "Delete driver software" box. Obviously at this point I had the drivers installed. To be honest, I can't recall which of the native (Nook, USB Composite Device, USB Mass Storage Device) I updated the drivers on, but I *believe* it was the "Nook".
After the above step, I unplugged the USB cable and plugged it back in. This was based on several suggestions to that effect. I repeated these two steps multiple times but nothing ever showed up in `adb devices`, so I tried rebooting.
During this and all subsequent reboots, I hit F8 on startup and selected the "Disable Driver Signature Enforcement".
Still nothing after the reboot, so I uninstalled the 'USB Composite Devices'. Windows informed me a reboot was required. Whoah! That was new!
After the 2nd reboot, Windows automatically installed drivers (presumably for the device I had just removed), but again required a reboot.
Since the required rebooting behavior was so different than previous attempts (none of which asked to boot), I tried `adb devices` again.
Nothing.
Drat!
Then I checked the c:\Users\edison\.android\adb_usb.ini file that I created yesterday. All it had was this!
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
I *know* I had inserted a single '0x2080' in the file with no spaces or CRs. I had double-, triple- and quadruple-checked that stinkin' file during the last two days of frustration and it always existed and contained the right string. Something had to have changed it, but I'm not sure what it was. At one point, I had run the SDK Manager (from \androidsdk) and removed the non-2.1-related packages, including the "USB drivers package, revision 4". That's my best guess for the culprit.
So I added the "0x2080" to the adb_usb.ini file (after the 3 existing commented lines) and `adb-remount` gave me the sought-after "remount failed: No such file or directory", after which `adb devices` listed my NC!
Woo.
Hoo.
FWIW, I don't know that `adb remount`, specifically, is necessary. I ran `adb kill-server`, then `adb start-server` afterwards and it worked that way as well. I think the key is restarting the server once everything else is in place.
Since there are SO many others having this exact problem, can those of you who are and who try these steps, record what you do and report back?
My guess is that rebooting without the signed drivers req, removing the 'USB Composite Device' and the subsequent reboots/auto driver installs is what worked.
I do want to clarify that I know my NC was properly rooted as I was able to sideload apks from my laptop. This was only an ADB issue on my PC. IMO, the best way to confirm your NC is rooted is to boot with the nooter SD card installed. If you get a standard nook boot process, it's not rooted. If the device shows up in Windows (as *anything*), but the screen stays blank, you're rooted. I was pretty careful on my SD boots, as per the guides, to wait long enough for the root to "take" (2 full mins).
I sincerely hope this helps as I've spent all of last night and today working on this and I hope to save as many others from the same rage-inducing frustrations as possible.
Thanks to everyone who has put in the effort to make this possible, and everyone who has stuck by the community and taken the time to help the rest of us out!
edison said:
It's working!
Unfortunately, I'm not 100% sure which step I did make it work
....
[*]Then I checked the c:\Users\edison\.android\adb_usb.ini file that I created yesterday. All it had was this!
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
I *know* I had inserted a single '0x2080' in the file with no spaces or CRs. I had double-, triple- and quadruple-checked that stinkin' file during the last two days of frustration and it always existed and contained the right string. Something had to have changed it, but I'm not sure what it was. At one point, I had run the SDK Manager (from \androidsdk) and removed the non-2.1-related packages, including the "USB drivers package, revision 4". That's my best guess for the culprit.
So I added the "0x2080" to the adb_usb.ini file (after the 3 existing commented lines) and `adb-remount` gave me the sought-after "remount failed: No such file or directory", after which `adb devices` listed my NC!
Woo.
Hoo.
[/B]
Click to expand...
Click to collapse
this is what fixed it, it is a known issue that when the sdk updates using the sdk manager it replaces the adb_usb.ini with this file. you can manually edit it or just run 'android update adb' in command prompt to fix it. just fyi
I've never had an issue with adb_usb.ini being altered. I always check it before another adb attempt.
I went through the lists posted in here and came up with the same result on my win 7 64 bit setup. Disabling driver signing, uninstalling usb composite as well as removing the android composite adb interface and reinstalling.
I still need a way to confirm my nooter img has written correctly. There is no way to confirm this other than following the steps very precisely.
It just gets me angry *kicks nook*.
I had the ini file get changed after I uninstalled the drivers and reinstalled them.
madsci73915 said:
I had the ini file get changed after I uninstalled the drivers and reinstalled them.
Click to expand...
Click to collapse
Un-/re-installed the drivers via Device Mangler or the SDK Manager?
moovius said:
I've never had an issue with adb_usb.ini being altered. I always check it before another adb attempt.
Click to expand...
Click to collapse
Same here. That's why I was so mystified when it changed this time.
moovius said:
I went through the lists posted in here and came up with the same result on my win 7 64 bit setup. Disabling driver signing, uninstalling usb composite as well as removing the android composite adb interface and reinstalling.
Click to expand...
Click to collapse
Remember, I was going from memory, which was pretty fried after the previous 12 hours of fiddling. There may be another combination or step I missed.
moovius said:
I still need a way to confirm my nooter img has written correctly. There is no way to confirm this other than following the steps very precisely.
Click to expand...
Click to collapse
Does your NC wake up to a blank screen when booting from the SD card?
To check the actual SD card, pop it back in your PC. It should have a regular 40MB FAT partition that Win7 can read. If you want, you can use DISKPART from the shell to verify the partition. It should go something like this:
Code:
C:\> DISKPART
DISKPART> list disk
DISKPART> select disk N <-- your SD card from the list above
DISKPART> list partition
You should see the 40MB partition listed, although I don't have a screen grab to show. I just reformatted my SD card 'cause the Kindle app requires one and I didn't have an extra spare, but I can either pick one up today or re-image it
moovius said:
It just gets me angry *kicks nook*.
Click to expand...
Click to collapse
Hang in there, moovius, we'll figure this out! I *completely* understand your frustration, but persistence and tenacity will pay off!
OOC, do you have another computer you can try this on?
edison said:
Hang in there, moovius, we'll figure this out! I *completely* understand your frustration, but persistence and tenacity will pay off!
OOC, do you have another computer you can try this on?
Click to expand...
Click to collapse
I had one of the guys from #nookdevs remoting my computer and even he was stumped.
I gave up on windows and downloaded Ubuntu Livecd:
1. From Ubuntu, I re-did the nooter img on the nook to make sure that it wasnt the issue behind all of this.
2. I spent 2-3 hours being instructed on how to work Ubuntu and run commands from the terminal. (That wiki really assumes a lot, it's hardly a step-by-step method, even this Linux expert was stumped with some of the instructions.)
3. Finally was able to see the nook with the adb device listing command.
4. Loaded z4 for Super User privileges, and added 5-6 more apps to test out.
5. Restarted my computer while playing around with the new programs on the nook.
6. Tried accessing the nook through win7 again, but no luck. Uninstalled the driver, etc, tried several things, still wouldnt work from windows. Tried from my win7 netbook also, but no dice.
Something either in my win7 installs or in my computer configurations is preventing communication between pc and nook color.
At least Ubuntu works.
pdanet
the drivers from pdanet seem to work just fine and will automatically install, never has used pdanet application though.
bg
http://www.junefabrics.com/android/
just download, don't buy, and install
moovius said:
3. Finally was able to see the nook with the adb device listing command.
Click to expand...
Click to collapse
Congrats! Glad to hear you were at least able to do it through Ubuntu. Would be nice to figure out your Win7 machine, but there may indeed be something funky with your install/machine.
moovius said:
At least Ubuntu works.
Click to expand...
Click to collapse
Hey Moovius, I just had something interesting happen.
I installed the NOOKdeveloper SDK and the android SDK Manager reported that ADP was updated and needed to be bounced. After that, I couldn't see or connect to my NC.
I ran the update again and it works. The Manager message mentioned updating ADB to support the device in the add-on package.
Might be worth a shot.
The SDK URL is http://www.barnesandnoble.com/nookcolor/developer/ - click on the "Add Add-on Site..." and slap it in there to get the SDK.
has anyone tried enabling the market with the autonook script? Im running Win7-64 and also had trouble rooting but got it to work. Cant figure this one out though. It either tells me I need to unmount my nook or that it can not write to the folder that the autonook file is in. Any help would be appreciated
jayman63 said:
has anyone tried enabling the market with the autonook script? Im running Win7-64 and also had trouble rooting but got it to work. Cant figure this one out though. It either tells me I need to unmount my nook or that it can not write to the folder that the autonook file is in. Any help would be appreciated
Click to expand...
Click to collapse
I've successfully run the autonook script over a dozen times under Win7-64. Other than a minor redirect issue (a ">" in the comments creates a "My" file), it's worked like a champ.
Have you ejected BOTH of the NC removable drives before running autonook? Have you tried running autonook as administrator?
1st post here.
Seems like basic problem but I cannot get adb connected to my G1.
I started off on process of upgrading to CM 6.1 but when I was about to put recovery image on phone I discovered flash_image program was not found. Then set off on the adb route but am now stuck. Tried searching but not found answer. Here is what I have done/tried so far:-
PC is XP Pro SP3
G1 V1.6 rooted via Universal method (su works ok via Term)
Downloaded and installed latest SDK in c:\Android-sdk
USB debugging is enabled on phone
SD card is not mounted
When I run "adb devices" (from C:\android-sdk\platform-tools) it fails with
msg "error: protocol fault (no status)"
The basic usb connection to PC is known to be working ok (have copied files to phone sd card etc. no problem if I mount it)
The installation of usb drivers seemed to go ok although I had to do it manually from folder \android-sdk\google-usb_driver
When I look at usb devices with USBDeview there are 3 related to Android phone (all enabled).
1. HTC Android phone usb device (connected)
2. USB Mass storage device (not connected)
3. Android composite ADB interface (not connected)
Further info...
I see other people have had the same problem (with other phones as well) but cannot find any specific reason or fix that works.
I have reinstalled latest sdk rev08
Unintsalled and reinstalled latest google usb drivers (ver 4) endless times
Usb driver install appears to all go ok
In XP Device Manager I get Android Phone device which expanded shows single Android Composite Interface Device which has staus enabled and working ok
I have no "Other" usb devices etc. showing up in Device Manager
USBDeview shows 3 usb devices for Android phone. The connected one shows the htc serial no. The ADB composite interface is not connected and has no serial number.
I have tried different usb ports, cables, and another standard G1 phone - all gives same results
I noticed the adb_usb.ini file had no device id in it, I ran "update adb" as per comment note at top of adb_usb.ini but still got not entries in file.
Someone surely must have solution to this. I cannot believe a G1 phone does not work/been tested with sdk adb.
Maybe some source code guru can tell me under what conditions adb gives the "protocol error: no status" msg.
Or could someone with a working G1 adb usb connection post their adb_usb.ini etc.
Have spent 2 days on and off fiddling with this sdk now. :-(
Thanks
Further info on problem:-
After cleaning up windows registry and driver remnants I noticed that very occasionally the adb devices command would actually return the connected device.
I did some tracing of adb actions by setting the adb_trace=all variable.
The traces at bottom of this post show a failed "adb devices" request and a successful one.
Interestingly I noticed that if adb server is started with trace mode on (see below) then subsequent "adb devices" commands will work correctly even if trace mode is turned off (set adb_trace=blank) straight after the start command has completed.
It would appear there is some sort of timing relate problem in adb which is masked when trace is on?
C:\>set adb_trace=all
C:\>set adb_trace=all
C:\>adb start-server
_adb_connect: host:version
socket_loopback_client: could not connect to tcp:5037
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\>set adb_trace=
C:\>adb devices
List of devices attached
HT843KV06347 device
FAILED TRACE:-
C:\>adb devices
adb_query: host:devices
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 100
writex: 100 0x22dce7 4: 30303063 000c
writex: 100 ok
writex: 100 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 100 ok
readx: 100 0x22dc67 4
readx: 100 0 No error
adb_close: 100(lo-client:5037)
error: protocol fault (no status)
SUCCESSUL TRACE:-
C:\>adb devices
adb_query: host:devices
_adb_connect: host:version
socket_loopback_client: port 5037 type tcp => fd 100
writex: 100 0x22dce7 4: 30303063 000c
writex: 100 ok
writex: 100 0x41d3ed 12: 686f73743a76657273696f6e host:version
writex: 100 ok
readx: 100 0x22dc67 4
readx: 100 ok: 4f4b4159 OKAY
readx: 100 0x22dd24 4
readx: 100 ok: 30303034 0004
readx: 100 0x22dd24 4
readx: 100 ok: 30303161 001a
adb_close: 100(lo-client:5037)
_adb_connect: host:devices
socket_loopback_client: port 5037 type tcp => fd 101
writex: 101 0x22dce7 4: 30303063 000c
writex: 101 ok
writex: 101 0x22ee11 12: 686f73743a64657669636573 host:devices
writex: 101 ok
readx: 101 0x22dc67 4
readx: 101 ok: 4f4b4159 OKAY
readx: 101 0x22ddc7 4
readx: 101 ok: 30303134 0014
readx: 101 0x4c28c8 20
readx: 101 ok: 48543834334b56303633343709646576 HT843KV06347.dev
adb_close: 101(lo-client:5037)
List of devices attached
HT843KV06347 device
As i am planning to retire ( actually retiring isn’t at all possible ... does it ?) , i am creating this thread for all new devs who want to port new Roms and projects and other users on XDA who want som of their liked projects to be ported to any samsung galaxy device ( as i am expert on this )...
Here in this thread u can ....
1. Make new request for any project u like to be ported to Galaxy devices ...
2. Can ask any question regarding compiling Roms and for kernel development i am asking Ryuinferno to help me out
3. Can paste any error u got and will try to solve with my all Guts ...
4. List will be updated ...
So welcome to development world guys
Project Request and Hall Of Fame dev of The Week
1. Port New Insomnia Rom
NOTICE: I'm beginning to see this tutorial on numerous other sites. I'm fine with it being posted on other sites, as long as I am given credit and have your thread point back to here for the pieces that I have specifically written. I do not condone near verbatim or verbatim copy and pasting of my work or others work without credit. Please give credit where credit is due. Thank you.
1) You need the following:
-JDK 6 if you wish to build Jellybean.
Code:
Code:
$ sudo apt-get install openjdk-6-jdk
-Python, which you can download from python.org. Or:
Code:
Code:
$ sudo apt-get install python
-Git, which you can find it at git-scm.com. Or:
Code:
Code:
$ sudo apt-get install git-core
-Android SDK:
Download the SDK here: http://developer.android.com/sdk/index.html
Extract the SDK and place it in your home directory.
I renamed my SDK to android-sdk to make it easier to navigate to.
Go to your home folder, press Ctrl+H to show hidden files, and open up your .bashrc file.
Add these lines at the bottom of the file:
Code:
Code:
# Android tools
export PATH=${PATH}:~/android-sdk/tools
export PATH=${PATH}:~/android-sdk/platform-tools
export PATH=${PATH}:~/bin
Find your .profile file and add this at the bottom of the file:
Code:
Code:
PATH="$HOME/android-sdk/tools:$HOME/android-sdk/platform-tools:$PATH"
You have now successfully installed the Android SDK.
To check for updates issue this into your terminal:
Code:
Code:
$ android
2) Install required packages.
Code:
Code:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils xsltproc
On Ubuntu 10.10:
Code:
Code:
$ sudo ln -s /usr/lib32/mesa/libGL.so.1 /usr/lib32/mesa/libGL.so
On Ubuntu 11.10:
Code:
Code:
$ sudo apt-get install libx11-dev:i386
Building on Ubuntu 12.04 is currently only experimentally supported and is not guaranteed to work on branches other than master.
Code:
Code:
$ sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev x11proto-core-dev \
libx11-dev libreadline6-dev libgl1-mesa-glx \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3) Configure your USB.
Code:
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
Inside of this blank text file insert:
Code:
Code:
#Acer
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
#ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0666"
#Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
#Foxconn
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
#Garmin-Asus
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
#Google
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
#HTC
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
#Huawei
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
#K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0666"
#KT Tech
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0666"
#Kyocera
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
#Lenevo
SUBSYSTEM=="usb", ATTR{idVendor}=="17EF", MODE="0666"
#LG
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
#Motorola
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
#NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0666"
#Nook
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0666"
#Nvidia
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
#OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0666"
#Pantech
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
#Philips
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0666"
#PMC-Sierra
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0666"
#Qualcomm
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666"
#SK Telesys
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0666"
#Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
#Sharp
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
#Sony Ericsson
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
#Toshiba
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0666"
#ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
4) Save the file and close it and then issue this command:
Code:
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
5) Install the repo:
Code:
Code:
$ mkdir ~/bin
$ PATH=~/bin:$PATH
$ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
6) Initialize the repo:
Code:
Code:
$ mkdir WORKING_DIRECTORY
$ cd WORKING_DIRECTORY
6a) For AOSP:
Code:
Code:
$ repo init -u https://android.googlesource.com/platform/manifest -b android-4.3.1_r1
For CM:
Code:
Code:
$ repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
6.1) For people who have already done a repo init:
Code:
Code:
$ cd WORKING_DIRECTORY
AOSP:
Code:
Code:
$ repo init -b android-4.3_r2
$ repo sync
CM:
Code:
Code:
$ repo init -b cm-10.2
$ repo sync
7) When prompted, enter your real name and email address.
8) Gather the files:
Code:
Code:
$ repo sync
9) Continue onto adding a device
~How To Add A Device To The List~
1) Find the github for your device you wish to add. (For me it is the Samsung Epic 4G Touch [codename d710])
2) Now navigate to the location you are going clone the device tree to:
Code:
Code:
$ cd WORKING_DIRECTORY/device
$ mkdir samsung
3) Clone the github device tree from remote to local: (The name after the branch would be whatever you want that folder to be named so make sure it is whatever standard name would be for your device, example: Nexus One [passion], Nexus S [crespo] [inc], etc.)
Code:
$ git clone git://github.com/CyanogenMod/android_device_samsung_i9100g.git -b cm-10.2
4) Now navigate into the folder:
Code:
$ cd i9100g
5) Connect phone to computer and make sure USB debugging is enabled and you have adb set up.
6) Extract Device Proprietary Files:
Code:
$ ./extract-files.sh
Or:
Code:
./proprietary-files.sh
Or: See if other repos have your device's proprietary blobs already (like i9100g):
Code:
HTML:
$ ~/WORKING_DIRECTORY
$ mkdir vendor
$ git clone https://github.com/TheMuppets/proprietary_vendor_samsung -b cm-10.2 samsung
6.1) Some devices have other dependencies like a common device repo. The i9100g utilizes a omap4-common repo for the galaxys2 family of devices. Clone that repo. From inside the samsung folder:
Code:
$ cd ..
$ git clone git://github.com/CyanogenMod/android_device_samsung_omap4-common.git -b cm-10.2 omap4-common
OR simply u can create local_manifest.xml file in ur .repo folder
HTML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com/" />
<remote name="cm"
fetch="git://github.com/CyanogenMod/" />
<project path="device/samsung/i9100g" name="android_device_samsung_i9100g" remote="cm" revision="cm-10.2" />
<project path="device/samsung/omap4-common" name="android_device_samsung_omap4-common" remote="cm" revision="cm-10.2" />
<project path="kernel/samsung/t1" name="android_kernel_samsung_t1" remote="cm" revision="cm-10.2" />
<project path="vendor/samsung" name="TheMuppets/proprietary_vendor_samsung" remote="github" revision="cm-10.2" />
<project path="packages/apps/SamsungServiceMode" name="android_packages_apps_SamsungServiceMode" remote="cm" revision="cm-10.2" />
<project path="hardware/samsung" name="android_hardware_samsung" remote="cm" revision="cm-10.2" />
<project path="hardware/ti/omap4xxx" name="android_hardware_ti_omap4xxx" remote="cm" revision="cm-10.2" />
</manifest>
7) Navigate back to your home directory for building:
Code:
Code:
$ cd ~/WORKING_DIRECTORY
8) Prepare To Compile:
Code:
Code:
$ source build/envsetup.sh
Or:
Code:
Code:
$ . build/envsetup.sh
9) Get your list of devices:
Code:
Code:
$ lunch
10) Pick your poison.
11) Now compile ('#' being the number of cores in your processor +1):
Code:
Code:
$ make -j#
12) Speed up builds using ccache (optional, but highly recommended):
Edit your .bashrc and add this line at the bottom:
Code:
Code:
export USE_CCACHE=1
Then issue these commands:
Code:
Code:
$ export USE_CCACHE=1
$ export CCACHE_DIR=~/.ccache
$ prebuilts/misc/linux-x86/ccache/ccache -M 50G
The suggested cache size is 50-100G. (This is size in GB)
Or for a flashable zip:
Code:
Code:
$ make -j# otapackage
Or u can try :
$ . build/envsetup.sh && brunch i9100g (or ur device name here)
Reserved for kernel development
FAQs
I having error :
1.
Code:
[email protected]:~/liquid# . build/envsetup.sh
including vendor/liquid/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/liquid# lunch
You're building on Linux
Lunch menu... pick a combo:
1. liquid_d2att-userdebug 17. liquid_jflteusc-userdebug 33. liquid_solana-userdebug
2. liquid_d2mtr-userdebug 18. liquid_jfltevzw-userdebug 34. liquid_spyder-userdebug
3. liquid_d2spr-userdebug 19. liquid_jfltexx-userdebug 35. liquid_t0lteatt-userdebug
4. liquid_d2tmo-userdebug 20. liquid_l900-userdebug 36. liquid_t0ltetmo-userdebug
5. liquid_d2usc-userdebug 21. liquid_maguro-userdebug 37. liquid_t0lte-userdebug
6. liquid_d2vzw-userdebug 22. liquid_mako-userdebug 38. liquid_targa-userdebug
7. liquid_grouper-userdebug 23. liquid_manta-userdebug 39. liquid_toro-userdebug
8. liquid_i605-userdebug 24. liquid_maserati-userdebug 40. liquid_umts_spyder-userdebug
9. liquid_i9100-userdebug 25. liquid_mb886-userdebug 41. liquid_vigor-userdebug
10. liquid_i9100g-userdebug 26. liquid_m7ul-userdebug 42. liquid_xt897-userdebug
11. liquid_i9300-userdebug 27. liquid_m7att-userdebug 43. liquid_xt897c-userdebug
12. liquid_i9305-userdebug 28. liquid_m7spr-userdebug 44. liquid_xt907-userdebug
13. liquid_jflteatt-userdebug 29. liquid_m7tmo-userdebug 45. liquid_xt925-userdebug
14. liquid_jfltecan-userdebug 30. liquid_n7100-userdebug 46. liquid_xt926-userdebug
15. liquid_jfltespr-userdebug 31. liquid_n7000-userdebug
16. liquid_jfltetmo-userdebug 32. liquid_n8013-userdebug
Which would you like? [aosp_arm-eng] 10
ls: cannot access device/*/i9100g/liquid.mk: No such file or directory
build/core/product_config.mk:231: *** Can not locate config makefile for product "liquid_i9100g". Stop.
** Don't have a product spec for: 'liquid_i9100g'
** Do you have the right repo manifest?
[email protected]:~/liquid#
ANS : Actually mate u dont have prepared liquid.mk for i9100g device which should be having path :
Code:
$working_dir/device/samsung/i9100g/liquid.mk
Code:
#
# Copyright (C) 2012 The CyanogenMod Project
# Copyright (C) 2012 The LiquidSmooth Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# name
PRODUCT_RELEASE_NAME := GT-I9100G
# device
$(call inherit-product-if-exists, device/samsung/i9100g/full_i9100g.mk)
# gsm
$(call inherit-product, vendor/liquid/config/common_gsm.mk)
# phone
$(call inherit-product, vendor/liquid/config/common_phone.mk)
## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := i9100g
PRODUCT_NAME := liquid_i9100g
PRODUCT_BRAND := samsung
PRODUCT_MODEL := GT-I9100G
PRODUCT_MANUFACTURER := samsung
PRODUCT_PROPERTY_OVERRIDES += ro.buildzipid=liquid.i9100g.$(shell date +%m%d%y).$(shell date +%H%M%S)
# overrides
PRODUCT_BUILD_PROP_OVERRIDES += \
BUILD_NUMBER=I9100GXXLSR \
PRODUCT_NAME=GT-I9100G \
TARGET_DEVICE=I9100G \
TARGET_BUILD_TYPE=user \
BUILD_VERSION_TAGS=release-keys \
PRIVATE_BUILD_DESC="GT-I9100G-user 4.1.2 JZO54K I9100GXXLSR release-keys" \
BUILD_FINGERPRINT="samsung/GT-I9100G/GT-I9100G:4.1.2/JZO54K/I9100GXXLSR:user/release-keys"
2.
Code:
No private recovery resources for TARGET_DEVICE i9100g
build/core/tasks/kernel.mk:56: ***************************************************************
build/core/tasks/kernel.mk:57: * Using prebuilt kernel binary instead of source *
build/core/tasks/kernel.mk:58: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *
build/core/tasks/kernel.mk:59: * Please configure your device to download the kernel *
build/core/tasks/kernel.mk:60: * source repository to kernel/samsung/t1
build/core/tasks/kernel.mk:61: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building
build/core/tasks/kernel.mk:62: * for more information *
build/core/tasks/kernel.mk:63: ***************************************************************
make: *** No rule to make target `/home/black-prince/liquid/out/target/product/i9100g/kernel', needed by `/home/black-prince/liquid/out/target/product/i9100g/boot.img'. Stop.
ANS : Hey did u forgot to add kernel source , u must be... Check (for i9100g) path
Code:
$Working_dir/kernel/samsung/t1
Its repo must have been given in local_manifest.xm look or post no. 2 for more info ...
GIT BASICS
1. CREATING UR ACCOUNT ...
First go to github and sign up with COOL NAME ... ( Dont forgot to think over ur git user name thousand times , its most imp decision u ever take in ur development life )
Now once u have ur git account ready , fork the repository from any project u want ... e.g. i u want to fork this just fork
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Let the forking be completed ... Now u want changes to the repository u have forked , its obvious who dont
Now must imp thing to learn first is Cloning the git repository ... Go to ur fork repo in ur account ...
now copy SSH url ...
Open ur terminal , create working_dir
Code:
$mkdir working_dir
$cd working_dir
working_dir$git clone [email protected]:Black-Prince/android_device_samsung_i9100g.git (here instead of Black-Prince Ur git acc name with ur repo url)
We must add other repository from which we have to cherry pick or the other repository branch we have to merge ...
Code:
$ cd working_dir
working_dir$ ls
android_device_samsung_i9100g
working_dir$ cd android_device_samsung_i9100g
working_dir/android_device_samsung_i9100g$ git remote add slim git://github.com/SlimRoms/device_samsung_i9100g.git
working_dir/android_device_samsung_i9100g$ git fetch slim
remote: Counting objects: 801, done.
remote: Compressing objects: 100% (328/328), done.
remote: Total 728 (delta 337), reused 672 (delta 286)
Receiving objects: 100% (728/728), 247.18 KiB | 14.00 KiB/s, done.
Resolving deltas: 100% (337/337), completed with 35 local objects.
From git://github.com/SlimRoms/device_samsung_i9100g
* [new branch] jb -> slim/jb
* [new branch] jb4.2 -> slim/jb4.2
* [new branch] jb4.3 -> slim/jb4.3
working_dir/android_device_samsung_i9100g$ cherry pick and merge next time :P
HEIMDALL >>> ODIN ON LINUX/UBUNTU/MAC Flashing KERNEL
First thing i am going to mention here is , PLEASE CHECK THAT UR DEVICE SUPPORT HEIMDALL
Lets get started ...
1. Download Heimdall
For Ubuntu 64 bit version which i use i will download
A. ubuntu13.04-heimdall-frontend_1.4.0-0_amd64.deb
B. ubuntu13.04-heimdall_1.4.0-0_amd64.deb
Will install via software centre of Ubuntu and now we are ready ...
2. Download the cwm for ur device , for i9100g , i will use this
3. Extract , U will get zimage ...
4. Now copy this zimage to ur home folder
5. Open terminal , either u exucute the command for flashing kernel or cd to ur dir where u copy zimage
6. Press volume down+home+power button and go in download mode , attach via USB to ue laptop/desktop
7. type in terminal
$ sudo heimdall flash --KERNEL zimage
$ sudo heimdall flash --KERNEL boot.img
8. Note down here , i typed two dash - - before KERNEL [--KERNEL]
9. Wait for a min and ur done ...
10. U have successfully flashed new kernel/cwm/twrp
Wow, @Black_Prince you're great guy, we won't see people you too often, who share their skills the way you do, great work dude, much appreciated
Sent from my GT-I9100G using Tapatalk
Alipk52 said:
Wow, @Black_Prince you're great guy, we won't see people you too often, who share their skills the way you do, great work dude, much appreciated
Sent from my GT-I9100G using Tapatalk
Click to expand...
Click to collapse
Much more to come , git basics with cherry picking and merging skills too
with odin support guide on linux
Black_Prince said:
Much more to come , git basics with cherry picking and merging skills too
with odin support guide on linux
Click to expand...
Click to collapse
Yeah, and it will require basic linux knowledge, and linux operating system isn't?
Sent from my GT-I9100G using Tapatalk
Alipk52 said:
Yeah, and it will require basic linux knowledge, and linux operating system isn't?
Sent from my GT-I9100G using Tapatalk
Click to expand...
Click to collapse
Hmm a very little u knw , if i can do it anybody can ...
Any body can code
Black_Prince said:
Hmm a very little u knw , if i can do it anybody can ...
Any body can code
Click to expand...
Click to collapse
Sadly i don't have linux, can i still learn it? All i know is there's an box like app or something which runs as linux in windows, or either through standalone software which could be compatible with windows?
Alipk52 said:
Sadly i don't have linux, can i still learn it? All i know is there's an box like app or something which runs as linux in windows, or either through standalone software which could be compatible with windows?
Click to expand...
Click to collapse
Its called virtual machine , i never used it as i lft windows three yrs ago and never run even on dual boot
Thats wat i looking for...i never found such a fine tutorial...thnx bro
Sent from my GT-I9100G using xda app-developers app
for other devices follow this
****i am not responsible for your phone or anything you do with aircrack-ng
this guide will help you, do what a $1,295.00 PWN PHONE can!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
------------------------------------------------------------------------------------------------
Things You Need
------------------------------------------------------------------------------------------------
1) Nexus 5 (rooted)
2) OTG Cable
3) list of USB supported
.TP-LINK TL-WN722N(confirmed by me & DragonHunt3r)
.Linksys WUSB600N V2 (confirmed by DragonHunt3r)
.TP-LINK TL-WN725N V1 & V2
.ALFA Network AWUS036H
(if you have other wifi usb then just ask ill try to add it into the guide)
4) Ubuntu (to compile kernel)
------------------------------------------------------------------------------------------------
PART A
(Compiling Kernel)
------------------------------------------------------------------------------------------------
Setting up your ubuntu machine
Code:
$ sudo apt-get update
Code:
$ sudo apt-get install oracle-java6-installer
Code:
$ sudo apt-get install git gnupg ccache lzop flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z1-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc libreadline6-dev lib32readline-gplv2-dev libncurses5-dev bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev squashfs-tools pngcrush schedtool dpkg-dev
Code:
$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
Code:
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/
create a file /etc/udev/rules.d/51-android.rules (as the root user)
copy paste the below code and save
Code:
# adb protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"
# fastboot protocol on passion (Nexus One)
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"
# adb protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"
# fastboot protocol on crespo/crespo4g (Nexus S)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"
# adb protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"
# fastboot protocol on stingray/wingray (Xoom)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"
# adb protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
# fastboot protocol on maguro/toro (Galaxy Nexus)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"
# adb protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d002", MODE="0600", OWNER="<username>"
# fastboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="<username>"
# usbboot protocol on panda (PandaBoard ES)
SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="<username>"
# adb protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="<username>"
# fastboot protocol on grouper/tilapia (Nexus 7)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="<username>"
# adb protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="<username>"
# fastboot protocol on manta (Nexus 10)
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="<username>"
<username> must be replaced by the actual username of the user who is authorized to access the phones over USB.
Setting correct paths
Code:
gedit android-path.sh
cope paste the code and save it
Code:
export CC=$(pwd)/arm-eabi-4.6/bin/arm-eabi-
export CROSS_COMPILE=$(pwd)/arm-eabi-4.6/bin/arm-eabi-
export ARCH=arm
export SUBARCH=arm
export PATH=$PATH:$(pwd)/andorid_boot_tools_bin
Make it executable and source to current terminal window.
(you need to source it to your current terminal window before you compile)
Code:
$ chmod +x android-path.sh
$ source android-path.sh
Download Source (any kernel source can be used)
ElementalX Kernel Source
Franco.kernel Source
Android Kernel Source
using andoid kernel source
Code:
$ git clone https://android.googlesource.com/kernel/msm.git
Code:
$ cd msm/
$ git branch -a
$ git checkout origin/android-msm-hammerhead-3.4-kitkat-mr2
Code:
$ make hammerhead_defconfig
$ make menuconfig
Adding required drivers
For TP-LINK_TL-WN722N
Code:
quick look in [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN722N"]wikidev[/URL] will tell you that TP-LINK TL-WN722N uses [URL="http://wireless.kernel.org/en/users/Drivers/ath9k_htc"]ath9k_htc[/URL] drivers
Enabling [URL="http://wireless.kernel.org/en/users/Drivers/ath9k"]ath9k[/URL] drivers in kernel
To enable ath9k, you must first enable mac80211 through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable ath9k through make menuconfig.
[CODE]Networking support --->
Wireless --->
< * > cfg80211 - wireless configuration API
< * > Generic IEEE 802.11 Networking Stack (mac80211)
You can then enable ath9k in the kernel configuration under
Code:
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
Atheros Wireless Cards ---->
< * > Atheros 802.11n wireless cards support
< * > Atheros HTC based wireless card support
save and exit menuconfig
check in your .config file if you have them enable(its a hidden file)
Code:
CONFIG_ATH_COMMON=y
CONFIG_ATH9K_HW=y
CONFIG_ATH9K_COMMON=y
CONFIG_ATH9K_HTC=y
[/CODE]
For TP-LINK TL-WN725N V1 & V2
Code:
quick look in [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN725N_v1"]V1[/URL] & [URL="https://wikidevi.com/wiki/TP-LINK_TL-WN725N_v2"]V2[/URL] wikidev will tell you that TP-LINK_TL-WN725N uses [URL="http://wireless.kernel.org/en/users/Drivers/rtl819x"]rtl8192cu[/URL] & [URL="https://github.com/lwfinger/rtl8188eu"]8188eu[/URL] drivers
To enable rtl8192cu & 8188eu, you must first enable rtl8192cu & 8188eu through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rtl8192cu & 8188eu through make menuconfig.
[CODE]Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter
For Linksys WUSB600N V2
Code:
quick look in [URL="https://wikidevi.com/wiki/Linksys_WUSB600N_v2"]wikidev[/URL] will tell you that WUSB600N V2 uses [URL="http://wireless.kernel.org/en/users/Drivers/rt2800usb"]rt2800usb[/URL] drivers
To enable rt2800usb, you must first enable rt2800usb through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rt2800usb through make menuconfig.
[CODE]Device Drivers --->
[*] Network device support --->
Wireless LAN --->
Ralink driver support ---->
< * > Ralink rt27xx/rt28xx/rt30xx (USB) support -->
< * > rt2800usb - Include support for rt35xx devices (EXPERIMENTAL) (NEW)
< * > rt2800usb - Include support for unknown (USB) devices
For ALFA Network AWUS036H
Code:
quick look in [URL="https://wikidevi.com/wiki/ALFA_Network_AWUS036H"]wikidev[/URL] will tell you that AWUS036H uses [URL="http://wireless.kernel.org/en/users/Drivers/rtl8187"]rtl8187[/URL] drivers
Enabling [URL="http://wireless.kernel.org/en/users/Drivers/ath9k"]rtl8187[/URL] drivers in kernel
To enable rtl8187, you must first enable rtl8187 through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable rtl8187 through make menuconfig.
[CODE]Networking support --->
Wireless --->
< * > Common routines for IEEE802.11 drivers
< * > Generic IEEE 802.11 Networking Stack (mac80211)
You can then enable rtl8187 in the kernel configuration under
Code:
[CODE]
Device Drivers --->
[*] Network device support --->
Wireless LAN --->
[*] Realtek 8187 and 8187B USB support
save and exit menuconfig[/CODE]
save and exit menuconfig if you dint do it
now your ready to compile
Code:
make -j4
this will take some time to compile
you should get something like this in the end
Code:
Kernel: arch/arm/boot/zImage-dtb is ready
now you need to get a boot.img from any nexus 5 rom and place it in boot_img (create this folder where you earlier downloaded the toolchain and the kernel)
Code:
$ cd .. # if you was in msm directory
$ git clone https://github.com/pbatard/bootimg-tools.git
$ cd bootimg-tools/
$ make
$ cd cpio/
$ gcc mkbootfs.c -o mkbootfs -I../include
$ cd ../..
$ mkdir andorid_boot_tools_bin
$ cd andorid_boot_tools_bin/
$ cp ../bootimg-tools/mkbootimg/mkbootimg .
$ cp ../bootimg-tools/mkbootimg/unmkbootimg .
$ cp ../bootimg-tools/cpio/mkbootfs .
$ cd ..
time to create your own boot
Code:
$ unmkbootimg -i boot_img/boot.img
$ cp msm/arch/arm/boot/zImage-dtb kernel
$ mkbootimg --base 0 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x02900000 --second_offset 0x00f00000 --tags_offset 0x02700000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1' --kernel kernel --ramdisk ramdisk.cpio.gz -o boot.img
install the boot.img to your phone (this wont flash the kernel, it will temporarily boot with this kernel, after you restart you will go back to what ever kernel you had before
Code:
$ adb reboot bootloader
$ sudo fastboot boot boot.img
------------------------------------------------------------------------------------------------
PART B
(setting up your phone)
------------------------------------------------------------------------------------------------
For TP-LINK_TL-WN722N
Code:
download the firmware files [URL="http://wireless.kernel.org/download/htc_fw/1.3/"]here[/URL]
1. htc_7010.fw
2. htc_9271.fw
For TP-LINK TL-WN725N V1 & V2
Code:
Download the firmware files [URL="https://drive.google.com/folderview?id=0Bxm4XqSOJU3YWlVaZ1NFRDF4RTA&usp=sharing"]here[/URL]
For Linksys WUSB600N V2
Code:
Download the firmware files [URL="https://drive.google.com/folderview?id=0Bxm4XqSOJU3YMGZTcjJ2ei10V1k&usp=sharing"]here[/URL]
1. rt2870.bin
For ALFA Network AWUS036H
Code:
hopefully nothing to do here,... if it doesnt work let me know
copy them to your phone
use a file manager with root to copy firmware files to /system/etc/firmware/
install Linux deploy on your phone
fire up linux deploy and go to properties-->Distribution and select kali linux
installation path set to /sdcard/linux.img
hit the install button
after installation click start button
start your favorite ssh program and happy aircrack-ng
(SH credentials are “android” for the username (configured via Linux Deploy) and “changeme” as the password.)
hello ... how did you get those two lines of commands on the keyboard ?!
which command are you talking about?
you should use the commands one by one
chiragkrishna said:
which command are you talking about?
you should use the commands one by one
Click to expand...
Click to collapse
If I'm not mistaken, I believe he means your screen shot. In terminal with Ctrl, alt, etc above the keyboard.
you need to install aircrack-ng in kali
i am not going to guide you on how to use kali!! you have to figure it on your own!!
code used in that screenshot,
Code:
$ sudo airmon-ng
$ sudo airmon-ng start wlan1
chiragkrishna said:
you need to install aircrack-ng in kali
i am not going to guide you on how to use kali!! you have to figure it on your own!!
code used in that screenshot,
Code:
$ sudo airmon-ng
$ sudo airmon-ng start wlan1
Click to expand...
Click to collapse
Love this reply.Honestly if u don't know how then you should not be trying it
Sent from my Nexus 5 using Tapatalk
What does this do, get you better WiFi connection in terms of speed/stability?
Search aircrack-ng on Google, you're very far !
Sent from my Nexus 5 using XDA Free mobile app
GT-af said:
Search aircrack-ng on Google, you're very far !
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well..... It could, just not the way he was probably expecting
Pretty cool tut I must say, I'm wondering, could you make it support aswell the Wusb600n v2 ? that's what I'm currently having as usb wifi
added support for WUSB600N V2
this guide will help you, do what a $1,295.00 PWN PHONE can!!
chiragkrishna said:
added support for WUSB600N V2
this guide will help you, do what a $1,295.00 PWN PHONE can!!
Click to expand...
Click to collapse
Oh woow cool, will test this out when I'm home
Hopefully packet injections etc will work ^.^
parker09 said:
What does this do, get you better WiFi connection in terms of speed/stability?
Click to expand...
Click to collapse
Yes, it turns your Wi-Fi into a 1Gb/s power house regardless of the connection you're on.
To test do this:
1 - hook up your dial-up cable and modem/router/whatever
2 - connect your N5 to that network and try to open www.nike.com
3 - if it takes 10m to load, then you're on the correct network, 56k yay!
4 - flash this
5 - connect to your 56k network
6 - ???
7 - www.nike.com loads in 2s
8 - profit
-----
Nice guide OP
Testing it out right now but there seems togo something weird ?
SIOCSIFFLAGS: No such file or directory
I gave the .bin file privs 644 and when trying airodump it says
Gave wlan1 and mon0 for fun a try... but not working
Kill the processes
867
1263
867
These are the problems..
@chiragkrishna
You know man if it works with tp-link tl wn723n ou wn725n?
...
chiragkrishna said:
Kill the processes
867
1263
867
These are the problems..
Click to expand...
Click to collapse
Killed em and the message dissapeared but it's still not working ?
http://puu.sh/b0BBg/18d9bc170b.png <- click the image
Could the alfa awus036h be compatible in the future?
Orderd now the same as OP (TP-LINK TL-WN722N) and we'll see how it goes
Ive read several dozen threads and none of them seem to have the same problem.
Note: this is on ubuntu, and a nexus 6 (though I have tried a dozen different phones)
adb devices // can see my device
adb reboot-bootloader // works fine (in boot loader mode now)
sudo fastboot oem unlock // waiting for devices
Everything I try... its always <waiting on devices>
Things Ive tried:
I made sure usb debugging was enabled
Enable oem unlock is checked in dev settings
Its unlikely a driver issue as I compile android apps all the time and deploy them to the device. adb works fine also.
There is a step which can be done where you look up the phone and you add it to a file in /etc and restart udev (ive done that too), but my understanding is sudo fastboot should work just the same.
Have tried a ton of devices always... <waiting on devices>
Read a ton of trouble shooting articles on <waiting on devices> on xdaforums but none seem to fit my problem.
Any help would be greatly appreciated. I need to root devices for development at work.
I would say check drivers but you say you've already done this. but adb can function without proper fastboot drivers.
Maybe I am missing a driver.
I just purged my machine of fastboot, and did sudo apt-get install android-tools-fastboot
Re-running sudo fastboot oem unlock still results in <waiting on devices>
Is there any other driver I need to install?
Is there any way to verify if a running device is in fact in fastboot mode?
It'd look something like this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not much of a linux person so I'm not sure about any additional drivers.
Thanks! Yes It id definitely in fastboot mode then.
Now the question remains... why does it always show <waiting for devices> when I run sudo fastboot <insert any fastboot command>
Not real familiar with the ins and outs of Ubuntu (use Fedora myself) but I've always had better luck running ADB and fastboot as root than trying to use sudo. Also, do you need to be in a special group to use the USB hardware for fastboot, maybe??? Like I said, not real familiar with Ubuntu...
Also, is the USB port a USB 3 port? I've had problems like that on USB3 ports but when I switched over to the USB 2 port on the Lenovo, it worked fine. Also, make sure you have a good USB cable...had one that the DATA IN wire was broken... charged fine, could send out, never got anything back. Had another that came with some Bluetooth headphones that turned out to just be for charging, i.e., only POS and NEG connected on the plug, no data at all - near went crazy with that one because it looked just fine, nice and thick, no markings on it to indicate anything. Finally figured it out when I sliced the plastic cover off because I was so mad and figured it wasn't working anyway...only 2 wires inside! Good Luck!
First, you don't need sudo for fastboot.
Then when you switch to user root, you don't use the same environment, so it's possible the path is different, and you are using a different fastboot. If you type "which fastboot", and " sudo which fastboot" what do you get?
But anyway, why do you need sudo?
Sent from my Nexus 6 running cyosp using Tapatalk
gathem said:
adb devices // can see my device
adb reboot-bootloader // works fine (in boot loader mode now)
sudo fastboot oem unlock // waiting for devices
Click to expand...
Click to collapse
Did you try doing fastboot devices first?
istperson said:
First, you don't need sudo for fastboot.
Then when you switch to user root, you don't use the same environment, so it's possible the path is different, and you are using a different fastboot. If you type "which fastboot", and " sudo which fastboot" what do you get?
But anyway, why do you need sudo?
Sent from my Nexus 6 running cyosp using Tapatalk
Click to expand...
Click to collapse
Thanks!
I tried it as user root. Still < waiting for device >
I also tried
# fastboot devices // output: (just an empty line break)
# which fastboot // output: /usr/bin/fastboot
// (as normal user
#sudo which fastboot // output: /usr/bin/fastboot
I am pretty sure I had tested with a brand new usb cable a while back but will acquire another to test it.
Im not exactly sure on the type of cable/port. Its not an old linux desktop
Got a brand new cable and plugged in directly to the front of the desktop linux machine. I can copy files from the phones internal harddrive to my linux desktop so bi-directional communication is possible.
running fastboot oem unlock as root still results in < waiting for device >
Wanted to say... THANK YOU ALL so much for taking the time to help a random internet stranger get unblocked. I need this for work and I need to root 4+ phones but if I cant figure it out today I'm just going to find someone on craigslist to do it for me so I can get back to working on this project.
Maybe your fastboot is outdated. Download the most recent SDK, or even better, use it from the AOSP source. That's what I always do.
But you still shouldn't really need sudo for fastboot.
Have you set up the udev rules in /etc/udev/rules.d/ ? I usually call that file 99-android.rules and put in the necessary USB entries. Also I agree with making sure fastboot is up-to-date.
RMarkwald said:
Have you set up the udev rules in /etc/udev/rules.d/ ? I usually call that file 99-android.rules and put in the necessary USB entries. Also I agree with making sure fastboot is up-to-date.
Click to expand...
Click to collapse
I had them in a file named 70-adnroid.rules
# cp /etc/udev/rules.d/70-android.rules /etc/udev/rules.d/99-android.rules
# service udev restart
still <waiting for devices>
I didnt compile from source but I did freshly sudo apt-get remove android-tools-adb android-tools-fastboot and sudo apt-get install android-tools-adb android-tools-fastboot
Compiling from source seems like a huge pain.
gathem said:
I had them in a file named 70-adnroid.rules
# cp /etc/udev/rules.d/70-android.rules /etc/udev/rules.d/99-android.rules
# service udev restart
still <waiting for devices>
I didnt compile from source but I did freshly sudo apt-get remove android-tools-adb android-tools-fastboot and sudo apt-get install android-tools-adb android-tools-fastboot
Compiling from source seems like a huge pain.
Click to expand...
Click to collapse
I don't think you had to rename it, you could've left it.
What info do you have in that file? Below is what I have, if you have it already I apologize:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0777", GROUP="plugdev" # MTP mode with USB debug on
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0777", GROUP="plugdev" # MTP mode with USB debug on
Top is when booted normally and TWRP recovery, bottom line is when at bootloader.
# All google devices
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"
# HTC devices
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0664", GROUP="plugdev"
# Motorola devices ## This is the device I am currently working on, but as I said I have over 10 various version nexus devices I need to root
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0664", GROUP="plugdev"
# Sony Ericsson devices
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0664", GROUP="plugdev"
# NVidia Tegra 250 development board
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0664", GROUP="plugdev"
# Dell
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0664", GROUP="plugdev"
# Samsung
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0664", GROUP="plugdev"
# LG devices
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0664", GROUP="plugdev"
# Pantech devices
SUBSYSTEM=="usb", ATTR{idVendor}=="10a9", MODE="0664", GROUP="plugdev"
# Huawei devices
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0664", GROUP="plugdev"
# Nook color
SUBSYSTEM=="usb", ATTR{idVendor}=="2080", MODE="0664", GROUP="plugdev"
# Acer devices
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0664", GROUP="plugdev"
# FOXCONN
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0664", GROUP="plugdev"
# GARMIN_ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="091e", MODE="0664", GROUP="plugdev"
# SHARP
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0664", GROUP="plugdev"
# ZTE
SUBSYSTEM=="usb", ATTR{idVendor}=="19d2", MODE="0664", GROUP="plugdev"
# KYOCERA
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0664", GROUP="plugdev"
# QUALCOMM
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0664", GROUP="plugdev"
# OTGV
SUBSYSTEM=="usb", ATTR{idVendor}=="2257", MODE="0664", GROUP="plugdev"
# NEC
SUBSYSTEM=="usb", ATTR{idVendor}=="0409", MODE="0664", GROUP="plugdev"
# PMC
SUBSYSTEM=="usb", ATTR{idVendor}=="04da", MODE="0664", GROUP="plugdev"
# TOSHIBA
SUBSYSTEM=="usb", ATTR{idVendor}=="0930", MODE="0664", GROUP="plugdev"
# SK_TELESYS
SUBSYSTEM=="usb", ATTR{idVendor}=="1f53", MODE="0664", GROUP="plugdev"
# KT_TECH
SUBSYSTEM=="usb", ATTR{idVendor}=="2116", MODE="0664", GROUP="plugdev"
# ASUS
SUBSYSTEM=="usb", ATTR{idVendor}=="0b05", MODE="0664", GROUP="plugdev"
# PHILIPS
SUBSYSTEM=="usb", ATTR{idVendor}=="0471", MODE="0664", GROUP="plugdev"
# K-Touch
SUBSYSTEM=="usb", ATTR{idVendor}=="24e3", MODE="0664", GROUP="plugdev"
# Pegatron
SUBSYSTEM=="usb", ATTR{idVendor}=="1d4d", MODE="0664", GROUP="plugdev"
# Hisense
SUBSYSTEM=="usb", ATTR{idVendor}=="109b", MODE="0664", GROUP="plugdev"
# Amazon Kindle
SUBSYSTEM=="usb", ATTR{idVendor}=="1949", MODE="0664", GROUP="plugdev"
# Nikon
SUBSYSTEM=="usb", ATTR{idVendor}=="04b0", MODE="0664", GROUP="plugdev"
# Intel
SUBSYSTEM=="usb", ATTR{idVendor}=="8087", MODE="0664", GROUP="plugdev"
# Cellon
SUBSYSTEM=="usb", ATTR{idVendor}=="283b", MODE="0664", GROUP="plugdev"
# TCL
SUBSYSTEM=="usb", ATTR{idVendor}=="1bbb", MODE="0664", GROUP="plugdev"
# TeleEpoch
SUBSYSTEM=="usb", ATTR{idVendor}=="2340", MODE="0664", GROUP="plugdev"
# MTK
SUBSYSTEM=="usb", ATTR{idVendor}=="0e8d", MODE="0664", GROUP="plugdev"
# HP devices
SUBSYSTEM=="usb", ATTR{idVendor}=="03f0", MODE="0664", GROUP="plugdev"
# OPPO devices
SUBSYSTEM=="usb", ATTR{idVendor}=="22d9", MODE="0664", GROUP="plugdev"
# Xiaomi devices
SUBSYSTEM=="usb", ATTR{idVendor}=="2717", MODE="0664", GROUP="plugdev"
# Razer devices
SUBSYSTEM=="usb", ATTR{idVendor}=="1532", MODE="0664", GROUP="plugdev"
# Archos devices
SUBSYSTEM=="usb", ATTR{idVendor}=="0e79", MODE="0664", GROUP="plugdev"
I noticed your mode is 0777 so I switched 22b8 ti 0777
That didnt help either
I was having issues pushing files but then it just started working, and stops when it wants to, sometimes in the middle of a transfer. I'm using Xubuntu 15.10
Sent from my Nexus 6 using Tapatalk