Database Info

[Q] Bricked Phone - Help!

Hey guys,
I tried flashing stock JH7 after disabling lagfix. When I tried to reboot, I ended up in a boot loop and the phone kept getting stuck on the "AT&T World Phone" screen. I can access stock Samsung recovery and Download Mode, but, although I tried numerous methods, Odin3 doesn't recognize my phone in Download Mode. I also don't have any update.zip or backup on my phone that I can flash in stock recovery.
Is there any way I can fix my phone without Odin3? If not, how can I get Odin3 to work on my computer? I'm running Windows 7 HP x64 on my laptop, and I have adb installed, but can't access adb shell for some reason.
I searched numerous threads but couldn't come up with a solution. Please help!

psai said:
Hey guys,
I tried flashing stock JH7 after disabling lagfix. When I tried to reboot, I ended up in a boot loop and the phone kept getting stuck on the "AT&T World Phone" screen. I can access stock Samsung recovery and Download Mode, but, although I tried numerous methods, Odin3 doesn't recognize my phone in Download Mode. I also don't have any update.zip or backup on my phone that I can flash in stock recovery.
Is there any way I can fix my phone without Odin3? If not, how can I get Odin3 to work on my computer? I'm running Windows 7 HP x64 on my laptop, and I have adb installed, but can't access adb shell for some reason.
I searched numerous threads but couldn't come up with a solution. Please help!
Click to expand...
Click to collapse
Have you tried reinstalling your drivers?
My laptop won't recognize my phone anymore for the Android UMS drivers so I've been using my desktop to flash using Odin.

I've tried, but Odin only recognizes my phone in recovery mode and doesn't recognize it in download mode.

Fixed at last!
I finally fixed my phone! I found out that I was using the wrong USB drivers -_-
I installed the correct drivers, and voila, my phone was recognized by Odin3
Sorry for the n00b error

[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] Broken USB connection, possible brick

I have a NS i9020T which was running the latest MIUI ROM until I tried to update it to MIUI ICS. I had noticed, while running pre-ICS, that my computer wouldn't mount USB storage. As a working around (rather that trying to fix the issue) I just FTPed files. When I tried to install MIUI ICS something went wrong (probably corrupt ROM image) and now my NS won't boot.
If I go through Clockwork Recovery to mount USB mass storage, nothing happens. I'm running OS X, but I've tried mounting in Ubuntu 11 and Win7 -- Windows recognizes that there is a device there but the drivers won't recognize it (I think).
Finally, I've tried flashing a new recovery using fastboot but I get "<waiting for device>" in Terminal.
My best guess is that the USB connection is shot, which would probably require me ripping the NS open and tinkering around (which I have zero experience doing).
Does anyone have any ideas for fixing what is likely a permanent brick? I can boot into Win7, OS X, or Linux to troubleshoot. Also I'm on the XDA IRC as "threepape" right now trying to solve this issue.
Thanks in advance!

I was working with threepape on IRC trying to narrow down the issue.
Basically he's had his phone rooted, tried flashing a rom and now it's stuck at the boot screen. He went to connect to his computer and it gave him an error. and wouldn't let him connect his phone to the os. This is a problem.
So he then downloaded kies to see if it would install drivers automatically, downloaded odin and then tried to see if odin would recognize the phone. It did not and his computer gave him the error "unknown USB device, error code 43"
So we reviewed what we could control: trying different cords, checking drivers, etc.
Now we are going to try booting into an osx platform, installing heimdall and seeing if "heimdall detect" prompt will detect the phone. If that doesn't work we're going to either need more help or rule it out as a hardware issue.
<threepape>
Failed to detect compatible download-mode device.
[8:55pm] <ddrt>
so you typed out heimdall, then heimdall detect and it came back with that?
[8:55pm] <ddrt>
and you are 100% it was in download mode?
[8:55pm] <threepape>
yep
[8:56pm] <threepape>
it does ay on my phonee "USB Control Init USB Control Init End"
Click to expand...
Click to collapse
edit: device is not being detected on multiple os using different programs, device will not wipe fully when doing a factory restore through CWM. I am at a loss.

[Q] phone bricked and not getting detected on computer

Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??

Morphie said:
Hi,
my friend's Nexus S was stuck in a bootloop. i went into recovery mode and hard reset the phone, so that the phone would come back to stock. however, the phone was being reset when the battery of the phone came off, switching it off.
the phone fails to start. there is no response when i try charging it. Also, it does not go into DOWNLOAD mode or FASTBOOT, so i cant even run any utilities to flash the stock rom back. adb commands as well as the nexus toolkit show that there is no device connected.
can anybody suggest me what to do?? i was gonna try odin but i read somewhere that it is only useful for custom recoveries, not to flash stock roms.
i've gotten some usb drivers mentioned at some thread, saying i would have to update my 'android' device listed in the device manager using them, but i cant seem to find any device mentioned in my device manager either.
any suggestions as to what i should do??
Click to expand...
Click to collapse
Something like this happened to me a week ago. I have Nexus S 4G. So, I ordered USB Jig from usbjig.com and now I have download mode. It worked! :laugh:
You can buy USB Jig from that site, or build it yourself, or borrow it from someone.

Stuck at bootloop after update, can't access ADB.

Hi, I need your help here. I'm trying to fix my friends phone for her. What she told me is that it got stuck at the second boot screen after an update. She also said that it happened before and her father got it working. So my first thought was to clean flash stock firmware but I can't get ADB working. I've installed usb drivers and minimal ADB and fastboot but it doesn't recognize the phone in "adb devices" (I have no idea if USB debugging was on in dev options but I'm assuming it wasn't). I have no idea what to do now as I'm not that familiar with Xiaomi firmware.
Thanks in advance.
Edit: Xiaomiflash sees the device but not as COM.. but 72e728fb (?) and trying to flash it in this state ends with error:Flash xbl error