Thanks for those but here is a Direct Link Mirror.
https://mirrors.napshome.net/AndroidCommander/AndroidCommander07911_setup.exe
Last edited:
Thanks for those but here is a Direct Link Mirror.
https://mirrors.napshome.net/AndroidCommander/AndroidCommander07911_setup.exe
Please...
Would you please take a look at KToons kernel and AC? It is having problems finding my GS3-i747 with SlimKat(SlimRom) 4.4.2 installed.. I have done all the required steps to getting it to work and I can see my device in the first little box that shows the number of devices. I select my device and it just sits and loads... Please help.. Thank you!!
P.S. would it have something to do with the undervolting I have done? Only -50 to all levels..
Found the "Android Commander (debugging mode).bat" and everything is working perfect again!! Thanks for letting me know it was there... lolol...
xKJTx
P.S. would it have something to do with the undervolting I have done? Only -50 to all levels..
Found the "Android Commander (debugging mode).bat" and everything is working perfect again!! Thanks for letting me know it was there... lolol...
xKJTx
Last edited:
It seems that Android Commander doesn't work with rooted Galaxy Tab Pro 12.2 (Sm-T900), doesn't recognise it
(Works perfectly with my Galaxy Note 2)
I found the problem :
The problem is ADBD Insecure v1.30, it doesn't work
I uninstalled it and reinstalled V1.20 and now Android Commander works perfectly but I have Root Access : NO even USB Insecure ticked
(Works perfectly with my Galaxy Note 2)
I found the problem :
The problem is ADBD Insecure v1.30, it doesn't work
I uninstalled it and reinstalled V1.20 and now Android Commander works perfectly but I have Root Access : NO even USB Insecure ticked
Last edited:
WOW Great TIP!
Finally Got my Dam Phone working with Android Commander!
HINT: http://xdaforums.com/showthread.php?t=1687590
THANKS !
Last edited:
Glad it helped WarlockW! Seems like even though this is super old, people are still using it. Is PanPiotr stil around? If he updated it a little bit, it would probably be worth maintaining from donations!
I cant get AC to see my phone anymorr. I have a GNote 3.It used to work fine on stock and TouchWiz roms. Im currently running AOSP based Carbon ROM. My PC can see the phone but AC cant. Im rooted and have TWRP recovery. USB Debugging is enabled and I also have the Java JDK 8 installed. I just tested with my Galaxy Tab Pro 12.2, running stock rooted ROM witn TWRP, no go there either. Am I missing something?
bin replacement
unzip this replace over your bin folder where u installed AC, worked for me on lg g3
unzip this replace over your bin folder where u installed AC, worked for me on lg g3
Last edited:
I try run it for my phone it's successful when I connect my nexus7 then it's not found device
My phone android 4.2.2 and nexus7 v4.4.4
My phone android 4.2.2 and nexus7 v4.4.4
Well I thought that you were just curious
Honestly I just came from workout, answered before shower and forgot after.
Solution: First update files in \Android Commander\bin\. You can find those files on xda, for example here. If still doesn't work (I already had updated bins but I had fresh flashed rom) then you have to enable root access under dev tools for adb (and apps). If still doesn't work (my case), close AC, start cmd, go to \Android Commander\bin\, type adb shell then su. Phone should ask you for permission, confirm it, close cmd, now AC should work.
Well I thought that you were just curious
Honestly I just came from workout, answered before shower and forgot after.
Solution: First update files in \Android Commander\bin\. You can find those files on xda, for example here. If still doesn't work (I already had updated bins but I had fresh flashed rom) then you have to enable root access under dev tools for adb (and apps). If still doesn't work (my case), close AC, start cmd, go to \Android Commander\bin\, type adb shell then su. Phone should ask you for permission, confirm it, close cmd, now AC should work.
I didn't know about option 3 there so did it and I got these gibberish in cmd, then still doesn't work.
According screenshot you have two different version of adb, one in Android commander and one somewhere else. Try to update both to the latest version.
Are you using or having installed QtADB?
Are you using or having installed QtADB?
I noticed but don't worry they're same now and updated adb to Google' ones 1.0.32, but it's still the same thing, gibberish like that and nothing display in data folder.
Can you access data folder from adb shell?
Try to clear trusted devices under developer options. If doesn't exist, try to disable/enable adb debugging.
Try to clear trusted devices under developer options. If doesn't exist, try to disable/enable adb debugging.
oh look it works per your option 3. Phone asked for permission and no more gibberish.
Yes I can access the folder via adb shell, see image 2. It works fine.
I don't see trusted devices, or anything similar, in dev nor in security. It's in SuperSU though, see screenshot. Disable/enable adb debugging works fine for itself but does nothing for AC.
Attachments
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
74
My website is down, but download is still alive.
Hi Guys!
Android Commander is windows application to keep control on your android apps and files from PC. This is a small, very very fast and intuitive app.
If someone want to try it, go a head. But remember, you doing this on your own risk! I'm not professional programmer, this is only my hobby
Program Requirements
Before you install the program you should read this:
Android Commander should works for any android device, but here is list of devices confirmed by me or users.
Before you report any problem to me, read program FAQ.
Full list of program features.
Screens:
Android Commander screenshots gallery
If you like my program, conceder a donation please!
Download is here
mirror
Changelog:
Full program changelog10
Thanks for those but here is a Direct Link Mirror.
https://mirrors.napshome.net/AndroidCommander/AndroidCommander07911_setup.exe7HERE'S HOW TO ADD 4.3 SUPPORT:
Make sure your USB drivers are fully updated! And have the 4.3 drivers as well through the SDK manager.
In developer options on your phone enable USB debugging, and for Root Access change it to "Apps and ADB"
run adb devices and I don't know if your phone does this, but mine prompted me on the phone to accept giving the computer adb access.
1. Open the root folder you installed Android Commander. (ex: C:\Program Files (x86)\Android Commander)
Open the root folder you installed Android SDK (ex: C:\Program Files (x86)\Android\android-sdk)
2. In Android Commander folder open /Android Commander/bin
Delete aapt.exe, adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll
3. In your Android SDK folder, navigate to /android-sdk/platform-tools
Copy adb.exe, AdbWinApi.dll, and AdbWinUsbApi.dll to /Android Commander/bin (where you just deleted these files)
4. In your Android SDK folder, navigate to /android-sdk/build-tools/android-4.3
Copy aapt.exe to /Android Commander/bin (where you just deleted this file)
Your Android Commander should now find your device.
I'm glad to be of any assistance, this took a little bit of guessing and snooping around the SDK files but it seems quite logical, Android Commander hasn't been updated with 4.3 compatibility (and it doesn't look like it's gonna be) but as long as you keep the DLL files up to date with google's releases it should be alright.3
Just uploaded working Android Commander. I've updated bins so it works with my Moto X Force running Android 6.0. Just unzip and run AndroidCommander.exe,
Great tool! Hopefully dev will come back and continue developing.
https://mega.nz/#!105BkZoT!mMv-CmKZzQm6J6kzDJmyBs1EEwiMQ-WygGiXZOxHkAo3Update!
small update for you
https://www.facebook.com/androidcommander/posts/10151031241149594
i will update thread tomorrow, i'm going to sleep nowww......
