Related
Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
ApplCobbler said:
Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
Click to expand...
Click to collapse
I feel your pain. Been there, done that. Although your process of bricking reminds me of a more sophisticated approach....lol....mine was out of total complete noobness.
Question:
1) Can you manually boot into download/ recovery manually using 3-button combo? If so you have hope (meaning your phone is basically "un-brickable").
-Bet that made you feel better huh?
-If you can't use 3-button to go into either modes, then you are in the same boat as i was. Hope you are still within your 30 days, or at least warranty. One way to tell if you can/ can't go into either modes is to check your "Batch #."
a) remove battery
b) look below your Serial Number
c) if your Batch # = 1007 = You are safe
d) Batch # = 1008 = good luck
2) When you say Brick, do you have the unfortunate "Phone (!) PC" screen? If yes, then its a "soft brick." If No, then its a "hard brick." I would start to worry.
3) According to your post, it sounds like you have the Regular Odin and NOT the One click version, correct? If you have regular Odin, i would at least try the One click. Regardless, both versions should be able to get you back to stock (JF6), but we already know how well your current version Odin has gotten you.
If you need help, there are TONS more knowledgeable people here in the Captivate forum than I. They should be able to help.
Good Luck!
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Stop trying to flash Froyo. Flash back to stock then master clear. Then go read the threads in the development section of the forum before flashing anything. The fact that you tried to apply Voodoo to Froyo and you tried to use one click lagfix on Froyo shows you haven't read and don't know what your doing. You corrupted something by flashing incompatable stuff, flash back to stock and master clear for now. Read a bit and then flash Froyo.
ApplCobbler said:
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Click to expand...
Click to collapse
LOL . I as well. I know enough to be dangerous.
Now, on to business. If you actually read what Rhiannon has posted for you, and click on the actual link itself, you will realize that the version of Odin you are using (yes the one click) is NOT the correct version for flashing back to stock (JF6/ Eclair.....NOT froyo). Remember, if all else fails....."The One must return to the Source...." <-----Plus 9,000 to whoever can guess where thats from.
Obviously your phone falls within the 1007 since you have the Luxury/ Advantage of manually entering Download/ Recovery mode....i wish i did.
Rhiannon224 said:
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
Click to expand...
Click to collapse
Well Said!
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Click to expand...
Click to collapse
I see you are still on Cog 2.2 B5......dont care for 8 or any of the new ones? Or Sheps? What's your story?
Mine is simple....Patience. lol
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
Click to expand...
Click to collapse
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Rhiannon224 said:
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Click to expand...
Click to collapse
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
spartan062984 said:
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
Click to expand...
Click to collapse
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
ApplCobbler said:
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Click to expand...
Click to collapse
Again, sorry if I sounded harsh, i am just trying to help you get out of the mess you're in. You can flash Froyo in the future you just need to learn about these ROMS and fixes so you don't have these kinds of headaches. I will stop repeating now. i really hope this works. I know your stressed and wasn't trying to give you a hard time, I just thought you were missing something and I am from NY and we are pushy Let us no if you get it working.
I have made some mistakes along the way too and it was because I didn't read the instructions clearly so I do understand how you felt.
Rhiannon224 said:
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
Click to expand...
Click to collapse
""Sory to hijack the thread""
I started it. No worries. I too would love to have voodoo. So far, with stock OS, ext2 + OCLF seems to work for me....for now. Keep in mind that i too would like to have the functionality of a Phone. That was my intention in the first place...lol.
As you are about to see, I'm new to this.
I have been attempting to root my Captivate. I have tried Galaxy One Click Root and Super One Click 1.7, among others.
My phone won't enter recovery mode. I have tried to install z4root, which the phone blocks. I've tried using sideload wonder machine, which doesn't work either.
I downgraded to 2.1....nothing. Reloaded 2.2....nothing.
Any advice would be helpful at this point, and please be specific, as I am slightly retarded.
It its rumored that Odin one click to jf 6 will actually get rid if the recovery/ download modes, maybe try flashing a cognition ROM
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
ryanmahan said:
It its rumored that Odin one click to jf 6 will actually get rid if the recovery/ download modes, maybe try flashing a cognition ROM
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
That's not a rumor, it's a fact. Does not happen with all models.
What about full odin to jf6? I personally like to use odin every so often to master clear.
It would explain why superone click wouldnt root my phone lst time i master cleared, too. Ended up installing cwm and flashing straight to rom(which took care of rooting and 3rd party apps)
mrhaley30705 said:
What about full odin to jf6? I personally like to use odin every so often to master clear.
It would explain why superone click wouldnt root my phone lst time i master cleared, too. Ended up installing cwm and flashing straight to rom(which took care of rooting and 3rd party apps)
Click to expand...
Click to collapse
As I said, I'm slightly retarded. Do you know of a forum with instructions for doing this? Everything else I've tried has just caused a face to appear on my phone's screen laughing at me.
When you use super one click, did you enable usb debugging?
Sent from a place my wife doesn't know about
The captivate is actually an extremely easy root process...
Download this file update.zip
Put it on your internal SD card (internal Memory) not your SD card you can remove
Turn off your phone
Once off hold both volume up and down and hold power until you see the AT&T boot screen then let go of all 3 buttons. You should see recovery mode soon. Select Reinstall Packages, congratulations you are now rooted.
Is that the modded cwm? I think he said he was on 2.2. Regular cwm won't work with froyo(signature verification errors). There is a modded one somewhere on this site that either replaces 3e, our fixed sig on cwm.
Sent from a place my wife doesn't know about
I think he downgraded to 2.1 again which is what you'll need to be on to use the method I described.
jayjr1105 said:
I think he downgraded to 2.1 again which is what you'll need to be on to use the method I described.
Click to expand...
Click to collapse
I'm running 2.2
1-Downloaded and installed file update.zip to internal sd. Turned off phone. Tried to enter recovery mode. Got blank screen, att screen, blank screen, att screen, blank screen, etc etc.
2-Tried to install z4root. Blocked by phone. Tried to use sideload wonder machine, which can't detect the phone (in usb debugging mode and mass storage (tried both))
3-Tried Super One Click, which ran but did nothing.
4-Flashed to 2.1 and factory reset. Tried (2) again. Failed. Tried 1-3. Failed.
5-Flashed to a different version of 2.2. Started over. Failed.
I've been using some of the mobile tech videos, but everytime I get to the "Eureka!" phase, my phone just laughs at me.
use odin full version to flash speedmod kernel on 2.2, i even do this on 2.1, but on 2.1 you need the .zip file on the sdcard before you start because the phone will not boot with a 2.2 kernel, only enter recovery.
once on speed mod kernel you can either root and flash a kernel for att roms or flash a new rom without the need to root, the new rom will be rooted.
if you are on 2.2 you will need a computer one way or another, flashing back to stock can be a pain for those with the 3 button problem and it is way more time consuming than flashing a kernel, i have never used the tools out there but i don't know of an easier way than flashing a kernel via odin, especially if you intend to flash a 3rd party rom. also any time you flash a sbl.bin or boot.bin can be a dangerous situation. bad flashes that break the boot loaders aren't common but it causes enough "omg i bricked" threads to keep me from recommending it. there is a odin one click with a 3 button fix, if you use that once it will be fixed untill you flash a rom with odin that changes the bootloaders again. im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
you must not have the right drivers installed.
2.2 cannot be rooted by using an update.zip....you will need to get your drivers working and adb seeing the device....
sharp1114 said:
I'm running 2.2
1-Downloaded and installed file update.zip to internal sd. Turned off phone. Tried to enter recovery mode. Got blank screen, att screen, blank screen, att screen, blank screen, etc etc.
2-Tried to install z4root. Blocked by phone. Tried to use sideload wonder machine, which can't detect the phone (in usb debugging mode and mass storage (tried both))
3-Tried Super One Click, which ran but did nothing.
4-Flashed to 2.1 and factory reset. Tried (2) again. Failed. Tried 1-3. Failed.
5-Flashed to a different version of 2.2. Started over. Failed.
I've been using some of the mobile tech videos, but everytime I get to the "Eureka!" phase, my phone just laughs at me.
Click to expand...
Click to collapse
sounds like you need the 3button fix first. there is an odin stock rom+3button fix, it should take you to 2.1 but you will get recovery mode. if that fixes the recovery mode 3-button combo and the phone boots you can put the rom of your choice on the sd card, then odin flash speedmod kernel and flash the new rom, warning the phone doesn't boot a 2.1 rom with speedmod kernel, i only do this as a faster way to get into cwm recovery, only do that if you intend to flash a rooted rom from 2.1.
Dani897 said:
use odin full version to flash speedmod kernel on 2.2, i even do this on 2.1, but on 2.1 you need the .zip file on the sdcard before you start because the phone will not boot with a 2.2 kernel, only enter recovery.
once on speed mod kernel you can either root and flash a kernel for att roms or flash a new rom without the need to root, the new rom will be rooted.
if you are on 2.2 you will need a computer one way or another, flashing back to stock can be a pain for those with the 3 button problem and it is way more time consuming than flashing a kernel, i have never used the tools out there but i don't know of an easier way than flashing a kernel via odin, especially if you intend to flash a 3rd party rom. also any time you flash a sbl.bin or boot.bin can be a dangerous situation. bad flashes that break the boot loaders aren't common but it causes enough "omg i bricked" threads to keep me from recommending it. there is a odin one click with a 3 button fix, if you use that once it will be fixed untill you flash a rom with odin that changes the bootloaders again. im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
Click to expand...
Click to collapse
Do you have a suggestion for a stable rom? I don't want to get to the point where I've got it working and throw a terrible third party on it. I'm just looking for device speed and controll over all apps, especially bloatware.
all of the available roms are stable. to be honest TiBu will remove bloat if you want it to.
Try them all and see which one you like. Pretty much all of the custom roms are better than stock. If you like to stay near stock but run more optimized, see Cognition. Otherwise see which one you like more. It's not a hard process if you read up on it.
sharp1114 said:
Do you have a suggestion for a stable rom? I don't want to get to the point where I've got it working and throw a terrible third party on it. I'm just looking for device speed and controll over all apps, especially bloatware.
Click to expand...
Click to collapse
it is hard to go wrong with cognition which is a stock rom with some mods and bloat removed and tethering enabled, that will have the proper kernel and modem for the captivate which for me has great call quality, also the disadvantages of not having hsupa are overblown.
there is also andromeda which is the rom from the armani captivate and is well polished and complete, has some of the more useful samsung apps. this can be used with a 2.2.1 kernel ported from the i9000 for a slight speed boost (shows in benchmarks, may not be detectable in user experience) this has hsupa and is designed for the captivate
i9000 ports are newer 2.2.1 versions and all of the features work now so you may want a newer firmware version from one of those..
there are many 2.2.1 i9000 roms that are fully functional. that is more a matter of feature set and theme preference it is hard to say one is better than the other. id say for stable the speedmod kernel is about the best on an i9000 port, for experimenting with overclock or undervolt i hear that the kernel with paragon is awesome.
now it is odd that you say you flashed a different version of 2.2 but cant get into recovery, was that in odin? can you get download without adb commands?
Dani897 said:
im not sure if there is a .tar stock rom for odin without the bootloader but that would be a good idea if there isn't.
Click to expand...
Click to collapse
Use this method to flash back to stock. Supposed to be much safer that doesn't mess with the bootloader files. I have been using it for about 3 weeks now to flash back to stock. You CAN however still use the one click odin to master clear once you have flashed back to stock.
Back on topic... I would flash back to 2.1 using the above method and master clear to start fresh with this issue. Once that is done look for mobiletechvideo's 3 button fix video on youtube. But even if you have 3 button issues the Galaxy S one click root program should still get you into recovery. It doesn't always succeed in copying the update.zip file to the internal SD card but you can do that manually and just use the program solely to get into recovery. Make sure you have USB debugging on. After the stock flash and master clear it is off by default and samsung kies is on. You might want to invest in a Jig also since you have 3 button issues, it may save you hide someday.
As far as a good rom goes. Really all the 2.2.1 roms are pretty stable and fast. I'm currently using Continuum 4 with the paragon kernel and it floats and sips battery. If you like the stock look you can use cognition. If you like the green themed gingerbread look you can use Phoenix, Serendipity, Firefly, or Paragon which is my personal fav but hasn't been updated in a month.
Anyways good luck. I'm sure you'll figure it out.
oops, got double posted somehow
Thanks for all your advice and help. I finally got it rooted.
I've tried Cognition 4.3 and Paragon, both of which I liked. I like the appearance of Paragon, but the optimization just doesn't seem to be there. Cognition is great for customization, but I the appearance is just to 'stockish' for me, if that makes sense. Something in between would be nice. (Ideas?)
I plan to try Phoenix Unleashed, but i can't get it to download.
The reason why the programs are having a hard time seeing your cappy is because you need the Serial COM driver available only by installing Samsumg's software: Kies Mini... don't run the program just install it. Once you do this Odin and the Wonder Root program can see the phone. I had this issue.
Hello astute folks on XDA!! My name is Brian and i'm a flash-a-holic. I'd like to share with you my experience that ultimately lead to me fubaring my beloved captivate.
I've flashed everything under the sun on this phone from roms to different kernels to modems. You name it, i flashed it with great success (after researching, never flashed on a whim.) UNTIL... Yesterday.. lol.. I was running a leaked 2.3.4 gingerbread rom and i noticed the problem first starting while trying to connect my phone to my computer via usb. The two didn't communicate when for the last 6 months, every single time i plugged in, my computer and phone recognized each other every single time. So that was my first clue that something aint right. Next thing i did was power the phone off. Went to turn it back on and NOOOOPPPEEEEE!!! Nothing!!!!! Held all three buttons and the little grey circular icon came on (the one that is initially in the battery icon when the phone is powered off but it's plugged in) but immediately shut off. Nothing turned my phone back on, but i was able to get into download mode. So thats what i did. I used odin3 oneclick to go back to stock eclair thinking that that will start everything all over, erase the bad/corrupt files and so forth. Flash was successful. Got back to stock eclair and got stuck in MTP initialization (you know, the screen in which you get if your debugging mode wasn't checked.) But it hung on that screen. No buttons would allow my to exit so, I pulled the battery. Then, the same damn thing.. I could NOT get the phone to power back on. Lesson learned for me. (today i learned that going back to stock is NOT a fresh install.) Used odin again, but this time unplugged my cord BEFORE i got to the eclair boot screen. As i'm peering at this home screen, i noticed that my USB connecting notification was flashing on, off, on, off yet my cord was unplugged. At this point i called tech AT&T tech support because i knew i was screwed. (i told them i tried to update to the 2.2 they provided on website and the phone cut out, lol).. I spent an hour on the phone and got no where other than determining that my phone is farked and they are gonna send me out a replacement (which will take 4 to 6 days) because luckily it was under warranty still. Tech support couldn't get my phone to turn on, but i could, lmao.. So... here i am stuck with a phone where usb debugging mode is buggin out!!!!!!! To wrap this story up, what i did was got back into download mode and flashed gingerbread bootloaders and a kernel and voila!! So long as i don't turn my phone off, i have a fully operational phone until my new cappy arrives in the mail in 4-6 days. (Dicks.. If i had been ordering a new phone, i'd have the option for next day shipping but thats another story.)
TLDR: Flashing too much will get you in a bad situation. Stick with a rom/modem/kernel setup that suits your needs because your next flash could be your last depending on the components in your phone.
EDIT: MAKE IT KNOWN THAT I HOLD NO ONE RESPONSIBLE OTHER THAN MYSELF FOR THE FUBARING OF MY CAPPY!!!!!!!!!!
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Things break...and ppl make mistakes... I'm still trying to figure out which one happened in your situation.
Sent from my SGH-I897 using XDA Premium App
That's a common hardware issue with the captivate. Happened to me twice. Its just the USB port spassing out thinking tthe cable is constantly getting plugged in and unplugged and freezing tthe phone with its craziness. Both times it was replaced under warranty. I'm paranoid it'll happen again now that I'm out of warranty.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
speedy_11 said:
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Click to expand...
Click to collapse
Oops, my bad!! It needs to be somewhere as a precaution to those that think flashing is completely harmless
EDIT: upon further contemplation, it really is a question of what went wrong
Sent from my GT-I9000 using XDA Premium App
I am a flash addict as well
i have flashed all froyo based roms on my cappy !
Can anyone confirm that excessive flashing may risk my phone?
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Thanks for the quick response....!
now i dont need to worry
xijar said:
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I'm 99% sure my board failed because of cheap, unreliable components. However, that 1% is still in the back of my mind that it could have been from something I flashed. I suppose I'll never know.
Sent from my fubared, soon to be replaced cappy running GT-I9000 gb rom using XDA Premium App
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Accidental post. Please delete.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
xijar said:
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
As I started before, the phone is fully functional with gingerbread other than the occasional usb flickering..Only problem I have with it really is if I turn the phone off, it won't turn back on unless I hold power and volume up, enter cwm and then select reboot now.
Before I send it back, I'll odin back to jf6 first with oneclick. Without cwm on the phone, lol, it absolutely won't turn on by just using the power button. I made sure of this before I even called the warranty department and explained my dilemma
The nice thing is that I can use the phone while I wait fire the new one to arrive AND I can flash and experiment with everything now without worries!!!
Sent from my fubared chappy running GT-I9000 GB rom using XDA Premium App
I am also a flash-o-holic and I think that if you flash with odin lots with repartition checked or are enabling/disabling voodoo lots, it can mess up your phone. Has happened to me twice, just sent my phone today for the second time. Both times this happened to me it happened when successfully flashing back to stock with 512.pit and repartition checked. On boot up it stalls at the "S" screen and never goes past it and in recovery I get some errors like:
error: can't mount /dev/block/mmcblk0p1
error: can't mount sdcard
I flashed many different firmwares with different pit files and different android versions but all conclude the same, stuck at the "S" boot screen.
I have determined that the partition tables were messed up and I tried to fix it by putting parted on my phone and trying to repartition it from the shell. Both times I get the "unable to write to /dev/block/mmcblk0 - I/O error!" Also, from CWM Recovery I try repartition sdcard but it also comes up with an error. The last time I sent it into Samsung repair they had to replace the main board to get it working properly again. Think it is definitely a good idea to find a rom / kernel / modem you are happy with and stick with it for a while.
I thought I knew what I was doing...
I've read and read and read. Thought I had all my ducks in a row. Thought I had everything figured out. But now I have a bricked phone.
I bought my Captivate refurbished from AT&T about 3 months ago. The mfg date is listed as 1011. It came with Froyo. By the third day I had it rooted and Cognition installed. Loved it. But lately it was starting to freeze up, lag, etc. so I decided to install Serendipity.
I followed the directions in the famous How-To thread here.
Odin reported success, but now my phone is stuck in bootloop. None of the tricks for getting it back into download mode worked.
I went to Radio Shack and bought some resisters and made a jig. Now, I can successfully get back to download mode now, so I'm still holding out hope!
I tried Odin again, but got the same result.
My warranty is up in 3 days. Called warranty place today and they won't do anything unless the phone can get to a recovery screen (probably their way of knowing when people have been doing what I've been doing!). Which it won't. I can put it in download mode with the jig. Otherwise, I just get the boot loop.
I have been stressing over this for the last 15 hours. I can't sleep. I've read countless forum posts. Now I find that Odin with Froyo and phones dated from 1008 and above is tricky. How did I miss that before? I've read so much, seen so many threads with people saying "do this" followed by "no don't do that" followed by "that's always worked for me" but it's not working for ME. At this point I'm confused and scared and just hope somebody can point me to instructions for getting a usable phone again.
EDIT: I see I misspelled "Odin" in the title of the thread... tried to edit it but I can't. Sorry.
That guide has not been updated for 2.3 roms. you should follow the instructions that were written by the rom maker, for the rom your trying to flash
This looks relevant http://forum.xda-developers.com/showthread.php?t=995143
- For unbricking
AdamOutler, is working on a unbrick method. http://forum.xda-developers.com/showthread.php?t=1206216
Or mobiletechvideos they have an unbricking service for 50$
(side-note if you have read and read like you said you should have had come a cross some of this.)
Which Cognition were u on ? And which Odin did u use ?
And since u can still get into Download mode u can relax a little, cause that's a good thing.
Lol relax If the phone shows any signs of life, that means it can be fix (usually). Now if the phone after odin doesn't want to turn on THEN your bricked. Since your phone is a newer build and they have been known to not always like jf6 Odin I suggest you try this KB1 odin. Best of luck
speedy_11 said:
That guide has not been updated for 2.3 roms. you should follow the instructions that were written by the rom maker, for the rom your trying to flash
Click to expand...
Click to collapse
Know that now! lol The instructions for Serendipity indicated I didn't have to go back to stock. But I just wasn't sure. So I figured I'd go ahead back to stock just to "be safe." That worked out well!
speedy_11 said:
(side-note if you have read and read like you said you should have had come a cross some of this.)
Click to expand...
Click to collapse
Yes, you are correct. And I deserve any amount of "stupid newb" criticism you can heap on me.
For2ndtwin said:
Which Cognition were u on ? And which Odin did u use ?
Click to expand...
Click to collapse
Which Cognition? Uhm... I don't recall. Whatever was the newest version when I installed it nearly 3 months ago.
I used the Odin One-Click. The filename is I897UCJF6-final-OCD-REV0. When I run it, the title bar says Odin3Execution_v1.0.
For2ndtwin said:
And since u can still get into Download mode u can relax a little, cause that's a good thing.
Click to expand...
Click to collapse
That's what I keep trying to tell myself...
prbassplayer said:
Lol relax If the phone shows any signs of life, that means it can be fix (usually). Now if the phone after odin doesn't want to turn on THEN your bricked. Since your phone is a newer build and they have been known to not always like jf6 Odin I suggest you try this KB1 odin. Best of luck
Click to expand...
Click to collapse
Thanks! I'm reading through the threads y'all linked to and I'm sure I'll be back with questions. This whole Odin thing, for one, has me confused. There's at least a dozen different versions available from samfirmware.com, there are different versions of the one-click (like the Designgears 2.2 one? Should I try that one?), then different "full" versions with different instructions ("only use the pda button," "use this pit file", "don't use a pit file", etc...) I'm trying my best to make sense of it all. I was in full-blown panic mode yesterday and trying to read through a dozen different threads at once. Maybe today I can slow down a bit, take a breath, and get this figured out.
The one click I linked should get you to stock. Atleast so you have a funtional phone. There is only one true odin with different versions (1.1 1.82 etc) one clicks r simplified odin that will only flash something specific like 2.1 jf6 or 2.3.3 kf1 to name a few. Samfirmware.com uses the actual odin as it supplies packages for it.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
prbassplayer said:
The one click I linked should get you to stock. Atleast so you have a funtional phone. There is only one true odin with different versions (1.1 1.82 etc) one clicks r simplified odin that will only flash something specific like 2.1 jf6 or 2.3.3 kf1 to name a few. Samfirmware.com uses the actual odin as it supplies packages for it.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Ok, another sucky thing is I'm on satellite internet and already dangerously close to being FAP'd. I've got to run into town this evening and will try to find some free wifi so I can download those things. Until then... it's just reading threads.
One quick question... that's a one-click you linked to? Posts 33 and 34 say to use regular Odin, not one-click. They provide a link to download regular Odin. Is the I897UCKB1-homeBinary.tar file part of the package I download from the link in the first page? The one-clicks I've downloaded have just been an .exe file.
HeathicusF said:
Ok, another sucky thing is I'm on satellite internet and already dangerously close to being FAP'd. I've got to run into town this evening and will try to find some free wifi so I can download those things. Until then... it's just reading threads.
One quick question... that's a one-click you linked to? Posts 33 and 34 say to use regular Odin, not one-click. They provide a link to download regular Odin. Is the I897UCKB1-homeBinary.tar file part of the package I download from the link in the first page? The one-clicks I've downloaded have just been an .exe file.
Click to expand...
Click to collapse
Because I'm a derp and didn't read it well. Regardless its the package files for stock KB1 use regular ODIN for it. Stick it in PDA. It doesn't have bootloaders so the possibilities of hard bricking are very low xD. My mistake for saying it was 1 click sorry xD
Ok, thanks. I'll post an update tonight after I get back home.
SUCCESS!!!
I now have a fully functional phone running what appears to be stock 2.2 firmware!!
THANK YOU!!!!
However... I can't seem to get into recovery mode. When I hold down all three buttons, it looks like I'm stuck in a boot loop again (ATT World Phone screen flashes). If I release the power button keeping the volume buttons held down, the phone just boots as normal. Is there a fix for this?
I still have all the folders for my old apps on the internal memory card. Can I delete these manually? I'd like it to be back to truly stock settings and start all over. Is that what the "Master Clear" in Odin is for? I didn't see that option in "regular" Odin.
I did get it rooted with Super-One-Click.
Ok, this is where I'm at.
Stock Foyo working phone.
Can't boot into recovery using volume & power buttons.
Rooted with Super One Click.
Installed Superuser.
Installed Rom Manager. At least now I can boot into Recovery Mode through the option in Rom Manager.
Flashed Clockworkmod using Rom Manager. Reported success, but Recovery Mode is still stock version 3e, not 2e. So, still can't install a new custom rom.
I'm a little nervous to try anything else at this point, but really want to be running Serendipity. Serendipity says DO NOT use Rom Manager to install it.
What to do from here? I'm researching, but any pointers would be helpful.
If I install Cognition again from Rom Manager (is that possible/safe at this point?), will that replace the Recovery Mode with 2e? Or is that not related at all?
not related at all.
you should really take the 30 seconds to search for that error you get when you try to reinstall packages from 3e recovery.....it would solve your problems.....
or do it the EASY way and just ODIN a freaking kernel on it that has built in CWM.
flash your rom of choice from CWM
HeathicusF said:
Ok, this is where I'm at.
Stock Foyo working phone.
Can't boot into recovery using volume & power buttons.
Rooted with Super One Click.
Installed Superuser.
Installed Rom Manager. At least now I can boot into Recovery Mode through the option in Rom Manager.
Flashed Clockworkmod using Rom Manager. Reported success, but Recovery Mode is still stock version 3e, not 2e. So, still can't install a new custom rom.
I'm a little nervous to try anything else at this point, but really want to be running Serendipity. Serendipity says DO NOT use Rom Manager to install it.
What to do from here? I'm researching, but any pointers would be helpful.
If I install Cognition again from Rom Manager (is that possible/safe at this point?), will that replace the Recovery Mode with 2e? Or is that not related at all?
Click to expand...
Click to collapse
You are in 3e recovery because you are running froyo. Flash to the stock 2.1 eclair and that will get you back to 2e. There are other ways but thats the most basic I feel.
Sent from my Samsung Captivate running Cognition 2.2 rom
capocaccia said:
You are in 3e recovery because you are running froyo. Flash to the stock 2.1 eclair and that will get you back to 2e.
Click to expand...
Click to collapse
Yeah, trying to flash the stock 2.1 is what got me in this trouble to begin with!
Pirateghost said:
not related at all.
Click to expand...
Click to collapse
Thanks!
Pirateghost said:
you should really take the 30 seconds to search for that error you get when you try to reinstall packages from 3e recovery.....it would solve your problems.....
Click to expand...
Click to collapse
I'm trying... but 1) satellite internet is frustratingly slow - not much better than dial-up at times; and 2) each path of research I take leads to several forks with several different people giving several different solutions to problems, some people saying it worked, some people saying it didn't, which leads to several more alternative solutions, some of which don't work, etc... It gets confusing after a while, but I'm trying my best to read through all the threads I wander through and to make sense of it all. Yeah, I'm a stupid newbie....
capocaccia said:
You are in 3e recovery because you are running froyo. Flash to the stock 2.1 eclair and that will get you back to 2e. There are other ways but thats the most basic I feel.
Sent from my Samsung Captivate running Cognition 2.2 rom
Click to expand...
Click to collapse
If you would have read the beginning og the thread you know that his phone didn't take well to jf6.
prbassplayer said:
If you would have read the beginning og the thread you know that his phone didn't take well to jf6.
Click to expand...
Click to collapse
There are more builds of 2.1 other than jf6...
Op look at the bottom of the first post of the odin one click thread by design gears there are 2 stock firmware packages the first one is an eclair build use the full version of odin (not one click) flash that and you're good.
Or search for the work around of 3e recovery, look in the sticky roll up at the to of the general section...it'll say "e: signature verification error"
HeathicusF said:
I'm trying... but 1) satellite internet is frustratingly slow - not much better than dial-up at times; and 2) each path of research I take leads to several forks with several different people giving several different solutions to problems, some people saying it worked, some people saying it didn't, which leads to several more alternative solutions, some of which don't work, etc... It gets confusing after a while, but I'm trying my best to read through all the threads I wander through and to make sense of it all. Yeah, I'm a stupid newbie....
Click to expand...
Click to collapse
funny thing, that STICKY section we have at the top of the forum....
theres this one called a 'STICKY ROLL-UP', not to be confused with fruit roll-up.
http://forum.xda-developers.com/showthread.php?t=1161102
all the info you need is located within it.....oddly enough
Pirateghost said:
funny thing, that STICKY section we have at the top of the forum....
theres this one called a 'STICKY ROLL-UP', not to be confused with fruit roll-up.
http://forum.xda-developers.com/showthread.php?t=1161102
all the info you need is located within it.....oddly enough
Click to expand...
Click to collapse
Yes, I tend to rely to heavily on the search feature and overlook sticky threads. Thanks for the reminder.
The "Fixing 3e" methods listed in this thread don't seem to be working for me. First method (the script) gives me an error. Tried with Win 7 64bit, and 32bit (two different computers). Yes, phone drivers were installed. Second method (manual copying of the file) doesn't work. When using Terminal Emulator to execute the command I get the message "Operation not permitted." When using ES File Explorer with Mount file System as writable checked in the settings, I get no errors or complaints... but nothing has changed when I boot into recovery.
Still working on it. Thanks for the pointers.
why dont you try one of the ODIN KERNELS that will add CWM for you? why are you wasting your time running in circles for nothing?
put phone in download mode
open ODIN, add the kernel into the PDA slot
connect phone
flash kernel
now you have CWM and can flash any 2.2 rom you want
Pirateghost said:
why dont you try one of the ODIN KERNELS that will add CWM for you? why are you wasting your time running in circles for nothing?
put phone in download mode
open ODIN, add the kernel into the PDA slot
connect phone
flash kernel
now you have CWM and can flash any 2.2 rom you want
Click to expand...
Click to collapse
After softbricking (is that the right term?) my phone with Odin, it makes me a little nervous. (Of course, I also recovered my phone with Odin, so maybe I shouldn't be nervous...).
This running around in circles...? We'll call it "education"!
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
in terminal emulator type su and then reboot recovery maybe it work
or may be you just flashed unsupported recovery
nycmon said:
HI!
Just recently signed up so I can't seem to post this question in the FASTY III forum....I kind of understand why xda has this policy about new members not being able to post int he developmental forums...but still...
I recently moved from FASTY II to III...ran into a bunch of issues but I managed to resolve most of them by going through the forums. What I am having trouble with is my inability to get to the Recovery menu. I have tried to go there thru the shutdown menu, by doing the button holding trick, and even from ROM Manager... none of those seem to work for me. Very frustrating... All those mentioned attempts only bring up an ATT screen which wont go away until I reboot the phone into a normal start....
So why am I unable to enter Recovery mode?
Any help would be much appreciated. Thank you!
Click to expand...
Click to collapse
I have been having the same problem recently, but not just with this rom. I have flashed many roms to my device, but it appears that almost everytime i try to flash something now, the same exact thing happens as the OP. any information on what is wrong or how to fix this would be greatly appreciated.
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
Sometimes this happens, but i am usually still able to use the rom after i wait for awhile. Recently it just gets stuck at the ATT logo screen and does nothing else.
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
studacris said:
HERE is a package containing JUST the ginger boots.
MAKE SURE YOU HAVE A GOOD PHONE/PC CONNECTION, FLASHING BOOTLOADERS IS THE ONLY WAY TO TRULY HARD BRICK
Click to expand...
Click to collapse
i just tried it with a solid connection and it almost instantly said failed in the red box. now i cant turn it on or get to download mode so im pretty sure it is hard bricked. is there any way you can help me with this?
EDIT: False alarm, i can still get to download mode so i can ODIN back to stock, but i do not know if i should risk it again
Whew that was close.
You can flash to stock using a bootloader less package, that way if it fails it can't hard brick.
Then if that works, find an entire stock gingerbread package with bootloaders included, and flash that instead of just the bootloader one click. this again, will involve risk, but full Odin package seem to work better on some phones than one clicks do.
I tried to flash the bootloader again and it succeeded. i then proceeded to try and flash Fasty KK4 v1.1 and once again i was stuck at the ATT logo. For some reason with every rom i flash, when the logo pops up, it starts dim and then get bright. After it gets bright, it stays that way and it is a real pain not being able to use custom roms anymore.
If you have the GB bls just make sure you follow LL's instructions in the OP for Fasty. I had the same issue, but it was me mistake for not following the istructions properly
studacris said:
When you boot up...do you guys get a scrambled screen that looks like white noise?
that's caused by froyo bootloaders on a gingerbread ROM.
Not all That familiar with fasty though...dunno of the jump from 2 to 3 was froyo to ginger, just a guess.
Click to expand...
Click to collapse
i DO get a very colorful white noise screen whenever it boots up ...the screen goes away once it fully reboots....I wondered about it but just assumed it was a quirk of the FASTY III package...
Is Rom Manager a froyo based app?
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
studacris said:
No, ROM manager is poop. Not implemented on galaxy devices properly, and won't work past eclair, and even them it was severely limited to just downloading an update.zip to your sdcard...which you could put there manually with out having to root...
FORGET ROM MANAGER EXISTS
Click to expand...
Click to collapse
Really? Rom Manager helped me a lot until this Fasty III installation....even in my previous rom Fasty II it worked fine and did great for backing up and restoring backups....saved my asss a few times with those restores lol....But if this program doesn't work for fasty III what comparable program can I use?
Also I still can't intorecovery mode...nothing works...I even tried using ADB and Droid Explorer....nothing seems to get it into recovery mode...
Am I going to have to flash back to stock ROM and try reinstalling fasty iii again? This seems all so tedious lol...
OR is there a way for me to flash back to Fasty II without having to go back to stock rom? or without having to access the recovery screen?
Thank you^
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
studacris said:
All that backing up and restoring you did with ROM manager can be done in cwm recovery and that's what you should use from now on. No app needed at all.
Follow the instructions I've already provided in this thread. You'll either need Odin to flash the gingerbread bootloaders,
or to go back to a froyo firmware, first flash a froyo kernel with Odin and THEN the froyo ROM. stock isn't needed.
Recovery in a gingerbread kernel is completely inaccessible with froyo bootloaders.
Click to expand...
Click to collapse
Thank you for the info!
Looks like fasty III is a GB based mod after all...I guess I should read up more on the rom before installing lol....I did not expect the dev to go from froyo to gb -_-
I was thinking of using your previous post for the one click gb bootloaders only....but it seems a little iffy and I can't afford to hardware brick the phone lol...
Makes me wonder tho...is it really THAT risky to flash bootloaders? It would make things simpler if i could just flash the gb bootloaders and go from there....
the whole flash should take less than a minute, where the actual writing takes only a few seconds...but if you were to lose communication in that awful window then it would be bad day.
But that is a small window, and if you have never had connection issues you should be ok if Odin tends to be iffy, you van try heimdall I've heard that works better for some.
Still haven't tried flashing the bootloaders because i'm scared of the possibility of hard bricking my phone... If worst case scenario was to happen and it gets hard bricked....are there any options to restore that phone? or is it just paper weight after?
Also until I flash those bootloaders there is no way to back up my phone or anything?
Thanks for all ur help btw!
another issue i am having is that the phone seems pretty laggy after installing this rom...even with tegra overclock premium and tweaking it up to 1252mhz 1275mv 1100mv setting...it still seems laggy when opening sms etc....is this just the results of a bad rom install? also battery life seems crappy....even after doing the battery recalibration...of course i couldn't wipe the battery stats since i cant get into recovery...
Hard bricks are recoverable by a hardware modification known as unbrickable mod, search for user Adam outler, or go to mobiletechvideos.com they both offer this service if you're not a soldering expert.
Battery recalibration does NOTHING the stats are reset everytime you charge to 100, and besides that they don't calculate your current battery level, just what's been using it, its what's used in settings> about phone> battery use. It has nothing to do with extending battery life.
oh lol...i have been reading all these threads where people are talking about how much their battery life improved after they did the recalibration and stat wipe ....well anyways I am going to attempt the bootloader flashing...I hope everything goes well! after that I want to try reflashing the fasty III ROM...
Do you have any recommendations as far as a good ROM for teh captivate? One that doesn't lag and has good gps & battery life? I would appreciate any help you can give.
Thanks!