I'm trying to install driver for my X9006
But my PC recognizes a drive which is "corrupted", Windows can't open the drive, so I can't install driver.
Instead my phone is recognized as a "portable media player". There's no green Oppo logo on the DVD drive which is supposed to appear.
I cannot flash anything because I'm stuck on stock recovery. I tried to flash stock ColorOS 1.2.0i but installation failed halfway. Same goes for ColorOS 2.0.0i beta. All failed. I want to wipe the whole thing clean.
So I'm thinking it might be infected perhaps? The only thing I could think of was, I rooted it using Root Genius. It installed Kinguser, which is a fishy app. Granted me root access but God knows what it did to my phone (you know... Chinese and their hackers and malwares..)
Help! I run windows 7 64-bit btw.
ianbong said:
I'm trying to install driver for my X9006
But my PC recognizes a drive which is "corrupted", Windows can't open the drive, so I can't install driver.
Instead my phone is recognized as a "portable media player". In short, my PC doesn't recognise the phone.
I cannot flash anything because I'm stuck on stock recovery. I tried to flash stock ColorOS 1.2.0i but installation failed halfway. Same goes for ColorOS 2.0.0i beta. All failed. I want to wipe the whole thing clean.
So I'm thinking it might be infected perhaps? The only thing I could think of was, I rooted it using Root Genius. It installed Kinguser, which is a fishy app. Granted me root access but God knows what it did to my phone (you know... Chinese and their hackers and malwares..)
Help! I run windows 7 64-bit btw.
Click to expand...
Click to collapse
Well your device is a portable media player in its own way....is it not? Mine is also recognized by my computer that way.
The driver should appear where your dvd drive is. It'll have the green oppo logo.
Can you access you phone when you plug it in? When you click on the phone can you see your internal storage/sd card...if so it is being recognized.
Have you installed any third party roms or recoveries? I'm assuming not since you say you are stuck on stock recovery.
Try googling the stock firmware...or go to oppoforums website and go down to colorOS and you can find downloads there...I know versions 1.2.3 and above failed halfway through for me too...but wiping and using the original stock firmware and then upgrading via OTA worked fine...If that fails as well...you could try reinstalling the recovery as well..
Salvia128 said:
Well your device is a portable media player in its own way....is it not? Mine is also recognized by my computer that way.
The driver should appear where your dvd drive is. It'll have the green oppo logo.
Can you access you phone when you plug it in? When you click on the phone can you see your internal storage/sd card...if so it is being recognized.
Have you installed any third party roms or recoveries? I'm assuming not since you say you are stuck on stock recovery.
Try googling the stock firmware...or go to oppoforums website and go down to colorOS and you can find downloads there...I know versions 1.2.3 and above failed halfway through for me too...but wiping and using the original stock firmware and then upgrading via OTA worked fine...If that fails as well...you could try reinstalling the recovery as well..
Click to expand...
Click to collapse
I can access my phone alright. Everything is there, in the internal storage.
It's just that the driver doesn't appear where my dvd drive is. It's driving me nuts. No green oppo logo, nada.. and clicking on the dvd drive that appears when I plug in the phone makes windows come up with an error message that says something like "windows cannot access this drive"
ianbong said:
I can access my phone alright. Everything is there, in the internal storage.
It's just that the driver doesn't appear where my dvd drive is. It's driving me nuts. No green oppo logo, nada.. and clicking on the dvd drive that appears when I plug in the phone makes windows come up with an error message that says something like "windows cannot access this drive"
Click to expand...
Click to collapse
Are you sure the drivers weren't already installed?
You could also try manually installing the drivers. I'd post some links...but I'm still new so it won't let me.
Do a quick "oppo find 7a drivers" google search, first or second link should do the trick, just make sure you read to make sure its the correct driver for your phone and computer's OS.
Is there a specific problem you are having with the phone? Or are you just trying to start fresh? You can still wipe data/cache in stock recovery, as well as flash stock roms, but like i said, they are finicky for whatever reason.
Salvia128 said:
Are you sure the drivers weren't already installed?
You could also try manually installing the drivers. I'd post some links...but I'm still new so it won't let me.
Do a quick "oppo find 7a drivers" google search, first or second link should do the trick, just make sure you read to make sure its the correct driver for your phone and computer's OS.
Is there a specific problem you are having with the phone? Or are you just trying to start fresh? You can still wipe data/cache in stock recovery, as well as flash stock roms, but like i said, they are finicky for whatever reason.
Click to expand...
Click to collapse
Okay you might be right. So I suspect the driver has already been installed when I used Root Genius to root the phone, that's why I didn't see any Oppo green logo on the dvd drive.
No specific problem with my phone.. Just that I wanted to try flash other ROMs and was following instructions when I got confused as to whether my PC has the driver already..
The other day I was trying fastboot and apparently the PC didn't detect anything. I tried many things, forgot what did I do to finally manage to make it able to detect my phone (via command <fastboot devices>)
Thanks.
ianbong said:
Okay you might be right. So I suspect the driver has already been installed when I used Root Genius to root the phone, that's why I didn't see any Oppo green logo on the dvd drive.
No specific problem with my phone.. Just that I wanted to try flash other ROMs and was following instructions when I got confused as to whether my PC has the driver already..
The other day I was trying fastboot and apparently the PC didn't detect anything. I tried many things, forgot what did I do to finally manage to make it able to detect my phone (via command <fastboot devices>)
Thanks.
Click to expand...
Click to collapse
Well you have the drivers for the phone installed most likely.
As for fastboot, did you install the androidsdk?? You'll need that in order to flash a custom recovery.
Do another quick google search: "how to use fastboot with oppo find 7a" the second entry from oppoforums has a guide to root the phone...I know you used "rootgenius" which i have no idea what that is I've always rooted android myself through custom recoveries (although it may be a similar process, just automated). That guide will at least show you how to install the tools you need to use fastboot correctly. If you have any troubles, let me know, ill do my best to help
---------- Post added at 11:49 AM ---------- Previous post was at 11:44 AM ----------
I forgot to mention, if you do use that guide...make sure you don't flash the x9077 TWRP version that the guide uses as an example. Just go to TWRP's site and find the version for your phone.... x9006. Then follow them as normal.
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.
Hey guys,
I'm having some issues with mounting while I'm in the recovery. In fact, the computer (win7) won't even recognize that the phone is connected via USB. The device manager just shows "SAMSUNG_Android_SPH-L710" with a yellow exclamation mark. Whenever I connect the phone in recovery to the computer, it tells me driver installation was unsuccessful. I searched around before posting and made sure of few things.
1. Using the Samsung USB Cable.
2. Installing the Sprint_L710_GSIII_Samsung_USB_Driver_v1_4_6_0.exe found on Samsung's website.
3. I reinstalled the driver after it didn't work the first time.
I did read that I need adb drivers to get my computer to recognize my phone while in recovery mode. Is that true? If so, can someone please provide me the link to those drivers. I googled it but want to make sure I install the right version and don't end up bricking it.
Is anything else can be the issue here? Also, is mounting in recovery supported in latest CWM/TWRP?
I'm stock rooted with the LI3 update and trying to wipe everything clean before trying out Paranoid Android ROM. I haven't wiped anything yet since I want to make sure after I wipe my external/internal SD Card, I can place ROM files in the storage. Please let me know and any help is appreciated.
Thanks!
Not sure why you are trying to access your computer from recovery mode.
MobDad said:
Not sure why you are trying to access your computer from recovery mode.
Click to expand...
Click to collapse
1) Because a lot of root instructions tell you to
2) Because it's really annoying to reboot the phone, load a file, reboot to recovery and flash
I root devices part time and use that feature pretty often
Sent from my Jelly Bombed SGS3
---------- Post added at 03:12 AM ---------- Previous post was at 03:06 AM ----------
It is hit or miss and I don't know why. Sometimes it mounts for me, sometimes it doesn't.
Save yourself a ton of time and heart ache. You shouldn't lose and internal or external memory when you flash a rom on the SGS3. When you wipe, it only wipes your system and data which is on a separate system storage. I have read some people report a flash wiped their internal storage, but certainly not the external.
Btw.. Are you selecting "mount usb storage"?
Sent from my Jelly Bombed SGS3
Thanks guys for replying. So I finally got it working. After the first reinstall of the drivers, it still wasn't working. I was getting frustrated so I was like let me reinstall one more time. Give it a one more try. This time, I have no idea what changed but it started mounting. It still shows up in device manager with yellow exclamation mark. However, when I click Mount USB Storage in TWRP, it mounts. It does seem random in a sense that it works sometimes and doesn't other times.
wolfpack15 said:
Hey guys,
I'm having some issues with mounting while I'm in the recovery. In fact, the computer (win7) won't even recognize that the phone is connected via USB. The device manager just shows "SAMSUNG_Android_SPH-L710" with a yellow exclamation mark. Whenever I connect the phone in recovery to the computer, it tells me driver installation was unsuccessful. I searched around before posting and made sure of few things.
1. Using the Samsung USB Cable.
2. Installing the Sprint_L710_GSIII_Samsung_USB_Driver_v1_4_6_0.exe found on Samsung's website.
3. I reinstalled the driver after it didn't work the first time.
I did read that I need adb drivers to get my computer to recognize my phone while in recovery mode. Is that true? If so, can someone please provide me the link to those drivers. I googled it but want to make sure I install the right version and don't end up bricking it.
Is anything else can be the issue here? Also, is mounting in recovery supported in latest CWM/TWRP?
I'm stock rooted with the LI3 update and trying to wipe everything clean before trying out Paranoid Android ROM. I haven't wiped anything yet since I want to make sure after I wipe my external/internal SD Card, I can place ROM files in the storage. Please let me know and any help is appreciated.
Thanks!
Click to expand...
Click to collapse
I have the same problem. I need a driver for device manager while in twrrp.
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
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.
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
erich_vogt said:
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
Click to expand...
Click to collapse
I used Odin and TWRP in a .tar file. This seemed to work ok but on rebooting the phone now gets stuck on the Google logo. I assume it is a boot loop. The solution to this according to various threads is to either re-flash a stock image or to flash with a custom ROM. I'll try the latter.
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
erich_vogt said:
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
Click to expand...
Click to collapse
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
erich_vogt said:
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
Click to expand...
Click to collapse
I went back to Device Manager and changed the MTP driver to the other alternative which now exists in the system. It's called "MTP USB Device" and is a Microsoft driver. This seemed to improve the situation and allowed me to see all of the contents of the folders in the phone's Internal Storage. I discovered by a process of trial and error that now I could copy files into all the folders except the folder called !ReadyToFlash. I believe this folder may have been created by TWRP when it installed. All the other folders are now behaving sensibly. I copied the Lineage 13 zip into the Downloads folder and booted the phone into Recovery Mode. TWRP 3.0.2-0 was able to install Lineage and everything seems to be working correctly although I haven't tested all the functions yet.
I notice that although the radio can see my 5GHz 802.11ac wifi it seems to be unable to connect and can only connect to the 2.4GHz wifi. I don't know if this a hardware limitation arising from the original modem or a software limitation of the Lineage modem driver. This thread, although it's just me, might give another noob attempting to reconfigure their old Galaxy Nexus a few pointers.