Database Info

What have I done?: Not bricked but phone can't be recognized any longer

I was trying to install Cyanogen 7 and my first step was a one-click return to stock that seemed to complete fine.
When I rebooted I go into Android 3e recovery. Each time I boot the recovery message says:
Update media. please wait
update media. finished
#manual mode#
--Applying Multi-CSC...
Installing Multi-CSC
Install default apk-files. please wait
Install default apk-files. finished
The phone is no longer recognized by windows even though I've tried several different versions of the Samsung drivers. (also tried different USB ports, different cables and different computers per my search results in here)
I can get into Download mode but the device is not recognized so its not recognized by any of the ODIN utilities to repair or restore...
Any idea what is going on - or more importantly what can I do to recover this thing?
Help?
Thanks!

First of all, I would try Heimdall One-Click instead of Odin. It's more reliable, and uses better drivers. Will it not reboot into Froyo? And which one-click package did you use?

I used the Heimdall One-Click and it seemed to complete okay. Trouble started when I rebooted. I can't seem to redo it because the the One click utilities don't recognize the phone as connected.
I always get the Windows message "USB Device is not recognized" and when I go into my Device Manager the phone is listed as an "Unknown Device"

I would strongly advise against flashing back to froyo or eclair as the bootloaders are out dated.. As.for.your phone not being recognized it could be a number of issues from anywhere to ypur pc.needs a reboot to your usb cable is bad. I once had the same issue and i reinstalled the samsung drivers a few times with no reults. Believe it or not what fixed my problem was a fresh install of kies (a program i never use)
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I installed Keis, rebooted and it did in fact recognize and re-install the drivers. I then tried the heimdall 1-click and it failed on the attemped handshaking with Loke step. Now I am back to not being able to recognize the USB device again.!
ugh!

WinoOutWest said:
I installed Keis, rebooted and it did in fact recognize and re-install the drivers. I then tried the heimdall 1-click and it failed on the attemped handshaking with Loke step. Now I am back to not being able to recognize the USB device again.!
ugh!
Click to expand...
Click to collapse
Heimdall uses completely different drivers
Sent from my SAMSUNG-SGH-I777

Yes it installed the heimdall drivers successfully when I tried to run the on-click. Then it timed out. I now appear to be back to an unrecognized device again. Installing Keis, Samnsung drivers etc trying to get it to recognize the phone again. It easily goes into download mode.
Anyone got any ideas how I can get this thing breathing again?

Try rebooting the computer. Use a USB port in the back of the computer. Try a different cable. Open Odin before connecting phone to computer.

mrhaley30705 said:
Try rebooting the computer. Use a USB port in the back of the computer. Try a different cable. Open Odin before connecting phone to computer.
Click to expand...
Click to collapse
Tried all of this - still no love. Every once in a while it will search and install Samsung drivers but then it disconnects almost instantly.
I also fumbled through getting a Ubuntu up to try it in Linux but the download mode isn't found in linux either.
Running out of options here. Wondering if I've pooched this phone.

WinoOutWest said:
Tried all of this - still no love. Every once in a while it will search and install Samsung drivers but then it disconnects almost instantly.
I also fumbled through getting a Ubuntu up to try it in Linux but the download mode isn't found in linux either.
Running out of options here. Wondering if I've pooched this phone.
Click to expand...
Click to collapse
Its not broken permanently, I promise.

Well slap my a$$ and call me Judy!
After 1 million attempts (cords, ports. pcs, windows, linux) I finally managed to get back into my phone. I literally must have had this phone in and out of download mode several hundred times in the last 24 hours. One of my attempts finally worked in Ubuntu! Not sure why really - but I am okay with that at this point.
Thanks for all you help!
Darren

<smack> good job Judy.

[Q] Samsung Galaxy 5 (GT-I5500) won't connect to PC!

I've tried a few other forums but haven't got any replies, I guess since the Galaxy 5 isn't such a popular device. I figured if there's anyone who can help me they will be here though.
I wanted to put CWM on it so I could get a CM7 port on. Unfortunately it's just about impossible for it to get detected on USB. I've installed Kies (and even the generic USB drivers found in the SDK). In 2 days I only got it to connect once, and then I went and bricked it.
The one time it finally connected I ran Odin and tried loading CWM onto it. It still hadn't finished after half an hour so I figured it ended with an error that was never displayed. So I unplugged it and as expected - brick! I can get into download (upgrade/firmware) mode so I think it can be fixed if I can get CWM on it (and just install the CM7 port I had originally intended to put on).
Problem is I cannot get the darn thing to connect! to my computer I've tried two separate PCs, one running Window 7 x64 and another running XP x32. Is there a a certain process of connecting things? I haven't ran across anyone making mention of one.
Has anyone else experienced USB problems like this with Samsung phones? Would it even be possible to flash CWM on after it's been bricked like this? When I boot (normally) all I get is an image showing a phone and a PC with and exclamation error connecting the two. Please help!

Try to look for stock firmware on the forum.xda-developers.com and flash via ODIN. You need to be able to put the phone into download mode, so maybe get an USB jig. That should do the trick. Odin has to recognize your phone. First of all right click on the ODIN executable and select "Run as administrator" on windows. Plug the phone in the DL mode and wait until it appears as active in Odin. Then flash the ROM and pit file. (Don't use ODIN one click). If ODIN does not recognize your phone try a different USB port or reinstall Kies. The Kies trick was which I used and it was able to recognize my phone.

Thanks, martin0176. I can still manage to get the phone into download mode - it's getting recognized by a PC that's the problem.
Could you tell me more about the pit file? I only have an ops file.

Try a different cable. I was having the same problem on the Samsung Continuum and it turned out that the cable was working for power, but not for data.

[Q] Help Needed: bricked or not and what to flash with Odin

Hi,
I have an issue with a Nexus S i9023 of a friend
I installed the latest stock ICS CF_YAKJU_IMM76D some months ago and everything was fine.
I broke the glass of the screen and it was substitued: after a couple of months, the phone entered in a bootloop.
I tried to access recovery but was impossible, I could get to Fastboot and Download mode but choosing recovery from the first started bootlop again.
I flashed a latest CWM in fastboot via adb but no joy.
On top of that, handset behaviour is strange because only 1 on 20 times it is recognized by the PC as a Samsung device, in all other cases it is a "unknown device".
I remove all drivers from Windows and reinstalled the naked version, but again only sometimes I get it... I found out I need to have connected another handset (my HTC currently...) to have it recognized!
Now I can enter in download mode using the USB jig and I can see it from Odin, but if I use the
CF_YAKJU_IMM76D_full.tar
I get "verify image ipbl (fail)" on the handset.
If I use
CF_YAKJU_IMM76D_nowipe_nobootloaders_norecovery.tar
I get an "invalid volume size"
Do I have an hardware issue here? Some partition/internal memory with failure?
What else can I try to flash via Odin?
Obviously now after the fail I can't even get fastboot...
I also tried Unbrickable resurrector under Linux but it doesn't recognize the handset when I connect it.
Any suggestion? :crying:

SergioBigred said:
Any suggestion? :crying:
Click to expand...
Click to collapse
Ok, update. Using this thread I was able to flash via Odin 1.82 the 2.3.4
However I am still in a bootloop and I can't get fastboot but not recovery... and in fastboot I can't via USB the handset because it says "usb device not recognized"

[Q] Samsung Galaxy S - cant flash

Hi there,
I've read every kind of threads here and no one works for me. I rooted my Samsung GT-I9000 and all worked well, then the phone started acting crazy, my root was gone and when I boot the phone I come to the usual screen where you enter pincode but after that the popup screens start, multiple popups saying that twlauncher crashed, media, acore etc.. so I cant get to the screen where I can enable usb debugging. I can enter the stock recovery and my PC can contact the phone, but when I press vol down + home + power so I get the download mode the PC cant find the phone, not in win7 or in Linux. I have tried every kind of driver there is for Samsung but no one works that make it possible for the PC to find the phone when it is in download mode, win7 list it under "unknown device" and NO driver at ALL works so win7 can reqonize the phone. I've tried installing Kies how many times I dont know and uninstalling, updated SDK, uninstalled every USB driver and even the hubs and installed them again, updated win7.. what can I do to flash the phone!?!? Because Odin, no matter old from new; cant find the phone in DL mode, same with linux. And in stock recovery, I wiped cache and data but the problem is still there when I enter the OS after enter my pin...
How can I flash my phone without PC finding the phone in DL mode and no USB debugging enabled? Or how to flash CWM so I can flash a ROM from SD? Please help!!

At first try another PC with Winsows or use another USB cable.
About recavery-try to find temperery recovery or cwm,that flash from recovery.

DeMaCr said:
At first try another PC with Winsows or use another USB cable.
About recavery-try to find temperery recovery or cwm,that flash from recovery.
Click to expand...
Click to collapse
As I wrote, my desktop is under Linux and the laptop under Win7 and none can reach the phone, both computers can only detect the phone in Recovery mode, but the laptop under Win7 only detect the phone as offline, Linux on the other hand can reboot phone into recovery from recovery, to download mode and reboot normal. Already tried to use Ubuntu 13 Live and it cant detect the phone in DL mode either. And tried different cables also. And if I find a recovery or CWM, then what? Dont I need to get phone into DL mode to flash something?
But in Linux I've got a small breakthrough, Heimdall can detect the phone know, but fails to flsah anything. Maybe wrong files or something..? But anyhow, if Heimdall now can detect the phone and it couldnt before; know I just need the right files to flash.

Just find a friend who owns Windows desktop/ laptop, download stock from Sammobile, flash stock via Odin. If not, try Odin mobile...

Accidentally deleted my OS on Samsung Galaxy S7. Nothing works!

I have a rooted S7 with TWRP recovery on it and i recently deleted my OS by accident as i was just trying to reset my phone to factory settings. Now the only thing i can do is boot into recovery mode and download mode, or i can just get stuck at a boot loop.
I have googled and googled and seen so many ways to try and fix this issue but nothing has worked for me. Heres a list of the issues i have and what i've tried so far. [Using Windows 10]
Installing Odin (3.12.3) and stock Samsung firmware from here.
Installing the necessary USB drivers from here.
My PC wont recognize my samsung device in either modes (recovery/download) and Odin wont recognize my phone either, as well as i cant find anything under "Device Manager".
Tried using ADB to transfer files to my S7 but when i activate ADB in recovery mode it just loads for a couple of seconds until it displays an error with no explanation.
I even tried downloading ADB drivers and necessary tools i got from this guide.
I also tried wiping Dalvik cache and cache.
I have tried three different USB cables on all available USB slots on my desktop PC and the one USB slot in my Surface and nothing works.
I have tried rooting previous phones but I'm still new to this rooting thing and there's a lot i don*t understand. Perhaps i downloaded the wrong USB drivers, or maybe I'm just unlucky. I just really need some help to understand how to fix this. If it can't be fixed is it possible to remove all traces of rooting on my phone?

The phone needs to be in Download Mode to use ODIN
The only sign it is connected is a COM port lit up at the top of the ODIN window
Add the .MD5 ROM to AP and hit start