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

Trouble getting adb to work

Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob

SD card not found
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob

emueyes said:
Sorry about the uninspiring title, but after an afternoon of this I'm uninspired. All I wanted to do was root this Xoom so I could take some screenshots..
I can get the tablet to stage where it says
--> fastboot
starting fastboot protocol support.
at which time I assume I can start adb. I've tried the USB drivers from the PDAnet package, but when I plug in the Xoom I get a desktop notification saying 'HTC Exit -1' (sorry, that may not be the exact wording, but the same effect).
in that 'fastboot' state, adb devices tells me there aren't any devices connected
the Xoom show up OK when booted into Android, Windows (7, 64 bit) sees it as a drive, and Device Manager sees an MZ604. adb still doesn't see anything
I started off by using the minimum set of utilities (adb, fastboot and their dlls) and then installed the SDK and used its tools (yeah, I've pathed everything properly, I was writing DOS batch files in 1985... and now am a grumpy old man )
The Xoom is Australian WiFi only, runs Honeycomb 3.2.2, hasn't been rooted (I'm trying to do that)
speaking of old, though, the fiddly volume rockers get that way (and or so ironically are used for screenshots in ICS I believe)
I have a feeling that I don't have the proper USB driver installed, I've uninstalled PDAnet, and the Xoom still shows up in windows, but since I can't get a root prompt on the Xoom have no idea what it's using
Any ideas?
Rob
Click to expand...
Click to collapse
What USB cable are you using? Try to use your Xoom oem cable. Also, make sure that you try different USB ports, especially the ones tied more directly to the pc motherboard. It's finicky like that. Recheck your drivers. I'm not familiar with that PDAnet source. Motodev is the place to get them from. You may also need the java sdk from oracle.
There are some useful guides on setting up adb/fastboot/rooting in General...you may have to go back a few pages but it will be worth it to make your task easier.
Good luck!
---------- Post added at 10:51 AM ---------- Previous post was at 10:47 AM ----------
emueyes said:
I may as well get all my woes into the open
When in Recovery Mode, the Xoom won't recognise the SD card, it seems to be trying to mount it on /sdcard
I have some zip files of a rooted Honeycomb image, and was going to triple cjeck whether flashing a zip file was a good idea or not first, but I don't get that far
I can see the card and contents from Windows while it's mounted in the Xoom
I should be able to use the card from recovery mode, right?
Rob
Click to expand...
Click to collapse
Which recovery mode are you talking about? Have you unlocked and installed a custom recovery, as in a ClockworkMod-based recovery? If so, which one? They have some different behaviors. If it is stock recovery, I don't think it sees the external sdcard at all.

Also make sure usb debugging option is enabled. And flash another recovery image.
You don't really need to root. Just unlock the bootloader. Push the recovery image. Reboot to recovery. And flash a pre rooted rom from team EOS.
Sent from my MZ601 using Tapatalk 2

[Q] Stuck rooting Samsung Galaxy S2 on Linux using Heimdall: device not detected

I hope this is the right place to post, apologies if not.
I'm trying to root my Samsung Galaxy S2 from stock.
I'm running Linux [Fedora 17 64bit]
I've installed Heimdall, and I've got what I think is the nearest zImage to my kernel.
Have added the 51-android.rules file
and set phone to allow debugging via usb
Settings > Applications > Development and enable USB debugging
However Heimdall reports that it is unable to detect my device.
This is very understandable as when I try
Code:
lsusb
my phone doesn't show up.
Any ideas anyone?
As an aside I have difficulties getting fedora to connect with my phone in normal mode, and have to use this workaround: [link removed as I have under 10 posts]
so as to unbind the ehci_hcd. But I think this is quite common.
Any help greatly appreciated.
Chris

Rooted it.
I have no idea what was wrong with doing it on my main machine.
But I just tried it on an ancient laptop with lxde fedora on it.
So ancient that I had to edit the boot code to not check for machine RAM before installing the lxde.
Yet it all worked perfectly cleanly first time within seconds!
I didn't even bother setting the android rules file.
Either way, all is good, and obviously heimdall + usb = finickety
my advice to others is just try it on a different pc.

[Q] Velocity CRUZ T103 (PT701) bricked

Oh I am hoping someone here can help me out here. I just got this tablet, and tried to do the Froyo update, only to find out (too late) that this model is different and not up-gradable to the 2.2. After screwing around a bit with it, not sure what happened, but now the entire system is gone.
It boots to the Cruz logo, and sits there. ADB recognizes it, but I have no shell access, and when I do a ADB ls /system it lists only 2 files, with random numbers.
ADB remount - FAILS
ADB reboot fastboot - FAILS (just reboots it)
ADB reboot recovery - gets to recovery (in ADB devices) but tablet is blank, but no sh access
Vol + & power do nothing.
Vol - & power do nothing
While attached to my PC (Win7-64) and hit the reset and Vol -, it shows up as JZ4760 USB Boot, but Windows REFUSES to let me install any drivers for it. (Got the USBToolKit, but even after turning off driver signing, it still says they're not signed and refuses to load them)
I got the 2.0 firmware (default) so now what I need it a way to push the img files to the tab (hopefully)
Any ideas, or is this thing really a neat little brick now?
Thanks

No one?? Come on guys...I've been on this site for a long time, and have seen some of you pull out a brick and make a phone out of it again. LOL
I'm thinking if I can just get fastboot to load somehow on the tablet, I could issue commands from my PC to "push" the image files back over.
Question is: how do I get fastboot to get onto the tablet to load into???

I would like a copy of your firmware if still available for the cruz of course impossible to find as site is no longer hosted

[Q] Hard bricked kindle fire 2(omap4430)

First of all this is my first post and I am a complete NOOB.
Also I apologize in advance if I break any rules with this post and please excuse my terrible grammar and spelling.
Computer 1:Windows 7 Ultimate 32bit
Computer 2:Ubuntu 12.04 LTS
Device: Amazon Kindle Fire 2nd Gen
I will try to provide as much information as I can stating how I got here
Eastern Time:
11:00pm : Decided to root and flash a custom rom on my friends kindle fire hd 10.4.6 have rooted and flashed my first gen kindle and a galaxy s before successfully. So i looked around the forums and found this http://forum.xda-developers.com/showthread.php?t=2494232 The last comment lead me to this site staticchaos.freeoda.com/fire/ where I downloaded the following files
1)Kindle Fire USB driver
2) RootFire.zip
The RootFire.zip had http://imgur.com/uqFGWyu
and i rooted the device using the RunME shown http://imgur.com/OCYoM9p
11:49pm: Happy and dandy rooted and superuser was installed no problem now I had to install TWRP so I followed http://forum.xda-developers.com/showthread.php?t=2404120 and
I thought everything was fine until I realized that in the post the version he says to download is CM-10.1 and I had downloaded cm-11-20140106-NIGHTLY-otter2.zip from the link he provided. I realized that after I was in TWRP after wiping all the caches and the system I went to install it and it gave me an error which i don't remember what it said.
12:40am: So now im trying to figure how the hell to mount the kindle back so I can transfer the rom out and put the correct one in. I see there is a mount option in TWRP but it would always show up as a hidden removeable disk and when i looked at the command line it said
"E: unable to locate volume information for usb storage mode"
So i googled that and found this post http://forum.xda-developers.com/showthread.php?t=2274315
I figured okay I don't have a fastboot cable so let me try the sideboot loader. But now my computer running windows 7 ultimate 32 bit was not recognizing the kindle like before. It came up as kindle fire2 and the previous drivers werent working
so when i ran cmd an issued the adb devices command nothing showed and I was unable to sideload anything.
So then i got to thinking the error said it could not locate volume information, there was an option in TWRP that said format or partition I don't remember so the idea in my noob brain was ill partition a small part of the memory inside to hold the correct ROM and than flash it using TWRP and problem solved. until this point I could turn my kindle off and on and be able to get into TWRP no problem just hitting the power button.
After the third try of partitioning and each time failing because it could not mount "/data"
i got fustrated and went looking for answers but the kindle was dying at 3% so i shut it off and let it charge while i looked. MISTAKE
i powered it off via the power button and the light disappeared when I went to turn it on again I had no luck BLACK SCREEN and nothing
SO i turned on my xbox and decided Ill play while it charges.
1:40am: no luck nothing on the screen cant get it to come up on the computer F Me i bricked this thing. Finally wiggle the usb around plug out of the hub and directly into the computer and BAM OMAP4430 is being connected and disconnected continuously
YES WE HAVE LIFE. So i began looking at what it is and found several post
http://forum.xda-developers.com/showthread.php?t=1413951
http://forum.xda-developers.com/showthread.php?p=20565446
http://forum.xda-developers.com/showpost.php?p=19800610&postcount=74
First i found out that im in the "cpu's USB boot mode. You need to send the cpu something to boot over usb or it will loop forever trying to find something to boot off flash".
so I powered up my vmware and transfered all the files in I would need to run 2) Open a terminal and sudo or su to root. It's easier that way.
3) Unplug the USB or AC adapter if it's plugged into the KF. But have the USB cable's A end plugged into the PC. This is very important.
4) Turn the power completely off. Do a shutdown if actually running Android, or hold the power button until there's no LED or backlight.
5) Pry open the back cover. The iFixit teardown (Google it) gives some ideas on how to do it, but be really careful because it's easy to snap the tabs along the long sides. DID NOT DO THIS SINCE I HAD READ ELSEWHERE I WAS ALREADY IN THIS MODE
6) The power must still be off. If you accidentally powered it back on, turn it back off.
7) Run:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
This will chain load aboot, FIREFIREFIRE, then TWRP.
This got me nothing expect waiting for
OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
< waiting for device >
and then the terminal just stood there so then on another thread I read
http://forum.xda-developers.com/showthread.php?t=1413358
" run the script usb_fix_parts_and_install_fff_twrp and plug your device in while off when it says <waiting for omap44xx device> in the terminal. The script should run when your device boots up because it`s in this state. I don`t believe you will even need the short trick"
yes a solution finally after looking for so long!
3:37am: download the files run the script run the
[email protected]:/home/orlando/Desktop/rekindle/rekindle# ./fk
5837+1 records in
5837+1 records out
5977554 bytes (6.0 MB) copied, 4.69615 s, 1.3 MB/s
Stopping any running adb servers...
Done. Tools are in /root/firekit. Files copied to USB are likely in /cdrom
Scripts:
install_fff_twrp_from_stock - install FFF and TWRP while in stock Android
install_fff_twrp - install FFF and TWRP while in fastboot
fix_parts - restore partition table to stock while in fastboot
normal_boot - set the bootmode to boot android and reboot while in fastboot
usb_boot_twrp - USB boot TWRP without installing
usb_install_fff_twrp - USB boot FFF, install FFF and TWRP
usb_fix_parts_and_install_fff_twrp - USB boot FFF, restore partition
table to stock, install FFF and TWRP
Good luck. -pokey9000
[email protected]:~/firekit#
[email protected]:~/firekit#
[email protected]:~/firekit#
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
unexpected 2ndstage response
Fixing partitions...
< waiting for device >
"YES ITS GONNA FIX IT"
20 mins later
"NOPE"
It froze there and the kindle kept connecting and disconnecting it is now 4:30am
it will still only connect and disconnect as OMAP4430
If the developers or someone who knows more than me would be kind enough to lead me in the right direction I would appreciate it
I have tried hard to fix this thing and no luck.

+1
+1

Is this considered as terminal?
As a super hard core bricked?
*i'm here now all ill be doing now buying is broken Screen Kindle and assemble with my good screen

Try search on YouTube for Tekify lollipop or marshmallow on Kindle fire HD. He has a real easy to follow step by step. I used him on 2 kindles both with success in minutes.
Or: www.tekify.co.uk/kindle-fire-hd/roms/cyanogenmod-13-6-0-marshmallow