Related
All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick
hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.
thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.
pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.
Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.
Howdy y'all,
So I was rooting and flashing and when I tried to flash after successfully rooting the device, I went to wipe everything in TWRP and then flash another ROM. Well, something happened and it gave me an error saying it could not wipe (I think it was OTG something something, it's been 2 weeks now since I did this), and now it won't allow me to transfer ANYTHING from the computer to the device. It will not allow me to create folders, nothing. I have uninstalled the drivers, installed the drivers and tried SO many drivers. Anyone able to provide me a suggestion? The odd thing is on the device itself, I can create folders and everything, but when it connects, eventually, I can open the device from my computer, BUT when I attempt to create a folder, the PC gives me an error dialog saying that the device is not there anymore.
Any help would be greatly appreciated!
Thanks!
kassem277 said:
Howdy y'all,
So I was rooting and flashing and when I tried to flash after successfully rooting the device, I went to wipe everything in TWRP and then flash another ROM. Well, something happened and it gave me an error saying it could not wipe (I think it was OTG something something, it's been 2 weeks now since I did this), and now it won't allow me to transfer ANYTHING from the computer to the device. It will not allow me to create folders, nothing. I have uninstalled the drivers, installed the drivers and tried SO many drivers. Anyone able to provide me a suggestion? The odd thing is on the device itself, I can create folders and everything, but when it connects, eventually, I can open the device from my computer, BUT when I attempt to create a folder, the PC gives me an error dialog saying that the device is not there anymore.
Any help would be greatly appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried using ADB push to get a new rom onto the device? Also I'd do a permission repair
Edit: As a side note, I don't think it's possible that you did actual damage to your device. It's probably just the software that's messed up. If you want a sure way to fix it, try downloading and flashing the stock factory image.
Funzo22 said:
Have you tried using ADB push to get a new rom onto the device? Also I'd do a permission repair
Edit: As a side note, I don't think it's possible that you did actual damage to your device. It's probably just the software that's messed up. If you want a sure way to fix it, try downloading and flashing the stock factory image.
Click to expand...
Click to collapse
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?
kassem277 said:
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?
Click to expand...
Click to collapse
Is it possible for you to try with a different computer?
Funzo22 said:
Is it possible for you to try with a different computer?
Click to expand...
Click to collapse
Unfortunately no and not for a very long time. Shoot.
kassem277 said:
Thanks so much for the reply. I just finished doing a complete stock re-image of the original bootloader and OS, but I'm still getting the same error message. I'll attach an image below of the error I keep getting.
Any more suggestions?
Click to expand...
Click to collapse
Have you done a wipe data factory reset?
It wasn't clear from what you described.
Bootloadeer wouldn't help and neither would ROM as this problem has to do with /data
sfhub said:
Have you done a wipe data factory reset?
It wasn't clear from what you described.
Bootloadeer wouldn't help and neither would ROM as this problem has to do with /data
Click to expand...
Click to collapse
Sorry about the lack of clarity. I have wiped multiple times, cleared all caches, dalvik, etc. I have installed and uninstalled ALL devices from USBDeview pertinent to anything ADB or android related.
kassem277 said:
Sorry about the lack of clarity. I have wiped multiple times, cleared all caches, dalvik, etc. I have installed and uninstalled ALL devices from USBDeview pertinent to anything ADB or android related.
Click to expand...
Click to collapse
Have you rebooted your PC?
Have you reconfirmed you are using mtp rather than ptp?
Does your /sdcard show more directories than dcim and pictures when viewed in adb shell?
sfhub said:
Have you rebooted your PC?
Have you reconfirmed you are using mtp rather than ptp?
Does your /sdcard show more directories than dcim and pictures when viewed in adb shell?
Click to expand...
Click to collapse
I have rebooted multiple times
I am in debugging mode as well as in ptp mode and my sdcard shows that I do have many folders there, however in my computer it is only showing DCIM and pictures.
kassem277 said:
I am in debugging mode as well as in ptp mode and my sdcard shows that I do have many folders there, however in my computer it is only showing DCIM and pictures.
Click to expand...
Click to collapse
That's your problem right there. PTP mode is camera mode, so you only get access to a couple of directories. Switch to MTP mode (menu under Settings / Storage).
tni.andro said:
That's your problem right there. PTP mode is camera mode, so you only get access to a couple of directories. Switch to MTP mode (menu under Settings / Storage).
Click to expand...
Click to collapse
I've tried MTP mode before and I get nothing. In fact the computer doesn't recognize the tablet is there. It's odd b/c I have done EVERYTHING I can think of and read about to install drivers (multiple kinds, like PDA, android, RAW, etc) and uninstall drivers. It sounds like a driver issue but I don't think it is.
EDIT: ok so after switching to MTP mode on the tablet, I went to device manager and uninstalled the "portable ADP drivers" as some people were saying they had issues that were similar to mine (but not exactly) here (http://forum.xda-developers.com/showthread.php?t=2380978&page=1).
After doing so, I unplugged and re-plugged the N7 back in and had it re-install the drivers from the Google USB drivers that I downloaded onto my desktop. That allowed me to get it to work and access the internal SD card on the device. BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures. Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.
kassem277 said:
BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures. Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.
Click to expand...
Click to collapse
That is how ptp mode is supposed to work.
That is why people prefer mtp mode.
kassem277 said:
BUT, when I go back into the PTP mode (camera) mode, I still have the same issue where I cannot creat subdirectories, transfer anything to the device AND I cannot see any directories except for DCIM and pictures.
Click to expand...
Click to collapse
Like I said, that's what you get in PTP mode. You are able to write to those 2 directories though (not the root directory).
Really weird. Both modes obviously worked before I rooted it. Now that I have unrooted and gone back to bare bone stock I am still not getting it to work.
Click to expand...
Click to collapse
No way. PTP mode is restricted on purpose. Here is the commit:
https://android.googlesource.com/pl...er/+/1e950b8090d90bbf92e528a974ecb8c5c48dff84
Thanks guys. I appreciate all the continued help and patience. Now that I went back and thought about it, I was only transferring images WHEN it was working before. It is all good now that my silly drivers were all sorted out. Really odd how the drivers just took a crap on me like that. Weird. All is well now though and I can get back to studying my PDF's for school.
Thanks again y'all!
Thanks guys. I appreciate all the continued help and patience. Now that I went back and thought about it, I was only transferring images WHEN it was working before. It is all good now that my silly drivers were all sorted out. Really odd how the drivers just took a crap on me like that. Weird. All is well now though and I can get back to studying my PDF's for school.
Thanks again y'all!
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.
[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"
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
slev!n said:
Hello guys,
Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
knpk13 said:
That's weird. Sounds like your screen (if not more parts) died. Hardware issue? Water damage? Might be better to contact a repair center since if you can't even access recovery I doubt the problem is related to LOS. Never happened on my 3T over the 4 years I've had it, though it's had its fair share of damage.
Click to expand...
Click to collapse
slev!n said:
But before my restart I could use the screen it just looks like something in the system doesn't work: could type on apps and settings, it just doesn't open or pop back. And the charging led is not part of the screen unit as I know.... If I could take out the battery I would do it. It often works in other phones. But I don't have tools here for my 3T. :/
Click to expand...
Click to collapse
slev!n said:
Hello guys,
I've got an issue and don't know if it belongs to the build or not. I'm on the last build with my 3T and today after charging my phone I couldn't turn on WiFi or start any app. It just didn't open. So I restated my phone but it never booted. Screen unit is completely dead. It even doesn't show a charging led anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect to the computer windows registers my phone by playing the 'connected sound'. But nothing more. Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
Sounds to me like an hardware error involving (but not necessarily limited to) emmc access. That would explain, why the parts still in ram (like homescreen) were still working but apps won't start anymore, as well as the blank screen on device startup (even the logo needs emmc access to read the logo partition).
Try unbricking (I'm afraid your pc won't find the device, if my guess is correct), if that fails: rma or repair center.
slev!n said:
Has anyone any idea or know where I can discuss my issue? Thanks a lot!
Click to expand...
Click to collapse
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
150208 said:
here
You need to be more spesific about the connected sounds, does it shows up on device manager or else, in detail (with SS/photos etc to prevent misjudge)
Click to expand...
Click to collapse
Thanks, I'll create a post there. Just one more post here:
I used this phone just carefully at home as a media device. So this brick came totally out of nowhere. When I connect my bricked 3T now to my computer it makes the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more pop up again.
slev!n said:
I'll create a post there.
Click to expand...
Click to collapse
When you've created that post ask the moderators to move this complete conversation from this thread to the newly created on in the help forum, please. This helps to keep this thread readable and searcheble.
For your trouble: if you can't boot rom, recovery nor fastboot mode, it doesn't make sense to debug the usb connection: what should the pc connect to if none of the three is bootable? There is just nothing up to connect to. That's why I recommended unbrick tool - if that fails rma or go to a repair center.
Hello guys,
I'm using my 3T carefully as a media device just at home. But suddenly I couldn't control my system anymore. I could swipe and open settings, but couldn't turn on WiFi or start any app. So I restarted my phone but it never booted. Screen is completely black and even charging leds doesn't work anymore. I can't access TWRP recovery. I used the button combinations ... Nothing! But when I connect my phone to my computer windows plays the typical sound like when you plug in an USB stick. Windows sayed once that the connected device is buggy and cannot be detected. Nothing more. When I reconnect no more message or pop up again.
Has anyone any idea? Thanks a lot!
Post SS of the device manager after connecting the phone to the PC
150208 said:
Post SS of the device manager after connecting the phone to the PC
Click to expand...
Click to collapse
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
@slev!n: please ask the moderators to move the existing conversation to thos from the los16 thread here. If all postings have moved, ask the moderators to move this thread from op3/help to op3t/help.
@nvertigo67 I wanted to do so and was searching how to contact moderators but couldn't find it in my XDA app. Maybe someone can give me a hint? I'm kind of new on xda... Thanks!
@150208 And as I wrote: it's not possible to get any kind of message on windows anymore. Just the sound appears when I connect and disconnect.
@nvertigo67 I was also following your advice to use the unbrick tool. I followed the steps on oneplus forum:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
When it comes to the integrity check windows doesn't accept "TESTSIGNING ON". And so windows doesn't recognise my phone in the device manager for the next steps.
And I guess RMA or repair centres are super expensive. I don't know if it's worth it? I thought about buying a device with a broken screen on eBay and try to change the motherboard...
Log in with a web browser locate each posting of the comversation. For each posting in question use the little triangle icon at the botom on the left side, report each posting, set non-urgent and pit the link of this thread together with something like "Please move this posting to the linked thread, thanx in advance".
For disabling driver signature enforcement try method 2. from this post: http://maxedtech.com/about-testmode/
Most of tbe time xda postings are more reliable and more current then the Oneplus forums: https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722, https://forum.xda-developers.com/oneplus-3/how-to/op3-collection-unbrick-tools-t3896722
slev!n said:
[MENTION=4405529]i thought about buying a device with a broken screen on eBay and try to change the motherboard...
Click to expand...
Click to collapse
If you already have a thought why do you keep asked here though? If you want another possible solution, at least put an effort to provide the information needed when asked by the one who tried to help you
I'm not into a guessing games, so i'm out
nvertigo67 said:
It doesn't make sense to debug the pc conmection: if neither recovery, fastboot mode nor rom is bootable, there is nothing up and running the pc can connect to (maybe unbrick tool can still access the msm hardware directly, but that's not sure - confirmation is still missing from @slev!n). I'm writing this the second time.
If none of recovery, fastboot mode nor rom is bootable, the last resource before rma or repair center is unbrick tool. I'm writing this the third time!
Click to expand...
Click to collapse
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
If it's hw problem, i'll try not to jump on MB conclussion yet, since there are still another possible reason
When talking about MSM, you need to make sure it's available first on the device manager
Otherwise, it's a waste of data for downloading the tool in these human malware days
Oh yes, the msm guide is quite lag behind. You don't need to boot into test mode anymore with the current driver for qualcomm
I flashed a lot qualcomm devices with w10 without the need to boot into test mode
150208 said:
There are 2 possible reason when the phone is not detected by the computer, driver or hw problem.
To know it i need to look at the device manager status
Click to expand...
Click to collapse
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
For the costs of rma: maybe it's expensive - maybe oneplus will be obliging... Since you don't relay on the device as your daily driver, you can ask for an estimate of costs - so you can decide if it's worth the costs.
nvertigo67 said:
True, if only "win is not detecting the device" is known. Since we know much more (neither rom, recovery nor fastboot mode are bootable), the debugging of the usb driver doesn't make sense. The msm tool uses it's own drivers to detect the hardware BEFORE one of the three is booted. If the msm tool has unbricked the device and booting recovery, rom and/or fastboot, you can start debugging the "nprmal" qc usb drivers, if still necessary.
Click to expand...
Click to collapse
Wait, I fail to see your explanation in line with mine. I want to start debug it on the windows side, but you seems to see it on the phone side.
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
150208 said:
Do you realize there are cases where everything is black/nothing responding but it's still detected by computer? That when emmc is corrupt, but repairable if you format it.
Click to expand...
Click to collapse
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc. In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side. Once this is fixed (at least fastboot mode is up again) you can utilize the "normal" usb connection again.
What do you want to do with the usb connection, if neither fastboot mode nor recovery is up amd running? What is your suggested next step, if the device is recognized? What should the pc recognize if neither fastboot nor adb os an option? Which command or procedure will fix the emmc?
nvertigo67 said:
If neither fastboot mode nor recovery is bootable, you need the msm interface to refprmat somethimg on emmc.
Click to expand...
Click to collapse
Yes, there are other tools but i'm not gonna bother since it's paid
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect. There are 4 status when a device plugged into the pc.
1. detected and driver is loaded
2. detected and driver isn't loaded
3. detected but not recognized
4. no sign at all
1 and 2 is sw problem, 3 and 4 is hw problem
In order for MSM to do it's job, you need to have either problem no 1 or 2 with qualcomm qloader 9008 driver already or later detected in devmanager
So it's important to know the driver status
OP states there was sounds coming then nothing, which mean it's either 2 or 3, more like 3 but again i repeating myself i don't like guessing games
I don't understand the part why you're explaining/asking about fastboot recovery or etc, his phone is on dead state, nothing-literally-no sign of life unless he plug it to the pc and then it making sounds for the first time,
Why do you even bother thinking about it?
nvertigo67 said:
Which command or procedure will fix the emmc?
Click to expand...
Click to collapse
No procedure will fixed his phone since there are no enough information
I think your other question should be already answered. If else, i don't know what to say anymore.
150208 said:
nvertigo67 said:
In other words: if there's no recovery nor fastboot, you can't utilize adb or fastboot to reformat or to fix the partition table. You need something to connect to to do the fixing, but without recovery or fastboot, there is nothing adb or fastboot can conmect to, no matter of the driver status on the pc/win side.
Click to expand...
Click to collapse
This is the part where you're incorrect.
Click to expand...
Click to collapse
If so, please explain how you can format a partition or fix the partition table if neither fastboot mode nor recovery (or a rooted system for that matter) is bootable.
@slev!n: please give a screenshot of the device manager to @150208. I'm too curious to learn how to fix a broken emmc without recovery nor fastboot mode.
Thank you so far!
I dont want to bother someone. Just thinking about further options thats why I wrote my thought about replacing the motherboard down.
I 'm in test mode now and I did this:
"Step 4 :- Press the power button for 40 seconds to turn off the phone.
Step 5 :- Press only volume up button for a few seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB (under COMs and Ports)]."
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
slev!n said:
But no device is listet in my device manager. But in msmtool my phone is connected. Does it mean I cann't continue with this tool somehow?
Click to expand...
Click to collapse
The pic is from msm tool, not the device manager. No unknown device in device manager?