Database Info

[SOLVED] Infuse wont connect to Ubuntu....

UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.

weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.

Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.

Linux driver should be perfect, before connects to PC the mass storage mode should be selected.

dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/

well I see you fixed it. did you get adb going?

Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk

are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.

Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone

Newbie help with rooting Asus Transformer Prime via ViperMOD

I have never rooted an android device before and this is my first time. The reason I'm rooting is so I can enable the Virtuous Prime ROM (the guide for Virtuous Prime suggested to use ViperMOD to root first)
[ROOT] [TOOL][Updated 2.22.12]viperMOD PrimeTime v4.5 | Auto Root/Unroot/Busybox/CMW - xda-developers
^I'm following the instructions from the link above word for word. So far I've met the following Criteria:
-Enabled USB Debugging
-Running build 9.4.2.15
-Have "ASUS Android Composite ADB Interface" drivers installed and updated
I downloaded the ViperMOD 4.5 zip and extracted it to my PC. I opened the folder and right clicked on "viperMOD Primer Tool v4.5 - copy.bat". A cmd popped up with several different options; I pressed 1 to root, and pressed enter to skip the following two prompts (that ask if USB debugging is enabled and asus usb drivers are installed).
The CMD then showed the following message:
*daemon not running. starting it now on port 5037*
*daemon started successfully*
However the CMD just stopped there. It didn't show the following flood of text that should show up when rooting w/ ViperMod (like shown in this video: http://www.youtube.com/watch?v=C3OQkxmUyLc at 2:35)
I'm not sure if I'm missing something here. The guide however did say that I needed to "Kill Asus Sync and Splashtop" though I'm not exactly sure what it means by "kill". I don't have Splashtop running on my Prime nor Splashtop remote running on my PC. I also don't have ASUS Sync software installed on my PC and I disabled Auto-Sync on my Prime (HOWEVER, the ASUS Sync icon is still visible in my Prime's notification bar when I connect it via USB to my PC).
Any advice?

I had a similar problem
I tried to use superoneclick to root my Samsung Gravity and it hung on waiting for phone. I used the adb commands to load the zergRush exploit. So you need to find which exploit works on your phone, adb push the exploit, busybox, and su to your phone and use adb shell to do the root.
** DISCLAIMER: I'm pulling this command sequence out of my memory... you should find a better guide but this stuff may give you clues as to what to google for, or if you're familiar with shell you may see the gist of what you're trying to do **
The commands will look something like this:
adb push exploitfilename
adb push busybox.apk
adb push su
adb shell
chmod 755 exploitfilename
./exploitfilename
(wait for the exploit to finish)
pm install busybox.apk
pm install su.apk
reboot
Once it rebooted, I installed terminal through the market so I could do cool stuf like so:
su
mount -o remount,rw /dev/whateverdevhasyoursystemfolder /system
rm /system/app/Vendorgarbagebloatapp.apk
and so forth. Knowledge of linux and shell commands is your friend here for sure. Basically, you should know what you're doing or don't do it. I'm no fan of one-clicks for anything like this, it's too hard to figure out what went wrong if it goes wrong, plus this way you can learn new skills.

Can't seem to run Vipermod
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.

sasori563 said:
I am trying to run vipermod on my computer but when I try to run it, it flashes on the screen for less than a second and then re-closes.
For a little extra info I have a tf101 running the 9.2.1.17 build
My computer is running the window 8 developers copy( no i'm not a dev just love testing new things before most other people.)
I've tried running it as an admin and in compatibility mode but have had no success as of yet any help would be greatly appreciated.
Click to expand...
Click to collapse
U should tried on another comp with windows seven imo

I would if i had one but my laptop got stolen so my only computer besides my desktop is my transformer, Are their any .bat files out their that i can use to run it from? I found out that its a problem with windows 8 not allowing .exe files to open command prompts, but if its a .bat file it will run.

[Q] adb not seeing my device...

I'm running "Megatron" 1.0.4 on my Transformer. However this was occurring with the predecessor CM9 build (before the author renamed to it "Megatron"). I had switched from the Stock asus rom to CM9 a while ago, I was running the 3/29 build of CM9 (as mentioned above), which turned into Megatron.
I use adb to push and pull files to/from my tablet, as i find MTP to be utterly useless. I also use adb for shell access and other things when i'm tinkering with Android.
adb was working perfectly, On the 3/29 build of CM9. I was quite happy with 3/29, which is why i ran it for the entire month of april, without updating to "Megatron". However, one day, adb suddently stopped detecting my device. Restarting the adb server doesnt help, i've tried doing things like wiping cache on my device, nothing helps. I updated to Megatron 1.0.4 to see if that would help (thinking it was a software thing), with no data wipe, the tablet is again working perfectly except for the adb issue.
When i connect my tablet to my pc over its USB cable, the notification area disaplsys that usb debugging is enabled, but i still can't detect it with adb.
So, how can i continue to troubleshoot this? Is there some sort of debugging log i can view? Or enable some verbose mode?
Any suggestions would be great. Thanks!

Just did a full wipe, still, adb is unable to see my device.
Some extra info.
My PC is Linux, Fedora 16.
adb version:
$ adb version
Android Debug Bridge version 1.0.26
I havent updated it in a bit, but as stated earlier, neither it, nor the tablet's config changed when this stopped working.

[SOLVED] Problems rooting using debugfs method

Hi everyone, I've been doing a good bit of googling and found nothing yet, so if this has been asked before I'm very sorry but I haven't yet seen anyone on the forum with the exact same issue. I actually updated to JB OTA when I first got the device in Canada (US version), when I got back to the UK I decided to root, but then found out that you can't on JB, luckily I managed to downgrade to ICS V9.4.5.30 downloaded from the ASUS website! I was not able to downgrade to an earlier version however, stock recovery wouldn't allow it so NVFLASH root method is out the window... Now I would prefer not to unlock my bootloader for now.
When running debugfs.bin 1 click root method, on my desktop (not run as admin) it says:
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
*daemon started successfully *
'find" is not a recognized as an internal or external command, operable program or batch file.
Less than half a second later it just closes down.
When run as admin, it does the same thing and instead of closing down it goes back to the first screen where you can select what method you want to use.
On my netbook it runs and just stops at daemon started successfully, the tablet has no response and debugfs just stays on that screen till I close it down.
Both my computers have all the correct drivers and the latest version of debugfs running, both are windows 7 Ultimate 64-bit.
Please help me as my Infinity is just sitting around doing nothing as when I downgraded to ICS all 190 apps I installed were wiped too, and obviously there's no point me reinstalling any apps till I get this bad boy rooted...
Many thanks in advance!

Make sure you're connecting to a USB 2.0 port, not 3.0, on your computer.
Try not to use any intervening USB hub.
Try to make sure that you're using the back ports on a desktop machine as sometimes the front ports and be a bit sketchy.
Reboot both tablet and computer before starting, and as always, make sure the tablet has USB debugging enabled.

only my netbook has usb 3.0 and I used the 2.0 port, I will now try the back ports of my desktop, I didn't use any extensions or usb hubs, I have debugging and unknown sources checked. I have tried the restarting already, which I'll do right now again... thanks though..

Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?

Android SDK and Java DK were not installed, just installed them still exactly the same issue, haven't rebooted since installing them though
Is there a way I could use Linux to root, as I do have Linux Mint running?
johnlgalt said:
Code:
@adb kill-server
@adb wait-for-device
@adb shell mount | find " /system" | call RootDebugfs.bat x
That is where you're system is tripping up. For some odd reason when it runs that part of the script, it trips up.
It's not a device not found error, b/c it would 1) say that, and 2) never make it to that last line, just hang at the previous line. Yet when I connect my Infinity it works perfectly fine on mine. For some reason the command "find /system" is not working correctly on your system after performing the shell mount command.
Do you have the Android SDK installed on your system?
Click to expand...
Click to collapse

I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link

johnlgalt said:
I dunno why it is not working then. What you're doing is exactly what I did *successfully* to root my Infinity and then take the JB upgrade ans restore root.
I have another file called Infnity Root that you can try: check your PMs for the link
Click to expand...
Click to collapse
Thanks so much anyway! I've already tried that file, it's exactly the same

Yeah, it looked very similar, but it included more things in the actual Download like the drivers.
Not sure why it is not working - can you run those three commands in a command prompt window and see what you get?

well they say 3's a magic number, computer number 3 worked! For some reason something on my desktop and netbook was causing the root to fail, now I'm updating to jb ota... Thanks for the quick responses otherwise I would have assumed the problem was with the tablet and not my machines...

Glad you got it working. Quite possibly an antivirus program, firewall, or other such problem.

Adb devices show blank after Twrp wipe

I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.

Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk

Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!