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
Related
I had loaded the ginger clone rom and all was well. I then however wanted to swap kernels so i loaded up seitrons cwm 1.5.6 and proceeded to flash through cwm. this has now become the worst day of my life. the phone will not boot past the galaxy s screen. i cannot not get into recovery and both computers now say usb device not recognized when in download trying to flash odin. i am worried that something is corrupted on my phone because not matter how many times i uninstall and reinstall the drivers no luck. i think it is officially bricked and im sol. maybe some great minds can figure it out here.
It's not bricked - issue is trying to get your computer to recognize your phone when in download mode so you can flash it back.
What OS are you running? Also - where did you download the drivers from? Some seem to work better than others.
If you can get to the galaxy screen you might still be able to to get into recovery. pull out the battery and use the 3 button combo. Hold down both volume button then power and let go of the power button after it turns on. then just reinstall the rom
I'm willing to bet you can also get into Download Mode either with button combos, or a JIG. Once in Download, you can use Odin to restore to JF6, and have a working phone to flash around with again.
i can get into download mode no problem. and i think it is quite possible drivers are corrupted on the phone itself. my wifes phone works on the same exact setup. no usb device not recognized error. i have tried the drivers from here and samsung directly with no luck. 3 button combo does not work. sim out sim in battery out and in. but like i said it will just not register with the comp and hers will. so im going to att and seeing about replacing it. but i will see how that goes. ive done this lots of times with no issues ever.
download works
3 button combo does not so no recovery
usb device not recognized error
thanks for the help and keep it coming i will try everything if i haven't already.
Try current usb port
Sent from my SCH-I897 using XDA App
Think I'm in worse shape. Tried flashing just the kernel to get BLN working again (last ROM I put on somehow loaded a non-compatible kernel). Now the phone boots the white ATT screen and just sits there. Can't get it into D/L mode with 3-button and doesn't respond to computer I have been using to flash ROMs for a couple weeks now...
Am I hosed? ANY help would be greatly appreciated...
You could try to use a JIG to force your phone into Download Mode
Okay...well, got into D/L mode finally. Used Odin to get it back to factory. Used the One Click rooter again, except now it boots to recovery 3e, which doesn't let my power button work as the okay button Pulling the battery to reset it, but it will no longer go into D/L mode to use Odin again. It keeps booting to the recovery Utils, which I cant get out of...*sigh*
Thoughts?
at least your able to do something i still cannot get my phone into recovery or to be recognized by the computer. it is not the drivers so i have no idea. i can only think that something got funked up with the kernel flash.
if you are getting into 3e recovery then you are most certainly NOT using the JF6 one click stock
3e recovery comes on JI6 which is the FroYo leak....completely different builds and roms
have you tried a different usb cable? I was having this problem, and the stock samsung cable was B.O. and wasnt working... i tried my blackberry one and all was good
magnumrt562 said:
have you tried a different usb cable? I was having this problem, and the stock samsung cable was B.O. and wasnt working... i tried my blackberry one and all was good
Click to expand...
Click to collapse
i actually tried this yes. i had a blackberry cable from the storm (shivers) that was laying around. tried that but no luck with that or my wifes cable as well. but a good tip for others nonetheless
Pirateghost said:
if you are getting into 3e recovery then you are most certainly NOT using the JF6 one click stock
3e recovery comes on JI6 which is the FroYo leak....completely different builds and roms
Click to expand...
Click to collapse
I just want to quote this to stress the importance.
Thank you, didn't realize that (still sorta new to this)...
I downloaded a zip (I thought from here somewhere) that extracted into the 4 files. Anyone got a link to the JH6 set of files?
I also downloaded DG's "One Click Odin", but it doesn't seem to really do anything when I run it unless I manually load all the files. Also, I don't see a "Master Clean" like the post refer too
are you sure you downloaded the right odin? in the one click version, theres no option to load files at all. only a "start" and "master clear"
make sure the odin one click is open before you connect your phone.
http://forum.xda-developers.com/showthread.php?t=731989
You guys rock! I don't know how, cause I could have sworn I D/L'd it from that link before and I got the generic Odin, but it looks like I have the right one now! Thank you for your patience with us noobs as we start getting into this new world!
glad you got yours working. i have officially given up and receiving a new one on tuesday. i tried everything but somehow someway the phone is not recognized in download mode. oh well have to mess the with new one then lol
zippox180 said:
glad you got yours working. i have officially given up and receiving a new one on tuesday. i tried everything but somehow someway the phone is not recognized in download mode. oh well have to mess the with new one then lol
Click to expand...
Click to collapse
I was having the same problem. Have you tried powering off, start odin, hold both the volume up/down, then plug in the usb to your phone?
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
I have an issue, I was updating my Captivate to 2.2 with Odin3 One Click and that worked fine, then for some reason I cannot explain I tried to use Odin to upgrade to 2.3 (the blow fish one) flashed the image then got the restart with the blowfish and then used Odin to complete the process as per the instructions and got soft brick, I fixed this with the one click unbrick, then it went into a boot loop.
The loop is AT&T screen then fuzzy colours and a restart (like a graphics card has gone haywire).
I can get into the download mode by removing the battery, plugging the USB cable in holding the volume buttons then installing the battery the download mode appears but Odin is not picking up the phone.
When it is in the loop I can get Odin to identify the phone but when I try to go into download mode it won’t identify it. I have tried with adb and it does the same thing.
Any suggestions? I have looked at the forums for a long while so my apologies if this has already been covered.
Have you installed the necessary drivers on your computer?
Sent from my glitched ICS Captivate using XDA App
You may want to also take a look at the "Captivate Connection Issues" thread - it has some steps to help get you connected in download mode.
Once you have it connected, you can probably safely flash a Gingerbread stock rom to get back to a clean place to start flashing from.
Hi,
Yes forgot to mention that I have installed the correct USB drivers, Odin picks up the phone during the loop so that tells me that the Cable is fine and the drivers are working. I will try to re-install them just to be safe.
Thanks I will look through the connection issues threads and see if that helps, I am at work at the moment so will be later in the day.
The garbled bootscreen happens when you try to run gingerbread with froyo bootloaders. You must have chosen a bootloader free package. Instead, for your first time flashing to GB (and first time only), use a package with bootloaders
Sent from my CM9 ICS i897 Captivate
Haplo Nash said:
... upgrade to 2.3 (the blow fish one) ...
Click to expand...
Click to collapse
What is this blow fish one that you speak of? Korockinout13 is correct that you are getting the garbled screen because of an incorrect bootloader. You may be having issues because the ROM you flashed might be an i9000 based ROM and you will need different drivers.
DISCLAIMER: It's still earlier early and I haven't had all my coffee yet. Please correct my logic if it is wrong.
Red_81 said:
What is this blow fish one that you speak of? Korockinout13 is correct that you are getting the garbled screen because of an incorrect bootloader. You may be having issues because the ROM you flashed might be an i9000 based ROM and you will need different drivers.
DISCLAIMER: It's still earlier early and I haven't had all my coffee yet. Please correct my logic if it is wrong.
Click to expand...
Click to collapse
I believe the blowfish one he's referring to is the Fugu Root method.
About One-Click UnBrick
This Software:
Will work on all Samsung devices which use Odin3
Is a single, portable executable
Is the first one-click anything for our devices on Linux
Works on Mac
Works on Windows
Is open source
Is programmed in Java
Deploys and installs Heimdall for your OS
Is super easy to use.... Only one button!
Click to expand...
Click to collapse
The bolded line is why ODIN no longer detects your phone. The Heimdall driver has been installed. You can either go grab a Heimdall one click from here or remove the Heimdall driver (trying another USB port may work) and then try using ODIN again.
Yes it was the Fugu Root's one and I didnt update to a Gingerbread bootloader before I flased it onto my phone.
Thank you for all your help, I will never mess around with my phone at 2am again.
I managed to get Odin to pick up the phone and was able to re-load FROYO and will start again.
Do Apex ROM Heimdall one-click flash with bootloaders enabled. Most painless process.
I had tried flashing the SlimBeam ROM (coming from Helly Bean, which worked great), but got the perpetual AT&T logo of death. This seemed to be an issue with several other users, as pointed out in the SlimBean thread.
To resolve this, I flashed back to stock with a Heimdall One-Click utility. Stock now boots great and the phone is functional (albeit now running a very old version of Android). I was looking to root again to go back to Helly Bean. However, I can no longer enter recovery mode with either the 3-button method or ADB. When the phone is told to enter recovery, it just hangs at the AT&T logo, just like when it was trying to boot SlimBean.
I can restart the phone into the stock ROM and I can also successfully enter download mode. Recovery just isn't happening.
Any ideas on what I can try at this point? I'm on a Mac but have access to a PC if necessary.
Have you tried flashing a stock rom with bootloaders? I hate suggesting that, but sometimes re-flashing the bootloaders makes a difference.
Just make sure you're careful to have a solid connection throughout the flash.
themilstead;30584149
To resolve this said:
Which stock did you flash back to? I've only done it (but lots of times) with Odin-one-click, not Heimdal but not all the one-click packages contain CWM.
You could try one of these:
http://forum.xda-developers.com/showthread.php?t=1300843
Click to expand...
Click to collapse
Ah, I don't remember if the Heimdall package came with a bootloader (I did this earlier today at the office, and I'm home now). When I was restoring earlier, Odin wouldn't recognize that my phone was connected in download mode...hence me using Heimdall. I'll give Odin another shot right now since I'm up and running with stock.
There are Heimdall packages with bootloaders, if you need it.
Just remember that Heimdall will write its drivers to the port you installed it to - if you plug in your phone to that port and try to fire up Odin, Odin won't see it.
I'm on a different computer than when I used Heimdall earlier, so Odin is now recognizing the phone.
New problem: The process won't get past "SetupConnection". I'm currently trying out "I897UCKJ3 Stock with BL".
Rah rah rah rah rah.
^
See this thread by jmtheiss for help with ur prob. --- Captivate Connection Issues and Download Mode Help
Well, I'll be damned: The Epilogue
Got it!
It was simply a matter of me continuing to try other USB ports (my computer has 4). I tried one that previously didn't work, and it suddenly did. Not exactly sure what changed, but persistence paid off! I suppose power tolerance is potentially different for each port? (...in the same vein of it's better to plug into the back of the computer rather than a keyboard. I digress.)
Anyway, after Odin both recognized my phone and got past the "SetupConnection" step, I proceeded to install "KI2 w/ Bootloaders & Boog's KernO". This included ClockworkMod built-in, so I thought it'd be a good option. Sure enough, I was finally able to boot into recovery without any sort of trouble, then proceeded to install the new CM10 nightly.
Everything works. Thanks for the replies and help, everyone!
Hi everybody,
I've been at this for a couple days now, trying every solution I can come across, but nothing seems to work. My mom's Captivate decided the other day that encryption had failed (I don't think anyone ever told it to encrypt itself...). It said all I had to do was click the Reset button, but that didn't work. So back to ODIN I went.
Unfortunately, though I could swear I've used ODIN on this phone before (it was running CM10, and I'm pretty sure I messed up a couple times trying to get it on there), I can't get it to work again. I've tried the One-Click ODIN (which is what I would have used before), as well as downloading two different tar.md5s from sammobile.com and flashing them with a different ODIN.
After using the One-Click method, the phone powers on to the AT&T screen, and then it powers off, switching between different charging icons if it's plugged in. The other ODIN flashes got me to Installing packages.. after boot, but then it gave me rfs errors. So I figured I needed to flash a new PIT, but that didn't seem to help. Doesn't One-Click do that anyway?
I've tried two different USB cables and two computers (both Windows 7 SP1, one doesn't even have any antivirus program on it yet), but no luck. I had a different computer the last time I would have used ODIN on this phone. I believe this phone is a 1007 build, assuming I am looking at the right number under the battery.
Any help would be greatly appreciated. Thanks in advance!
see encryption unsuccessful thread. your internal storage is probably dead, but you can run from external sdcard with the fix described in the thread.
http://forum.xda-developers.com/showthread.php?p=21439417
Sent via Monty Pythons Flying Circus
Yeah, that's the problem
Darn. Seems like that is the problem. Simply putting in an external SD card allowed me to boot, but now I have to get CWM on it through ODIN... Thanks.
CWM via ODIN?
Does anyone know how to install CWM through ODIN? I'm back with the stock recovery, and when I try to install a ZIP it fails the signature verification (for any ZIP I try). Seems that ODIN would be the way to go.
Stock recovery won't let ya flash zip files that r not signed by samsung.
Ya have to have the zImage in a .tar file in order to flash it through Odin.
Here is the KK4 Corn Kernel thread. http://forum.xda-developers.com/showthread.php?p=18233847
I recommend the version 7.0A for what u r wanting. There is a .tar version of it there. PDA slot is the one to use in Odin for flashin a kernel.
Sent from my SAMSUNG-SGH-I747 using xda premium
Running CornKernel, repartition error
OK, I'm up and running with CornKernel. I rooted it using the ZIP (and now the phone is unbelievably slow, but it's rooted nonetheless). (I also tried the advanced CWM option to root it, but that messes the phone up.) But when I try to repartition the SD card, it says "An error occured while partitioning your SD Card. Please see /tmp/recovery.log for more details." but /tmp is empty.
Getting rid of the phone
Meh, forget about it. I'm going to sell this phone as-is or part out anything I can. I need to move on, as spending more time on this phone when it's permanently damaged is not worth it to me. (If anyone wants it by chance, just let me know...) Thanks for pointing me to what the problem was though.
...necro bump... You wouldn't still happen to be selling that would ya?
Sent from my GT-I9000 using XDA Premium 4 mobile app