Database Develop

[Q] Problem with computer recognizing phone?

After much searching and work on fixing my bricked captivate, i broke down and bought a jig from mobiletechvideos.com. It works perfectly as intended, except for the fact that my pc is not recognizing the phone after it enters download mode. As a side note, i may have royally screwed up when i did something in clockwork recovery, where now i cant even get past the ATT World phone boot screen. Im afraid i may have deleted anything that can mount the phone to the pc. I have already installed the proper drivers, I think. Anything i can do to fix this?

So it shows the world phone screen a bunch of times? Plug it into an outlet see if the green battery comes up, just wait for it, the Gray battery will do a short of loop a few times... Once its at the green battery try to turn the phone on, be patient too, if you get the phone on, go to settings> privacy then factory data reset, make sure you backup to external or computer first
Your welcome
Now you say/press thanks
Teaching manners one person at a time

Thats not gonna work... nothing i know of can be done to it. it doesn't move past the att screen. No animation, not sound. Just ATT World Phone. i can get into download mode, but cant connect to computer. Thats the problem right there.

Try restarting your computer? I've had similar issues on a yucky iPhone, and I've read about other Captivate users with it as well, and a restart helped resolve the problem.

Go under your drivers and uninstall them and reinstall them it helped when I finally had got mine "back to his construction job" (lol download mode) it should then work
Sent from my SAMSUNG-SGH-I897 using XDA App

Ive already tried another PC and Uninstalling and reinstalling the drivers to no avail.
It just like the phone isn't even there. It will charge, but wont mount to the PC.

Not trying to insult your intelligence or anything (I might actually be insulting my own) but you have Odin open, right?
Just trying to think of anything lol

Yeah, but it wouldnt matter anyway if the computer doesnt know its there.

Try cleaning the mini usb port. Or switch the usb cord connector the samsung factory one tends to break the data + and -.
As for not getting past the at&t screen. The kernel you installed cannot read the system partition probably corrupted or the kernel you installed cannot read ext4.
If you cannot get it to be recognized send it back to your carrier for repair, should be under warranty.

Thats what im doing now. Thanks for the help, though.

Palen222 said:
After much searching and work on fixing my bricked captivate, i broke down and bought a jig from mobiletechvideos.com. It works perfectly as intended, except for the fact that my pc is not recognizing the phone after it enters download mode. As a side note, i may have royally screwed up when i did something in clockwork recovery, where now i cant even get past the ATT World phone boot screen. Im afraid i may have deleted anything that can mount the phone to the pc. I have already installed the proper drivers, I think. Anything i can do to fix this?
Click to expand...
Click to collapse
You sure you have the proper drivers installed for your phone? The links for them are on the odin forum in captivate development
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Galaxy Nexus COMPLETELY DEAD. Does not boot into ANY mode.

Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.

wrong forum mate...if you go to this link, they might be able to help you there
http://forum.xda-developers.com/forumdisplay.php?f=1431

hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse

onlinemoon said:
hi, i have same problam with my galaxy nexus. i just want to ask how to fix my phone, thanks
Click to expand...
Click to collapse
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
IamPoison said:
Hello guys,
I have recently bought my first android phone, the Samsung Galaxy Nexus.
On the second day I decided to root it since I needed market enabler, as my local market (UAE) has literally no apps.
I rooted using the SDK tools, fastboot and superboot. Everything worked fine for 1 day.
However, the next day, the phone just died on me, and would not boot at all. It kept getting stuck on the "Google" image at startup. At that point, I could still go into the bootloader. I tried locking/unlocking the bootloader again, since that basically wipes all the date on the phone, but it still refused to load, it would get stuck at the startup animation.
After a few more attempts, it kept spam restarting every time I tried to switch it on.
At that point, I was downloading the default OEM ROM so I could reflash that onto the phone. However, I thought I could try using the superboot bat file again, and maybe that would fix the problem. BIG MISTAKE.
As soon as I ran that file, the phone COMPLETELY died. It will not start at ALL, it will not go into Bootloader, not go into Recovery mode, and not even go into Download (odin) mode.
The ONLY possible response you can get from it, is when you plug it into the PC. My PC seems to play that "detection" sound, same sound as when you plug in a USB, but it would just play that sound over and over again, as if im plugging/unplugging a device really quickly. It seems like the phone is continously restarting itself. When I connect the phone to the PC and that disconnect/reconnect sound comes up, I went into my device manager and I could see the following:
An item under "Other Devices" called "OMAP4440" keeps appearing and dissapearing all the time, with the little "!" mark next to it indicating that there is a driver error. The drivers for this phone are fully installed on this same PC, and it use to work fine before it went dead.
Now the problem is since I cant get into any mode whatsoever, its a bit hard to diagnose the phone. I know there is a "recovery" slot at the bottom of the phone that is accessible with a small pin, but I dont for the life of me know how that works or what it does. Does anybody know how to work that or what it actually does?
Any help would be appreciated! Thanks fellas.
Click to expand...
Click to collapse
i have same problem. can you fix it now?

adesos said:
i have same problem. can you fix it now?
---------- Post added at 08:21 PM ---------- Previous post was at 08:20 PM ----------
i have same problem. can you fix it now?
Click to expand...
Click to collapse
Well done for not reading the thread and realising you were asking the question in the *wrong forum*!

Hey man I have the same problem and my phone is also from UAE. Did you figure it out??
Sorry posting here.

WTF are these guys for real? This thread should have been deleted the day it was started!!

This is posted in wrong section.
**Reported**

Thread Closed​
This forum is for the galaxy note, please post in the correct forum​

[Solved] Slim ICS never loads past logo

I have been running Slim ICS on my Captivate for a month or two now. I have been on version 3.6 for awhile now and have had no issues.
Today however, My phone was acting a little odd, and I decided that it had been awhile since my last reboot, so I held the power button, clicked reboot, (not into recovery) put the phone back in my pocket once I was sure it was rebooting and went on my way.
30 minutes later I took my phone out of my pocket and looked at the screen. It was still on the Slim ICS screen and I thought maybe it was looping, but it never rebooted itself or went back to the AT&T screen. It just stayed on the Slim ICS screen until I pulled the battery.
It has done the same thing every time I try to turn it on.
Download mode wont work (my cappy doesn't have the 3-button combo, so I have to use a jig.) I can get it in download mode but my computers wont read it. I tried uninstalling/reinstalling drivers, I tried different chords (on each computer.) and nothing works.
I'm kind of at my witts end, as it is my alarm in the mornings and I rely heavily on my phone. any suggestions on what to do? or is it time to check if I can upgrade...?
(P.S. I apologize for the sloppy formatting, it's 2:30 am and I've been trying to make this work for 2 hours...)
EDIT: I kept trying and eventually got my phone to read as gadget serial instead of unknown, flashed back to stock and am now getting back to ICS. To anyone in a similar situation, just keep trying and hopefully it'll pay off.

Do you have recovery mode?
Swyped from my ICS Samsung Captivate

korockinout13 said:
Do you have recovery mode?
Swyped from my ICS Samsung Captivate
Click to expand...
Click to collapse
None of the button combos work on my device (none of them ever have) and I cant get my computer to read my phone, so I can't use ADB to reboot in recovery. All I can really do right now is get into download mode with my jig, but none of the computers in my house will read it with any of my chords.

Have u tried "Mobile Odin" by Chainfire ?? Find it in the Market...uuugghh...the Play Store. :/
Sent from my SAMSUNG-SGH-I777 using xda premium

alright, it was a huge headache... but I got back to gingerbread stock.
I'll tell how I did it:
Deleted all installed samsung drivers (and rebooted computer).
Go to download mode (I used the jig, if you have button combos, it's probably easier)
Plug the device into the computer and hope to god it reads as Gadget serial
I then used this to restore to stock (it failed 3 times before it worked... everytime it got just a little bit further, until it finished.)
So ultimately, after a nightmare of a time and a lot of headache, I'm thankfully back at stock, and working on getting back to ICS.
although the process is difficult, as odin still won't find my phone (heimdall does though)

Weird problem with GT-8190L when trying to root, install CWR/TWR or custom ROM

Hi hello howdy!
I'm going to skip the foreplay cose the action here is pretty weird and you'll want to get right in, trust me.
I've a Galaxy S3 Mini GT-8190L, that reboots itself, after it has booted up, and I entered the sim pin and lock pattern I've from seconds to 5 min of grace before the phone restarts itself. I have tried two different batteries and the problem persists. I went and decided to rule out hardware problems (power bttn) and after some tinkering, ruled that out too. So now my best guess is firmware.
The phone is not rooted, does not have recovery mode installed, and is running stock 4.1.2 jelly bean with TouchWiz, no mods, no hack-y stuff, your old regular samsung s3 mini.
I tried installing CM11 with odin, and didn't work. But not because odin threw an error, no, that went on perfectly according to the program. But when the phone booted up, the rom was still stock, nothing changed, and it rebooted itself briefly. Weird. So then I thought "well, maybe at least the recovery mode is there now" since it supposedly was a package install. But no, when I tried to boot onto recovery the phone gets stucked on the boot screen with the samsung brand and model of the phone, and then restarts itself, this happens like four times and then the phone boots normally, the OS starts, everything loads and then goes on to restarting. So this was not a solution either.
Next I though, well lets just install the recovery, no, that didn't work, odin said that the install was successful but it was not. Tried with odin 3.04, .07 and .09, tried CW and TWR, neither of them load, as before, when trying to boot to recovery the phone displays the splash and the reboots itself like four times before starting up the OS.
Next I though well, lets try to root this thing, at this point I was just trying anything to see if anything sticked, but nothing, tried SuperOneClick, and no. Wanted to try TowelRoot but that uses an apk. I tried vRoot against my best judgement, but that didn't work, but not because of the reasons you might think, it did install, the phone managed to stay on for enough time for it to get running, but when it restarted, there was no app there, it was as if nothing was installed just a few second ago. I thought "huhh? That's really weird". So I went and did some testing on this matter.
It turns out that no matter what I do, I can install an app, delete 5 apps, change settings, and nothing sticks, when the phone restarts it goes back to the way it was, its like the phone lost the short memory and its like that Adam Sandler and Drew Barrymore's movie, 50 First Dates. The phone rollsback to the state it was when everything began.
I even tried to change something quick, and restart myself the phone to see if that would make the change stick, but no, that didn't work either.
So, I came up with a brilliant idea, look up a similar case on internet, 'cose you know, it has to have happened to someone else before me. But this is so weird that looking it up is a challenge by itself. I tried a few things here and there but nothing does it. So now I'm here writing my sci-fi story looking for some feedback on how can this story be ended without killing any of the characters, I want everyone to survive and work again. You know, happy endings.
Any ideas on what can be the problem? Seen anything like this before?

Stuck in boot loop after insufficient space on internal storage

Hey guys, I need some help.
My beloved phone got too full the other night and ended up in a coma. Now she..I mean it, wont wake up anymore. I can only get her to open her eyes enough for a couple of blinks, but never really to a conscious state. I'm certainly not willing to let her go and want to keep her from loosing all the good memories we had together... Please help me safe her!...
Enough storytelling...
I've got the Samsung GT-I9252 (Galaxy S4 Active), which is not rooted. Recently I updated to Lollipop which worked fine without any issues.
As I am a usual data horder, I quickly ran out of space (yes, both on the SD card and the internal memory), so that I constantly saw the warning in the status bar that the phone ran out of memory. As I wasn't near a computer I could use for a while to move some files, I continued using it as normal. Because of the lack of memory, the google play store would not install any updates, which was totally fine. However, the Samsung app-store-thing seemed to care a bit less about it and tried to force to download and install what it thought to be "important updates", like for example "text-to-speach" (I haven't even figured out how to use that feature)... Even though there would not be enough space. And I couldn'd really do anything to stop it. The phone started to get slower and I wasn't even able to take pictures anymore (still not around a computer to tranfer data). So the other day I wanted to restart the phone (as I had done a couple of times since the message of lack of space) and it would just not boot up anymore.
It is stuck at the Samsung logo.
My first thought was, well I simply plug it into a computer and transfer some data to make some space and then it would boot up again, but I had to find out that you do not simply plug your phone into a computer and access its data if it refuses to boot...
So I read about the safe mode and tried to find it without any luck (either I'm too stupid to activate it or it got removed). Next I tried to sweep the cache partition, as I managed to get into the recovery boot. It got deleted, but the phone would still not boot.
I definitley want to avoid a factory reset for various reasons!
Then I read about some ways to push/pull data from your phone with a computer, when in recovery mode (with ADB if I recall correctly)... But that's kind of as far as I got.
Now I'm asking for your help and expertise.
Do you think it would be possible to transfer and/or delete some files and if that would solve the problem and lets the phone boot up again; and if yes, how should I approach? Or do you think the cause for the problem lies somewhere completely different?
Thank you so much in advance!
-Nino

Go to Recovery, go to Mount USB storage then connect your phone to your PC. Wait for a few minutes as the drivers will still be installed. Move all your files then try rebooting. I'm not really sure what could be the cause of your problem but if it still doesn't boot up, I've got no clue what other things you could do aside from factory resetting. To be safe, wait for another reply before taking my advise.

Thanks for your reply, VIPNobie!
Well it reminds me that I actually read about it and the problem is that in the recovery boot there is not the option to choose mount usb =/
Don't really understand why.. It would be the easiest solution tho.

Alright, so now I managed to fix it. To be honest, I'm not exactly sure what the problem\solution was. My plan was to connect it with Heimdall and see what I could do through that.. I set the phone in download mode, got the drivers installed and detected the device in heimdall, I ran the command to list the partitons and as soon as that finished, the computer notified me that the device had been disconnected and my phone restarted by itself... tho this time it booted normally as if nothing happened.. so I could back up my data, still need to try to restart the phone, but just wanted to make sure that I got everything backed up.
So even if this might not help others, this thread can be set to solved I guess
Thanks again.

I have the same problem. what did you mean by "I ran the command to list the partitons". Please provide more details.

Donino said:
Hey guys, I need some help.
My beloved phone got too full the other night and ended up in a coma. Now she..I mean it, wont wake up anymore. I can only get her to open her eyes enough for a couple of blinks, but never really to a conscious state. I'm certainly not willing to let her go and want to keep her from loosing all the good memories we had together... Please help me safe her!...
Enough storytelling...
I've got the Samsung GT-I9252 (Galaxy S4 Active), which is not rooted. Recently I updated to Lollipop which worked fine without any issues.
As I am a usual data horder, I quickly ran out of space (yes, both on the SD card and the internal memory), so that I constantly saw the warning in the status bar that the phone ran out of memory. As I wasn't near a computer I could use for a while to move some files, I continued using it as normal. Because of the lack of memory, the google play store would not install any updates, which was totally fine. However, the Samsung app-store-thing seemed to care a bit less about it and tried to force to download and install what it thought to be "important updates", like for example "text-to-speach" (I haven't even figured out how to use that feature)... Even though there would not be enough space. And I couldn'd really do anything to stop it. The phone started to get slower and I wasn't even able to take pictures anymore (still not around a computer to tranfer data). So the other day I wanted to restart the phone (as I had done a couple of times since the message of lack of space) and it would just not boot up anymore.
It is stuck at the Samsung logo.
My first thought was, well I simply plug it into a computer and transfer some data to make some space and then it would boot up again, but I had to find out that you do not simply plug your phone into a computer and access its data if it refuses to boot...
So I read about the safe mode and tried to find it without any luck (either I'm too stupid to activate it or it got removed). Next I tried to sweep the cache partition, as I managed to get into the recovery boot. It got deleted, but the phone would still not boot.
I definitley want to avoid a factory reset for various reasons!
Then I read about some ways to push/pull data from your phone with a computer, when in recovery mode (with ADB if I recall correctly)... But that's kind of as far as I got.
Now I'm asking for your help and expertise.
Do you think it would be possible to transfer and/or delete some files and if that would solve the problem and lets the phone boot up again; and if yes, how should I approach? Or do you think the cause for the problem lies somewhere completely different?
Thank you so much in advance!
-Nino
Click to expand...
Click to collapse
Lacking storage booting is the option you choose. Fixed it?