Since yesterday my Galaxy S got stuck. It doesnt start anymore.
What happened?
I flashed my rom to the newest ICS. Everything went well and I used it a couple of days. Yesterdaymorning I did wiped the battery stats and cleared the Davik cache. I rebooted and it got stuck in the bootscreen.
I tried to got in recoverymodus but that was not possible. Bootscreen was all I saw.
Then I tried the downloadme. That is working BUT odin did not see my phone and KIES did also not recognize it. I have the right drivers. When my phone was working it was also not recognized because I am afraid the USB port is not good anymore.
Does anyone have tips?
wvawijk said:
Since yesterday my Galaxy S got stuck. It doesnt start anymore.
What happened?
I flashed my rom to the newest ICS. Everything went well and I used it a couple of days. Yesterdaymorning I did wiped the battery stats and cleared the Davik cache. I rebooted and it got stuck in the bootscreen.
I tried to got in recoverymodus but that was not possible. Bootscreen was all I saw.
Then I tried the downloadme. That is working BUT odin did not see my phone and KIES did also not recognize it. I have the right drivers. When my phone was working it was also not recognized because I am afraid the USB port is not good anymore.
Does anyone have tips?
Click to expand...
Click to collapse
can you go to recovery?
unfortunately not.
if i do the 3button trick the sreens stays on the bootscreen.
Change your drivers to the Nexus drivers in OP of TH ICS thread and try a different USB port.
Once in odin flash the initial CM7 kernel without reboot then go into recovery and reflash CM9.
installed nexusdrivers.
still nothing happens.
any other suggestions?
thx for the help!!!
Different USB port?
tried all 4 and another laptop
also used different cables.
almost start crying
-prereq-
install samsung drivers for your device and windows install type (x32/x64). It's quite important that you install 64 bit drivers on a 64 bit box and not 32, because they are ****ty and work 7/10 times used.
1. be sure to use the same port.
2. be sure to use ONLY the original cable that came with your phone
3. Make sure your phone is able to enter download mode. (Vol down+Home+Power)
if it does, it should install your drivers without issue about then.
4. If you can't use odin to restore your pda/csc/modem, then use heimdall. If that fails, you need to commandprompt heimdall into flashing with 512.pit + required files (refer for help to the heimdall readme included in their install) file after unpacking pda,modem,csc into the heimdall commandline exe.
If 4 does not work you need to unbrick it via 1clickbrick. It's a jar file you donwnload, dblclick and use.
thx for trying to help me. but I am afraid my USB port (mini) on my galaxy is not working. Tried 4 computers, several drivers but stil no connection possible.
Any other suggestions?
wvawijk said:
thx for trying to help me. but I am afraid my USB port (mini) on my galaxy is not working. Tried 4 computers, several drivers but stil no connection possible.
Any other suggestions?
Click to expand...
Click to collapse
Did you indtall usb drivers?
Sent from my GT-I9000 using XDA App
Try flashing the EZBase with Odin in Download Mode. Then report back
Sent from my GT-I9000 using Tapatalk
thx but the problem is : odin does not work.... it does not recognize my phone.... and I use the right drivers....
can it be because I work on isc rom?
When i was on ics (bootloop), ich have downloaded the Samsung USB drivers (exe.) and flashed via odin jvu...
Sent from my GT-I9000 using XDA App
@ aakaashjois
damn....it didn't work with the EZbase pitfile.....:-(
Unusual
wvawijk said:
@ aakaashjois
damn....it didn't work with the EZbase pitfile.....:-(
Click to expand...
Click to collapse
Are you sure? did your phone appear as 'added' after you out it in d/l mode? follow these steps...this is a sureshot method dude.
http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/
Good Luck!
any of the computers find it as new hardware?
amadeus_l said:
Are you sure? did your phone appear as 'added' after you out it in d/l mode? follow these steps...this is a sureshot method dude.
http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/
Good Luck!
Click to expand...
Click to collapse
No added unfortunately..... starting to give up.......
hackandmore said:
any of the computers find it as new hardware?
Click to expand...
Click to collapse
Nope..... I am afraid I lost my Galaxy...... :-(
Had the same problem on Windows machines - for some reason two of my Windows powered computers stopped recognizing my phone. Tried different drivers for no effect, so I gave up and tried it on linux and successfully flashed new kernel using heimdall.
I don't know if this is a legitimate solution because it's like going around the problem instead of solving it, but if everything else fails, try different operating systems.
try charging it..does it charge?
if it doesnt then go in a service and ask them to take a look at it.they will do that for a pack of cigarettes in their extra time.if its fixable and cheap(dont think of replacing the entire motherboard...sell this one for parts and buy another one, or find one with broken display and take em both to a service and tell them to replace the screen from your phone to the other)
Related
So heres the synopsis on what my issue is:
first of all-
phone: Samsung Captivate build 1010
current OS: (botched install of Darky 8)
problem: no recovery menu capability, stuck in reboot loop (will not go past ATT Logo), can go into download mode but odin does not see the phone
I botched a Darky 8 install. I attempted to install the rom to my captivate via rom manager but to no avail. I then decided to give the install a try via clockwork and had luck. the rom was not to my liking so I went to mount the internal sd and proceeded to delete all files internally to make a fresh odin install possible (as I always do). It was at the time of restarting my phone that I realized the rom I install was accidently the I9000 rom on my captivate, thus forth being a possible source of my issue. Currently I have a phone that is stuck in a reboot loop any time I plug it into a power source, or attempt to power it on. While in said loop the phone will not go past the ATT logo, and as it cycles, at the I9000 screen a robot voice pops up saying restore system. Ive attempted to reflash back to stock with the stock captivate odin3 OCD, but I am having no luck with the phone being recognized by odin (run as admin). I am currently running Mac OSX 10.6 with windows vista on Virtual Box 4.0, and have had luck previously with flashing the phone back to stock after I decided to try new versions of cognition. Currently my phone can only go into download mode and not recovery due to the boot loop. please help asap, this my only means of communication with my family on the other side of the states
Try multiple USB ports/different computers if possible. I had a similar issue after flashing an i9000 rom. I could get into recovery but the power button wouldn't work for selections and in download mode my computer wouldn't recognize it. I just kept at it and eventually it worked.
CB650 Wolf said:
Try multiple USB ports/different computers if possible. I had a similar issue after flashing an i9000 rom. I could get into recovery but the power button wouldn't work for selections and in download mode my computer wouldn't recognize it. I just kept at it and eventually it worked.
Click to expand...
Click to collapse
going to try, redoing my virtual box in hopes that it was something stupid, and also trying the other usb port on my macbook.
Have you tried using a different cable? I had the same issue with a bad flash and Odin would not pick up my phone. If it did, it would nit complete the flash back to stock. I switched cables and it worked fine.
Sent from my SGH-I897 using XDA App
butchatbg said:
Have you tried using a different cable? I had the same issue with a bad flash and Odin would not pick up my phone. If it did, it would nit complete the flash back to stock. I switched cables and it worked fine.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
cable is fine considering I am still able to bring up the gadget serial on my virtual box with the phone.
s0n1cm0nk3y said:
cable is fine considering I am still able to bring up the gadget serial on my virtual box with the phone.
Click to expand...
Click to collapse
Try using ADB..
Edit...misread
rickysa2000 said:
Try using ADB..
Click to expand...
Click to collapse
sadly I wished that work, I tried using adb reboot recovery, and in the attempt, the phone was not able to be detected. Should this be done in hopes to catch it at the right time in the boot loop or in download mode. Ive tried both.
So can you still get into Download mode? If so I would suggest finding another computer to use. For some reason, last week, my PC that I have been using to flash for months decided not to recognize my phone in download mode.
So I switched to my laptop, loaded the ROM. I tried reinstalling drivers and all kinds of stuff but nothing worked. I backed up my PC and re-imaged it and it's working again.
Another person on here had to go and manually remove all references to the USB Driver and re-install it.
I would say just try re-installing (with the phone in DL Mode) the USB drivers with the phone plugged in and see what happens then. Hopefully the OS will detect the phone and you should be golden.
And that mechanical voice is voodoo... need to be careful what folders your deleting even if you are going to flash ODIN.
avgjoegeek said:
Another person on here had to go and manually remove all references to the USB Driver and re-install it.
I would say just try re-installing (with the phone in DL Mode) the USB drivers with the phone plugged in and see what happens then. Hopefully the OS will detect the phone and you should be golden.
And that mechanical voice is voodoo... need to be careful what folders your deleting even if you are going to flash ODIN.
Click to expand...
Click to collapse
Odd I was told your perfectly fine to do so, and then from there do an odin flash. Ive done it before, but oddly enough I think what screwed me was because I did it during while in the rom, vs while in 2.1. I just wanted to try to get a clean slate. doing the master clear code from samsung never really deletes the left overs from say clockwork and such on my internal sd.
problem was the virtual machine, plugged it into a friends computer and all was done within a couple of mins. leave it to emulation falling short :/
ok to start with I am soft bricked cause i got the phone-!-computer on my screen. here is how it got bricked to start with... was updating to android 2.3 gingerbread with kies mini and the first time when finished updating my wifi would not work so i flashed the rom with odin and it was a bad version cause instantly it went to recovery mode. so I went and downloaded odin one click and flashed it back to stock android eclair and went to update to 2.2 froyo with kies mini our power blinked and now im softbricked.
ok here is what ive tried so far... 3 button combo both volumes and power tried all that. ok next i tried one click unbrick it just say failed everytime... tried AIO captivate toolbox and no avail.. went radio shack got 3 resistors 100k made a jig touched pins 4 and 5 and didnt work either.. so my questions are as follows
1. what next????
2. could i have possibly shorted out my usb port on my phone since i accidently slipped and touched a pin i should not have and AIO captivate toolbox says usb debugging isnt on.
3. is there any way to test the micro usb port on the phone to see if its working right?
any and all help would be very much appreciated.
thanks...
You're actually in an ok place. That phone--/!\--computer screen will function like download mode most times. Just try your Odin file again and you should be fine.
odin isnt recognizing it. is there a way i can make it recognize it?
I just went through this and got my phone working so no need to panic. Odin wouldnt see my phone but heimdall does. Search for the kb2 heimdall one click package and see if that helps. Since you flashed back to 2.2 youll need to use kb2. If you are on GB i897 bootloaders youll need the kk4 heimdall one click package
garydv2002 said:
odin isnt recognizing it. is there a way i can make it recognize it?
Click to expand...
Click to collapse
Try different ports, if nothing else. Look in the "Captivate Connection Issues" post in my signature for more items.
Also, you will probably want to stop using the AIO Toolbox. That particular piece of software is a little risky, as it flashes a known dangerous bootloader setup.
I found myself in the same boat. 3-button combo won't work, you have to remove battery and usb cable. Replace battery. Plug usb cable into the motherboard directly(rear), hold volume + and volume - then plug the usb cable into your phone. hold volume buttons until your phone boots into download mode. (assuming you have proper drivers installed)
didnt work
tried both heimdels kk2 and kk4 they both say looking for device. and also tried plugging my usb cord into every usb port on my computer still nothing.
Did your drivers unseat? for some odd reason i had to reinstall the drivers to get mine out of soft brick.
drivers
would that be the drivers for the program or the phone? and also on the kk2 and kk4 they download as jar files just like oneclick unbrick did so do i need to unzip them and move the jar file to where the exe folder is then right click and run as administrator or can i just run the jar file i downloaded?
also the the zadig driver program that comes with heindel programs will not see my phone at all when plugged in any usb port but my wife has a captivate also and when i plugged hers in zadig can see it as samsung usb composite device....
garydv2002 said:
odin isnt recognizing it. is there a way i can make it recognize it?
Click to expand...
Click to collapse
Pull battery, pull cable. With phone off, replace battery. Then press volume up only, and power. When screen loads, plug your USB in. If you get the system files screen, press the menu key. Then try Oden. This is what I had to do to get it to work.
Gingerbread through mini kies sucks. Your better off getting Gingerbread here:
http://forum.xda-developers.com/showthread.php?t=1300843
didnt work either
tried the just the volume up and power and plugged in usb still stuck in brick mode...
didnt work
the volume up and power then plug usb didnt work still in brick mode. should i try the usb jig with the phone off or on? when i touch pins 4 and 5 with the jig and the phone off the screen will come on but still computer- ! - phone no download mode
got it
finally got into download mode with the jig and alot of wiggling cussing fussing griping and finally praying lol.... thanks to all of you for your help not many strangers will help people anymore so thanks guys for your time i really appreciate it greatly
HELP
I have the Phone...!... computer screen ive done ever battery pull method oden cant "see" it but my computer says that a unidentifiable USB is plugged in. any advice?
cappy flasher said:
I have the Phone...!... computer screen ive done ever battery pull method oden cant "see" it but my computer says that a unidentifiable USB is plugged in. any advice?
Click to expand...
Click to collapse
Unistall your phone's drivers, restart pc and reinstall them.
Drivers
So i dont know what the drivers are I had a friend set this all up for me. also i think if odin id updated that might work. It was current at the time but when a few months pass its time to update!
---------- Post added at 03:53 AM ---------- Previous post was at 03:46 AM ----------
BWolf56 said:
Unistall your phone's drivers, restart pc and reinstall them.
Click to expand...
Click to collapse
so i just updated odin and i still got nothing. so what are the drivers? ill try that.
if you dont even know what drivers are in windows, and have other people set things up for you, you should not be flashing your phone in the first place.
any time you buy a device and hook it up to windows you install??? drivers.
Google: "drivers"... a piece of software that tells an operating system how to use a device.
but it is doubtful reinstalling your drivers will help
what version of odin are you using? what are you trying to flash now? what were you flashing when it messed up?
im sorry but this may end up being an expensive lesson not to do things you dont understand. you may have to send your phone away to be jtagged or unbricked.
I still have the phone...!...computer screen so i should be able to flash it back to stock. and even though i didn't add the drivers I know what im doing so don't assume Im a noob at this. and for your information I own 6 Samsung captivates and I work for Mobile Tech Videos so I flash these phone a lot I flash at least twice a day. so Jtaging it will be rather inexpensive but I would like to figure this out so I don't have to spend my time shipping this phone out. I notice that a lot of people have the same trouble as I am having so if I figure out how to solve the worst soft brick (witch I now have) it will be great for A post that covers everything with this screen. I got my phone this way by the USB port falling out during flashing so I'm lucky to even have this screen. I was at gingerbread 2.3.5 stock flashing to ice cream sandwich. I tryed using the USB jig but it failed so all I need to know is what the driver names are so i can try what was recommended. I also think ADB might help solve the problem some how some way. I just got the most recent Odin I was using 1.3 now im using 1.85
Not to be mean or start something, but if you work for mobile tech videos and you don't know what drivers are or you say you flash phones multiple times a day, then you should have a GREAT idea of what to do to fix this problem. Did you flash an ICS ROM and it bootlooped on the first flash, well that is supposed to happen. And Since you were on 2.3.5 then there is no DL mode combo problem. I don't know what to tell you. use your resources and Google it, or better yet let me Google that for you...
cappy flasher said:
I still have the phone...!...computer screen so i should be able to flash it back to stock. and even though i didn't add the drivers I know what im doing so don't assume Im a noob at this. and for your information I own 6 Samsung captivates and I work for Mobile Tech Videos so I flash these phone a lot I flash at least twice a day. so Jtaging it will be rather inexpensive but I would like to figure this out so I don't have to spend my time shipping this phone out. I notice that a lot of people have the same trouble as I am having so if I figure out how to solve the worst soft brick (witch I now have) it will be great for A post that covers everything with this screen. I got my phone this way by the USB port falling out during flashing so I'm lucky to even have this screen. I was at gingerbread 2.3.5 stock flashing to ice cream sandwich. I tryed using the USB jig but it failed so all I need to know is what the driver names are so i can try what was recommended. I also think ADB might help solve the problem some how some way. I just got the most recent Odin I was using 1.3 now im using 1.85
Click to expand...
Click to collapse
Heimdall flash!
Sent from my SAMSUNG-SGH-I897 using XDA
I have a Samsung Captivate which has been rooted and unlocked...it was running 2.3.5 uckk4
I believe I got a virus from downloading some app that was not on the market well long story short I tried to flash it back to a different version
I believe I put something in odin bootload that I wasnt suppose to it was an accident as you see I am a total noob at this then I use the 1 click unbrick now my phone keeps rebooting itself but i looked at the about phone which i get to for a few seconds before it reboots itself again and this is what it says
Firmware
2.3.3
Baseband
1879UCKF1
Kernel Version
1897UCKK414489
BUILD
gingerbreadUCKF1
I have tried a master reset since I could get it into debug just that it keeps looping and it worked in odin but not on my phone and this is what it generated
<?xml version="1.0" encoding="UTF-8" ?>
- <REFLASH>
- <UNIT>
<ESN>00000000000000 /0</ESN>
<TIMESTAMP>20120424002823</TIMESTAMP>
<RESULT>_20120424002823</RESULT>
<SOFTWARE_NAME>Downloader</SOFTWARE_NAME>
<SOFTWARE_VER>3.00</SOFTWARE_VER>
<OEM_NAME>SAMSUNG</OEM_NAME>
</UNIT>
</REFLASH>
PLEASE HELP ME....if you can get my phone operational again I WILL DONATE MONEY TO YOU!
I have tried EVERYTHING and searched FAR AND WIDE!!!! I almost forgot Odin does not display my device anymore...ie such as com4...I really have tried everything that's why I am willing to donate/ pay you if you can solve my problem....if odin recognizes my device then it gets stuck halfway through. As of today my computer recognizes my device but Odin does not!
I have read and tried everything here
http://forum.xda-developers.com/showthread.php?t=858765
and here
http://forum.xda-developers.com/showthread.php?t=731989
and alot of other things listed and not listed on this site
NEW IFO: now I'm stuck at ATT logo and can not get into download mode
This thread will selfdestruct in 5...4...3...2...1....
DANG IT wrong section? SORRY MODERATORS!!!! SORRY
Please dont delete please just move it please!!!!
oh goodness... No need for donation but all you need to do is download a stock package odin like kk4 which is the most recent. Flash in download mode. There a sticky at the top of the thread list with all the packages.
In the future post in the questions/help section.
diskjockee said:
DANG IT wrong section? SORRY MODERATORS!!!! SORRY
Click to expand...
Click to collapse
Ok I gave you the only warning in the PM. I have moved this thread. A word from the wise. Learn what you are doing before you do it. This is not something to be taken lightly. You could very easily mess something up beyond repair. Take a few hours to spend reading and researching.
ThisWasATriumph said:
oh goodness... No need for donation but all you need to do is download a stock package odin like kk4 which is the most recent. Flash in download mode. There a sticky at the top of the thread list with all the packages.
In the future post in the questions/help section.
Click to expand...
Click to collapse
I have tried that it doesnt work. thats was one of the 1st things I tried
try this
http://forum.xda-developers.com/showthread.php?t=1266172
Make sure you're using a usb port that is on the motherboard (back of computer). Before you plug in your phone to flash, set up Odin first. Put all the files you are going to flash in the right places. After Odin is fully set up, plug in the usb to the back of your computer, then to you phone. Make sure you are in download mode. If the usb still isn't working, try a different USB port that is on the back of the computer. Connecting the usb to the back of the pc is very important. Odin doesn't recognize my phone when it's plugged in the front, when the phone is in download mode. Only the back usb ports.
If Odin still doesn't recognize the phone, try a different USB cable. But do everything else the exact same way as I described.
Also make sure you fully setup Odin before you plug your phone in to the usb.
Sent from my Serendipity VII flashed Captivate using xda premium
Limitz Cash said:
Make sure you're using a usb port that is on the motherboard (back of computer). Before you plug in your phone to flash, set up Odin first. Put all the files you are going to flash in the right places. After Odin is fully set up, plug in the usb to the back of your computer, then to you phone. Make sure you are in download mode. If the usb still isn't working, try a different USB port that is on the back of the computer. Connecting the usb to the back of the pc is very important. Odin doesn't recognize my phone when it's plugged in the front, when the phone is in download mode. Only the back usb ports.
If Odin still doesn't recognize the phone, try a different USB cable. But do everything else the exact same way as I described.
Also make sure you fully setup Odin before you plug your phone in to the usb.
Sent from my Serendipity VII flashed Captivate using xda premium
Click to expand...
Click to collapse
I just tried that....it worked but now I'm stuck at the ATT logo
You probably have mismatch kernel and bootloader loader. Maybe you can try to wipe data / factory reset in recovery.
Sent from my Serendipity VII flashed Captivate using xda premium
If you continue to go into a bootloop then I recommend a USB jig for the galaxy s series. I had had that happen before, Nothing worked, couldnt get it into download mode, couldnt get into recovery, Until I got the USB jig, Fixed my problem right away, and I flashed back to stock. The USB jig is only 6 bucks on ebay. Ill link you if you are interested.
Limitz Cash said:
You probably have mismatch kernel and bootloader loader. Maybe you can try to wipe data / factory reset in recovery.
Sent from my Serendipity VII flashed Captivate using xda premium
Click to expand...
Click to collapse
I know you're trying to be helpful, but there is no such thing as a kernel/bootloader mismatch...
b-eock said:
I know you're trying to be helpful, but there is no such thing as a kernel/bootloader mismatch...
Click to expand...
Click to collapse
Are you sure? Becuz I tried to flash an overclock kernel on my rom, and kept getting a bootloop. Then after flashing a few different kernels, the kernel that came with my rom didn't even work. I had to go back to stock and reflash my rom.
Idk, maybe it was just me then. I apologize. thank you for correcting me, that's how we learn what's right, and what's wrong.
Sent from my Serendipity VII flashed Captivate using xda premium
noob advice
I'm a noob, so this comment might just serve to show how little I know, but whenever I find myself in a bootloop situation, I've noticed that the problem starts with the initial attempt of installing a rom via a kernel with an older version of CWM. During the post-install boot sequence, I'll see the AT&T splash screen, a CWM screen with script running, and then a reboot. Usually, accessing the CWM (now on a higher version) and reinstalling the rom will get it working. Not quite kernel / bootloader mismatch, but close.
whisky23 said:
I'm a noob, so this comment might just serve to show how little I know, but whenever I find myself in a bootloop situation, I've noticed that the problem starts with the initial attempt of installing a rom via a kernel with an older version of CWM. During the post-install boot sequence, I'll see the AT&T splash screen, a CWM screen with script running, and then a reboot. Usually, accessing the CWM (now on a higher version) and reinstalling the rom will get it working. Not quite kernel / bootloader mismatch, but close.
Click to expand...
Click to collapse
Ohh ok. That might have been my problem before. Thank you.
Sent from my Serendipity VII flashed Captivate using xda premium
Try this.
Buy a jig. Either off of Ebay or mobiletechvideos.com
That week get you into download mode.
Then find the HEIMDALL flasher for a build. (my favorite was the one click for saurom Kk4)
Install heimdall drivers, and flash. Boom. Functioning phone.
Im on ics rom right now and im stuck on it. My computer wont recognize my phone, i tried installing drivers and many other things but it just wont work... Can someone tell me what to do??? (i tried connecting to other computers but it doesnt work) If not can someone suggest custom rom that doesnt drain 1% of battery in 2 minutes.
xXcRazycRackeRXx said:
Im on ics rom right now and im stuck on it. My computer wont recognize my phone, i tried installing drivers and many other things but it just wont work... Can someone tell me what to do??? (i tried connecting to other computers but it doesnt work) If not can someone suggest custom rom that doesnt drain 1% of battery in 2 minutes.
Click to expand...
Click to collapse
Did you try a other computer? Sometimes the computer fails to identify you device, happend to me 1 time.
Or try Blazr rom, fast stable and very long battery life!
Just put the zip file on your sdcard and copy it to your phone (since your computer doesnt let you connect via usb)
Then go into recovery mode en update via zip file.
See this link for the rom: http://forum.xda-developers.com/showthread.php?t=1628639
Everything you need is posted there.
Greetings
CybertekDj said:
Did you try a other computer? Sometimes the computer fails to identify you device, happend to me 1 time.
Or try Blazr rom, fast stable and very long battery life!
Just put the zip file on your sdcard and copy it to your phone (since your computer doesnt let you connect via usb)
Then go into recovery mode en update via zip file.
See this link for the rom: http://forum.xda-developers.com/showthread.php?t=1628639
Everything you need is posted there.
Greetings
Click to expand...
Click to collapse
I tried it on friends computer.
And i need i9000 roms.
xXcRazycRackeRXx said:
I tried it on friends computer.
And i need i9000 roms.
Click to expand...
Click to collapse
Odin or Heimdall is the only way, but try flashing another ics Rom to see if it fixes the phone not being recognised
slaphead20 said:
Odin or Heimdall is the only way, but try flashing another ics Rom to see if it fixes the phone not being recognised
Click to expand...
Click to collapse
I tried almost every ics rom but it didnt work. I guess i will have to buy new usb cable and check if there is something wrong with the phone.
I had the same problem, I uninstalled the usb drivers and installed them again and it seemed too work fine
Sent from my potato using xda app-developers app
xXcRazycRackeRXx said:
I tried almost every ics rom but it didnt work. I guess i will have to buy new usb cable and check if there is something wrong with the phone.
Click to expand...
Click to collapse
yep, the cable is likely the common cause and problem but not all cables are compatible, best to get original or bring phone and test data mode before buying as charging mode works on all
on the other hand, just examine your usb slot too..a slight misalignment can also cause this problem
xsenman said:
yep, the cable is likely the common cause and problem but not all cables are compatible, best to get original or bring phone and test data mode before buying as charging mode works on all
on the other hand, just examine your usb slot too..a slight misalignment can also cause this problem
Click to expand...
Click to collapse
Will Sgs 2 cable work?
xXcRazycRackeRXx said:
Will Sgs 2 cable work?
Click to expand...
Click to collapse
give it a try, it should
I had Android 4.0.3 (IceCream Sandwich) on my Galaxy S GT-I9000B (I did install it through Odin, nothing went wrong), but is was laggish (too much for it to handle, I think) and after a few months, I decided to roll it back to 2.3.3 (Gingerbread).
I started the process to install the firmware through Odin3 v1.85 - the file I download (from sammobile.com/firmware, had only one file that I used on the PDA space.
Odin recognized my phone and I started to install it, but after a while my phone was stuck on the downloading screen (2 hours of installation, I tought that something went wrong).
I then turned my phone off to try and install again, but when I turned it on, there were a Phone - exclamation mark - Computer Symbol.
I can get it to dowlonad mode (Volume Down+Home+Power), but when I plug it to the pc, it says "unknown device" and it can't find drivers for it.
I think I have the latest drivers from Samsung (I had from Kies and I re-downloaded a file somewhere from this forum named SAMSUNG_USB_Driver_for_Mobile_Phones_1_5_6_0.exe).
It appears that since windows can't install the drivers, Odin doesn't recognize the device - it was recognizing it before, when I was installing the firmware.
Now I'm stuck - I tried anything I saw in this forum and in other places - I did even pray for a miracle, but it didn't work
I know that there must be a way, but I don't know how.
Before I forget, I'm using Windows 7 Ultimate x64.
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
KainFromNod said:
I know that there must be a way, but I don't know how. Before I forget, I'm using Windows 7 Ultimate x64.
Click to expand...
Click to collapse
Ok, k4Z3666, has given you a starting point...the phone is still in download mode but without a booting ROM, so its OK, the problem is your PC, USB cable or USB port. If you want to be quick about it, just try on a lap top..if not a simple Reboot of PC ( after removing power cord) and Phone (after a battery Pull), and a switch to a different USB port at the back of PC can solve this for some...for other solutions try these http://forum.xda-developers.com/showpost.php?p=27205737&postcount=4571 anything else you may need can be found on My Android collections., link below
k4Z3666 said:
If you can get it in download mode everything should be fine, I've had a problem like this, my pc couldn't see the phone in download no matter what. Try to use another USB port, better another PC. Also I've heard that x64 doesn't get along well with Odin. If possible you can try Linux and Heimdall, after all Android is Linux too.
Click to expand...
Click to collapse
I tried other USB Ports and also rebooting. It was working just fine - it seems like a driver problem to me.
My notebook is dead, but I'll try using someone else computer.
Does Odin runs in Windows XP? I might try it in my virtual box - I doubt that it will work, but it is the best thing I have to do untill tomorrow.
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
KainFromNod said:
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
KainFromNod said:
I got it working in my mother's notebook - should I try something different? I only have the PDA, should I try a PIT?
I don't know what those do, but I read somewhere that PIT is used to recover bricked phones.
EDIT: I installed only the PDA, it worked fine on the 2nd time (first time, it got stuck but I could make it work changing the usb port and cable).
Now it is on loop - it repeats the samsung logo over and over again. Any ideas now?
Click to expand...
Click to collapse
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Ok, I'm posting it here just to leave a reply and reference for future generations, as my problem was solved.
xsenman said:
what ROM did you use? Did you do any wipes?
Opps..you got an i900B, so make sure you are only using I9000B ROMS as i9000 is not compatible with your phone
I used a firmware from my country (available here: sammobile.com/firmware/?page=3&model=GT-I9000B&pcode=ZTO&os=1&type=1#firmware) and I wiped the cache (I'm not sure what this means, but I believe it is the 2 options on volume up+menu+power)
Follow guidelines from here
http://forum.xda-developers.com/showthread.php?t=919219
http://forum.xda-developers.com/showpost.php?p=22941192&postcount=300
Click to expand...
Click to collapse
k4Z3666 said:
Assuming that you're on the right rom for your phone can you enter recovery mode? Try reinserting battery, and enter recovery with [vol+, menu button, power on]
Click to expand...
Click to collapse
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
yahyoh said:
Yep if u want to back to stock u need pit file because ICS use different system file
Why u don't like ICS ? Its way better and faster than sammy ROM even its more stable , I think u should try it again with devil kernel with oc to 1.2 it will fly u can add some live oc which will give more fluidity
Sent from another galaxy powered by CM10 & Syiah
Click to expand...
Click to collapse
ICS wasn't faster here - it was laggish and always crashed some common apps (gallery, music player). I believe that the firmware wasn't completely "done" as it was being adapted from another version (my phone is brazilian) and some functionalities that it has (i.e. digital TV) wasn't available.
What I done to correct the boot was simple (I found a tutorial in a brazilian site, so it had all the roms that I needed).
1) Used a PIT and a stock rom to get it back to factory version;
2) Upgraded to Froyo (original) - That was kind of a mistake, the tutorial said to do it because then KIES would update it automatically to Gingerbread. The phone was fully functional, but KIES said that it couldn't update it (it recognized the phone and everything).
The tutorial stoped there, but since I had the ROM, I used Odin to install Gingerbread (the one that was looping) and it was done.
Now I need to remember how to root it because there are some dumb apps who can't get away (i.e. Orkut app, some demo games).
Thank you all for the help!
KainFromNod said:
I was entering recovery mode, but it was giving me some error when I tried to wipe the 2 things that I forgot the name =/
Click to expand...
Click to collapse
From recovery you can always try to flash another kernel, that would probably resolve things too. Anyways the problem's solved, glad to help