Related
Hey! I'm not completely new at this, I have a little knowledge as regards to rooting and and tweaking different things. But I'm having an issue that I just don't understand how to fix, and I can't find any help on google. So I came here.
BTW, I have Windows XP 32bit.
I'm trying to install the ADB files so the computer can recognize the phone. Before Ive done anything(nothing installed or changed), I can plug my phone into the computer and the phone gives me the option to charge, sync, use as disc drive, or internet sharing. So, I don't know if maybe thats all I need.
I downloaded the adb files for windows from here http:/ /htcevohacks . com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/. I hope its not a vista/win 7 file...
I installed the correct "SDK platform Android 2.1 AP17" and "usb driver revision 3" as the instructions read. I shut the phone off and boot into recovery mode, and then plug the USB in. Nothing happens. Nothing on the computer or the phone change. I don't find any "ADB" in the device manager, and no window pops up asking about updating drivers. I do exactly as the instructions on that site say, but nothing happens.
If the phone is on normally and in "Debugging Mode", I can plug the phone in and the Device Manager shows the "ADB". Also, the window pops up to ask about updating drivers. So I've tried going through both; I specify a location, which for me is c:\android-sdk-windows\usb_driver. It searches for a few seconds, and then says it cant find the right driver for my device.
I really want to start doing some things with this phone, but im stuck! Any help would be greatly appreciated.
read this whole thread
that should help. hopefully
and I think I've just recently read that its not really necessary to install the adb files?
timothydonohue said:
read this whole thread
that should help. hopefully
Click to expand...
Click to collapse
thanks, I'll take a look at it now!
Hello,
I have tried attempted to root and flash a new ROM on my phone and now I seem to have lost SD and USB support. it does not recognize any of the SD cards i put it (doesn't realize theres an SD card inside) and does not recognize any USB plugged in.
I have HBOOT .80 and i THINK i got the root correct (lotsa problems along the way so i'm not sure), but i was able to flash a ROM (NexTSENSE) so i think it worked. now, i saw a thread about fixing USB support but that required SD support. and reading that made me feel like i was royally screwed. in any case, any suggestions? I think USB support is still kinda there since I can get it to recognize it in the boot menu. but when i try to do it in recovery and use the flash rom .bat, it says device not found.
it would seem that the main concern right now is that i can't get it to see my SD cards. any of them, even after reformats and whatnot.
i can't connect to HTC Sync or anything of the of the sort. usually when i charge the phone, you get the charging notification but i don't even get that now. sounds like a driver problem but i can't see what is wrong. my computer doesn't even recognize the phone as a device every now and then
Hope i provided sufficient information. New to android scene so don't be too hard on me please =O but yea, any suggestions are welcome. thanks in advance
edit: usb support... ever so slightly back. aka, it charges now. probably was drivers on my lappy getting funny after moving between bootloader and recovery and all that fun stuff
You have the usb brick issue. Check out the thread on that. Also once you are up and running again, root using unrevoked or the fake flash method. All information is available in the dev forum.
ok, i've done some reading and this is what i've found so far. my phone is stuck in USB debug hence no USB support and somewhere along the way, SD support was disabled. from what i see, the fix is to
first:
reload the step1 of root to get back to 1.15 and basic root access.
second:
from there, i can re-enable SD support using the command:
fastboot oem enableqxdm 0
third:
apply USB-Brick fix found in post 1 of thread
and then i should be able to reload ROMs as usual. is this correct?
and where exactly do i put in the command to re-enable SD support? this is what has be confused right now. along with the commands for the USB fix
i am using the tinycore method so i just have the step1.sh. and then in the same console, can i enter that command? should i do it after a reboot? or load back into bootloader to do it. (bootloader or fastloader)
OOOOK. sorry about the continuous posts. putting new info up so it isn't exactly a bump right?
in any case, i used the androidSDK tools and ran the fastboot from there and i think i re-enabled my SD correctly. i was then able to run the USB-brick fix found on modaco forums. all done and done. nowww, since i just went through half the root process (step1.sh with tinycore), do i need to finish it? or since i had already rooted before, is it all done now?
I'm not 100% sure about that as I haven't had to fix the usb brick for ages now!
Download and install titanium backup from the market. If it works fine, then you are rooted. If not, root woth unrEVOked or fakeflash.
All the older root methods that require usb during the root process leave you open to the usb brick again.
Hi fatpandas..
Is your phone ok now? Actually my phone also have a problem like yours last week..until now,i can't fix it..if now your phone ok,can u share with me..thnks in advance..
@csyrix
sorry to hear about your situation. after just being there, i can tell how horrible it is. good news is, if you really have the same problem, then it is definitely fixable.
now, i don't know what method you used to flash yours the first time but from what i've seen, they're mostly the same. what you wanna do first is do that step1 thing where you have a temporary ROM installed. (1.15?) same process as usual.
then you'll need to run 'fastboot oem enableqxdm 0' with phone plugged in while in FASTBOOT (back button + power button thing)
in case you don't know where to put that in, you wanna run that in your command prompt (computer) while operating in the tools folder of the android SDK. (thank god for my limited computer knowledge cuz all the instructions i found just say, "run this command" and like hell if most know how/where)
in any case, the end result will be you having completed step1 and having re-enabled SD support. then turn off phone.
then get the fix from this thread
move that to your SD card (micro SD adapter) and turn back on your phone into bootloader. go to the recovery menu and hold volume up + power to bring up menu and hit the apply: update.zip.
then all should be well. i then moved on to step2 to make sure i had rooted properly. may not be necessary but i remember reading that rooting a rooted device isn't a problem so i just felt the need to do it to be safe.
that should be it. the link provided actually has all the instructions anyways (i hope mine are a bit more clear), but if not, that link should be able to fill in the holes. g'luck sir
Hi and thanks for taking the time to read this
My brother tried to do the update of his nexus through the phone download (not through the sd card or connecting to a computer). Since this it will not start up and if i go to download mode it says that it is downloading constantly (have left for hours).
I can make it to the clockworkmod recovery v6.0.1.0 but unfortunately my brother didnt make a backup before trying to update to 4.2 jellybean.
The unfortunate part of this equation is that i cant access the phone via usb as the drivers wont install and the phone doesnt have an sd card slot except the sim card slot. So placing the correct files on the phone is proving too hard for me to complete.
Sorry if this situation has been covered before but i have searched for about 1.5 hours now to no avail. I would very much appreciate if someone can take me through how to get this phone working in any way possible (i dont care if he loses all data and goes back to stock).
Regards
Sam from New Zealand
samakbuchanan said:
Hi and thanks for taking the time to read this
My brother tried to do the update of his nexus through the phone download (not through the sd card or connecting to a computer). Since this it will not start up and if i go to download mode it says that it is downloading constantly (have left for hours).
I can make it to the clockworkmod recovery v6.0.1.0 but unfortunately my brother didnt make a backup before trying to update to 4.2 jellybean.
The unfortunate part of this equation is that i cant access the phone via usb as the drivers wont install and the phone doesnt have an sd card slot except the sim card slot. So placing the correct files on the phone is proving too hard for me to complete.
Sorry if this situation has been covered before but i have searched for about 1.5 hours now to no avail. I would very much appreciate if someone can take me through how to get this phone working in any way possible (i dont care if he loses all data and goes back to stock).
Regards
Sam from New Zealand
Click to expand...
Click to collapse
CWM recovery offers the ADB interface. I would:
1. get the naked driver package (see Efrant's guide)
2. boot device into recovery and connect usb cable
3. open windows device manager, find your device and manually update the driver
4. use adb to backup the /sdcard to your computer
5. flash 4.2 stock images using fastboot
6. done
Petrovski80 said:
CWM recovery offers the ADB interface. I would:
1. get the naked driver package (see Efrant's guide)
2. boot device into recovery and connect usb cable
3. open windows device manager, find your device and manually update the driver
4. use adb to backup the /sdcard to your computer
5. flash 4.2 stock images using fastboot
6. done
Click to expand...
Click to collapse
op, if you just want to get the device to working state again, and dont care about any data:
1. get the naked driver package (see Efrant's guide)
2. boot device into bootloader and connect usb cable
3. open windows device manager, find your device and manually update the driver
5. flash 4.2 stock images using fastboot
step 3 is the same, the same procedure, the same driver; windows is dumb so you have to tell it again when device is in bootloader (which, btw, is NOT the same as download mode).
Hi and thank you for the replies.
I have downloaded the naked driver but cant get it to work. I have followed the steps to make it work but i get to the device manager and there is no option for uninstalling current driver (as it has none currently). It only has update driver software (which if i use windows to search for it cant find any) and properties. The Galaxy Nexus icon in the device manager has the yellow exclamation mark sign on it. I can
When i try to manually find the naked driver it comes up with the following error
Windows found driver software for your device but encountered an error while attempting to install it.
Google Galaxy Nexus ADB Interface
Access Denied.
Where to from here lads, i appreciate the input
samakbuchanan said:
Hi and thank you for the replies.
I have downloaded the naked driver but cant get it to work. I have followed the steps to make it work but i get to the device manager and there is no option for uninstalling current driver (as it has none currently). It only has update driver software (which if i use windows to search for it cant find any) and properties. The Galaxy Nexus icon in the device manager has the yellow exclamation mark sign on it. I can
When i try to manually find the naked driver it comes up with the following error
Windows found driver software for your device but encountered an error while attempting to install it.
Google Galaxy Nexus ADB Interface
Access Denied.
Where to from here lads, i appreciate the input
Click to expand...
Click to collapse
if you're using windows 7, i read something about you need to disable windows digital driver signature check, or something in those lines.
can't help any further on that subject, since i'm a Linux user (Windows knowledge is very limited) and also that is an operating system's issue and would be better discussed in a Windows forum, IMO.
bk201doesntexist said:
if you're using windows 7, i read something about you need to disable windows digital driver signature check, or something in those lines.
can't help any further on that subject, since i'm a Linux user (Windows knowledge is very limited) and also that is an operating system's issue and would be better discussed in a Windows forum, IMO.
Click to expand...
Click to collapse
Thank you for another helpful reply! Yes i am using windows 7 - i will try to perform the task now - results soon. In the meantime if anyone else knows instructions on how to do this i would love to hear
I am at work and dont have administrator settings on windows 7 so i went to an older computer and started fastboot.exe. I went to recover and there was the IP address of the computer went to that and recovered. From there i went to reboot and now i am just getting a Google in the middle of the phone (as before). I will wait some time to see if it will start up now. If not what is my plan?
So i havent got any closer to having a usable phone.
Im up to this step:
"flash 4.2 stock images using fastboot" how do i do this? i have fastboot and i have the stock image
samakbuchanan said:
So i havent got any closer to having a usable phone.
Im up to this step:
"flash 4.2 stock images using fastboot" how do i do this? i have fastboot and i have the stock image
Click to expand...
Click to collapse
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40C)
Thanks for that i had since found that and have printed it and will work through each step methodically. I have the stock image on download.
I have spent the best part of my working day on it now. Fingers crossed it all works out.
Thanks to all who have helped me through this far
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?
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.