Database Info

[Q] Another Brick Thread - Not recognized by ODIN/ADB??

Hey everyone, I'm quite the lurker on these forums and don't post very often at all. I just want to first and foremost say that everyone here has been amazing and the work that has gone on for this phone is truly astonishing.
Now, with that being said... I'm bricked.
I was running CM7 today and decided (don't ask why) to try that ICS for the i9003. Dumb move. Hopefully someone is getting a laugh out of this as well.
I expected the results to be bad, but not disastrous. In the process of trying to do this I bricked the phone. When I had the ICS ROM on it, it got stuck on the AT&T screen. No worries, I made a back up this morning... I figured just pop back into recovery and restore myself back to normal and everything's fine.
Well, here's where it gets bad. I cannot get into recovery. After multiple attempts of trying to get into recovery. ADB nor Odin even see my phone in download mode. I do have a USB JTAG jig, which has saved me quite a few times.
I started downloading stock ROM's like crazy today. The only one that I could get to install was stock 2.3.5 with Boog's kernel with CWM. I booted into the OS and all seemed well at the time... except there's no modem! I have no internet, service, or anything. This is the only time ADB can see my phone, is when it's booted up. As soon as it's in download mode, ADB can no longer see my phone. The same with ODIN.
ODIN sees my phone when it's booted up, but doesn't actually make the handshake for an install of another version. I've tried to root it, in hopes of being able to push ROM Manager, Super User, and restore my back up in CWM. This didn't work either. During the rooting, using a one-click, it hangs up trying to run the psneuter exploit.
If I'm booted into this 2.3.5 stock of android with no modem, I tried to reboot into recovery using ADB running reboot recovery. This just boots the phone back into Android as if there's no recovery on the device at all.
Soon as I'm back in download mode I cannot push any files with ODIN or ADB. Neither one of them see my device at this point. Even using the JTAG jig.
This is where I'm now at. I'm not sure what else to try at this point. Is there a reason that my device is no longer being recognized in ADB when in download mode?
Any insight would be greatly appreciated. I've been trying to scour forums and search engines with no luck so far. This is my only phone, so it's a little depressing to be without any means of communication on the go, but that's the chance you take...right?
p.s. I do have all the Samsung USB drivers as I normally push files with ADB and have just done so earlier this week. Had the same luck on my computer at work today. So, I know it's not a PC related issue.
Thank you to everyone in advance.

I've also tried to push a modem to the phone with no luck.
I installed 2.3.5 with the Executable JAR of Heimdall AndroidOS 2.3.5 to push the files and that JAR version is the only device that will install to my phone and makes the handshake. Just no modem

You may want to give Heimdall a try - it installs its own USB drivers, so it's possible it might be able to see your phone that way. Nevermind - just saw your post. Which Heimdall did you grab?
Also try switching USB ports - sometimes a different port makes a difference.
There's a one-click in my signature if you need it.

I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
edit: Just to be sure I did try the one in your sig. It installs no problem, but ROM manager crashes and the screen distorts right before home screen loads. Once it's loaded it seems OK. Might be a boot loader issue.. but not sure. Once in download moad Odin3 doesn't recognize the device. The one click app does, but not Odin3 v. 1.3 to flash rooted kernel. It just doesn't recognize the device for some reason, but java installer still recognizes it.
I cannot get into CWM as it just crashes. Doesn't reinstall correctly, gets stuck on running privileged commands. Cannot boot into it since it's a privileged command as well. Only version of odin that recognizes my phone is the one in your link and it's a JAR Exe lol. This is the strange part.. no modem. Just got the wifi to work to at least make it to the market place. Still no modem, broadband is 'unknown'.
When I go back into download mode to flash a kernel in Odin v1.3 it doesn't recognize my device. ADB does not recognize my device. The java installer for the stock rom I just used in your sig still recognizes the device. Only the java installer recognizes it. Tried using Heimdall 1.1 for the kernel flash and it also does not recognize my phone.

I do have an HP TouchPad running CM7 alpha 2.1 as well. Not sure if this will help, unless someone can think of something clever by having an extra Android device. Just throwing it out there.

sunfirex said:
I believe it was the one in your signature to be honest. Which is the only one that recognizes my phone in download mode.
I get it to boot to Android, but that's where I'm stuck. Can't get into CWM from that stock ROM. I'm assuming it would have to be rooted to even use CWM, and I was unable to one-click root it.
Click to expand...
Click to collapse
As far as I know, that should have CWM installed in the file. Depending on which bootloaders you have, either holding V+ and Power from a powered-off state, or V+/V-/Power should put you straight into CWM.
If that isn't working for you, but you're at least on a Gingerbread rom, try this. It appears Heimdall is ok with your phone, and this kernel I'm certain has CWM baked in. You might bootloop, but you should definitely get to CWM from this.

That's exactly what it was. That version of Heimdall in the link you provided solved my issue.
Thank you so much!

Glad to hear it.

Getting Rainbow screen on every boot and when trying to get to recovery mode

Getting Rainbow screen on every boot and when trying to get to recovery mode
For some reason I cannot get my computer to detect my device thus I can not even get into download mode. when I launch Odin and and not able to access my SD. I am at a lost here since now I cannot flash nor can I odin to get back to stock can anyone help here? I think I have tried everything I can find.
I just recently flashed octane 2.x per the instructions under development

rozzko said:
Getting Rainbow screen on every boot and when trying to get to recovery mode
For some reason I cannot get my computer to detect my device thus I can not even get into download mode. when I launch Odin and and not able to access my SD. I am at a lost here since now I cannot flash nor can I odin to get back to stock can anyone help here? I think I have tried everything I can find.
I just recently flashed octane 2.x per the instructions under development
Click to expand...
Click to collapse
If you came from Froyo, follow this guide: http://forum.xda-developers.com/showthread.php?p=16762954
Hope this helps.
sent from my CommandCenter using xda premium

sounds like the bootloader.
flash a froyo rom, then try to odin. AFTER you have tried installing the drivers linked in the previous post. That guide should work.

Did you get this fixed?
Sent from my SGH-T959V using xda premium

I bought a Jig an can get into download mode but still cant get into recover (because of the rainbow screen) and i cannot get my computer to recognize my my phone either via sd or via odin or i think i could solve this.
thanks in advance

I bought a Jig an can get into download mode but still cant get into recover (because of the rainbow screen) and i cannot get my computer to recognize my my phone either via sd or via odin or i think i could solve this.
thanks in advance
Click to expand...
Click to collapse
Go into the control panel & uninstall the USB drivers & kies mini if installed. Then reinstall Kies Mini & use the menu option to reinstall the drivers. See if that helps.
Sent from my SGH-T959V using XDA App

I re installed drivers several times and used a different machine. I feel like I am stuck and there might now be a solution to this except toss the phone in the ocean!

rozzko said:
I re installed drivers several times and used a different machine. I feel like I am stuck and there might now be a solution to this except toss the phone in the ocean!
Click to expand...
Click to collapse
Could it be the cable you're using? I've seen quite a few posts here about people using cables that were bad and/or too long and it prevented the phone from being recognized via USB. People could charge the phone but not use ODIN or anything.
Do you have a different cable to try?

ive tried two different cables, i could try another one thats a good idea. somehow i think maybe i messed up the mounting, i thought i followed the instructions to a t. UMMU .. i will try a few different cables when i get home tonight... actually just tried at work no dice, my system storage is also only showing 126 MB

rozzko said:
ive tried two different cables, i could try another one thats a good idea. somehow i think maybe i messed up the mounting, i thought i followed the instructions to a t. UMMU .. i will try a few different cables when i get home tonight... actually just tried at work no dice, my system storage is also only showing 126 MB
Click to expand...
Click to collapse
I thought the phone did not boot up. How are you seeing how much storage you have left?
I'm curious to know what state it really is in. There has to be a way to get it going for you.

the phone boots fine during the boot after the initial boot screen where it says galaxy s 4g it goes into rainbow patterns. so every time i try to get into recovery when I am in the recovery menu (or into where the recovery menu should be) i cannot see anything because of the rainbow screen. I was told maybe i have the wrong boot loaders installed.
because i cant see recovery and I cannot get my computer to see my phone I have no idea what to do get my phone back to stock to start over.
This is why I am stuck.
If i could get my computer to see the phone I think i could odin back to stock, using the dongle is half the battle as i can get in recovery

rozzko said:
the phone boots fine during the boot after the initial boot screen where it says galaxy s 4g it goes into rainbow patterns. so every time i try to get into recovery when I am in the recovery menu (or into where the recovery menu should be) i cannot see anything because of the rainbow screen. I was told maybe i have the wrong boot loaders installed.
because i cant see recovery and I cannot get my computer to see my phone I have no idea what to do get my phone back to stock to start over.
This is why I am stuck.
If i could get my computer to see the phone I think i could odin back to stock, using the dongle is half the battle as i can get in recovery
Click to expand...
Click to collapse
Pardon me if I'm not getting it....but yo said it boots fine but then you get the rainbow screen when the Galaxy S 4G logo should appear? The rainbow screen is definitely a boot loader issue. I'm just trying to figure out a way to either get you into a download mode where the phone is recognized or into recovery so you can get it going again.
How are you getting it into recovery mode?
I'm wondering if Heimdall would be your best bet? You could try to download it from here, extract it somewhere, then go into the Drivers folder and double-click zadig.exe. Select Options from the menu bar, select List All Devics then select Samsung Android Composite (something along those lines), then click Install Driver. This is a different driver than the one that comes from Samsung.
After that, maybe try Bhundven's [Heimdall][One-Click][UVKJ6] The KJ6 Heimdall One-Click Collection [12/11/2011]. Select whichever one-click file you want to go for and follow his instructions. They all have the GB bootloaders in them, so you should be set.

Usually both volume buttons power button for a few secs or through rom mgr

rozzko said:
Usually both volume buttons power button for a few secs or through rom mgr
Click to expand...
Click to collapse
From what I've read ROM Manager is a no-no on this model phone. I dunno why, but I've read that on a few threads.
Let me know if you're able to install Heimdall and the open source drivers that come with it. If you can, you can get into download mode, and it sees the phone, then you can try the One Clicks or even just flash the boot loaders from a ROM that contains them.

I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.

rozzko said:
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
Click to expand...
Click to collapse
Ugh...well let's hope for the best. I would uninstall any drivers and programs like Kies you have installed first, then install the Heimdall drivers. Let me know how it goes.

so i uninstalled drivers executed Heimdall and put phone in download mode with dongle. the computer still did not detect phone, however i got my replacement SGS4 today put it in download mode and it was detected immediately.
I dont know what else I can do do get the phone detected or fix the boot loader to get into recovery

rozzko said:
I will try when i go home tonight.
just an fyi every time i plug in my phone, it does not show up on my computer. i have tried using debugging mode and mass storage and neither work.
Click to expand...
Click to collapse
Maybe I'm missing something. How are you switching between debugging mode and mass media if you can't boot the phone?
The way I understood the problem, you would get to the SgS logo screen during boot, then the whole screen would be covered by the rainbow effect, which renders the screen unreadable, nd thus the phone unusable. Is that correct, or is the problem different?

the rainbow screen happens right after the SGS Logo then fades out once the lock screen comes on.
it also shows up once I try to get into recovery but from that point I cannot see anything and have to reboot.
Phone works after fully booted
both debugging and mass storage have been tried

You need to flash the "GINGERBREAD" bootloaders. This issue is 100% caused by froyo bootloaders. Once you obtain the GINGERBREAD bootloader, there is a 100% chance that the issue will go away. Flash THISTHIS/download. in heimdall. Get into recovery, then flash a rom of your choice.

Infuse Soft Brick - HELP!

I have a Samsung Infuse that I recently rooted and installed Serendipity on. I then attempted to load CM7, which caused some problems. Now the phone gets stuck on the Samsung logo and doesn't go any further; I can only load into CWM (Red), which can be "updated" to Green, after a hard reset. I've attempted to reflash the ROM from the SD card (even after wiping Dalvik cache, cache partition, and factory reset), but it just gets stuck on the Samsung logo.
My issue is further complicated by the fact that Download mode doesn't want to work - my phone can enter Download mode, but my computer (with Kies installed for the drivers) doesn't recognize the phone being connected. I've occasionally gotten Download mode to work if the battery is removed at just the right moment, but it doesn't last. Due to this, I can't get Odin to work.
Any ideas on what to do next?

kmv_007 said:
I have a Samsung Infuse that I recently rooted and installed Serendipity on. I then attempted to load CM7, which caused some problems. Now the phone gets stuck on the Samsung logo and doesn't go any further; I can only load into CWM (Red), which can be "updated" to Green, after a hard reset. I've attempted to reflash the ROM from the SD card (even after wiping Dalvik cache, cache partition, and factory reset), but it just gets stuck on the Samsung logo.
My issue is further complicated by the fact that Download mode doesn't want to work - my phone can enter Download mode, but my computer (with Kies installed for the drivers) doesn't recognize the phone being connected. I've occasionally gotten Download mode to work if the battery is removed at just the right moment, but it doesn't last. Due to this, I can't get Odin to work.
Any ideas on what to do next?
Click to expand...
Click to collapse
You have a soft brick.
Odin or heimdall back to stock.
There are about fifty threads previously posted on this topic.
Just read thru a few...
Gl

qkster said:
You have a soft brick.
Odin or heimdall back to stock.
There are about fifty threads previously posted on this topic.
Just read thru a few...
Gl
Click to expand...
Click to collapse
Thanks for the attempt, but as I said before Download mode isn't recognized by the computer, and that is an important component for Odin or heimdall to work.
I have occasionally gotten access to the SD card through CWM, so I can place ZIP files directly on the phone. If anyone has any ideas on what to flash from the phone, I'd love to hear it.
Thanks in advance!

kmv_007 said:
Thanks for the attempt, but as I said before Download mode isn't recognized by the computer, and that is an important component for Odin or heimdall to work.
I have occasionally gotten access to the SD card through CWM, so I can place ZIP files directly on the phone. If anyone has any ideas on what to flash from the phone, I'd love to hear it.
Thanks in advance!
Click to expand...
Click to collapse
Try it on another computer. I recommended Odin back to stock first before you start flashing!
Sent from my SGH-I997 using Tapatalk

Thanks, I'll give a different computer a try.

kmv_007 said:
Thanks, I'll give a different computer a try.
Click to expand...
Click to collapse
make sure you are trying to get into DL mode correctly...
pull battery, hold ONLY the volume buttonS - not the power button -;
insert battery, plug in cable.
if that doesnt work, use a different usb cable.
try different port on the computer
try a different computer or winxp or win7
it's kinda finicky at times.

Finally got it working - needed to use a different computer. Used my brother's laptop and it worked first try. Thanks for your guys' help.

[Q] botched ROM load, now stuck in recovery hell

I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!

try installing kies odin wouldnt see my phone until i installed it

Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.

okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.

If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.

i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda

I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.

Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.

also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?

If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)

rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?

rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....

Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!

Samsung Infuse Soft Brick and Distorted Clockwork Mod Recovery

I am in desperate need of help .. I am not a noob to flashing roms and rooting, however I have a one-off situation w/ no precedents to my knowledge. I have read these and other forums for days to no avail.
I was flashing Infintium Rom 4.0.4 from MIUI 2.3.6. I followed the steps listed in the post (http://forum.xda-developers.com/showthread.php?t=1661690). After flashing I rebooted and waited however the phone was/is stuck on the Samsung logo and never progressed. I then pulled the battery and attempted to go back to recovery mode to reflash make sure I did flashed correctly. However, upon going back into recovery I was greeted by the below image.
Clockwork Mod is extremely distorted and flat out unusable !! As I read further down it advised to use Heimdall (http://forum.xda-developers.com/showthread.php?t=1331381). I downloaded and attempted to use, however my PC (Which by the way is Windows 7 64-Bit) recognized the phone but the Heimdall software did not. I already had the right drivers for the PC and phone. After a few tries I deleted the files and reapplied them. On the 2nd menu after selecting list devices, on the drop down the option for Samsung USB Composite Device neeever ever appears. I also tried on a different PC that ddnt have the drivers and started brand new. Still, Heimdall ddnt recognize.
I also tried to flash numerous files including but not limited to GTG Ultimate Unbrick via Odin. Again, PC recognized USB connection however program ddnt. At this point, I do not know if it is because the status of Clockwork Mod on my phone, but I know it is not because of the drivers or the USB ports on my PC.
In addition to that, I have just scrapped the idea of flashing or getting in CWM and just wanted to do a hard reset (While phone is off held Vol down and Power, once started released power and contimued to hold Vol down. This should take the phone from the Samsung logo to an alt menu that will give the option to do a factory reset. But again w/ my luck .. that screen neeever appears.
In short I have tried at least 3 different ways and many maaany variations to get the phone back into recovery or into a full boot and had NO success.. Please help and ask as many questions as needed to diagnose and resolve this issue .. Thanx in advance and apologize in advance if posted in the wrong thread.

Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse

andros11 said:
Are you placing your phone in download mode?
Remove battery and place it back.
Hold vol+ & vol- , and plug in the usb to your phone with the other end already connected to the PC.
Now see if Odin or heimdall recognize your device.
Sent from my sweet & buttery Infuse
Click to expand...
Click to collapse
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.

ohsirus said:
I have done so neither Odin or Heimdall are recognizing it or showing the phone is connected.
Click to expand...
Click to collapse
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
http://d-h.st/sKF
Then open Odin/Hemdall and plug your phone in again while in Download Mode.

Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
I will try again .. Downloaded, rebooting then will go thru the process again .. standby

Ryo Misaki said:
If neither Odin or Hemdall can 'see' the phone, then possibly you don't have the correct drivers installed...
Try downloading and installing these:
Then open Odin/Hemdall and plug your phone in again while in Download Mode.
Click to expand...
Click to collapse
no change .. still shows disconnected

The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2

rkkaranrk said:
The pic u have posted it shows u need to press the up button to get the download mode (continue)
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I just did that to post a pic as an example .. I did go to download mode and not recognizing it

The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!

drnecropolis said:
The CWM screen is shot because you don't have gingerbread bootloaders, it will always look like that until to can flash the right ones..
Have you tried different cables, different ports, etc?
Sometimes mine would recognize.. sometimes being plugged in first then running Odin works, sometimes I would have to run Odin and then plug in the phone.. kinda a crapshoot...
Its powered by Jellybeaned AOKP!
Click to expand...
Click to collapse
I know I need to get the bootloader and a kernel on it however I cant = ( .. yet .. I have 4 different ports on my PC and have tried them all. i have tried phone on then run programs and programs on 1st then phone on and no new results.
I found this short video and it describes my exact situation .. please watch to futher understand http://www.youtube.com/watch?v=OHLUYckTlug

So u have odin and heimdal both on the same PC and drivers for them if yes then try this.
On the PC/Laptop uninstall all the drivers for samsung or any other phone and follow this.
Go to accessories> system tool> system restore and check the restore point where the drivers for heimdall were installed restore to a previous restore point after restore finishes install the drivers for Infuse and see now Odin recognizes ur phone, It should.

I had the same exact problem, do you have another phone on which you can install the same CWM recovery on? ...Because the clockwork mod recovery still works, it's just that you can't see it. So just flash a new ROM, by going back n forth between phones, clock how many clicks it takes to get to 'choose zip to install' then 'download' on the not messed up phone, then do the same on the screwy one, just keep doing that till u flash the new ROM.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app