Description of problem: Besides the usual commands adb and fastboot, this updated release of android-tools would have these commands as well: simg2img -- A tool for converting Android sparse images into regular filesystems img2simg -- A tool for converting regular filesystem images to Android sparse images that can be used with fastboot append2simg -- A tool to append to a sparse image ext2simg -- A tool to create fastboot compatible sparse images from ext2/ext3/ext4 images make_ext4fs -- A tool to generate ext4 sparse images Version-Release number of selected component (if applicable): 7.1.2_r17
Created attachment 9455 [details] Proposal spec that needs to be worked with a bit
CC: (none) => hamnisdude
Assigning to the registered maintainer.
Assignee: bugsquad => geiger.david68210CC: (none) => marja11
Created attachment 9465 [details] Latest build error Seems like it's trying to use a RSA key file that doesn't exist. Should one create it before building this package or use a premade one from another dist?
I would like to thank whoever built and imported android-tools for Oreo into Cauldron. I rebuilt the src.rpm to Mageia 6 and I had no errors installing it. :) I'll close this report if noone feels otherwise. Marja?
Summary: Update android-tools to version 7.1.2_r17 => Update android-tools to version 8.0.0_r4
package android-tools is now up-to-date on Cauldron and also on mga6/Core/Updates_testing repo!
Closing as RESOLVED FIXED then. If anyone feels that this needs to be reopened for some reason please feel free to reopen it. Once again, thanks David for pushing the update. :)
Status: NEW => RESOLVEDResolution: (none) => FIXED
I rebuilt the src.rpm for Android Tools that was put in Updates Testing. However when I install it and connected my phone with USB debugging enabled and restarted the adb server to get an prompt to allow ADB to communicate with my phone I get this error: [kristoffer@localhost ~]$ adb kill-server [kristoffer@localhost ~]$ adb start-server * daemon not running. starting it now at tcp:5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon Should I reopen this with further information or do I open a new one?
I even tried this: [kristoffer@localhost ~]$ adb shell * daemon not running. starting it now at tcp:5037 * * daemon started successfully * error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set Try 'adb kill-server' if that seems wrong. Otherwise check for a confirmation dialog on your device. [kristoffer@localhost ~]$ adb kill-server [kristoffer@localhost ~]$ adb start-server * daemon not running. starting it now at tcp:5037 * * daemon started successfully * [kristoffer@localhost ~]$ adb devices List of devices attached 02157df264f0452f unauthorized
I'm not sure how this is supposed to work, but apparently the adb daemon can only be run as root, while it looks like you're trying to run it from a user account. It can be started/restarted by systemd instead of using adb kill-server/adb start-server.
CC: (none) => cjw
or you may have to revoke authorizations on your device, there is info on this on the web
Okey. That's news for me. I did revoke any authorisation, but the issue still happened. I'll try running adb as root to see if that makes a difference.
(In reply to Kristoffer Grundström from comment #11) > Okey. That's news for me. I did revoke any authorisation, but the issue > still happened. I'll try running adb as root to see if that makes a > difference. I've tried to restart adb as root, but I still get the same result.
I noticed that Ubuntu puts their 51-android.rules file in /etc/udev/rules.d/ instead of /usr/lib/udev/rules.d/ Could this difference cause any problem?