Related
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.
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"
Hello everyone...
I was updating the phone recently, and went to reboot it (cyanogen mod ROM btw) and now I have no idea what it did but it is now stuck on the Samsung logo, and their is no recovery I can use on it. Only DL mode works.
I tried to use Odin to relfash but the problem is on both my Windows 7 and Windows 8 computers, they install the drivers, but they still fail to recognize the phone when I plug it in!
I have tried different USB ports, a full driver uninstall, multiple USB cords and the computer refuses to recognize the phone saying "USB Device not recognized"
Again, the drivers install fine, and I did a reboot after each install and uninstall. No luck.
I didnt even install drivers on my W8 netbook and I was able to flash back TWRP using Odin and Download mode yesterday when my attempt at flashing TWRP 2.6.0.4 originally failed.
Fire up download mode, then open up Odin (you should see a COM port open), load up what you need to install, then flash.
What are you trying to flash using ODIN? A bootloader or a ROM?
"BootLooping GhostBrick"
Holy crap! you too? I'm experiencing the same thing too bro. its my girlfriend's phone tho. she's borrowing my Nexus 4 while I work on fixing her SGS2...I seem to have contracted a serious case of the BootLooping GhostBrick, just like you did, right after updating. I went through the same steps troubleshooting as you did, and ...its a guess, but I'm starting to figure the solution will probably include: 1. using ADB to push sum files to the phone, or otherwise somehow reflashing stock firmware from the PC.
2. Re-Root the dam thing and flash a kernel with a recovery (like CWM or TWRP) using rom manager...and 3. Considering installing a ROM of my choice Like PACMAN, or Cyanogenmod.....hmm...Yum
anyway, the search for the vaccine to this dreadful affliction begins. Please post if you find something, I will too.
---------- Post added at 10:21 AM ---------- Previous post was at 10:13 AM ----------
nagoshi said:
I didnt even install drivers on my W8 netbook and I was able to flash back TWRP using Odin and Download mode yesterday when my attempt at flashing TWRP 2.6.0.4 originally failed.
Fire up download mode, then open up Odin (you should see a COM port open), load up what you need to install, then flash.
What are you trying to flash using ODIN? A bootloader or a ROM?
Click to expand...
Click to collapse
...true, I second that. I'm doing this as we speak.
No Go Mi Amigo... PC still No read
vdorvilus said:
Holy crap! you too? I'm experiencing the same thing too bro. its my girlfriend's phone tho. she's borrowing my Nexus 4 while I work on fixing her SGS2...I seem to have contracted a serious case of the BootLooping GhostBrick, just like you did, right after updating. I went through the same steps troubleshooting as you did, and ...its a guess, but I'm starting to figure the solution will probably include: 1. using ADB to push sum files to the phone, or otherwise somehow reflashing stock firmware from the PC.
2. Re-Root the dam thing and flash a kernel with a recovery (like CWM or TWRP) using rom manager...and 3. Considering installing a ROM of my choice Like PACMAN, or Cyanogenmod.....hmm...Yum
anyway, the search for the vaccine to this dreadful affliction begins. Please post if you find something, I will too.
---------- Post added at 10:21 AM ---------- Previous post was at 10:13 AM ----------
...true, I second that. I'm doing this as we speak.
Click to expand...
Click to collapse
.....well, so much for that attempt.... still cant get either the PC or Odin to Read....I just flashed CWM recovery using ODIN minutes ago with no problems, but now its borked too
vdorvilus said:
.....well, so much for that attempt.... still cant get either the PC or Odin to Read....I just flashed CWM recovery using ODIN minutes ago with no problems, but now its borked too
Click to expand...
Click to collapse
Reinstall Odin and the drivers for t989, then go get twrp 2.6.0.4 from techerrata.com/browse/twrp2/hercules then open Odin and put the phone in DL mode, now when odin connects make sure u open the recovery in PDA format and touch nothing else in Odin, flash twrp and ur good, this version is capable of dealing with 4.3 too with no issues at all
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Same issue
soupysoup said:
Reinstall Odin and the drivers for t989, then go get twrp 2.6.0.4 from then open Odin and put the phone in DL mode, now when odin connects make sure u open the recovery in PDA format and touch nothing else in Odin, flash twrp and ur good, this version is capable of dealing with 4.3 too with no issues at all
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Re-installing Odin and drivers still didn't get Odin to recognize the device in download mode. Windows 7 isn't assigning it any COM port, and nothing can be flashed unless Odin sees the com port the device is on. I used Goo Manager to flash TWRP 2.6.0.3 over my previous 2.6.0.0 version and now I'm stuck on samsung logo, can't reboot to recovery and PC won't recognize device in download mode. Anyone know a solution?
VermontKindBud said:
Re-installing Odin and drivers still didn't get Odin to recognize the device in download mode. Windows 7 isn't assigning it any COM port, and nothing can be flashed unless Odin sees the com port the device is on. I used Goo Manager to flash TWRP 2.6.0.3 over my previous 2.6.0.0 version and now I'm stuck on samsung logo, can't reboot to recovery and PC won't recognize device in download mode. Anyone know a solution?
Click to expand...
Click to collapse
Welcome to ur first soft brick, and as I said in ur other post u need to disable or removes Samsung kies before trying to use Odin as long as any part of kies is running even in background Odin won't see the device, also make sure u use factory/data approved USB wires, also try diff ports, sometimes Odin won't see com3 but will see com5, be patient and follow this and ull be fine, also twrp2.6.0.3 has been known to cause sftbricks, DL 2.6.0.4 from techerrata.com/browse/twrp2/hercules its the newest and 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Yup
soupysoup said:
Welcome to ur first soft brick, and as I said in ur other post u need to disable or removes Samsung kies before trying to use Odin as long as any part of kies is running even in background Odin won't see the device, also make sure u use factory/data approved USB wires, also try diff ports, sometimes Odin won't see com3 but will see com5, be patient and follow this and ull be fine, also twrp2.6.0.3 has been known to cause sftbricks, DL 2.6.0.4 from its the newest and 4.3 compatible
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, I wish I'd known that. Goo Manager automatically selected it as the latest recovery. I just can't get past the device not showing up as a com port issue at all. Is there any known way to make windows recognize it?
VermontKindBud said:
Yeah, I wish I'd known that. Goo Manager automatically selected it as the latest recovery. I just can't get past the device not showing up as a com port issue at all. Is there any known way to make windows recognize it?
Click to expand...
Click to collapse
Yes u need to make sure kies isn't running or installed on ur PC, if it is Odin won't see it
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Unrecognized by PC
VermontKindBud said:
Yeah, I wish I'd known that. Goo Manager automatically selected it as the latest recovery. I just can't get past the device not showing up as a com port issue at all. Is there any known way to make windows recognize it?
Click to expand...
Click to collapse
It's not a matter of trying different com ports, I can't get the PC or Odin to recognize the phone in download mode despite uninstalling kies, installing the latest drivers twice, 3 different OEM cables, multiple usb ports, nothing. when I plug it in, Windows doesn't make any sound like with other usb devices, nor does it try and search for drivers. Are there any other options short of JTAG repair?
VermontKindBud said:
It's not a matter of trying different com ports, I can't get the PC or Odin to recognize the phone in download mode despite uninstalling kies, installing the latest drivers twice, 3 different OEM cables, multiple usb ports, nothing. when I plug it in, Windows doesn't make any sound like with other usb devices, nor does it try and search for drivers. Are there any other options short of JTAG repair?
Click to expand...
Click to collapse
I was going to reply earlier, but I got side tracked and this guy is literally having the exact same problem as me. I tried multiple OEM cables, and ports and Windows recognized it but it still won't let me USE it. Odin (after re-install) still shows no connections or ports.
Also, yeah this phone isn't mine either, my Dads. He is using my old S3 for now and is quite mad with me hahaha.
So yeah, I have to re-cap...
-Updated through Goomanager.... (the culprit I am guessing)
-Rebooted
-Got stuck on the Galaxy S 2 screen
-Plugged in with 4 USB cables to three different USB ports
-Uninstalled and reinstalled Odin numerous times, each with a reboot between.
-Odin fails to recognize it
-Windows KNOWS IT IS THERE, and makes a sound when plugged in, however it says "USB Device not recognized"
Any more ideas?
Thanks for the help to guys it is very much appreciated. I will donate to the person that can help me out of this
Here is a screen shot of Windows with the phone in DL mode
LGIQEXPO said:
Here is a screen shot of Windows with the phone in DL mode
Click to expand...
Click to collapse
Do u have Samsung kies installed on the PC? If u do your going to need to remove all traces of it in order for Odin to see the phone, also search Samsung t989 USB drivers and install the specific driver for Hercules, if u can get the phone into DL mode its fixavke so don't stress to much, I use Odin v1.85, download twrp2.6.0.4 from this site techerrata.com/browse/twrp2/herculesif Odin still fails to recognize the device try diff PC, factory/data approved USB wire, an make sure kies is nowhere and it should work, pm me if u need more help I'll do what I can, but like I said as long as DL mode is accessible its only a soft brick...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
soupysoup said:
Do u have Samsung kies installed on the PC? If u do your going to need to remove all traces of it in order for Odin to see the phone, also search Samsung t989 USB drivers and install the specific driver for Hercules, if u can get the phone into DL mode its fixavke so don't stress to much, I use Odin v1.85, download twrp2.6.0.4 from this site techerrata.com/browse/twrp2/herculesif Odin still fails to recognize the device try diff PC, factory/data approved USB wire, an make sure kies is nowhere and it should work, pm me if u need more help I'll do what I can, but like I said as long as DL mode is accessible its only a soft brick...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Kies is no where in sight. I will try yet another PC as well as searching for Hercules specific drivers (any link?) When I get home. Thank you in the mean time
LGIQEXPO said:
Kies is no where in sight. I will try yet another PC as well as searching for Hercules specific drivers (any link?) When I get home. Thank you in the mean time
Click to expand...
Click to collapse
Just Google Samsung t989 Hercules USB drivers, download and install, it should work, like I said as long as DL mode is accessible it should be an easy fix...
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Omg....
I am experiencing the same problem. Did anyone find the solution?
Probably a faulty USB port. My computer shows that message all the time, only one of them works correctly. If not, you just need to install the correct USB Drivers, because even if you don't have them it should recognize your phone as a Samsung phone but will say that the drivers did not install correctly.
I upgraded from Stock 4.1.2 to Stock 4.3.3 (L900VPUBMK4) today. I did this via ODIN3 v3.09. Not my first time flashing a device. Not my first time with Odin. It upgraded no problem. Package installed, phone rebooted, on boot the package completed installation, rebooted again, and then came up shiny new 4.3.3.
Next step, of course, was to re-root. I went back into Download Mode, opened up Odin, plugged back in the phone, and NOTHING. It wouldn't connect to Odin. Mind you, this is the same Computer, Drivers, Cable, and Odin that I'd used 10 minutes beforehand and several times in the past.
I don't get it! I've tried re-installing my Samsung drivers, just for fun. I tried another cable. Also, when the phone's booted up in normal mode, the phone connects fine to the computer as a Media Device. I can't make this sucker connect to Download Mode all of a sudden!
ANY IDEAS?! Sure would appreciate it!
-Frif
Additional info
Not trying to bump (but glad).
Still no luck. Tried another computer.
Additional info:
My Download Mode reads:
ODIN MODE
PRODUCT NAME: SPH-L900
CUSTOM BINARY DOWNLOAD: Yes (1 counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX WARRANTY VOID: 0
RP SWREV: A2
Use a different port and a different cable. Reboot the phone into download mode, connect it to the computer, then load Odin. I've had issues where if i loaded Odin before connecting to the phone it wouldn't find a connection.
Sent from my SPH-L900 using xda app-developers app
No dice
ecs87 said:
Use a different port and a different cable. Reboot the phone into download mode, connect it to the computer, then load Odin. I've had issues where if i loaded Odin before connecting to the phone it wouldn't find a connection.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
No such luck. Still getting absolutely nothing out of Odin.
Is there ANYTHING I can maybe flash in Stock Recovery to get me anywhere?
I should also mention there's no USB connect/disconnect sound coming from the computer when in Download Mode. Although I can't remember if that's normal or not.
How are you getting into download mode? If you're using the 3 button salute, try adb reboot download in recovery (and vice versa).
Sent from my SPH-L900 using xda app-developers app
Nope
ecs87 said:
How are you getting into download mode? If you're using the 3 button salute, try adb reboot download in recovery (and vice versa).
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
Thanks.
I did it 3-button. I don't have that option in Stock Recovery. All I have is:
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Is there a way? Or maybe is there some way to get TWRP installed without Odin somehow?
Debug Mode?
Hey I was thinking about Debug Mode. I didn't think it would affect Download Mode, but I figured I'd try it.
WHERE THE HECK IS IT?!
I can't find it at all in 4.3.3.
Thanks!
-Frif
Still No luck
Friffy1 said:
Hey I was thinking about Debug Mode. I didn't think it would affect Download Mode, but I figured I'd try it.
WHERE THE HECK IS IT?!
I can't find it at all in 4.3.3.
Thanks!
-Frif
Click to expand...
Click to collapse
Well, I found Debug Mode. For those interested, it's hidden in 4.3. Go to About Phone, then tap Build Number a bunch of times until it opens up Dev Options.
Anyway... Still no luck. In USB Debug Mode, in Download Mode, Odin still doesn't see the device.
Different cable. When flashing phones (using Odin, QPST, DFS, CDMA WS, etc.) I ALWAYS use the OFFICIAL HTC usb cable. It works with every phone that has a micro USB port (duh) and it's NEVER given me any problems. I'm sure the same can be said for other brand name cables, but I stick with what I know. Try a different cable. My generic China cable will do EVERYTHING...except get a COM port in Odin.
If this doesn't work, your charging port might be boned. It's possible a single pin may be damaged, preventing a data connection.
YES!
ecs87 said:
Different cable. When flashing phones (using Odin, QPST, DFS, CDMA WS, etc.) I ALWAYS use the OFFICIAL HTC usb cable. It works with every phone that has a micro USB port (duh) and it's NEVER given me any problems. I'm sure the same can be said for other brand name cables, but I stick with what I know. Try a different cable. My generic China cable will do EVERYTHING...except get a COM port in Odin.
If this doesn't work, your charging port might be boned. It's possible a single pin may be damaged, preventing a data connection.
Click to expand...
Click to collapse
Maybe it IS my cables!!?!?!!?! TWO of them!
So! I just uninstalled my drivers again and reinstalled them. Still no luck. So I got super-frustrated and just started plugging and unplugging into different USB ports. All of a sudden, I got back to my "normal" port and heard the USB connect sound!!?!?! Then the drivers re-installed, then Odin connected!
I installed CF-Auto-Root! My phone's still not rooted, and I don't know why yet. But at least now I have options!
THANKS TO ALL THAT STOPPED BY TO HELP!!!
-Frif
It's been just me and you in this thread buddy lol. Don't use CF auto root. It doesn't work for MK4. Use Kingoroot (you can google it and find the program). It looks like an iffy program but it seems like some kind of multiroot and from what I can tell, it's very credible. Just put your phone into MTP+ADB (USB Debugging) and start the program. After a few minutes, your device will be rooted. Couldn't be easier.
ecs87 said:
It's been just me and you in this thread buddy lol. Don't use CF auto root. It doesn't work for MK4. Use Kingoroot (you can google it and find the program). It looks like an iffy program but it seems like some kind of multiroot and from what I can tell, it's very credible. Just put your phone into MTP+ADB (USB Debugging) and start the program. After a few minutes, your device will be rooted. Couldn't be easier.
Click to expand...
Click to collapse
Yes...Kingoroot will work for a 4.3 ROM. Used it myself with no problems.
Sent from my SPH-L900 using Tapatalk
So i was trying to find some new roms for my SGH-i747M and what i did was backed up my original rom running on a avatar nightly build i tried to upgrade my clockworkmod touch to the latest version using the terminal method (cause i was getting status 7 errors from all the other roms). I finally got the install the work then when i reboot the rom doesn't work i tried going back into CMW recovery and it just crashes and for some reason the computer can't recognize the phone so i can't unbrick it.... what do i do now totally scrub
Have you tried odin
duoblade said:
So i was trying to find some new roms for my SGH-i747M and what i did was backed up my original rom running on a avatar nightly build i tried to upgrade my clockworkmod touch to the latest version using the terminal method (cause i was getting status 7 errors from all the other roms). I finally got the install the work then when i reboot the rom doesn't work i tried going back into CMW recovery and it just crashes and for some reason the computer can't recognize the phone so i can't unbrick it.... what do i do now totally scrub
Click to expand...
Click to collapse
Hey try downloading the stock firmware and used Odin flash it on
What stock ROM was on your phone before you update CWM? It's important to let us know so we can help guide you in the right direction.
Can you get into download mode at all? Have you tried the debrick method described in this forum?
tried everything(mostly)
audit13 said:
What stock ROM was on your phone before you update CWM? It's important to let us know so we can help guide you in the right direction.
Can you get into download mode at all? Have you tried the debrick method described in this forum?
Click to expand...
Click to collapse
I've tried odin and stock rom but the thing is i don't think my usb debugging is on so odin and my computer can't access the components inside the phone, i've tried unistalling drivers and trying to reconnect it but no luck... my stock rom on my phone was a avatar 4.0 nightly build or something (4.3 version) and my old CMW was 6.0.3( or something before i tried to get the 6.0.4) now i can't even get it to work when i tried to flash the slimkat rom
i can't get into CMW recovery.... when i try it restarts, when it restarts all i get is a black screen i think i'm screwed here
Try different drivers, cables and usb ports. Usb debugging only matters when you are booted into android. Shouldn't have any effect on download mode.
duoblade said:
I've tried odin and stock rom but the thing is i don't think my usb debugging is on so odin and my computer can't access the components inside the phone, i've tried unistalling drivers and trying to reconnect it but no luck... my stock rom on my phone was a avatar 4.0 nightly build or something (4.3 version) and my old CMW was 6.0.3( or something before i tried to get the 6.0.4) now i can't even get it to work when i tried to flash the slimkat rom
i can't get into CMW recovery.... when i try it restarts, when it restarts all i get is a black screen i think i'm screwed here
Click to expand...
Click to collapse
Can you get into download? From what I recall with my phone USB debugging was not needed to flash ROMs via Odin or CWM.
i've tried
DocHoliday77 said:
Try different drivers, cables and usb ports. Usb debugging only matters when you are booted into android. Shouldn't have any effect on download mode.
Click to expand...
Click to collapse
i've tried different port different cables different computers i've tried reinstalling the drivers and using different installations nothing seems to be making the phone readable, and yes i can get into download mode but odin or the computer can't detect which port it is on
How are you reinstalling drivers? You have to uninstall through device manager. And make sure your cables are data cables. Many out there are not capable of data transfers. Unless the port on the device has gone bad or been damaged, I'm not sure what else you can try. But if it cannot connect on any port on any computer, I think it may be a hardware issue like I just mentioned.
Did you try different driver versions? You can get several from the link in my sig.
What about trying different operating systems (i.e. WinXP, Win7, OSX, etc.)?
Could be worth a shot. Odin is Windows only though. I think heimdall works for the rest.
try what i can
DocHoliday77 said:
Could be worth a shot. Odin is Windows only though. I think heimdall works for the rest.
Click to expand...
Click to collapse
audit13 said:
What about trying different operating systems (i.e. WinXP, Win7, OSX, etc.)?
Click to expand...
Click to collapse
i've tried switching between the two operating system(windows 7(labtop), windows 8.1(desktop)) don't seem to be working neither have worked i tried installing the driver again on windows but the phone still can't read if anything imma try this method http://forum.xda-developers.com/showthread.php?t=2549068 but idk what the results will yield w/e take what i can get btw idk where the samsung driver would be in device manager at least the general heading if it doesn't show up at all...
wow wtf
never mind guys it was the usb cable it's weird its the stock cable that came with the s3 and it didn't work it was only after i used my bros s4 mini cable that it started to read it wtf...
Cables go bad far more easily and frequently than most people believe. Glad you figured it out!