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] How to use CIFs with Windows 7

Could some kind person point me in the direction of how to use CIF's (on DJ Droid 1.4, presume it's the same for every rom) along with Windows 7 to share a media folder?
I've (obviously wrongly), shared the folder in Windows, put in the network path, username and password and local path in the CIF's manager but it always fails to mount.
Many thanks.

I've worked it out now, in case anyone is interested, do not use the windows network name, instead do this:
Right click folder in Windows, select properties/sharing then click "Advanced Sharing", check "Share this folder" click ok.
Add the share in the CIFs manager with the windows box IP address and the folder, e.g.
192.168.1.2/Media
Use your windows username and password.
Job done.

what should be entered at Mount Point?

abc001 said:
what should be entered at Mount Point?
Click to expand...
Click to collapse
Any path on the phone. /sdcard/cifs/media works fine for me.
Sent from my HTC Desire using XDA App

Can someone explain how I would use this to access music on my home computer - I have a dns service so that I can remotely access the computer - using the built in htc music player, or is this not possible?
From what I understand, I simply share the folder (samba) in windows but how do I point my phone at that directory?
Chimp

Bump Would love this

Note: This will only work on your home Wifi network. If you want to make use of files from your home PC over 3G, you might want to use a VPN.
You'll need a rooted device and a custom kernel that allows CIFS. All AOSP ROMs use CIFS enabled kernels, but if you use a Sense ROM then you may need to install a newer kernel to get this to work (see the "all things Desire" thread in the "Desire Android Development" subforum for kernel options).
Install CifsManager from the market. Find the file 'cifs.ko' on your phone and make sure that the 'path to cifs.ko' in the CifsManager settings points to it.
You'll need to know:
- Your PC's IP address (i.e. 192.168.0.10)
- The name of the share you've created (i.e. Media)
- The name of the Windows user allowed to access the share (i.e. smeddy)
- The password of the Windows user allowed to access the share (i.e. 53cr3t)
In CifsManager, press menu, 'Add new share' and enter the above details. Press on the line in CifsManager with the red dot on the right. The dot should turn green. From now on, to use files from your PC on your phone, just open CifsManager and tap the share to connect.
You should now be able to access the files from the share on your PC as if they were located in /mnt/cifs/<share name> (if you have S-OFF) or /sdcard/mnt/cifs/<share name> (if you haven't).

I was thinking that a folder in the phone can be added as a share and accessed as a shared folder from a Windows 7 PC (the reverse of that mentioned here) using CIFs manager. Can this be done? If so can someone post detailed steps please?

No, as far as I know, that doesn't work yet.
What you'd need for that is an Android port of Samba. Some people over in the Android Software Development forums are discussing that, but I don't think it's working (yet). Edit: Apparently it is. See this thread for more information.
There are several FTPd's for Android in the market, though. That could do much the same thing.

@Cuchulainx
WOW! Thanks man. I was having trouble getting this to work. Couldn't seem to make a connection to my PC shares. Now with your help it works superb.
I can open word documents and excel spreadsheets on my phone from my computer and edit them with Quickoffice. Awesome.
Can also wirelessly transfer files from PC to phone. Cool.
Cheers mate. Clever boy!

great！！want to have a try, but don't know how to start~~

is there any way to get cifsmanager work with windows 7 which doesn't have a password? i get "I/O error" all the time.

[Guide] Mount Internal Storage in Ubuntu

First, I didn't know if this should go in development or general since most of the people who are going to be on Ubuntu will be devs, but hopefully this will be useful for everyone.
Honeycomb changed a lot of things. Most of the changes are awesome (as we know) but some of them have made certain things frustrating. Honeycomb marked the move from USB Mass Storage to MTP (media transfer protocol). Although for Windows users it actually works pretty well, for Linux users it doesn't...at least at first.
If anyone has hooked up their Xoom to a Ubuntu box then they know at first nothing happens. There is no selection on the tab to "mount" USB Mass Storage because it is not supported (which I thought Honeycomb was supposed to support both so this may change) It's like the computer doesn't even recognize anything is plugged in.
So this was very frustrating but I have put together a solution. Previously I was using a GUI interface called gMTP to connect to the Xoom and transfer files. This was an ok solution and it worked but I would still rather just use it in Nautilus like every other drive I use. Ok so starting here I will just post the commands and then explain after so no code gets lost.
Start with installing a needed program for all of this to work
Code:
sudo apt-get install mtpfs
Next we will create the device rules, so Ubuntu recognizes it as a USB device.
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
NOTE: Some of you may have already added the Vendor ID. If you don't this file will start off blank and then you need to add this next line. If it does not come up blank, then make sure you have a line with Vendor ID 22b8 and 18d1 (for bootloader which uses a different VendorId) and you are all set.
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
You might need to start a new terminal for this change to take effect for adb and bootloader access.
make the mount point and take ownership:
Code:
sudo mkdir /media/xoom
sudo chown user:user /media/xoom
NOTE: "user" in the above code is literally your user name for your box.
ANOTHER NOTE: if you stopped here you could mount by typing mtpfs /media/xoom -o allow_other and unmount by typing fusermount -u /media/xoom...but that's no fun
add the mount point to your fstab:
Code:
sudo gedit /etc/fstab
In the first unused line available you might want to type a comment like:
Code:
# mount point for moto xoom
then add this line after it:
Code:
mtpfs /media/xoom fuse user,noauto,allow_other 0 0
Next modify fuse.conf to allow_other:
Code:
sudo gedit /etc/fuse.conf
uncomment the last line which should read:
Code:
#user_allow_other
uncomment this line by removing the '#' symbol.
add your user to the fuse group:
Code:
sudo gedit /etc/group
a long file will open, press CTRL+F to bring up the find dialog and type
Code:
fuse
close the dialog and fuse should be selected and visible.
At the end of that line with no space add your user name.
Save that file. Close it.
Lastly reboot your computer.
Now when your computer restarts, if you look at your "Places" menu you will see a Drive marked with 'xoom'
Plug in your xoom, and click on xoom in Places.
Nautilus should open with all your files that you have on your device. It will also place a mounted drive icon on your desktop. If you would like to unmount, right click on that icon and click unmount.
As you can see this was a pain for me, but hopefully this solution will work for everybody. I know the instructions are really long but follow it and you will feel old school mounting your storage in your file browser.
NOTE: THIS WAS TESTED ON UBUNTU 10.10 ONLY, IF THIS WORKS FOR ANYONE ELSE PLEASE POST YOUR FINDINGS.
Also, I am fairly new to Linux actually, so if there is an easier way to mount the storage in nautilus let me know. This works for me and I just want to help out so please no flames.

Couple things I have also noticed with MTP, when you have the internal storage "mounted" you still actually have access to the files on the device. Plus the file transfer is a lot faster. Usually I had been getting about 4 Mb/s and now I get about 15. Of course this speed difference from what I am used to might be the internal storage vs. SDCard transfer rate diffs.
Last thing, is this might need to modified when the sdcard access comes since there is only one mount point specified.

not trying the artificial bump.
I guess no comments on 228 views means this is working?
Can someone chime'in if this worked for them so I can know'if it works'as is or needs to be tweaked.
Thanks

I got mount up and running last night. Works like a champ. Great work. I was tired of pushing and FTP.

Thanks for the reply. Glad it worked for you too. One thing I need to add tonight to it is the fact that the xoom uses a different vendor'id when it's in the bootloader. The one vendor id if used alone will not recognize the xoom to use fastboot but ill update it when I get home.

FWIW, the "mtpfs" package in 10.04 was broken when using the Xoom, and causing segfaults. I found the source and rebuilt that and now it's working OK.

kcrudup said:
FWIW, the "mtpfs" package in 10.04 was broken when using the Xoom, and causing segfaults. I found the source and rebuilt that and now it's working OK.
Click to expand...
Click to collapse
So, I'm on 10.04 and not getting segfaults, but after pugging in (xoom is in usb debug mode) and click on xoom in places, ubuntu gives me the error "could not open location file:///media/xoom. Error stating file '/media/xoom': Permission denied"
Would love to get a copy of your recompiled 10.04 mtpfs package as a deb file...

I found this deb package for mtpfs 0.9-1 that you can try
mtpfs_0.9-1_amd64.deb

roberj13 said:
I found this deb package for mtpfs 0.9-1 that you can try
mtpfs_0.9-1_amd64.deb
Click to expand...
Click to collapse
Unfortunately, that's not gonna work for me. I'm 32-bit.

Ill keep looking, for some reason the 64-bit was the only one there.

roberj13 said:
Ill keep looking, for some reason the 64-bit was the only one there.
Click to expand...
Click to collapse
Thanks! If i could ge this to work, it would totally be awesome!
--Q

Most excellent guide!! Thanks you for taking the time to figure this out. I'm on 10.10 so I have nothing else to add.

Works flawless on Ubuntu 10.10 running on an older Mac Pro
Thank you for posting the easy to follow guide.

This is semi-working for me in that I can successfully mount and browse the device, but there are a few problems. One, it locks up Nautilus for 30-60 seconds (grayed out and unresponsive) though it does come back. Two, file transfer speeds are very poor.
I'm trying to load two movies totaling 1 GB right now and the copy dialog says 2hrs 56 min to transfer w/ a speed of 99.7 kb / sec. This is unreliable, however, as the copy dialog is frozen on those metrics.
Build is AMD64, distro is 10.10 upgraded from 10.4.
I appreciate the effort to document this, in spite of my issues. Let me know if anyone has suggestions for a fix and I'll try them.

One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.

sogrady said:
One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.
Click to expand...
Click to collapse
I find it odd that Android dosn't play nicely with *nix.. considering they are cousins in the OS family. That it works sooo well with Windows instead offensive IMO

sogrady said:
One day later and this solution is now working for me. The Xoom filesystem behaves oddly in Nautilus, with some files not appearing that have in fact been transferred to the device, but otherwise this is the best solution I've found.
Click to expand...
Click to collapse
I've seen the same thing. Usually an unmount then mount will clear it up.

this did not work for me. i'm getting no application is registered as handling this file
i told nautilus to open it and its saying /media/xoom is not a folder

Using this guide I'm able to mount fine, but I'm seeing a couple issues:
I have my music organized like this:
Artist
-----Artist - Album
----------Music files
When I copy over the top 'Artist' directory to the Xoom's Music folder it works, but, all of the music files have been directly placed in the Xoom's Music folder and the Artist and Artist - Album folders are empty, seems pretty weird?
EDIT: It looks like the Xoom (or MTP?) forces all music files into the root of the Music directory. Even if I try copying the artist folder to the root of the device the mp3 files end up in the Music folder.
EDIT take 2: Nevermind...the Android docs say nested directories are supported for music, and Windows preserves the directory structures fine.
I'm totally unable to copy over movies. I've transcoded a file into mp4 and it seems to copy over but, once the copy is finished the file doesn't show up on the Xoom.
EDIT bonanza: Looks like I'm also able to copy over movies fine through windows...so I guess all my problems are Linux related.

I keep gettting a "Transport endpoint is not connected" error when I try this. I am using 10.04 64-bit. Does anyone know how to resolve this?

[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:

[Tool][Mac] Google Installer and Amazon Killer

About:
Scripts and packages to install Google services, aid in KingRoot, and disable Amazon services written for Apple OS X.
Requirements:
OS X, device wifi connected, debugging enabled, host RSA key accepted.
Notice:
This project is sleeping. Feel free to modify and redistribute. However, be warned that tampering with the scripts may cause unintended damage to your device.
Link:
Download v0.33
Usage:
Download and extract .zip file.
Run Terminal, cd into extracted GIaAK folder, then "sh install.sh".
Contributors:
kanderson88 - inspiration, collaboration
sd_shadow - insights
KingRoot - root

I am glad there are some happy Mac users here, I have made a bunch of neat scripts but never uploaded them. Good work.

Gonna give it a go, wish me luck! lol

#to re-enable Amazon Web view. Google web view doesn't currently step in and take over, probably needs permission to.
./adb shell
su
pm enable com.amazon.webview
pm uninstall com.Google.Android.webview
#affects things like Spotify Facebook login function, etc.

Can't download the file, keeps giving a 403 error (tried chrome and firefox) ... may want to upload to somewhere else like rghost.net or something
"NetworkError: 403 Forbidden - https://app.box.com/index.php?rm=box_download_shared_file&shared_name=6qwfdy900fydyf64lst9zi0uudcsvsg0&file_id=f_53278030645"

TripFlex said:
Can't download the file, keeps giving a 403 error (tried chrome and firefox) ... may want to upload to somewhere else like rghost.net or something
"NetworkError: 403 Forbidden - https://app.box.com/index.php?rm=box_download_shared_file&shared_name=6qwfdy900fydyf64lst9zi0uudcsvsg0&file_id=f_53278030645"
Click to expand...
Click to collapse
I had no issues downloading today. Using it soon.

Does this exist for windows? How about a similar tool?

can any one post command for manual install in windows ?

-waiting for device-
I am getting this message...
"error: device '(null)' not found
- waiting for device -"
I have the Fire HD 8 plugged into my Macbook via USB using MTP. What am I missing?
Thanks.

watson007 said:
I am getting this message...
"error: device '(null)' not found
- waiting for device -"
I have the Fire HD 8 plugged into my Macbook via USB using MTP. What am I missing?
Thanks.
Click to expand...
Click to collapse
On tablet Go into settings > device options > developer options > enable ADB.
If you don't see developer options then settings > device options > tap on build number 7 times > then tap developer options > enable ADB. You will get a pop up on your tablet asking for permission. check the box and say yes.

For Windows
Wouldn't work in windows obviously.. so I edited the install.sh so it would work. You have to use a program like cygwin.
Just delete all ./ before all adb commands.

leejuspsa said:
Wouldn't work in windows obviously.. so I edited the install.sh so it would work. You have to use a program like cygwin.
Just delete all ./ before all adb commands.
Click to expand...
Click to collapse
What version of FireOS are you on?

DragonFire1024 said:
What version of FireOS are you on?
Click to expand...
Click to collapse
I'm on 5.4.0.1 now but I think I ran it on an earlier version. I just bought it from staples in store so it probably was not by much.

leejuspsa said:
I'm on 5.4.0.1 now but I think I ran it on an earlier version. I just bought it from staples in store so it probably was not by much.
Click to expand...
Click to collapse
Did you do this before or after 5.4.0.1? We are trying to determine if uninstalling/disabling the apps is still possible on 5.4.0.1.
EDIT: Just noticed you said earlier version.

Does anyone know if this will work with the new 2017 edition?

pastorbennett said:
Does anyone know if this will work with the new 2017 edition?
Click to expand...
Click to collapse
did you end up trying it?

Can anyone modify it for linux or windows? As not everyone has a mac.

dadoc04 said:
did you end up trying it?
Click to expand...
Click to collapse
Sort of. It won't work, because Kingroot isn't yet compatible with the 2017 Fire HDs.