Related
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
donk232 said:
Well to start out I have googled the drivers but still doesn't work... after bricking it pretty bad this happen and I fixed it by drivers while bricked to flash it to stock. But it has happened to me again after odin. Is it possible to just break it. Can someone link me working drivers maybe I've been trying ones that don't work or something
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Make sure you are using the oem usb cable. I had the same problem, changed cables and it worked
some cheap cables are for charging ... bt headsets and other stuff the data cables dont connect, its just for power.
koreancanuck said:
It's not recognized when the phone is on? Seeing as you posted this topic using your phone I assume so lol. Have you tried restarting your computer?
You can download the correct drivers here.
http://forum.xda-developers.com/showthread.php?t=731989
Click to expand...
Click to collapse
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
donks232 said:
deleted drivers restarted, installed drivers restarted and still not working. i am using the cord that came with the phone.
Click to expand...
Click to collapse
You gotta make sure that your usb port is directly connected to your motherboard (usually back of your computer).
same usb port that has always worked. ive tried them all by now anyway
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
donks232 said:
now i cant tell you how this helped but... i downloaded drivers to a different computer odin crashed while flashing reflashed and im 100% stock atm. Didnt do ANYTHING to my computer plugged it in and its working.
Click to expand...
Click to collapse
lolol
Duno what happened but I'm glad it worked out for you
I'm having the same problem with my captivate after flashing REDROM. It won't recognize it if I have USB debugging turned on...
i have a theory... were you on a GB or other i9000 based rom/kernel???
well, im still having a problem getting my computer to recognize the phone, i have to mess with it for a a while to get it to work. i really want to flash anew 2.3.3 rom but without being able to get everything working right im stuck in 2.1
is this a problem with my cord or the connection on my phone? or something weird with my phone after flashing it a lot. its currently back to odin stock, i have been trying to master clear it with no luck
TRusselo said:
i have a theory... were you on a GB or other i9000 based rom/kernel???
Click to expand...
Click to collapse
continiuum miui and cyanogen mod are the only things ive tried to flash
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Guys, this problem while connecting to the PC body is stupidly charging .... Even in the download mode Odin does not see a body that could be? Connect other Cappy-all OK.
donks232 said:
well it looks like i'm done. my phone will not show up on my computer and its currently bricked, although i have no issue getting it to download mode i cant do anything with it. unless someone knows some magic, looks like im downgrading to my gf's 4 year old busted up BB
Click to expand...
Click to collapse
it must be a powered usb hub, on my buddies laptop only 1 out of 4 usb ports saw his phone.
if you can get into download mode you arent bricked.
try installing i9000 drivers, or try another computer.
I came up with this a while back. Could very well be the same issue.
Let me start by saying I'm flash happy, and everyone that knows me personally, tells me to just quit jacking with my phone. NOT A CHANCE! I'm on my 3rd Cappy and shouldn't have ever exchange it again. I only had to in the beginning, because I was a newbie and had not know enough, but to get me in trouble.
I presume that this should work on all Windows OS's. I personally am running Vista Enterprise x86.
My symptoms:
Plug in phone to the usb and it there was about a 15% chance off being able to mount to usb, and Windows recognizing as a mass storage device. I tried un-installing drivers and re-installing and it would work some of the time, until the point came when parts of the driver install would fail. Then to the point when it was just completely unrecognizable. I thought I had it fixed because it seemed intermittent. In the middle of flashing to stock, something interrupted communication between the pc and my phone. Restarted the phone and attempted the flash again. Got a little farther and froze again. I had to use another pc that I had never connected my phone to before and I was able to use my jig to trigger download mode, because no buttons combinations would allow it into download mode.
This got me thinking that it was specific to my pc and not my cable or my phone.
My resolution:
I went straight to the registry and went to find. I deleted every entry that came up for "i897" and "i9000" excluding what was listed in the system volume information, as I didn't have permissions to remove any keys. I didn't keep count, but I probably deleted 300-400 registry keys that pointed to my phone. It seems as if with each developers rom that I had flashed, there was an entry for a different device. Don't quote me on that, because it is just my personal consensus. I also un-installed the samsung drivers, the unknown device driver, kies software, and anything associated with samsung. I noticed that next to all of the i9000 instances, the hex key for me started with 1000ee. So I also searched for the first part of that key trying to ensure that all instances of the device. Lastly, I deleted the samsung folder from program files.
I installed the samsung drivers package commonly listed in all of the other threads for x86 operating systems. I plugged in my phone and watched as each and every driver installed successfully. Keep in mind different drivers are installed depending on if you have usb debugging on/off, and the options for if the preferences on you phone are set to media, storage, or kies. I have multiple usb ports, however testing has shown me that, for me and my setup, I can plug into the port that I used when installing the drivers the final time, I am able to connect consistently. Earlier today, I tried to plug into a different usb port and it was an unknown device. I am led to believe, this is because I didn't un-install the unknown device on this particular port.
If you intend to work in the registry, please remember to always back it up first. You can always restore.
Hopefully my findings can help you as they did me. Happy flashing and I would like to thank the community for the dedication to assisting each other and the developers, for making flashing, better than crack cocaine. Flashing rom's doesn't make you twitch near as much as a crackhead.
Well since you can't use your phone you should sell it to me
Sent from my GT-I9000 using XDA Premium App
I didn't even install drivers, ubuntu got them for me
Sent from my SGH-I897 using XDA Premium App
Long story short, I've been haiving a bunch of problems, and someone pointed me to an update.zip file that might help me unroot my phone without needing a USB connection. When I go into recovery mode and select "install package", I get this message:
E:signature verification failed
installation aborted
Does anyone know what I may need to do in order to clear this up freaking problem?
first you might want to look at the stickies in general, thats what they are there for. if you dont find your issue SEARCH. 2 minutes of effort would have found you this http://forum.xda-developers.com/showthread.php?t=1052991
studacris said:
first you might want to look at the stickies in general, thats what they are there for. if you dont find your issue SEARCH. 2 minutes of effort would have found you this http://forum.xda-developers.com/showthread.php?t=1052991
Click to expand...
Click to collapse
Omg.. Another signature failed issue lol
Thanks for taking care of this one Studa
My apologies. I did look at the "related topics" that came when I did my post, but that one didn't come up. Guess I wasn't through enough.
I'm pretty new to all this, and I'll admit that part of that linked thread is a bit over my head so this may be another stupid question. My main issue is that I get an error trying to connect via USB, and it looks like all those fixes require Odin 1 click. Does one of those methods allow for the fix without a USB connection (I do think I have the ability to get a file from the computer to my phone via the external SD card).
Girevik said:
My apologies. I did look at the "related topics" that came when I did my post, but that one didn't come up. Guess I wasn't through enough.
I'm pretty new to all this, and I'll admit that part of that linked thread is a bit over my head so this may be another stupid question. My main issue is that I get an error trying to connect via USB, and it looks like all those fixes require Odin 1 click.
Click to expand...
Click to collapse
What you mean you get an error connecting the USB? Could you be more precise?
Also, the signature failed fix is quite easy. Tbh, you simply have to have your phone plugged in in debugging mode and run the .bat file.
Please explain your usb issue.
BWolf If the phone won't connect to usb he can't use the .bat
studacris said:
Please explain your usb issue.
BWolf If the phone won't connect to usb he can't use the .bat
Click to expand...
Click to collapse
I know, I know. I was saying for when/if it works. Duh
When I try to connect via USB I get a "USB Device Malfuctioned" error. (Which I HAVE searched on ) that I can't seem to find a fix for. I've tried it on 3 different computers, each with a different version of Windows, with the same result so don't think it's a driver issue.
I've done a factory data reset (several atually) and am still having problems, so I'd like to get a warranty replacement. But my phone is rooted so I'm worried about them voiding my waranty. Basically where I am now is tryign to find a way to unroot my phone without the USB so I can get it replaced. That lead me to the signature verifaction error and the shame of a premature post.
how loose are your ethics?
if your phone doesnt boot at all they can't tell if its rooted. a few 2 second bursts in the microwave should do it, don't do it any longer than that at a time. you don't wanna have any physical signs you just wanna fry the curcuits.
just PLAY DUMB and you should get a warranty replacement.
studacris said:
how loose are your ethics?
if your phone doesnt boot at all they can't tell if its rooted. a few 2 second bursts in the microwave should do it, don't do it any longer than that at a time. you don't wanna have any physical signs you just wanna fry the curcuits.
just PLAY DUMB and you should get a warranty replacement.
Click to expand...
Click to collapse
I'm not opposed to hiding the fact that it's been rooted, or if a fix I tried bricked it I'd be okay returning it, but I'm not sure I want to go as far as frying it in a microwave.
I've been looking for an ap in the market that would unroot for me, but so far none of the ones I've found have worked for me. Do I have no other options for something I could load directly to my phone via the SD card (I do have the ability to put something on my external SD card and transfer it over to the phone)?
Girevik said:
I'm not opposed to hiding the fact that it's been rooted, or if a fix I tried bricked it I'd be okay returning it, but I'm not sure I want to go as far as frying it in a microwave.
I've been looking for an ap in the market that would unroot for me, but so far none of the ones I've found have worked for me. Do I have no other options for something I could load directly to my phone via the SD card (I do have the ability to put something on my external SD card and transfer it over to the phone)?
Click to expand...
Click to collapse
no apps that i know of work for froyo to root/unroot without needing a computer and a working usb port ... what you will have to try is fix the 3e recovery manually. i dont think that update.zip will unroot, it just roots, but you could try. If that doesnt work go grab cognition rom from development flash that but while its in the process pop the battery out. if youre "lucky" you will either get a "phone....!....pc" screen or a hard brick in either case all eveidence will be erased.
this process will require some research and learning on your part...
Are you SURE you have the correct drivers for your computer? When I tried to use my phone on someone elsewhere computer the computer would not install it until I installed the samsung drivers from the odin one click post.
Can you get into download mode? Method varies based on build number or phone. Try turning your phone off, holding the two volume keys and plugging in usb, if you see a big yellow triangle with an android and a shovel you are in download mode. Once in download mode the computer will see your phone as a different device and install more drivers. If all that works, you can use odin one click to go back to stock.
Once back to stock your problem may be fixed anyway, if not it will be unrooted and you can return it to att. Morals intact.
Sent from my Captivate running FireFly
studacris said:
no apps that i know of work for froyo to root/unroot without needing a computer and a working usb port ... what you will have to try is fix the 3e recovery manually. i dont think that update.zip will unroot, it just roots, but you could try. If that doesnt work go grab cognition rom from development flash that but while its in the process pop the battery out. if youre "lucky" you will either get a "phone....!....pc" screen or a hard brick in either case all eveidence will be erased.
this process will require some research and learning on your part...
Click to expand...
Click to collapse
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
But like Studa said, you have some reading to do
quarlow said:
Are you SURE you have the correct drivers for your computer? When I tried to use my phone on someone elsewhere computer the computer would not install it until I installed the samsung drivers from the odin one click post.
Can you get into download mode? Method varies based on build number or phone. Try turning your phone off, holding the two volume keys and plugging in usb, if you see a big yellow triangle with an android and a shovel you are in download mode. Once in download mode the computer will see your phone as a different device and install more drivers. If all that works, you can use odin one click to go back to stock.
Once back to stock your problem may be fixed anyway, if not it will be unrooted and you can return it to att. Morals intact.
Sent from my Captivate running FireFly
Click to expand...
Click to collapse
I'm pretty sure on the drivers. I removed what I had and re-installed from a link I found online. From the searching I've done it seems that "Device Malfunctioned" error is the kiss of death. I've not found anyone yet who's recovered from that.
I remember getting into dowload mode when I did the update to 2.2 but don't recall the method. plugging in the USB cable with the volume buttons pressed just powers up the phone.
Girevik said:
I'm pretty sure on the drivers. I removed what I had and re-installed from a link I found online. From the searching I've done it seems that "Device Malfunctioned" error is the kiss of death. I've not found anyone yet who's recovered from that.
I remember getting into dowload mode when I did the update to 2.2 but don't recall the method. plugging in the USB cable with the volume buttons pressed just powers up the phone.
Click to expand...
Click to collapse
The method is actually a bit different then what he mentionned:
Unplug usb;
Pull battery;
Hold volume buttons (and keep holding no matter what);
Plug usb in your pc and then your phone;
Put the battery back in and wait until the android with a shovel shows up.
It can take a few tries too before it works.
studacris said:
what you will have to try is fix the 3e recovery manually.
Click to expand...
Click to collapse
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
BWolf56 said:
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
Click to expand...
Click to collapse
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
BWolf56 said:
lol Studa, you should stop helping people with their phone and start helping them destroy it
As for Cognition, it flashes the 2nd bootloader (sbl.bin) and once you start playing with bootloaders, you increase your chance of bricking. Which is why Studa suggested it.. Basically, you could just unplug your phone when Odin if showing Sbl.bin and you would have a brick in your hand = You bring it to the store saying it never turned on again after updating through Kies.
But like Studa said, you have some reading to do
Click to expand...
Click to collapse
Hahaha I know this is a nice change.
But with his usb issues I doubt odin will ever recognize the phone.
Girevik said:
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
Click to expand...
Click to collapse
No flashing a rom doesn't require odin. And the manual fix should be on the sticky
Girevik said:
Was that one of the options in the sticked in the response to my original post? If so I must've missed it....
But doesn't Odin require a USB connection? I guess I thought flashing any rom required a USB connection.
Click to expand...
Click to collapse
No, you actually shouldn't flash a ROM with the usb plugged in (UNLESS using Odin lol). I guess my point was that you could have Cognition on your ext sd card and flash it but didn't think about the signature failed.
studacris said:
Hahaha I know this is a nice change.
But with his usb issues I doubt odin will ever recognize the phone.
No flashing a rom doesn't require odin. And the manual fix should be on the sticky
Click to expand...
Click to collapse
You could always get Root Explorer and switch the recovery by yourself from your phone. That's actually what I did back when I was on 2.2 - Then again, you have to pay for Root Explorer and you have some more reading to do if you wanna take that path.
BWolf56 said:
No, you actually shouldn't flash a ROM with the usb plugged in (UNLESS using Odin lol). I guess my point was that you could have Cognition on your ext sd card and flash it but didn't think about the signature failed.
You could always get Root Explorer and switch the recovery by yourself from your phone. That's actually what I did back when I was on 2.2 - Then again, you have to pay for Root Explorer and you have some more reading to do if you wanna take that path.
Click to expand...
Click to collapse
1. I don't think you can flash from the external sdcard, he will have to download it with the phone itself to get it on the internal sdcard.
2. The root explorer method is the manual fix I'm talking about.
studacris said:
1. I don't think you can flash from the external sdcard, he will have to download it with the phone itself to get it on the internal sdcard.
2. The root explorer method is the manual fix I'm talking about.
Click to expand...
Click to collapse
That was imployed but Fine be that way! lol
So yea, OP - Beside all that Team confusion we're having here.. Go read/keep reading the Sticky about 3e recovery fix and if you think you can do it. Do the manual fix (getting Root Explorer and moving the recovery file by yourself) and get Cognition on your external and move it to your internal sd card.
(There I'm being clear Studa )
So heres the thing.
I flashed some firmware on my phone (did it 100 times no problem) but i got fail in odin.
I said ok nothing is wrong i can fix it. but to my suprise Odin wont recognise my phone. I get a message that the Usb is unknown.
Now beacuse i reinstalled my drivers i think that the computer needs a first time plug of another galaxy s to install the driver from the phone is that correct? (Cause my phone can only go to download mode)
so all i need to do is to get another galaxy s plug it in and let the computer recognise it for the first time. and than use my broken phone phone and it will work?
what firmware was it ,if it was ics sometimes you lose usb connections and odin wont recoqnise the phone
TIGER 123 said:
what firmware was it ,if it was ics sometimes you lose usb connections and odin wont recoqnise the phone
Click to expand...
Click to collapse
@Topic started i have the same problem and have a similar thread.
as for tiger. . . does that mean ics users are screwed if that occurs to them?
http://forum.xda-developers.com/showthread.php?t=1431523
I used this one
Problem solved here. I hope this solution helps you
I've tried so much, seriously SO MUCH. At the end it turns out it was my usb cable. i ripped my old usb cable apart for making me go ape ****.
lesson? No matter how many times you install, change ports, etc. Always be sure to try a new usb cabel. If you don't have a second one, i'd suggest you go buy a second one, it's worth a try. The whole time it wasn't working it was my stupid usb cable, changed it and in an instance i was ready to roll.
Wish you good luck!
Ok so I purchased an i9000M that was advertised as broken (got it for cheap) to see if I could get it going for my step daughter. I turn it on.... I get the samsung boot screen and goes black when it should be booting OS.
Windows still recognizes it somewhat. If I look in device manager under "portable devices" It shows a "j" and "k" drive that are identified as i9000 and i9000 sd or something like that. Although Windows sees it.... It wont mount these drives unfortunately.
Things I've tried ( Before someone suggests I use a JIG............. It doesn't and will not work on this phone)
USB JIG (tested and working on my Hercules)
SD Card Partition (EXT4 and FAT32) because I suspect borked internal storage
SD Card Partition (ReiserFS and FAT32) Still nothing......... then I realized the phone probably wasnt rooted
3 button combos ( every single combination) nada
plugging in USB cable while holding volume up and down...
ADB Reboot recovery/download ( not recognized because I cant turn on debugging)
ETC ETC ETC........
I have been searching google for hours for some kind of clue as to what can be done other than JTAG repair and All I come up with (no matter what site im on) is " Use a USB JIG" duhhhh Its getting rather annoying.
Im no stranger to flashing ( no expert) but this one has me stumped. I was considering buying a RIFFbox anyways but I thought maybe some experienced users out there might be able to suggest something.
My hope is that something can be done with the J and K drive that was mentioned. Perhaps I can format and somehow push a rom straight to the internal storage without any assistance from the phone itself...... I know..... wishful thinking. or perhaps boot straight from external SD???? That would be interesting!
More to this.... I realize this question has probably been asked a million times because it seems to be a common issue on this phone but I suppose my long winded question really boils down to my last paragraph which I havent seen suggested yet.
EDIT: I have a Windows 7 AND kubuntu 12.04 dual boot if any suggestions require linux
Any help would be greatly appriciated.
kibosh1981 said:
Any help would be greatly appriciated.
Click to expand...
Click to collapse
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
xsenman said:
My Android Solutions should get you started but FIRST ensure your battery is no malfunctioning and Battery contacts are good and not loose.
Click to expand...
Click to collapse
Thanks. i will have a look and experiment tomorrow.
I'll report back my progress
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
taz0697 said:
if it pops up when you plug it into the computer, check if it does in odin. if does in there too try to flash a stock rom. or better yet take this download and follow the read me intructions, except the dl mode part cause you said it doesnt work. try both with the phone on and off. no it isnt the bell version of the pom but it will work. you will problably want to root it then install galaxy s unlock tool from the market and use that to unlock the phone aswell.(cause it not the bell rom)
http://www.mediafire.com/download.php?34oxweahfpy53dj
Click to expand...
Click to collapse
As I mentioned.... no download mode, therefore.... No ODIN. Unless someone has some magical way to make it work otherwise. The computer knows its an I9000 at least. Kies says its in the wrong mode and I have no UI so debugging is out of the question.
Also: Xsenmen. I was unable to get any of the tools to connect. In one section you mention that AndroPlatina attempts to connect while booting? I was unable to get this to happen. I even tried the "heat trick" to no avail
Hello everyone,
I've done quite a lot of searching, and I can find almost no one else with the same issues.
Basically, when I plug in the phone via usb, the computer will not recognize the device. I have tried every mode (mass storage, kies, usb debug, etc). However, it will charge. I have tried several cables, including those I know transfer data. When I try to put it into mass storage mode, I do not get a notification on the notification bar telling me to mount the SD or USB storage. I'm not sure if this is a hardware & software issue, or just one of the two.
I work in IT, so I'm not new to repairing hardware or software. Just trying to find SOME leads. The guy who owned this before me didn't do a great job of putting the phone back together when he tried to repair the screen (has a greenish tint, thought it was a loose connection but it may just be defective or needs to be cleaned. Either way, not my concern as of right now).
If anyone has any suggestions, it would be greatly appreciated
PS I have tried SEVERAL drivers on SEVERAL computers, Win7, Win8, OSX Lion, Lubuntu 12.10
Also tried putting the phone in Download mode to see if Odin/heim-something or other would recognize it, no luck.
Wondering if the usb isn't fully connected to the port, and if I should take off the back housing, plug it in, and see if it works that way?
x0ne215 said:
Hello everyone,
I've done quite a lot of searching, and I can find almost no one else with the same issues.
Basically, when I plug in the phone via usb, the computer will not recognize the device. I have tried every mode (mass storage, kies, usb debug, etc). However, it will charge. I have tried several cables, including those I know transfer data. When I try to put it into mass storage mode, I do not get a notification on the notification bar telling me to mount the SD or USB storage. I'm not sure if this is a hardware & software issue, or just one of the two.
I work in IT, so I'm not new to repairing hardware or software. Just trying to find SOME leads. The guy who owned this before me didn't do a great job of putting the phone back together when he tried to repair the screen (has a greenish tint, thought it was a loose connection but it may just be defective or needs to be cleaned. Either way, not my concern as of right now).
If anyone has any suggestions, it would be greatly appreciated
PS I have tried SEVERAL drivers on SEVERAL computers, Win7, Win8, OSX Lion, Lubuntu 12.10
Also tried putting the phone in Download mode to see if Odin/heim-something or other would recognize it, no luck.
Wondering if the usb isn't fully connected to the port, and if I should take off the back housing, plug it in, and see if it works that way?
Click to expand...
Click to collapse
Other than charging, when you connect to a pc do you get a device malfunction message in windows? We know the +5v and ground work since it charges so if you get the malfunction message in windows its a short in the data pins. If there is no message, just charging and no reaction from the phone other than the charging indicator, I'd say there is no contact to one or both data pins. I'd look in the micro usb port to make sure the pins are straight (and there lol) and if it looks dirty, use a shot of crc electronic cleaner in the port (battery out and screen facing up).
Of coarse this is if it isn't software related which it very well could be, but sounds more hardware related to me....
rmntruexjr said:
Other than charging, when you connect to a pc do you get a device malfunction message in windows? We know the +5v and ground work since it charges so if you get the malfunction message in windows its a short in the data pins. If there is no message, just charging and no reaction from the phone other than the charging indicator, I'd say there is no contact to one or both data pins. I'd look in the micro usb port to make sure the pins are straight (and there lol) and if it looks dirty, use a shot of crc electronic cleaner in the port (battery out and screen facing up).
Of coarse this is if it isn't software related which it very well could be, but sounds more hardware related to me....
Click to expand...
Click to collapse
Yep, that's exactly what pops up. I can't see very well right now (at work, have no magnifying glass here). I remember a long time ago having a couple bent data pins in my old BlackBerry Curve lol, ended up popping em back in. Hopefully, that will be the same case here.
I appreciate the quick reply, wasn't even thinking of that :fingers-crossed:
x0ne215 said:
Yep, that's exactly what pops up. I can't see very well right now (at work, have no magnifying glass here). I remember a long time ago having a couple bent data pins in my old BlackBerry Curve lol, ended up popping em back in. Hopefully, that will be the same case here.
I appreciate the quick reply, wasn't even thinking of that :fingers-crossed:
Click to expand...
Click to collapse
No problem:good: Good luck!!:fingers-crossed:
On a slightly-unrelated note, did some browsing and came up with this quick question.
Is there anyway to root the Captivate on 2.3.5 without PC connection? (I can send files to the phone via an external SD, just can't use Super One Click etc right now).
If not, couldn't I just flash back to 2.2 using recovery(stock, but as long as the update.zip signed correctly[will be stock firmware so I don't see why it wouldn't] it should work right?) and use z4root?
Well, to follow up:
I see no broken or misplaced pins, it all looks correct to me. I will try to upload a photo tonight.
In the meantime, I managed to brick (I think). Accidentally installed the wrong kernel from my SD (speedmod, which I forgot was for Froyo). Now I have CWM, but I cannot mount via usb still, and since I can't access the external sd from cwm, I'm stuck either in recovery mode or stuck at the Samsung screen.
Anyone have any ideas besides just setting it aside for a paper weight?
x0ne215 said:
Well, to follow up:
I see no broken or misplaced pins, it all looks correct to me. I will try to upload a photo tonight.
In the meantime, I managed to brick (I think). Accidentally installed the wrong kernel from my SD (speedmod, which I forgot was for Froyo). Now I have CWM, but I cannot mount via usb still, and since I can't access the external sd from cwm, I'm stuck either in recovery mode or stuck at the Samsung screen.
Anyone have any ideas besides just setting it aside for a paper weight?
Click to expand...
Click to collapse
Does that version of cwm have the option to flash from ext sd? Go to install zip in cwm and see if there is the option to flash zip from extsd. If so, then you should be all set putting the right kernel or rom on your ext sd and flash away. Not sure I'm the best person to answer your question, but I would start there I guess.
x0ne215 said:
Hello everyone,
I've done quite a lot of searching, and I can find almost no one else with the same issues.
Basically, when I plug in the phone via usb, the computer will not recognize the device. I have tried every mode (mass storage, kies, usb debug, etc). However, it will charge. I have tried several cables, including those I know transfer data. When I try to put it into mass storage mode, I do not get a notification on the notification bar telling me to mount the SD or USB storage. I'm not sure if this is a hardware & software issue, or just one of the two.
I work in IT, so I'm not new to repairing hardware or software. Just trying to find SOME leads. The guy who owned this before me didn't do a great job of putting the phone back together when he tried to repair the screen (has a greenish tint, thought it was a loose connection but it may just be defective or needs to be cleaned. Either way, not my concern as of right now).
If anyone has any suggestions, it would be greatly appreciated
PS I have tried SEVERAL drivers on SEVERAL computers, Win7, Win8, OSX Lion, Lubuntu 12.10
Also tried putting the phone in Download mode to see if Odin/heim-something or other would recognize it, no luck.
Wondering if the usb isn't fully connected to the port, and if I should take off the back housing, plug it in, and see if it works that way?
Click to expand...
Click to collapse
Just to verify, you have tried these particular usb drivers? http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897#USB_Drivers
x0ne215 said:
On a slightly-unrelated note, did some browsing and came up with this quick question.
Is there anyway to root the Captivate on 2.3.5 without PC connection? (I can send files to the phone via an external SD, just can't use Super One Click etc right now).
If not, couldn't I just flash back to 2.2 using recovery(stock, but as long as the update.zip signed correctly[will be stock firmware so I don't see why it wouldn't] it should work right?) and use z4root?
Click to expand...
Click to collapse
U can't get Root for a Captivate running Android 2.3.5 without a proper working micro usb port.
U can't flash back to Stock Froyo without a proper working micro usb port. (Unless u had Root already and then u could use Mobile Odin from the Play Store).
Only update.zip files signed by Samsung would work in the Stock 3e Recovery.
Stock Eclair had the 2e Recovery that did not require the signature verification.
Sounds like u need a new micro usb port.
Did u take a read at this thread...Captivate - PC Connection Issues...
If that thread is no help then it probably is a hardware issue. :/
Sent from my SAMSUNG-SGH-I747 using xda premium
4-2ndtwin said:
U can't get Root for a Captivate running Android 2.3.5 without a proper working micro usb port.
U can't flash back to Stock Froyo without a proper working micro usb port. (Unless u had Root already and then u could use Mobile Odin from the Play Store).
Only update.zip files signed by Samsung would work in the Stock 3e Recovery.
Stock Eclair had the 2e Recovery that did not require the signature verification.
Sounds like u need a new micro usb port.
Did u take a read at this thread...Captivate - PC Connection Issues...
If that thread is no help then it probably is a hardware issue. :/
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
1. Yes, actually you can. It's a temp root, but it works (how else would I have been able to flash the wrong kernel). I forget the apk I used, not on market anymore. I think it was like Mizu m9 or something, actually worked was kind of surprised.
2. Stock 3e is nbd now, I can boot into CWM 2.5.1.0 [which does have boot from ext-sd, but it either says it can't mount it or no files found. Not sure if its a version issue, if I could mount it and access the files on the ext-sd somehow this would all be solved and I'd love you guys <3
Yeah, I looked into the new USB port thing.I've tried every driver known to man lol. I think I'll end up getting the port repaired from that one website that was suggested, I think its $35 or so no big deal.
But can anyone confirm that CWM 2.5.1.0 can read an ext-sd? It's odd, because I assume on the captivate it gets mounted at /sdcard/external_sd, and when I look for a zip file to flash from the sd, I can see that folder, but trying to go into it just causes the message "no files found"
Gonna check this meizu m9 root method out.... hmmm...
Sent from my SAMSUNG-SGH-I747 using xda premium
Go for it, once installed it's pretty straight forward lol. But make you you dl the superuser app from the market (I did it before, just in case that matters). Mobile odin worked fine, adb wireless worked fine, etc.
But I just tried partitioning my SD card, and it still won't read in CWM. I tried mounting /sd-ext but every time I do it just says Error: can't mount
Yeah...i'm just curious as to how that root method works...since a method like that (gaining Root without having to use a connection to a pc) has never been done before with the Captivate since its release.
Sent from my SAMSUNG-SGH-I747 using xda premium
I'm not really sure, I didn't think it would work but it did...not sure what exploit it uses either. Did you try it? Wanted to check if it was just my phone or others too...
Sent from my Rooted PantechP8000 using xda app-developers app
Nope...haven't tried it, but am definately gonna check into it. I will post back if it works or not (if i decide its ok to try) when i can... :thumbup:
Sent from my SAMSUNG-SGH-I747 using xda premium
Gotcha, sounds good. Yeah not too sure if it's safe or not, was just trying anything.
On another note, what format does my SD card need to be in to be read by CWM Recovery? I had it set to exFat, Fat32, and ext2/fat32 and I still isn't being read or able to mount :\.
I was gonna say FAT32 full format as i have read that suggested by others, but looks like u tried that. The card may be bad...idk for sure though.
(Btw...would u mind attaching a copy of the meizu m9 root apk ? Thx.)
Sent from my SAMSUNG-SGH-I747 using xda premium
I may try fat32 again. Interesting though, I had a zip of another version of CWM on the INTERNAL SD which I CAN access.
When I install that (not really install it, just run it), I can mount sd-ext but not /sdcard/ lol...says it's busy...I'm starting to think this is a permissions issue more than anything.....
Sure, it's on my dropbox I can just download it quick and upload it here.
EDIT: idk what's with the extension on the file, should just put it on an sd card and install fine.
I have EXACTLY the same issue x0ne215, has you managed to resolve this issue? Or just replaced microusb?
TNK2005 said:
I have EXACTLY the same issue x0ne215, has you managed to resolve this issue? Or just replaced microusb?
Click to expand...
Click to collapse
The M9 root method did work afaik. That being said, it's not safe at all to flash with a broken USB port.
Sent from my SGH-I747 using xda app-developers app