Related
I am an Ubuntu Linux user. I am now using ubuntu 12.10.
Just upgraded my HOX to JellyBean via OTA.
When I connect HOX to computer via USB cable,
'Mount USB Mass Storea' option is not appeared and I can't find it in system settings.
After google search, I know that USB Mass Storge mode is replaced by MTP/PTP mode.
I found a post and followed it to mount my HOX.
But aways fail.
I can't post URL here.
HTML:
sudo mtp-detect
libmtp version: 1.1.5
Listing raw device(s)
Device 0 (VID=0bb4 and PID=0df6) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:0df6 @ bus 1, dev 57
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.
Does anyone successfully mount HOX external store under ubuntu linux after update to JellyBean?
You should ask ubuntu to make drivers for hox in MTP mode, or mount the usb in a custom recovery
I didn't use linux for a long time,
trulyliu said:
I am an Ubuntu Linux user. I am now using ubuntu 12.10.
Just upgraded my HOX to JellyBean via OTA.
When I connect HOX to computer via USB cable,
'Mount USB Mass Storea' option is not appeared and I can't find it in system settings.
After google search, I know that USB Mass Storge mode is replaced by MTP/PTP mode.
I found a post and followed it to mount my HOX.
But aways fail.
I can't post URL here.
HTML:
sudo mtp-detect
libmtp version: 1.1.5
Listing raw device(s)
Device 0 (VID=0bb4 and PID=0df6) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:0df6 @ bus 1, dev 57
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.
Does anyone successfully mount HOX external store under ubuntu linux after update to JellyBean?
Click to expand...
Click to collapse
I have the same probem, i find this 2 posts, i didn't try it yet....
http://sourceforge.net/p/libmtp/bugs/663/
In the last post the people of libmtp add HOX to the mtp devices and the put it in the GIT, so you will have to compile it from the source
https://gist.github.com/3884439
in this one, they offer a solution to connect it, albeit, probably you have to compile it anyway.
If you make it, post it here, i will do the same...
in this one, they offer a solution to connect it, albeit, probably you have to compile it anyway.
If you make it, post it here, i will do the same...[/QUOTE]
I compiled libmtp and go-mtpfs.
Still doesn't work.
Hi mates,
Kubuntu 12.10 here. Attaching HOX (JB 3.14.401.27) to my PC works out of the box.
It appears (and gets automatically mounted) as "portable media player", and I can open it with any file explorer (i use dolphin).
Strange that you can't make it work on ubuntu. Finally, I don't know whether it is relevant or not, but I have a simple udev rule for allowing HTC devices (0bb4, it was necessary for using adb).
trulyliu said:
I am an Ubuntu Linux user. I am now using ubuntu 12.10.
Just upgraded my HOX to JellyBean via OTA.
When I connect HOX to computer via USB cable,
'Mount USB Mass Storea' option is not appeared and I can't find it in system settings.
After google search, I know that USB Mass Storge mode is replaced by MTP/PTP mode.
I found a post and followed it to mount my HOX.
But aways fail.
I can't post URL here.
HTML:
sudo mtp-detect
libmtp version: 1.1.5
Listing raw device(s)
Device 0 (VID=0bb4 and PID=0df6) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
0bb4:0df6 @ bus 1, dev 57
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.
Does anyone successfully mount HOX external store under ubuntu linux after update to JellyBean?
Click to expand...
Click to collapse
If you're on custom recovery
Have you tried:
1. Boot into recovery
2. Connect USB
3. Mount Storage under mount section
Work'd for me and it saved my phone from brick.
poisonwell said:
If you're on custom recovery
Have you tried:
1. Boot into recovery
2. Connect USB
3. Mount Storage under mount section
Work'd for me and it saved my phone from brick.
Click to expand...
Click to collapse
This also did work for me.
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?
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
fdelago said:
Hi everybody.
I try to install Cyanogenmod on my LG G3 (model D855P bought on Brazil), but the install stopped after some minutes before finish.
I received the LG loop logo. After read some topic's about this error, I try to write a original firmware (.TOT D855AT European). The install runing with any problems. But now, my smartphone is show in LGUP with "Unknow" in the model, but show me the connection port is COM3.
I used the Boarddiag to verify the phone and any error founded. I try to re-write the SDRAM with files extract from LGD855PAT-01-V10a-370-02-JUN-10-2014-16G-32G+3, but not work. I install, but the problem continue the same.
I try the process when you change the COMxx port to COM41 and using a specified .dll, but the process stop in the first steps of validation.
Now, when I turn-on my phone, after some minutes I receive the message: Kernel Crash Handler. If I press Power+Down, the fastboot interface is started, but when I try to access using ADB (in Linux or Windows 10), the device is not listed with command ADB DEVICES. In the Windows 10, my device is recognize in "Manager Devices" with the name "Kedacom USB Device > Android Bootloader Interface".
I try to create the file on .android folder, but not work.
When run the command DMESG in the Linux, my device have this information:
usb 1-5: new high-speed USB device number 3 using ehci-pci
usb 1-5: New USB device found, idVendor=18d1, idProduct=d00d
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-5: Product: Android
usb 1-5: Manufacturer: Google
Anyone have some idea to help me about this problem???
Click to expand...
Click to collapse
Any luck unbricking your device?
I have the same problem here
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
danhawker said:
Hi,
Have a Shield 2017 which I'd like to flash to a normal LInux userland rather than Android, however I seem to be failing at the first hurdle, namely ADB and Fastboot.
I have been able to ADB over Ethernet, however when I use ADB and Fastboot over USB I never seem to be able to discover the attached device. I've tried using both macOS and Linux, and have tried a number of USB A-A cables.
I've followed both the nVidia flashing instructions, plus a few from this forum, eg enabling the developer mode, USB debugging, etc. to no avail. These are the steps I've taken.
- Enable Development mode on SATV (click build a number of times)
- Enable ADB over USB on SATV (Settings/Development Options/Toggle USB Debugging)
- Download and install Android SDK tools from the Android SDK pages.
- Plugin USB A-A into the end USB port and my Macbook/Linux box
- Run `adb devices`
At this point I don't get any output.
Code:
[[email protected] ~]# adb devices
List of devices attached
If I connect via Ethernet...
Code:
[[email protected] ~]# adb connect 10.200.1.111
connected to 10.200.1.111:5555
[[email protected] ~]# adb devices
List of devices attached
10.200.1.111:5555 device
Although I can at this point reboot the Shield in fastboot/bootloader mode, with a quick `adb reboot bootloader`, I can't then fastboot, as again fastboot cannot see the device.
Code:
[[email protected] ~]# fastboot devices
On neither my mac nor Linux box, the USB device doesn't seem to be recognised (with lsusb or ioreg), although have tried a couple of new USB 3.0 A-A cables. Wondering if the USB debugging isn't enabling fully for some reason?
Any ideas??
Thanks
Dan
Click to expand...
Click to collapse
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
melendi said:
Have you solved your issue? I do not have PC but want to use other android device with Magisk and osm0sis ADB & Fastboot script and I have the same problem...
Click to expand...
Click to collapse
Do you have a nvidia gamepad?
gengt said:
Do you have a nvidia gamepad?
Click to expand...
Click to collapse
Yes and I had already been in fastboot but on another android device with osm0sis ADB & Fastboot script there are no fastboot devices listed.