Related
Yessss another dead captivate thread.
I think I'm gonna go die now.
I followed the video guide to install a custom ROM, in the development thread to the letter, and now my phone wont even turn on... (now that im thinking about it, I think I may have left the debugging mode OFF before I went to flash back to stock, maybe thats why?)
I got into download mode, plugged the phone into odin3 JF6 one click, it started and at some point during the process it said "removed" even though I didnt touch anything, and then i got a weird msg saying my device is not recognized, keep in mind the drivers were installed properly, and I had everything double checked before i flashed....
wtf do I do now? Cant boot at all or go back into download mode. this is my third galaxy, got it two days ago ffs.
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
bobbylx said:
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
Click to expand...
Click to collapse
I'm not sure if I was looking at the right place, but I think its 10.12. I'll do a search and see what comes up, thanks for your help.
JayPhill89 said:
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'll try that, thanks.
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
G.Hook said:
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
Click to expand...
Click to collapse
I've tried every possible key combination out there and nothing works. I think my best bet is a Jig, unfortunately the source didnt have any transistors in stock so im SOL for now.
Use JIG ... It will be your last help.
Use it as a paper weight.
If you look up samsung captivate jig on ebay you will find some pre built. I bought one not long ago just to have and it works just fine.
I hope this helps. Best of luck to you.
Sent from my GT-I9000 using XDA App
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Check out this link for a jig. And there is a video to show you how to build one. Or mobiletechvideo guy sells them for 17 bucks.
http://forum.xda-developers.com/showthread.php?t=889128&highlight=usb+jig
Sent from my SGH-I897 using XDA App
newter55 said:
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Click to expand...
Click to collapse
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
rsnt said:
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
My first captivate went fubar within my 30 days and I damaged the nv_data.bin on my second captivate and was stuck with the test IMEI. Samsung fixed my second one for free. Now I'm at the point where I'm totally sure about what precautions I need to take to keep me out of trouble but I'm not sure if I want to risk it again, heh.
The cheap jig does work. It helped me when I accidentally unplugged my phone during an odin flash.
Yes, you make a good point. You will find that most of the guides are written by people like myself who have an early revision or a phone from the initial release. For most of us, from what I've read and experienced, our phones are really hard to brick, ie, button recovery always works, odin one-click works, etc.
I honestly don't know all the differences now between revs. The first hiccup was the phones missing button recovery/download, and now it seems that people are having issues using the Odin One-click that we have been using for months.
I would recommend with your next phone check the rev or manufacture date, then search the forums for people with similar or same revs that have been successful at flashing and find out what they did.
good luck
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
newter55 said:
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
Click to expand...
Click to collapse
I agree with you completely. I tend to take it for granted that button recovery works for me and that good old odin one-click does too. It seems we need to start collecting data and making new guides.
Something like,
If you have rev, 1006, 1007,1008 go here,
If you have rev 1009 to 1012 go here,
etc.
latest update,
Two cables, and six resistors later, my phone won't go into download mode, lol, I'm not even sure I did things right, I'm gonna try stripping the same cable, used in one of those videos on how to make a jig, I still have three extra resistors.
I'm starting to think its because of it being with rogers. im gonna search the forums.
A micro usb breakout board is the simplest method for constructing a jig.
Wow, I guess I'm lucky that the used Captivate I picked up for my gf is an older one at 1007. Root procedure for her went without a hitch.
From stock rom, all set up and in daily use, WITHOUT ROOTING first.
Put clockwork update.zip on her sdcard.
Reboot into recovery.
Reinstall packages twice to get into clockwork recovery.
Wipe data/factory reset.
Flash Cognition.
Profit.
She's been using it this way for two weeks and loves it so much more than stock.
What was so complicated about the procedure you followed? Or was it the same as this but it just didn't work?
rsnt said:
...and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
I think you may have a good point. Eventually your carrier will stop replacing bricks for you. If you still have the inclination to play with flashing, investing in a jig would definately be a wise investment and if I were in your shoes, I wouldn't flash anything without one. I made a jig for myself before I ever flashed anything but luckily I have never had to use it, probably because I took the time (about a month and a half of trolling around here reading.) to research what all was involved with what I was about to jump into. Just something to consider in case you want to try again. Good luck!
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
JavaMac said:
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
Click to expand...
Click to collapse
Welcome!
Now first you must get your tools (Android SDK, Odin3) and study them a bit before flashing anything. Nothing is safe but if it's done properly your chance of bricking your phone are close to none.
Look in the Dev and Q&A for sticky post regarding flashing roms and how to start.
I would recommend you stay away from Gingerbread roms (2.3) for the moment. It requires to flash a new bootloader and you need a good understanding of how to flash and how to use Odin3 options before you venture there.
For your first flash i would recommend flashing Firefly rom but your free to select the one you prefer. Always read the first post of the rom to learn what it offers and don't.
Happy flashing
JavaMac said:
Hey folks. I`m new to Android, but I am well versed in how to manipulate Linux systems and I've got a new SGH-i896 that Ive been itching to tear apart.
I've never touched a phone in regards to hacking, and I know there's a lot of system stuff that can be screwed up while tweaking. What I'd like to do is explore these custom ROMs and see which is best for my specific phone.
If anyone could talk me through a good first option for trying out, it would be great. I see so many options, but I'm not seeing a popular choice, or a safe "for-dummies" ROM. Thanks for any help.
Click to expand...
Click to collapse
What he said^^^
I would start out reading a lot. Start here and here. Use this program to get started. This will allow you to flash FROYO. You can now flash FROYO custom ROMs.To flash Gingerbread go here read post 1 to get directions after flashing Stock FROYO. Once you have the GB bootloaders installed you should be able to flash custom GB ROMs. I stress read a lot before flashing. You can brick your phone easily if you don't. Good luck and welcome to the world of ROM flashing!
silvertag said:
Welcome!
For your first flash i would recommend flashing Firefly rom but your free to select the one you prefer. Always read the first post of the rom to learn what it offers and don't.
Happy flashing
Click to expand...
Click to collapse
I'll second firefly, very nice smooth rom, i used it for over 2 months.
I already had the Android SDK, as well as SuperOneClick. I went ahead and downloaded Odin3, and the Captivate Toolbox and the other linked tools. Thanks for the links by the way. I've also already taken a look at how to flash a custom ROM. I'm going to read a bit more and settle on a choice by tonight.
Thanks for all the help.
Having a bit of trouble on my first go
Hey folks. I went over the reading material that was provided and I went ahead with this guide
[link]http://forum.xda-developers.com/showthread.php?t=884364[/link]
I got through to the point where I had to use Odin. When I clicked start on Odin, it ran through the predicted cycles and claimed to be successful. My device won't mount now though. I can't see it in my computer anywhere, and I'm not sure how to continue.
Any thoughts would be appreciated. Thanks.
You were on stock 2.1 or 2.2 ?
What rom did you flash ?
What files did you put in Odin and with what boxes checked ?
Is the phone booting normally ?
What part does not mount ? (It's not detected by windows but charges when you plug in the usb cable ?)
Settings>applications>usb settings. Make sure thats set to mass storage.
stock has that checked to kies by default.
Let me clarify:
My phone is currently only sitting at the battery screen, with an empty battery image and a spinner.
I can bring up an AT&T splash screen that says "World Phone" below it if I follow the instructions to recovery mode, but it still does nothing.
I'm afraid I've bricked the phone, and I'm missing some clue as to why.
if something comes up on the screen it is not bricked.....i hate that word
you are not bricked. any sign of life at all means not bricked.
what odin did you use? im guessing odin one click, which means you have a newer build phone and it bootloops when odin one click is used.
get into download at this point you may need a jig, once in download mode use this package and you will be ok (you are canadian right?)http://forum.xda-developers.com/showthread.php?t=979133
Thanks for the tip pirateghost.
Hmm, I might be offended a little.
You thank the guy who pops in just to correct your jargon and not the guy giving you a link to help you?
studacris said:
Hmm, I might be offended a little.
You thank the guy who pops in just to correct your jargon and not the guy giving you a link to help you?
Click to expand...
Click to collapse
LOL
damn, studa, tryin to drag me into the dirt
I'm wondering if there's a way to do this without a jig. I don't really want to get that involved if I don't have to.
If I do have to, I will, but let's try to keep this in the software department if we can.
Thanks to everyone who's been helping out here.
Lol I was only joking
no harm done
there are a couple button combos to try if those don't work a jig is needed, but it's a very cheap and easy process to make one not "involved" at all or under 10 us dollars if you were to buy one.
Alright button combos to try:
Both volumes held plug in usb cable.
Cable in, pull the battery, hold the volume buttons while reinserting the battery.
JavaMac said:
I'm wondering if there's a way to do this without a jig. I don't really want to get that involved if I don't have to.
If I do have to, I will, but let's try to keep this in the software department if we can.
Thanks to everyone who's been helping out here.
Click to expand...
Click to collapse
-Remove the battery
-Remove the sim card
-Remove any external sd-card
-Pop battery in
-Hold BOTH volume buttons (on the left) and plug usb cable.
Are you back in download mode ?
Okay, I tried all the button combos, and it did nothing different.
I've only got the one micro usb right now. I guess that means I've got to go out and get another, along with some resistors?
This sucks. I guess I should have remained happy with the Android Rogers gave me.
If you insulate the resistors well enough you don't need to chop up the cable... You can touch the leads of the resistor loop thing you made directly to pins 4 and 5 on the phones usb port. Granted that way takes ALOT more fiddling with to work, but you don't have to hack a cable.
studacris said:
If you insulate the resistors well enough you don't need to chop up the cable... You can touch the leads of the resistor loop thing you made directly to pins 4 and 5 on the phones usb port. Granted that way takes ALOT more fiddling with to work, but you don't have to hack a cable.
Click to expand...
Click to collapse
So if I get the proper resistors, protect my thumb and finger, and apply them carefully to pins four and five on the phone's connection, it works the same way?
Actually, not my phone but a friend's. I was trying to restore it to stock with Odin in order to flash Cyanogen, however Odin was being a real PITA. Through numerous attempts, Odin would refuse to finish the restoration process, often hanging at sbl.bin or Setting PIT file. I tried at least ten times to get it to flash correctly. The final time I decided to let it sit overnight and flash, just in case. When I got up this morning though, it was still hung up. I unplugged the phone and pulled the battery like I had done multiple times the night before, so that I coould give it one last try before I went to work. But this time, the phone wouldn't go into download mode. I had been using the USB and 3 button combo method, but nothing this time. The phone shows no signs of life at this point, and I really don't have anything short of a JTAG left to try on it. Now I have to buy my friend a new phone.
Has anyone else experienced this kind of terrible performance from ODIN? And is there anything other than JTAG I can try. If there is someone out there that can fix it with JTAG, I would also pay money for that. I don't have the soldering skills necessary to fix this thing.
They sell the pre made jigs you can buy, just search for it and you will find plenty
Sent from my SGH-I897 using XDA App
The battery doesn't charge in download mode, the battery could very well just be dead. Pull the battery, reinsert it and plug in the phone to charge it, if all it does is get really hot and never shows any sign of life that is a brick. Check your PM.
super coffee said:
Through numerous attempts, Odin would refuse to finish the restoration process, often hanging at sbl.bin or Setting PIT file. I tried at least ten times to get it to flash correctly.
Click to expand...
Click to collapse
Can't really blame anyone but yourself for that one.. If it hung at sbl.bin and you managed to not brick it, you dodged a bullet.
Anyway, sounds like you dodged several bullets and then the inevitable happened. A jig won't help, and you're correct in your assumption that JTAG is your only way out. Fortunately for you, one of our fellow captivaters is still offering (at least to my knowledge) a free JTAG service. You should contact him to see if he'd be willing to restore your device, his name is connexion2005.
For future reference, don't flash back to stock unless you really need to. And when you do, don't flash an image that includes bootloaders. If you have bootloaders that work (3 button combo enabled on 2.2- bootloaders or 2.3 bootloaders), use a non one-click odin with an image that doesn't include sbl.bin or boot.bin; otherwise you're just taking unnecessary risks.
little8020 said:
They sell the pre made jigs you can buy, just search for it and you will find plenty
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I got one off eBay for 10 bucks. Probably the best investment I've made as I have encountered about every brick situation you could imagine.
This may sound stupid, but maybe trying to flash GB bootloaders with ODIN(not one-click) could work? Exhausting all options before sending your phone in or having somebody JTAG would be preferable.
+1...they are well worth the money if you do any ROM flashing!
I have same problems before. 3 button combo method didn't work at all. No JTAG at that time.
When you plug your phone to computer, make sure it still can detect "SAMSUNG Android USB composite Device", but not "Unknown devices".
Even I wasn't on download mode or recovery mode, the odin able detect my phone as COM port then I was using Odin3 v1.8. then I put "galaxys-bootloader-JVB.tar.md5" to bootloader since I already have 2.3.3 rom before.
Another "dad, my friend has this problem" thread!?
For future reference, use Heimdall and read instructions thoroughly and multiple times. I just started using Heimdall when I made my move to flash gingerbread again when the KF1 ROM came out and I love it. Regardless how well a program works though, it's only as good as the person operating it. There are TONS of people here far more educated than me when it comes to flashing anything, but I have never bricked, or soft bricked even (yet) and I flash a decent amount.
If all else fails, I did have good luck with Josh @ mobiletechvideos (haven't posted enough times to be allowed to post the link, but he's on youtube. He's also here as connexion2005) he was able to unbrick my phone for $50. The post office does not seem to like to deliver mail from him to me, but I'm typing this on the phone he unbricked.
Sent from my GT-I9000 using XDA App
Josh @ mobiletechvideos rocks!
He unbricked my Captivate!
There is not a problem with odin! Why do people always say don't use odin because it will brick your phone. You have to use it correctly. Make sure before you even open odin that the computer recognizes your phone and you have all of the correct drivers, etc. installed BEFORE even messing with odin. Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
megatronisabeast said:
Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
Click to expand...
Click to collapse
Your hard drive has usb ports?
You mean motherboard?
cappysw10 said:
Your hard drive has usb ports?
You mean motherboard?
Click to expand...
Click to collapse
Yes, the motherboard! Was in the middle of a tech class when I posted that! Guess I can't multi task! Thanks!
Thanks for the feedback guys. I'm here when you need the impossible done to your Captivate...
megatronisabeast said:
There is not a problem with odin! Why do people always say don't use odin because it will brick your phone. You have to use it correctly. Make sure before you even open odin that the computer recognizes your phone and you have all of the correct drivers, etc. installed BEFORE even messing with odin. Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
Click to expand...
Click to collapse
I've had odin fail a few times in a row on me when flashing gb bootloaders for i897. I had odin flashed countless times on multiple devices and computers. I'm pretty sure Odin isn't foolproof. Not everything can be contributed to pebcak, although the vary majority of problems posted on xda are...
kimchi0400 said:
I've had odin fail a few times in a row on me when flashing gb bootloaders for i897. I had odin flashed countless times on multiple devices and computers. I'm pretty sure Odin isn't foolproof. Not everything can be contributed to pebcak, although the vary majority of problems posted on xda are...
Click to expand...
Click to collapse
everytime odin has 'failed' for me, it's been a user error on my part. you need to follow the steps sequentially otherwise you have a higher probability of failure/brickage.
rmal0 said:
everytime odin has 'failed' for me, it's been a user error on my part. you need to follow the steps sequentially otherwise you have a higher probability of failure/brickage.
Click to expand...
Click to collapse
I honestly think that a lot of information here on XDA is only partial and this will get some into trouble. I know people say "search for it, it's here" and it is but the problem is that 10% of the time the information that someone is looking for is buried in a thread and the other 90% the search results list the same question being asked and answered with "it's here search" or "Did you search??"
There honestly should be posting guidelines, for everyone, I mean people take all the time to write disclaimers why not proper directions? Is there a standard Template? If I'm missing it please feel free to point it out.
For example:
This is a 9000/897/896 based ROM
This ROM needs the following bootloaders: ....
This ROM contains Bootloaders: Yes/No
This ROM will change your product code: Yes/No
This ROM requires a Davlik wipe to work: Yes/No
This Kernel is 9000/897/896 based
blah blah blah.......
If the information is readily and easily available then the amount of "dumb" question should go down dramatically and then there will be a "standard"
But then again it's Android/Linux, being fragmented is half the fun..
</rant>Just needed to vent...
Yes, I have read other threads prior to posting this. My Samsung infuse WILL NOT connect to my PC to attempt to use GTG's unbrick to revert back to stock. I have tried the following:
1. Multiple USB cables
2. Install Kies
3. Install Kies Mini
4. Uninstall both versions of Kies
5. Install just sole Infuse drivers
6. Attempted multiple computers (2 Windows 64-bit machines, 1 Windows XP SP3)
7. Attempted to use in VMWARE
8. Performed factory reset
9. Used USBdeview to delete any association of the device with the computer
10. Select mass storage mode when prompted to connect to the PC. Also set it to automatically select this setting.
I have tried everything I can find on this form and on the internet, still no luck. My phone makes the noise that it is going to connect and does nothing. Doesn't show that the device is installing, doesn't ever show up under my computer, just sits there. When I pick mass storage on the ROM it goes back to the main screen. I am running GTG's infused ROM, attempting to take back to stock. I have tried Heimdall, I have tried GTG's back to stock methods, phone NEVER is picked up by the computer even in download mode. To say the least, I have tried this OVER AND OVER on multiple machines, within the past week, and I would like to just go out and run my infuse over with my car at this point. I do not believe I will ever be buying a Samsung device again. Can someone please help me before I go insane? Any recommendations would be greatly appreciate on attempting to get this POS to connect to the computer. I am on Windows 7 64-bit edition.
Since you are attempting to unbrick... Have you tried to do a factory reset from the ROM settings?
Just my 2¢
http://forum.xda-developers.com/forumdisplay.php?f=1237
omnimanx1 said:
Since you are attempting to unbrick... Have you tried to do a factory reset from the ROM settings?
Just my 2¢
Click to expand...
Click to collapse
Several times. I have also tried reflashing the ROM through CWM as well.
drivel2787 said:
Several times. I have also tried reflashing the ROM through CWM as well.
Click to expand...
Click to collapse
1. You might have a bad usb data CORD or one meant only for charging, not DATA. Edit..nvm..saw the first line.
2. Your phone's UBS port may be bad.
3. Are you able to connect via kies air?
Thank you for doing your research. The only thing that I can see that you're missing is that you didn't say you ran the program with admin access. And comon Cheezy.. be nice. This guy knows his stuff man..
Erik_T said:
Thank you for doing your research. The only thing that I can see that you're missing is that you didn't say you ran the program with admin access. And comon Cheezy.. be nice. This guy knows his stuff man..
Click to expand...
Click to collapse
Apologize for not posting, I ran Odin as Administrator, even tried XP Compatibility mode on both Windows 7 64-bit boxes. I installed Ubuntu, but doesn't appear that GTG's Back to stock is compatible with Wine, so couldn't resort to that option. I didn't recall if I had tried installing Kies mini with administrative rights or XP compatibility mode so I'm trying that now. Will report back. I'm thinking I could have a bad data cable that's just used for charging. Thing is, it worked when I originally rooted the phone from Stock, so I was wondering if it had something to do with the firmware for GTG's infused and Windows 7 64-bit. But, I see plenty of people able to get Odin to work on his build, so doesn't make sense to me. I did flash back to GTG's Infused 2.2.1, seems to have fixed some of the issues I was having with 2.2.3 (random freezing of the phone, system volume freezing and crashing when opening through Settings menu), random WIFI turning on/off. That seems to be all good now. Just wanted to figure this issue out.
No luck... But, Kies Air does work. Still doesn't fix the fact that I can't connect via USB to store back to factory. But, I think that both USB cables I have may be bad for data connection. They are the ones that came with the phone, and BOTH cables attempt to just charge the phone and not attempt to mount the external storage in Windows 7 64-bit. Debating whether or not I want to order another cable, thinking about upgrading devices since I'm eligible at this time. Any recommendations on a good upgrade from the Infuse??
drivel2787 said:
No luck... But, Kies Air does work. Still doesn't fix the fact that I can't connect via USB to store back to factory. But, I think that both USB cables I have may be bad for data connection. They are the ones that came with the phone, and BOTH cables attempt to just charge the phone and not attempt to mount the external storage in Windows 7 64-bit. Debating whether or not I want to order another cable, thinking about upgrading devices since I'm eligible at this time. Any recommendations on a good upgrade from the Infuse??
Click to expand...
Click to collapse
If you're looking for a data cable, i got 2 off Ebay for $1 each. They worked. Search for mini usb DATA cable.
I've seen them go bad midcharge. If you had it plugged in, wiggle it, push slightly in each different direction gently. sew if you can get a brief response.
Re: new phone, galaxy note seems to be the hot device.
Sgs2 seems to be the fav by devs
I know you've said you've tried different cables, I had the same problem and it did turn out to be a cable issue. I tried 3 different types, and I ended up having to use one that I got directly from the local AT&T corporate store.
drivel2787 said:
No luck... But, Kies Air does work. Still doesn't fix the fact that I can't connect via USB to store back to factory. But, I think that both USB cables I have may be bad for data connection. They are the ones that came with the phone, and BOTH cables attempt to just charge the phone and not attempt to mount the external storage in Windows 7 64-bit. Debating whether or not I want to order another cable, thinking about upgrading devices since I'm eligible at this time. Any recommendations on a good upgrade from the Infuse??
Click to expand...
Click to collapse
If you have an old Blackberry USB it will work. I use one for my Infuse . Or maybe a friend of yours has one you can try before you decide to buy one...
Just my 2¢
Thanks guys, will definitely give that a shot and buy a new cable. I'm pretty sure that's gotta be what the issue is. I wouldn't think that 3 different computers are bad with two different OS's. I will probably get one here in a few days. I plan on upgrading the device here soon. I bought it out of pocket retail about six or so months ago so I didn't have to renew my contract. I'm waiting to see what they release at the end of next month's conference before upgrading. Probably give a quad core a shot to see how they are
Well, new USB cable NOPE, Still no connection to the phone via USB.
Did you try the ports on the back of the comp?
Sent from my SAMSUNG-SGH-I997 using xda premium
Try PUtting the phone in MTP mode
drivel2787 said:
Well, new USB cable NOPE, Still no connection to the phone via USB.
Click to expand...
Click to collapse
Drivel,
While you are plugged in, try pushing the connection around a bit. See if there is any recognition. If there isn't, i think you may have a hardware issue.
If it was a hardware issue, the trick it's to get att to honor their warranty.
if you're running infused, the trick is how to get out back to stock or to brick it
The closet thing i can think of is to download download dman uckl2 rooted package via kies air or by phone. Dl the stock kernal. Flash the ROM, disable lagfix, then flash the stock kernel.
That's as close to stock as I can think off for you to take to the att store and have them check the usb hardware port
edti: no prob GoSooner.
thanks qkster^ Thanks button failed on me
Take this with a little tolerance from a noob.
I am trying to get my G friends In fuse to upgrade and can't get past the unregistered device.
Shes uses it for prime business and is going out for 2 days so I can't wipe the internal till she gets back but I'm up to the last 2 steps. After pulling the sd card it wanted to but still hung. Will wait till she gets back to wipe the memory clean.
Following long trails of solutions it looks to me for some steps for you to try.
Do a search on your comp and find all kies. Remove all.
Pull usb from comp and phone.
Hard reboot of phone,reboot comp.
Reload Kies mini
Open above, file drop down,load drivers.
plug in usb to comp.
phone usb to kies.
plug in usb. Go/no go?
No go pull phone sd card. Repeat all above. Go/no go.
No go? wipe internal memory.
Repeat /Go/nogo.
No go /Sledge Hammer cure.
Pu
Appreciate the help guys. It's weird because when I first had the phone it worked for me to root the phone. I think I'll just stick to Kies air if I need to back up or anything. I don't feel like going through the trouble of flashing/exchanging and then re-rooting the new phone. I'll just deal with it. With the new USB cord I did trying a Windows 7 64-bit and Windows XP.
I do want to say that I appreciate everyone's help.
Had to remove the site address cause I'm a noob and this info wouldn't post. But the below is the issue for me.
[14] On February 3, 2012, the update went live on Kies Mini.
Samsung Infuses with "Kernel 2.6.32.9" blocks Kies Mini from being able to update to Android 2.3.6 "Gingerbread". An over the air patch should be released by 2/8/2012 to fix this issue.[citation needed]-
I have a Sprint Nexus S 4G that I've recently rendered without service or USB connection as a result of a fastboot accident. I'm currently running ICS 4.0.3 (Dooderbutt-aosp-v-5 build), but have tried restoring multiple backups on CM7 to no avail. Wiping all user data in CWM doesn't fix it either. I have also tried flashing the LC1 radio zip with no results.
The way I see it, my two best courses of action would either be to try and return to a stock ROM so that I can send the device in under warranty or to continue to try to fix it myself, which has been less than successful so far. Every process I have found online to return to stock seems to end in fastboot oem lock, which won't do anything for me as my phone doesn't show up in fastboot devices, file explorer, or seem to be recognized by my computer in either Ubuntu or Win 7. I've tried connecting on my friends' computers with the same results. I've also tried using another USB cable. No dice.
Sorry if I missed something obvious before posting. I tried to do a lot of research online and have reached the end of what I know what to do. Any suggestions?
Bump.
After some more researching, it appears that there is no way to lock the bootloader except through USB connection with a computer. Does this mean I'm out of luck? Any suggestions as to how to solve this issue? Since my first post, I've flashed ICS 4.0.4 with no improvement on the above symptoms. Also, auto-rotation doesn't seem to work. My Baseband version in About is listed as Unknown. Does anyone have any clue? Replies would be greatly appreciated.
have you updated the android drivers on your computer? you wont be able to connect to fastboot without the drivers. you can get it here http://www.junefabrics.com/android/ do the free download(on your computer) then follow the on screen instructions.
simms22 said:
have you updated the android drivers on your computer? you wont be able to connect to fastboot without the drivers. you can get it here ... do the free download(on your computer) then follow the on screen instructions.
Click to expand...
Click to collapse
I'm running Ubuntu, so from what I understand, I don't need any drivers. Prior to this fiasco, my computer recognized it as a storage device in the file system as well as a device in fastboot. It doesn't come up as either now.
I had a similar problem after I updated to ICS 4.0.3, what version of Ubuntu do you have, and does the device show up when you run lsusb?
Also, have you checked inside the usb connector to see if one of the pins is bent or damaged?
I'm running Ubuntu 11.10 and no, my Nexus doesn't show up in lsusb or anything else I seem to try. I have checked the pins in the connector of the phone and even bent them around a little bit, but I doubt that's the problem. Since it disappeared immediately after a bad flash, I'm fairly confident this is a software-induced error.
Ok, the only other thing I can think of is a bad kernel or baseband, but since you've tried several different roms, I don't think that's the problem (unless you put on one that's not for your model).
Sorry I can't be more helpful, hope you figure it out!
Thanks for your help anyway. To be clear, each rom has its own kernel and baseband, correct? Are those things I can flash independently of roms like the radio?
Found something, not sure if you've seen it already : http://forum.xda-developers.com/showthread.php?t=1077168
This bit is especially interesting :
"*If your having problems after the radio flash......go to dialer:
Type in *#*#72786#*#*, put your msl in, and let it re-provision"
For the usb not connecting, I had the same problem. After trying every computer in the house, I grabbed a can of compressed air for electronics and blew out my micro usb port on the phone itself. There was a small piece of lint in there that was causing the connection to not be made. It's worth a try.
statisticalanomaly said:
Found something, not sure if you've seen it already : http://forum.xda-developers.com/showthread.php?t=1077168
This bit is especially interesting :
"*If your having problems after the radio flash......go to dialer:
Type in *#*#72786#*#*, put your msl in, and let it re-provision"
Click to expand...
Click to collapse
I'm attempting to try this work around, but I can't seem to find my msl. I've tried putting in an incorrect code and checking alogcat for it as well as the terminal output of getprop. Neither of these give me the number. Sprint mentions using this code for resetting your phone in this tutorial, but I can't for the life of me find the part of their site that shows the msl.
This is exhausting. I really appreciate all your guys' help though. Thanks so much.
Unfortunately, I never figured out how to solve the problem. I took my phone into Sprint the other day and lucked out on the repair technician. He was messing around trying stuff and had a moment of realization when he booted into Clockworkmod. Even though I had voided my warranty, he still let me replace the phone for the $35 fee. I walked out with a brand new Photon 4G. I'm so happy, it's like Christmas in May!
To others who have this problem: sorry, but I don't know what to tell you! Mine was probably bricked. The MSL number didn't connect the phone and neither did anything else I tried. Best of luck to you.