[Q] Soft Brick / USB Brick / General Weirdness - Samsung Galaxy Nexus

Phone: VZW Galaxy Nexus, Rooted, TWRP Recovery, Lean Kernel
For the first (and last) time in my life I decided to dirty flash a ROM (4/16 build of Project Elite) to my phone (from an earlier build of PE). My phone apparently hated that. It has created an odd world of problems for my phone that I am hoping someone may be able to see a trend with and offer up some suggestions for escaping this odd world.
Here are my phone's symptoms:
(1) Earpiece on phone stopped working: During phone calls, I can only hear audio when using speakerphone. I was able to remedy this by getting the SoundAbout App from the Play store. This tool allows you to manually change how the audio is routed. My phone thinks a headphone is plugged in and tries to route the audio through the headphone jack. This app allows me to fix that problem.
(2) USB File Transfer Mode stopped working: When connecting my phone to the computer it will charge (sometimes, see #3) but my computer will not recognize it as a device. Consequently, adb (and wireless adb), fastboot and ODIN all will not connect to my phone because the phone is not recognized. I have uninstalled, updated and re-installed just about every driver set I can find for the Galaxy Nexus/ I know it is not a driver issue because my wife's Nexus connects to the CPU just fine.
(3) Phone Charging is Intermittent: I have trouble finding a trend with this one. If I toggle Fast Charge (Off or On), my phone will no longer charge. This is fixed by powering off the phone with the cable plugged in. At that point the white battery icon appears and the phone begins charging. If I power the phone back on, the phone will continue to charge but will not be recognized as a USB device.
Here is what I have tried over the past 2 days:
(1) Both GNEX Toolkits: With no USB connectivity, adb and fastboot are not options. This option becomes unavailable with no usb. Have tried both.
(2) ODIN: Phone is not recognized by ODIN tool.
(3) Cleaning USB/Headphone Ports: This produced some interesting black stuff, but no results.
(4) Clean Flash of PE 4/16 Build: Wipe data/cache/dalvik and re-flash. Same problem.
(5) Clean Flash of Stock Rooted Build: Wipe data/cache/dalvik and flash. Same problem.
(6) Mobile ODIN: Cannot locate the tar balls for a stock 4.2.2 factory flash. Have found the necessary files for 4.0.2, but these will not flash in Mobile ODIN. I have read that you have to be on the same android version as the ODIN tar files you are trying to flash. I think this is my best option at this point, but I cannot for the life of me figure out how to get Mobile ODIN to work.
As far as I can tell this is a software problem that is baked somewhere deep in the phone. Since the USB and headphone problem started at the same time, I do not believe it to be hardware. My theory is that somehow fast-charge is locked on (?) and my phone is locked to routing the audio to the headset. If I can find a way to completely wipe everything off and start fresh, I believe my problem will be solved.
Does anybody have any ideas what may be going on here and how I may be able to get this phone back to Stock?
tldr; no usb, no headset audio after dirty flash, how do i get back to stock??

In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus

bk201doesntexist said:
In fastboot, there's no fast charge, since there's no Android running aka no Android kernel running.
Sent from my Nexus
Click to expand...
Click to collapse
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.

7ontheline said:
Thanks for the response.
I am running Win7. Like I said, I have tried connecting my wife's Nexus to the same computer and it is recognized as usual. The only reason I thought it had something to do with FastCharge was that toggling it has an effect on the charging capabilities of my phone. When I boot into FastBoot the phone still does not show up in the Toolkit and running any operation in the Toolkit that uses FastBoot gets hung on "waiting for devices."
My latest experiment is to Flash a Nandroid of a Stock Nexus Image. However, I have not been able to find flashable stock image! Seems like something that would have been a common file so if you are aware of any Stock Nandroid Backups I would love to try that.
Click to expand...
Click to collapse
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?

bk201doesntexist said:
I don't use toolkits, so I don't know how to help there. Does the device get recognized under Device Manager as a fastboot interface? Have you followed http://forum.xda-developers.com/showthread.php?t=1812959? Tried the Universal Naked Drivers?
Click to expand...
Click to collapse
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.

7ontheline said:
My device does not get recognized within Device Manager. No yellow exclamation mark, no mention of a connected device, nothing. When my wife's Nexus is connected it shows up as expected and communicates just fine via adb. I have followed the guide you mentioned and have installed ROMs many many times with nor problems previously. I have tried the Universal Naked Drivers. I uninstalled all other drivers and installed these. They work as expected with another Nexus, just nothing with mine. Starting to look like I may just be out of luck here.
Click to expand...
Click to collapse
You seem to be confusing stuff... Fastboot is not ADB, and you have to feed the same driver to windows twice.
You've done this? Sure the USB port doesn't have a bent pin or something?
Sent from my Nexus

My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app

tdf666 said:
My phone is doing the exact same thing. Started about 2 weeks ago. I can't remember but I think it started after flashing the latest liquid smooth rom. I don't think it was a dirty flash but hell I can't remember.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Let me know if you figure anything out. I am just dealing with it right now using the SoundAbout App and rebooting my phone whenever it won't charge. It is pretty annoying, but I am at a loss for fixes at this point.
I am not really confusing ADB and Fastboot. I understand that they are two separate ways of communicating with the phone via USB. However, as I stated, there is no USB connectivity other than for charging.

I'm at a loss. Then the other day I got down to 13 percent battery and it started shutting off. I think I'm just going to get another phone. This has been the best and worst phone I've ever had.
Sent from my Galaxy Nexus using xda app-developers app

Related

[Q] ICS to GB Problems

Hello guys this is my first post so forgive me if I don't have the terms down to key.
I've recently flashed to the Codename Android ICS rom and while it's a beautiful rom my battery life after 4 cycles or so hasn't improved past 8 hours a day. I was previously getting decent life on Blazer so I want to revert back to GB. After doing my research on the million topics of reverting from ICS to GB, I thought I would give it a shot. Right now I still have the Codename Android rom, FC22 Kernel, and the EL26 modem. I followed sfhub's well written guide using the EL29 one-click modem program. I had my phone in download mode and recognized by my computer, but when I clicked the start button ODIN almost instantly showed a red fail box and as far as I know the cable is fine and the computer never lost power. Fearing the worst I quickly unplugged my phone and restarted it and luckily still booted into the rom fine and everything seemed normal. However my phone is no longer recognized by my computer, in download mode or not. The phone charges and my computer makes the device recognition beep, but one second later it makes the device unplugged beep and this keeps continuing and the phone is never fully recognized. I still want to revert to GB so I installed mobile odin to cut out the pc part. Before I do anything I want to make sure I have the right files downloaded (EL29 or 26 files), and that mobile odin will work fine on ICS to get me back to GB without breaking my phone. With all the brick stories lately, I want to make sure I have everything down.
Any help will be appreciated.
I would try a different USB port on the computer. I used to have problems with my Samsung moment where out would stop seeing the phone but changing the port let it redetect. Reinstalling the drivers or trying a different PC to see if it detects the phone could point you to which end is the problem.
Sent from my Epic 4g Touch running Blazer 4.1 using xda premium
I tried different USB cables and computers, but still having the problems. My girlfriend also has the E4GT, albeit all stock, and I plugged it into my computer and everything recognized correctly. I have the mobile Odin application installed on my phone and I just want to make sure I flash the correct files from the ICS Codename Android rom to get me safely back to GB. Seeing one red fail box from Odin has me on the cautious side.
Ok re download the el29 stock root one click first. Get rid of the one you have. Now download Calkulins format all and download auto root eg39-el29. Make sure you have system debugging checked. (settings /applications or settings/developer options) That is why your computer is most likely not recognizing. If it is checked then check your drivers. Go in to recovery. Run calls format all av few. Times. Pop o out the battery when its finished and go to Odin download mode. Flash one click rooted el29. Reboot. Check USB debugging again and connect usb but don't go into usb mode. Start auto root el29 cwm rogue to get recovery. Reboot. After successful reboot flash blazer offer whatever el29 rom you.like. Hope i helped.
Thanks for the reply Tinmetal. I checked my phone and I have Android Debugging and USB Debugging Notify checked. I also tried reloading the drivers on different computers, switching cables, and rebooting the devices. I'm pretty sure the connectivity problem came from the failed Odin flash, which I still don't know what went wrong.
I looked more into when I connect the phone to the computer and I recognizes the device, but before the drivers are applied the device gets disconnected. This lead me to a USB cable or port problem, but I tried every combination and still had the problem.
Do you still feel that Calkulin's wipe all is necessary being on a ICS rom, I read that flashing the cache's while on ICS can cause problems. I extracted the .tar files for the stock root el29, do you expect any problems if I use mobile Odin?
kal727 said:
Thanks for the reply Tinmetal. I checked my phone and I have Android Debugging and USB Debugging Notify checked. I also tried reloading the drivers on different computers, switching cables, and rebooting the devices. I'm pretty sure the connectivity problem came from the failed Odin flash, which I still don't know what went wrong.
I looked more into when I connect the phone to the computer and I recognizes the device, but before the drivers are applied the device gets disconnected. This lead me to a USB cable or port problem, but I tried every combination and still had the problem.
Do you still feel that Calkulin's wipe all is necessary being on a ICS rom, I read that flashing the cache's while on ICS can cause problems. I extracted the .tar files for the stock root el29, do you expect any problems if I use mobile Odin?
Click to expand...
Click to collapse
Check out this thread...bricked my phone http://forum.xda-developers.com/showthread.php?t=1525495
First of all yes you should ruin Calkins format all. Its not the same as using the recovery wipe. Next i would try to run sfhub's E4GTAUTO EL29EL29 auto root. You don't have to be in DOWNLOAD MODE OR USB MODE. IF YOU'RE HEARING THE CONNECTION SOUND THEN YOUR PC IS RECOGNIZING THE DEVICE. IF e4gtauto doesn't connect to your device i would uninstall kies and all Samsung drivers from the device manager on your computer and reinstall with just the sprint drivers. Put in a search for the sprint drivers here on xda and it should come up. If you can't find the sprint drivers hit me back and I'll post them for ya
Alright I have an update hopefully this will help someone who may be experiencing the same problems. My phone was working perfectly fine the day before. I woke up this morning and my phone was completely uncharged even on the charger overnight and would not turn on or charge (PC or wall outlet). I tried different cables and usb ports/wall outlets and I didn't do any flashing at all for a while and I was still on Codename ICS with USB not working. The blue light kept flashing and when I tried to go into download mode I got the "Low Battery, No Download" in red letters.
I took out my gf's battery from her US Cellular gs2 which is basically the same except no WiMax. Put it in my phone and it worked booted up, albeit with really weird touch issues (my battery didn't work/charge in her phone if anyone was wondering). Thinking I had no other choice at this point I used Mobile Odin to flash my phone back to GB in el29 with sfhub's .tar file. Surprisingly everything seemed to work. I am currently back on gb el29 without root (all stock) and I put my battery back in and it wouldn't turn on. I put the charger on and it took about 10mins of charging without the phone on and then I turned it on with it working. I unplugged the charger and it is holding a charge pretty well. However, I am still experiencing the same USB problems. When I plug the phone into the PC it recognizes it and I get the mtch-usb?? (sorry I'm not at home to be exact) on my notification bar, but I cannot get into USB debugging. My PC keeps beeping device recognized then beeping device unplugged and I don't see any activity on device manager. Any explanations, questions, or help would be appreciated?
It sounds to me, unrelated to ODIN, you coincidentally had USB port problems when you were doing this flashing.
Have you tried blowing compressed air into the USB port to dislodge any particles that might have gotten stuck?
I just blew some some compressed air into the phone and it didn't change much. When I plugged it in this time the installing drivers bubble came up and installed "Gadget Serial", which turned into Samsung CDA... My phone's USB connections were working perfectly before I tried my initial ODIN back to the el-29. When I tried that ODIN ran for a good 2 seconds before having the red fail box. I think I set everything to directions, but something happened that caused the failure (slight cable disconnection, bad USB port...) but I have no exact idea what caused that initial red fail box i"m only speculating. Nothing seemed out of the ordinary. After that failure thought my phone couldn't maintain a USB connection. sfhub are you aware of a bad ODIN flash compromising the USB connection, even if ODIN ran for only around 2 seconds, I don't know if it even had enough time to unpack the .tar files.
Mobile Odin el26+cwm. Hold power+volume up and reboot into recovery. Run Calks format all, flash ROM and reboot.
EL26+CWM kernel:
http://db.tt/0QJkleJR
Sent from Nocturnal Venum v1 using Tapatalk 2 Beta-5
kal727 said:
sfhub are you aware of a bad ODIN flash compromising the USB connection, even if ODIN ran for only around 2 seconds, I don't know if it even had enough time to unpack the .tar files.
Click to expand...
Click to collapse
The ODIN OneClicks are purposely arranged to flash recovery.bin first before anything else for just the situation you described. Recovery.bin is basically the *unused* recovery partition so losing it would have no detrimental affects on the phone. The leaked tar releases from Samsung/Sprint are arranged differently and flash the bootloader as the first item. If something went wrong there, I suppose USB could be compromised.
I just don't see how a compromised recovery that is unused could affect your USB and that is the basis of my suggestions.
That's exactly what I was thinking. I never used the modified ICS recovery, because of the problems people were having. I guess either the USB cable wasn't plugged in all the way or some kind of hiccup caused the failed ODIN attempt.
I have more information on my current USB connection. It says USB Connected, MTP-Connected on the notification bar. I've made sure USB debugging is on, but that is as far as my connection gets for either my phone or PC. Other than that notification on my phone I get no activity from my phone, or from Odin, the Samsung drivers, or Windows recognizing the phone.
For anyone new I've tried all the common fixes: switching cables, PC's, usb ports, and every variation of restarting PC/Phone and re-installing drivers, wiping data to factory settings(while on gingerbread), and blowing out the USB port.
Can you open an "adb shell" session to your phone when it is booted into android?
When you are going to ODIN DL mode, do you start ODIN first, then boot to download mode, or do you boot do download first, then start ODIN?
Are you using software to reboot to download mode or Power+VolDown.
Is it actually getting to download mode or not getting there?
I got confused when you said something about not being able to get into usb debugging. Can you change toggle that setting in the configuration? On GB ROMs if you enable USB debugging, it also disables MTP and switches you USB Mass Storage mode.
If you want you can try a ##786# reset from the dialer. It will reset NVRAM and your Android User Data. You'll need your MSL which you can get typing "getprop ril.MSL" in a termina or adb shell.
Mobile Odin might be your only choice if your pc doesn't see your phone. I have flashed from AOKP ROM numerous times using mobile odin and flashing the el26+cwm GB kernel. Just hold power+vol^ to boot into recovery as soon as phone starts to reboot. Just wipe everything and flash new ROM.
Sent from Nocturnal Venum v1 using Tapatalk 2 Beta-5
killaphatboy: I just successfully used Mobile Odin today to go back to gb, but my USB problems continued.
sfhub: Another thing I never mentioned was that before I went to ICS about a week ago Google Voice kept auto-starting and enabling Car Mode, that quickly went away when I flashed another rom so I didn't initially think it caused a problem.
Also sorry for the confusion. I could always cleanly get into download mode without any errors using Vol Down+Power. However no matter which sequence of starting Odin/plugging in USB cable/and going into download mode, the result is the same which the PC recognizes the phone, but gives the disconnected beep a second later. Can you link me a adb shell thread, I think I know how to set it up but 'adb devices' can't find any devices. Once in a while an installing drivers bubble pops up in in Windows for a split second before the device is disconnected. I caught the processes and found out that there are two drivers that install even though I have no recognition through Odin and no functionality through windows. The first is 'SAMSUNG Mobile USB CDC Composite Device' and the other is 'SAMSUNG Mobile USB Modem #2'. Both install and says Ready to use but I have no further recognition through Windows or Odin.
kal727 said:
sfhub: Another thing I never mentioned was that before I went to ICS about a week ago Google Voice kept auto-starting and enabling Car Mode, that quickly went away when I flashed another rom so I didn't initially think it caused a problem.
Click to expand...
Click to collapse
Enabling of car mode is a common symptom that has been reported when the USB port on the phone is starting to malfunction. Other people have reported the same thing when their USB port was on the way out. Sometimes cleaning out the port helped, sometimes not.

[Q] Can I get root w/o USB?

So the short question is if there is any way for me to get root without a working usb port?
Last week I plugged in to charge my phone overnight with the phone off. In the morning, I was surprised to find that the screen was on and what should have been a full green battery was instead a scrambled image that kind of looked like a battery. I powered on the phone and it worked so I thought nothing of it but later on that night I needed to pull a file off my phone via usb and realized that the phone will no longer detect the usb host, ie. no mtp options whatsoever. It at least does still charge.
Since then I have tried cleaning the usb connector, pulling the battery/sim, setting the UART using *#7284#(PDA, mtp+adb), multiple computers, and multiple cables(including the Samsung one) and the phone still doesn't ever think its connected to a host. So today I decided to use my php warranty service which meant I had to restore stock recovery and rom. So I grabbed mobile odin and a stock UVLDJA image. Ran Triangle away once to clear the counter, and another time to verify it was at zero, and installed the full image via mobile Odin. When the phone booted back up, it successfully installed the rom only the flash counter is back at one and now I have lost root. If I had used my head I should have flashed just the recovery first but I wasn't thinking....
Any suggestions on how to get root back? I read these forums quite a bit and I am thinking that I am SOL but hoping maybe someone has a suggestion I haven't seen yet.
Dlkiser said:
So the short question is if there is any way for me to get root without a working usb port?
Last week I plugged in to charge my phone overnight with the phone off. In the morning, I was surprised to find that the screen was on and what should have been a full green battery was instead a scrambled image that kind of looked like a battery. I powered on the phone and it worked so I thought nothing of it but later on that night I needed to pull a file off my phone via usb and realized that the phone will no longer detect the usb host, ie. no mtp options whatsoever. It at least does still charge.
Since then I have tried cleaning the usb connector, pulling the battery/sim, setting the UART using *#7284#(PDA, mtp+adb), multiple computers, and multiple cables(including the Samsung one) and the phone still doesn't ever think its connected to a host. So today I decided to use my php warranty service which meant I had to restore stock recovery and rom. So I grabbed mobile odin and a stock UVLDJA image. Ran Triangle away once to clear the counter, and another time to verify it was at zero, and installed the full image via mobile Odin. When the phone booted back up, it successfully installed the rom only the flash counter is back at one and now I have lost root. If I had used my head I should have flashed just the recovery first but I wasn't thinking....
Any suggestions on how to get root back? I read these forums quite a bit and I am thinking that I am SOL but hoping maybe someone has a suggestion I haven't seen yet.
Click to expand...
Click to collapse
Checking your flash counter in TA trips your counter, that's why it's at 1. Use mobile Odin to flash root66 to get rooted again.
Sent from my SGH-T999 using Tapatalk 2
Towle said:
Checking your flash counter in TA trips your counter, that's why it's at 1. Use mobile Odin to flash root66 to get rooted again.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, thanks for the explanation on the counter. Don't I need root already to run mobile Odin?
Dlkiser said:
Ok, thanks for the explanation on the counter. Don't I need root already to run mobile Odin?
Click to expand...
Click to collapse
Oh, duh! Yes lol you do. There would be no other way. Have you tried a factory reset then try to connect your phone? You could also try to install Kies on your PC to make sure all drivers are correctly installed.
If you wouldn't have said you have tried other cables, I would have for sure thought defective cable. Some cables are also charge only.
Sent from my SGH-T999 using Tapatalk 2
Towle said:
Oh, duh! Yes lol you do. There would be no other way. Have you tried a factory reset then try to connect your phone? You could also try to install Kies on your PC to make sure all drivers are correctly installed.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, did the factory reset along with all of the other suggestions I could find. I typically try to avoid Kies and since I cannot even get the device to enumerate I'm pretty sure it's not driver related.
I think my only hope would be getting root or twrp intalled via stock recovery or adb over wifi.
Thanks, I appreciate the help.
download Odin3 v1.85
Put your phone in download mode (vol down=menu=power then after the screen comes up press vol up
plug the phone usb to the computer,
run odin
the first box on the top left should have a colored highlight (the ID:COM )
if that pops up, your phone is 99% functioning correctly, and only problem is in your computer.
When trying do do a regulad usb transfer to the computer:
I have noticed, sometimes I have to connect, wait a bit (like maybe 2 minutes)
then disconnect the cable for about 15 sec then connect again, and it pops up after a minute
you could also try this:
open explorer on the computer(double click on my computer) and see if there is a t999 in your left pane. Sometimes the autorun function in the
computer gets farkled and it does not open automatically and you have to do it manually,
Good luck & Aloha !
Go to galaxys3root.com and follow his t.mobile root tutorial WORD FOR WORD. USE THE USB THE PHONE CAME WITH AND KILL SAMSUNG KIES. also run Odin before you connect the phone to Pc, should be no problem bruh once it took me a couple of hours making love to my comp before I got a colored com box. And use a windows PC Mac suxx for this kind of.
Sent from my SGH-T999
I've basically given up trying to get the usb port working... I am convinced this is a hardware issue. Nothing shows up in the device manager when I plug in the phone whether USB debugging is on/off or I am in normal mode or download mode. The phone will never bring up the MTP options in the notification bar either. Again this is with multiple cables on 2 different comps where it used to work just fine. I think whatever bad charge experience I had last week damaged the USB host controller on the phone.
I think what looks promising now is using adb over wifi(http://forum.xda-developers.com/showthread.php?p=26844535) along with root via adb(http://galaxys3root.com/galaxy-s3-root/how-to-root-u-s-canadian-dual-core-galaxy-s3-on-mac-osx/). I can't do this at work but I'll follow up tonight on what will hopefully be success in case this could help someone else out.
Edit: Ugh, some quick googling shows that I need either root or working USB to make adb over wifi work.
Would you want to replace your chatging port?
Sent from my SGH-T999
AppzTheGawd said:
Would you want to replace your chatging port?
Sent from my SGH-T999
Click to expand...
Click to collapse
I don't think so.... the micro usb port is mounted on the main board and short of replacing that entire board it would be a ton of time/effort for something that I don't exactly think is the problem.
Dlkiser said:
I've basically given up trying to get the usb port working... I am convinced this is a hardware issue. Nothing shows up in the device manager when I plug in the phone whether USB debugging is on/off or I am in normal mode or download mode. The phone will never bring up the MTP options in the notification bar either. Again this is with multiple cables on 2 different comps where it used to work just fine. I think whatever bad charge experience I had last week damaged the USB host controller on the phone.
Click to expand...
Click to collapse
This happened to me, and it was from using different devices in the same port (with same cable). I switched ports and it worked. Might not work for you, but worth a mention - it really stumped me and I tried everything including restoring the OS to an earlier point.
Sent from my SGH-T999 using xda app-developers app
Dlkiser said:
I don't think so.... the micro usb port is mounted on the main board and short of replacing that entire board it would be a ton of time/effort for something that I don't exactly think is the problem.
Click to expand...
Click to collapse
Now that S3's are getting older, more people will be losing their functional USB ports. I found holding the phone vertically with steady even pressure on the plug was the trick to getting a solid connection on my flaky port, at least enough to get stock back (to send it back). That was the longest 15 minutes of my life (OK, not, but it was in the top 10, mostly because it was simultaneously nerve-wracking and insanely boring).
I tried de-soldering a usb port on a Galaxy S. Yeah.... To say it mildly, the way Samsung sets them up is booby-trapped. You can't get the existing silver solder hot enough to melt without toasting the board somehow. The boards are also wafer-thin and dimensional on both sides. Despite generally having a knack for fine tuning and detail work (thanks to estrogen or something), I felt like an ogre in a doll house. I definitely would suggest having all the (exactly) right tools in place before tackling it. Even then it might not be the port itself, but something between the actual port and the other components.
One other thing to note, Mobile Odin is an amazing tool, but it's even ***more crucial*** than regular Odin to get your ducks in a row before you flash. Know exactly what you are flashing what your next steps are, and what your results are supposed to be. One thing in particular: if you flash a stock ROM, it includes stock recovery, and you will lose root. make sure you've run Triangle Away before you flash stock (which won't trigger your counter, but anything else will).
I plan to keep the Triangle Away and Mobile Odin apk's ready on ExtSD to install, and a copy of a stock image (ROM) as well, from now on, on all my phones. You never know when that port is going to give up the ghost.
Just thought I'd add a couple things here. More times than not, when someone thinks their usb port on the phone is bad, it's actually just the cable. Even if the cable works on something else, or works to charge the phone. They ruin much, much, more easily than anyone wants to believe! Especially when you plug/unplug it as often as with a phone.
As for Mobile Odin, I fully agree! It's one of my favorite apps by far! But if you're going to keep stock firmware handy, which I highly recommend, you may as well keep the root66 version. Flash back with that, then run triangle away, then in SuperSU, choose full unroot. Then all you need is a factory reset. Making TA the last step makes for far fewer user mistakes.
Sent from my SCH-I535 using Tapatalk 4

[Q] USB connection

Hey,
I have looked everywhere found many tricks and tips, guides, programs, drivers, yet i'm still have problems. I think that it could be problems with my phone. I recently bricked my phone (installed a rom from a different note 2 version and was stuck in a boot loop). Went to go plug in the phone to restore back to stock and the phone wasn't detected. It was a new laptop so i figured it was a driver issue. Installed the drivers still nothing. Long story short I have installed multiple drivers, Note 2 toolkit (mskip big thanks), Samsung Kies, and Odin (all at separate times) all in an attempt to get this phone connected. I have tried 2 different USB cords, different plug-ins, different computers yet still nothing. Now I have gotten my phone back to stock but went to install a new rom and now it wont load past the boot screen. But that was after my trying for a whole day of plugging in and unplugging before 1 time it was connected. I can not understand the issue besides it being my phone. I don't have anything else to try besides plugging it in and out over and over for the 1 time it decides to work and connect. I am getting very frustrated with this because I currently have no phone. Is their a way to tell if the connector is messed up in any way? I'm really needing help because nothing i'm doing is working.
Steepgnomeking said:
Hey,
I have looked everywhere found many tricks and tips, guides, programs, drivers, yet i'm still have problems. I think that it could be problems with my phone. I recently bricked my phone (installed a rom from a different note 2 version and was stuck in a boot loop). Went to go plug in the phone to restore back to stock and the phone wasn't detected. It was a new laptop so i figured it was a driver issue. Installed the drivers still nothing. Long story short I have installed multiple drivers, Note 2 toolkit (mskip big thanks), Samsung Kies, and Odin (all at separate times) all in an attempt to get this phone connected. I have tried 2 different USB cords, different plug-ins, different computers yet still nothing. Now I have gotten my phone back to stock but went to install a new rom and now it wont load past the boot screen. But that was after my trying for a whole day of plugging in and unplugging before 1 time it was connected. I can not understand the issue besides it being my phone. I don't have anything else to try besides plugging it in and out over and over for the 1 time it decides to work and connect. I am getting very frustrated with this because I currently have no phone. Is their a way to tell if the connector is messed up in any way? I'm really needing help because nothing i'm doing is working.
Click to expand...
Click to collapse
Have the same issue. I am trying fr a work computer, internet restricted, no kies. Now can only recognize note 2 as a camera. When I switch thw usb settings in android, I get the not supported box. Same thing happens at the home computer. I left bb for this??
This is a simple hardware fail and needs to be taken in for warranty repair. The fact that it's bricked, we'll you're just gonna have to cross your fingers and hope they don't charge you for a new one.
Or you can try a jig to get it into download mode and try to push a rom through.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Thats what i'm going to do take it in and see if they can fix it but i want to get it back to stock firmware before but not being able to plug it in to update it is kinda ruining that plan.
Well I turned in 3 notes with custom roms that were rooted and I never got charged, but I always run a stockist rom.
What rom did you flash?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Are u able to boot in recovery?
PM me if u need help
Sent from MOON......
Can you boot into recovery? If so then you can push a file to your SD card using adb. If your having problems with Samsung drivers or what ever good way to test is connecting your phone to a Linux box and setting up udev and adb. Then you can do a adb device command and see if it sees it.
If you have the time to install Linux on a extra hard drive or duel boot you can connect using adb.
Nice thing about Linux is that you can connect directly to the USB device using udev and the device id and with ADB you can push a file onto your phones SD card. Here's a good how to
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Sent from my SGH-I317 using xda app-developers app

[Q] Stuck in Download Mode (can't get to recovery)

My wife has a T-Mobile GSII. I successfully rooted it via ODIN to CWM-SuperSU-v0.87. My wife wanted me to put it back to stock so I unrooted it to T989UVLE1. It was killing the battery (and some other weird things began happening) so I want to re-root it but now the USB port is not working so I can't ODIN it back to the rooted MOD.
When I plug in the USB cable connected to my PC it charges but it doesn't connect for data. My computer doesn't see it, and it doesn't show the USB icon in my notifications on the phone either. When I try to boot to recovery, it goes into download mode (even if it's not connected to a USB cable). ODIN doesn't see that it's connected so I can't change the ROM.
Now, I also have the SGH-T989 and used this same process successfully. When I connect it to the same PC with the same cable I can do anything I want, ODIN works, I can get to recovery mode when it's not plugged into a USB. It's as if my wife's phone thinks it's connected to a USB even though it's not and when it is connected it doesn't recognize it. I'm thinking I could send it in for warranty figuring the USB port is dead but the ROM that's on there isn't stock and I'm afraid I'll get into hot water with TMO. For grins, I uninstalled all of my Samsung drivers and reinstalled them, and did the same thing with Kies. My phone connects fine, my wife's doesn't at all.
Anyone have a good idea? I've looked around on here all day and can't find anything that will work for me.
Once you Odin back to stock on your wife's phone you lost the recovery. Use [URL="https://www.dropbox.com/s/jdfj55rcj6p5c7c/odin3%20v1.85.exe]this version of Odin[/URL].
Remove battery
Open Odin (the one I provided)
Put battery back in after about 20 seconds
Hold volume up and volume down
Connect phone to computer via USB
Download mode should pop up on the phone and Odin should recognize your phone
After that just Odin a recover onto her phone and flash supersu to root
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Problem with your link...
The ODIN in your post doesn't lauch an ODIN session. Instead I get a dialog box that says, "Odin3.ini" and then seven boxes with an OK button. Now I'm really baffled.
stecina said:
The ODIN in your post doesn't lauch an ODIN session. Instead I get a dialog box that says, "Odin3.ini" and then seven boxes with an OK button. Now I'm really baffled.
Click to expand...
Click to collapse
Sorry about that man. That was my faul, the dialogue means you need the ini file for Odin. I've reuploaded everything in a zip file here. Just unzip to your desktop and follow the same steps I provided earlier.
*note* the zip file includes the two Odin files you need...just open Odin.exe. A recovery tar file and a superuser zip file...the superuser zip I provided outdated so just use your root zip file.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Didn't Work
Okay, so that returned the same result as before. Your method also didn't make my computer (or ODIN) think it was connected to anything, so I'm unable to get the root onto the phone.
What can I try next?
stecina said:
Okay, so that returned the same result as before. Your method also didn't make my computer (or ODIN) think it was connected to anything, so I'm unable to get the root onto the phone.
What can I try next?
Click to expand...
Click to collapse
You can try reinstalling the drivers. If you don't have them you can download it here. Just run the exe file. Also if you have Samsung kies on your computer that could be causing the interference so remove it
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
I have uninstalled and reinstalled drivers as well as Kies. Remember, I have another phone of the same model that is easily recognized by my computer AND ODIN. I'm pretty sure there is something wrong with my wife's USB port. That's why I want to restore it to stock, so I can get a warranty replacement.
Sent from my SGH-T989 using xda app-developers app
stecina said:
I have uninstalled and reinstalled drivers as well as Kies. Remember, I have another phone of the same model that is easily recognized by my computer AND ODIN. I'm pretty sure there is something wrong with my wife's USB port. That's why I want to restore it to stock, so I can get a warranty replacement.
Click to expand...
Click to collapse
There is a flashable stock zip on the first post here:
http://forum.xda-developers.com/showthread.php?t=1858435
Scroll down to T-Mobile t989 UVLH1 and click show content. It's at the bottom.
---------- Post added at 11:59 PM ---------- Previous post was at 11:45 PM ----------
meekrawb said:
There is a flashable stock zip on the first post here:
http://forum.xda-developers.com/showthread.php?t=1858435
Scroll down to T-Mobile t989 UVLH1 and click show content. It's at the bottom.
Click to expand...
Click to collapse
After re-reading your OP I see you can't even get into recovery. I don't think there is anything you can do but take it to T-Mobile and hope for the best. Or send it to Samsung...
Have you tried using a PC which you have not used for flashing your own?
I realize its unlikely to make a difference, but trying to flash your wifes using a "virgin" PC is at least worth a shot...
Chris
Another thing you could try is disconnect the phone from the PC (leave it powered up and everything), load up device manager in windows then plug the phone in and watch for device manager to flicker or do anything. I'm thinking maybe your phones are the same (T989's) but possibly a different revision that requires a different driver. Device manager will tell you if the phone was able to start or not. One thing that SOMETIMES works with windows computers (although it sounds silly) is to use a different USB port. I always use the one on the back of my computer as it is directly connected to the motherboard and thus offers a shorter path for the data to travel. I have had issues using front USB ports with devices before (my MP3 player will time out during large data transfers if I use the front USB port sometimes).
Also, is "debug mode" turned on on your phone? It is under development tools. If it is off, try turning it on. And with it on, do you get any results from running "adb devices" (presuming you have the android SDK installed or a copy of adb floating around on your computer from some other tools)?
And lastly, does the phone charge when the USB cable is plugged in? It is unlikely that 2 of the pins on the USB connection are bad without them all being bad.
Good Ideas!
Well, I've tried a couple of those ideas. The Device Manager idea revealed nothing. Nothing changes in the Device Manager when I plug in the phone. The phone DOES charge, so like you said, it's likely a software issue not hardware since two of the pins seem to work fine. BTW- the phone acknowledges it has been plugged in, too, by beeping. The computer does not.
I had tried using different computer USB ports because I have found the same to be true as you: the ports on the back go directly to the motherboard but the ones on the front are actually going through a hub, though it's inside the case, the computer sees it as a hub.
I don't have ADB Devices. I don't have any experience with that program...can you advise me? Next up, trying on a virgin computer...
Thanks for the ideas. I've got to get this worked out or my wife's going to DIE. Currently, the home button doesn't take her home, it takes her to this weird Clock App based lock screen/screen saver. Anyone have an idea how to correct that problem itself?
UPDATE: I tried to install and run ADB Devices and it didn't result in recognition by my computer.
Sending in For Warranty
It appears that this is my problem.
I took it to TMO and they approved a warranty replacement for a faulty USB port. Just in case anyone wondered.

SAMSUNG epic 4g stuck on boot screen after trying to restore Stock Rom

I was running CM10 but I got a message whenever I got into the Camera App that said "Unfortunately, Gallery has stopped working", after a research in here I found that I wouldn't get that msg again if I installed this "gapps-jb-picasa-20121011-signed" thing.
I did, but when I got into my Camera App, I didn't have the other options like "Image Effects" and all that stuff.
So, what I did was to Restore my phone from my BackUp folder that I've created before installing CM10, but for my surprise I got a msg saying "VolumeError" or something like that and other things that I can't really remember... and as a good Mexican that I am, I ignored it and hit the Reboot System Now..
What happened next almost made me cry...
I was expecting to get in my stock rom without any problems and yadda yadda but... OH SURPRISE!
I got stuck on the boot screen, where it says "Samsung" and the website of it and I didn't freak out... I waited like 5-6 mins and took the battery out. When I turned again, I tried to get in Recovery Mode but the screen just kept turning off and on and saying the exact same thing, the "Samsung" logo and it's website.
I hope you can help me and please answer me. I don't know if I'm 1000000% screwed but I will only wait for the worst. Sorry for my bad english and don't hate me for being mexican
I don't know if I can get into my phone from my PC but whenever I plug my phone in, it just loads it as if it was in Charging Mode
PLEASE HELP ME!
I BEG YOU!
Flash again CM10 with wipe data, cache, dalvik
If still stuck
Odin to stock ROM, you can search on google to odin the epic
Sent from my JellyBeer v.4.14 epicmtd (b3)
Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator
Like @dropple said, it seems you stuck "SAMSUNG" and in this case you can't get into recovery so you can't flash CM10 as of now. Go find some tutorials and Odin back to stock via download mode. Then install CWM recovery if you want and do whatever you like. Should get you outta trouble.
Sent from HTC Incredible S @ PACman v21
AndyYan said:
Like @dropple said, it seems you stuck "SAMSUNG" and in this case you can't get into recovery so you can't flash CM10 as of now. Go find some tutorials and Odin back to stock via download mode. Then install CWM recovery if you want and do whatever you like. Should get you outta trouble.
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
Thanks to Everyone!
I solved this like 2 hrs after all this happened.
I got it by Odin. I couldn't go into Recovery Mode, but I got in Download Mode and do it by Odin.
Sorry, I'm a n00b to all this.
Greetings from México and thanks for all your support.
Here's a weird one for you,
Same thing as OP stated. Device is stuck on logo. Can't get into CWM. Was on People's Rom. Device was lagging really bad. Then the system requested superuser permissions. Yes the system requested. Being as I did not request it, I declined. Shut the device down to see if that would help with the extremely bad lag (i mean BAD lag. Like..........................ok it does something then.......................................................................ok it does something else. 10-20 seconds lag)
Connect device to computer to Odin back to Stock or whatever ROM would have worked, computer recognizes device..... wait for it.......
But in download mode Odin does not see it. Com Port will not illuminate. Tried 3 different cables. Tried 6 different USB ports on computer. Still nothing.
Any ideas, because I'm all out?!?
To the OP:
I would follow the instructions in this video from the part where qbking77 talks about putting the phone in download mode, as you presumably did when you first rooted your phone. Download all the files linked/referenced on the site, especially the Samsung mobile drivers, Odinv3 1.87, CWMRecovery, and the deOxed versions of the stock ROM. In sum:
1) get into recovery mode by holding onto the volume down, camera buttons, and then without letting either of those go, press and hold the power button.
if you get into recovery mode, skip to step 4
2) while your phone is completely off, hold onto the "1" button on the slide out keyboard first, then without letting the 1 button go, press and hold the power button until you're in download mode.
3) flash the version of Clockworkmod
4) once in recovery mode, wipe your phone, clear the cache, and dalvik cache, and then flash the deOxed version of the stock ROM
niteNarmor said:
Here's a weird one for you,
Same thing as OP stated. Device is stuck on logo. Can't get into CWM. Was on People's Rom. Device was lagging really bad. Then the system requested superuser permissions. Yes the system requested. Being as I did not request it, I declined. Shut the device down to see if that would help with the extremely bad lag (i mean BAD lag. Like..........................ok it does something then.......................................................................ok it does something else. 10-20 seconds lag)
Connect device to computer to Odin back to Stock or whatever ROM would have worked, computer recognizes device..... wait for it.......
But in download mode Odin does not see it. Com Port will not illuminate. Tried 3 different cables. Tried 6 different USB ports on computer. Still nothing.
Any ideas, because I'm all out?!?
Click to expand...
Click to collapse
Do you have the mobile drivers installed on the computer you're trying to connect your phone to?
Yes. The drivers have been installed previously. The computer will see the device as "Samsung SPH-D700 Card USB Device". But Odin3 1.85 will not see it.
EDIT: When I put device into download mode and connect to computer, the computer only sees it as "Gadget Serial".
niteNarmor said:
Yes. The drivers have been installed previously. The computer will see the device as "Samsung SPH-D700 Card USB Device". But Odin3 1.85 will not see it.
EDIT: When I put device into download mode and connect to computer, the computer only sees it as "Gadget Serial".
Click to expand...
Click to collapse
Uninstall and reinstall drivers.
Sent from my SPH-D700 using Tapatalk 2
Have already done that. But just for laughs, I did do it again with no change.
can you get your D700 into download mode as described above?
Yes I can get into download mode but without Odin recognizing the device (not computer. The computer recognizes the device) there is not much I can do.
niteNarmor said:
Yes I can get into download mode but without Odin recognizing the device (not computer. The computer recognizes the device) there is not much I can do.
Click to expand...
Click to collapse
Try to install another version of Odin or getting Odin from a different server.
My phone is fully recovered and now I'm only SuperUser 'cause I don't want any CM by now.
Greetings from Mexico!
I'm using the same version of Odin I used to root the device. Would a different version really help and if so, what version to use?
I actually have a different version of Odin I used for another device and tried that one as well, with no luck.
EDIT: I have now downloaded and tried 4 different Odin programs with no avail. Again, that makes 6 Odin programs, 6 different USB ports, 3 different cables with the same exact results. The computer recognizes device but Odin will not.
niteNarmor said:
I'm using the same version of Odin I used to root the device. Would a different version really help and if so, what version to use?
I actually have a different version of Odin I used for another device and tried that one as well, with no luck.
Click to expand...
Click to collapse
Had a simular issue when I had two odins on the same computer, for a lark and as I had nothing better to do, tried installing drivers and one version of odin to a vertual machine running vista and checked to see if my computer's vertual machine would reconize and it did, I took it as a sine that at one point I had done something to my computer's main os sometime between rooting my epic 4g and frying it (recovering from a backup from a different parition layout I think, bad times with bootloops and seeing way to much of the samsung logo.) So as I'm not brave enough to run odin on vm I instead removed all of odin from my main os and all of the samsung drivers, then reinstalled rebooted and repluged my epic in, got reconition and reflashed with plesure.
The other issue might be that your computer is reconizing the device and try/failing/hanging and not allowing odin in. Had an issue when my computer was failing to pop up a 'what do I do with this' window and hanging round in the system. A reboot with the internet unpluged strangely solved that for some reason, might be the reboot might be the combo, but I find better connection reconition with my computer when I've fewer things connected.
Don't mind the spelling to much I clean up with my other device.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app
One question I noticed that hasn't been asked is when you plug the phone into the computer while the phone is on, is usb debugging checked? If not, check it, and reinstall drivers again.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
One question I noticed that hasn't been asked is when you plug the phone into the computer while the phone is on, is usb debugging checked? If not, check it, and reinstall drivers again.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Phone does not boot past the "Samsung - www.samsung.com" logo. Plus, as with all of my devices, USB debugging is always checked.
Thanks for the suggestion though. Always helps to double check things.
I believe I am going to take it to Sprint tomorrow.
If I can't get into it, they should not be able to get into to it either. If they can't get into it, HELLO WARRANTY....
Perhaps before doing the whole getting found out thing with the return center, perhaps they do know what they're doing, try rolling this link past your eyes?
http://forum.xda-developers.com/showthread.php?t=773032
I know I've been in your boot problem situation and recovered, it just took persistence and eyenumbing amounts of reading.
Note On the multiple Odin, USB, and driver installation: if you've access to another computer it could be worth wile to run once though on a previously virgin computer, meaning your phone and computers' USB's have never touched. Just do the installation, rebooting, and plugging in exasperatingly meticulous order.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"
Yep tried the "virgin computer" computer as well. The computer sees the device but Odin does not. Com light will not illuminate.
Sounds grim.
So to rap up all the cables, plugs, computer, and software with odin is out of the debug process.
So I did some digging into the past and if your computer is reconizing and odin is not then ADB (android debug bridge) and the sdk are the other option
http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/33427-how-access-your-adb-shell.html
Ran across this and it might just be what you need. Its not quick but it has worked for me in the past.
The other thing that may work is ejecting the sd card and battery before doing anything. Though its likely something you've already tried.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"

Categories

Resources