My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Have you installed the LG drivers for your pc and tried the unbrick method?
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
twill1987 said:
My LG E980 is bricked. I can access download mode and that is it! I am unable to boot into recovery,
and the hard reset screen simply sits there forever. My computer only recognizes my device as an "unknown usb device."
I'm unsure what can be done about this, but I feel like this is better than the infamous QHSUB icon displayed when the device cannot be recovered.
Does anyone have a remedy for this problem?? I have GOT to fix this phone and can't afford to Jtag the device, but I'm losing hope that this is possible, PLEASE help. :crying:
Click to expand...
Click to collapse
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Yes
riki126 said:
Have you installed the LG drivers for your pc and tried the unbrick method?
Click to expand...
Click to collapse
Yes I tried that. The drivers won't install. I even used another windows 8 computer my roommate has and switched out
the usb cables, still came back "unknown device"
shabbypenguin said:
There is never a time when this device cant be recovered. even the qhusb is a fairly simple fix. ill go ahead and make a sdcard boot image tonight. do you have a 32gb sdcard? (or larger) and an sdcard reader, if you have those two things i can make an unbrick.img that you flash toi the sdcard and put in the non-booting phone and it will get you to download mode/recovery mode. ill have to check out what partitions are where as i dont wish to include my efs along with it all .
Click to expand...
Click to collapse
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Okay
stulzerl said:
Happened to me.
1. With the phone on download mode and plugged in the computer; uninstall the unknown device on your computer using device manager. The computer should try to get the drivers for your phone.
2. If it doesn't. Repeat step one and install the drivers first.
That worked for me hopefully I'll work for you.
Sent from my LG-E980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
twill1987 said:
I will give your method a shot, but I have done this a lot already. The only thing I can think of is I usually unplug the phone from the computer right after deleting the drivers and uninstalling in device manager. Maybe I should just leave the phone plugged in and see if the computer automatically downloads the drivers, but I don't think it will because I've tried to update the drivers before. It gives me an error code "10" and says the device has malfunction or stopped working This phone has been undetectable via USB since flashing the candykat 4.4 rom. Every computer I've tried (3) and every USB cable (3 again) has displayed it as an "unknown device"
Click to expand...
Click to collapse
I've had similar issues when i had my optimus g. I had to use a pc with xp to flasht he phone, dunno why though. You could give that a shot.
twill1987 said:
I do have a 16gb sd card, but I can pick up at 32 gb sd at my local best buy. I have an Asus laptop running windows 8 and it has an SD card reader. I am a little confused (semi-noob) as to how this will work because my phone will boot up, and the led changes colors on the home button for about 4 seconds and then the light stops flashing. The phone is stuck on the LG boot screen, and there is no way out of it but to pull the battery or to reset with power button. Of course no recovery as previously mentioned. I really just want to get back to stock, but I can't manage to get both the windows 8 computers I've tried to detect the phone in download mode. Ever since I switched to the Candykat rom 4.4 the computer wasn't able to recognize the phone, even when the phone was fully functional inside the rom.
I have tried it on my dads windows 7 laptop as well with no dice. Instaled LG drivers, uninstalled LG Drivers, uninstalled device from the Device Manager. I've done everything I could think of. I previously was in a Philz touch recovery, but every rom I tried to flash wouldn't work. I tried to flash another recovery from inside it and then the device bricked like it is now. What a head ache. If you think this method would work, I am more than willing to try it, just unfamiliar with what I need to do on my end.
Click to expand...
Click to collapse
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Thanks
WeActOnImpulse said:
Yeah dude there's an unbrick method. If this doesn't work just sell the phone on Ebay. http://forum.xda-developers.com/showthread.php?t=2302660
Click to expand...
Click to collapse
I have tried this and unfortunately since the USB drivers aren't detected by the computer there is no way for me to flash back to stock.
Thanks for the information though, I appreciate it.
shabbypenguin said:
I dont know lg's download mode, kdz, tot etc all that well. im more of a samsung guy. however qualcomm since the s4 chipset has allowed for sdcards that are properly formatted to boot the os instead of the internal emmc. here is a decent guide, just need to make teh image for this device. this will let your device boot no matter how bad it gets you are welcome to try with 16gb, the rule of thumb i know of is as big as teh emmc is use that same size or larger sdcard, however some people have had sucess withs maller, just not many that i know of. http://forum.xda-developers.com/showthread.php?t=2439367
however afaik the only way to reflash teh bootloader partitions is via kdz/download mode so perhaps the sdcard will let you get into that mode and then you can flash, so long as you keep your sdcard like that it will boot fully, but in order ot get your sdcard back you need to repair teh files on your phone .
Click to expand...
Click to collapse
Wow, that sounds awesome. I followed most of that. I access download mode on the device by pressing vol up and down simultaneously and plugging in the usb cable. I am more willing to try this, and if it works I will pay you from my paypal. I guess all I need now are those files to run to the sd card. I read the tutorial you posted for the samsung and downloaded the windows disk manager. I am eager to try this method, though it is admittedly very new to me.. If you can post those files, I will follow the instructions you give and pay you a little bit of money for your help!
I am a broke college student so it won't be much, but I really appreciate your response and information on this method with the qualcomm s4.
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Just wrote it to sd card
shabbypenguin said:
Here is the unbrick image. follow the guide for your platform (gunna guess windows) and write this to your sdcard after backing it up. from there you need to restore your partitions by flashing them .
https://mega.co.nz/#!YB5xWQ7Y!Qcnx9UmcNn-f6skfiIFN-jd0EeYxdmrQGA1zzP5hfA0
Click to expand...
Click to collapse
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
twill1987 said:
Okay so I bought the 32 gb sd card. Just wrote the .img file you sent me to the sd card.
I powered on the phone and nothing happened, I got the same LG screen where the led flashes and then stops.
I followed that guide, but am I supposed to go to download mode instead of just powering on the device?
I got a little confused by the samsung jargon lol. I just want to know after I've written the unbrick.zip to the sd card
how do I get my phone to recognize the card is there? And once I am able to do that how do I "restore my partitions by flashing them?"
I do have the factory firmware set to flash through lg flashtool, but the phone can't be detected of course due to the usb issue.
Just want to say thanks for walking me through it this far, I feel like I'm close hopefully but unsure what to do next.
Click to expand...
Click to collapse
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Possible hope??
shabbypenguin said:
you wrote the image to the sdcard? i wonder if its because you still have the low level bootloaders that it may not be booting from the sdcard, normally this is done to fix qhusb errored devices. as for restoring the partitions all you would need to do is one its booted up push the unbrick image to the phone and use rooted adb shell to write it back onto your phone.
Click to expand...
Click to collapse
I meant I used the windows tool to write the debrick.img to the sd card. But no dice, the device isn't recognised.
However! I installed a driver clean up tool and now if I plug in the device it is recognized as Android Original ADB Interface.
The LG Flashtools even says the port is ready! But I get the error code "10" "device cannot start, A request for the USB device descriptor failed."
So now I am stuck on that instead lol. This just sucks.
that sucks about the sdcard, it must be because you arent "truly" bricked. sorry i thought it would help ya :/.
What is the driver repair tool you used? I know this thread is old but I'm having the same problem. I was trying to root my E980 and now my computer wont recognize my device. The phone works perfect, its just when I plug it in to the computer it isnt recognized. How can I fix this?
+1
Just wondering if anyone's come across a solution to this besides a sledge hammer... been having the same "Code 10: Device failed to start" when in Download Mode, though Windows finds a driver fine when the phone is stuck on the LG screen... doesn't help much, though, 'cause it won't receive adb commands. I manually installed the LG USB Composite Device driver, which added a modem and a COM port, both of which Windows recognized to be active, but the LG FlashTool USB Viewer showed no open pipes. I'm a relative noob, so please feel free to point out the obvious, like an alternative to adb that the phone can always receive or a way to brick it the rest of the way so the MicroSD trick will work.
I came across this problem like the OP and just wanna let everyone know that you have to use computer with USB 2.0 port then the driver issue would be fixed.
Related
I tried to root it a few weeks ago, but it didn't quite work, so i did a hard reset.
Everything works, except the phone won't boot with the SD card in it (it just keeps looping at the "MyTouch 3g Slide" screen. And the phone will not recognize any SD card. i've tried three. the original samsung 8gb, a kingston 2gb, and a 16gb one. all the cards work perfectly on my computer, one is used to run android on my HD2. so i KNOW it works. I've tried reformatting it also, and that didn't work (FAT32).
how can i fix this?
HotEspresso said:
I tried to root it a few weeks ago, but it didn't quite work, so i did a hard reset.
Everything works, except the phone won't boot with the SD card in it (it just keeps looping at the "MyTouch 3g Slide" screen. And the phone will not recognize any SD card. i've tried three. the original samsung 8gb, a kingston 2gb, and a 16gb one. all the cards work perfectly on my computer, one is used to run android on my HD2. so i KNOW it works. I've tried reformatting it also, and that didn't work (FAT32).
how can i fix this?
Click to expand...
Click to collapse
Can you get to the bootloader and recovery with the SD card in it? If you don't know how hold down the vol down button and power button, then use the volume rocker to go down to recovery and pres power again to select it. If you can't access the bootloader with an sd card in it I would suspect a hardware issue but I'm not sure. If you can get into recovery and flash clockworkmod recovery, then re-download and flash a ROM, such as cyanogenmod 6.1.0 or CR_mod or something. Just to rule out a ROM error.
Might want to try a full wipe again using recovery if you can get into it.
MusicMan374 said:
Can you get to the bootloader and recovery with the SD card in it? If you don't know how hold down the vol down button and power button, then use the volume rocker to go down to recovery and pres power again to select it. If you can't access the bootloader with an sd card in it I would suspect a hardware issue but I'm not sure. If you can get into recovery and flash clockworkmod recovery, then re-download and flash a ROM, such as cyanogenmod 6.1.0 or CR_mod or something. Just to rule out a ROM error.
Click to expand...
Click to collapse
in order to flash CM or clockworkmod recovery, i need to have my phone rooted, correct? what's the easiest way?
HotEspresso said:
in order to flash CM or clockworkmod recovery, i need to have my phone rooted, correct? what's the easiest way?
Click to expand...
Click to collapse
In the Dev section for our phone THIS method.
Also, check the slide rom bible for some other stuff you might need, like the stock rom.
Oh, I assumed you were rooted. When you power on with Vol Down, the first screen is hboot... isn't there a full wipe option there, therefore not requiring the OP to go into recovery?
Yeah, there is a wipe option in Hboot.
fermunky said:
Oh, I assumed you were rooted. When you power on with Vol Down, the first screen is hboot... isn't there a full wipe option there, therefore not requiring the OP to go into recovery?
Click to expand...
Click to collapse
nope. not yet, at least. i'm working on it now, but i keep running into problems. the latest one, is when i run the "adb push exploid /sqlite_stmt_journals" command in step 4, it just says "error: device not found". i'm pretty sure i've done everything right.
is there anyone willing to help walk me through this with an instant messenger or something? i can probably figure it out eventually, but help would be much appreciated.
also, when i plug the phone into the computer, the phone charges, but doesn't recognize the phone. windows (7) says it can't identify it. and when i unplug the phone, it resets.
HotEspresso said:
nope. not yet, at least. i'm working on it now, but i keep running into problems. the latest one, is when i run the "adb push exploid /sqlite_stmt_journals" command in step 4, it just says "error: device not found". i'm pretty sure i've done everything right.
is there anyone willing to help walk me through this with an instant messenger or something? i can probably figure it out eventually, but help would be much appreciated.
also, when i plug the phone into the computer, the phone charges, but doesn't recognize the phone. windows (7) says it can't identify it. and when i unplug the phone, it resets.
Click to expand...
Click to collapse
Yeah you have to download the drivers for the phone. Here's the link: http://www.htc.com/us/support/t-mobile-mytouch-3g-slide/downloads/
Download the sync update, it'll install the drivers necessary for adb to work
MusicMan374 said:
Yeah you have to download the drivers for the phone. Here's the link: http://www.htc.com/us/support/t-mobile-mytouch-3g-slide/downloads/
Download the sync update, it'll install the drivers necessary for adb to work
Click to expand...
Click to collapse
still doesn't work. nothing shows up when i run "adb devices", and it says "error: device not found" when i run the adb push... command.
any ideas?
HotEspresso said:
still doesn't work. nothing shows up when i run "adb devices", and it says "error: device not found" when i run the adb push... command.
any ideas?
Click to expand...
Click to collapse
Do you have USB debugging enabled on your phone?
Sent from my T-Mobile myTouch 3G Slide
MusicMan374 said:
Do you have USB debugging enabled on your phone?
Sent from my T-Mobile myTouch 3G Slide
Click to expand...
Click to collapse
yes i do. i've done everything right.
if it helps, hboot does see my SD card. so i know it's not a hardware issue.
is there any way i can load the original stock firmware? i loaded ESPRIMG.zip and it worked, but didn't do anything.
It must be an issue on the computer side with your computer not recognizing your phone. I'm on my phone at the moment, with an almost dead battery (bad cm6.1 battery life) but when I get to a computer I'll look it up, there's something else you might have to install. Are you on xp vista or 7?
Sent from my T-Mobile myTouch 3G Slide
thanks. i've got windows 7. i can try using another computer. i'll post when i try that.
i called HTC and i'm still under warranty. but will they be able to see my root attempt and not repair it? i don't wanna be charged the $40 "triage fee"
HotEspresso said:
thanks. i've got windows 7. i can try using another computer. i'll post when i try that.
i called HTC and i'm still under warranty. but will they be able to see my root attempt and not repair it? i don't wanna be charged the $40 "triage fee"
Click to expand...
Click to collapse
Yes, they will see your root attempt and say you voided your warranty, but it's easy to unroot. Although I don't think your phone is the issue here, since you can still see your microsd card when you plug into your computer, right? Like if you mount USB storage, it works?
Also, try following the instructions in the link I'm about to paste, I used it and it worked fine for me: http://androidforums.com/t-mobile-mytouch-slide/90832-adb-drivers.html
MusicMan374 said:
Yes, they will see your root attempt and say you voided your warranty, but it's easy to unroot. Although I don't think your phone is the issue here, since you can still see your microsd card when you plug into your computer, right? Like if you mount USB storage, it works?
Also, try following the instructions in the link I'm about to paste, I used it and it worked fine for me: http://androidforums.com/t-mobile-mytouch-slide/90832-adb-drivers.html
Click to expand...
Click to collapse
not from the phone. but i can take the SD card out and put it into my computer.
i'll try the link now.
nope. i already had that driver. but i installed it again anyway. no luck. how can i restore to good enough condition so HTC will fix it?
HotEspresso said:
nope. i already had that driver. but i installed it again anyway. no luck. how can i restore to good enough condition so HTC will fix it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=746577 Flash that, it will flash the pure stock w/OTA update, without root or wifi tether, it's just pure stock. They don't think twice about it.
And if you cant mount usb storage on your phone and see it on your computer, then I think your phone does have an issue with the usb port. Either that or it's a rom issue? Could be something corrupted.
MusicMan374 said:
http://forum.xda-developers.com/showthread.php?t=746577 Flash that, it will flash the pure stock w/OTA update, without root or wifi tether, it's just pure stock. They don't think twice about it.
And if you cant mount usb storage on your phone and see it on your computer, then I think your phone does have an issue with the usb port. Either that or it's a rom issue? Could be something corrupted.
Click to expand...
Click to collapse
it MIGHT be a usb issue, but i doubt it. it can't be a rom issue, because i haven't rooted the phone.
when i hit apply update.zip in recovery, it just says "can't find /sdcard/update.zip". it's definitely there, in the root of the SD card.
any ideas?
EDIT: i just used hboot to load ESPRIMG.zip. i THINK that worked. but it still says firmware 2.1-update 1. will that be enough to clear it for HTC?
Hi all...bare with me here, I posted this earlier, but in the wrong forum section so I am going to start over here.....thanks for your patience....
Hi everyone...I have a problem..I tried to use the Firerat zips to increase my internal storage, and during the flash of the zip file the phone hung and I had to pull the battery out.....since then the usb wont mount.
I am using a Tmobile mytouch slide 3g.
I tried using the sdk and running the fastboot commands etc to get the sd card to mount...no go.
I have tried the fastboot oem enableqxdm 0 command and no go....
Note:..My sd card works fine in a card reader on my computer, I can drag and drop anything to it etc. etc.
Finally i downloaded the stock rom, and i was able to put it on the card, and rename it ESPRIMG.zip and installed it through recovery...My phone was rooted and S-off running ginger, but now back to stock...S-on, and hating the phone now...lol.....
I have been all over the web and I am so confused...everywhere you search there is something different, I just dont know what to do, Windows doesnt recognize the phone when plugged in so I cant load custom rom etc back on....AARGH!!!..I am so frustrated, and have a migraine messing with this damn thing.....lol...
Someone here suggested the MISC is bad and that a binary flash_img would fix it, but honestly, I have no idea what any of that means...all that means to me is confusion, and I have that already.....lol
Can someone please suggest what I may try doing?I am pretty savvy with computers but some of the adb/shell stuff is very confusing to me, I dont like cmd prompts...so maybe a detailed explanation?..
Thank you so much for taking your time to read my problem, I really appreciate it very much.....Dirtylarry
"Kharma...It's a good thing"
ok man im gonna try to understand the problem... you say your usb mount doesnt work but the sdcard works with the adapter, then you went back to stock and un-rooted and the pc doesnt recognize your phone? right?
So it looks to me (just an idea) that the problem is your cable or the port on your pc... just beacuse your sdcard IS working in your phone as well since you used the ESPRIMG.zip(wich was really unnecessary) and you flashed it using the sdcard obviously.
Now you need to find a way to root it again just like you did the first time... dont mess with the drivers since you havent changed them in your pc (i guess) and try this guide....
http://richard.gluga.com/2010/08/complete-guide-to-rooting-and-hacking.html
Now all i can say is ALWAYS DO A NANDROID BACKUP BEFORE MESSING WITH YOUR PHONE. And check the cable/ports... thats the only problem i can think of...
well the fact that I have 3 computers that all used to recoginize the phone just fine is what's weird....none of them do, nor does my usb connection on my car stereo...the computers all say "USb not recognized" etc. etc. and the car stereo says USB N/A .......So i'm just at a loss as to what is going on here....Any ideas????? Thanks much ....Dirtylarry
Try installing PDA Net. It installs USB Drivers and resets the registry. One day it would work, then the next day it didn't work, reinstalling PDA Net worked every time.
Thanks Wave_Sailor, I tried the pda net install but it wont work....Everytime I try it says that it can't handshake to the phone, and then gives me an error code 103, I have tried many many times....also, in the device manager for computer it shows a yellow Exclamation mark everytime I plug the phone in listed at "Other Devices", and says Qualcomm CDMA Technologies MSM....So I googled, and found another thread saying Install Windows mobile 6 center, so I did, and nothing changed.......ARGH....DIrtylarry
Do part III, but while the phone is unplugged, download and install HTC Sync, and then plug the phone back in.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Ok...I did EXACTLY what you have suggested, and in the driver information box this is what I got after the install....
USB Composite device installed successfully
USB Mass Storage Device Failed
Mytouch slide tmobil installed successful
Still a no go on the Mass storage device......hmmm.....so weird of a problem to have....I would have thought that clearing everything on the phone and going back to stock would have done the trick......any more ideas?...Thanks so much for your help.....Dirty
Have you checked in device manager on your computer to see if the mass storage device has a yellow triangle? I just went through the same thing but in reverse. My pc would see the sd card while in my phone but not through the reader. I still haven't gotten it straightened out either, just learned to live with it.
dirtylarry10 said:
Ok...I did EXACTLY what you have suggested, and in the driver information box this is what I got after the install....
USB Composite device installed successfully
USB Mass Storage Device Failed
Mytouch slide tmobil installed successful
Still a no go on the Mass storage device......hmmm.....so weird of a problem to have....I would have thought that clearing everything on the phone and going back to stock would have done the trick......any more ideas?...Thanks so much for your help.....Dirty
Click to expand...
Click to collapse
Make sure you don't have any drivers disabled. Ran into that problem with a different phone. I had one driver disabled so it wouldn't install some of the other drivers.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Ok...just checked,...no drivers disabled in device manager...has to be something wrong with phone...its a/most like the driver is missing from within the phone or something...isn't there some way to get this back to where I could root it and install a custom rom again without the USB to phone connectivity and use my card reader to get some sort of files back onto phone that way?
ok....well I re-did the whole flash process over, and I am now rooted again once more.....I dont know how or why or what...but I am now going strong again.....lol thanks for the help everyone,
I messed it up ultimately. I wanted to repartition the external sd using "aparted", instead I formated and repartitioned the internal one.
My situation now: tab doesn't boot into system, doesn't show in adb, doesn't show in flashtool (offline or online), doesn't boot to recovery, doesn't boot to download and doesn't show in windows. There's only one sign of life: when I plug it into a usb cable which is attached to my PC I get the windows "connect sound". And I get the disconnect/connect sounds when turning it off while attached to PC.
I assume that I can throw away my tab. If you know better, don't be afraid to tell me!
android404 said:
I messed it up ultimately. I wanted to repartition the external sd using "aparted", instead I formated and repartitioned the internal one.
My situation now: tab doesn't boot into system, doesn't show in adb, doesn't show in flashtool (offline or online), doesn't boot to recovery, doesn't boot to download and doesn't show in windows. There's only one sign of life: when I plug it into a usb cable which is attached to my PC I get the windows "connect sound". And I get the disconnect/connect sounds when turning it off while attached to PC.
I assume that I can throw away my tab. If you know better, don't be afraid to tell me!
Click to expand...
Click to collapse
Ouch.
You've tried all the button combos?
You could try the warranty... If they can't get into it either, then it probably won't matter if your rooted or not.
android404 said:
I messed it up ultimately. I wanted to repartition the external sd using "aparted", instead I formated and repartitioned the internal one.
My situation now: tab doesn't boot into system, doesn't show in adb, doesn't show in flashtool (offline or online), doesn't boot to recovery, doesn't boot to download and doesn't show in windows. There's only one sign of life: when I plug it into a usb cable which is attached to my PC I get the windows "connect sound". And I get the disconnect/connect sounds when turning it off while attached to PC.
I assume that I can throw away my tab. If you know better, don't be afraid to tell me!
Click to expand...
Click to collapse
When you connect to computer do you see any devices in Device Manager?
You should still be able to get into download mode and use "upgrade recovery" in lg mobile tool.
id10terror said:
When you connect to computer do you see any devices in Device Manager?
Click to expand...
Click to collapse
Hi. Actually, it does appear here, as qhsusb_dload. That must be a good sign..?
android404 said:
Hi. Actually, it does appear here, as qhsusb_dload. That must be a good sign..?
Click to expand...
Click to collapse
Good sign, yes, but will probably be difficult to recover from, might be better off just doing a warranty replacement.
Another option is to use a current version of Ubuntu or similar linux distro to see if you can access partitions from there. I remember something similar on a buddy's HTC phone a couple years back and was able to get him back up and running, so might be a similar issue here.
id10terror said:
Good sign, yes, but will probably be difficult to recover from, might be better off just doing a warranty replacement.
Another option is to use a current version of Ubuntu or similar linux distro to see if you can access partitions from there. I remember something similar on a buddy's HTC phone a couple years back and was able to get him back up and running, so might be a similar issue here.
Click to expand...
Click to collapse
Ok. I installed a virtual ubuntu and after work tomorrow i'll follow this http://forum.xda-developers.com/showthread.php?t=2582142 thread to see if it shows me anything. If so I might need halp to find the proper images to push. I found some other potenitally helpful stuff when googling qhsusb_dload. I'll see what where it takes me tomorrow. A replacement is kind of hard to get here in Norway afer my experience.
Thanks for now!
android404 said:
Ok. I installed a virtual ubuntu and after work tomorrow i'll follow this http://forum.xda-developers.com/showthread.php?t=2582142 thread to see if it shows me anything. If so I might need halp to find the proper images to push. I found some other potenitally helpful stuff when googling qhsusb_dload. I'll see what where it takes me tomorrow. A replacement is kind of hard to get here in Norway afer my experience.
Thanks for now!
Click to expand...
Click to collapse
Good find! If that works out for you, maybe you can do a How To incase anyone encounters the same issue down the road.
Let me know if you need any partitions, although you should be able to grab most of them from any of my flashable zips. Just get them from the flash folder in the zip.
Good luck and godspeed! :fingers-crossed:
id10terror said:
Good find! If that works out for you, maybe you can do a How To incase anyone encounters the same issue down the road.
Let me know if you need any partitions, although you should be able to grab most of them from any of my flashable zips. Just get them from the flash folder in the zip.
Good luck and godspeed! :fingers-crossed:
Click to expand...
Click to collapse
I think that will not work.
qhsusb_bulk is different from qhsusb_dload.
Newer qualcomm SOC has some "rescue" modes to recover fom bad flash. If the internal flash/eMMC can´t be accessed the SOC "bootROM" activates the qhsusb_dload mode. To get the device to "live" again is needed to use a qualcomm program to flash a qhsusb_bulk "driver" to the internal eMMC to activate the mass storage device...
There is a Korean Note2 qhsusb_dload topic about this here on xda... http://forum.xda-developers.com/showthread.php?t=1914359
The problem is find the correct flasher binary to upload to the SOC, the right "driver" to flash and the correct partition layout of the internal flash/eMMC.
It´s better send to warranty replace...
android404 said:
Ok. I installed a virtual ubuntu and after work tomorrow i'll follow this http://forum.xda-developers.com/showthread.php?t=2582142 thread to see if it shows me anything. If so I might need halp to find the proper images to push. I found some other potenitally helpful stuff when googling qhsusb_dload. I'll see what where it takes me tomorrow. A replacement is kind of hard to get here in Norway afer my experience.
Thanks for now!
Click to expand...
Click to collapse
Hello,
i am having the same problem here, I flashed by mistake the wrong system files for V500 instead of VK810, when i was trying to flash twrp, any fix for the QHSUSB-BULK? or did you go through the warranty?
[Q] E980 bricked - Computer says "unknown device" - Only boots into Recovery and DL
My wife somehow managed to bork her Optimus G Pro. She was running rooted stock, and the phone ended up somehow booting to CWM. She said she "picked a few selections", and the phone won't get past CWM now.
I can't do the mobile flash tool because every time I connect the phone, it somes up as Unknown Device. This is after I updated the drivers on both computers. Tried various ports & USB cables, same thing. MY E980, by the way, shows up fine in Device Manager.
I've tried restoring a previous backup, but it still boots right back to recovery. For some reason, the phone doesn't recognize the external card, or I would have tried making a backup on the other phone with the bootloader included, but I have no way of getting it onto the broken phone, unless I can push it via adb somehow.
Anyway, I appreciate any help anyone can give
ixijimixi said:
My wife somehow managed to bork her Optimus G Pro. She was running rooted stock, and the phone ended up somehow booting to CWM. She said she "picked a few selections", and the phone won't get past CWM now.
I can't do the mobile flash tool because every time I connect the phone, it somes up as Unknown Device. This is after I updated the drivers on both computers. Tried various ports & USB cables, same thing. MY E980, by the way, shows up fine in Device Manager.
I've tried restoring a previous backup, but it still boots right back to recovery. For some reason, the phone doesn't recognize the external card, or I would have tried making a backup on the other phone with the bootloader included, but I have no way of getting it onto the broken phone, unless I can push it via adb somehow.
Anyway, I appreciate any help anyone can give
Click to expand...
Click to collapse
If the message you are referring to is one that pops up using a windows computer. I have seen it most of the times I have flashed back to stock. Unknown device, device can't be recognized, something not installed, etc. Carrying on with the restore method even so has also worked every time.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
Return to stock method: http://forum.xda-developers.com/showthread.php?t=2420219
abumy said:
If the message you are referring to is one that pops up using a windows computer. I have seen it most of the times I have flashed back to stock. Unknown device, device can't be recognized, something not installed, etc. Carrying on with the restore method even so has also worked every time.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
Return to stock method: http://forum.xda-developers.com/showthread.php?t=2420219
Click to expand...
Click to collapse
Yep, that's the message. I'm running Windows 7.
I'll give it a shot when I get home, but without the device showing up in the com port section of device manager, I can't change the phone over to port 41, right?
I have a TWRP backup from my other E980 that I included the Bootloader option in the backup. Is there any way to push that to the phone using ADB?
I don't know if OP has the same problem as mine. My phone just keep boot into CWM all the time. No matter which rom I flash.
And I Finally found a method to solve this problem, please look here:
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
It salve my phone and I don't have to use the LG tools
@ixijimixi
laofan said:
I don't know if OP has the same problem as mine. My phone just keep boot into CWM all the time. No matter which rom I flash.
And I Finally found a method to solve this problem, please look here:
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
It salve my phone and I don't have to use the LG tools
@ixijimixi
Click to expand...
Click to collapse
Reading that post, it sure seems like what I'm going through. I'll have to give it a shot tonight. Either way, thanks for the response. This thing has me pulling my hair out.
ixijimixi said:
Reading that post, it sure seems like what I'm going through. I'll have to give it a shot tonight. Either way, thanks for the response. This thing has me pulling my hair out.
Click to expand...
Click to collapse
before you boot into system, make sure you already have one system installed( I did once wipe system and fogot to install a rom..)
At least that post is working for me! Now I am using TWRP,
laofan said:
before you boot into system, make sure you already have one system installed( I did once wipe system and fogot to install a rom..)
At least that post is working for me! Now I am using TWRP,
Click to expand...
Click to collapse
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...
ixijimixi said:
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...
Click to expand...
Click to collapse
Did you install LG driver in those two computer?
That post has cover issues when device is not recognized. If that doesn't help, you need to go back to stock using files in the General section
I'm also having the same problem. Can I run those adb commands on a Ubuntu machine?
ixijimixi said:
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...
Click to expand...
Click to collapse
try this one, use the TWRP method. ( I got into recovery bootloop again today, my computer could not see my phone at all. And I accidently press continue on OTA... f**k, then phone run into recovery for 2 hours.)
This method help me out even when computer could not see your device.
http://forum.xda-developers.com/showthread.php?t=2451696
laofan said:
Did you install LG driver in those two computer?
That post has cover issues when device is not recognized. If that doesn't help, you need to go back to stock using files in the General section
Click to expand...
Click to collapse
Right, but if my computer isn't connecting to my phone (except to show it as an "Unknown Device"), and ADB isn't connecting, and none of the recoveries see the ext. SD card, how do I get the files across?
laofan said:
try this one, use the TWRP method. ( I got into recovery bootloop again today, my computer could not see my phone at all. And I accidently press continue on OTA... f**k, then phone run into recovery for 2 hours.)
This method help me out even when computer could not see your device.
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Holy crap...that idea with the TWRP terminal command got me up and booting! So glad that I kept TWRP on there!
For some reason, it's still not reading either the SD card or recognizing the device on USB, but at least this is progress, and at least I can run the thing.
*update* and now it seems to be reading the SD card. At least with that and wifi, I'll be able to move files to/from the phone. I'm going to try reinstallng drivers. With all the reinstalling, uninstalling, and swearing I've done lately, I think there's a good chance that'll work.
ixijimixi said:
Holy crap...that idea with the TWRP terminal command got me up and booting! So glad that I kept TWRP on there!
For some reason, it's still not reading either the SD card or recognizing the device on USB, but at least this is progress, and at least I can run the thing.
*update* and now it seems to be reading the SD card. At least with that and wifi, I'll be able to move files to/from the phone. I'm going to try reinstallng drivers. With all the reinstalling, uninstalling, and swearing I've done lately, I think there's a good chance that'll work.
Click to expand...
Click to collapse
well You should owe me 8 thanks hit for saving your phone..:fingers-crossed: LOL
I would also recommend reinstall drivers, then reboot computer( it is important), and try different USB ports on your PC. my computer just won't recongize my phone on one port, but it does on the other. God knows why...
laofan said:
well You should owe me 8 thanks hit for saving your phone..:fingers-crossed: LOL
I would also recommend reinstall drivers, then reboot computer( it is important), and try different USB ports on your PC. my computer just won't recongize my phone on one port, but it does on the other. God knows why...
Click to expand...
Click to collapse
Heheheh, yeah, I was going to, but then I read your previous sig. Perfectly happy to ignore.
My google-fu failed me major league on this mess. I'm just hoping it's not a busted USB port on the phone.
ixijimixi said:
Heheheh, yeah, I was going to, but then I read your previous sig. Perfectly happy to ignore.
My google-fu failed me major league on this mess. I'm just hoping it's not a busted USB port on the phone.
Click to expand...
Click to collapse
Try different USB ports on PC. When my PC could not see my phone, I also panic and thinking that the USB port on the phone goes wrong.
Then I switch the port which my mouse is usually hook up. Bang! Windows is installing driver and few seconds Iater I was accessing the files on the phone.
Just give it a try.
My signature is just for fun...Emm, I should change it to " hit thanks twice if you like my post "..
laofan said:
Try different USB ports on PC. When my PC could not see my phone, I also panic and thinking that the USB port on the phone goes wrong.
Then I switch the port which my mouse is usually hook up. Bang! Windows is installing driver and few seconds Iater I was accessing the files on the phone.
Just give it a try..
Click to expand...
Click to collapse
Well, I'm out of ports to try on my work computer. I'll try on my home computer later on. It didn't read it last night...but then again, the phone wasn't booting last night either
My signature is just for fun...Emm, I should change it to " hit thanks twice if you like my post "..
Click to expand...
Click to collapse
"Hit the thanks button like a rat pressing a lever for a nugget of food, thanks"
So just as the title says, but here's a little back story (might help).
I'm trying to help out a friend with his Bell Mobility i747M. He wanted to try out Lollipop, so I looked into it and said I could do it. Last I even touched his phone was quite a while ago when he wanted me to flash CM11, back when KK was still pretty new. So it's been over a year. I flashed CWM back then, got the ROM installed, and everything has been good ever since. Fast forward to now, and he wants to try Lollipop. I figured the first thing I should do is update the bootloader/radio, which went perfectly fine (after some researching, I chose 4.3/MK5 for his i747M). I tested them by booting back to the ROM and checking About Phone - everything was good. So I booted back to the old version of CWM, and thought it would be a good idea to get a more modern recovery. CWM or TWRP didn't matter, just as long as it was more up to date (I thought it might help with Lollipop compatibility). So I decided on TWRP, and I got the latest version (2.8.4.0 as of now) and flashed it. Successfully flashed, then rebooted recovery. TWRP is there and working. Great. Next step... I had the Lollipop ROM and Gapps already downloaded and ready to go, so in TWRP, I proceeded to wipe everything (system, data, cache, internal sd).
Uh oh... Half way through wiping, the phone reboots itself! Now there's no ROM, so naturally it has nothing to boot to. Try going back to TWRP, and I see the splash screen again. OK, false alarm... Well, not really... Because now it just reboots itself after the splash screen, every time. Can't get into TWRP no matter what! I can access download mode, but Odin doesn't recognize the phone. Yes, I have the drivers. In fact, the device isn't detected by Windows at all.
So here we are. Download mode boots, but Odin doesn't work because there's no communication through USB at all. There's no ROM on the phone because it was wiped. And TWRP won't boot beyond the splash screen.... Now what?? I tried the 80MB MK5 debricking .img on a 64GB microSD. It does nothing - besides, USB isn't reading anyway, so it's not like I can proceed with Odin.
I'm at a stalemate here... Any suggestions?
My friend's gonna kill me if I killed his phone I'm pretty experienced with several devices, but not much with Samsung. I've never seen anything like this happen before...
When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?
audit13 said:
When connecting to the computer, have you tried different USB 2.0 ports and USB cables? Have you tried different computers? Different operating systems?
Is the phone recognized using adb or fastboot commands?
Click to expand...
Click to collapse
Yeah, I figured that would be the case. Just about done downloading Ubuntu which I'll boot from USB. I'll post back with results once that's ready. I should have it booted within 10 minutes. Once I get there and verify the phone connects, what would be my next step? Should I try flashing stock 4.3 first?
I would confirm the bootloader that is on the phone before flashing anything from sammobile.com.
You may be able to use fastboot commands to get the information by typing fastboot getvar all.
OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.
Bloodflame said:
OK, in Linux now. ADB/fastboot won't connect. Tried different USB ports and cables, ones that I know work. No luck...
The only thing I can boot to in the phone is Download mode, so that's where I'm trying from.
For the record, ADB picks up my Nexus 5, so I know it's all set up right.
I'm gonna retry the debrick img, using dd to write it this time.
Click to expand...
Click to collapse
No luck. wrote to the SD successfully, and it just boots to download mode. Nothing else.
ADB and fastboot still do nothing
Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?
audit13 said:
Maybe the phone's USB port is flaky?
Have you tried Kies to see if it recognizes the phone?
Click to expand...
Click to collapse
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Edit: Downloading Heimdall (Linux-compatible Odin)...
Bloodflame said:
I don't have Kies, but I'm doubting that would work anyway. There's absolutely no communication between the computer and phone. Nothing happens when I plug it in. No sound, no indication anything was even plugged in. Running lsusb in a terminal doesn't show the phone either.
Click to expand...
Click to collapse
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?
audit13 said:
Okay, forget kies. Sounds like a USB port issue. Does the phone start charging when connected to a power source?
Click to expand...
Click to collapse
Plugging into the wall makes the phone vibrate every couple of seconds, but nothing shows up on screen, and there's no indicator light.
The vibrations lead me to believe it's detecting something, but no indicator light worries me (unless that's just because there's no kernel)
The red light does come on if I plug it in without the battery.
Heimdall fails to detect the device as well (no surprise there)
If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.
audit13 said:
If the phone was bricked, it would usually be recognized as a some sort of device under Windows' device manager which leads me to conclude that it is a USB port issue.
Click to expand...
Click to collapse
I agree that it is weird, because it's not coming up as a device at all, in either Windows or Linux, yet it does receive power.
I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?
audit13 said:
I'm guessing here but it appears to me that the only left to try is a debrick image. Is it possible the battery is drained and needs to be charged?
Click to expand...
Click to collapse
The debrick image is what I've been trying. It's on a 64GB microSD. And I made a new one from Linux a few minutes ago (booted back to Windows now).
The battery was about 80% before all this started, and the phone powers on without being plugged in, so I doubt it's the battery.
Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.
audit13 said:
Maybe you need a different SD card? Based on posts I have seen, it seems that certain brand/size combinations work while others don't.
Click to expand...
Click to collapse
I only have one card over 16gb...
Either way, I still have the USB problem. I'll need USB to flash with Odin. The debrick card only seems useful when Download mode isn't working, but that part works fine on the phone, even without the debrick card. My problem is with recovery. If I could run that from the SD, I think I would be fine - just flash a ROM. But I'm not finding anything for that (not surprised).
I thought it could potentially be a corrupt driver, so I tried using USBDeview to uninstall all disconnected devices. I tested it with a portable hard drive, which indeed had to reinstall after. So the program works as intended. However, the phone still isn't detected when I plug it in. No sound, no notification saying it's installing or install failed - absolutely nothing. Power goes to the phone through USB, with multiple cables and USB ports. Just no data connection.
I'm starting to think there's just nothing I can do...
The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.
audit13 said:
The phone may need a USB port replacement. I know of no way to push recovery to the phone from as SD card without USB capabilities.
Click to expand...
Click to collapse
Yeah, that's what I'm thinking. Found this, and it's cheap enough... But that shipping!
You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill
audit13 said:
You'd be better off getting it from China with free shipping. The problem is the amount of time required to get the part.
Maybe contact a cell repair shop to see how much it would cost to have them replace it. Soldering is not my strongest skill
Click to expand...
Click to collapse
Yeah, doesn't look easy. I already tore down to here, and visibily, it looks OK. I'm not so sure about soldering either :silly:
I appreciate your assistance.