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.
Related
I am trying to flash epic back to stock rom, but when i run odin and plug in the phone in download mode it keeps on saying it's been added and then removed repeatedly. Any help?
Windows says this?
You put the phone in download mode, start Odin and then connect the phone to the PC.
I'd check to be sure you're using the usb cable that came with your epic. Using others can have mixed results, even though they fit.
Check the connection to the phone; be sure nothing is in the connector.
Try a different usb on your PC.
Can always try to reboot the PC as well.
Good luck
Now it works, but when i select the 528 pit, it's stuck on Setup Connection, but if i use the 512 pit it just says it failed.
Going to second the try a different usb port, although if you have any other micro-usb cords that have thicker cables than the samsung one, use that for flashing.
Also may want to reset computer after you have it fail. It seems to mess with something in windows or leave a process open that keeps it from working right
Also gonna ask a dumb question, you do have a stock epic rom that you're trying to flash along with the pit and you are clicking repartition in odin right?
Sent from my SPH-D700 using XDA App
I was on the DK28 rom before but now since 2.2 has been released officially i want to flash to stock and then get the official version. The problem is everytime i run it, it's on the SetupConnection part but it never gets past that. no i didnt repartition it.
The only suggestion I can offer other then the usual stuff (check connections, USB ports, drivers, etc) is to redownload everything. It's possible that the download could have been corrupted for whatever reason. It's happened to me once when I was trying to Odin back to stock.
Hope this helps.
So now i got it to run, but the phone it self booted into a green screen, and in the list in Odin it's stuck on modem
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Sorry to hear that. This is something I learned (second hand, thank god) when I had my Galaxy S1. Odin can simultaneously be the best and worst tool you use.
Sent from my Galaxy Nexus
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
ericaraj said:
I just wanted to share what happened before it was bricked so others could possibly avoid it (and because I didn't think I could brick a Nexus...).
Yesterday my USB connection began failing intermittently. It would charge, but the computer would not always recognize the device. On Windows 7, I got an error message saying that the device had malfunctioned and that I should try reconnecting it. On OSX, Android File Transfer could not find my device. Unplugging and plugging back in got the computer to recognize it about 20% of the time.
I went back to stock using fastboot, but I had to battle with it for several hours because of how unreliable my USB connection was. On stock I still had the problem, but I wondered if I had just gotten unlucky during flashing since I had so many failed attempts. Then I decided I would try again with Odin since it just takes one flash to go back to stock. Unfortunately, my USB connection failed again during the Odin flash. I pulled the battery (this could be the true problem but I couldn't get the flash process to start over otherwise) and at this point my phone was bricked. The screen showed an image with a phone and a computer with an exclamation point between them. I couldn't get to my bootloader and couldn't try any other fixes because my computer would no longer recognize my phone at all.
Long story short, if your phone's USB connection begins to malfunction then don't use Odin.
Click to expand...
Click to collapse
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
rayiskon said:
There is a chance it's not totally bricked, that happened to me on an other samsung device while i was flashing with odin. U pulled the battery too early.i also had that black screen with the yellow pc and exclamation mark, try another usb port in ur pc and try to flash again with odin, if not, take the battery out and keep it out for a while (i don't know, 30min for example) then try odin again... u should be able to enter download mode somehow despite the screen u got now.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
I had a feeling that it wasn't truly bricked, but since my phone's USB driver (or whatever aspect of USB data transfer) was malfunctioning I couldn't do anything about it. I think of it this way: if in that state my phone had a 5% chance of being recognized by Odin, and if my phone already had less than a 20% chance of being recognized before the soft-brick, then I had a 1% chance or less that it would even show up in Odin and even lower odds at a successful flash. Regardless, Verizon agreed to send me a warranty replacement.
iCaptivate said:
Your phone is not bricked. This happened to me on my Vibrant countless times. Not it's basically trial and error to get it to show up on Odin, but use a reliable USB connection, like another port on your PC or something. Trust me, you're fine. I was ****ting myself when this happened for the first time, but it's just like download mode, you can still restore to stock.
Even if he can't enter download mode, if Odin recognizes the phone while the screen with the exclamation mark is up, he'll be fine.
Click to expand...
Click to collapse
Same here with the vibrant. IIRC there was a special way to get your phone to recognize Odin when it happened. Something like plugging in the phone to the computer and then pulling the battery. Odin even worked when I borked a flash and the screen wouldn't even turn on. I would think the nexus could be brought back similarly.
But if the USB port is on the fritz I'm not sure I would want to bring it back.
As far as I'm concerned Odin is the worst thing you can hook up to your devce. No single program has bricked more devices than Odin.
______________
Just Flash It !!!
on my old SGS1 there was chance get back bricked device by method called "JIG"..(its hardware way get back download mode) but i dont study it more...
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
try to use another cable to connect ur phone to pc
just flash stock via odin, it's not bricked.
My s2 sometimes has that problem when i flash stock
eksasol said:
I don't think its bricked, I once restore my phone from a black screen that Odin still recognized as download mode. The drivers can get iffy, do you have a third comp that you can install fresh drivers on. Also is your USB jack on the Nexus loose? Sometimes it really is due to your PC's USB connection. I also had issues with cheap blackberry cables and had to use higher quality ones.
Did you try going into download mode by connecting it to the PC while with battery removed and hold (whatever buttons to boot it into download mode), then insert the batteries. Or try entering using a jig.
Also a bit lazy of me (on phone), but can someone point me to where to get Odin images for the Nexus?
Click to expand...
Click to collapse
I appreciate the advice but I no longer have that phone. My replacement should come today.
With regards to the drivers, I was referring to the drivers on the phone not on the computer. I honestly don't know if there are USB drivers on the phone (I would think there are) or even if those drivers were causing the malfunction.
The first thing I'm doing this afternoon is plugging my replacement phone into my computer. If the new one doesn't work right then I'll have to make a trip to the Apple store because the problem will almost certainly be my laptop. I'll also owe a big apology to Verizon.
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.
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"
I've had this old note II pretty much since it came out have had plenty of ROMS on it and normally have had no problems. I recently had SlimKat on there and I was having battery life issues so I reinstalled it to no avail, so then I tried moving to Blisspop and that fixed the battery life issue some but I was having issues with crashing and the proximity sensor not registering during calls. I found a thread with this issue that directed me to Shift Kernal as a solution to the proximity sensor and crashing issues. I reflashed Blisspop, flashed the Shift kernel, then Gapps and now I have a brick. Upon turning on the phone it gets stuck on the Samsung boot screen. It won't open CWM recovery anymore to access my nandroid backups. I can get it into download mode but I cannot get my computer to recognize the phone as a USB device anymore. I have tried different drivers, cords, usb ports, and even different computers so I assume thats not the issue. Any suggestions would be helpful or even just telling me its a definite hard brick so I'll quit tinkering with it.
If you can get DL MODE it's not a brick...
Reflash of a stock rom via Odin should help...
Device could have partition damage...but I'd avoid the PIT flash until after the stock rom attempt..
I don't know what bootloader you have...but if you have version 4.2 or lower then flash a complete stock rom..
If you have 4.3 official or higher...then use an ODIN version from Zen Arcades threads as they don't contain the loader image...g
gregsarg said:
If you can get DL MODE it's not a brick...
Reflash of a stock rom via Odin should help...
Device could have partition damage...but I'd avoid the PIT flash until after the stock rom attempt..
I don't know what bootloader you have...but if you have version 4.2 or lower then flash a complete stock rom..
If you have 4.3 official or higher...then use an ODIN version from Zen Arcades threads as they don't contain the loader image...g
Click to expand...
Click to collapse
I can get it into download mode but when I connect it to a computer its not recognized as a device and therefore doesn't show in ODIN to flash those ROMs. Is there anyway to force recognition of a USB device. I've tried pretty much every combination of cord, usb port, driver and computer to get it to connect to ODIN but haven't had any luck.
hlhastie09 said:
I can get it into download mode but when I connect it to a computer its not recognized as a device and therefore doesn't show in ODIN to flash those ROMs. Is there anyway to force recognition of a USB device. I've tried pretty much every combination of cord, usb port, driver and computer to get it to connect to ODIN but haven't had any luck.
Click to expand...
Click to collapse
Ouch...
Well....beyond switching versions of Odin...(you've likely done this already)...the only action you could take would be a direct ADB push to the device...
It's been 2 years since I've attempted that...and can't remember the thread locations for the tutorials.
There is also the possibility that the EMMC is damaged.
My second device had this failure and I never recovered it...
I'm sorry that I can't provide links...but I know the threads exist.
So start a search and I'll do the same...g
Edit:
I keep coming back too a PC environment problem...(perhaps)
Run Odin as admin only...and quadruple check those USB drivers...making sure to completely uninstall the old version before loading new drivers.
Also..try using Odin 1.85....not 3.09...as it is a bit more reliable.
Also use only a factory cable connected to the PC mother board only...no front ports...
Plug in the device in download mode then reboot the PC and then open Odin...
Brainstorming here and hoping it'll trigger that dang "added" symbol for ya....g
Thanks I'll try those and see what happens!
I prefer Odin 3.07 on a Win7 machine.
I see the thing...
You damaged your bootloader, try re-flashing it through Fastboot on ADB, if tour pc does not recognize the device then try to install the latest USB drivers for your model.
Sent from my VF-895N using XDA Free mobile app