Related
Hi all,
I am trying to get fastboot to work on Mac OS X with my Xperia Play. I can't seem to get it to recognize my device at all.
It works fine in Windows when using fastboot on my other computer. (I have gotten it to work this way) ADB works in OS X for me and sees the device just fine. It's just whenever I try to use fastboot it never will see the device.
Here is some interesting findings. The device is connected and in fastboot mode (the led is blue) and OS X seems to see it. Issuing 'system_profiler SPUSBDataType' in terminal gives me the following:
Code:
USB High-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x283a
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0xfa
S1Boot Fastboot:
Product ID: 0x0dde
Vendor ID: 0x0fce (Sony Ericsson Mobile Communications AB)
Version: 1.00
Serial Number: CB5A1GD1EX&ZLP
Speed: Up to 480 Mb/sec
Manufacturer: Sony Ericsson Mobile Communications AB
Location ID: 0xfa200000 / 2
Current Available (mA): 500
Current Required (mA): 0
Whenever I issue 'fastboot devices' it yields nothing. If I start the phone up normally and issue 'adb devices' I get the device readout fine.
Has anyone else had this issue or ran into such problems? I feel like I might be overlooking something. Please excuse my ignorance on the subject. This all is still very new for me, as this is my first android device and I just got the phone over the past weekend.
Any help would be greatly appreciated. Thanks!
xSoNiCcRaCkErSx said:
Hi all,
I am trying to get fastboot to work on Mac OS X with my Xperia Play. I can't seem to get it to recognize my device at all.
It works fine in Windows when using fastboot on my other computer. (I have gotten it to work this way) ADB works in OS X for me and sees the device just fine. It's just whenever I try to use fastboot it never will see the device.
Here is some interesting findings. The device is connected and in fastboot mode (the led is blue) and OS X seems to see it. Issuing 'system_profiler SPUSBDataType' in terminal gives me the following:
Code:
USB High-Speed Bus:
Host Controller Location: Built-in USB
Host Controller Driver: AppleUSBEHCI
PCI Device ID: 0x283a
PCI Revision ID: 0x0003
PCI Vendor ID: 0x8086
Bus Number: 0xfa
S1Boot Fastboot:
Product ID: 0x0dde
Vendor ID: 0x0fce (Sony Ericsson Mobile Communications AB)
Version: 1.00
Serial Number: CB5A1GD1EX&ZLP
Speed: Up to 480 Mb/sec
Manufacturer: Sony Ericsson Mobile Communications AB
Location ID: 0xfa200000 / 2
Current Available (mA): 500
Current Required (mA): 0
Whenever I issue 'fastboot devices' it yields nothing. If I start the phone up normally and issue 'adb devices' I get the device readout fine.
Has anyone else had this issue or ran into such problems? I feel like I might be overlooking something. Please excuse my ignorance on the subject. This all is still very new for me, as this is my first android device and I just got the phone over the past weekend.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
you are not alone bro and I'm not new to android have rooted everything ive had. some were tricky but this damn xperia is kicking my a$$.. im on windows 7
Thanks bori!
I did some extensive research on the issue and it seems a lot of people are also having the same issue on all platforms. From what I found the issue seems to fix itself on Windows by installing the google_usb and fastboot drivers. On linux it seems the issue is in adding the device's vendorID to the udev configuration. For Mac it is just suppose to 'work'. Sometimes these fixes work, sometimes they don't. For everyone with the issue for OS X though, not a single one had a solution or a person that got it working unfortunately.
It seems to be a very tricky device indeed.
bori1030 said:
you are not alone bro and I'm not new to android have rooted everything ive had. some were tricky but this damn xperia is kicking my a$$.. im on windows 7
Click to expand...
Click to collapse
if your on Win7 like me its piss easy.
http://www.youtube.com/watch?v=LRH3pC7MhEA
you shouldnt have any qs after the video. The only thing you do is hold the search button for Fastboot blue led mode
I don't know if you are still trying to do this or not, but I just stumbled upon this thread while doing some research of my own. I am running 10.6.6 and say, for example, if I want to boot the CWM that is listed in the developer forum, all I have to type is "fastboot-mac -i 0xfce boot recoveryPLAY.img" Just make sure that your phone is in fastboot mode. Power off the device and while holding the search button plug in your USB cable. The LED should be blue. If you notice the 0xfce is the vendor id for the phone. Adding the -i 0xfce works for any of fastboot's commands, ie fastboot-mac -i 0xfce flashall, etc
Hi all.
I have seen this in another kind of devices but haven't found thread related about Kindle Fire (1st gen).
A little introduction:
- My kindle was in CM10 and I noticed it started to be detected as Unknown Device in Windows, so
- I used TWRP to flash 6.3.1 stock ROM BUT forgot to wipe before flashing and rebooting. In that moment my situation was an endless loop wih the Kindle being rebooted after 15 seconds aproximately.
- I modified a cable to make it "factory cable" but even in fastboot (plain kindle fire logo) the Unknown Device was there.
- After many tries I managed to make a Reset to factory defaults in Android in the 15 seconds
- Currently the kindle is in stock ROM but still is not correctly detected.
Of course, I have re-installed the drivers in my computer and even tried in a fresh windows installation with no previous drivers without luck. Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
So, if some of you have any idea to try, please tell me. I have the factory cable and the back cover of the kindle removed... ready for anything!
Thank you for your time!
soukron said:
Hi all.
Also, booted an Ubuntu USB with SoupKit and no lsusb changes after plugin the device (just a few dmesg messages about being unable to enumerate USB device on port).
Click to expand...
Click to collapse
This is the part I mentioned before about dmesg messages:
Code:
[ 234.956030] usb 2-5: >new full-speed USB device number 4 using ohci_hcd
[ 235.136035] usb 2-5: >device descriptor read/64, error -62
[ 235.420038] usb 2-5: >device descriptor read/64, error -62
[ 235.700026] usb 2-5: >new full-speed USB device number 5 using ohci_hcd
[ 235.880055] usb 2-5: >device descriptor read/64, error -62
[ 236.164040] usb 2-5: >device descriptor read/64, error -62
[ 236.444025] usb 2-5: >new full-speed USB device number 6 using ohci_hcd
[ 236.852030] usb 2-5: >device not accepting address 6, error -62
[ 237.028025] usb 2-5: >new full-speed USB device number 7 using ohci_hcd
[ 237.436025] usb 2-5: >device not accepting address 7, error -62
[ 237.436037] hub 2-0:1.0: >unable to enumerate USB device on port 5
And there's no reference in lsusb:
Code:
[email protected]:~$ lsusb
Bus 001 Device 004: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive
Bus 001 Device 005: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 002 Device 002: ID 04ca:0022 Lite-On Technology Corp.
Bus 002 Device 003: ID 046d:0a0b Logitech, Inc. ClearChat Pro USB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/10p, 12M
|__ Port 3: Dev 2, If 0, Class=HID, Driver=usbhid, 1.5M
|__ Port 4: Dev 3, If 0, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 1, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 2, Class=audio, Driver=snd-usb-audio, 12M
|__ Port 4: Dev 3, If 3, Class=HID, Driver=usbhid, 12M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/10p, 480M
|__ Port 9: Dev 5, If 0, Class=>ifc, Driver=rtl8187, 480M
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
soupmagnet said:
From what I've seen, this is usually a problem with the bootloader. How or why, I don't know. That being said, Firekit w/shorting trick seems to be the most successful at resolving this issue.
Click to expand...
Click to collapse
I'm trying to follow this thread http://forum.xda-developers.com/showthread.php?t=1636883 but I don't know how to check if the "short trick" is well performed or not. Is there anything I should notice? At this moment if I make the short trick and plug in the usb connector, nothing seems to be working in the kindle but dmesg is continuously showing errors like previous ones.
Regards,
Are you using Firekit? What command?
"That's a special kind of stupid. The kind that makes me laugh"
I'm still in the step of the process when I make the short trick, plug the usb and the kindle should be detected. Should I try the usbboot commands even when there's no kindle entry in lsusb output?
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
"That's a special kind of stupid. The kind that makes me laugh."
soupmagnet said:
YES absolutely! And hold the power button for 15 seconds to make sure the CPU isn't running before attempting the short.
Click to expand...
Click to collapse
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
soukron said:
The command is ./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img but it keeps stopped in waiting for OMAP44xx device....
I'm going to try a few times more. Thank you!
BTW, what are the next steps? Because this unit is working properly but the USB port to transfer data between computer and device: it boots, it loads stock firmware, and works properly.
Click to expand...
Click to collapse
Are you using a 32bit or 64bit machine? If you have SoupKit installed, option 2 should have installed 32bit libs, but sometimes it fails...mostly due to Ubuntu servers and them trying to make 32bit libs obsolete. If you're running a 64bit machine, try installing 32bit libs again and see if you get any errors.
Code:
sudo apt-get install ia32-libs
Also since you have SoupKit installed, run it and select option 4 to launch the Firekit. There's really no difference in using Firekit and manually entering the commands for Rekindle but it makes things a little easier. Select "usb_install_fff_twrp". The important thing to know about the "usb_fix_parts..." and "usb_install..." commands in Firekit is that they both use "fastboot boot ..." instead of "fastboot flash ..." to install TWRP and FFF. Meaning, if you reboot or shut the device down before actually installing a bootloader, the device won't turn back on and you'll have to do the shorting trick again.
That being said, from the moment you make the short, you only have about 2 seconds to plug the device in and have Linux detect it before the CPU resets and you have to start all over again.
Hold the power button for 10-15 seconds to make sure the CPU is off before attempting the short.
Launch Firekit and select "usb_install_fff_twrp". When the command is run, you will get the "Waiting for OMAP4 device..." prompt. Let it wait.
To do the shorting trick...
Something I have found to be most useful in this situation is to use a sharp pair of tweezers or safety pin to make the short.
Keep the device flat on a desk or table with the USB connection pointed away from you. Use one hand to hold the short, one hand to plug the device in, and use your body against the other end of the device as leverage as you plug it in.
Using a safety pin, stick the sharp end of the safety pin into the short point and press it in a little to keep it from sliding off when you plug the device in. Squeeze the other end of the safety pin or tweezers to make contact with the metal frame and immediately plug the device in while holding the short.
If the tweezers slip or make contact with the frame before you are ready, hold the power button for 10-15 seconds to make sure the device is completely shut down and try again.
You should see something going on in the terminal to let you know it's working...let it finish.
It might take a few attempts to get the timing right but persistence (and practice) is key...don't give up.
Follow these instructions and I'm positive you'll get it working again. Good luck.
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
soukron said:
OK, it's a matter of time and try it.
My computer is 64bit, but I am booting a LiveUSB with Ubuntu 12.10 32bits, so no problem around it.
About the short, one friend of mine solded a thin wire in the point in the board and I only have to connect the other side to the wire to the frame each time, so it also seems to be fine. http://forum.xda-developers.com/attachment.php?attachmentid=1045562&d=1336355873
My main concern: once I manage to make properly the short trick and the process goes forward, what will be the next step? What should I expect of this usb_install_fff_twrp command? Will it fix the hardware detection problem automatically?
Thank you again for all your help, I know you answer a lot this kind of questions and your help is very valuable.
Click to expand...
Click to collapse
When the OMAP4 device is detected, you will see something similar to this in the terminal:
http://forum.xda-developers.com/attachment.php?attachmentid=1262650&d=1345043823
That will temporarily install the bootloader, which is likely the cause of Linux not being able to detect it in the first place. When you see the yellow triangle on your Kindle, you'll know the Firekit worked. But you still have to permanently install the bootloader via fastboot (or TWRP if accessible) before you reboot the device.
Will it work to get Linux to detect it? Most likely, but there's no way to know for sure until you get a new bootloader installed.
On second thought...
I just realized you may not even have to do that in the first place. Lucky you? If your device is working properly as you said, boot into Android and open up the Terminal Emulator. Make sure the u-boot.bin is on your sdcard and enter the following:
Code:
su
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
reboot
See if that works.
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
soukron said:
Yes, working with stock ROM but without root access. If there's any way of rooting it without connecting it to the computer I can do it and then use dd to override the block device.
Click to expand...
Click to collapse
Nope...you need root access to use the 'dd' command.
soupmagnet said:
Nope...you need root access to use the 'dd' command.
Click to expand...
Click to collapse
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
soukron said:
Dude, thank you for your all work but I'm giving up. I'll close it and use it without data cable. I always can use dropbox like applications to transfer data.
Again, thank you, I really appreciate your help.
Click to expand...
Click to collapse
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds..
Sent from my GT-I8350 using Board Express
prahladvarda said:
If y wer on windows, u could have just grabbed a copy of kindle fire utility and had rooted it in merely seconds.
Click to expand...
Click to collapse
Unfortunately, it won't work in this situation.
Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system:
Code:
[49875.145923] usb 1-1.2: new high-speed USB device number 12 using ehci-pci
[49875.240046] usb 1-1.2: New USB device found, idVendor=0bb4, idProduct=0c02
[49875.240057] usb 1-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[49875.240063] usb 1-1.2: Product: MT65xx Android Phone
[49875.240068] usb 1-1.2: Manufacturer: MediaTek
[49875.240072] usb 1-1.2: SerialNumber: ...
but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi
prinz.z said:
Hi there,
has anyone tried to use the MTP file transfer option of the Fairphone with Ubuntu (I'm using 13.04 at the moment). It seems that the phone is recognized by my system. but the device is not shown in Nautilus.
Who knows how to fix that?
Thanks,
Tobi
Click to expand...
Click to collapse
I guess this is more an Ubuntu issue/question than Fairphone's..
You can follow instructions here
Code:
$ sudo mtpfs -o allow_other /media/MTPdevice
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=0bb4 and PID=2008) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:2008 @ bus 2, dev 20
Attempting to connect device
Android device detected, assigning default bug flags
Listing File Information on Device with name: FP1
Nautilus gave me read-only access to content under the custom mount point /media/MTPdevice. dmesg gave me the same log as yours when recognizing the device...
It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)
Okay, I see.. With my former phone (LG O4x, cm-11) it was working flawlessly with mtp on Ubuntu, that's the rason I asked.. With the fairphone, I'm simply using adb for the moment to copy single files..
elchi1234 said:
It doesn't work for me either. But this is an issue that is usual in Ubuntu. Even though it is not an issue in Ubuntu.
* libMTP with a detailed description
* gvfs-mtp
* go-mtpfs
I use either the USB storage or PTP.
(MTP is buggy.)
Click to expand...
Click to collapse
Hey community,
I have big problems with my Fairphone.
It doesn't boot, it happens nothing, totally black screen, no fairphone logo, no system popup...
I turned it off yesterday and since then I've got this issues.
I tried :
-every key combination but nothing happened
-to connect it with my computer and charger but nothing happened, no sign, no LED signal
-removed battery and sim card
I didn't make something unusual, only turned it off, so can anyone please help me?
Thanks in advance
DarkerTimes said:
Hey community,
I have big problems with my Fairphone.
It doesn't boot, it happens nothing, totally black screen, no fairphone logo, no system popup...
I turned it off yesterday and since then I've got this issues.
I tried :
-every key combination but nothing happened
-to connect it with my computer and charger but nothing happened, no sign, no LED signal
-removed battery and sim card
I didn't make something unusual, only turned it off, so can anyone please help me?
Thanks in advance
Click to expand...
Click to collapse
Hi can you try if the recovery mode still works? (e.g turn off the phone and power it on by keeping the power and volume up button pressed).
If that doesn't work try removing the battery and connecting the device to a Linux PC and see if a new device appears (by running dmesg). Do you see a device appear?
_keesj said:
Hi can you try if the recovery mode still works? (e.g turn off the phone and power it on by keeping the power and volume up button pressed).
If that doesn't work try removing the battery and connecting the device to a Linux PC and see if a new device appears (by running dmesg). Do you see a device appear?
Click to expand...
Click to collapse
Hi,
recovery mode doesn't work, the phone is completely dead.
Then I will try your tip with the Linux PC. But first I have to find one^^
I will tell you when i have access to a linux computer and when it gets the device.
Thanks for your help
Gesendet von meinem GT-I9505 mit Tapatalk
DarkerTimes said:
Hi,
recovery mode doesn't work, the phone is completely dead.
Then I will try your tip with the Linux PC. But first I have to find one^^
I will tell you when i have access to a linux computer and when it gets the device.
Thanks for your help
Gesendet von meinem GT-I9505 mit Tapatalk
Click to expand...
Click to collapse
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Vinnl said:
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Click to expand...
Click to collapse
Thank you very much, I will try
Gesendet von meinem GT-I9505 mit Tapatalk
Vinnl said:
You might like to know that you can run many versions of Linux directly from a DVD drive or USB drive. A popular one, and probably the easiest, is: http://www.ubuntu.com/desktop
To "run dmesg", as suggested by @_keesj, do the following:
Start Ubuntu
When the desktop is open, press the Windows key.
Connect your phone.
Type "Terminal".
Press Enter or click the Terminal icon.
Type dmesg, press Enter.
Click to expand...
Click to collapse
View attachment 2925701
I got this message when i connect my Phone to a 32bit Ubuntu VM (VMWare-Player)
Do you know an option for dmesg to make the text shorter? Its such a huge text, larger than the Terminal is able to display.
DarkerTimes said:
View attachment 2925701
I got this message when i connect my Phone to a 32bit Ubuntu VM (VMWare-Player)
Do you know an option for dmesg to make the text shorter? Its such a huge text, larger than the Terminal is able to display.
Click to expand...
Click to collapse
Congratulation for your first GNU/linux use !:highfive:
Yeah dmesg is super huge, it contains record of all that happened on your system since your started it up. (it s a bit more complicated in fact).
I dont know any option to make it shorter, but there are ways
- to only get the bottom of it,
- to save its output in a file
Code:
dmesg > ~/Desktop/dmesg-output.txt
- or to increase the amount of message your terminal can display (right click, profile, profile preferences, scrolling, unlimited).
However here you only need to look at what happened recently (i.e when you connected your phone)
If you connecte your phone and then run the dmesg command the end of the output should show the device detection in the last 50 lines.
I cant acces your attachement, is this only me ?
With a working phone on a non VM ubuntu you should see something like this.
(It may be different on your system, as long as you can read som usb lines, further more containing MT65xx or Mediateck, you are good to go !
....
...
[ 237.437926] usb 2-1.6: new high-speed USB device number 5 using ehci-pci
[ 237.530804] usb 2-1.6: New USB device found, idVendor=0e8d, idProduct=2000
[ 237.530809] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 237.530812] usb 2-1.6: Product: MT65xx Preloader
[ 237.530814] usb 2-1.6: Manufacturer: MediaTek
[ 237.637040] cdc_acm 2-1.6:1.1: ttyACM0: USB ACM device
[ 237.692248] usbcore: registered new interface driver cdc_acm
[ 237.692250] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapter
....
That would means that your OS detected that a new device was connected to USB and that it recognise a mediateck phone.
I hope it's also the case with your phone !
BTW I don't know vmware so well, but sometimes virtual machine prevent virtualised operating system to acces usb port. Maybe someone can confirm that this issue wont appear here ? Or you can check it out by plugging some working usb device and look if some lines get added to dmesg
MoreThanADev said:
I cant acces your attachement, is this only me ?
Click to expand...
Click to collapse
Nope, apparently the attachment wasn't uploaded correctly.
MoreThanADev said:
I cant acces your attachement, is this only me ?
Click to expand...
Click to collapse
hope it works now
View attachment 2927858
here is the output from dmesg:
first run:
[ 5.270990] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 5.271001] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.271010] usb usb1: Product: EHCI Host Controller
[ 5.271019] usb usb1: Manufacturer: Linux 3.13.0-35-generic ehci_hcd
[ 5.271027] usb usb1: SerialNumber: 0000:02:03.0
[ 5.272005] hub 1-0:1.0: USB hub found
[ 5.272231] hub 1-0:1.0: 6 ports detected
[ 5.273333] ehci-platform: EHCI generic platform driver
[ 5.273386] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 5.273404] ohci-pci: OHCI PCI platform driver
[ 5.273465] ohci-platform: OHCI generic platform driver
[ 5.273494] uhci_hcd: USB Universal Host Controller Interface driver
[ 5.273813] uhci_hcd 0000:02:00.0: UHCI Host Controller
[ 5.273822] uhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 5.274010] uhci_hcd 0000:02:00.0: irq 18, io base 0x000020c0
[ 5.274349] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 5.274351] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 5.274352] usb usb2: Product: UHCI Host Controller
[ 5.274353] usb usb2: Manufacturer: Linux 3.13.0-35-generic uhci_hcd
[ 5.274355] usb usb2: SerialNumber: 0000:02:00.0
[ 5.274492] hub 2-0:1.0: USB hub found
[ 5.274546] hub 2-0:1.0: 2 ports detected
second run
[ 201.982468] usb 2-2.1: new full-speed USB device number 4 using uhci_hcd
[ 202.310781] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 202.310840] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 202.448421] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
[ 202.456529] usbcore: registered new interface driver cdc_acm
[ 202.456544] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 202.471104] usbcore: registered new interface driver usbserial
[ 202.471210] usbcore: registered new interface driver usbserial_generic
[ 202.471344] usbserial: USB Serial support registered for generic
[ 202.481866] usbcore: registered new interface driver option
[ 202.482531] usbserial: USB Serial support registered for GSM modem (1-port)
[ 241.102849] usb 2-2.1: USB disconnect, device number 4
[ 266.180249] usb 2-2.1: new full-speed USB device number 5 using uhci_hcd
[ 266.581692] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 266.581747] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 266.660505] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
what to do now?
btw, every 50-60 seconds i got the pluggin and unplugg sound from my windows system
Edit:
i have a second Fairphone now and tried to turn on the first one with tha accu of the second one and the second phone with the accu of the first one. both doesn´t start. only the second one with the second accu is working.
DarkerTimes said:
second run
[ 266.180249] usb 2-2.1: new full-speed USB device number 5 using uhci_hcd
[ 266.581692] usb 2-2.1: New USB device found, idVendor=0e8d, idProduct=0003
[ 266.581747] usb 2-2.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 266.660505] cdc_acm 2-2.1:1.0: ttyACM0: USB ACM device
what to do now?
Click to expand...
Click to collapse
These lines are your phone so there is still some life in it. But it doesnt even start the preloader which appears after these lines if I plug in my phone (powered off).
Maybe this low level mode is enough for the SP flash tool and you can try the unbrick guide: http://forum.xda-developers.com/wik...o_restore_Fairphone_if_you_totally_bricked_it
Make sure to chose the correct image (FUSE for upgraded partition layout, 1G13G for the old layout)
You might want to uncheck "userdata", this might give you a chance of keeping your apps and settings.
Other than that you could contact Fairphone support.
My Solution
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same Problem while trying install CM11.
What works for me @ a Win7 PC:
- remove the Battery (Force shutdown the phone)
- plugin the Battery
- Turn on the Phone while pressing the power-button and the volume-UP button. (release power button after 6 Secs)
- Now you're in the recovery menu
- If you have CWM (like me) goto --> install zip --> install zip from sideload
If you have another bootloader you'll find the "install zip from sideload" somewhere...
- Download the Original zip-file from Fairphone (Fairphone Website --> SUPPORT --> SOFTWARE --> UPDATES --> SOFTWARE --> DOWNLOADS)
- Download / install the MTK6589 ADB Driver (http://forum.xda-developers.com/showthread.php?t=2247537)
- now download a tool which contains the adb.exe (I tooked the "MTK droid root & tools" http://forum.xda-developers.com/showthread.php?t=2160490)
- Start the MTK tool as Admin and press "ADB-Terminal"
- in the Terminal write: "adb push NAMEOFTHEZIPFILE.zip"
- now your phone should start transfer, reboot and install the original OS
Hope this works for you too...
* More about ADB and Sideload (http://forum.xda-developers.com/showthread.php?t=2318497
Regards
_tmp said:
These lines are your phone so there is still some life in it. But it doesnt even start the preloader which appears after these lines if I plug in my phone (powered off).
Maybe this low level mode is enough for the SP flash tool and you can try the unbrick guide: http://forum.xda-developers.com/wik...o_restore_Fairphone_if_you_totally_bricked_it
Make sure to chose the correct image (FUSE for upgraded partition layout, 1G13G for the old layout)
You might want to uncheck "userdata", this might give you a chance of keeping your apps and settings.
Other than that you could contact Fairphone support.
Click to expand...
Click to collapse
shooter_92 said:
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
I had the same Problem while trying install CM11.
What works for me @ a Win7 PC:
- remove the Battery (Force shutdown the phone)
- plugin the Battery
- Turn on the Phone while pressing the power-button and the volume-UP button. (release power button after 6 Secs)
- Now you're in the recovery menu
- If you have CWM (like me) goto --> install zip --> install zip from sideload
If you have another bootloader you'll find the "install zip from sideload" somewhere...
- Download the Original zip-file from Fairphone (Fairphone Website --> SUPPORT --> SOFTWARE --> UPDATES --> SOFTWARE --> DOWNLOADS)
- Download / install the MTK6589 ADB Driver (http://forum.xda-developers.com/showthread.php?t=2247537)
- now download a tool which contains the adb.exe (I tooked the "MTK droid root & tools" http://forum.xda-developers.com/showthread.php?t=2160490)
- Start the MTK tool as Admin and press "ADB-Terminal"
- in the Terminal write: "adb push NAMEOFTHEZIPFILE.zip"
- now your phone should start transfer, reboot and install the original OS
Hope this works for you too...
* More about ADB and Sideload (http://forum.xda-developers.com/showthread.php?t=2318497
Regards
Click to expand...
Click to collapse
Hey guys,
sry that I've been away for this long period of time.
The problem is that i can't enter recovery mode, so the only way to try it would be with the SP flash tool but I decided to contact the fairphone support and sent it back for repairing it.
But thanks all for your help!!
Edit: I got my phone back now. The issues were caused by damaged mainboard, they change it completely.
Sent from my Galaxy S4 using Tapatalk
I have the same problem
Hey,
I have the same problem, did it fall under warranty or did you have to pay for the repair?
hewitje240 said:
Hey,
I have the same problem, did it fall under warranty or did you have to pay for the repair?
Click to expand...
Click to collapse
Hi, did fall under warranty
Sent from my GT-I9505 using XDA Free mobile app
I've seen reports of the VK815 being rooted and would like to root mine. Is there someone who has a VK815 and has rooted it who is willing to share how they accomplished it?
I have 'adb' available and working, the developer mode enabled, and can talk to the phone. Trying to attain superuser from the 'adb shell' doesn't work because the 'su binary' is missing. 'adb reboot recovery' gives the ''dead android' and the 'power/volume -' key combination results in a normal boot.
Thanks,
Jim
I rooted my vk815 with one click root from the g3 section. Not sure yet how to post links I'm new to xda...
---------- Post added at 12:56 AM ---------- Previous post was at 12:49 AM ----------
http://forum.xda-developers.com/showthread.php?t=3056951
That looks like a solution for those who have Windows PC's connected to their tablets. I'm a linux only and should have put that in my original post.
I guess I could look at the script and see if there's any clues inside it.
Thanks,
Jim
There is a python script for using the send command with the files. On my phone and at work, so difficult for me to look up, but I'm sure googling send command LG python will turn it up (probably under g3 or g4 forums...)
danaff37 said:
There is a python script for using the send command with the files. On my phone and at work, so difficult for me to look up, but I'm sure googling send command LG python will turn it up (probably under g3 or g4 forums...)
Click to expand...
Click to collapse
I've seen it and given it a try. The writer and everyone else in the thread look like they aren't working with a VK815. The VK815 doesn't trigger loading of the 'serial' module. I don't have one on my system so that looks like a problem. I keep getting this error message:
[email protected]:/root# qcdlcomm.py /dev/ttyUSB0
Traceback (most recent call last):
File "/home/jim/Desktop/qcdlcomm.py", line 13, in <module>
import serial
ImportError: No module named serial
For anyone who's interested; the python script is here about a quarter of the way down the page. hxxp://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772/page46 (Change the x's to t's)
Jim
Seems like the kernel can't figure out what chip is handling the serial I/O for the tablet so it only loads 'usbserial_generic'. That module can't change any of the comm parameters. The error messages now want a more specific module loaded before running the python script.
[1655862.790132] usb 1-9: new high-speed USB device number 9 using ehci-pci
[1655862.905356] usb 1-9: New USB device found, idVendor=1004, idProduct=6293
[1655862.905359] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1655862.905361] usb 1-9: Product: LGE Android Phone
[1655862.905363] usb 1-9: Manufacturer: LG Electronics Inc.
[1655862.905365] usb 1-9: SerialNumber: VK815275a2846
[1655862.905753] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655862.905755] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655862.905757] usbserial_generic 1-9:1.0: generic converter detected
[1655862.905816] usb 1-9: generic converter now attached to ttyUSB0
[1655862.946215] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
[1655862.946343] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[1655862.946356] usbserial_generic 1-9:1.0: device disconnected
[1655863.049404] usb 1-9: reset high-speed USB device number 9 using ehci-pci
[1655863.164195] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655863.164201] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655863.164203] usbserial_generic 1-9:1.0: generic converter detected
[1655863.164288] usb 1-9: generic converter now attached to ttyUSB0
[1655863.164329] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
Jim
jowski said:
Seems like the kernel can't figure out what chip is handling the serial I/O for the tablet so it only loads 'usbserial_generic'. That module can't change any of the comm parameters. The error messages now want a more specific module loaded before running the python script.
[1655862.790132] usb 1-9: new high-speed USB device number 9 using ehci-pci
[1655862.905356] usb 1-9: New USB device found, idVendor=1004, idProduct=6293
[1655862.905359] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1655862.905361] usb 1-9: Product: LGE Android Phone
[1655862.905363] usb 1-9: Manufacturer: LG Electronics Inc.
[1655862.905365] usb 1-9: SerialNumber: VK815275a2846
[1655862.905753] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655862.905755] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655862.905757] usbserial_generic 1-9:1.0: generic converter detected
[1655862.905816] usb 1-9: generic converter now attached to ttyUSB0
[1655862.946215] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
[1655862.946343] generic ttyUSB0: generic converter now disconnected from ttyUSB0
[1655862.946356] usbserial_generic 1-9:1.0: device disconnected
[1655863.049404] usb 1-9: reset high-speed USB device number 9 using ehci-pci
[1655863.164195] usbserial_generic 1-9:1.0: The "generic" usb-serial driver is only for testing and one-off prototypes.
[1655863.164201] usbserial_generic 1-9:1.0: Tell [email protected] to add your device to a proper driver.
[1655863.164203] usbserial_generic 1-9:1.0: generic converter detected
[1655863.164288] usb 1-9: generic converter now attached to ttyUSB0
[1655863.164329] usb 1-9: usbfs: process 29489 (pool) did not claim interface 0 before use
Jim
Click to expand...
Click to collapse
I doubt there are drivers for linux for a g4 in Linux, and I know people used the script for that. You are doing this in download mode? I can't remember since it's been a while for me setting it up, but does the Android sdk install the generic android USB drivers in Linux?
danaff37 said:
I doubt there are drivers for linux for a g4 in Linux, and I know people used the script for that. You are doing this in download mode? I can't remember since it's been a while for me setting it up, but does the Android sdk install the generic android USB drivers in Linux?
Click to expand...
Click to collapse
The kernel modules handle what drivers would do in Windows.
I'm in the download mode and if I boot normally instead of into download; I can talk to the tablet with adb. I'm thinking that maybe if I comment out the serial port settings code, the script might work. I'll try that later.
Jim
jowski said:
The kernel modules handle what drivers would do in Windows.
I'm in the download mode and if I boot normally instead of into download; I can talk to the tablet with adb. I'm thinking that maybe if I comment out the serial port settings code, the script might work. I'll try that later.
Jim
Click to expand...
Click to collapse
I just know in the past for fast boot mode on other devices, I had to run the Android sdk tools and add some udev rules. But I can't remember if the sdk tools was simply for executables, or for modules/drivers
danaff37 said:
I just know in the past for fast boot mode on other devices, I had to run the Android sdk tools and add some udev rules. But I can't remember if the sdk tools was simply for executables, or for modules/drivers
Click to expand...
Click to collapse
When I can talk to the tablet; adb works but fastboot doesn't. 'adb reboot recovery' gives the dead android. This is turning into a real adventure.
There has to be something after 'modprobe usbserial' to load a specific module on the PC so it can talk to the VK815. Would the Windows ddl's give a clue?
Jim
Well, I'll be go to ....
Commenting the block of code that sets the serial port settings worked! I went into the download mode with the key press (power off, volume +, connect the usb cable, wait for Firmware Update screen, release volume +) and ran the script and was talking to the tablet. Looks like the next step is to load the goodies first and then try the manual commands to install root.
Whatcha think gang? I'm thinking we're almost there and how cool is that!!!
Jim
edit: [email protected]:/# ./qcdlcomm.py /dev/ttyUSB0
Traceback (most recent call last):
File "qcdlcomm.py", line 47, in <module>
port=sys.argv[-1]
File "/usr/lib64/python2.7/site-packages/serial/serialutil.py", line 282, in __init__
self.open()
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 296, in open
self._reconfigurePort()
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 325, in _reconfigurePort
raise SerialException("Could not configure port: %s" % msg)
serial.serialutil.SerialException: Could not configure port: (25, 'Inappropriate ioctl for device')
Any ideas??? I changed the 'ser' block to
ser = serial.Serial(
port=sys.argv[-1]
)
I'm back to thinking it's a module that needs to be loaded.
Previous post errors were due to 'cdc_acm' being reloaded and me not checking that before running the script. Fixed that and reloaded usbserial. Now the errors are:
[email protected]:# qcdlcomm.py /dev/ttyUSB0
Special commands: ENTER, LEAVE, exit
# ENTER
Traceback (most recent call last):
File "/home/jim/Desktop/qcdlcomm.py", line 100, in <module>
cmd(input)
File "/home/jim/Desktop/qcdlcomm.py", line 87, in cmd
rawcmd(commands[input])
File "/home/jim/Desktop/qcdlcomm.py", line 63, in rawcmd
ser.write(input)
File "/usr/lib64/python2.7/site-packages/serial/serialposix.py", line 490, in write
if not self._isOpen: raise portNotOpenError
serial.serialutil.SerialException: Attempting to use a port that is not open
So much for talking to the tablet.
Jim
I tried usb_modeswitch and got something that may be encouraging. I'll post the command and output so someone who knows a bit about usb_modeswitch can shed some light.
[email protected]:/home/jim/Desktop# usb_modeswitch -p 0x6293 -v 0x1004 -M a1
Look for default devices ...
product ID matched
Found devices in default mode (1)
Access device 067 on bus 001
Get the current device configuration ...
OK, got current device configuration (1)
Use interface number 0
Use endpoints 0x01 (out) and 0x81 (in)
Not a storage device, skip SCSI inquiry
USB description data (for identification)
-------------------------
Manufacturer: LG Electronics Inc.
Product: LGE Android Phone
Serial No.: VK815275a2846
-------------------------
Looking for active driver ...
OK, driver detached
Set up interface 0
Use endpoint 0x01 for message sending ...
Trying to send message 1 to endpoint 0x01 ...
Sending the message returned error -1. Try to continue
Reset response endpoint 0x81
Reset message endpoint 0x01
Could not reset endpoint (probably harmless): -99
-> Run lsusb to note any changes. Bye!
There are other messages that can be sent as part of the command. I'm wondering if this is how we can gain access to the device using linux.
Jim
Tried the windows method from an XP machine. Keep getting a "Device cannot start. (Code 10)" error. Tried uninstalling and reinstalling the LG drivers along with the VZW drivers. Also tried using only the VZW drivers. Same results. The device manager says the DIAG port is COM16 but Send_Command.exe can't open port 16.
Anyone had success rooting from XP or do I need to try Windows 7?
Jim
jowski said:
Tried the windows method from an XP machine. Keep getting a "Device cannot start. (Code 10)" error. Tried uninstalling and reinstalling the LG drivers along with the VZW drivers. Also tried using only the VZW drivers. Same results. The device manager says the DIAG port is COM16 but Send_Command.exe can't open port 16.
Anyone had success rooting from XP or do I need to try Windows 7?
Jim
Click to expand...
Click to collapse
I tried XP but the device drivers wouldn't install. 7 worked great for me tho. But I'm not real good with Windows possibly some others would know better??
So my tablet today prompted me to update to 11A. But since it's rooted, so it didn't go thru. Does anyone know what we can do with that info? Like to keep root and update?
I gave up on finding a linux solution and did it with WinDoze 8. A root canal has to be less painful. At least it's rooted now.
I'm holding off on the update until after I get a few apps loaded that require root access. I wish there was a way to turn off the updates and nags.
Jim
I think the linux answer to talking to the VK815 involves the BCM2079x on the tablet. Could that mean the linux box trying to load a serial driver would need to do something like 'modprobe bcm2079x'? If so, where to we find the config for it in the kernel .config?
Jim
I know this is an old thread, but maybe someone can send me in the right direction. My non-rooted VK815 updated to 6.0 and ruined the battery life. So, I'd like to root it. I can only find threads on rooting the previous version - has anyone rooted the 6.0 version?