Related
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.
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
Hello, everybody,
I am experiencing problems with my hardware/kernel module when connecting two softbricked devices:
Motorola Moto C (xt1757)
Fiesta Duo I6C (China phone)
I am connecting them without battery so I can access them as /dev/ttyACM0; which would allow me to use SP Flash Tool.
However, device gets disconnected after 3 seconds or so, with the following error message:
Code:
kernel: usb 1-3: new high-speed USB device number 83 using ehci-pci
kernel: usb 1-3: New USB device found, idVendor=0e8d, idProduct=2000, bcdDevice= 1.00
kernel: usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
kernel: usb 1-3: Product: MT65xx Preloader
kernel: usb 1-3: Manufacturer: MediaTek
kernel: cdc_acm: probe of 1-3:1.0 failed with error -22
kernel: cdc_acm 1-3:1.1: ttyACM0: USB ACM device
mtp-probe[17092]: checking bus 1, device 83: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-3"
mtp-probe[17092]: bus: 1, device: 83 was not an MTP device
mtp-probe[17110]: checking bus 1, device 83: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-3"
mtp-probe[17110]: bus: 1, device: 83 was not an MTP device
kernel: usb 1-3: USB disconnect, device number 83
which tells me that the device is being detected by the Kernel and the right module kicks in; yet, it might not have the firmware, or something like it, necessary to achieve successful communication.
So has anyone being able to overcome this issue?
I am currently using artix linux (fork of arch linux without systemd) with ck kernel 4.20.5.1
I have tried connecting the phones at my USB 2.0 (as shown above) and USB 3.0 ports. The same result is obtained.
I will appreciate any assistance that could be provided. Thank you in advance.
Regards.
I managed to get it working.
You have to
open SP Flash Tool,
provide all your data (scatter file, download agent, authentication, et cetera),
click download,
then connect the device.
Hope this helps somebody.
Connection:
USB 2.0, original datacable.
When the device is on:
and when the device is off, the device is not even listing in the device manager as any device (like Other device->Android..etc). It is not detecting at all.!
What could be the issue here?
jithuelad said:
Connection:
USB 2.0, original datacable.
When the device is on:
and when the device is off, the device is not even listing in the device manager as any device (like Other device->Android..etc). It is not detecting at all.!
What could be the issue here?
Click to expand...
Click to collapse
Which platform are u using?
Amd or intel