I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.
So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.
Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.
hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.
I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.
Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.
Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.
Hi guys, i just wanted to unlock my phone's bootloader when my computer was suddenly getting 'blue death'. My phone turned off, I tried to turn it on but nothing happened. After that I found some fixing method like SEUS, Flashtool (installed drivers to recognize my phone..), but im still bricked 'cos none of these programs can recognize my phone. When programs say 'turn off phone - hold back key - plug in usb' i get nothing, i mean i know what is flash mode (with the green led) but i cant get into it. I've tried all buttons on the phone (even combos like - power button & back) but noting. When i plug in the charger the led isnt light. Please help me i want my phone back. - and sorry for my english
Same problem: Hard bricked x10 mini pro
I have exactly the same problem as you.
I have had no success in finding a solution, because the phone cannot enter flash mode. There are absolutely no signs of life in the phone even though bootloader unlock was reported as successful.
Any ideas guys? Or can you recommend a decent, trustworthy repairer?
Cheers
the only one here with any inkling of a solution
if i am not mistaken, the only way to solve this problem is to J-tag your phone.
basically, what that means is you take your phone to a repair shop, they take apart your phone and plug in a chip which enables certain debugging features, and they simply re-flash your phone for you.
however, unless you are willing to buy a J-tag board yourself, you need to pay 20+$CAD for this.
After all, they need to make money too..
Hello,
Long time unregistered lurker, first time poster.
So I was using a nexus one for to long, had a friend root it and he slapped on what I was told was MIUI 9. I know it was MIUI but not confident on the version. It was released and I believe the most up to date version around the time ICS was first released. I had a black ice theme on the device that made menus blue and black, if that helps.
I dropped the phone and screen started bleeding colors and eventually went black. The touch response was still working without issue, but I cannot see anything. I'm trying to recover the pictures off it, and can hook it up to PC with USB, computer installs drivers and responds, however I dont get any new drives available on my PC.
I'm hoping someone has a screenshot of the prompt I would see on the phone to enable mass storage if it asks? Does MIUI prompt to turn on USB storage mode when plugged into a PC? I've honestly never done it with this phone before. Is there another alternative? Tried connecting microSD into adapter then into PC but it advises format and cannot read. Any help greatly appreciated!
Apologies if this is the wrong section :cyclops:
The developer mode for MIUI is on by default, so you should be getting in the USB debugging mode once you plugged it in.
Maybe you should try to do a dirty flash via the recovery mode. If it is still does not work....
Good luck.
Hi,
I have a Samsung Infuse and yesterday when I left it to charge everything was fine, but after I took it out, nothing was working. I mean nothing at all, no Samsung logo, No download mode, no recovery mode, nothing. The LCD or the phone won't start up. I did the basic troubleshooting and the battery and all are fine. I showed it to a mobile hardware repair shop and they said that the hardware is fine and it's a software problem.
Now, since the phone won't even start up, I cannot connect it to windows and hence can't use Odin as well (phone doesn't even go to download mode).
Moreover, I am unable to install the driver on windows since Kies requires the phone to be connected and detected by windows and that isn't happening.
Any suggestions on what could be the problem and how I can fix it ?
Thanks
So my G8141 recently started rebooting whenever it would get disconnected from an audio out source via the headphone jack. That's been happening for about two days. Today, I had it plugged into my car, shut my car off, and my phone rebooted. And continued rebooting. Endlessly. Only way I managed to get it to shut off was Volume Up + Power + Camera (not sure what about that specific sequence did it, but I got one vibration followed by three vibrations, let go, and it was off). I got home, held Volume Down, plugged it into my Windows computer. The LED came on green, Windows found a new device...and nothing. Granted, I just wiped my desktop, so I don't have any of my android debug stuff installed, and I never got around to installing the drivers for this phone before now. So I downloaded the drivers from Sony, tried to install them, and...nothing. Windows says it can't find a driver for the device in the directory. Am I missing something, or is the phone FUBAR?
The phone already needs to go back to Sony for repair (the back cracked about a week after I got it)...do I have any shot of salvaging what's on it before sending it in? I don't think there's much if anything that's important, but I'd like to see what I can do before sending it in...because I bought the UK model from the UK and live in the US...so I have to ship it to the UK repair facility, per Sony help. Also, if I can get it working again, I'm not terribly worried about the back now that I have a case on the way, so I may just live with the cracked back, as long as the phone is stable.
Update: Plugged it into my work MacBook Pro, fastboot devices is giving me
Code:
???????????? fastboot
Same result whether sudo-ed or not.
---
Update 2: fastboot reboot-bootloader followed by fastboot devices lists an actual device. LED is blue. Progress?
Never unlocked the bootloader on this phone, so not sure what I can do from here...thoughts? I can't tell if it's a hardware issue or a software issue...device has updated a couple of times, so it's possible one of those updates introduced a bug. That said, the spontaneous reboot feels more hardware-y to me...reminds me of a PC with bad memory or something. If I could somehow get logs out of it, I suspect I'd find a kernel panic in there.
---
Update 3: Contacted Sony Support, they suggested using Xperia Companion to "repair" the phone. Currently doing what I believe is a stock reimage of the device using Companion. Next step is probably sending it to Sony UK :-/
Just a note for others that might be interested, green is download mode, blue is fastboot.
Well if you haven't unlocked bootloader just repair it? I don't really understand what the issue is about in your post.