Usbutil Android
Peter Rayshell
I have followed the instructions to install snagboot and have used it to flash a regular SK-AM62 (GP device). Now I am trying to get a locally built version of the android bootloader flashed on to the SK-AM62-LP and I am having issues with the loading of the bootloader. I modified my am62x-sk-evm.yaml to reference the lp-hsfs files, is this the correct file btw? I'm confused since the LP evm does have an HS-FS AM62 on the board, but it's not necessarily blown with a key and the instructions have separate files called out for HS-FS as if there are variants of the LP EVM which have a GP device on there?
I see that it's looking for a partition ID, but I have never formatted the emmc on this device so is there some sort of issue with running snagrecover without first partitioning the EMMC? Or is it supposed to do this automatically?
I also tried running the bootloader off the SD card and I can get u-boot running but loading the environment defaults and then running saveenv, it said that there was nowhere to save the environment. From my understanding saveenv should start partitioning, but obviously this did not run.
Hi, I connect my particle photon 2 via usb to computer, then i downloaded particle app on my android device in order to set up and configure wifi and other stuff for set up.However, particle2 is not listed on my android device. I dont use antenna, but only micro usb connector to pc. Also i tried to make set up with setup.particle.io, it found my device as P2 and paired, but page is not moved to other steps but only remained on the same page. I also tryied to set up via CLI of particle , however, i met with an erro that it is not possible to setup this device with particle-cli. Please provide me support to solve this situation. Thank you!
in play store, there is no particle tinker ,there is only particle iot app, which i already tried.Lookup Tools Tools Particle here you mentioned some parameters, where can I get them to verify that those are for my device?
Your Particle device must be connected by USB to your computer and in listening mode (blinking dark blue). If it's in another mode, hold down MODE (SETUP on Photon) until the status LED blinks dark blue.
The identify tool only works on Chrome (version 89 or newer) on Windows 10, Mac, Linux, or Chromebook. If you are using a different browser, you can use the Particle CLI and the particle identify command instead.
I created account on paticle cloud, the connected my device via usb to pc.After all , i see that it is not connected to cloud, hiowever, my particle photon is in listening mode, blinking blue color. I dont know what is the issue?
connection1779810 29.6 KB
My device is particle photon 2. Then, i can not set up even wifi , because there are 2 options on setup.particle.io, first: usb connection on whcih i use my device and pair it, then page throw an error that particle is not seeing my device as attached on image png. Furthermore, I choose monitor one , as a result it is not connecting to particle cloud. I also tried to connect via particle cli? It throws an erro that it can not setup my device. Could you please help to configure this device??
issue1179890 101 KB
issue2705361 45.1 KB
thanks. I tried to do particle usb configure. particle usb command is not found. Then i tried to installed dev rools as you can see. but again error is as attached. Please let me know. I rebooted as well.
dfu923509 91.6 KB
dfu274436 8.1 KB
What version of node do you have installed? If you have v18 or later, you may be running into an issue where node serialport won't install. The best workaround is to use nvm or fnm to be able to quickly switch to node 16 if you need to use any of the USB serial commands in the particle CLI.
I'm trying to debug an app (or simply inspect pages in the Chrome browser) on my mobile device and I'm trying to use docker containers for housing adb. Everything goes well while starting up the adb server in the container and I even get to list my device with adb devices, but once I go to chrome://inspect/#devices (on my local machine), I don't get to see my device listed over there.
If you define a hostname for the container (docker run --hostname...), you can use the hostname instead of the ip (which is better, because the ip can change) in the socat command. For example, if the hostname is android-emulator you can run the above commands as:
I followed the guide available on the wiki, but I'm having trouble tethering my pixel 6 on android 12 to my Linksys wrt3200acm. My pixel 3 running android 11 does not have the problem, so I believe the problem's related to the android version. Does anyone have suggestions or is familiar with troubleshooting android tethering problems?
I had the same problem. Diffing your usb opkg list with mine, I think you are missing kmod-usb-net-cdc-ncm and perhaps kmod-usb-net-cdc-subset (I don't remember which of those two was the magic package).
Some googling shows other Android 12 users even on Windows being confronted with missing driver for CDC-NCM. It may not be android 12 specific since I see references going back to 2017 and even 2014 mentioning subset...
I'm not sure this is entirely correct on Android, but on Linux, lsusb -v tells a lot about USB devices, including their maximum current output. If you can get usbutils on Android, that might tell you.
USB utilities for Linux, including lsusb. Make sure you connect theraw-usb and network-control interfaces withsnap connect usbutils:network-control :network-control andsnap connect usbutils:raw-usb :raw-usb
Recently, I've been working on a pretty interesting and foolish project I had in mind, and here I'm bringing to all of you my findings. This guide's main aim is to document the process of building an Android kernel, specifically a CyanogenMod kernel and ROM, and modifying the kernel configuration to add special features, in this case, wireless adapter Alfa AWUS036H support, one of the most famous among Null Byters.
I want to apologize in advance if this guide will be dispersive, but the point which I'm trying to make is more than just one, and this has multiple scopes and topics in it. Be ready to explore every hidden corner of the Android OS, and its infamous kernel!
When I first bought my Samsung Galaxy S5, I was sure it was going to support native monitor mode directly on its internal wireless card. However, as soon as I started looking around to make this happen, I found out that the chipset doesn't support monitor mode yet, and probably never will, because it is a combination of the 2x2 MIMO and Broadcom 4354 chips.
Summer is very hot this year. I spent the last few months trying to get monitor mode to work on my Samsung Galaxy S5. However, I can't deny that the way to success wasn't easy, mostly because of lack of documentation as always, so here I am, breaking down the steps I've been following in order to make this work.
Before proceeding, I must inform you that I've been trying to follow other paths before recompiling the entire kernel, even though, unfortunately, none of them worked for my device (but might for yours).
The most straightforward way to do this is by having a device with a wireless card that has a chipset known to support monitor mode. If these requirements are satisfied, your device is probably supported by the application bcmon, which is aimed to set your built-in wireless card into monitor mode.
Another option is to use Kismet's application Android PCAP which "implements the Linux kernel RTL8187 driver in userspace using the Android USB host API. This means it doesn't require root privileges (a highly dangerous requirement), and will run on stock phone firmware."
First of all, rooting is not that dangerous. It is almost impossible to brick an Android device today, and even if you do, if you have a backup and a computer, you can basically pick up your stuff where you left it. Flashing ROMs is even more risky, but you can recover from that too very easily nowadays.
Second, this application does in fact put the Alfa adapter in monitor mode, but is limited to the environment set up by the application itself (capturing PCAPs to analyze later with Wireshark), so no Airodump-ng nor wardriving. (Kismet, you had one job! Anyway, remember this, Kismet, we'll talk about it later).
Finally, the last option was trying to load kernel modules, but this is out of the scope of this guide because Realtek drivers source code for RTL8187L, AWUS036H chipset is too outdated thus incompatible with most of recent Linux kernels, Android included.
The only option left was to recompile the Android kernel with built-in support for Realtek's specific drivers, which were patched and built into most Linux distributions over the years, thus available to the compilers we are going to use.
Before starting: I like my posts to be full of references and links that guided me through my findings, however, nothing fundamental will be excluded from this guide, even though I will have to assume that you are comfortable with the concepts of Linux, kernel, Android, SDK, ROM flashing, source code, and open source.
Kernel is the soul of "stuff," it is the link between hardware and software, just like body and thoughts, matter and imagination; it is the fragile line between what something is and what something feels like. When you scroll down a page very fast on your smartphone, and it actually feels like you are reading a book, at the end it is all just memory being updated with a time lag of milliseconds! ADB's "logcat" is maybe the best way to show what an Android kernel does and how hard it works (or dmesg on Linux, if you want, but we'll get to it later).
For a third-party device to work on any device, computer or smartphone doesn't matter, the device must know how to interact with it. Drivers are somehow "rules" that set up a proper language trough which the devices can communicate.
What we are about to do is recompile the Android CyanogenMod kernel with support for the drivers we want to be built in. In this case, I will be building AWUS036H (RTL8187) drivers support for a Samsung Galaxy S5 G900F (KTLE), however, this guide's main goal is to inform you about Android kernel building.
e59dfda104