[Q] samsung captivate boot loops - Captivate Q&A, Help & Troubleshooting

i have a att samsung captivate sgh-i897 and i flashed kit kat on it. it was working fine until one day it booted up to recovery and i couldnt get the phone to boot up. so i decided to flash back to a stock of gingerbread (i used the odin3 to do this) and that was successful. the only thing was my internal and external sd are no longer being detected and when i needed to reboot the phone it would continuously boot loop. ive looked every where for solutions. i just wanted to get everything back to normal so i tried to flash a what i believed was stock 2.2 froyo to it through hiemdall (SamsungCaptivate-SGHi897-UCKB2-NoRoot-One-Click) because i read it was the safest way to flash. after doing so i either get a black screen after boot or in boot loop and i can still get into download mode but when i try to run odin it wont detect the phone at all. can anyone help me get everything back to stock and get my phone usable again and possibly get my external sd card working again?
p.s. ive tried to wipe the cache and factory reset wipe too.

^
Go here... Stock I897UCKK4 Android 2.3.5 One Clicks *Heimdall and Odin*
If u want to use the Heimdall version that I linked, then use the same USB port that u used to flash the other heimdall one click that u mentioned.
If u want to use the Odin version, then use a different USB port, Because the heimdall usb drivers are installed only to the one specific usb port that u r using at the time of the install. That is more than likely why the computer is not recognizing ur phone when u r trying to use odin.
Here is another thread that may help as well... Captivate - PC Connection Issues, Download Mode and Recovery Mode Help

Sounds like failing internal memory to me.

ok
4-2ndtwin said:
^
Go here... Stock I897UCKK4 Android 2.3.5 One Clicks *Heimdall and Odin*
If u want to use the Heimdall version that I linked, then use the same USB port that u used to flash the other heimdall one click that u mentioned.
If u want to use the Odin version, then use a different USB port, Because the heimdall usb drivers are installed only to the one specific usb port that u r using at the time of the install. That is more than likely why the computer is not recognizing ur phone when u r trying to use odin.
Here is another thread that may help as well... Captivate - PC Connection Issues, Download Mode and Recovery Mode Help
Click to expand...
Click to collapse
i downloaded the heimdall with no bootloaders and no difference. im still getting boot loops. should i try it with bootloaders and see that works?

Val D. said:
Sounds like failing internal memory to me.
Click to expand...
Click to collapse
is there anything i can do to boot it up if thats the case?

I'm not 100% sure this is the case, but failed internal memory issue happens to Captivate phones and the symptoms are same to what you describe. The phone can't read part of the memory and reboots constantly no matter what ROM you attempt to flash. Search the forum for internal/external swap methods. I never had to deal with this issue and have no experience with workarounds.

Related

[Q] Captivate Soft Brick - Need a rooted Odin solution.

Hi
My brother (a no-geek) has a captivate, and lives in a different city (I donot have physical access to the phone). He visited me few weeks ago and I installed CM-7 on his phone, i know my bad. Some of his videos were not working, so i asked him to update to the latest CM-7 build. He download the build, saved it on int sd_card and used ClockWork Recovery to install the selected ROM. Upon reboot it entered in never-ending splash screen. I found couple of odin ROMs, and posted him link, we tried to flash them, but no good.
Status --
The COM ports are detected, but the process at times halts at <SET PARTITION> at times at <SET UP>... at times all thread completed successful would show up as soon as hitting START.
I dont have a captivate, can someone please suggest a sure shot solution and post me a link for ODIN, with a root rom. I am using Team Whiskey on my Vibrant, and I prefer stable modified ROM because of its features and power.
I can explain him the process on skype using desktop sharing, but the ROM should be good. Thankyou very much in advance.
if he can access recovery, try wiping everything thru recovery then start again
Phone is in Soft Brick state.
Phone is in Soft Brick state. So i cannot boot into the phone and go to CW recovery.
What he needs is just a stable usb connection that's how he got to this point, bad communication between the phone and computer. On cm7 I beleive you need the nexus s drivers installed. Also make sure it's plugged into a usb port that's attached directly to the motherboard (back of pc, port 1 on laptop)
@studacris
I think the drivers are already installed good. The connection is also good, as i can the COM port detection in the ODIN, with one of the boxes changing its colour from NO-COLOUR to YELLOW-COLOUR.
I think the ROM builds are not good. They go action-less during flashing, actually nothing (progress bar) comes on phone, it keeps showing the Downloading screen, endlessly. Odin usually is stuck at at <SET PARTITION> at times at <SET UP>...
Can someone post a link for a test one click odin. Well i would prefer one click.
You did try DG's JF6 one click, thats the only one I use, how are you establishing dowload mode on the phone or are you even doing this.
REMY4223 said:
I would suggest to Odin back to stock then update to Froyo via Kies.
Click to expand...
Click to collapse
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Ragin Caucasian said:
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Click to expand...
Click to collapse
+1 If you read the OP the problem is he can't flash back to stock he is having problems flashing anything period, @ the OP correct me if I'm wrong but I have a strong hunch that you are leaving out some pretty crucial steps, I have a feeling that you are not putting the phone into download mode, I also believe that you are gonna need to make a jig and pay a visit to your brother to help him out especially if its bricked the same way mine just was flashing with cm7 roms. But if you are getting a com port to show without having to put in download mode then you are farther along in the boot process. If this is the case you may be able to adb into recovery do a full wipe excluding /boot and reflash. Will the PC recognize the phone with it in its current boot locked state? If so then recovering should be somewhat of a breeze.
http://forum.xda-developers.com/showthread.php?t=829392 read this post it may help otherwise there are tons others
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
viveksharma2108 said:
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
Click to expand...
Click to collapse
Try putting the phone into download mode after you open Odin. Which version of Odin is this? Also, installing the nightly build of CM7 again often fixes the boot loop on the newer builds. I would try that if you can get to recovery.
Sent from my SGH-I897 using XDA Premium App

[Q] OH NO! Another noob bootloop thread :p

Hello fellow captivate users, I need some help here!
I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.
With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).
So far I've tried these oneclicks-
I897UCJF6 with bootloaders
I897UCKK4 with bootloaders
Plus various other packages that use odin to flash the different parts of the filesystem etc...
I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)
I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!
I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter )
Any help would be greatly appreciated
Cheers XDA Gurus
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..
do you need the jig? is the button combo not working? both volume + plug in usb to PC
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/showthread.php?t=1386924
heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.
or...
try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.
give that a shot...
Wow, quick replies guys, thanks.
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with
Click to expand...
Click to collapse
I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
Click to expand...
Click to collapse
I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.
do you need the jig? is the button combo not working? both volume + plug in usb to PC
Click to expand...
Click to collapse
Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
Click to expand...
Click to collapse
Cool, so cable/ports are ok
Code:
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/show....php?t=1386924
Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.
To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.
Thanks again
I must be messing up - having trouble getting into recovery.
Here's what I did;
The links here: http://forum.xda-developers.com/showthread.php?t=1386924 are dead, so I went straight to method 2.
Downloaded speedmod kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.
How long should I hold the 3 buttons down for? (How many bootloops?)
Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?
All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)
**edit
I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.
For button combo to get into recovery--release when u see 1st att screen.
Or
Have u tried Adb (Android Debug Bridge) to get into recovery ??
Sent by XDA Premium App
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.
Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
Sent from my FUSIONideos using XDA
TRusselo said:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Click to expand...
Click to collapse
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business
*removed double post
studacris said:
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Click to expand...
Click to collapse
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.
You have to hit enter at the Right moment, it takes practice
Lol, lucky I've got plenty of patience then!
Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?
Am I able to use adb from there to get an update.zip to internal sdcard?
How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!
Also am I right in assuming that because it gets to download mode it is eventually fixable?
Sent from my FUSIONideos using XDA
Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.
Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.
Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?
Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
Sent from my FUSIONideos using XDA
If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.
Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.
There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.
I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course )
How about a non one click?
I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.
Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
Sent from my FUSIONideos using XDA
Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.
I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.
Unless anyone has any other ideas I'm stumped for now.
When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know
Edit: mabey designgears remembers what fix it when cognadian bacon porked it
Sent from my SGH-I897 using xda premium

Please help i will donate/ pay u

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.

[i9000b] BSOD - Phone ! Computer Screen

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

Galaxy S Os upgrade questions.

Searching the forum constantly, but I figured I'd ask at the same time.
Heres what i have:
Galaxy S
Rooted
Froyo 2.2
Baseband I9000UGKC1
Kernel 2.6.32.9 [email protected] #4
Buikd FROYO.UGKC1
I've Rooted and Unlocked. I require UNLOCK.
I'd like to upgrade my OS to either JB or ICS whichever is the most stable and smooth. (I'm looking for iPhone smooth.)
I think I'll use Cyanagenmod and Clockwork recovery.
Will This remove my unlock? If so. Is there a way to unlock ICS or JB?
Suggestions, Tips please.
Thanks a bunch.
Liquyd said:
Galaxy S
Rooted
Froyo 2.2
Click to expand...
Click to collapse
First backup your important files to your PC than you must first upgrade to gingerbread 2.3.6 only than you should and can flash ICS and after that JB. you can do the gingerbread upgrade by using KIES or ODIN, and flash again with a semaphore kernel which will give you CWM + root using Odin, after that backup your EFS before flashing ICS using CWM and finally JB with CWM
Thank you. Didn't realize I had to go gingerbread first. Could have ended badly...
By re flashing I lose my unlock. Yes?
There is a way to unlock in JB?
Thanks again.
Sent from my GT-I9000M using Tapatalk 2
Liquyd said:
Thank you. Didn't realize I had to go gingerbread first. Could have ended badly...
By re flashing I lose my unlock. Yes?
There is a way to unlock in JB?
Thanks again.
Sent from my GT-I9000M using Tapatalk 2
Click to expand...
Click to collapse
No, you won't lose your unlock, Read your wiki page for guidance http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_Series
Sorry for the late reply. I've been fighting for two days with Kies.
I can't get my phone to connect with it.
I believe its a driver issue.
I can let windows find the driver. Phone then is recognized by windows. But doesn't connect to kies. I get an error message.
Tried following the troubleshooting guide in Kies. It installs driver. No connect.
Went to Samsung for driver. No go with Kies again.. I get a message from windows saying my device can perform better using a usb 2.0 port. I was on a 2.0 port.
Got a driver from xda wiki. Same results.. I cannot get kies and my galaxy to work together.
Tried different usb cable (official Samsung). And different USB port.
I'm lost...
**Update**
I just tried on an XP machine. Same thing. 'can't connect to device, please disconnect and try again'...
Should i try a factory restore and start over from the beginning?
Sent from my GT-I9000M using Tapatalk 2
Liquyd said:
Should i try a factory restore and start over from the beginning?
Sent from my GT-I9000M using Tapatalk 2
Click to expand...
Click to collapse
just uninstall KIES, leave the USB drivers, and connect with ODIN to flash a gingerbread 2.3.6 ROM according to your region from here http://forum.xda-developers.com/showthread.php?t=1102881 than root with a semaphore kernel from here http://forum.xda-developers.com/showthread.php?t=1112908 , you will also get CWM with this kernel.
No use wasting time trying to get KIES to work, this is happening to a lot of people , could be due to Microsoft's competition with Samsung. you can get all your softwares , tools etc from here http://forum.xda-developers.com/showthread.php?p=29331775#post29331775
xsenman said:
just uninstall KIES, leave the USB drivers, and connect with ODIN to flash a gingerbread 2.3.6 ROM according to your region from here http://forum.xda-developers.com/showthread.php?t=1102881 than root with a semaphore kernel from here http://forum.xda-developers.com/showthread.php?t=1112908 , you will also get CWM with this kernel.
No use wasting time trying to get KIES to work, this is happening to a lot of people , could be due to Microsoft's competition with Samsung. you can get all your softwares , tools etc from here http://forum.xda-developers.com/showthread.php?p=29331775#post29331775
Click to expand...
Click to collapse
Followed Instructions... Got stuck in boot loop.
now
Phone ! PC image....
Did I Brick it? I could access Download mode. Tried recovery. now I have the Phone ! PC screen...
appreciate any help now... I'm without a phone.
Obviously, your flashing process was interrupted.
First of all, did you backup your data?
2nd, Go to Download mode (Power + Home + Volume Down) then reflash Gingerbread via ODIN.
Liquyd said:
Followed Instructions... Got stuck in boot loop.
now
Phone ! PC image....
Did I Brick it? I could access Download mode. Tried recovery. now I have the Phone ! PC screen...
appreciate any help now... I'm without a phone.
Click to expand...
Click to collapse
Nope, not bricked, Did this happen after you flash ROM or after you flashed the semaphore kernel? anyway...
1) reboot PC as well reboot phone after a battery pull, also take out SIM Card as well as your EXT SD card , reisert battery after pressing power button for a min
2) make sure you had uninstalled the KIES only leaving the Samsung USB drivers
3) go into download mode and flash again the ROM as per instructions on that page.
IF not you can use a i9000 rescue or resurrection kit from http://forum.xda-developers.com/showthread.php?p=29331775#post29331775 , has guides there too
BTW make sure you have good battery charge at least 50% before you flash and never interrupt flashing process
xsenman said:
Nope, not bricked, Did this happen after you flash ROM or after you flashed the semaphore kernel? anyway...
1) reboot PC as well reboot phone after a battery pull, also take out SIM Card as well as your EXT SD card , reisert battery after pressing power button for a min
2) make sure you had uninstalled the KIES only leaving the Samsung USB drivers
3) go into download mode and flash again the ROM as per instructions on that page.
IF not you can use a i9000 rescue or resurrection kit from http://forum.xda-developers.com/showthread.php?p=29331775#post29331775 , has guides there too
BTW make sure you have good battery charge at least 50% before you flash and never interrupt flashing process
Click to expand...
Click to collapse
Thank you so much! Without your help. I'd be knee deep in threads and various topics that made no sense to me.
It was battery.. I gave it a full charge and tried again. Worked. Sorta... Still had a boot loop after flashing GB. Got fed up and hit restore. Upon reboot. GB was there... Flashed sephamore with 0 issues. Running like a charm.
One last thing. Is ICS worth it if GB is working fine? I mean what are the benefits of ICS over GB? My friend swears by ICS on his RAZR should I worry about it on my 9000M?
Big thanks again. Cheers! :good:

Categories

Resources