Develop Bugs

Defy bricked (completely?)

hi, yesterday i just bought a bricked motorola defy, since i read that was almost imposible to brick one...i thought it'd be easy to unbrick
ill explain:
black screen, no recovery, no bootloader mode....
theorically it had android 2.2
when i conect it to the pc it connects and instantly disconects (someone posted the same and he said that randomly it'd connect succesfully)
battery shows 4v (so itd flash)
white led shows up when i connect the usb without battery and turns off when i put the battery
rsd cant recognise it (windows neither)
also tried a linux script, but it neither recognises it...
i thought id be an uncharged battery + wrong sbf
but i cant get it to connect...
id apreciate fast responses

May be your battery will b low....Try to charge it and than try...
Sent from my MB525 using XDA App

i already charged it with the mvgyber fix... i guess the red cable goes to the + (top right) and the black to the - (top left...)
if so, i tried.

also tried a linux script, but it neither recognises it...
Click to expand...
Click to collapse
What script did you use?
Is it sbf_flash? Please give us more details! Like the name of the script/binary file you used, the parameters passed at runtime, the error you received after running the script/binary tool.
Did you tried to see if any information is added in the linux log files while connecting the phone to your computer using a "microUSB to USB" cable?

i tried the sbf_flash one, (there are others?)
it says, waiting for phone... or something like that...(i dont have linux here)
if the battery shows 4v it isnt a battery issue am i right?

Not as far as I know, but sbf_flash is a binary tool and since you said that you have tried a linux script I thought that you are using something else.
Basically, when a device is connected to a computer running linux, via USB, you can find informations about the attached device in some log files (/var/log/messages or /var/log/udev).
If/when you will have a linux around, let me know and I'll try to help you (if I can).

tomorrow ill have linux access, ill post logs...
btw... has nobody seen a solution for the connecting-disconeccting issue? ive seen few posts with it, but anyone posts a solution, just someone saying is luck...
i thought electronics had no true randomness,

im getting this at /var/log/messages
May 12 08:11:01 ubuntu kernel: [ 1192.928137] usb 1-6: new high speed USB device using ehci_hcd and address 9
May 12 08:11:01 ubuntu kernel: [ 1193.062719] usb 1-6: configuration #1 chosen from 1 choice
May 12 08:11:04 ubuntu kernel: [ 1196.056253] usb 1-6: USB disconnect, address 9
May 12 08:11:17 ubuntu kernel: [ 1209.308069] usb 1-6: new high speed USB device using ehci_hcd and address 10
May 12 08:11:17 ubuntu kernel: [ 1209.442678] usb 1-6: configuration #1 chosen from 1 choice
May 12 08:11:20 ubuntu kernel: [ 1212.436317] usb 1-6: USB disconnect, address 10
at udev, i cant see anything related to the phone...

Those messages appear in the log file exactly when the phone is connected to the computer?
In my /var/log/messages other information appears when the phone is plugged in (like device manufacturer, device serial number etc) but all my log messages go into /var/log/messages (I'm using Gentoo at home), but in Ubuntu it seems that most of these messages go to /var/log/udev.
What version of sbf_flash did you use? The last version is 1.23 (mbm).
A few days ago I came across an article describing the udev configuration in order to be able to connect to the phone using adb. I don't know if this will help you since USB debugging must be turned on and for that you need a running android device. I'll send you the link via PM since I do not have enough posts in this forum to be allowed to write url's in the post.

ill post the last lines of the udev log, at night (3h actually)
but somehow i dont know why, but the behaviour is the same, gets conection, looses conection...
maybe is a hardware issue...

Here's what's added in my /var/log/message when I connect my (working defy) via USB: (USB debugging is not turned on and the USB connection is set to charge only)
May 12 22:33:07 tuxtm kernel: [ 2506.674023] usb 1-4: new high speed USB device using ehci_hcd and address 3
May 12 22:33:07 tuxtm kernel: [ 2506.788858] usb 1-4: New USB device found, idVendor=22b8, idProduct=41d9
May 12 22:33:07 tuxtm kernel: [ 2506.788863] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 12 22:33:07 tuxtm kernel: [ 2506.788866] usb 1-4: Product: MB525
May 12 22:33:07 tuxtm kernel: [ 2506.788869] usb 1-4: Manufacturer: Motorola
May 12 22:33:07 tuxtm kernel: [ 2506.788871] usb 1-4: SerialNumber: <serial_number_here>
May 12 22:33:07 tuxtm kernel: [ 2506.789567] scsi2 : usb-storage 1-4:1.0
May 12 22:33:08 tuxtm kernel: [ 2507.790153] scsi 2:0:0:0: Direct-Access Motorola MB525 0001 PQ: 0 ANSI: 2
May 12 22:33:08 tuxtm kernel: [ 2507.790684] sd 2:0:0:0: Attached scsi generic sg1 type 0
May 12 22:33:08 tuxtm kernel: [ 2507.792748] sd 2:0:0:0: [sdb] Attached SCSI removable disk

with lsusb i get nothing by connecting, if i put the battery in, the next 4sec i get a texas instruments device, then goes off
i guess is hw issue, im trading that brick for a working samsung wave device.
tyvm for the help, but i guess it was a fully brick.

ANSWER!!!
Flash sbf file using rsd lite............IT WORKS........I DID IT...........I THINK U R A NEWBIE

im a newbie, but, rsd cant recognise it, when i plug the phone without battery:
-white led ON
-put the battery (here i can press whatever button, no change)
-white led off
-pc detects new hw (motorola flashing device)
-3seconds
-pc looses conection with motorola flashing device
(even pressing show device at light speed once conected, i doesnt detect anything)
and since on linux i get same result (connect - disconect), it means isnt a pc issue (also tried on another pc)

got an answer for you too
pjgowtham said:
............IT WORKS........I DID IT...........I THINK U R A NEWBIE
Click to expand...
Click to collapse
It's the little "arrow down" key on the left side of your keyboard. Just above the "CTRL" and "arrow up" Key.

hallo.. i'm newbie. i got some proble in my defy
I made a mistake in ROM CM7: I "install the 2nd init". and the results stuck on the boot logo .. : (
I finally went into the boot loader, then flash again use 3.4.2_177 SBF-005_NORDIC (do not wipe the data) .. remain stuck at the boot logo. and I try to use flash SBF-Stock.UKTmobile 3.4.3_11 (not wipe the data) and the results .... still stuck>> it's just an animated logo appears only.
AND THEN ---------------------------------
for this case:
I want to get into stock recovery:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
please help me
thanks before

omneon said:
1. defy turn off, turn the power button + volume down (hold a while)
2. logo appears>> android +! (the menu does not appear anything)
3. and I do not know anymore what should I do: (
Click to expand...
Click to collapse
you did tap the lower right corner of your screen when android appeared, didn't you?

If right corner doesn't do the trick, try instead pushing both volume buttons at the same moment. Worked for me
Sent from my MB525 using XDA App

[Q] Kindle 1st gen working BUT "Unknown Device" in Device Manager

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.

[Q] Data transfer via MTP on ubuntu

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

VK815 rooting help

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?

Recovering files from dead(?) HTC One X

I'm trying to salvage some important files from a dead HTC One X (stock everything) - from what I've been told, it was in use and suddenly turned off. After attempts to charge the phone etc. to no avail (monitor does not turn on, no LEDs turn on at all) it was sent for repair with the instructions to not proceed if they could not salvage the files. The repair shop opened the phone, molested some plastic parts and sent it back in two parts, stating that they could not proceed further without loosing the data on the phone. I have no idea what they tried, so I'm hoping they didn't try very much before giving up.
So - I put the thing back together and tried to turn it on and charge it. The display and LEDs show no signs of life, even when charging, holding down power button etc. When I attach the phone to my (Linux) PC, I get the following in dmesg:
Code:
[142745.586102] usb 3-2: new high-speed USB device number 99 using xhci_hcd
[142745.603030] usb 3-2: New USB device found, idVendor=0955, idProduct=7130
[142745.603038] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[142745.603042] usb 3-2: Product: APX
[142745.603045] usb 3-2: Manufacturer: NVIDIA Corp.
which is the only sign of life I've seen so far (why NVIDIA vendor ID and not HTC?). When holding down the power button for ~15 seconds, there's a "USB disconnect" and it re-appears.
Sometimes the phone seems to enter a slightly different state, giving me some sort of connect-timeout-reconnect loop four times:
Code:
[143124.943256] usb 3-2: new high-speed USB device number 101 using xhci_hcd
[143129.944609] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[143130.148758] usb 3-2: Device not responding to set address.
[143130.352699] usb 3-2: device not accepting address 101, error -71
I was hoping that it was just a busted display, and booting a recovery image would let me grab the files via adb - but it does not show up when doing "fastboot devices". I've tried different blind combinations of holding the power button and volume down, but nothing seems to happen (not sure if I'm doing something wrong though, since nothing appears on screen).
Maybe someone here on xda has an idea on how I could get into the device? Recovering the phone does not matter, but getting the files is very important to the owner.

Tausen said:
I'm trying to salvage some important files from a dead HTC One X (stock everything) - from what I've been told, it was in use and suddenly turned off. After attempts to charge the phone etc. to no avail (monitor does not turn on, no LEDs turn on at all) it was sent for repair with the instructions to not proceed if they could not salvage the files. The repair shop opened the phone, molested some plastic parts and sent it back in two parts, stating that they could not proceed further without loosing the data on the phone. I have no idea what they tried, so I'm hoping they didn't try very much before giving up.
So - I put the thing back together and tried to turn it on and charge it. The display and LEDs show no signs of life, even when charging, holding down power button etc. When I attach the phone to my (Linux) PC, I get the following in dmesg:
Code:
[142745.586102] usb 3-2: new high-speed USB device number 99 using xhci_hcd
[142745.603030] usb 3-2: New USB device found, idVendor=0955, idProduct=7130
[142745.603038] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[142745.603042] usb 3-2: Product: APX
[142745.603045] usb 3-2: Manufacturer: NVIDIA Corp.
which is the only sign of life I've seen so far (why NVIDIA vendor ID and not HTC?). When holding down the power button for ~15 seconds, there's a "USB disconnect" and it re-appears.
Sometimes the phone seems to enter a slightly different state, giving me some sort of connect-timeout-reconnect loop four times:
Code:
[143124.943256] usb 3-2: new high-speed USB device number 101 using xhci_hcd
[143129.944609] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[143130.148758] usb 3-2: Device not responding to set address.
[143130.352699] usb 3-2: device not accepting address 101, error -71
I was hoping that it was just a busted display, and booting a recovery image would let me grab the files via adb - but it does not show up when doing "fastboot devices". I've tried different blind combinations of holding the power button and volume down, but nothing seems to happen (not sure if I'm doing something wrong though, since nothing appears on screen).
Maybe someone here on xda has an idea on how I could get into the device? Recovering the phone does not matter, but getting the files is very important to the owner.
Click to expand...
Click to collapse
For me the battery is dead. Try changing battery... Has the repair center remounted all connectors like the screen/battery connector?