Hard bricked G3 - G3 Q&A, Help & Troubleshooting
So I recently got a bricked G3 from a friend (t-mobile variant) and I'm coming to terms with that it's definitely hard bricked. No combination of buttons does anything on the phones screen. I can't get into recovery or download / update mode to do the suggest stock procedures. Has anyone dealt or beaten this? It's definitely not under warranty so that's out of the question.
Despite having installed the drivers, my computer recognizes the phone as "QHSUSB_BULK" under device manager. But for some reason I see a glimmer of hope in that my computer recognizes anything at all.
Absolutely any suggestions welcome and appreciated. Thanks!
EDIT: To anyone reading trying to find a solution to a similar problem, just call up LG. The phone has a one year warranty, and being under a year old, how you broke it doesn't really matter (unless its physical damage haha). They have you send it to Texas to either repair or replace it.
UPDATE 10/14 My repaired should be arriving via fedex today!
That QHS for LG phones in the past has meant a brick.
The only way to fix it was JTAG. I don't know if anybody is doing it yet for the G3.
engine95 said:
That QHS for LG phones in the past has meant a brick.
The only way to fix it was JTAG. I don't know if anybody is doing it yet for the G3.
Click to expand...
Click to collapse
Damn I've never seen anything go that far south for anything I own. Should I even bother with a usb jig? That saved one of my old galaxy phones a couple years back
Could the phone be taken apart and rebuilt? Curious myself too. I have heard of this but never seen it before.
f2bacon said:
Damn I've never seen anything go that far south for anything I own. Should I even bother with a usb jig? That saved one of my old galaxy phones a couple years back
Click to expand...
Click to collapse
You said the phone was tmo and it's bootloader is unlocked. My guess it they flashed something they shouldn't have.
I don't know what a USB jig is but I'd say go for it cause it can't hurt it now, I wouldn't think.
hack14u said:
Could the phone be taken apart and rebuilt? Curious myself too. I have heard of this but never seen it before.
Click to expand...
Click to collapse
My limited knowledge of JTAG is they somewhat disassemble it and hook it to a computer and somehow fix it. The going rates I knew of ranged in the hundreds of dollars.
engine95 said:
You said the phone was tmo and it's bootloader is unlocked. My guess it they flashed something they shouldn't have.
I don't know what a USB jig is but I'd say go for it cause it can't hurt it now, I wouldn't think.
My limited knowledge of JTAG is they somewhat disassemble it and hook it to a computer and somehow fix it. The going rates I knew of ranged in the hundreds of dollars.
Click to expand...
Click to collapse
This is correct.
In the event of a hardbrick, almost always what happens is there is a driver on the phone just like the PC, but it does the opposite of a PC driver. The PC driver allows communication to the device, And the device driver allows comminucation with the PC.
In any event, this driver is hidden deep down on a secret partition on the phone and if this driver somehow gets deleted/currupt in any way the device becomes hardbricked and requires a JTAG connection (a physical hookup via other means that is not usb) to be able to reinstall this driver onto the phone to reestablish funtionality to the usb, which would allow flashing funtionality again.
Once in a blue moon you can get a hardbrick from somthing more rare like too much voltage frying a piece of hardware, or something coming loose inside the phone. But it's usually the above reason, in any case the phone would only be able to be fixed by a hardware vendor.
Amb669 said:
This is correct.
In the event of a hardbrick, almost always what happens is there is a driver on the phone just like the PC, but it does the opposite of a PC driver. The PC driver allows communication to the device, And the device driver allows comminucation with the PC.
In any event, this driver is hidden deep down on a secret partition on the phone and if this driver somehow gets deleted/currupt in any way the device becomes hardbricked and requires a JTAG connection (a physical hookup via other means that is not usb) to be able to reinstall this driver onto the phone to reestablish funtionality to the usb, which would allow flashing funtionality again.
Once in a blue moon you can get a hardbrick from somthing more rare like too much voltage frying a piece of hardware, or something coming loose inside the phone. But it's usually the above reason, in any case the phone would only be able to be fixed by a hardware vendor.
Click to expand...
Click to collapse
LG said an option is to send it in for repair, and it could be over or under $100 to fix, so I'm debating what to do from here. Are there any other means of recovering from a hard brick? I was set on getting this for a great price and if I put more money into it, it sorta lessens the deal
f2bacon said:
LG said an option is to send it in for repair, and it could be over or under $100 to fix, so I'm debating what to do from here. Are there any other means of recovering from a hard brick? I was set on getting this for a great price and if I put more money into it, it sorta lessens the deal
Click to expand...
Click to collapse
Sorry to hear this, But if you can't get into download mode then sending it to LG is your only option since they are the only ones with a LG G3 JTAG.
Maybe one day someone in our community might be able to create a JTAG for the G3 but it is extremely unlikely and it won't happen any time soon.
Cut your losses and go from there since what happened already happened. Spending the $100 to get it fixed is far better than a $700 loss.
So the LG Flashtool still goes with the motions with the phone recognized as QHSUSB_BULK , or as my windows 8 computer calls it, "Qualcomm HS-USB QDLoader 9008" but it stops. I doubt the log would be helpful for anyone, but I've been trained to provide logs.
[23:49:34] ¡Ú Tool : 1, 8, 6, 527 : C:\LG\LGFLASHTOOL\LGFLASHTOOL.EXE
[23:49:34] ¡Ú DLL : 1.0.0.0 : C:\Users\Bacon\Desktop\LGD851_20140611_LGFLASHv160.dll
[23:49:34] Process :
[23:49:34] BIN : C:\Users\Bacon\Desktop\LGD851AT-01-V10c-310-260-JUN-20-2014+0.tot
[23:49:34] SCR :
[23:49:34] PRL : ;;;;;;;;;;
[23:49:34] ERI :
[23:49:34] + 1. Web Download Mode = -1
[23:49:34] + 4. Web param-Bin Version =
[23:49:34] Frmae Type : LGFlashTool
[23:49:34] Load : 19 Total : 4194303KB Avail : 4194303KB
[23:49:34] AvailPage : 4194303KB AvailVirtual : 1924508KB
[23:49:34] Total/Free of C:\ : 122101 MB / 37402 MB
[23:49:34]
¡Ú¡Ú¡Ú Factory Information ¡Ú¡Ú¡Ú
[23:49:34] 1. Model Name :
[23:49:34] 2. SWV :
[23:49:34] 3. SWOV :
[23:49:34] 4. PID :
[23:49:34] 5. IMEI :
[23:49:34]
[23:49:34] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:34] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x488
[23:49:34] CPort:penPort() Success. Port number is 41
[23:49:34] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:34] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:36] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:36] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x490
[23:49:36] CPort:penPort() Success. Port number is 41
[23:49:36] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:36] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:37] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:37] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x47c
[23:49:37] CPort:penPort() Success. Port number is 41
[23:49:37] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:37] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:38] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:38] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x47c
[23:49:38] CPort:penPort() Success. Port number is 41
[23:49:38] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:38] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:39] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:39] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x47c
[23:49:39] CPort:penPort() Success. Port number is 41
[23:49:39] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:39] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:40] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:40] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x480
[23:49:40] CPort:penPort() Success. Port number is 41
[23:49:40] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:40] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:41] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:41] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x4a4
[23:49:41] CPort:penPort() Success. Port number is 41
[23:49:41] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:41] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:42] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:42] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x4a4
[23:49:42] CPort:penPort() Success. Port number is 41
[23:49:42] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:42] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:43] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:43] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x4a4
[23:49:43] CPort:penPort() Success. Port number is 41
[23:49:43] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:43] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:45] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:45] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x4a0
[23:49:45] CPort:penPort() Success. Port number is 41
[23:49:45] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:45] CBasicComControl::Close, the port(COM41) is closed successfully
[23:49:46] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[23:49:46] CBasicComControl:pen, the port(COM 41) is constructed successfully => HANDLE : 0x4a0
[23:49:46] CPort:penPort() Success. Port number is 41
[23:49:46] CComPort::ClosePort, Closed Port Successfully for COM 41
[23:49:46] CBasicComControl::Close, the port(COM41) is closed successfully
ohmygod the emojis
f2bacon said:
ohmygod the emojis
Click to expand...
Click to collapse
hahahaha, i know right.
Anyways, your error is a usb error.
Do you have your phone on "com port 41" on your PC? it MUST to be on com port 41 in order to flash.
Amb669 said:
hahahaha, i know right.
Anyways, your error is a usb error.
Do you have your phone on "com port 41" on your PC? it MUST to be on com port 41 in order to flash.
Click to expand...
Click to collapse
Yeah, "Qualcomm HS-USB QDLoader 9008 (COM41)"
f2bacon said:
Yeah, "Qualcomm HS-USB QDLoader 9008 (COM41)"
Click to expand...
Click to collapse
Did you set the PC to com 41 though? in the device manager under com ports it should report "LGE Mobile USB Serial Port (COM 41)"
Even if your flashing app is set to com 41, you still need to set windows to com 41 via device manager or it won't know what com 41 is for.
Amb669 said:
Did you set the PC to com 41 though? in the device manager under com ports it should report "LGE Mobile USB Serial Port (COM 41)"
Click to expand...
Click to collapse
Yeah I did have to, it originally came up as COM3. Damn I really thought I was onto something. Even though the screen didn't respond it still connects via usb and recognizes the qualcomm, I thought it was a glimmer of hope
f2bacon said:
Yeah I did have to, it originally came up as COM3. Damn I really thought I was onto something. Even though the screen didn't respond it still connects via usb and recognizes the qualcomm, I thought it was a glimmer of hope
Click to expand...
Click to collapse
I'm starting to run out of stuff i can think of.
When you downloaded your version of LG flash tools, did your version came with an extra megalock.dll file to replace the one that gets installed? this is required for LG flash tools to have proper permissions to access your phone.
If you haven't already tried another PC, i would HIGHLY recommend it as i bricked my device and my 2014 PC wouldn't flash no matter what i tried, after over 5 hours of frustration i tried my sisters 10 year old laptop and it flashed my device without hesitation.
Also that driver name "Qualcomm HS-USB QDLoader 9008 (COM41)" doesn't sound right, you should try and reinstall your drivers and make sure your using the LGUnitedMobileDriver
And somtimes it can be as simple of an issues like not restarting your PC after installing drivers sometimes will cause issues.
Amb669 said:
I'm starting to run out of stuff i can think of.
If you haven't already tried another PC, i would HIGHLY recommend it as i bricked my device and my 2014 PC wouldn't flash no matter what i tried, after over 5 hours of frustration i tried my sisters 10 year old laptop and it flashed my device without hesitation.
Click to expand...
Click to collapse
This is my second computer! I guess we think alike haha
The issue seems to be it's not recognizing the device as a G3, but as the processor. No amount of driver installation seems to be changing that either. I just may have to go to LG for repair :/
f2bacon said:
This is my second computer! I guess we think alike haha
The issue seems to be it's not recognizing the device as a G3, but as the processor. No amount of driver installation seems to be changing that either. I just may have to go to LG for repair :/
Click to expand...
Click to collapse
haha, this is true
Yea it defnitly has something to do with the PC not detecting the phone, sorry i couldn't help more.
Amb669 said:
haha, this is true
Yea it defnitly has something to do with the PC not detecting the phone, sorry i couldn't help more.
Click to expand...
Click to collapse
It's alright! Turns out since the phone is under a year old, the 12 month warranty carries over regardless! Sending it back tomorrow! Free repair!
the moral of this problem is to not let anybody use ur phone unless they know what they are doing
hello00 said:
the moral of this problem is to not let anybody use ur phone unless they know what they are doing
Click to expand...
Click to collapse
I bought it broken for around $300 and got it fixed for free, I don't know how your "moral to the problem" applies to my situation whatsoever
Related
[Q] Bricked Find 7
Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version. http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25 The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made. Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty? I can't reach recovery,fastboot or anything Any help would be much appreciated. Thank's a lot
bcuraman said: Hey guys. I tried to flash TeamEOS rom latest nightly on my device,and the flashing process went fine. I was using the TWRP gummified version and it said it was all successfull. This is the link,and on the download pages there is Find7 version. http://www.oppoforums.com/threads/rom-4-4-4-teameos-the-revival-nightlies.16320/page-25 The problem is,after flashed everything,my phone died. I think i made a mistake when flashed the modem package,which is supposed to be for the find5.. I didn't thought that it could make the difference,but it might have made. Now my phone won't start,boot or anything. Simply died. Is there anyway i could try to bring him back to life before i send it to the warranty? I can't reach recovery,fastboot or anything Any help would be much appreciated. Thank's a lot Click to expand... Click to collapse Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006 Let me know if it shows that. (go to device manager on pc to check that) If it doesnt show, try taking the battery out and putting it back and then connecting to pc.
suraj.das said: Okay. Try to connect your phone to your PC and see if your phone is showed as "QHSUSB BULK" Or qualcomm 9008/9006 Let me know if it shows that. (go to device manager on pc to check that) If it doesnt show, try taking the battery out and putting it back and then connecting to pc. Click to expand... Click to collapse yeah: This is the result of the command line: " 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3) [50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2) [50149.664014] wlan0: associated [51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci [51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008 [51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [51146.928969] usb 1-4: Product: QHSUSB__BULK [51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM [51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected [51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0
bcuraman said: yeah: This is the result of the command line: " 50149.656170] wlan0: associate with 9c:97:26:9d:78:05 (try 1/3) [50149.663938] wlan0: RX AssocResp from 9c:97:26:9d:78:05 (capab=0x411 status=0 aid=2) [50149.664014] wlan0: associated [51146.796129] usb 1-4: new high-speed USB device number 13 using ehci-pci [51146.928956] usb 1-4: New USB device found, idVendor=05c6, idProduct=9008 [51146.928964] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [51146.928969] usb 1-4: Product: QHSUSB__BULK [51146.928974] usb 1-4: Manufacturer: Qualcomm CDMA Technologies MSM [51146.929416] qcserial 1-4:1.0: Qualcomm USB modem converter detected [51146.930584] usb 1-4: Qualcomm USB modem converter now attached to ttyUSB0 Click to expand... Click to collapse Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz Extract it. Connect your phone and then click on the msm 8974download.exe.. Wait till it turns green and then reboot your phone Thanks to Addel from oppoforums.
suraj.das said: Great. Now download this file, http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz Extract it. Connect your phone and then click on the msm 8974download.exe.. Wait till it turns green and then reboot your phone Thanks to Addel from oppoforums. Click to expand... Click to collapse Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then?
bcuraman said: Hmmm if i were on a windows machine,that would be easy,but i'm running Linux Mint 17.. what shall i do then? Click to expand... Click to collapse I have no idea. Sorry. Maybe use your friend's pc? OR VM?
Hi there. I too am having issues with my Find 7 as well. I just bought it today. The previous owner apparently went to flash cm11 and he soft bricked it. The phone will power on to the start screen the the screen stays black and goes on and off. I can get to fastboot but not recovery. I have read in the oppo forums that I need to push the stock recovery too it but am unfamiliar with fastboot. I am willing to pay someone to get this phone working. Any input would be greatly appreciated.
MsmDownloader works great from inside an Windows XP VMWare virtual machine.
LG E980 Stuck at 4.1.2
Hi, I flashed stock rom to fix booting error and in order to install cwm but I end up kinda soft bricking my phone. I am on 4.1.2 now which is working fine but I can't access recovery just black screen with led changing lights continuously. I tried again flash it with tot file but now it is not picking driver in download mode which I forcibly installed to LGE Android Platform USB serial which installed correctly but when I change its port to 41 it gives error that port is in use but still I forcibly set it. Now when I start flashing firmware with LG Flash tool it stuck at ready and cannot pick the phone. I have tried every possible way but I don't any solution. Anyone put some light on this issue ? Thanks in advance.
When I flash using flash tool, it always gets stuck at ready. Unplug the phone and back in immediately. Always works for me. I've gotten the port 41 error before also. I just ignored it. ---------- Post added at 02:52 AM ---------- Previous post was at 02:51 AM ---------- Also, don't turn phone off. When you're at download mode on phone and PC says ready, just unplug phone leaving it in download mode, then plug it back in.
I tried it again but no luck, can you confirm me one thing by checking, in download mode can you tell me full name of device driver in device manager under ports and under universal serial bus controller. I am asking because when I installed forcibly there were 3 drivers though I tried all of them but no luck. Currently I am on LGE Android Platform Composite USB Device and under ports LGE Android Platform USB serial Port(COM 41)
buynsell said: I tried it again but no luck, can you confirm me one thing by checking, in download mode can you tell me full name of device driver in device manager under ports and under universal serial bus controller. I am asking because when I installed forcibly there were 3 drivers though I tried all of them but no luck. Currently I am on LGE Android Platform Composite USB Device and under ports LGE Android Platform USB serial Port(COM 41) Click to expand... Click to collapse Uninstall all drivers, pc suite whatever you have installed and use this one: LGUnitedMobileDriver_S51MAN312AP22_ML_WHQL_Ver_3.12.3
[Q] VS98512b downgrade with FlashTool stuck in "Waiting for connection"
I am trying to downgrade my LG G3 VS98512b so I can root it. I am running Windows 7 Professional Edition in a VM on an elementary OS host. I am following this guide: androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html I have gotten to step 19, but I cannot get past the "Waiting for connection" stage. The device manager tells me "This device cannot start. (Code 10)." It does this shortly after FlashTool starts waiting; before that, the device is working fine. I believe I have correctly installed all of the drivers I need, and I am using the LG connector that came with my phone. I have no idea what the problem is. Please advise.
I had that problem when you get to waiting for connection unplug usb lead from phone then reconnect it and it detects it and finishes the job.....
Sadly, that isn't working. When I try unplugging/replugging the first time, I get the waiting message. If I try again while the message is up, some more messages flash by and FlashTool says "Download FAIL!! (0 sec)." The other messages are Code: PID: NULL IMEI: NULL Model : DLL : VS985 BIN : VS98510B_03.TOT SWV : SWOV : Model Information Check FAIL! 00000000 This all happens within about a second of unplugging my phone. I've tried using a different USB port on my computer, and I've tried waiting varying amounts of time between unplugging and replugging my phone. While this is happening, my phone doesn't change at all; it just keeps the "Firmware Update" screen. I'm also using VirtualBox version 4.3.26, if that makes any difference.
I have the same problem ! Did u fixe it ?
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?
Stuck in USB port - Smart Phone Flash Tool
Hello, I'm in Ubuntu. I'm use Smart Phone Flash Tool. But i'm stuck in USB Port detected. I trying to flash a OS to my phone. I have flashed all my phone into a brick. my phone works fine into i flash my device. Then i use SP Flash Tool again: I trying to connect the device to my Computer i got this error here: Code: Connecting to BROM... Scanning USB port... Search usb, timeout set as 3600000 ms [email protected]/devices/pci0000:00/0000:00:14.0/usb3/3-2 [email protected]/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0 [email protected]/devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/tty/ttyACM0 vid is 0e8d device vid = 0e8d pid is 0003 device pid = 0003 com portName is: /dev/ttyACM0 Total wait time = -1569339566.000000 USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0) USB port detected: /dev/ttyACM0 How can i fix this issues?