[Q] Can't Flash Stock Rom + Terrible Battery Life - Captivate Q&A, Help & Troubleshooting

My Captivate is only about a week old. After getting it, I immediately rooted it and installed stock Froyo, but wasn't satisfied with the battery life or performance. So I installed Darky's 7.5 ROM (nowipe version using the 'wipe data + cache' option in CWM) along with the glitterball kernel and JL3 modem. Performance and stability were excellent, but battery life was abysmal, even with no apps running and the CPU capped between 100MHz and 800MHz using SetCPU (which is plenty fast on this ROM). I'm talking about 10-15% drain per hour while on standby, packet data, wifi, bluetooth, GPS, and sync all off.
I attempted to flash back to stock to try other ROM's, but Odin one-click simply bricked my phone to the point where I needed a hardware jig. After much work, I was able to flash Cognition using the regular Odin and then use CWM to restore my phone back to the Darky's ROM state with all my data and apps intact. Battery life is still terrible though. I've tried several methods to revert my phone to a stock kernel, including Odin one-click, Odin with 3-button fix, and regular Odin loading various stock ROM PDA and PIT files.
The furthest I was able to get was a phone with a working recovery menu that gave me 'Kernel Panic' right after the AT&T logo. Otherwise, the phone would be completely bricked (no button combinations) and I'd have to reset it using the jig. However, flashing a custom ROM that *doesn't* require reverting to stock first (Odin-flashable), or restoring a backup from CWM works just fine every time, no matter how badly I brick the phone. It's just stock ROM's and kernels that I can't get to boot or install properly.
I'm running out of ideas, because this battery drain is unacceptable and my ROM choices are severely limited. I did try flashing some ROM's over Darky's (JPY) without the revert-to-stock step, but I always get weird problems like missing phone, message and contacts apps.
I would really appreciate it if someone could help me out.

You need to get your odin issues worked out. They are abnormal. One I would try to delete the prism then re download. Two please list steps your are following to flag with odin, hopefully it is an ready oversight someone xan point out to you.
Sent from my SGH-I897 using XDA App

mcord11758 said:
You need to get your odin issues worked out. They are abnormal. One I would try to delete the prism then re download. Two please list steps your are following to flag with odin, hopefully it is an ready oversight someone xan point out to you.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I have re-downloaded both Odin and the files to flash multiple times, confirmed by the '(1)' tacked onto the filenames in my download folders. My procedure:
1. Extract Odin and PIT file (if flashing with a PIT).
2. Run Odin as Administrator, select PDA tar/md5 file (and PIT file if applicable). Untick 'Auto Reboot'.
3. Put phone into download mode using volume button combo (or hardware jig if Odin already bricked my phone).
4. Plug phone in. Phone recognized immediately by Windows and Odin.
5. Click start in Odin. Procedure always completes successfully.
6. Battery pull and unplug phone. Put battery back in and turn phone on. If flashing a stock ROM, phone either gets kernel panic, or is bricked and all button combos are disabled.
The files I used for stock flashing were found in the Odin one-click + master clear thread and the Odin one-click button combo fix thread (which uses a PIT and PDA file). I used Odin 3 v1.0 when flashing PDA files (had no problems flashing cognition ROM or non-stock kernels).
For the one-click versions, I followed the above procedure (minus the selection of PDA/PIT files). One-click always bricks, regular Odin will either brick or cause kernel panic when flashing a stock ROM or kernel, depending on PDA/PIT files and the previous state of the phone.

When you run odin one click, were do things appear to go wrong
Sent from my SGH-I897 using XDA App

mcord11758 said:
When you run odin one click, were do things appear to go wrong
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
There's no sign of anything going wrong until the phone auto-reboots (since you can't disable that in one-click). Upon rebooting, the phone just loops the AT&T logo, requiring a battery pull. Button combinations do not work and the battery charge icon (when the phone is off) freezes when the phone is plugged in.

GGXtreme said:
There's no sign of anything going wrong until the phone auto-reboots (since you can't disable that in one-click). Upon rebooting, the phone just loops the AT&T logo, requiring a battery pull. Button combinations do not work and the battery charge icon (when the phone is off) freezes when the phone is plugged in.
Click to expand...
Click to collapse
are you at&t our rogers? What us the name if the odin file you are using/
Sent from my SGH-I897 using XDA App

mcord11758 said:
are you at&t our rogers? What us the name if the odin file you are using/
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I'm on AT&T. Odin files I've tried include:
Odin3 v1.3.exe (bundled with Odin3.ini and s1_odin_20100803.pit)
Odin3_v1.0.exe (bundled with PIT.pit and used with PDA.tar)
Odin.exe (bundled with PIT.pit and PDA.tar for Cognition)
I897UCJF6-final-OCD-REV0.exe
All of the Odin executables (with the exception of the one-click) work fine flashing Cognition and I9000_reoriented_v2.3.0.tar (xcalib kernel), but not with the included PDA.tar files. When I say 'work fine', I mean flash the phone into a workable, non-bricked state, since Odin never throws me any errors or failures.

*bump*
Is this hopeless? I've asked about this elsewhere, and no one seems to have any suggestions. My phone has been up and running fine on multiple different custom ROM's and kernels, but it still bugs me that I can't flash back to stock if needed. Also, any suggestions on improving battery life are very welcome.

After searching around for a bit, it seems that Captivates from batches 1008 to 1010 cannot be flashed back to JF6 using any version of Odin. The closest that can be achieved is JH3 using Odin 1.7. This is pretty disappointing.
Oh well, I guess I have no luck with technology. Unless anyone feels like throwing battery life suggestions at me, this thread can be closed/deleted I guess.

The battery probably just needs calibrating.
There are.multiple threads in the forum on this and I would be happy to point.you to them, bit.I am on the phone app and its a little more.difficult to do so.
Sent from my GT-I9000 using XDA App

Search development thread for I897UCJH7 - OTA by designgears. Close enough to JF6.
Sent from a phone somewhere in the universe

http://forum.xda-developers.com/showthread.php?t=731989 <-- this is what I use to go back to stock before every re-flash. Never had an issue.
Build 1008 phone - hobbling along with random reboots etc.. and no buttons working.
I wouldn't suggest using anything else to flash back to stock. Then flash your new ROM as usual. You do NOT need to do a "stock" 2.2 froyo ROM first before installing any custom ROM.
The simple way to flash correctly to a new ROM
Use Odin 1 Click I897UCJF6 back to Stock.
Root your Phone (Or if you kept the Update.zip from CWM you can fore go all of this )
Download ROM Manager - update Busybox
Put the ROM you wish to use on your SDCard
Go into CWM and flash as normal following the dev/cooks instructions.

cappysw10 said:
Search development thread for I897UCJH7 - OTA by designgears. Close enough to JF6.
Sent from a phone somewhere in the universe
Click to expand...
Click to collapse
Thanks. I eventually figured out the JH2 to JH7 trick. It seems I can't properly flash any ROM below JH3 using any version of Odin.
avgjoegeek said:
http://forum.xda-developers.com/showthread.php?t=731989 <-- this is what I use to go back to stock before every re-flash. Never had an issue.
Build 1008 phone - hobbling along with random reboots etc.. and no buttons working.
I wouldn't suggest using anything else to flash back to stock. Then flash your new ROM as usual. You do NOT need to do a "stock" 2.2 froyo ROM first before installing any custom ROM.
The simple way to flash correctly to a new ROM
Use Odin 1 Click I897UCJF6 back to Stock.
Root your Phone (Or if you kept the Update.zip from CWM you can fore go all of this )
Download ROM Manager - update Busybox
Put the ROM you wish to use on your SDCard
Go into CWM and flash as normal following the dev/cooks instructions.
Click to expand...
Click to collapse
That is what I've always been trying. Attempting to flash anything below JH3 with any version of Odin (one-click or regular with PDA/PIT files) ALWAYS bricks my phone and requires a jig, 100% of the time, using any computer. Flashing a newer/custom ROM works fine.

GGXtreme said:
Thanks. I eventually figured out the JH2 to JH7 trick. It seems I can't properly flash any ROM below JH3 using any version of Odin.
That is what I've always been trying. Attempting to flash anything below JH3 with any version of Odin (one-click or regular with PDA/PIT files) ALWAYS bricks my phone and requires a jig, 100% of the time, using any computer. Flashing a newer/custom ROM works fine.
Click to expand...
Click to collapse
intriguing the somewhat random button combo issues on some newer builds of phone

newter55 said:
intriguing the somewhat random button combo issues on some newer builds of phone
Click to expand...
Click to collapse
I can't remember if it did, but I think the actual issue is that my phone came with JH7 (not JF6) and is actually incapable of running older firmware due to some difference in the hardware/build. That's why flashing stock JH7 seems to work fine.

Related

[Resolved]Stuck in a boot loop (I think) What now?

Help.
I have been running Frost just fine for about 24 hours now. Have rebooted a few times for media scanning reasons without incident. Just now I rebooted and am stuck in a boot loop. So I long held the power key and boot loop again. Then pulled the battery and tried again and I get the same thing. Google logo and then the frosty Team Whiskey a few times and then it vibrates and starts all over. What should I do from here. Its the first time Ive had a problem flashing and Im thinking I have to use Odin now....or can I get into recovery somehow and boot from there? ( sorry if I posted this in the wrong section. In my nervousness I posted here instead of Q&A)
edit: Read, read, and read some more. Odin-ed to stock successfully....and then did it again to be safe. Now to start the root/ flash process all over. It's almost like an addiction. This time I think I'll stick with one rom for a while.
just ODIN back to something. Learn it. Love it. It's simple.
Ok. Any way I can use my nandroid backups? If no.....would I be best to go back to stock and then to my rom of choice? or just odin to my rom of choice
GoodVibrant-ions said:
Ok. Any way I can use my nandroid backups? If no.....would I be best to go back to stock and then to my rom of choice? or just odin to my rom of choice
Click to expand...
Click to collapse
Since frost uses ext 4 for partitions, I recommend odin to jfd stock with repartition checked. it has all the fs files you would need. Then flash back to whichever rom you want. there are tutorials on how to use odin, or you can use heimdall, same thing but open source and you need to unzip the tar that the rom comes in to get the individual files inside.
wildklymr said:
Since frost uses ext 4 for partitions, I recommend odin to jfd stock with repartition checked. it has all the fs files you would need. Then flash back to whichever rom you want. there are tutorials on how to use odin, or you can use heimdall, same thing but open source and you need to unzip the tar that the rom comes in to get the individual files inside.
Click to expand...
Click to collapse
Ok...looks like I have some reading to do. I knew I was gonna have to do this sooner or later so I guess it's good I learn it now.
When you say I have to unzip the tar that the rom comes in.....does that just apply to heimdall....or heimdall and odin both?
GoodVibrant-ions said:
Ok...looks like I have some reading to do. I knew I was gonna have to do this sooner or later so I guess it's good I learn it now.
When you say I have to unzip the tar that the rom comes in.....does that just apply to heimdall....or heimdall and odin both?
Click to expand...
Click to collapse
Just heimdall. If you use odin, just load the whole tar the rom is in into the pda field.
I just odin back to Eugenes Froyo that doesn't brick w partitions set, I wonder if im doing it right, or if my phone would work better if I odin'd back to JFD stock, never had any problems though, and ive been in some bad soft bricks (e: cant mount, bootloop, etc..)
Sent from my SGH-T959 using XDA Premium App
gfropr said:
I just odin back to Eugenes Froyo that doesn't brick w partitions set, I wonder if im doing it right, or if my phone would work better if I odin'd back to JFD stock, never had any problems though, and ive been in some bad soft bricks (e: cant mount, bootloop, etc..)
Click to expand...
Click to collapse
I've heard of this also but I don't want to mess anything up worse than it already is. Would Eugenes froyo no brick be ok since I'm coming from frost?
My best advice would be odin back to stock, it's a fresh clean start, don't be intimidated, odin is very ready to use, go to the Bible and get the 512 file, JFD stock file, and Odin program. If I could do it without a hitch, you can too, it takes about 2 minutes to odin, go for it! lol
Sent from my Vibrant w/ Bionix V 1.3 and Launcher Pro Plus
negerhab said:
My best advice would be odin back to stock, it's a fresh clean start, don't be intimidated, odin is very ready to use, go to the Bible and get the 512 file, JFD stock file, and Odin program. If I could do it without a hitch, you can too, it takes about 2 minutes to odin, go for it!
Click to expand...
Click to collapse
Thanks man. I appreciate the reply.....wish I would have saw it earlier. It might have saved me a little bit of time. I am writing this from my phone after odin-ing to stock and then odin-ing to eugenes jk2 froyo. After that it was cake to flash back to bionix 1.3. You're right though....its intimidating to use odin when you have never done it but now that I have I will use it anytime I switch between roms. Plus I feel like I now have a clean install of bionix. But mainly I'm glad the panic is over and my phone is back to lightning speed operation.
Sent from my SGH-T959 using XDA App

[Q] Questions about preventing a second hardbrick

This is how the story goes, bear with me.
I had an ATT Captivate 1012 running on S7 but it was rebooting on me during phone calls. I decided to go back to stock with odin oneclick as I had read it works with 1012s but the process hung. I managed to recover and flashed back to stock JH2 with the non-one-click version.
I followed this guide by Breakin' Ranh
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
I had used it successfully to get to stock before many times.
This is where I think I screwed up, please correct me if im wrong.
I thought that taking me back to JH2 would restore my bootloaders and allow me to install the 3buttonFix.zip via CWM over stock JH2, but after installing that zip my phone didnt boot up since.
The 3ButtonFix.zip I used was from this thread http://forum.xda-developers.com/showthread.php?t=1134443 . Via CWM, not Odin.
My battery was not at 100% (checked with a friend's phone and it was at about 24% so I'm not sure if that was the issue.
The question is, wouldnt have flashing to JH2 wipe out the bootloaders S7 installed (i9000 GB loaders if im correct)
I can only think of few things and would appreciate, if possible, your thoughts about these, all in an effort to learn more about the process and to reduce my chances of hardbricking again (Got a new captivate, 1010 this time)
1) JH2 bootloaders are clearly not compatible with that 3ButtonFix.zip because it perhaps assumes an underlying JF6 base? I was on JH2 when i flashed the 3ButtonFix.zip linked above
For future reference, should i then go JH2->JH7
This is the JH7 i have used before the 'accident'
(it is linked in the thread above)
I897UCJH7 Firmware
http://www.ponack.net/designgears/JH7_OTA.zip
2) The JH2 .tar provided in that thread did not /*correctly*/ install all? captivate bootloaders?
3) The flash to stock with the above guide didnt clear out my bootloaders successfully. The first time i tried to flash with odin oneclick it failed so i had to start over with the non-oneclick, that's how i managed to successfully get into JH2.
4) Perhaps flashing with a low battery (30% or so) ruined the install of 3buttonFix.zip?
Maybe I botched my flash via odin only to ruin it further with 3buttonFix.zip via CWM.
Would you recommend heimdall for all my (new) flashing endeavours? I _reaally_ don't want to go through the jtagging/phone replacement experience again.
Would have flashing the Odin version of 3buttonFix have prevented this? or maybe using heimdall to get back to stock?
What do you recommend i do to avoid these problems in the future? Stay away from 3ButtonFix.zip and just use a usb jig (finally got one *AFTER* hardbricking).
TL;DR
I read on the forums that people have bricked by ruining their sbl.bin by coming from a gb bootloader. But I was under the impression (apparently incorrect) that flashing to stock (Any stock froyo/eclair?) would prevent such issues. What do you think went wrong?
Sorry for the 20 questions :|
Thanks!
-XercesBlue
That package you flashed did not contain bootloaders at all... you mixed a gingerbread pbl with a froyo sbl.
Did you even try the button combos BEFORE you flashed the fix? You shouldn't have needed it at all...
Just forget that the 3 button "fix" even exists.
studacris said:
That package you flashed did not contain bootloaders at all... you mixed a gingerbread pbl with a froyo sbl.
Click to expand...
Click to collapse
Thank you for your reply studacris.
So the I897UCJH2.tar package I linked to does not contain bootloaders? If so this makes muuuuch more sense now. Should I find a package that contains those "stock" bootloaders to restore the phone into a stock state then ?
Will the packages linked at the bottom of this thread work then?
http://forum.xda-developers.com/showthread.php?t=731989
The "The internal beta's are NOT one-click, please read the linked threads
UPDATE: I897UCJH2 (Internal BETA)" ?
Do you have any ideas how that one is different from the I897UCJH2.tar I flashed following Breakin' Rahn's. If you follow the link you will see they link to the same files I had used during my first hardbrick.
Reading some more I stumbled upon your old reply,
http://forum.xda-developers.com/showpost.php?p=13581072&postcount=1798
So, If i get this right and to reiterate
For 1010s to get back to stock+bootloaders
1) OneClick (http://forum.xda-developers.com/showthread.php?t=731989)
OR
Use the internal betas "I897UCJH2 (Internal BETA)" linked at the bottom of the same thread ??
2) Do this http://forum.xda-developers.com/showthread.php?t=995143
If you run into a bootloop
OR this
http://forum.xda-developers.com/showthread.php?t=963403
?
I hope you understand how I can be a bit confused here.
I had no luck previously with OneClick on my 1012. Maybe the 1010 is different but i doubt it. The process hung at some point and had to start over with Breakin'Rahn's guide. Finally got to stock by perhaps without bootloaders.
---
As for the combos, when on s7 the combos worked. Volume down+power worked as expected for dl mode volume up + power for recovery. Upon flashing the new package I lost them leading me to assume incorrectly I was at a new factory mode.
The power down, remove battery, hold power, put battery, plug usb did not work either when on JH2. Of course, me being new at this I might have missed something.
only odin one click has both stock bootloaders... so IF you wan tot restore stock boots that is the FIRST step. if after that you get stuck in a bootloop you can use any other stock package to fix that.
if you want to flash back to stock firmware but KEEP the gingerbread boots (THEY ARE BACKWARDS COMPATIBLE) just flash another stock package other than one click. that way you should never lose button combos.
and as i said before. delete that 3 button fix from your brain completley.
studacris said:
only odin one click has both stock bootloaders... so IF you wan tot restore stock boots that is the FIRST step. if after that you get stuck in a bootloop you can use any other stock package to fix that.
if you want to flash back to stock firmware but KEEP the gingerbread boots (THEY ARE BACKWARDS COMPATIBLE) just flash another stock package other than one click. that way you should never lose button combos.
and as i said before. delete that 3 button fix from your brain completley.
Click to expand...
Click to collapse
Great, thank you for taking the time to read/reply!
Yes, I am definitely staying away from 3buttonfix.
XercesBlue said:
Yes, I am definitely staying away from 3buttonfix.
Click to expand...
Click to collapse
BUT, Im on a 1010 and the vol up + vol down and power buttons wont get me into recovery.
What method should I use to get into recovery?
If you have the gingerbread bootloaders the combo will work. The combo is in the secondary bootloader...

[Q] Galaxy S i9000 softbricked; won't enter recovery or reflash from download mode

Similar to Masterslackers issue.
The phone was originally a stock Optus Éclair 2.1. About 6 months ago I decided to customize the i9000 with a custom Froyo 2.2.1 Rom (Doc's Rom Docs_XWJS3_Wipe-v9_1) from “The ROM Kitchen”. It worked really well and was much faster and responsive..
Yesterday, I decided to look at a move to Gingerbread and cook another ROM @ the ROM Kitchen, this time a Gingerbread 2.3.4 iteration.
The phone was rooted so I used Rom Manager to get into recovery mode where I could flash my new, Doc's JVR_No_Wipe-v8-00-08-22-10-09-4e6a8e4e86718.zip Rom.
All seemed to go well, but after the Flash, as the phone booted the first screen became filled with 100s of random coloured lines, then it transitioned to the normal Samsung start animation, but soundless.
After booting, I noticed that I no longer had a notification bar where battery, time, signal strength etc. was normally displayed atop the screen. I tried several different launchers to see if that was the issue, but to no avail. I tried to enable the notification bar using Go Launchers gesture setting (no go)
I tried rebooting the phone over and over, the notification bar would not return.
I was starting to lament my decision to flash when the following occurred.
I tried to re-enter recovery mode via ROM Manager to install a different ROM, but the phone bypassed it and then hung @ the Samsung I9000 logo screen. I then had to power the phone off before it would reboot into its UI. I could no longer reach recovery mode by any means.
Because I was getting nowhere and I had read that after flashing a new rom, root would often be lost, so I tried rerooting with "XXJVP-Complete-Rooting-Package" from
http://androidadvices.com/how-to-root-galaxy-s-on-android-2-3-4-xxjvp-firmware/ This also failed but it has also left me with a soft bricked phone.
The phone will not boot up or boot into recovery now, however It would still boot into (3 button) download mode.
I have tried various versions of Odin from v1.0 to v4.28 to ReFlash the phone back to life but with no success yet.
Using Odin, the phone hangs with no sign of progress and reports the following when left for 30minutes or so.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
Anyone have any suggestions that might help to get the phone back.
Thanks, TeZ
So you didn't flash stock gingerbread before flashing custom rom? so you should first flash stock jvr and do hard reset after booting. Then you are safe to flash cwm capable kernel and custom rom.
For the odin problems, maybe you have kies running in background? Kill all kies processes and try again.
And I'd suggest reading all guides found in romkitchen thread..it saves lots of trouble. Hope that can fix your phone
Sent from my GT-I9000 using xda premium
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Thanks for that, I did install kies after I bricked it, in the hope (probably missguided) that it would somehow help. Uninstalling
bigmadpete said:
Agree with above post, if you have Klies on your pc/laptop uninstall it, and re download the drivers, i have a good 2.3.4 tutorial and root 2.3.4 tutorial, both with Odin, let me know if interested. Also if you have heimdall installed then uninstall it also.
Click to expand...
Click to collapse
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Your post looks promising, I'm going to try this method out and see where it leads. I'll reply back with the outcome, many thanks
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
bigmadpete said:
No problem. Try this option if you like http://www.theandroidsoul.com/xxjvp-android-2-3-4-firmware-galaxy-s-install-and-download/
And then this to root
http://www.theandroidsoul.com/root-xxjvp-firmware/
Click to expand...
Click to collapse
Thanks for the info, running out of time today, will try for tomorrow
When moving from a froyo (2.2) rom to gingerbread, (2.3), you need the gingerbread bootloaders or you'll get all sorts of crap when turning on your phone (ie what you have).
Use odin to flash back to froyo, or flash a gingerbread firmware that comes with bootloaders. (I would recommend going back to froyo first to make sure everything is ok, since flashing bootloaders is a bit risky, as messing it up can permanently brick your phone)
cobrasixtysix said:
Thanks for your input, right now i need all the help I can get, hadn't heard of heimdall before. I guess its one more thing I could try if all else fails. But right now I'm going to try a few more conventional things with odin, like flash a stock rom etc.
Click to expand...
Click to collapse
DSGE said:
After you unistalled Kies (or at least stop it) and installed the drivers , pick a stock rom with bootloader from Ramad collection http://forum.xda-developers.com/showthread.php?t=1102881 .
I prefer Odin 1.82.
If you still unable to flash your phone, please follow steps from this guide to see how can debrick your phone.
http://forum.xda-developers.com/showthread.php?t=1134975
Good luck
Click to expand...
Click to collapse
Ok, here's where I'm at:
For the sake of simplicity I will detail what gave positive results rather than a tirade of what didn't.
Uninstalled Kies, rebooted
As instructed, went to:
http://forum.xda-developers.com/showthread.php?t=1102881
downloaded: Odin v1.82
downloaded: Gingerbread 2.3.3 (Australia and New Zealand)
XWJVN/XXJVQ/XSAJV5/Sbl (CSC: XSA): Download (150 MB) (Build date: Sun Jul 10 11:30:54 KST 2011)
Loaded up Odin and followed instructions.
Flash went ahead as normal and I now have a working phone again, thanks to you DSGE, I'm a very happy man
So I now have Gingerbread 2.3.3 installed and running.
My only issue's now is, that.
1. Half my apps dont work now or force close even after a reinstall.
2. Some apps won't install at all IE; my fav launcher; Go Launcher
3. I no longer have root access so Rom Manager and Titanium backup wont work.
4. My Backup Pro, works after I rewrote the correct path to the External Sd, but do I want to do that just yet? and just how much data should I reinstate so I don't corrupt the new system?
What should I do now?
Install busybox?
do a hard reset?
Flash a different Rom that will work for me?
Thanks so very much for all the good advise.
Cheers
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
bigmadpete said:
First root the phone, then either a different rom, or format system and re install 2.3.3 or which ever u just installed, i think ure apps are not working due to the phone needing a wipe/reset and cache cleared from clockwork recovery
Click to expand...
Click to collapse
OK, latest update:
Everything is working fine including all my progs.
Like you say, I just need to root it now.
Can you point me to the correct files to root?
Thanks
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
bigmadpete said:
http://www.addictivetips.com/mobile...t-samsung-galaxy-s-i9000-with-a-single-click/
or
http://androidadvices.com/how-to-root-samsung-galaxy-s-gt-i9000/
Read carefully friend
Click to expand...
Click to collapse
Seems to relate to 2.1 to 2.2.1 didn't see any mention of 2.3.3. I'm afraid I'll stuff the phone if I use the old root files.

Download "yes," Recovery "no"

I was on Slim ICS and downloaded an update (2.8) which was to include a wifi toggle fix. After downloading directly to my phone, I tried to install it and it started looping (kernel then into recovery). I could not stop it in recovery. It would loop through the boot up and then I could see the recovery and but it said something about not being able to read zip file (corrupted download?). It just kept looping.
I was able to get Odin to work once (that is why I get the AT&T screen). Now, I can get Odin to recognize my phone but I cannot get beyond that. I have tried to reflash kernels that have worked before (assuming that I needed to start over). But Odin just sits there with the tar file in the pda section (for well over five minutes). Working on a Windows 7 machine (64-bit).
My phone's current status is that it is frozen at the AT&T screen (from the boog kernel without bootloaders - since I was on gingerbread before). I can get into download (volume buttons, plug in USB).
FYI, in the past I had flashed Continuum, Andromeda3, Mosaic IX, Fusion ICS, and Slim ICS, without a problem other than a soft brick or two that I was able to fix using Heimdall. (I am realizing I know/knew enough to be dangerous)
Am I "bricked" or can it be repaired.
Any direction as to what to do right now would be greatly appreciated.
Since I have yet to start playing with ICS this is just a guess on my part.
Since you are experiencing looping issues maybe you should go back to stock (without bootloaders). Flash one of the Odin/Heimdall one clicks so that your phone will get repartitioned back to RFS.
If that gets you working again you can reinstall SlimICS from that point.
Red_81 said:
Since I have yet to start playing with ICS this is just a guess on my part.
Since you are experiencing looping issues maybe you should go back to stock (without bootloaders). Flash one of the Odin/Heimdall one clicks so that your phone will get repartitioned back to RFS.
If that gets you working again you can reinstall SlimICS from that point.
Click to expand...
Click to collapse
I will try it again but I did try once with Odin and after about ten minutes, I cancelled the process (hopefully that did not add to my problems). It seemed to be hung up on the message, "Do Not Turn Target Off," but there was no process started.
Try a heimdall one click then. It might solve the issue.
Red_81 said:
Try a heimdall one click then. It might solve the issue.
Click to expand...
Click to collapse
Red_81,
Thank you!
Heimdall worked (http://forum.xda-developers.com/showthread.php?t=1300843)! Although I loaded the version that contains bootloaders, it actually flashes the kernel first and then give you the opportunity to flash again installing the bootloaders. Since the phone worked after the first flash, I did not bother doing a second flash. Now, back to Slim ICS!
Glad I could help. I had to sit down and read some info on SlimICS. I found through a couple of threads that one of the developer's post mentions a bootloop and going back to stock.
Heimdall packages tend to include the bootloaders, but only if you flash the second time and enable that option. According to the creator, it is much safer to flash them after flashing the ROM rather than flashing them first like Odin does.
Red_81 said:
Glad I could help. I had to sit down and read some info on SlimICS. I found through a couple of threads that one of the developer's post mentions a bootloop and going back to stock.
Heimdall packages tend to include the bootloaders, but only if you flash the second time and enable that option. According to the creator, it is much safer to flash them after flashing the ROM rather than flashing them first like Odin does.
Click to expand...
Click to collapse
Heimdall worked but I was left with two problems. One was that the Kernel installed by Heimdall did not have CWM in it, which I need to flash Slim ICS.
The second problem is that my computer will not recognize my device when I try to use Odin since Heimdall installs different drivers (I have read about how to covert to Odin and/or uninstall/replace the drivers, but it is hard to find that time given family and job obligations).
Since Heimdall did work to fix my original problem work, I found a package to install Apex 12.4 (http://apex.merseine.us/installation/) on my phone. I did this so I can have a working copy of CWM in order to re-flash Slim ICS.
Given the travails of the last two days, I may wait a battery charge or two on Apex (lots of customization but higher battery drain, which is why I went from Fusion ICS to Slim in the first place).
Anyway, thanks again for your help.
I know the feeling with family and job. You could try a different usb port and it may recognize. Using odin to add another cwm injected kernel is by far the easiest way. Of course, if you could find a ROM in the One Clicks master collection that was a heimdall with CWM already in it then you wouldn't have to worry about getting odin working again right away.
Red_81 said:
I know the feeling with family and job. You could try a different usb port and it may recognize. Using odin to add another cwm injected kernel is by far the easiest way. Of course, if you could find a ROM in the One Clicks master collection that was a heimdall with CWM already in it then you wouldn't have to worry about getting odin working again right away.
Click to expand...
Click to collapse
Believe me, I tried seven ports on three different computers with two different cords (my Kindle cord is actually the most dependable ).
I then searched for a Heimdall package that had CWM. It has a Talon kernel with CWM 3.0.x and I can get into recovery with the option of installing from my internal sd card.
I just have to wait for my nerves to settle (and this is a very fash gb rom and I have had no issues yet).

Forever stuck on Eclair

I received the Captivate from a friend of mine who complained that AT&T kept bricking his device through Kies and OTA updates. He never was able to update his device to Froyo. I unlocked the device to work on my carrier and then I tried Kies on 3 different computers (running XP and 7), and my device was stuck on the AT&T screen. Using odin oneclick, I got my firmware back to UCJF6 (stock Eclair). Since then, I've tried nearly every one click available (that hasn't been deleted off the internet), I've tried updating bootloaders and installing a separate kernel before flashing a rom in CWM:
(http://forum.xda-developers.com/showthread.php?t=1350266)
However, the device would not boot into recovery mode after following these steps:
(http://forum.xda-developers.com/showthread.php?=1953930).
Anyone have any suggestions? Never have I had such a frustrating phone, and that has some merit after owning a Motorola XT720.
Have u tried this one With Bootloaders http://forum.xda-developers.com/showthread.php?p=18370912.
Then use the regular Odin to flash the .tar file version of the KK4 Corn Kernel v7.0A that will give u CWM Recovery and u could proceed from there to a Dev's Rom.
Sent from my SAMSUNG-SGH-I777 using xda premium
Flashed Stock
I tried the Heimdall One-Click - Link to thread - by AdamOutler to try and get to Froyo -- Stuck at AT&T logo.
Flashed Stock
I tried the I897UCKF1 Android 2.3.3 Gingerbread with BL and then flashed the Kernel after the ROM using Odin v1.85 -- Stuck at AT&T logo.
Flashed Stock
I tried the I897UCKI2 Android 2.3.5 Gingerbread with Bootloaders [With CWM Injected Kernel from Boog] -- Stuck at AT&T logo
Am I doing something wrong here, or am I just unfortunate?
Try the one i posted. It is a Full Wipe Stock flash and should get ya goin.
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
Try the one i posted. It is a Full Wipe Stock flash and should get ya goin.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
The link you posted contained a good 7 different ROMS. I already had the Designgears Odin one click (Eclair stock with BL) downloaded and that's what I used before flashing anything else on that page. That ROM works and gets me back to stock 2.1 however that's the only ROM that has worked for me.
The link i posted was to my One Clicks in post #3 of that thread.
Sent from my SAMSUNG-SGH-I777 using xda premium
4-2ndtwin said:
The link i posted was to my One Clicks in post #3 of that thread.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I flashed using Odin with BL, then i flashed KK4 Corn Kernel v7.0A. Now I try restarting my device and booting it into recovery mode, and it doesn't work..? Recovery mode has never worked on this device unless I run an ADB command in CMD or using an app with root access.
I've been holding down all 3 buttons for 3-5 seconds and releasing, tried using the up button too the same way.
If I leave the device running, it stays stuck on the AT&T screen.
newbkilla said:
I flashed using Odin with BL, then i flashed KK4 Corn Kernel v7.0A. Now I try restarting my device and booting it into recovery mode, and it doesn't work..? Recovery mode has never worked on this device unless I run an ADB command in CMD or using an app with root access.
I've been holding down all 3 buttons for 3-5 seconds and releasing, tried using the up button too the same way.
If I leave the device running, it stays stuck on the AT&T screen.
Click to expand...
Click to collapse
Try reflashing corn kernel. And with gb bootloaders, it will always be the 3 buttons combo to get in recovery.
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
Try reflashing corn kernel. And with gb bootloaders, it will always be the 3 buttons combo to get in recovery.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
I swear, the phone will not allow me to boot into recovery mode let alone get passed the AT&T screen.
smokestack76 said:
Works every time for me if i power off. Hold down volume up and down and power. Wait for the att screen to go off and as soon as it comes back on the second time let go of the power button and continue holding both volume button down until you see recovery booting. It works the same with a usb cable plugged in for download mode.
Click to expand...
Click to collapse
I even tried this and I was unsuccessful.
Okay, I must be missing something here, because none of the oneclicks work except for designgears stock 2.1 ROM (I897UCJF6).
I'm going to start over and i hope someone here can guide me in the right direction:
I'm running stock 2.1 ROM, might as well be straight out of the box. I want to upgrade to 2.3 with GB BL so that I can flash whatever ROM i wish in the future. Kies Mini doesn't work, so that's out of the picture.
The One Clicks that 4-2ndtwin post a link to (both IlluminatedOne's and his own) do not work, meaning that I get stuck at the AT&T screen and it just pauses there. I have no problem getting into Download Mode or Recovery Mode while using the WORKING 2.1 I897UCJF6 ROM, however if I run ANY of the oneclicks other than I897UCJF6, i cannot boot into Recovery Mode.
I'm running Windows 7 64 bit, I have the 64bit drivers installed. I have tried Windows XP as well.
Sorry for the double post, but what in the world do I do?
Ok. Go here...http://forum.xda-developers.com/showthread.php?p=30840818
This is the full firmware for i897ucKF1 GB 2.3.3 with Bootloaders included. This is not a One Click. U will use the regular Odin and load the files in their cooresponding tabs of Odin. PDA file in PDA slot of Odin. CSC file in CSC slot. MODEM file in MODEM slot. Pit file in pit, etc. Connect in Download mode. Start. After this u can flash Corn Kernel and proceed.
Some of the Captivates don't like One Clicks. So maybe that is the deal with ur phone.
Sent from my SGH-I777 using xda premium
4-2ndtwin said:
Ok. Go here...http://forum.xda-developers.com/showthread.php?p=30840818
This is the full firmware for i897ucKF1 GB 2.3.3 with Bootloaders included. This is not a One Click. U will use the regular Odin and load the files in their cooresponding tabs of Odin. PDA file in PDA slot of Odin. CSC file in CSC slot. MODEM file in MODEM slot. Pit file in pit, etc. Connect in Download mode. Start. After this u can flash Corn Kernel and proceed.
Some of the Captivates don't like One Clicks. So maybe that is the deal with ur phone.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Well I did finally get it downloaded off of your dropbox and I used the Odin that came with the zip file and flashed all files given (CSC, Modem, PDA and PIT) and it's still stuck on the AT&T screen.. haha. Any other ideas?
Maybe this
I upgraded from stock Froyo 2.1 rooted to GB 2.3.5 with bootloaders using this package:
http://forum.xda-developers.com/showthread.php?t=1285616.
If you look here at post #3:
http://forum.xda-developers.com/showthread.php?p=18370912
it says this:
**Once u have the i897 Gingerbread Bootloaders, it is not necessary to flash bootloaders again. The i897 Gingerbread Bootloaders are backwards compatible, therefore you can flash Eclair, Froyo, Gingerbread, CyanogenMod, and MIUI Firmware/Roms without the bootloaders included, per the proper install instructions.**
Maybe your boot conflict is because you're trying to load the GB bootloaders again and there are 2 boot files or a glitched boot file. I'm no expert but I tend to go back to the simplest reason when I'm troubleshooting something that should work. Though it seems like a complete wipe and re-partition would delete bootloaders, maybe it doesn't from the sound of the above.
Try the package without bootloaders from here:
http://forum.xda-developers.com/showthread.php?t=1285616
It loads the rom and the kernal with CWM all at once with a full wipe and repartition.
I always remove the Sim and external sd card before flashing and disable my anti-virus when I'm in Winblows.
I hope SOMETHING works for you.
akone2 said:
I upgraded from stock Froyo 2.1 rooted to GB 2.3.5 with bootloaders using this package:
http://forum.xda-developers.com/showthread.php?t=1285616.
If you look here at post #3:
http://forum.xda-developers.com/showthread.php?p=18370912
it says this:
**Once u have the i897 Gingerbread Bootloaders, it is not necessary to flash bootloaders again. The i897 Gingerbread Bootloaders are backwards compatible, therefore you can flash Eclair, Froyo, Gingerbread, CyanogenMod, and MIUI Firmware/Roms without the bootloaders included, per the proper install instructions.**
Maybe your boot conflict is because you're trying to load the GB bootloaders again and there are 2 boot files or a glitched boot file. I'm no expert but I tend to go back to the simplest reason when I'm troubleshooting something that should work. Though it seems like a complete wipe and re-partition would delete bootloaders, maybe it doesn't from the sound of the above.
Try the package without bootloaders from here:
http://forum.xda-developers.com/showthread.php?t=1285616
It loads the rom and the kernal with CWM all at once with a full wipe and repartition.
I always remove the Sim and external sd card before flashing and disable my anti-virus when I'm in Winblows.
I hope SOMETHING works for you.
Click to expand...
Click to collapse
Thanks for the tips, however I'm flashing the stock 2.1 ROM with the BL, so even if I had the GB BL's flashed, wouldn't they be overwritten when I flash a the stock ROM? Nonetheless, I tried flashing without the BL, and it still froze at the AT&T screen..
What happens to ur phone doesnt make sense...idk. Honestly dont get it...
The only thing u can run is stock eclair... and no other plain stock will boot and run ?
Wish i could be of more help.
Sent from my SGH-I777 using xda premium
Have you tried getting into recovery when its stuck at the att screen and clear the cache or whatever other clearing you can do? Maybe CWM will be loaded. If it re-boots while holding the three button recovery method, that may be a good sign. Then at the re-boot, let go of the power button at the next att screen.
Does Odin give it a pass?
Are the roms your flashing rooted before you flash? In other words is Eclair rooted and then all others?
Pull the battery at the att screen?
Or go back into download mode and re-flash if that doesn't work.
I'm just guessing and the last 2 suggestions could be dangerous.......................I don't know.
Edit: Have you tried this?: http://forum.xda-developers.com/showthread.php?t=884364. It has a root file and a CWM file for Eclair. I tried the links to those and they did connect.
akone2 said:
Have you tried getting into recovery when its stuck at the att screen and clear the cache or whatever other clearing you can do? Maybe CWM will be loaded. If it re-boots while holding the three button recovery method, that may be a good sign. Then at the re-boot, let go of the power button at the next att screen.
Does Odin give it a pass?
Are the roms your flashing rooted before you flash? In other words is Eclair rooted and then all others?
Pull the battery at the att screen?
Or go back into download mode and re-flash if that doesn't work.
I'm just guessing and the last 2 suggestions could be dangerous.......................I don't know.
Click to expand...
Click to collapse
I've found that when applying the stock Eclair ROM, it never says "pass", it says reset--however it works and reboots into 2.1update1. My phone isn't rooted, it has been though. I've realized that some oneclicks say "Re-partition, Full Wipe". My experience is that my phone never enters recovery mode so my phone never wipes anything like the oneclick intends to do. I have not been able to enter recovery mode once I have flashed 2.2 or even 2.3 with or without bootloaders. Do you guys think that's the problem? And if it is, how would I enter recovery if the button combo doesn't work...?
akone2 said:
Have you tried getting into recovery when its stuck at the att screen and clear the cache or whatever other clearing you can do? Maybe CWM will be loaded. If it re-boots while holding the three button recovery method, that may be a good sign. Then at the re-boot, let go of the power button at the next att screen.
Does Odin give it a pass?
Are the roms your flashing rooted before you flash? In other words is Eclair rooted and then all others?
Pull the battery at the att screen?
Or go back into download mode and re-flash if that doesn't work.
I'm just guessing and the last 2 suggestions could be dangerous.......................I don't know.
Click to expand...
Click to collapse
Pulling the battery is not a great idea, it's only when it's "needed".
OP, I'm must say I'm quite confused myself, none of it makes sense.. Although, did you try flashing a 2.2 custom ROM?
I'm thinking you have some either bad or corrupted files/hardware keeping you from flashing but if you're able to flash a custom ROM, then there might be hope.
Also, a JTAG/box might work. They now flash stock GB and could *maybe* overwrite w/e in your phone that is messing with all your flashing.
BTW, it sounds like you are doing the wrong thing to get into recovery. Hold both volume keys, and then press the power button as you would to turn the phone on normally/until the screen turns on. Then, keep holding the volume buttons until you see recovery.
And which at&t screen are you stuck on? The very first one or the boot animation?
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
BTW, it sounds like you are doing the wrong thing to get into recovery. Hold both volume keys, and then press the power button as you would to turn the phone on normally/until the screen turns on. Then, keep holding the volume buttons until you see recovery.
And which at&t screen are you stuck on? The very first one or the boot animation?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
That's the strange thing, it will NOT boot into recovery when I flash say KK4. I hold the volume buttons for over 30 seconds, and it just stays at the AT&T screen. It gets stuck before the boot animation, I never see it when I try to flash anything 2.1+. I have booted into recovery mode before, so I know that I am doing the button combo properly.

Categories

Resources