Hi every body!
I'm from vietnam,that why my english is so poor,but i'll try to explain my problem and waiting for some help from bros.
My HTC status now:
No any life signal,can not wake up,can't enter hboot,recovery....truly dead.
I had follow this : http://forum.xda-developers.com/showthread.php?t=1627882
Already do command : "gsettings set org.gnome.desktop.media-handling automount false"
My usb port is 2.0,i'm sure that i 99% do correctly same the post,but that can't recognize my device
I'm still S-ON,Stock rom.Locked.
But,recived :
"[email protected]:/home/eadrang# ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections"
I's tried many times,but this loops.evn i plug out and plug in many times,too.
And when i do command : "dmesg",the result is :
[ 6142.914092] qcserial 1-3:1.0: device disconnected
[ 6144.948090] usb 1-3: new high-speed USB device number 23 using ehci_hcd
[ 6145.080952] usb 1-3: New USB device found, idVendor=05c6, idProduct=9008
[ 6145.080961] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6145.080967] usb 1-3: Product: QHSUSB_DLOAD
[ 6145.080973] usb 1-3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 6145.081553] qcserial 1-3:1.0: Qualcomm USB modem converter detected
[ 6145.081809] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0
[ 6152.311255] usb 1-3: USB disconnect, device number 23
[ 6152.311628] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 6152.311669] qcserial 1-3:1.0: device disconnected
[ 6153.984110] usb 1-3: new high-speed USB device number 24 using ehci_hcd
[ 6154.117115] usb 1-3: New USB device found, idVendor=05c6, idProduct=9008
[ 6154.117123] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6154.117129] usb 1-3: Product: QHSUSB_DLOAD
[ 6154.117135] usb 1-3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 6154.117577] qcserial 1-3:1.0: Qualcomm USB modem converter detected
[ 6154.120219] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0
[email protected]:/home/eadrang#
That my problem,so,can some one help me a advice?:crying:
eadrang said:
Hi every body!
I'm from vietnam,that why my english is so poor,but i'll try to explain my problem and waiting for some help from bros.
My HTC status now:
No any life signal,can not wake up,can't enter hboot,recovery....truly dead.
I had follow this : http://forum.xda-developers.com/showthread.php?t=1627882
Already do command : "gsettings set org.gnome.desktop.media-handling automount false"
My usb port is 2.0,i'm sure that i 99% do correctly same the post,but that can't recognize my device
I'm still S-ON,Stock rom.Locked.
But,recived :
"[email protected]:/home/eadrang# ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections"
I's tried many times,but this loops.evn i plug out and plug in many times,too.
And when i do command : "dmesg",the result is :
[ 6142.914092] qcserial 1-3:1.0: device disconnected
[ 6144.948090] usb 1-3: new high-speed USB device number 23 using ehci_hcd
[ 6145.080952] usb 1-3: New USB device found, idVendor=05c6, idProduct=9008
[ 6145.080961] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6145.080967] usb 1-3: Product: QHSUSB_DLOAD
[ 6145.080973] usb 1-3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 6145.081553] qcserial 1-3:1.0: Qualcomm USB modem converter detected
[ 6145.081809] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0
[ 6152.311255] usb 1-3: USB disconnect, device number 23
[ 6152.311628] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 6152.311669] qcserial 1-3:1.0: device disconnected
[ 6153.984110] usb 1-3: new high-speed USB device number 24 using ehci_hcd
[ 6154.117115] usb 1-3: New USB device found, idVendor=05c6, idProduct=9008
[ 6154.117123] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6154.117129] usb 1-3: Product: QHSUSB_DLOAD
[ 6154.117135] usb 1-3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 6154.117577] qcserial 1-3:1.0: Qualcomm USB modem converter detected
[ 6154.120219] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0
[email protected]:/home/eadrang#
That my problem,so,can some one help me a advice?:crying:
Click to expand...
Click to collapse
how you bricked it??
I was installed game, after that it restart itself, and boot loops, i charge it to wall, and loops happen overnight, tomorrow, it's dead.
Sent from my HTC One X+ using xda premium
eadrang said:
I was installed game, after that it restart itself, and boot loops, i charge it to wall, and loops happen overnight, tomorrow, it's dead.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
thats very damn weird but the thing is i hope you noticed this line
Note: This will fix only devices which were bricked by turning S ON. And bricks caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device. Any devices bricked with other ways are currently *not* supported. We are working on it
anyway the only hope is to join their IRC and ask for help their more active in their than in xda
eadrang said:
I was installed game, after that it restart itself, and boot loops, i charge it to wall, and loops happen overnight, tomorrow, it's dead.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
You installed a game? As in an app? How can that brick you?
Ok this is a shot in the dark but what about if you take out the battery, charge it overnight, then turn it on.
Wait hold on a minute, if you turn it off then hold down volume down for a few seconds then hold power can you get into the bootloader? If you can do that you aren't bricked. Then you can flash a recovery using hasoons toolkit then a stock rom. Something like that, but if the bootloader is accessible, then you aren't bricked, my friend.
Sent from my HTC_Amaze_4G using Tapatalk 2
"Users with the QHSUSB_DLOAD issue can now fully recover their phones and get them fully functional."
I have exactly this QHSUSB_DLOAD issue, it means my cellphone is truly bricked, when I connect phone to windows, i's received a request for
QHSUSB_DLOAD driver.
Sent from my HTC One X+ using xda premium
SuperAfnan said:
You installed a game? As in an app? How can that brick you?
Ok this is a shot in the dark but what about if you take out the battery, charge it overnight, then turn it on.
Wait hold on a minute, if you turn it off then hold down volume down for a few seconds then hold power can you get into the bootloader? If you can do that you aren't bricked. Then you can flash a recovery using hasoons toolkit then a stock rom. Something like that, but if the bootloader is accessible, then you aren't bricked, my friend.
Sent from my HTC_Amaze_4G using Tapatalk 2
Click to expand...
Click to collapse
Thanks for ur reply, but it's still not working on this case. Nothing happened, events i tried to replace with fully battery from another htc amaze phone.
Sent from my HTC One X+ using xda premium
eadrang said:
Thanks for ur reply, but it's still not working on this case. Nothing happened, events i tried to replace with fully battery from another htc amaze phone.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Well this unbrick project worked for some people I know so I can't tell it's something wrong with that make sure you have the exact requirements they asked for also ask help in that thread the dev is still active he can help you
Sent from my HTC_Amaze_4G using xda premium
Still waiting for a helpful
Sent from my HTC One X+ using xda premium
eadrang said:
Still waiting for a helpful
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Post on unbrick project thread that's the only way you can have dexter's attention (dev of unbrick project)
Sent from my HTC_Amaze_4G using xda premium
I'm trying. I don't understand why everyone needs to post ten topics to have right for replying in that page. Do you want everyone makes a spammed before joining your 4rum,moderate?
Sent from my HTC One X+ using xda premium
eadrang said:
I'm trying. I don't understand why everyone needs to post ten topics to have right for replying in that page. Do you want everyone makes a spammed before joining your 4rum,moderate?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
LOOOL it's cuz there was this guy called avengesevenfold he use to open threads and post posta every hour like heaps reason that this rule came I guess haha
Sent from my HTC_Amaze_4G using xda premium
eadrang said:
I'm trying. I don't understand why everyone needs to post ten topics to have right for replying in that page. Do you want everyone makes a spammed before joining your 4rum,moderate?
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Not ten topics, 10 posts... unless something has changed & I didn't know
eadrang said:
Hi every body!
I'm from vietnam,that why my english is so poor,but i'll try to explain my problem and waiting for some help from bros.
My HTC status now:
No any life signal,can not wake up,can't enter hboot,recovery....truly dead.
I had follow this : http://forum.xda-developers.com/showthread.php?t=1627882
Already do command : "gsettings set org.gnome.desktop.media-handling automount false"
My usb port is 2.0,i'm sure that i 99% do correctly same the post,but that can't recognize my device
I'm still S-ON,Stock rom.Locked.
But,recived :
"[email protected]:/home/eadrang# ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections"
I's tried many times,but this loops.evn i plug out and plug in many times,too.
And when i do command : "dmesg",the result is :
[ 6142.914092] qcserial 1-3:1.0: device disconnected
[ 6144.948090] usb 1-3: new high-speed USB device number 23 using ehci_hcd
[ 6145.080952] usb 1-3: New USB device found, idVendor=05c6, idProduct=9008
[ 6145.080961] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6145.080967] usb 1-3: Product: QHSUSB_DLOAD
[ 6145.080973] usb 1-3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 6145.081553] qcserial 1-3:1.0: Qualcomm USB modem converter detected
[ 6145.081809] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0
[ 6152.311255] usb 1-3: USB disconnect, device number 23
[ 6152.311628] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 6152.311669] qcserial 1-3:1.0: device disconnected
[ 6153.984110] usb 1-3: new high-speed USB device number 24 using ehci_hcd
[ 6154.117115] usb 1-3: New USB device found, idVendor=05c6, idProduct=9008
[ 6154.117123] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6154.117129] usb 1-3: Product: QHSUSB_DLOAD
[ 6154.117135] usb 1-3: Manufacturer: Qualcomm CDMA Technologies MSM
[ 6154.117577] qcserial 1-3:1.0: Qualcomm USB modem converter detected
[ 6154.120219] usb 1-3: Qualcomm USB modem converter now attached to ttyUSB0
[email protected]:/home/eadrang#
That my problem,so,can some one help me a advice?:crying:
Click to expand...
Click to collapse
have u figured out a way to fix? please share if so, thanks! i'm in the same situation
Sent from my Desire Z using xda app-developers app I recently purchase a htc amaze 4g, which was bricked but powered on occasionally, i read the unbrick project for may amaze and carried out the steps to unbricking how ever i got the following error in the unbrick project:
Searching for bricked device...
The bricked device is on
sdb
Use the above node to perform operations using the emmc_recover tool
[email protected]:/home/shannan# sudo ./emmc_recover --flash ruby1.93.nb0 --device /dev/sdb12 --backupafter hboot_f.nb0
=== emmc_recover 0.2, written by Fuses =====
Messing up with device /dev/sdb12, ARE YOU SURE?
CTRL+C if not, ENTER to continue
Flash image file is ruby1.93.nb0
Device is /dev/sdb12
Press ENTER if everything is correct, CTRL+C if not
Waiting device /dev/sdb12.......
Foundit!
dd: writing `/dev/sdb12': Input/output error
89+0 records in
88+0 records out
180224 bytes (180 kB) copied, 21.4905 s, 8.4 kB/s
Return code is 256
FAILED!!
The device also doesn't show any hdd file folders when detected with the script 'brickdetect.sh'
Any help will be deeply appreciated.
You are posting in the wrong thread @Cannon1994, i told you to post it in the htc amaze unbricking project thread. And second thing is how did you even brick the cell phone in the first place, different solotions for different causes.
Sent from my HTC_Amaze_4G using Tapatalk
Muneeb Saeed said:
You are posting in the wrong thread @Cannon1994, i told you to post it in the htc amaze unbricking project. And second thing is how did you even brick the cell phone in the first place, different solotions for different causes.
Sent from my HTC_Amaze_4G using Tapatalk
Click to expand...
Click to collapse
Muneeb, I don't think he has enough posts to get into the unbricking project thread. I think he needs 10 posts to post in the dev section. Anyways @Cannon1994 here is the thread that Muneeb has been referring you to http://forum.xda-developers.com/showthread.php?t=1627882
Maybe as you read through it you'll get some ideas.
I hope this helps
Ciao
Ok just viewed his profile and he is a newbie
Sent from my HTC_Amaze_4G using Tapatalk
Thank you ive being trting to get into the unbrick thread but as u said probably i need 10 post first
Ok explain how did you brick it in the first place. Are you S-ON, bootloader unlocked, rooted etc.
Sent from my HTC_Amaze_4G using Tapatalk
---------- Post added at 12:44 AM ---------- Previous post was at 12:40 AM ----------
Ok i read your older post, i dont think a bricked phone is supposed to turn on in the first place. I think you should have flashed a factory ruu or it might have been a hardware issue.
Sent from my HTC_Amaze_4G using Tapatalk
Related
Hi
i am trying to connect my Xperia Ray on my computers running Ubuntu 13.04 but i am having troubles. Adb and Fastboot are not detecting any device.
The funny thing is that my other phone, a Nexus 4, is correctly detected and working.
My Xperia Ray was flashed with CM 10.1 + default CM 10.1 kernel and i cannot even go in fastboot mode by pressing Vol Up at start: the blue led is blinking for half a second and then the charging screen is appearing.
Have anybody of you the same issue with CM 10.1?
How can i flash a different kernel in CWM recovery to unlock fastboot?
Best regard
Volume up at start? You just have to push the volume up button when it's turned off and connect the usb to your PC. Then Ubuntu should detect it
For me my xperia mini pro and my nexus 4/7 are working great on Ubuntu 13.04
Sent from my Nexus 4 running Android 4.2.2
I do already it.
When i do this, the blue led fblinks for haf a second and then goes in charging mode.
Running dmesg on linux, it says "failed to enumerate device on port 2"
It's not a problem of linux, because the Nexus 4 is working fine with it.
I think it's a kernel issue, but how can i flash a new kernel without entering in fastboot mode?
mihahn said:
Volume up at start? You just have to push the volume up button when it's turned off and connect the usb to your PC. Then Ubuntu should detect it
For me my xperia mini pro and my nexus 4/7 are working great on Ubuntu 13.04
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
mikedj84 said:
I do already it.
When i do this, the blue led fblinks for haf a second and then goes in charging mode.
Running dmesg on linux, it says "failed to enumerate device on port 2"
It's not a problem of linux, because the Nexus 4 is working fine with it.
I think it's a kernel issue, but how can i flash a new kernel without entering in fastboot mode?
Click to expand...
Click to collapse
If your device is powered on, are you able to run adb? Try to run adb devices and see if it comes up there
If yes use adb reboot bootloader (I guess) for fastboot mode
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
If your device is powered on, are you able to run adb? Try to run adb devices and see if it comes up there
If yes use adb reboot bootloader (I guess) for fastboot mode
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
The problem is that neither adb or fastboot work..
using dmesg command, the result is:
Code:
[346390.854534] usb 3-1: new full-speed USB device number 8 using xhci_hcd
[346390.854778] usb 3-1: Device not responding to set address.
[346391.058748] usb 3-1: Device not responding to set address.
[346391.262533] usb 3-1: device not accepting address 8, error -71
[346391.374523] usb 3-1: new full-speed USB device number 9 using xhci_hcd
[346391.374743] usb 3-1: Device not responding to set address.
[346391.578744] usb 3-1: Device not responding to set address.
[346391.782514] usb 3-1: device not accepting address 9, error -71
[346391.894542] usb 3-1: new full-speed USB device number 10 using xhci_hcd
[346391.894780] usb 3-1: Device not responding to set address.
[346392.098778] usb 3-1: Device not responding to set address.
[346392.302521] usb 3-1: device not accepting address 10, error -71
[346392.414523] usb 3-1: new full-speed USB device number 11 using xhci_hcd
[346392.414742] usb 3-1: Device not responding to set address.
[346392.618777] usb 3-1: Device not responding to set address.
[346392.822546] usb 3-1: device not accepting address 11, error -71
[346392.822565] hub 3-0:1.0: unable to enumerate USB device on port 1
and adb shows "no devices found". It happens also when i am in CWM and when i do "mount usb", it doesn't show anything
mikedj84 said:
The problem is that neither adb or fastboot work..
using dmesg command, the result is:
Code:
[346390.854534] usb 3-1: new full-speed USB device number 8 using xhci_hcd
[346390.854778] usb 3-1: Device not responding to set address.
[346391.058748] usb 3-1: Device not responding to set address.
[346391.262533] usb 3-1: device not accepting address 8, error -71
[346391.374523] usb 3-1: new full-speed USB device number 9 using xhci_hcd
[346391.374743] usb 3-1: Device not responding to set address.
[346391.578744] usb 3-1: Device not responding to set address.
[346391.782514] usb 3-1: device not accepting address 9, error -71
[346391.894542] usb 3-1: new full-speed USB device number 10 using xhci_hcd
[346391.894780] usb 3-1: Device not responding to set address.
[346392.098778] usb 3-1: Device not responding to set address.
[346392.302521] usb 3-1: device not accepting address 10, error -71
[346392.414523] usb 3-1: new full-speed USB device number 11 using xhci_hcd
[346392.414742] usb 3-1: Device not responding to set address.
[346392.618777] usb 3-1: Device not responding to set address.
[346392.822546] usb 3-1: device not accepting address 11, error -71
[346392.822565] hub 3-0:1.0: unable to enumerate USB device on port 1
and adb shows "no devices found". It happens also when i am in CWM and when i do "mount usb", it doesn't show anything
Click to expand...
Click to collapse
Did you add the usb driver in /etc/udev/rules.d/99-android.rules?
How did you install fastboot/adb? Using the following commands?
Code:
# sudo add-apt-repository ppa:nilarimogard/webupd8
# sudo apt-get update
# sudo apt-get install android-tools-adb android-tools-fastboot
Try it again and afterwards connect it
i've tried with this ppa on Ubuntu and then also under Windows 8,but it's not working.
the device doesn't detect the pc, but just uses it like a charger, and the pc doesn't recognize the device. I've used different cables (the original one + another one of a Nexus 4) but still it isn't recognized, while any other android device works.
I guess it's a problem related to the usb port of the phone.
Hello
I've got Lark Freeme 70.65, it's a cheap tablet based on Allwinner A13 procesor. It was allright till yesterday. I installed here CWM and Cyanogenmod 10.1 from there and it still was allright. But then suddenly, when I tried to replace camera drivers, everything collapsed, touchscreen is completely reversed in Y axis and it ain't got it's full range, so it was completely unaccesible. But it wasn't so bad, I did recovery of my stock rom from CWM mod, then once again installed cyanogenmod 10.1 and I did few experiments. It was nothing that would really hurt it, but I was so unlucky than in one moment every one way of access to the tablet failed. So right now I cannot use USB connection in any way, CWM when I try to recovery says about 'MD5 mismatch' (I haven't touched clockworkmod folder at all!) and I have touchscreen that is responding but is completely unusable.
Of course I tried different USB cable, different computer, different system and everything. lsusb can't see device at all, so do ADB. dmesg says this:
Code:
[91554.840089] usb 4-6: new high-speed USB device number 10 using ehci-pci
[91554.984872] usb 4-6: New USB device found, idVendor=18d1, idProduct=0003
[91554.984881] usb 4-6: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[91554.984885] usb 4-6: Product: Android
[91554.984888] usb 4-6: Manufacturer: USB Developer
[91554.984892] usb 4-6: SerialNumber: 200804116426ef0
[91554.985969] usb-storage 4-6:1.0: USB Mass Storage device detected
[91554.986928] scsi8 : usb-storage 4-6:1.0
[91555.561110] usb 4-6: USB disconnect, device number 10
so it connects disconnects immediately after plugging the usb cable.
It would be great if I only could restore touchscreen or usb connection. I thought that replacing the rom would help, but CWM can restore them only from zips, and I have only imgs and I haven't found any way to do this.
I'm starting to accept my sytuation, this device was very cheap (170 PLN, it should be about $60), but it would be a great experience and happines for me to repair it. If anyone have got his own lark freeme 70.65 backup from CWM or any other Allwinner A13 and could upload this for me, I could try it out from any SD card (sadly I lost my own backup). Any other propositions also in common.
flashed new rom with sad consequesces. Unable to get tab out of booting recovery kernal image. unable to reconnect to tablet as it show usb not recognized. have updated usb files with naked usb zip and also new fv flash files. still not getting anywhere. I have tried to flash recovery at apx but not working. Is there any hope or have I created a true brick/
Is your PC recognizing the gTab in APX mode (Power and Vol [-])? Does nvflash complete? Post screenshots.
usb not recognized
rajeevvp said:
Is your PC recognizing the gTab in APX mode (Power and Vol [-])? Does nvflash complete? Post screenshots.
Click to expand...
Click to collapse
usb not recognized, tablet goes into apx but the computer does not recognize it. I have tried several different driver combinations and it still cant' see it. I think that I somehow screwed up the driver in the tablet. but can't even get it to connect to the computer. I tried a linux connection and it didn't recognize it either. I was using a live cd and tried to get the startup to locate a driver, no such luck. Is there a way I can completly format the tablet??? I can't get it past the boot loader error. thanks for your input up to now. hope someone has answers for me. I may have created a very nice parts machine.
mfmmetz said:
I think that I somehow screwed up the driver in the tablet.
Click to expand...
Click to collapse
You can't screw-up the APX-mode USB driver on the gTablet--it's built into the system firmware --ie. it's hard-coded. A HW error is a more likely culprit (if, indeed, the PC doesn't see the tablet in APX mode) . Disassemble the gTab and carefully inspect the USB port and surroundings for stray bits of metal, or solder, or cut traces, etc.
I tried a linux connection and it didn't recognize it either. I was using a live cd and tried to get the startup to locate a driver, no such luck.
Click to expand...
Click to collapse
Since you can use Linux, do this:
1. Boot into Linux.
2. Put the tablet into APX mode (the screen will turn off).
3. Plug the cable from the tablet into the PC.
4. Run these command (only the stuff in bold) and post their output (or a screenshot):
Code:
$ [B]dmesg | tail -n20[/B]
...
[ 7872.447589] usb 1-2.2: new full-speed USB device number 8 using ohci_hcd
[ 7872.552503] usb 1-2.2: New USB device found, idVendor=[B]0955[/B], idProduct=[B]7820[/B]
[ 7872.552514] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7872.552521] usb 1-2.2: Product: APX
[ 7872.552528] usb 1-2.2: Manufacturer: NVIDIA Corp.
$ [B]lsusb
[/B]...
Bus 001 Device 008: ID [B]0955:7820 NVidia Corp.[/B]
...
$
I can't get it past the boot loader error.
Click to expand...
Click to collapse
Take a snap and post it.
Hello,
I'm trying to do a nvflash backup of my Prime to avoid bricks, but I can't connect it with APX nor in Windows neither in Linux.
In Linux I obtain this, and the device is not connected:
[ 170.990681] usb 2-1.2.1.2: new high-speed USB device number 17 using ehci-pci
[ 176.064021] usb 2-1.2.1.2: device descriptor read/64, error -71
Click to expand...
Click to collapse
In Windows the device still as Unknown Device even when I've installed the Naked Driver.
I've try in several PCs, in all USB ports, even with a powered hub, with the same results.
Any idea, please?
Linux Debian x64 and Windows 7 x64
Thanks!
Hi,
Yesterday a friend of mine gave me a LG L9 (P760). Some months (or maybe years) ago he changed this phone for a new one and stored it without battery. 2 days ago he tried to turn it on but no life, same result when he connected it to the wall charger.
I tried connecting it without battery to the PC (on Ubuntu, if I use windows 10 the device keeps disconnecting and connecting and I can't install the OMAP4430 driver because win says they are already updated (it isn't so, uses the driver for "usb enumeration failure")) and is recognized, via lsusb, as "ID 0451:d00f Texas Instruments, Inc.".
If i launch dmesg it gives (more than one time):
Code:
[ 973.692035] usb 1-6: new high-speed USB device number 26 using ehci-pci
[ 973.825080] usb 1-6: unable to get BOS descriptor
[ 973.825953] usb 1-6: New USB device found, idVendor=0451, idProduct=d00f
[ 973.825958] usb 1-6: New USB device strings: Mfr=33, Product=37, SerialNumber=0
[ 973.825961] usb 1-6: Product: OMAP4430
[ 973.825964] usb 1-6: Manufacturer: Texas Instruments
[ 976.826505] usb 1-6: USB disconnect, device number 26
.
I tried using the method suggested here: http://vincenzoml.blogspot.it/2013/08/lg-l9-unbrick-script.html. I can get into fastboot but then it says
Code:
sending 'u-boot' (1024 KB)...
OKAY [ 0.675s]
writing 'u-boot'...
FAILED (remote: partition does not exist)
What can I do? Is there a possibility to make this phone work again?
Thanks in advance to all!
Under Win7 i had both the LG drivers and the Google SDK drivers installed. Under Win10 also, but the Google drivers can't be found in device manager. Anyway, in contrary to Win7, the LG drivers and LG software xan niw detect my phone and work, with the exception of Fastboot. Under Win7 and with a custom rom, LG drivers were only good to provide a virtual com port in D/L mode.
And the morale of this tale: These outdated OMAP drivers were never of any use to me.
That's the normal behavior of the OMAP Chip, the only thing you've to do is to re-flash putting back the battery and then, connecting your device over USB while holding Vol+.
Ah, no battery. While it's sometimes recommended to remove the battery during unbricking, i think it's simply impossible to do this or anything w/o battery, despite the 0,5A power via usb.
After a failed attempt to invoke D/L mode, you can remove the battery shortly, or switch the phone on and (force) off for an extra time, to try again. Otherwise it's more likely that D/L mode will again fail.
lecorbusier said:
Ah, no battery. While it's sometimes recommended to remove the battery during unbricking, i think it's simply impossible to do this or anything w/o battery, despite the 0,5A power via usb.
After a failed attempt to invoke D/L mode, you can remove the battery shortly, or switch the phone on and (force) off for an extra time, to try again. Otherwise it's more likely that D/L mode will again fail.
Click to expand...
Click to collapse
I have the battery! The problem is that fastboot can't find the partitions
If the first hurdle has been passed, and there is actual access to the phone(i'm not sure whether this is the case here), the partitions really got deleted or damaged. Unbricking with a stock rom is the only option. Or professional service (better a new phone) if that ain't possible.
Can't you try this, please? http://forum.xda-developers.com/showthread.php?t=2546571 I've found it on the forum just a couple of minutes ago, I hope it helps .
Good luck!
I have the same problem.
If x-loader and u-boot partitions does not exist, we do not have the bootloader, and you can't do anything to make the phone work aside from JTAG.
I tried to boot recovery from computer without flashing using 'boot' command (fastboot boot recovery.img) and this still doesn't work because I don't have bootloader.
Method from post above does not work for me.