sierraindigo:
and adb devices gives You?:
giorgio130:
source is closed
and adb devices gives You?:
giorgio130:
source is closed
giorgio130:
QtADB is free. I've created it because i want to improve my programming skills so it will be closed
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. ^^
???????????? no permissions
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
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.
One of the main purposes of QtADB2 is to support many devices simultaneously. Not only Android devicesAnother idea, could you support more than one device in the same time?
It always shows has stopped working in windows 8 64 bit... please help me
Unfortunately QtADB 0.8.x has a bug with update checking. Disable Your internet connection, disable 'check for update' QtADB settings and enable internet.