[TOOL]QtADB (AndroidManager for Linux, Windows and MacOS)

Search This thread

7ymekk

Senior Member
Mar 8, 2010
316
126
Białystok
TheWizKid95: if phone is detected, You can send debug.log now

giorgio130:
QtADB is free. I've created it because i want to improve my programming skills so it will be closed
 
Last edited:

rockettman

Senior Member
Nov 11, 2010
115
10
Florida
the way i did it was as followed.

1. load up Qtadb
2. make sure it finds the phone
3. go to shell and type in as followed without quotes. "Su" enter. "chmod 777 /data/app" enter
4. then check on the apps, and hit refresh.

that should fix the problem for you. happy hunting. ^^

great thanks, but it says chmod777: not found
 

sierraindigo

Member
Nov 20, 2010
29
2
sierraindigo:
and adb devices gives You?:

yep. i get
Code:
????????????	no permissions

what am i doing wrong?

thanks

edit:
i have already tried the instruction in the faq
“gksudo gedit /etc/udev/rules.d/51-android.rules” and insert it into this file:
SUBSYSTEM==”usb”, SYSFS{idVendor}==”0bb4″, MODE=”0666″
just so you know i'm not a complete numpty...
 
Last edited:

sierraindigo

Member
Nov 20, 2010
29
2
i hadn't installed busybox separately - just through titanium backup. read that there may be an issue in that only titanium backup could access busybox this way so installed as per instructions here:
hxxp://android.modaco.com/content/htc-desire-desire-modaco-com/307587/busybox-on-rooted-desire/#entry1439001

still not working...

thanks very much for your help by the way!
 

mozarcik__

Senior Member
Nov 11, 2009
188
45
b-stok
i get "error: device not found". so i'm guessing i haven't got the android sdk working.

i've edited my .bashrc file to include the filepath to the android sdk /tools directory and have run Android SDK and AVD Manager to install the SDK API

when in usb debugging mode the output from adb shell busybox ls -l -a is
"error: insufficient permissions for device"

sudo adb shell busybox ls -l -a gives:
sudo: adb: command not found

thanks for help

"error: insufficient permissions for device" is because that adb server is started in user mode but it has to be run in root.

sudo adb shell busybox ls -l -a gives:
sudo: adb: command not found
command not found because you've set path for user only and not for root. start adb server from root passing all path like this:
sudo /home/ubuntu/android-sdk/tools/adb start-server
and then it should work :)
 

7ymekk

Senior Member
Mar 8, 2010
316
126
Białystok
i just wanted write something like mozarcik wrote;)

but i want to add that on every start of linux You will have to run adb demon from root
 

idkidk

Senior Member
Oct 1, 2009
411
44
Piacenza
Hello,

i'm trying Qtadb..... it fantastic but i can't retreive the app installed: for system app all is ok, for personal app the tool not download the app.

PC - Win7 x64
Htc dream CM508 app installed in ext4 part on sdcard.

Tia to all

Bye
Idk
 

idkidk

Senior Member
Oct 1, 2009
411
44
Piacenza
tried everything from FAQ?

I've put QtADB in debug mode and i see this:

" Get apps sd - "ls: /mnt/asec/*/*.apk: No such file or directoryls: /sd-ext/*.apk: No such file or directory"

but the app is in "/sd-ext/app/" and in "/sd-ext/app-private/" and i can access those directorys without any problem from QtADB file manager (i see the installed apps).


Tia
Idk
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    hello,

    QtADB is window app based on adb.it lets you to copy,remove etc your files and apps from PC and Android Phone
    This app is under developing so be tolerant for any bug...

    visit QtADB website: http://qtadb.wordpress.com/

    Features:

    1. File manager
    -copying files and dirs between phone and computer
    -removing files and dirs
    -creating new dir
    -and other

    2. App manager
    -installing apps
    -removing apps
    -creating backup of apps with data
    -restoring backups of apps with data

    3. Shell
    -opens android shell

    4. Screenshot
    -take screenshot of your device
    -save screenshot to png file

    5. Fastboot
    -flash bootloader, radio and recovery
    -boot recovery

    6. Recovery
    -nandroid backup/restore
    -wipe data
    -flash rom
    -wipe battery stats
    -fix uid mismatches

    7. Reboot
    -to bootloader
    -to recovery
    -normal reboot

    8. Settings
    -set font used by app
    -set starting paths (or remember paths on exit)
    -and other

    9. Automatically detects phone (device, fastboot and recovery mode)

    it requires installed AndroidSDK and busybox on phone (so and root)
    linux and macOS version reguires installed Qt libraries(libqtgui4, libqt4-declarative and libqt4-network 4.7 version)(install it from synaptic or some similar app)

    if you have connected phone but the file list is empty run with root permisions:
    1)adb kill-server
    2)adb start-server
    or:
    create file:
    gksudo gedit /etc/udev/rules.d/51-android.rules
    and insert this line:
    SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"

    Ive got HTC Magic with Cyan6 and im testing everything on this. QtADB should work with every phone with busybox

    if you have any suggestions/questions or you found any bug please let me know:)


    0-6windows1.png


    lin5.png


    0-6macos2.png




    More screenshots on official site


    I am not responsible for damage done to your phone while using QtADB.



    DOWNLOAD FROM OFFICIAL SITE

    Do You miss fome feature that QtADB doesn't have? please post Your idea here: http://qtadb.uservoice.com/forums/87039-general


    [size=+2]DO YOU HAVE SOME PROBLEMS WITH QTADB? PLEASE READ FAQ FIRST[/size]


    If You like QtADB please consider donation:
    8
    Modded QtADB

    I have a custom QtADB build for testing. This is not officialy supported from the authors yet, they are still checking my changes.
    I fixed most of the bugs(I believe) and added some new useful features:

    Code:
    What is different from current official build 0.8.1:
     
    Files Page:
      -double click on phone file (both panes) opens file in
     PC with the associated program for that extension 
    with option to edit the file and save it back to phone;
      -added "Properties" in phone files/folders right click 
    context menu with permissions changing capabilities;
      -switching left pane between PC/phone files now
     remembers last folder view for both;
      -left paths combo box now works for phone files too 
    when switching left pane to phone files;
     
    Apps Page:
      -major speedup displaying apps after the initial first 
    run when apps info is collected;
      -fixed all functions, now all buttons and actions works
     as they should;
      -now you can backup and restore apps and data to 
    any folder on /sdcard or PC, set backup folder location
     in Settings first;
      -option added to Backups context menu to add 
    app/data if missing from existing previous backup;
     
    New CWM Page replaces current Recovery Page if CWM
     Recovery is installed on phone and detected. If CWM 
    Recovery is not detected, the current Recovery Page is 
    used. What can be done in the New CWM Page:
      -run fix_permissions in Android OS mode, not in 
    recovery mode. As you may know fix_permissions in 
    CWM recovery is broken (at least for me and others with 
    phones like my LG-VM670);
      -Fix/Undo Fix Market Cache Download;
      -Flash new Recovery;
      -Mount/Unmount any partition in recovery mode, 
    Remount /system with read-write/read-only access in 
    Android OS mode;
      -Repartitioning SD Card with /sd-ext partition 
    (your choice of size and type) with option to backup 
    /sdcard content before, and restoring it after the operation;
      -Wipe data/factory reset, cache, dalvik-cache, battery
     stats (your choice) in recovery mode;
      -Install zip of your choice from /sdcard;
      -Backup ROM to any folder on /sdcard or to default 
    CWM location with option for Backup md5 sum 
    validation after phone reboots back to Android OS, 
    ensures proper backup is done;
      -Restore nandroid Backup with option to choose 
    which partitions to restore(select all for full restore) 
    and preliminary md5 sum validation for double safety;
      -One click Update ROM function which wipes cache 
    and dalvik-cache before flashing. If Link2SD is 
    detected on your phone you have an option to 
    automatically copy its sd-ext mount script from current
     ROM to the new updated ROM saving you one reboot. 
    Link2SD will not even know you updated the ROM;
      -One click ROM Flash with full wipe and options to 
    install zips before/after(or both) the flash - this 
    procedure reboots phone to Recovery, wipes 
    dalvik-cache, formats /boot, /system, /data and /cache
     partitions, installs zip before(if selected),  installs the
     new ROM, installs zip after(if selected) and reboots 
    back to Android OS.
     
      Detailed information in Status Window is displayed 
    for all operations taking place in real time. After phone 
    reboots back to Android OS, the last CWM recovery log 
    is displayed so you can spot any errors occurred during
     the last operation.
     
    And probably something else I forgot about;
     
    All bugs fixed(I believe).
     
    If you can't connect with adb over WiFi leave port# to 
    0000 and it should connect(that's how it works on my phone).
     
    I want to thank and give credits to the guys (couldn't 
    find their names) created some of the tools I'm using 
    to make the new features works.

    I'm not allowed to post links yet so if you want to test it, please PM me and I'll get you the link. Sorry about that.

    Just unzip it and run "QtAdb.exe". You need Android SDK installed, or at least adb working with your phone. For the CWM features CWM based recovery is required. And of course with applications like this one root access and busybox is needed.

    All credits and my "thank you" goes to 7ymekk and mozarcik. Also I want to thank and give credits to the guys (couldn't find their names) created some of the tools I'm using to make the new features works.

    I did some extensive testing, especially the features running in recovery mode, but with all the different working environments etc. some bugs may occur.
    So if you have any issues or questions let me know.

    Have fun!
    5
    Another idea, could you support more than one device in the same time?
    One of the main purposes of QtADB2 is to support many devices simultaneously. Not only Android devices;)

    It always shows has stopped working in windows 8 64 bit... :confused::rolleyes: please help me
    0.8.1 crashes on Windows 8.1 x64 but 0.7.3 version works here:)
    Unfortunately QtADB 0.8.x has a bug with update checking. Disable Your internet connection, disable 'check for update' QtADB settings and enable internet.
    5
    Nijel8 asked me to post the link and his message is a per below:

    Thanks for testing my build.
    Here it is, I call it CWM-edition:QtADB-cwm_edition.zip
    Please, post your findings about my mod as well as issues or questions in the thread.

    Sent with Desire.
    4
    Hey guys!

    Recently I was wondering on QtADB 2.0. The gui would be the same, just without these embarrassing animations, stupid fonts etc :) With lot improvements of course and the new features. If You are interesed in QtADB 2.0 please consider visiting: http://qtadb.wordpress.com/2014/02/17/the-qtadb-2-0/ . Let me know what You think!