Develop Bugs

Odin Fail. Could use some ideas...

So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...

Seifer48 said:
So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...
Click to expand...
Click to collapse
are you putting the phone in download mode before you start the flash process?
EDIT: why did you make a new thread for this here when you already asked the same question in another thread? This isn't development talk please use proper forums next time thanks.

go here...
http://forum.xda-developers.com/showthread.php?t=1311229
that should fix it

Mainly because I didn't want to highjack that thread. Regardless, I felt this was development related hence the post in this forum. Yes, I've put it into download mode (vol up+down+power)

movieaddict said:
go here...
http://forum.xda-developers.com/showthread.php?t=1311229
that should fix it
Click to expand...
Click to collapse
That was actually my first idea. I haven't been able to even attempt this yet though, my issue is that Odin will not progress past "SetupConnection".

It sounds like you don't have all the drivers....
Sent from my GT-I9100 using xda premium

daddymatt said:
It sounds like you don't have all the drivers....
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yea, that was my first thought as well. Would you mind putting yours into Download Mode and checking to see which driver it uses in Device Manager? I'm sure that would be a great help!

Seifer48 said:
Yea, that was my first thought as well. Would you mind putting yours into Download Mode and checking to see which driver it uses in Device Manager? I'm sure that would be a great help!
Click to expand...
Click to collapse
Install Samsung Kies & that will give you all the correct drivers. You can find it by doing a google search.
Sent from my SGH-T989 using XDA App

I actually installed the kies package before I initially tried flashing. I've tried just about every driver package I can think of now.... Random errors are frustrating, especially since its beginning to look like I need a jtag to fix this. I really don't wanna have to build one again.

its not volume up and down plus power. Its pull battery, hold volume up and down, insert usb and then put battery in. a screen will come on the phone that says its dangerous to do this press volume up to confirm. Then make sure phone is recognized by odin and id.com space in odin turns yellow.

At this point I've been pulling the battery, volume up+down+power and plugging in USB. It will be detected by windows, but the device stays at a black screen. I haven't tried pressing volume up after windows detects it though, due to never seeing more than a black screen. Ill go try that and hopefully get somewhere.

Also, Odin has always detected it regardless of what I do.

odin will detect it no matter what but are you using a tmobile version because ive noticed your carrier is att in you sig and youve also posted in the att sg2 forums. if you are trying to use our method to flash an att sg2 guess what my friend you are bricked. It is a different method of rooting.

No luck, when I press volume up nothing happens. Odin detects it regardless.
The particular driver I'm using is "Qualcomm HS-USB QDLoader 9008", I'd love it if someone could plug their device in while in download mode and let me know which driver is in use under device manager. The kies package never installed the download mode driver for me and I had to hunt this one down using a google search for similar issues.

mongo41 said:
odin will detect it no matter what but are you using a tmobile version because ive noticed your carrier is att in you sig and youve also posted in the att sg2 forums. if you are trying to use our method to flash an att sg2 guess what my friend you are bricked. It is a different method of rooting.
Click to expand...
Click to collapse
Lol, yea I know. I have a lot of devices. I am indeed using a TMobile Galaxy S2, SGH-T989. I actually have a phone line with each of the 4 major US carriers. I just use my AT&T line as the primary.

Seifer48 said:
I'd love it if someone could plug their device in while in download mode and let me know which driver is in use under device manager.
Click to expand...
Click to collapse
Not sure if this is what you're looking for, but I see "SAMSUNG Mobile USB CDC Composite Device"

Seifer48 said:
Lol, yea I know. I have a lot of devices. I am indeed using a TMobile Galaxy S2, SGH-T989. I actually have a phone line with each of the 4 major US carriers. I just use my AT&T line as the primary.
Click to expand...
Click to collapse
Does Adb recognize your device?? If so, to make sure you are in download mode run "adb devices" on cmd to see if your device pops up and if it does run "adb reboot download".... This should get you to download mode Then i want you to delete your current .tar file and Re-Download the .tar file!
Ps: both commands run WITHOUT quotation marks
Pss: If odin recognizes your device... Drivers are not the problem

Seifer48 said:
So, I went through the instructions and odin told me flash failed, the phone reported back that it had no partition structure in the download screen. Now the phone is stuck at a completely black screen regardless of what I do. Odin wouldn't recognize it at first till I tracked down the missing driver (Qualcomm HS-USB QDLoader 9008), now Odin picks it up again but never moves past <ID:0/003> SetupConnection.. Any ideas? I can't seem to get it to take any flashes whatsoever... I'm currently trying various drivers to see if that is the issue...
Click to expand...
Click to collapse
When you make a post like this, you should reference EXACTLY which instructions you are talking about. Referring simply to "the instructions" is pretty useless - which instructions?
Normally, a black screen means you are dead and hardbricked - however the T989 is not a normal device, so what has happened to you is completely unknown. Especially since no one has any clue how you got to where you are.
If Odin is actually recognizing your device, that's good news.
BTW, process is not to insert battery after plugging in USB usually.
It is:
Ensure your device is off (may need a battery pull and reinsert)
Hold VolUP+DN
Insert USB

Entropy512 said:
When you make a post like this, you should reference EXACTLY which instructions you are talking about. Referring simply to "the instructions" is pretty useless - which instructions?
Normally, a black screen means you are dead and hardbricked - however the T989 is not a normal device, so what has happened to you is completely unknown. Especially since no one has any clue how you got to where you are.
If Odin is actually recognizing your device, that's good news.
BTW, process is not to insert battery after plugging in USB usually.
It is:
Ensure your device is off (may need a battery pull and reinsert)
Hold VolUP+DN
Insert USB
Click to expand...
Click to collapse
Sorry, wasn't thinking that well, I was tired lol. Anyways, it was the Root via Odin instructions that Slayher posted. I was mainly posting to see if anyone had encountered anything like that and if so how they fixed it. I've got a black screen that is unresponsive to everything! At this point I'm just gonna say f it and use a jtag. I appreciate everyones help!

Bricked T989 when rootimg with odin
i got the same problem today.
When using ODIN to implement CWM, ODIN stopped
with failure: "could not complete write"
After this i tried to load the stock Rom with odin.
But i get always the same error.
Does anyone have an idea what is going wrong?
Is there a possibility to rebuild the ROM from SDcard?
Thanks for any help

Soft bricked - No recognition

EDIT: Sorry, this post wen't to completely wrong place. Hope some mod can move this to right section.
I know. There's number of similar threats. I have read them all. Or at least feels like it.
I managed to soft brick my sgs2. I was playing with this new lol boot (dual boot app) from market. I think I pushed something wrong in this app. After that my intention was to make a CWM backup before I start to play seriously with lol boot. At the second I pressed backup from the menu, my phone shut down. Now I'm in a sitsuation whre I can't enter recovery mode. There's just this Samsung Galaxy logo. At the time I had CheckRom v4 installed.
My intention was to flash stock rom via odin. I can enter to download mode just fine BUT odin or kies isn't able to connect to phone. Kies is recognizing the usb connection, but fails to connect it properly. Here's a list what I've tried so far:
- Restart PC (100x)
- Restart Odin (101x)
- Restart Kies
- Reinstall USB Drivers (with Kies and without)
- Trying different computer which has never seen Kies or any Samsung USB drivers
- Reinstalling Windows (W7 x64)
- 3 different USB cables (2 stock Samsung)
- Different USB ports
- Also Nexus S USB drivers as mentioned on another thead in XDA
- Starting odin after USB connection, and before
- Googling with any keywords I have come up
Is there anything else I can do for now?

you mean when you try to connect to odin there is no yellow square ?
maybe try to remove battery for + 90 sec and try to enter in odin ?
ps in this situation you must forget kies since its barely work when everything is fine with the phone ...

Thanks for your reply. Odin doesn't 'do' anything when i connect my device. I'm using version 4.43. When I connect s2, windows install two drivers, Samsung Mobile USB CDC Composite Device and Samsung Mobile USB Modem. I also tried taking battery off. Actually the battery wasn't attached for 6 hours, still no success.

I didn't see this in your list, but have you tried entering download mode and connecting?
Sent from my GT-I9100

can you enter recovery? which recovery you have? Clockwork? 2e, 3e?
Just trying to feel out your situation...

Guys. I think there is some Android God that came to help me. After ~36 hours of googling, crying and throwing the phone to the wall, I've managed to solve my problem! As I was googling cheap shotgun for me, I had a vision. Why not, let's try older odin. The solution was v1.83. And right when I plugged in my phone with this odin, it got recognized! At the same second! Nuff said, I'm satisfied. And do you know what is the best part? I flashed with original stock rom and every app, every launcher and so on was STILL WORKING and running!
Thanks to everyone. I'll be more careful next time!
EDIT: How the heck the custom binary counter went to zero? I was thinking its only possible with usb jig?

not older odin! but the one u need for sgs2 (and 1) only use odin 3 v. 1.83 or v. 1.3.
The one you said IS NOT FOR YOUR PHONE. Sorry I missed that text.

So if I understood you correctly, u are saying that I flashed my phone with wrong version of odin (1.83) ? Sorry, I'cant understand english too good, so can you say your point more literally and s_l_o_w_l_y? Thanks

I only use odin3 v1.3 or odin 3 v.1.83.
As far as I know, you cannot use anything else, since it is not made for your device!
I might be wrong, if so, somebody correct me.
Sent from my GT-I9100

So if you're correct on this, the reason why I couldn't get my phone recognized was the wrong version of odin?

pazzio said:
Guys. I think there is some Android God that came to help me. After ~36 hours of googling, crying and throwing the phone to the wall, I've managed to solve my problem! As I was googling cheap shotgun for me, I had a vision. Why not, let's try older odin. The solution was v1.83. And right when I plugged in my phone with this odin, it got recognized! At the same second! Nuff said, I'm satisfied. And do you know what is the best part? I flashed with original stock rom and every app, every launcher and so on was STILL WORKING and running!
Thanks to everyone. I'll be more careful next time!
EDIT: How the heck the custom binary counter went to zero? I was thinking its only possible with usb jig?
Click to expand...
Click to collapse
gratz!
to reset your binary, there is only one way to do it. u are right, usb jig.
however, beware, i read somewhere saying that GB ver 2.3.4 onward has a new version of bootloader which prevent usb jig from resetting the counter, which mean samsung is trying to lock the bootloader now. however, flashing the old bootloader still helps (claim by others).

Fully Bricked Galaxy Nexus! HELP!

Okay so my friend bricked his galaxy nexus (Gave it to me because he said its bricked) of course i accepted it lol. But i tried to fix it i did everything i could from reading forums i swear i have worked forever looking for a fix. It is completely unresponsive no download mode. no ADB connection because when it plugs into a computer it shows up as OMAP 4440 or something like that. i have tried all kinds of different drivers and i have tried on multiple computers (Xp, Windows7, even a mac) he said he was flashing the sdcard or something and unplugged it by accident. So i could understand that being a issue since the phone only has a internal sd card. Anyone know how to get it back? i havent seen a Jtag yet for it and i have a Jig for my Galaxy Sii Skyrocket but it doesnt work on the nexus (FYI to anyone out there the jig works on my dads samsung windows phone) HELP!

You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?

paperhurts said:
You tried different drivers? You should just use the most current ones for the phone. Did you try the new toolkit mskip posted? Did you isntall the SDK?
Click to expand...
Click to collapse
Thanks for the response i didnt use mskips i dont think. i have tried the galaxy nexus toolkit 6.0 or whatever but i have tried all kinds of drivers including the google official galaxy nexus i515 or something like that. it shows up as omap 4440 in app manager and disconnects and connects constantly then says device didnt install properly. what do you mean by the sdk? i cant find any way to access my phone. i think i tried something with sdk but im not sure

Yes i read up i did do that GNex Toolkit v6.0 and it wouldnt find my phone (Because of the omap 4440 disconnect and reconnect thing i believe.

First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.

miketoasty said:
First off, on't use a toolkit.
Second, when you plug it in, go to device manager, right click the "OMAP 4460" and click install driver. Either install PDANet or find the driver online and your phone should be able to be used in fastboot.
Finally, if your (Or your friends) phone was "Fully Bricked" it wouldn't be recognized by the computer, it wouldn't turn on, it would literally not be able to do anything except sit there, the fact that the computer sees it means that it is "Soft Bricked" which is much less serious.
Click to expand...
Click to collapse
i appreciate it but when i install the driver which one should i select? it is the Verizon LTE one and i have tried manually choosing the driver but there is so many. What one should i choose?

When i try to install pdanet it always uninstalls at the end automaticaly? why is that?

IRusselldABear said:
When i try to install pdanet it always uninstalls at the end automaticaly? why is that?
Click to expand...
Click to collapse
I couldn't get PDAnet to work for me either. It asks you to enter Debugging mode and I can't get into android

I cant get into android neither thats the problem... it is unresponsive except for the fact that it says omap 4440 over and over. im gonna play with it more when i get home but im currently in school. LOL

is it possible to volume+power into recovery mode?

Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.

Install PDANet and when it asks for your phone, go into Task Manager and force close the process. This will keep the driver/program installed without needing your phone and it should then be seen in recovery.

Not working still :/

Thanks for highjacking my post twinky lol. i have seen the answer to yours around... google a little more.
TwinkyOfHope said:
I can get mine into CWM, but whenever I'm flashing a ROM, it reboots itself.
Click to expand...
Click to collapse
Jsweetser2 said:
is it possible to volume+power into recovery mode?
Click to expand...
Click to collapse

Please Help!
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks

It sounds like what I did to my Galaxy Note before I bought my Nexus. When unrooting I overwrote my bootloader with a missed character through ADB. I tried everything, naked drivers, ODIN, all it would come up with was OMAP on the PC. I ended up having to return it to AT&T. Ask him if he was trying to root it the old way through ADB.
samiaziz said:
My phone goes into boot loader and download mode however every time I flash Stock it finishes successfully and goes to the same google screen its always stuck on. I'm kinda a n00b so if anyone could help me with this (try to have a lot of detail) I would be grateful. Thanks
Click to expand...
Click to collapse
samiaziz, make sure you're wiping everything before flashing a stock rom. It wouldn't hurt to wipe system, cache and dalvik and then restart recovery (in advanced menu) and wipe again before flashing the stock rom.

Ok, as long as it shows up, it's still working
OMAP440 is the processor, which means, that is is working, but the bootloader is corrupt, or missing. I'd say it's corrupt (Flash-error)
The best way I've found, check this website: http://www.mobiletechvideos.com and see if they have a JTAG solution... (My JTAG device will arrive in a few weeks )
Even if they don't, send it in, and they'll figure out a way to do that I think they do some special offer, if you send it in for testing purposes...
But, other than that, there's no way I can help you. The firmware is completely fu**ed...

Tried That
I have already tried getting into recovery but that dosnt work. it takes me to the google splash screen

2 words: fastboot, linux.
sent from my i9250

Instead of JTAG-ing it, you could always try this. The maker of the Riffbox JTAG has come out with a solution for unbricking by reflashing the OMAP processor.. Aptly named OMAPFlash.
I've used it with success several times, but also had it fail on me. It can't hurt though, if your phone is already bricked.
If it's coming up with OMAP4460 (even briefly) when the phone is plugged into your computer without a battery, you are able to run the program. You just need to install the drivers for it.
See http://forum.gsmhosting.com/vbb/f634/unbrick-dead-samsung-gt-i9250-galaxy-nexus-32gb-prime-via-usb-cable-freeeeeeeeeeee-1465412/ for download.
Lemme know if you need instructions.

Hard bricked... without a good reason!

I've owned my SGII since release, went through a few roms, never had any issues. I have been running liquidsmooth for a month or two, without much issue. Although, lately stablity has dropped off a little. Nothing bad, just a freeze every few days and other minor hiccups.
Then something bad happened.... Last night I was using the phone and it turned off. Then it wouldn't boot. Battery pull, and rebooted but no joy. Then I booted to recovery (TWRP, but I'm not sure which version) and found that it said something along the lines of "E: could not mount /system", along with lots of other similar failure to mount messages. Oh well, I guess I'll just wipe it and flash something new. Any attempt to wipe would hang and then the phone would turn off after a few minutes.
Then I went to flash the stock setup from odin (using the howto from the dev section) , but it too would fail every time. I even tried different builds from samsung's official roms, but they all would fail to install on the phone. I read every thread I could find, and the next thing to try seemed to be an emergency recovery through Kies. That also failed, except it left my phone hard bricked. I can't get into download or anything, nothing shows in the device manager, just completely dead... I made a USB jig, but no luck there either.
I'm completely frustrated... I don't know what to do now... Buy a MB from ebay? The phone was flawless before all this. Any suggestions? I'm using a blackberry pearl for now, I can't let that happen.

Have you tried the Jig on another Samsung phone so you know the one you made physically works?
Some people have managed to get into DL Mode by pulling the battery, SIM, SD, etc. For 5 - 10 minutes then connecting it to the pc with Odin running b4 inserting the battery to enter DL Mode.
Otherwise mobiletechvideos has a really good reputation and turn around time for JTag service.
There is a chance its a hardware problem, and hopefully another member on here can shed some light on the possibility of it being a HW issue or not..
Cheers,
Chris

Thanks for the suggestions. I don't have another samsung phone to try the jig with, but I'll see if I can get a friend to let me hook up this crazy looking thing. I got the resistors set up to 299K, hoped that would be close enough, but perhaps not.
I tried that plug-first-battery-second trick to get into DL mode, but that's not working either.
I looked at the jtag service too, but my fear is that I have corrupted memory. In that case, I wouldn't get a refund if I still couldn't get to a fully healthy boot. It seems odd though... not like it's a common trend for this particular model (that I've seen).
Just seems so strange that it happened for no apparent reason... before it was hard bricked I was able to USB mount the internal storage and access and transfer almost all the contents, except for one folder. I wonder if that one part of the memory caused all the problems?
Again, thanks for the suggestions. I'll keep plugging away at anything that might help, and in the mean time I guess I'll keep my eyes out for broken phones or some way to salvage a board.

If im not mistaken, a hard brick should show up in you device manager as the board itself when connected.
Does anything show in you device manager when its connected? And have you tried using a different PC which has never had Kies installed on it, where you just install the drivers for the T989?
Odin tends to fail at the modem or due to the presence of a .PIT
I got myself out of a brick which started over the a very similar issue, but due to a bad flash.
After 5 hrs of getting nowhere (I was using a Jig) I would get Odin to recognize the phone (My Screen was NOT displaying the DL Mode screen, It was going into DL Mode but other than Odin recognizing it, there were no signs of life!) after enought tries but flashing to stock would fail. I ended up taking a shot at flashing the stock kernel using 512.Pit from a T959, Reflashing the same Kernel, then flashing recovery. I don't advise anyone do this as that PIT file is NOT for a T989, and it may have been BS luck not the use of that PIT file that did the trick.
But I did get it back running %100

Good tips, thanks! Were you using the jig to get the phone into the black screen download mode?
I hadn't tried another PC, although I did make sure any Kies processes were disabled. I just tried another computer, but still nothing gets recognized. Oddly enough, not even the basic "hard brick" USB driver shows up in the device manager.
Thanks for the additional ideas.

This happen to me before, I just cleared cache and Davik then rebooted recovery then flashed another Rom.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

Unfortunately for me, since data, cache, and system couldn't be mounted, I couldn't successfully clear them.

KLR Rico said:
Good tips, thanks! Were you using the jig to get the phone into the black screen download mode?
I hadn't tried another PC, although I did make sure any Kies processes were disabled. I just tried another computer, but still nothing gets recognized. Oddly enough, not even the basic "hard brick" USB driver shows up in the device manager.
Thanks for the additional ideas.
Click to expand...
Click to collapse
I would put the jig in with the battery and everything still removed, and alot of trial and error trying things like battery first then connecting the cable with Odin always being already running. Then doing the reverse, etc.
When I did get Odin to recognize the phone, one thing I learnt is when it would detect, it only ever happened after having killed and reopened Odin. I have no explanation on why using "End Task" after each attempt to connect and opening Odin again made a difference but it did.
Have you had a look at the QPST thread? I would ask one of the members contributing to it about why you would or would not see the board. And you could always try installing the boards drivers manually, or enable "Show hidden devices" in your device manager.....
Did you contact the guys at mobiletechvideos and explain the details?
You were able to boot to recovery, so it sounds partition related. But I would try just to flash the stock UVLH1 kernel and recovery with Odin vs full stock rom if you do get it to detect. And if it does detect with Odin eventually do not let it reboot or loose power. Just Kill Odin, unplug the cable if you need to, Start Odin again and reconnect the cable. Once in DL Mode it will stay in DL Mode as long as you have the reboot option in Odin unchecked, etc.
Also if you can get the battery charged fully somehow, your best shot is with a fully charged battery.
Chris

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

I was running CM10 but I got a message whenever I got into the Camera App that said "Unfortunately, Gallery has stopped working", after a research in here I found that I wouldn't get that msg again if I installed this "gapps-jb-picasa-20121011-signed" thing.
I did, but when I got into my Camera App, I didn't have the other options like "Image Effects" and all that stuff.
So, what I did was to Restore my phone from my BackUp folder that I've created before installing CM10, but for my surprise I got a msg saying "VolumeError" or something like that and other things that I can't really remember... and as a good Mexican that I am, I ignored it and hit the Reboot System Now..
What happened next almost made me cry...
I was expecting to get in my stock rom without any problems and yadda yadda but... OH SURPRISE!
I got stuck on the boot screen, where it says "Samsung" and the website of it and I didn't freak out... I waited like 5-6 mins and took the battery out. When I turned again, I tried to get in Recovery Mode but the screen just kept turning off and on and saying the exact same thing, the "Samsung" logo and it's website.
I hope you can help me and please answer me. I don't know if I'm 1000000% screwed but I will only wait for the worst. Sorry for my bad english and don't hate me for being mexican
I don't know if I can get into my phone from my PC but whenever I plug my phone in, it just loads it as if it was in Charging Mode
PLEASE HELP ME!
I BEG YOU!

Flash again CM10 with wipe data, cache, dalvik
If still stuck
Odin to stock ROM, you can search on google to odin the epic
Sent from my JellyBeer v.4.14 epicmtd (b3)

Questions go in Q&A
Thread moved
Friendly Neighborhood Moderator

Like @dropple said, it seems you stuck "SAMSUNG" and in this case you can't get into recovery so you can't flash CM10 as of now. Go find some tutorials and Odin back to stock via download mode. Then install CWM recovery if you want and do whatever you like. Should get you outta trouble.
Sent from HTC Incredible S @ PACman v21

AndyYan said:
Like @dropple said, it seems you stuck "SAMSUNG" and in this case you can't get into recovery so you can't flash CM10 as of now. Go find some tutorials and Odin back to stock via download mode. Then install CWM recovery if you want and do whatever you like. Should get you outta trouble.
Sent from HTC Incredible S @ PACman v21
Click to expand...
Click to collapse
Thanks to Everyone!
I solved this like 2 hrs after all this happened.
I got it by Odin. I couldn't go into Recovery Mode, but I got in Download Mode and do it by Odin.
Sorry, I'm a n00b to all this.
Greetings from México and thanks for all your support.

Here's a weird one for you,
Same thing as OP stated. Device is stuck on logo. Can't get into CWM. Was on People's Rom. Device was lagging really bad. Then the system requested superuser permissions. Yes the system requested. Being as I did not request it, I declined. Shut the device down to see if that would help with the extremely bad lag (i mean BAD lag. Like..........................ok it does something then.......................................................................ok it does something else. 10-20 seconds lag)
Connect device to computer to Odin back to Stock or whatever ROM would have worked, computer recognizes device..... wait for it.......
But in download mode Odin does not see it. Com Port will not illuminate. Tried 3 different cables. Tried 6 different USB ports on computer. Still nothing.
Any ideas, because I'm all out?!?

To the OP:
I would follow the instructions in this video from the part where qbking77 talks about putting the phone in download mode, as you presumably did when you first rooted your phone. Download all the files linked/referenced on the site, especially the Samsung mobile drivers, Odinv3 1.87, CWMRecovery, and the deOxed versions of the stock ROM. In sum:
1) get into recovery mode by holding onto the volume down, camera buttons, and then without letting either of those go, press and hold the power button.
if you get into recovery mode, skip to step 4
2) while your phone is completely off, hold onto the "1" button on the slide out keyboard first, then without letting the 1 button go, press and hold the power button until you're in download mode.
3) flash the version of Clockworkmod
4) once in recovery mode, wipe your phone, clear the cache, and dalvik cache, and then flash the deOxed version of the stock ROM
niteNarmor said:
Here's a weird one for you,
Same thing as OP stated. Device is stuck on logo. Can't get into CWM. Was on People's Rom. Device was lagging really bad. Then the system requested superuser permissions. Yes the system requested. Being as I did not request it, I declined. Shut the device down to see if that would help with the extremely bad lag (i mean BAD lag. Like..........................ok it does something then.......................................................................ok it does something else. 10-20 seconds lag)
Connect device to computer to Odin back to Stock or whatever ROM would have worked, computer recognizes device..... wait for it.......
But in download mode Odin does not see it. Com Port will not illuminate. Tried 3 different cables. Tried 6 different USB ports on computer. Still nothing.
Any ideas, because I'm all out?!?
Click to expand...
Click to collapse
Do you have the mobile drivers installed on the computer you're trying to connect your phone to?

Yes. The drivers have been installed previously. The computer will see the device as "Samsung SPH-D700 Card USB Device". But Odin3 1.85 will not see it.
EDIT: When I put device into download mode and connect to computer, the computer only sees it as "Gadget Serial".

niteNarmor said:
Yes. The drivers have been installed previously. The computer will see the device as "Samsung SPH-D700 Card USB Device". But Odin3 1.85 will not see it.
EDIT: When I put device into download mode and connect to computer, the computer only sees it as "Gadget Serial".
Click to expand...
Click to collapse
Uninstall and reinstall drivers.
Sent from my SPH-D700 using Tapatalk 2

Have already done that. But just for laughs, I did do it again with no change.

can you get your D700 into download mode as described above?

Yes I can get into download mode but without Odin recognizing the device (not computer. The computer recognizes the device) there is not much I can do.

niteNarmor said:
Yes I can get into download mode but without Odin recognizing the device (not computer. The computer recognizes the device) there is not much I can do.
Click to expand...
Click to collapse
Try to install another version of Odin or getting Odin from a different server.
My phone is fully recovered and now I'm only SuperUser 'cause I don't want any CM by now.
Greetings from Mexico!

I'm using the same version of Odin I used to root the device. Would a different version really help and if so, what version to use?
I actually have a different version of Odin I used for another device and tried that one as well, with no luck.
EDIT: I have now downloaded and tried 4 different Odin programs with no avail. Again, that makes 6 Odin programs, 6 different USB ports, 3 different cables with the same exact results. The computer recognizes device but Odin will not.

niteNarmor said:
I'm using the same version of Odin I used to root the device. Would a different version really help and if so, what version to use?
I actually have a different version of Odin I used for another device and tried that one as well, with no luck.
Click to expand...
Click to collapse
Had a simular issue when I had two odins on the same computer, for a lark and as I had nothing better to do, tried installing drivers and one version of odin to a vertual machine running vista and checked to see if my computer's vertual machine would reconize and it did, I took it as a sine that at one point I had done something to my computer's main os sometime between rooting my epic 4g and frying it (recovering from a backup from a different parition layout I think, bad times with bootloops and seeing way to much of the samsung logo.) So as I'm not brave enough to run odin on vm I instead removed all of odin from my main os and all of the samsung drivers, then reinstalled rebooted and repluged my epic in, got reconition and reflashed with plesure.
The other issue might be that your computer is reconizing the device and try/failing/hanging and not allowing odin in. Had an issue when my computer was failing to pop up a 'what do I do with this' window and hanging round in the system. A reboot with the internet unpluged strangely solved that for some reason, might be the reboot might be the combo, but I find better connection reconition with my computer when I've fewer things connected.
Don't mind the spelling to much I clean up with my other device.
Sent from my T-Mobile myTouch 3G Slide using xda app-developers app

One question I noticed that hasn't been asked is when you plug the phone into the computer while the phone is on, is usb debugging checked? If not, check it, and reinstall drivers again.
Sent from my SPH-D700 using Tapatalk 2

jeffreyjicha said:
One question I noticed that hasn't been asked is when you plug the phone into the computer while the phone is on, is usb debugging checked? If not, check it, and reinstall drivers again.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
Phone does not boot past the "Samsung - www.samsung.com" logo. Plus, as with all of my devices, USB debugging is always checked.
Thanks for the suggestion though. Always helps to double check things.
I believe I am going to take it to Sprint tomorrow.
If I can't get into it, they should not be able to get into to it either. If they can't get into it, HELLO WARRANTY....

Perhaps before doing the whole getting found out thing with the return center, perhaps they do know what they're doing, try rolling this link past your eyes?
http://forum.xda-developers.com/showthread.php?t=773032
I know I've been in your boot problem situation and recovered, it just took persistence and eyenumbing amounts of reading.
Note On the multiple Odin, USB, and driver installation: if you've access to another computer it could be worth wile to run once though on a previously virgin computer, meaning your phone and computers' USB's have never touched. Just do the installation, rebooting, and plugging in exasperatingly meticulous order.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"

Yep tried the "virgin computer" computer as well. The computer sees the device but Odin does not. Com light will not illuminate.

Sounds grim.
So to rap up all the cables, plugs, computer, and software with odin is out of the debug process.
So I did some digging into the past and if your computer is reconizing and odin is not then ADB (android debug bridge) and the sdk are the other option
http://forums.androidcentral.com/epic-4g-rooting-roms-hacks/33427-how-access-your-adb-shell.html
Ran across this and it might just be what you need. Its not quick but it has worked for me in the past.
The other thing that may work is ejecting the sd card and battery before doing anything. Though its likely something you've already tried.
Sent from either my SPH-D700 or myTouch3Gs using XDA app
"it never hurts to help"