Develop Bugs

[Q] USB Bricked

Let me say upfront that yes I did read all of unrevoked replies in the dev section.
They mention that the 8/1 leak (ROM I'm currently running) may also have the same USB issues as SkyRaider.
When I plug my phone into my mac, I get a device error message and the option to ignore or (I think cancel). Anyway, if I click ignore, I can see both the SD card and internal storage just fine. I can also see my SD card from my phone and I know adb is working because I recently went into recovery, /mount systen, to remove the old flash.apk for the hulu hack.
So on the surface it appears like my phone is fine except for this error message. I'm curious if any other mac users receive the same error message (never got it before the 8/1 leak). With s-off coming as early as tonight, I don't want a USB brick. Thanks for any help.

Hey bro I'm a Mac user as well and was getting the same message. This has to do with a file that verizon included in the Rom to auto-run the device like an mp3 player on windows machines. You can remove this by rebooting into recovery-partition menu-mount system....now open up terminal and cd into your Android SDK/tools folders now run ./adb shell hit enter next type rm /system/etc/CDROM.ISO hit enter ....unmount system - reboot and your golden.

HeyItsLou said:
Hey bro I'm a Mac user as well and was getting the same message. This has to do with a file that verizon included in the Rom to auto-run the device like an mp3 player on windows machines. You can remove this by rebooting into recovery-partition menu-mount system....now open up terminal and cd into your Android SDK/tools folders now run ./adb shell hit enter next type rm /system/etc/CDROM.ISO hit enter ....unmount system - reboot and your golden.
Click to expand...
Click to collapse
Hey thanks a lot for the info. I'll run adb shell when I get home and see if this solves the problem. Good to know it wasn't just me.

let me know if that fixes the issue for you

Worked perfect. Thanks!

Glad I could help

i had the same problem, but with a pc. whenever i plug in my phone into my pc, nothing comes up, i hav to go to my computer to open it up. and also i have an extra cd drive that says verizon mobile. do u know if the "rm /system/etc/CDROM.ISO" command works with a PC too?

[Q] adb on ubuntu 11.04 help plz?

i already set up adb and the sdk
now i need help setting up udev.
can anyone please explain it to me in a way a noob can understand?

teh5abiking said:
i already set up adb and the sdk
now i need help setting up udev.
can anyone please explain it to me in a way a noob can understand?
Click to expand...
Click to collapse
Here you go.

Yeah, I tried that tutorial.
Didn't work for me.
Sent from my T-Mobile G2 using XDA App

I installed 11.04 recently and ADB seemed to work right out of the box.
Have you tried:
Code:
adb devices
I grepped the rules.d directory for 0bb4 and came up with this, in 40-usb-media-players.rules
Code:
ATTRS{idVendor}=="0bb4" , ATTRS{idProduct}=="0c94" , ENV{ID_MEDIA_PLAYER}="htc_vision"
"lsusb" returns (among other devices)
Code:
Bus 002 Device 007: ID 0bb4:0c91 High Tech Computer Corp.
Note that the product ID is different.
For 10.10, I think I had to update the udev files, but support for the vision might already be baked into 11.04. If "adb devices" returns a serial number, you're all set. If it doesn't let us know what pops up.

I found this:
http://eddieringle.com/udev-rules-for-adb-in-ubuntu-11-04-natty-narwhal/
I'm not sure what to say? I don't have the 99-android rules and adb works fine. Maybe you didn't have enough permissions to change the udev files when you installed ADB/SDK?
maybe reboot or restart udev or unplug/plug your device?
Code:
sudo service udev restart

I don't see how it didn't work. That tutorial worked for me just fine.
Sent from a Western Union telegram.

You need to reboot your computer for it to work.
Sent from my HTC Vision using XDA Premium App

Well, I did get adb to work just fine on my Acer Aspire One.
I had to mix the tutorial on the Cyanogenmod wiki with a tutorial that was for the G1/Magic/Droid/N1/i7500.
It's working great.
The one on the android dev page didn't work for me because of some deep internal stuff that was going on with my laptop. as explained by my good friend Chris who's actually a registered Android developer. I forgot exactly what it was, but it had to do with the security features of Ubuntu that collide with something that's in my laptop.

For others looking for info with adb on natty, the SYSFS is deprecated (if you are following the tutorial on the android site). You should be using ATTRS instead. Also, the rule can be 51 or 99.
Here is mine (i have an nvidia pad and an htc phone):
Code:
[email protected]:/etc/udev/rules.d$ cat 51-android.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0955", MODE="0666"
And don't forget to restart udev. Unplug the device, do the command below and then plug back in. HTH.
Code:
sudo /etc/init.d/udev restart

[Guide] ADB connection between two Android devices

Probably not breaking any ground here (since in hindsight it was blatantly obvious), but I thought I would share anyways...
I own several Android devices, and I'm always playing. well, tonight I was tweaking a few things over adb and got to wondering if I could use adb to connect from one Android device to another. Well, turns out it's pretty easy, if you're rooted...
Both devices need to be connected to the same wireless network.
Install adbWireless from the Playground (sorry, Play Store): https://play.google.com/store/apps/...251bGwsMSwyLDEsInNpaXIuZXMuYWRiV2lyZWxlc3MiXQ..
You only really need it on the receiving device, but I have it on everything anyway.
Copy the Linux adb binary into /system/xbin/ and set the permissions to 755 (rwxr_xr_x), and reboot.
You only really need to do this on the controlling device, but may as well do it on all.
Fire up adbWireless on the receiving device, grant root privileges, and note the IP address
Fire up a Terminal Emulator on the other device, and enter: adb connect <IP address from other device> (you typically don't need to add the :5555 on the end.
Job done! Pretty handy when working from a slate!
I also run dd-wrt firmware on my router, which let's me assign static IPs by MAC address, so the IP for the devices are always the same.
Regards - dr

adb binary is already built in, /system/bin/adb.
besides that, all that's left is get adbd running, and that can be achieved either by an app (like you suggest) or edit init.rc to have adbd as one shot service to allow manual start (doesn't boot with the system). cyanogenmod also has adbd over wireless done like this.
also, one could use an OTG cable to connect devices directly, while i agree adb over wireless is good, adb over ssh would be best.

Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...

danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Agreed.
Sent from my i9250
edit: checkout this commit @aosp-master: https://android-review.googlesource.com/#/c/41846/
i'll be cherry-picking this one today

danger-rat said:
Valid points.
The adb in /system/bin is a less functional version than the standard Linux binary (94kb versus 156kb); kinda similar to the chown binary, where the recursive function doesn't work...
I'll concede to the rest though...
Click to expand...
Click to collapse
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.

elfaure said:
Hi - Where can I get this more functional binary that's half the size of a standard linux binary? I've tried two, they are both around 330Kb, and they fail to run with error "non executable: magic 7F45" because they were not compiled for my ARMV71 processor. I ran chmod 755 on it and when I check the permissions it is executable (-rwxr-xr-x). Can you post a link to the one that's 156kb - I can't find it.
Click to expand...
Click to collapse
Bumb. Anyone home? Shoot me a link please.

Hey guys,
Now, I have a tablet (running android) and is rooted already (so, I'm ready to get any needed binary on my device). It supports OTG. When I plug in my phone (rooted) using OTG to my tablet, my phone says 'Android debugging enabled' in notifications, is also charging. When I go to TE (Terminal Emulator) of my tab and type: 'adb devices', it displays no device in the list of attached devices (obvious).
And yes, my tab has got OTG host modules in kernel because when I turn on USB mass storage on (in my phone), my tab detects it and I can use it.
Now, my question:
Can I actually do this? i.e., using adb in my tablet (for my phone) via OTG?

Can we run adb from the device to detect itself?
I'm sure you can see why this would be amazing and powerful.. possibly giving root to apps on non-rooted devices with adb's run-as com.package.apk and such?
Is this possible? To have adb run on the Android device and connect to itself? If it is, can you guide me to where to learn it?
Dave :cyclops:

so my FLO dont want to show up on ubuntu?

okey im needing little help now, i just installed 64bit ubuntu to start practicing how to compile roms etc.....but now when i have zip on my computer finally, my nexus dont want to show itself anywhere on my pc. i followed these guidelines without succes "# sudo gedit /etc/udev/rules.d/99-android.rules" and added "SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0666", OWNER="your-login" # MTP mode with USB debug on" but obviously changed login and ATTR. also with ADB devices command my nexus is there, but should there read nexus instead of random numbers and letters?
E: got it working by following this -> http://bernaerts.dyndns.org/linux/74-ubuntu/268-ubuntu-automount-any-mtp-device

Trouble getting my device authorized on Linux Mint 19

I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.

Triscuit said:
I've tried everything to my knowledge including doing multiple google searches but I can't figure this out. I recently switched to Linux Mint 19 from Ubuntu 18.10 and I'm having issues getting my device to properly work using ADB. I have created the proper rules (to my knowledge) in /etc/udev/rules.d/51-android.rules and also added vendor id in ~/.android/adb_usb.ini. The main issue I seem to be having here is that after I revoke USB debugging authorizations from developer settings, I do not get the pop up on my device to allow authorization. I've tried restarts of my phone and PC but it still shows as unauthorized when typing adb devices. Any help would be appreciated. Also, just noticed I was missing some spaces in 51-android.rules I fixed but that did not fix it.
Click to expand...
Click to collapse
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...

Tulsadiver said:
Try this
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
If after that you type adb devices and you don't see your serial number type
echo 0x2717 >> ~/.android/adb_usb.ini
Just something I googled...
Click to expand...
Click to collapse
The first two commands are to install adb and fastboot, which I've done. The third command is to add a new product id in adb_usb.ini which I got "permission denied" so I entered it manually for ****s and giggles but it didn't help. Thank you though!

I was finally able to get the device to authorize, I did a few things but I'm not sure which one corrected the problem, first. I deleted the adbkey file from /home/.android folder, I also changed permissions of the folder to rw-rw-rw and finally I hit "Revoke USB debugging authorizations" under development settings WHILE the phone was plugged into the computer. Every other time I had done it after unplugging the device. Not sure which one worked but it did, now I can get back to flashing again!
Sent from my Pixel 2 XL using XDA Labs

I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2

jbarcus81 said:
I had to go back in time to find this.. but this was how I originally was able to get things going in Ubuntu... It's very dated but I'm sure some of this may work?
https://forum.xda-developers.com/showpost.php?p=39144762&postcount=2
Click to expand...
Click to collapse
Yep I honestly think my problem was that I was unplugging my device before revoking authorizations..... Silly me haha
Sent from my Pixel 2 XL using XDA Labs