Database Info

[Q] Tether Wifi XOOM via USB OTG?

Is it possible?
It doesn't work by default when connected to an android device with USB tethering enabled.
My guess is that there needs to be software in place to bring up the USB network?

Oops. Mod please move to general.

I'm pretty sure the latest tiamat kernel supports this
Sent from my Xoom using XDA Premium App

I have been trying to set up/enable USB tethering from my rooted Droid Incredible (running CM7) to my rooted Xoom (HC 3.1, kernel 1.4.2, wireless only).
When I type : "Cd /dev/block" then "ls" on my Xoom terminal I can see "sda" for phone and "sda1" for my USB flash drive. And my phone recognizes the USB connection to my Xoom.
But when I type "busybox mount /dev/block/sda1/mnt/usbotg" on Xoom, the response is > "mount: can't read '/etc/fstab' : No such file or directory"
And while I can enable USB tethering on my phone, my Xoom doesn't recognize it (of course). My phone is also charging from the Xoom.
Sent from my Xoom using Tapatalk

Same problem. Using the tiamat kernel, have USB tether enabled on the phone, but the xoom doesn't recognize it. Is there something I need to do in user space to enable the tether on the xoom?
Sent from my Xoom using XDA Premium App

Thread moved to Q&A... Since it's a [Q]uestion.

satadru said:
Same problem. Using the tiamat kernel, have USB tether enabled on the phone, but the xoom doesn't recognize it. Is there something I need to do in user space to enable the tether on the xoom?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
This was posted by BigRushDog a short time ago :
" I have to check, but I may have borked Vold.fstab in the 3.1 update. I'm gonna release 1.4.3 in a day or so. Ill clean it up."
Sent from my Xoom using Tapatalk

[Q] MTP driver issue

Ok i just picked up my 32gb wifi only xoom. whenever i try to install the drivers it finds the files it needs but produces the following error, "A service installation section in this INF is invalid", WTF do i do tried uninstalling the drivers and anything i can think of ive rooted numerous phones before. is this a problem with the xoom itself and should i take it back?

josephparlangeli said:
Ok i just picked up my 32gb wifi only xoom. whenever i try to install the drivers it finds the files it needs but produces the following error, "A service installation section in this INF is invalid", WTF do i do tried uninstalling the drivers and anything i can think of ive rooted numerous phones before. is this a problem with the xoom itself and should i take it back?
Click to expand...
Click to collapse
check to make sure you have windows media 11 or higher on your computer. I had that issue. Running XP I had an issue but Win 7 it installed easily..
This is what I used
Motorola_End_User_Driver_Installation_5.1.0_32bit.msi
MotoHelper_2.0.49_Driver_5.0.0.exe
Windows Media 11
Also search around on google lots of people have had this issue and thats how I found my answer.. Also xoomforums.com is a good site for answers as well

OK so I installed wmp11 and it will recognize my xoom thanks for the tip. however now I cannot get ADB to work my device is there I have every sdk ever made down loaded and I have the moto USB driver mentioned installed but I can't get into a ADB to save my life.
Sent from my Xoom using XDA Premium App

Try un/check/ usb debuging, don't remember witch is correct...
Had this problem with adb...
Sent from my Xoom using XDA Premium App

makokoko said:
Try un/check/ usb debuging, don't remember witch is correct...
Had this problem with adb...
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
usb debugging needs to be checked in order for the adb to work.

[Q] Rooting Kindle Fire 6.3 >> KFU 0.9.4 or BurritoRoot4??

I've got the same problem as lots of KF rooted user >> the 6.3 update broke my root. My KF 6.2.2 was rooted using BurritoRoot3.
I've been searching the web and found a manual solution using fastboot mode (See "HOW TO Root Amazon Kindle Fire 6.3" http://www.blogotechblog.com/2012/03/how-to-root-amazon-kindle-fire-6-3/). It looks do-able but definitely more involved than some of the pre-scripted rooting tools.
Anyone know if/when some of those tools [i.e., KFU 0.9.4 or BurritoRoot(4?)] will be available?
Does anyone have contact info for the KFU developer --> I'd email them directly and ask.
Alternatively, I found this post on XDA >> "Rooted Kindle Fire 6.3 fixed using Kindle Fire Utility" http://forum.xda-developers.com/showthread.php?t=1571622
I don't have KFU installed on my Fire, though. Can it be installed on my Fire since I now have 6.3? If yes, where can I get the steps to do that?
Thanks!
~K

in the same boat. no idea on br4, but i've read quite a few places that KFU 0.9.4. works well. not sure of what steps to take EG 1) temp root 2) perm root 3) flash FFF ..ETC also, do u know if there are .sbf/ruu files to return this thing to stock if something fails? i'll pm if i find more info plz do the same..

Has anyone replied to you yet or have you figured this out? I've got my Fire rooted again & it's running 6.3. I can help you get yours working too.
Sent from my Kindle Fire using xda premium

What's possible on a rooted Fire
And, I've got other stuff working on my Fire that other users were struggling with; such as:
• Swype keyboard
• HBO Go
• Screenshots (w/ app that requires root)
• Wireless printing
• Synched my Google acct to run Gmail & Listen w/o changing the stock launcher
• Have my Verizon Droid Razr broadcasting infrastructure hotspot *w/o* paying Verizon extra $30/mo
• Set up external wireless drive & converted DVDs to watch w/o wireless connection
None of this has taken up much memory - I'm only using about half my app memory space. You probably have much of this working too, but if not, ping me for info. I'm always happy to share.
~Kat
Sent from my Kindle Fire using xda premium

Tried FBmode to reroot no luck
Hi,
I tried following instructions using fbmode. Got hung up on TWRP boot would not
go to yellow triangle for reboot. Tried running Fire Utility does not work - errors.
How did you reroot yours?

What error did you get when using KFU and what version of KFU are you using? I used KFU 0.9.5 and I realized that on the K Fire, KFU does not install the SuperUser.apk. Try running the most recent version of the KFU, then install the SuperUser.apk manually by sideloading it. That worked for me.
If you are going to run the Fastboot commands youself in a Windows command window, make sure of 2 things >> 1) you are running the commands from the directory where you have ABD installed and 2) that your laptop has recognized your K Fire (when you plugged it into your Laptop, your laptop loaded the K Fire drivers and you can see it as a drive in your Windows explorer). I got stuck in a boot loop with TWRP myself after I'd rooted and it took me a while to get out of it -- after I made sure of those two things above, the commands worked perfectly.

KFU
I was using the older 9.4 version - will give the new version a try.
Thanks,
Leapin

KFU 9.5 Works!
Thanks morgan - 9.5 worked !

KF rooting troubles
Using KFU 9.5.0 I've got my computer recognizing my KF as an android phone but KFU will not see that my KF is connected to my computer. I am eternally stuck in <waiting for device> mode. Any help would be greatly appreciated.

What version of firmware is your Fire running - 6.2.2, 6.3, or 6.3.1? I know that KFU 0.9.5 supports firmware 6.3 and 6.3.1. Not sure if 0.9.5 supports the older 6.2.2. If you're running 6.2.2, you might need to run KFU 0.9.4.
I've gotten stuck at the 'waiting for device' prompt too. In my case, my Fire wasn't showing up as a device in my laptop's device manager. You're certain that your Fire is accessible? Does the Fire screen show the message that it's got a USB connection?
When I've had a problem with KFU, I contacted the developer Vashypooh. Got a really quick response too.
[email protected]
Vashy also monitors this IRC channel and, if online, will answer questions/provide help immediately:
http://chat.andirc.net/?channels=kindlefire
One other question -- are you running KFU from a Windows PC or a Mac? If you're on a Mac, I probably won't be much help -- I'm really more a Windows/Linux kind of gal.
Sent from my Kindle Fire using xda premium

[Q] MTP mounting under Linux

I had ICS on a different tablet and had no trouble using mtp with Linux either through the device mounter (KDE/Plasma) or just using mtpfs. With the Samsung 5113 though I "see" the MTP device but it times out. Here's an mtp-detect log:
Code:
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
Found 1 device(s):
Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 26
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
Any ideas? Yeah, I know I can use sshfs and a variety of other ways to get to the device. Just wondering why MTP seems broken.

Bumping this thread ...
I recently upgraded to Fedora 17 and found that libmtp has a known defect that prevents the tablet from connecting. Perhaps you've got the same issue on your nonfunctioning system.
Did you ever find a solution? I now copy files to/from my tablet using scp.
Sent from my GT-P3113 using xda app-developers app

jeffm5150 said:
Bumping this thread ...
I recently upgraded to Fedora 17 and found that libmtp has a known defect that prevents the tablet from connecting. Perhaps you've got the same issue on your nonfunctioning system.
Did you ever find a solution? I now copy files to/from my tablet using scp.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
No real solution. Like you, I use scp or ES Explorer or adb or some other mechanism.

I did a little more research this morning and got mtp to work between Fedora 17 and my 3113 tablet.
I did a couple things in total, although I'm thinking the 2nd one was the solution:
1) add vid/pid pair to my 51-android.rules file with 0755 permissions
2) disabled "USB debugging" under development settings. Apparently with that enabled, you can only move files with adb [push | pull].
Now I can connect my tablet to my Linux machine with a USB cable and create files/folders with the Linux file manager.
Hope it works for you as well. Copying with scp over wireless is pretty painful.
Sent from my GT-P3113 using xda app-developers app

jeffm5150 said:
I did a little more research this morning and got mtp to work between Fedora 17 and my 3113 tablet.
I did a couple things in total, although I'm thinking the 2nd one was the solution:
1) add vid/pid pair to my 51-android.rules file with 0755 permissions
2) disabled "USB debugging" under development settings. Apparently with that enabled, you can only move files with adb [push | pull].
Now I can connect my tablet to my Linux machine with a USB cable and create files/folders with the Linux file manager.
Hope it works for you as well. Copying with scp over wireless is pretty painful.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
Ah. I do development so never thought to try that. I already have the machine in my udev files. Turning off USB debug did not seem to work. I went back and killed my adb-server (which I confess was running) and that still didn't work. May try everything again after a clean boot. But the symptoms were the same.
Still, might be something to it.

The MTP mounted device now seems to work but it doesn't really seem to be stable or fast. I can copy small files easily but large files really don't seem to copy any quicker than scp. I did successfully copy a 1.7GB mp4 movie without any problems but it took almost 20 minutes with mtp/USB connection.
Sent from my GT-P3113 using xda app-developers app

jeffm5150 said:
The MTP mounted device now seems to work but it doesn't really seem to be stable or fast. I can copy small files easily but large files really don't seem to copy any quicker than scp. I did successfully copy a 1.7GB mp4 movie without any problems but it took almost 20 minutes with mtp/USB connection.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
Still can't get it to work. I already had the udev rules and turning off USB debug didn't help. We aren't the only ones with issues. Lots more detail here: http://forum.xda-developers.com/showthread.php?t=1077377
Also gphoto2 has some success in reading info from the "camera" (for example, battery level) but I still can't get it to see any files.

Are you running a stock kernel? I'm running the kernel that comes with CM9. I wonder if that has anything to do with it. Thx for the thread URL. I would like to get a reliable wired transfer solution.
Sent from my GT-P3113 using xda app-developers app

jeffm5150 said:
Are you running a stock kernel? I'm running the kernel that comes with CM9. I wonder if that has anything to do with it. Thx for the thread URL. I would like to get a reliable wired transfer solution.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
Well, I am semi-stock. It is the 4.0.4 stock with my own init.d add on and rooted. But yes, it is the stock kernel. I keep thinking of switching to CM9 but suspect it will cost me my IR blaster. I don't use it very often but I always think I will But I know it is just a matter of time before I switch.

Even stranger. If you click on the USB options and pick PTP mode, your root directory of internal and external show up and gphoto2 sees it all. But all the subdirectories are empty! So close, but no cigar. gphotofs, as you would expect, sees the same thing.
Update: ok so here's an answer for ADB: https://github.com/isieo/adbfs
Doesn't handle symlinks but on the other hand you can get to the whole file system.
One thing though, adb MUST be on your path for this to work. The adbfs file can be anywhere and it doesn't matter if it is with the adb executable or not.

[Q] ADB Stopped Working in Windows 7

Hey all,
Was going to post this in the Android section but I figured this is more of a Windows issue, so if I misplaced this I'm sorry.
A couple of days ago my ADB stopped working. I have tried connecting with both my GNex and my TF700, over wired ADB and ADBWireless. With wired it sees not devices and in wireless I get "can not connect to xxx.xxx.xx.x".
I thought that maybe my SDK was out of date so I did update it (a few packages did update) but still no luck. The only thing I can think of that has changed is I did receive a Windows update a few days back.
Has anyone else experienced anything like this? Anyone have any ideas?
Thanks in advance,
Blake

Update java too. Alt ctrl delete and kill ALL runned adb next run your program.
Sent from my SK17i using xda app-developers app

thanks too