[Q] Questions about preventing a second hardbrick - Captivate Q&A, Help & Troubleshooting

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

Related

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

[Q] Just permabricked my cappy, a few questions related

How did I permabrick my cappy?
Flashing with Odin, I restored to the Rogers stock 2.1 firmware, however the phone refused to boot past the rogers loading screen. I re flashed the phone a few more times playing with the flashing options of Odin, using alternate stock .tar files with no luck. My final flash caused the phone to get into such a state that going into download mode no longer worked, as well as it failing to boot. Luckily Rogers warranty has replaced the phone for me
Any ideas on what caused the phone from booting into the OS, so I don't do it again?
Additional Questions
1. The new cappy given to me through the Roger's warranty has stock 2.2 loaded on it. Is there anyway to back up this firmware to a tar file for later use? If so, how can I use it in conjunction with Odin to restore to stock 2.2?
2. Do I HAVE to restore the phone to 2.1 eclaire firmware before loading a custom ROM on it? Or is it possible to root / reboot into clockwork recovery and successfully flash from stock 2.2 froyo?
3. In my past experiences, after restoring to Rogers 2.1 stock firmware through Odin, kies no longer recognizes the firmware currently loaded on my device... Is this normal? Any fixes? Is there anyway to get kies to recognize the firmware such that it would be able to upgrade or even wipe the phone with the standard stock firmware? I ask this because on the new kies I see the function "emergency firmware recovery".
did you brick flashing the NEW stock 2.1 thats in my sig? or the old one that messed alot of people up in a few ways?
#1 yes but unsure how to make, it would be used like any other tar and odin.
#2 from what ive seen sofar, 2.1 wont boot on phones that came with 2.2, but it was a noob i was talking to that had the issue. the only thing you run into is having 3e recovery and needing the fix before you can load clockwork on 2.2. all is good from there.
#3 normal. no fix. keis sucks
Trusselo said:
did you brick flashing the NEW stock 2.1 thats in my sig? or the old one that messed alot of people up in a few ways?
Click to expand...
Click to collapse
Yeah it was from the one in your sig (linked in the stickies I believe).
#2 from what ive seen sofar, 2.1 wont boot on phones that came with 2.2, but it was a noob i was talking to that had the issue. the only thing you run into is having 3e recovery and needing the fix before you can load clockwork on 2.2. all is good from there.
Click to expand...
Click to collapse
Thanks for the link! and the prompt response
Are there any .tar files floating around for the Rogers froyo 2.2 that address the warranty / logo issues? (search function seems to be broken).
Any stock 2.2 rogers .tar files for use with Odin floating around the board?
What is your recommendation with regards to proceeding with flashing? Should I try to flash 2.1 on the phone with 2.2 preloaded, or just go the 3e clockwork recovery fix route?
Any other pieces of reading you might be able to point me towards in this regard?
I would suggest adding your locale to your profile for future reference, as restoring an I896 is different than an I897.
There is also another way to get clockwork on your phone.
Use Odin and just flash the speedmod kernel .tar from here: http://forum.xda-developers.com/showthread.php?t=893880
I have done it this way since I got my phone and have yet to run into a problem. This works with 2.2 only.
2.2 odin flashable (NO ATT boot fix) and cwm upgrade from 2.1 zip. are here
http://forum.xda-developers.com/showthread.php?t=905042
the person i mentioned before that couldnt get my 2.1 stock to boot on his 2.2 ... he did fix the att boot by un-successfully flashing my 2.1 then the 2.2 overtop, then it booted correctly WITH the i896 bootscreen, basically double flash.
i will contact the creator of the updated 2.1 and see if he can do it to 2.2 as well.
feel free to attempt to flash 2.1 to confirm weather or not it does work on a phone that comes with 2.2. as this isnt confirmed. also note any new notes on the 2.1 stock rom page.
oh and speaking of the updates on that page...
theres the fix for the getting stuck at rogers bootscreen on first boot after flash... (the problem you had)
reboot into recovery and clear data and cache, reboot. done.
sorry its late...
Trusselo said:
oh and speaking of the updates on that page...
theres the fix for the getting stuck at rogers bootscreen on first boot after flash... (the problem you had)
reboot into recovery and clear data and cache, reboot. done.
sorry its late...
Click to expand...
Click to collapse
That's common. Everytime I flash the gf's Galaxy Spica, that's the first thing you have to do with it is clear the data and cache. I just do it instinctively now.

Flashed from 2.3.3 back to stock with Odin3 and lost 3button!

Looking in the About phone area it says my Kernel is 2.6.29 [email protected] #2 which i'm assuming isn't a stock Kernel. I can't get into download mode or recovery to save my life. Any good ways to get it back? Everything I've tried doesn't work. I'm curious about this android sdk adb access thing but I haven't been able to search about it. Thankfully my phone works right now but the only way i know how to flash stuff it through the key method.
Any links to a tutorial about this adb thing? ALso, where to download the android-sdk?
Thank you thank you thank you!
wrong section
WRong thread but dont wanna flame... : D
This happens some time, just flash this and you will have 3 button recovery again.
EDIT: STUPID ME, just realized you cannot get into recovery... Well use ADB to get into Recovery then flash that
Android SDK - http://developer.android.com/sdk/index.html
Make sure u have Java JDK installed! - http://www.oracle.com/technetwork/java/javase/downloads/index.html
Sorry idk about a good ADB tutorial though
That is a stock kernel.
1. This is a stock kernel
2. Which 3-button combo did you try? It can be either +-USB or -Power
amtrakcn said:
1. This is a stock kernel
2. Which 3-button combo did you try? It can be either +-USB or -Power
Click to expand...
Click to collapse
I can't get into download mode or recovery mode. I've flashed quite a few different roms since i've had this phone and never had a problem. For some reason this time when I went from MikeyMike01's GR-12 2.3.3 back to stock with Odin3, I lost the ability to use my volume buttons + power to go anywhere. I was trying to install CWM to put Serendipity 6.4 on my phone because the other one was having some weird issues.
Thanks to everybody else for the links I'll try them when I get home... work is blocking the android sdk download website. I'll update in a bit with success (hopefully).
If all else fails, you could extract the 3 button fix posted above, and odin.
No buttons working? Pull batt, open odin, insert usb, reinsert bat, and it should go into download mode..
illavbill said:
Looking in the About phone area it says my Kernel is 2.6.29 [email protected] #2 which i'm assuming isn't a stock Kernel. I can't get into download mode or recovery to save my life. Any good ways to get it back? Everything I've tried doesn't work. I'm curious about this android sdk adb access thing but I haven't been able to search about it. Thankfully my phone works right now but the only way i know how to flash stuff it through the key method.
Any links to a tutorial about this adb thing? ALso, where to download the android-sdk?
Thank you thank you thank you!
Click to expand...
Click to collapse
skip all that .... if it boots upto OS and you just have no 3 button..... Use This
http://forum.xda-developers.com/showthread.php?t=944418 and flash 3 button with it. Access to recovery or dl mode not needed. Just be sure to follow the instructions with the tool. It works. Simple.
Moved to proper forum.
illavbill said:
Looking in the About phone area it says my Kernel is 2.6.29 [email protected] #2 which i'm assuming isn't a stock Kernel. I can't get into download mode or recovery to save my life. Any good ways to get it back? Everything I've tried doesn't work. I'm curious about this android sdk adb access thing but I haven't been able to search about it. Thankfully my phone works right now but the only way i know how to flash stuff it through the key method.
Any links to a tutorial about this adb thing? ALso, where to download the android-sdk?
Thank you thank you thank you!
Click to expand...
Click to collapse
before i tell you an easy way to get into recovery, was this odin "oneclick" or did you have to add a .tar file to a "PDA" slot and perhaps a .pit file and others? this is highly important because 3-button fix only flashes the secondary bootloader. if you still have 2.3.3 bootloaders this will brick the phone! there needs to be an update to the 3-button fix to flash both bootloaders. a quick test if you have 2.3.3 bootloaders is if the phone says "galaxy s gt-i9000" you may have 2.3.3 bootloaders on the phone. on 2.3.3 this screen is part of the bootloaders as well as the param.ifs, flashing 2.1 without the bootloaders will show the i9000 splash before the att param.ifs splash
if it was odin oneclick you are safe to flash a 3-button fix. if it was odin full you may still be on the 2.3.3 bootloaders and dont have button combos due to some incompatablility with the phone, i saw this once. please use odin oneclick first then see if it still needs 3-button fix.
if you need to reflash with odin "oneclick"
look up "adb" make sure you know how to manually install drivers. there are links in posts above
if you did flash with oneclick then you can also root and use rom manager to reboot into recovery. then flash 3-button fix via update.zip. search dev section for designgears' 3-button fix, there is a update.zip version.
why do u need the three button here...just hold down the volume key and the power button to get in to the recovery. worked for me.
Dani897 said:
before i tell you an easy way to get into recovery, was this odin "oneclick" or did you have to add a .tar file to a "PDA" slot and perhaps a .pit file and others? this is highly important because 3-button fix only flashes the secondary bootloader. if you still have 2.3.3 bootloaders this will brick the phone! there needs to be an update to the 3-button fix to flash both bootloaders. a quick test if you have 2.3.3 bootloaders is if the phone says "galaxy s gt-i9000" you may have 2.3.3 bootloaders on the phone. on 2.3.3 this screen is part of the bootloaders as well as the param.ifs, flashing 2.1 without the bootloaders will show the i9000 splash before the att param.ifs splash
if it was odin oneclick you are safe to flash a 3-button fix. if it was odin full you may still be on the 2.3.3 bootloaders and dont have button combos due to some incompatablility with the phone, i saw this once. please use odin oneclick first then see if it still needs 3-button fix.
if you need to reflash with odin "oneclick"
look up "adb" make sure you know how to manually install drivers. there are links in posts above
if you did flash with oneclick then you can also root and use rom manager to reboot into recovery. then flash 3-button fix via update.zip. search dev section for designgears' 3-button fix, there is a update.zip version.
Click to expand...
Click to collapse
I used Odin oneclick to reset it to stock. I've been moving this weekend so I just left the phone on 2.1 but today at work i'll try the method you mentioned above. I didn't even think about rom manager to reboot to recovery i'll try that first. I was trying to reboot the phone into recovery so I could install CWM. Sounds easier than the other methods.

[Q] im lost????

i'm trying to figure out how to just get to where i can flash a rom, my phone is sgh-I897 running 2.2 froyo.uckb1
if i have read some of the stickys right i need to use odin to flash back to stock or flash a different kernel is this correct? to get around the 2e-3e sig.verif.
could someone please point me in the right direction? from what i can tell there are alot of ways to do this or maybe not??? which is the safest or shortest..
thanks to any that can help me out.....
Yes, you need to get past the stock 3e recovery before you can do anything.
Method 1) simple, easy. Use the script from the 3e sticky in general section (post 3 from TRusselo) to patch from your computer. Then you can flash CWM (through update.zip or ROM manager on the market if you are rooted), and flash any number of FroYo ROMs. NOTE: you cannot flash a GB ROM from FroYo.
Method 2) kill fly via sledgehammer, possible risk, and 3-button problems later depending on build number of phone. Put phone in download mode (power off, hold volume up and down, plug in USB) flash via Odin back to 2.1 stock. (Different Odin will fix 3button if you know it will be an issue) then flash CWM, and flash FroYo ROM desired. Odin *can* brick your phone if something goes wrong; cable unplugs, battery removed, etc.
Im sure there are more ways, but those are the most common and easiest.
Recovery is in the kernal, so a new kernal will fix, but you have to replace or mod the 3e recovery before you can flash a new kernal.
My suggestion is the windows script file, its easiest, and can't brick your phone.
Sent from my Captivate running Continuum 5.5
quarlow said:
Recovery is in the kernal, so a new kernal will fix, but you have to replace or mod the 3e recovery before you can flash a new kernal.
Click to expand...
Click to collapse
this is false. you can flash a kernel in ODIN and completely bypass 3e recovery altogether.
there are several kernels that are ODIN ready......
Read the before flash posts, then read them again. It will save you a ton of headaches down the road. And almost every rom has step by step instructions-read these next.
Please search before opening a new thread. All of this is in the threads. On a side note. A fast way is not the safe way, and the safe way is not fast. Think about what you are doing, do you really want to rush it?

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

Categories

Resources