Database Develop

[Q] Can't Flash Stock Rom + Terrible Battery Life

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.

[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

Lost recovery access after using odin one click?

I was just wondering if anyone else lost three button recovery access when flashing back to eclair with odin 1 click. I had stock 2.2 and used odin to get to 2.1 and I got into recovery no problem, I put cognition 4.3 on. Then used odin again to go back to eclair and it went fine but after that I couldn't get into recovery with the three button method. I was just wondering if that happened to any one else and why it did that. I just like to go back to stock before I flash new roms and now I have to take extra steps to get CMR back on. Thanks and if I sound stupid sorry I am a noob
Sent from my SAMSUNG-SGH-I897 using XDA App

Check out mobiletechvideos. He has a download to fix this.
Sent from a super smooth captivate running andromeda

CWM Help?

So, just switched out my captivate because my warranty was still in effect. Rooted etc etc. But I remember installing CWM with rom manager to begin flashing my first rom back in the day.
But anywho, I have installed ROM Manager, clicked to flash CWM but when I go into recovery (vol + - & Power) All I get is the samsung one. (Blue text) and I only have the options to reboot, install packages, clear cache or wipe sd card.
Can anyone offer any advice?

^ Try reinstall packages. U may have to do it twice.

Gotta install the update.zip with install packages but you have signed bootloaders if you're on stock froyo. Odin to 2.1 and install cwm from there. You can find the update.zip for cwm on the cappy forums and just put that on the root of your internal memory to avoid using rom manager. Don't even have to root to flash.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

Hmmmm do you have the stock odin pit file/pda or is the old school odin where you couldnt even do that shoot you right back to 2.1?

^ If u want to go back to Stock Eclair...use the first link in my signature below.

I typically use Odin jf6 one click rev0 from designgears. Its still on the forums I believe but might be dead link. Just make sure it has the pbl and sbl. If you are worried I can upload the one I have used for the past 9 months without fail( but ffailure is always possible, just be sure to follow directions and you should be alright. ) alternatively there is a guide to get to stock jh7 on the forums using the Odin that you have to manually select files for. Should be an easy search. I believe people consider this safer for the newer builds but I used oneclick on my 1010 tons of times and have used it once on my 1012 no problems.
Sorry for the long post hope I helped
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

You all have helped. Thank you so much. Running MiUi again and still loving it.

[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...