Phone won't boot into Android, also having trouble installing ADB Drivers - Samsung Galaxy Nexus

Hello all,
My phone randomly turned off today and started hanging on the boot animation screen.
I can still access CWM and fastboot.
I've tried wiping and reinstalling a ROM, but the phone just reboots itself during the install . It also does the same thing during a nandroid restore.
Since I wasn't sure what else to do, I tried to use the GNEX Toolkit to flash to stock. I keep getting write errors when trying to flash. I think the problem is I can't install the ADB drivers on my computer. I've done some research, but it seems that you have to be in Android, with USB Debugging on to install them. I can get the fastboot USB drivers working, but can't do do the restore without the ADB drivers as well.
Also tried Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
PDAnet needs me to be in Debugging mode.
Tried updating Android 1.0 Driver manually in Device Manager.
Any help would be appreciated. Will thank any helpful posts. Thank you!

This is also my issue and a link to my thread http://forum.xda-developers.com/showthread.php?p=25386193#post25386193
---------- Post added at 05:08 PM ---------- Previous post was at 05:06 PM ----------
TwinkyOfHope said:
Hello all,
My phone randomly turned off today and started hanging on the boot animation screen.
I can still access CWM and fastboot.
I've tried wiping and reinstalling a ROM, but the phone just reboots itself during the install . It also does the same thing during a nandroid restore.
Since I wasn't sure what else to do, I tried to use the GNEX Toolkit to flash to stock. I keep getting write errors when trying to flash. I think the problem is I can't install the ADB drivers on my computer. I've done some research, but it seems that you have to be in Android, with USB Debugging on to install them. I can get the fastboot USB drivers working, but can't do do the restore without the ADB drivers as well.
Also tried Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0
PDAnet needs me to be in Debugging mode.
Tried updating Android 1.0 Driver manually in Device Manager.
Any help would be appreciated. Will thank any helpful posts. Thank you!
Click to expand...
Click to collapse
I have also tried the same stuff the issue is i cant get into debugging mode because the screen doesnt turn on. i have 2 batterys so the battery isnt the issue. (besides the fact that the phone drains the battery but doesnt charge)

Bump
Sent from my SGH-I897 using xda premium

Have you tried Odin?
Sent from my Galaxy Nexus using xda premium

lucas.scott said:
Have you tried Odin?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I got my phone detected by ODIN this morning after numerous driver installs.
However, I've been a little worried to flash a stock ROM through it since the Gnex toolkit had write errors. The guy in this thread seems to have possibly bricked his phone http://forum.xda-developers.com/showthread.php?t=1621430&page=2

Related

Sprint Gnex: Help! Can't unlock bootloader, root or flash roms, phone not detected!

Hey guys I am having a very annoying issue with my Sprint Gnex. It runs the latest OTA (I believe 4.1.1) and is not unlocked or rooted.
Well, I want to unlock it, and so I try following this guide:
http://www.droid-life.com/2011/12/05/how-to-unlock-the-galaxy-nexus-bootloader/
I have the latest drivers from Samsung installed on my PC. What happens is that whenever the phone is in recovery mode, it is not properly detected by my computer, and in device manager, it has a yellow exclamation mark next to it. When I am running the phone normally with USB debugging enabled, it works fine. Just not in recovery mode.
As a result, I can't run the "fastboot oem unlock" command! Essentially, I can't do anything with the phone! Can anybody help or knows what might be going on? Again, when the phone booted normally, it is detected by my computer and adb commands work fine. Just not when it is in recovery mode!
userno69 said:
Again, when the phone booted normally, it is detected by my computer and adb commands work fine. Just not when it is in recovery mode!
Click to expand...
Click to collapse
First, of course it's your fault. Who else's would it be?
A tip for you: When you get that yellow exclamation mark when connected in recovery, you need to manually update the driver.
Another tip for you: naked drivers, you don't need any of that Samsung crap
And the last one: normal ADB mode doesn't work in stock recovery, only ADB sideload.
Okay, this is really the last one: if you had EVEN browsed this forum and read the stickies, you would have known that to unlock your device, you need to be in fastboot mode, not recovery mode, 2 different things, and you can get there by.. Searching.
sent from my Google Galaxy Nexus
bk201doesntexist said:
First, of course it's your fault. Who else's would it be?
A tip for you: When you get that yellow exclamation mark when connected in recovery, you need to manually update the driver.
Another tip for you: naked drivers, you don't need any of that Samsung crap
And the last one: normal ADB mode doesn't work in stock recovery, only ADB sideload.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
Where do I get the driver to manually update? And sideload didn't work either, I tried using it to install the 4.2 official ROM, but it wouldn't detect the phone
userno69 said:
Where do I get the driver to manually update? And sideload didn't work either, I tried using it to install the 4.2 official ROM, but it wouldn't detect the phone
Click to expand...
Click to collapse
I've edited my previous post. Where do you get the driver? Where did you install it to? Search for naked drivers in Dev section.
sent from my Google Galaxy Nexus
---------- Post added at 07:02 AM ---------- Previous post was at 06:59 AM ----------
You know what? Nothing personal and all, I'm tired of answering the same type questions, I'm taking vacations from this ****.
Read or don't read, your call.
http://forum.xda-developers.com/showthread.php?t=1626895
sent from my Google Galaxy Nexus
You know what? Piss off. I was tired when I posted this thread, and looks like I had some of my terminology mixed up. When I was in recovery trying to flash GA02, adb sideload IS what I was using. The drivers I got from Samsung simply didn't work. If you are trying to suggest that it should have occurred to me that "Hey, seems like the official drivers don't work for what they are designed to do. Obviously I need hacked ones" then you are out of your mind.
In fact, it turns out that the Universal Naked Drivers you referenced did the trick perfectly, which I do appreciate. Right now, that is aside the point however.
On to the terminology mixup. It turns out when I was trying to unlock the device I WAS in the fastboot menu, not recovery. I was not aware of the naming distinction, but I WAS in the right place, and it still didn't work. Presumably due to the Samsung drivers, which were apparently the source of all the problems I've been having.
Again, I appreciate you pointing me in the direction of the Naked drivers, but I take serious issue with condescending attitude that so many people have on XDA.

[Q] Computer doesn't recognize HOX after flashing

Hi guys, my dad got a problem with his rooted HTC One X. His phone crashed after flashing. After the crash he formatted the phone except for the SD card. Now none of our computers recognize the phone anymore so he isn't able to put firmware on it. He has tried to mount/unmount the SD card via device manager, but the computer sees it as an unknown device. My dad tried to install the drivers but that didn't work. After that he tried to install ADB drivers but that also didn't work. Anyone here who can help him?
Yup, dozens of ppl here can help him.
What did he flash?
What firmware are you talking about?
ROM? Firmware.zip?
What do you mean by "didn't work"? Did he actually install the drivers or did it fail?
TToivanen said:
Yup, dozens of ppl here can help him.
What did he flash?
What firmware are you talking about?
ROM? Firmware.zip?
What do you mean by "didn't work"? Did he actually install the drivers or did it fail?
Click to expand...
Click to collapse
Hmm, I actually don't know what he flashed; I'll ask him when he gets home! I was talking about ROM. He actually installed the drivers but the computer still didn't recognize the phone
Sent you PM.
Sent him a PM in Dutch :thumbup:
Hello,
I have the same problem with my HOX, after rooting I can't connect to my pc , so I cant flash anything.
Theo
My friend is also having this same issue.
The phone is not turning on.
HTC Sync Manager, ADB, non of them recognize the device.
Holding Vol down + Power button didn't do anything.
It's like the device is completely dead. But when connected to the PC, device manager shows it as an unknown device.
Any ideas/ solutions?
Make sure you dont use a USB3.0 connection. We had a hard time getting adb to work last night. My suggestion is to deinstall the htc drivers, uninstall the unknown device. Reinstall the htc drivers and reboot the pc then hook the phone to the pc and let it install. If it still comes up with unknown device you click it and select to install your own your own drivers and then select to choose from the list......you should see ANDROID PHONE in the list, click it and there should be an option called MY HTC install it and reboot the phone and the pc ....this way we got it working last night.
Sent from my GT-P5110 using xda app-developers app
Thanks for the reply. I'll try that.
Maybe this helps too
http://forum.xda-developers.com/showthread.php?t=1644730
Thanks again for the reply. I've already tried it. Nothing gets installed. And still it says Unknown device.
Well the problem that QQ had is solved. We got the drivers in order late lastnight after a lot of de-installing and re-installing of java and HTC drivers .....finally it worked, but then the battery ran out so i wrote him a full and easy to use tutorial and put the files he needed where they had to be .....
:and he did a great job following the steps and got him back a full working phone :thumbup:
---------- Post added at 07:24 PM ---------- Previous post was at 07:08 PM ----------
dushan90 said:
Thanks again for the reply. I've already tried it. Nothing gets installed. And still it says Unknown device.
Click to expand...
Click to collapse
I found another link
http://forum.xda-developers.com/showthread.php?t=1830108
Check this .....

[Q] Nexus stuck in boot loop. how get to install drivers?

Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...

[Q] [Help!] Bricked Phone with driver problem

Hello everyone...
I was updating the phone recently, and went to reboot it (cyanogen mod ROM btw) and now I have no idea what it did but it is now stuck on the Samsung logo, and their is no recovery I can use on it. Only DL mode works.
I tried to use Odin to relfash but the problem is on both my Windows 7 and Windows 8 computers, they install the drivers, but they still fail to recognize the phone when I plug it in!
I have tried different USB ports, a full driver uninstall, multiple USB cords and the computer refuses to recognize the phone saying "USB Device not recognized"
Again, the drivers install fine, and I did a reboot after each install and uninstall. No luck.
I didnt even install drivers on my W8 netbook and I was able to flash back TWRP using Odin and Download mode yesterday when my attempt at flashing TWRP 2.6.0.4 originally failed.
Fire up download mode, then open up Odin (you should see a COM port open), load up what you need to install, then flash.
What are you trying to flash using ODIN? A bootloader or a ROM?
"BootLooping GhostBrick"
Holy crap! you too? I'm experiencing the same thing too bro. its my girlfriend's phone tho. she's borrowing my Nexus 4 while I work on fixing her SGS2...I seem to have contracted a serious case of the BootLooping GhostBrick, just like you did, right after updating. I went through the same steps troubleshooting as you did, and ...its a guess, but I'm starting to figure the solution will probably include: 1. using ADB to push sum files to the phone, or otherwise somehow reflashing stock firmware from the PC.
2. Re-Root the dam thing and flash a kernel with a recovery (like CWM or TWRP) using rom manager...and 3. Considering installing a ROM of my choice Like PACMAN, or Cyanogenmod.....hmm...Yum
anyway, the search for the vaccine to this dreadful affliction begins. Please post if you find something, I will too.
---------- Post added at 10:21 AM ---------- Previous post was at 10:13 AM ----------
nagoshi said:
I didnt even install drivers on my W8 netbook and I was able to flash back TWRP using Odin and Download mode yesterday when my attempt at flashing TWRP 2.6.0.4 originally failed.
Fire up download mode, then open up Odin (you should see a COM port open), load up what you need to install, then flash.
What are you trying to flash using ODIN? A bootloader or a ROM?
Click to expand...
Click to collapse
...true, I second that. I'm doing this as we speak.
No Go Mi Amigo... PC still No read
vdorvilus said:
Holy crap! you too? I'm experiencing the same thing too bro. its my girlfriend's phone tho. she's borrowing my Nexus 4 while I work on fixing her SGS2...I seem to have contracted a serious case of the BootLooping GhostBrick, just like you did, right after updating. I went through the same steps troubleshooting as you did, and ...its a guess, but I'm starting to figure the solution will probably include: 1. using ADB to push sum files to the phone, or otherwise somehow reflashing stock firmware from the PC.
2. Re-Root the dam thing and flash a kernel with a recovery (like CWM or TWRP) using rom manager...and 3. Considering installing a ROM of my choice Like PACMAN, or Cyanogenmod.....hmm...Yum
anyway, the search for the vaccine to this dreadful affliction begins. Please post if you find something, I will too.
---------- Post added at 10:21 AM ---------- Previous post was at 10:13 AM ----------
...true, I second that. I'm doing this as we speak.
Click to expand...
Click to collapse
.....well, so much for that attempt.... still cant get either the PC or Odin to Read....I just flashed CWM recovery using ODIN minutes ago with no problems, but now its borked too
vdorvilus said:
.....well, so much for that attempt.... still cant get either the PC or Odin to Read....I just flashed CWM recovery using ODIN minutes ago with no problems, but now its borked too
Click to expand...
Click to collapse
Reinstall Odin and the drivers for t989, then go get twrp 2.6.0.4 from techerrata.com/browse/twrp2/hercules then open Odin and put the phone in DL mode, now when odin connects make sure u open the recovery in PDA format and touch nothing else in Odin, flash twrp and ur good, this version is capable of dealing with 4.3 too with no issues at all
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Same issue
soupysoup said:
Reinstall Odin and the drivers for t989, then go get twrp 2.6.0.4 from then open Odin and put the phone in DL mode, now when odin connects make sure u open the recovery in PDA format and touch nothing else in Odin, flash twrp and ur good, this version is capable of dealing with 4.3 too with no issues at all
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Re-installing Odin and drivers still didn't get Odin to recognize the device in download mode. Windows 7 isn't assigning it any COM port, and nothing can be flashed unless Odin sees the com port the device is on. I used Goo Manager to flash TWRP 2.6.0.3 over my previous 2.6.0.0 version and now I'm stuck on samsung logo, can't reboot to recovery and PC won't recognize device in download mode. Anyone know a solution?
VermontKindBud said:
Re-installing Odin and drivers still didn't get Odin to recognize the device in download mode. Windows 7 isn't assigning it any COM port, and nothing can be flashed unless Odin sees the com port the device is on. I used Goo Manager to flash TWRP 2.6.0.3 over my previous 2.6.0.0 version and now I'm stuck on samsung logo, can't reboot to recovery and PC won't recognize device in download mode. Anyone know a solution?
Click to expand...
Click to collapse
Welcome to ur first soft brick, and as I said in ur other post u need to disable or removes Samsung kies before trying to use Odin as long as any part of kies is running even in background Odin won't see the device, also make sure u use factory/data approved USB wires, also try diff ports, sometimes Odin won't see com3 but will see com5, be patient and follow this and ull be fine, also twrp2.6.0.3 has been known to cause sftbricks, DL 2.6.0.4 from techerrata.com/browse/twrp2/hercules its the newest and 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Yup
soupysoup said:
Welcome to ur first soft brick, and as I said in ur other post u need to disable or removes Samsung kies before trying to use Odin as long as any part of kies is running even in background Odin won't see the device, also make sure u use factory/data approved USB wires, also try diff ports, sometimes Odin won't see com3 but will see com5, be patient and follow this and ull be fine, also twrp2.6.0.3 has been known to cause sftbricks, DL 2.6.0.4 from its the newest and 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, I wish I'd known that. Goo Manager automatically selected it as the latest recovery. I just can't get past the device not showing up as a com port issue at all. Is there any known way to make windows recognize it?
VermontKindBud said:
Yeah, I wish I'd known that. Goo Manager automatically selected it as the latest recovery. I just can't get past the device not showing up as a com port issue at all. Is there any known way to make windows recognize it?
Click to expand...
Click to collapse
Yes u need to make sure kies isn't running or installed on ur PC, if it is Odin won't see it
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Unrecognized by PC
VermontKindBud said:
Yeah, I wish I'd known that. Goo Manager automatically selected it as the latest recovery. I just can't get past the device not showing up as a com port issue at all. Is there any known way to make windows recognize it?
Click to expand...
Click to collapse
It's not a matter of trying different com ports, I can't get the PC or Odin to recognize the phone in download mode despite uninstalling kies, installing the latest drivers twice, 3 different OEM cables, multiple usb ports, nothing. when I plug it in, Windows doesn't make any sound like with other usb devices, nor does it try and search for drivers. Are there any other options short of JTAG repair?
VermontKindBud said:
It's not a matter of trying different com ports, I can't get the PC or Odin to recognize the phone in download mode despite uninstalling kies, installing the latest drivers twice, 3 different OEM cables, multiple usb ports, nothing. when I plug it in, Windows doesn't make any sound like with other usb devices, nor does it try and search for drivers. Are there any other options short of JTAG repair?
Click to expand...
Click to collapse
I was going to reply earlier, but I got side tracked and this guy is literally having the exact same problem as me. I tried multiple OEM cables, and ports and Windows recognized it but it still won't let me USE it. Odin (after re-install) still shows no connections or ports.
Also, yeah this phone isn't mine either, my Dads. He is using my old S3 for now and is quite mad with me hahaha.
So yeah, I have to re-cap...
-Updated through Goomanager.... (the culprit I am guessing)
-Rebooted
-Got stuck on the Galaxy S 2 screen
-Plugged in with 4 USB cables to three different USB ports
-Uninstalled and reinstalled Odin numerous times, each with a reboot between.
-Odin fails to recognize it
-Windows KNOWS IT IS THERE, and makes a sound when plugged in, however it says "USB Device not recognized"
Any more ideas?
Thanks for the help to guys it is very much appreciated. I will donate to the person that can help me out of this
Here is a screen shot of Windows with the phone in DL mode
LGIQEXPO said:
Here is a screen shot of Windows with the phone in DL mode
Click to expand...
Click to collapse
Do u have Samsung kies installed on the PC? If u do your going to need to remove all traces of it in order for Odin to see the phone, also search Samsung t989 USB drivers and install the specific driver for Hercules, if u can get the phone into DL mode its fixavke so don't stress to much, I use Odin v1.85, download twrp2.6.0.4 from this site techerrata.com/browse/twrp2/herculesif Odin still fails to recognize the device try diff PC, factory/data approved USB wire, an make sure kies is nowhere and it should work, pm me if u need more help I'll do what I can, but like I said as long as DL mode is accessible its only a soft brick...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Do u have Samsung kies installed on the PC? If u do your going to need to remove all traces of it in order for Odin to see the phone, also search Samsung t989 USB drivers and install the specific driver for Hercules, if u can get the phone into DL mode its fixavke so don't stress to much, I use Odin v1.85, download twrp2.6.0.4 from this site techerrata.com/browse/twrp2/herculesif Odin still fails to recognize the device try diff PC, factory/data approved USB wire, an make sure kies is nowhere and it should work, pm me if u need more help I'll do what I can, but like I said as long as DL mode is accessible its only a soft brick...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Kies is no where in sight. I will try yet another PC as well as searching for Hercules specific drivers (any link?) When I get home. Thank you in the mean time
LGIQEXPO said:
Kies is no where in sight. I will try yet another PC as well as searching for Hercules specific drivers (any link?) When I get home. Thank you in the mean time
Click to expand...
Click to collapse
Just Google Samsung t989 Hercules USB drivers, download and install, it should work, like I said as long as DL mode is accessible it should be an easy fix...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Omg....
I am experiencing the same problem. Did anyone find the solution?
Probably a faulty USB port. My computer shows that message all the time, only one of them works correctly. If not, you just need to install the correct USB Drivers, because even if you don't have them it should recognize your phone as a Samsung phone but will say that the drivers did not install correctly.

Not working after update

My computer won't recognize my phone after update bricked it. Sprint update broke my phone. I was rooted with stock rom, I updated and know my phone is semi-bricked. I've been working on the phone for almost two weeks reading through forums trying everything possible. It goes in download mode but it wont install drivers and wont even recognize device. When I I put in in recovery my computer recognizes the device but drivers wont install. I have already done the terminal script laf.img, tried to install a rom gives me an error, I have backup but it doesn't installs either. Please Help Me.
Download mode, is it the small screen with a small bar or the big one at the bottom bar.
May need to remove all your drivers then reinstall.
Sent from my LG-LS980 using Tapatalk
Small Screen It says I'm in fastboot, Cant install the drivers for the phone, I refresh my only pc an Asus laptop to be able to attempt to install drivers again, did the laf.img terminal command, tried adb sideload device not showing in adb
Computer doesn't recognize phone and download mode broken. I've read somewhere where Linux can sometimes read it when windows doesn't.
Recovery stock or custom? I think I might be able to find a flashable laf.zip
If it is such you, dam. If custom which version of it. If twrp, you may be able to upgrade to newest from cm12 forum. I'll find the link. It may give a better access. If stock might be able to adb side load update zip of laf by changing the name.
Sent from my LG-LS980 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=2898705
Latest and greatest twrp version.
Sent from my AOSP on Grouper using Tapatalk
---------- Post added at 02:54 AM ---------- Previous post was at 02:51 AM ----------
http://forum.xda-developers.com/showthread.php?t=2582142
How to fix no recovery no download mode. This might help also.
Sent from my AOSP on Grouper using Tapatalk
Recovery is TWRP V2.7.0.0 I only have access to my laptop. Before this problem I had no problem connecting to laptop. Let's not get excited but finally I was able to do something I installed the new TWRP zip you gave me now I'm in TRWP 2.8.1.1
That is good. Now they have an mtp button under I believe advance. You may be able to get a ROM transferred to it that way. In which we may be able to save the p phone.
Sent from my LG-LS980 using Tapatalk
Thank You for your help, it sucks not having a functional device to use. I tried using the MTP button but it did not help, I even set up an VMware Ubuntu virtual machine but no luck yet. I appreciate any tips on using this two methods. What I think is that that Laf.Img fix, with the terminal command is the key to my problem. Maybe I haven't edited correctly, recently I tried doing it again but this time around I can't never find the file, even do I copied or moved the file to root of sd card with an otg mount several times, all I'm able to find in the internal storage are folders none of the files that I have in the root appears. Please Help.
What would happen if it toggle off from USB debugging?
Then adb would have a hard time finding the device.
Sent from my LG-LS980 using Tapatalk
And my laptop too ; (
I haven't given up on you yet. Even if I can't, fix it for you. One great but if info. Never take ota, when you do anything to a phone.
Sent from my LG-LS980 using Tapatalk
Hi I worked on the phone again and now I'm able to put it MTP and SDK recognizes the phone I get a string of numbers and it says recovery.
That is good news. I've been having some issues with that darn laf but if my wife and kids leave me alone. I might get it figure out right.
Sent from my LG-LS980 using Tapatalk

Categories

Resources