Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd? The reason I ask is because I have been bouncing between cognition and paragon for about 2 weeks now NOT using the method of flashing back to stock 2.1 without a single problem. I'm sure there is a good reason flashing back to 2.1 before trying new roms, I would just like to know why. I was able to preform a stock wipe using odin3 one time last week (just did it to make sure the phone would do it) it just seems like a really long process, but I'll start doing it that way to avoid a brick.
Thanks
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
For the most part, you don't really need to flash back to stock. It used to be a bigger deal to flash back to stock because some of the Roms would intervene with each other and mess things up. It is still recommened for a clean flash, but I rarely do it and my flashes work great.
EDIT: @Trusselo: damn it! Second time someone beat me to the answer tonight!
HAHA
and forget ODIN ONE CLICK !!
i keep forgetting about this
http://forum.xda-developers.com/showthread.php?t=944418
ALL IN ONE CAPTIVATE TOOLBOX
I have been trying roms weekly since November and have only needed to flash to stock twice, after failed flashes caused by my lack of patience. YMMV of course
jayjr1105 said:
Hey all. Just joined the forums a few minutes ago and I have a burning question on why it is necessary to flash back to stock with odin before you try different roms. Why can you not just boot into clockwork, factory wipe, wipe cache, wipe d cache and then simply load the new rom from sd?
Click to expand...
Click to collapse
It's not necessary and not even a good idea. Also, why wipe cache and d-cache when the install script does that?
Trusselo said:
to be safe, and some roms mod files that others dont, some roms depend on apps and files in the stock rom that might be different or not there at all in other roms.
Click to expand...
Click to collapse
ROMs don't mod or use any files which are on the phone prior to installing them. All the files on your phone after the install were in the CWM flashable zip file. Any ROM cook would be stupid to do otherwise. The exception would be no-wipe ROMs, but you would never flash to stock before using one of those.
Ive also wondered this as well and talking to guys like opcow, and a couple other Devs such as MikeyMike and a lot of guys at the Andromeda IRC they all agree that you should be perfectly fine now as long as you wipe everything before you flash.
I may try with Andromeda when I get home because I have my PC and Jig there just in case but still may try now. But also tlaking to a lot of users that they dont even do it anymore now because of the install scripts and as Opcow said if you think logically its technically safer.
Trusselo said:
long process? extra 5 minutes when you get used to it. if you are ATT use ODIN ONE CLICK to restore stock 2.1 (hint: it takes one click)
Click to expand...
Click to collapse
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Dlev7 said:
Actually thats not true at all.
If your a build 1009 and under you can use the one click. Although the build 1008 sometimes have problems.
But for the Build 1010's and up (like me) you have to use Odin3 and take a good 30-40 minutes just to get to JH7 because half of the time I lose my 3 buttons then have to push the 3 button fix over via ADB. I have gotten use it and its a pain in the ass.
And the time I listened to someone that says ALL ATT people can use the one click it completely ****ed my phone and if I didnt have a jig my phone would have been completely screwed up.
Im not trying to be rude im just saying I saw a post very similar to that a couple weeks ago and it came very close to completely bricking my phone and reading posts here now saying they have the same problem and if they dont have a jig they just got a 200 dollar paper weight.
Sorry for getting off topic back to topic today Im going to flash Andromeda over Darkyy 9.3 and wipe data cache and d cache in CWM and see how it goes although everyone and even the devs and a lot of users now a days say it should work perfectly.
Click to expand...
Click to collapse
+1 Guys if you don't know exactly what to do/suggest please don't say it. I'm not trying to start a war, but a wrong suggestion can easily soft or hard brick someones phone. This is a forum, so no one can stop you from saying things, but think about if it happened to you? You would be pissed!
Anyways back on topic, what model phone do you have, because having a 1009 model phone makes flashing and going back to stock (usually) so much easier. But then again, I rarely use odin because all the roms are compatible for the most part.
Sent from my SGH-I897 using XDA App
I've never used ODIN because I haven't wanted to try to run it from GNU/Linux in a virtual box.
I just wipe and flash from clockwork like the op. Been flashing roms for a couple months now, never had a single problem. (except when I noobed it up by trying to flash back to a nandroid backup via Rom Manager. Even then, didn't need Odin to sort it out).
If I ever run into a problem, then I'll try Odin, but I'm waiting to cross that bridge till I come to it.
To prevent exceptions or troubles from the version you already have... so everybody comes from the same rom, understand?
I flash to jf6 because that's what I have been conditioned to do for a while. However, the few times I was impatient and didn't....no problems either.
From all the reading I've done here, the only reason to do it is for the placebo effect.
There was once a time when all the new roms were built on the unofficial froyo and it only had 3e recovery. The quickest way to get around that was to flash stock. Also the lag fixes were tricky and easily fixed by flashing stock. Now recovery is in the kernel. As long as you insure the kernal lag fix in rom A understands the kernal lag fix in rom B flash away. Nandroid backups are kind of useless they don't backup the kernal or the modem. Save odin for when things go really wrong(;~ )
Sent from my i897 using XDA App
I have done it both ways, and there its no difference going back to stock and or flashing over other roms. I flash often, have not got stick in boot loop in months
I like to go back to stock since I KNOW that everything has been defaulted back to normal. Just a security blanket step for me.
I flashed andromeda over darkyy 9.3 just wiping data cache and d cache. Nothing wrong. Everything worked perfect so I got to believe that if you just wipe everything it should work perfectly.
Just for safety I got a jig and odin but for now I'm saving a good 45 minutes to not flash back to stock
Sent from my SGH-I897 using XDA App
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.
Hey I have a question I am on Darkyy 9.3 and have flashed to stock before numerous times and have a Download Mode Jig always handy but I have been hearing and reading recently that with good ROMs with the new install script that you can just flash ROMs over each other if you wipe data and cache and dalvik cache and if you get in trouble just flash to stock.
The reason this interests me is because im a build 1011 and its super annoying because I have to flash to JH3, then Root, then apply 3 button fix.zip sometimes if the 3 buttons dont work, ROM Manager, Quick Boot, JH7ota.zip, then flash the next ROM.
I am willing to do this but I am feeling lazy today and wanna try out Serendipity so Im asing YOU do you think i'll be alright if I flash Serendipity JS3 over a JS5 Darkyy 9.3?
Also one more questions related to that is Serendipity users does it overwrite your Kernel and modem when flashing? I have Suckerpunch and JL3 and am wondering if I should disable lag fix-->Install latest Speedmod. Or would the ROM script just overwrite that.
Finally a question that was posed to me today from a user that doesnt flash to stock and hasnt had a problem that really made me think that what really is the difference when using Odin which installs an unneccesary bootloader and ect going from a JS5 base to a JH3, then using CWM to go JS5 to JS3? Wouldnt it seem logically easier and safer?
Any input and comments about your experience will be GREATLY appreciated.
you can use odin1click, or odin3...
since you have a jig, flashing to stock is not a big deal to you.
Owais1437 said:
you can use odin1click, or odin3...
Click to expand...
Click to collapse
he cannot use odin 1click since the build is 1011. it will brick the phone, for sure.
I Odin3 back to stock, but I'm also on the safe side. I have heard more and more people flash over the old ROM with using Odin though.... I figure that it only adds a few more minutes to the overall task, so why not?
always flash stock imo
just best to go to stock , flashing over has created small bugs for me ..., i do this even for common builds or updates, even though the Dev's work hard to make them upgradeable...i still do .....and if your courageous,,, its good you have the jig or a 1007 build
My personal choice is flash to stock if the roms use different kernels. If the kernel is the same, even different revs of same, I don't bother with stock.
Sent from my Captivate using XDA App
mengbo said:
he cannot use odin 1click since the build is 1011. it will brick the phone, for sure.
Click to expand...
Click to collapse
I use print one click all the time and my phone is build 1012
Sent from my SAMSUNG-SGH-I897
I always flash to stock and go through the whole process. I find it less buggy and the mental idea of a clean slate allows me to address issues solely on that rom and not past components.
It's sure as heck faster to flash to stock than to read through 1000's of posts to figure out if it's a good idea or not when I don't know as much about it...
I'm still new to the flashing ROMs world, but I'd rather be safe than sorry at this point so I go back to stock whenever I switch.
Ive now just wiped data cache and dalvik cache, and flashed over 4 ROMs in the past week with ZERO problems.
That being said im always safe I do it at home with my jig and odin ready on my PC.
But i actually havent had a single problem.
Darkyy-->Andromeda-->Paragon-->Serendipity
I think we need to sticky/pin this for us who just flash the stock/leaked GB 2.3.3 along with the optional root from this thread since we can't post there http://forum.xda-developers.com/showthread.php?t=1127249
Since this is the route that I went I would be able to help answer questions for others. I see cognition, mosaic.... but how about us who like to keep it stock?
Brickster
Just want to say that I have learned so much on here and I have a lot of fun trying out different ROMs. Thanks to all the DEVs, when I get a job I'll buy you guys some beers lol.
So... This has soft bricked my phone every single time. The first 4 attempts were from stock eclair. My last attempt I was successfully running Stock I9000 2.3.3 NEE so I thought I would try it from there. Odin gets to boot.bin and then says FAIL! I got into download mode using VOL DWN and PWR which is the key combination from Stock I9000 2.3.3 NEE. I have been running I897UCJF6-final-OCD-REV0 to flash back to stock after brickness.
So i'm sure i'm missing something pretty simple, but any help is appreciated.
Woah dude, that was very very very close to being a hard brick. Boot.bin is the primitive bootloader. so you had a kf1 pbl, and since you had the combos for I9k boots you obviously had an I9000 sbl, (secondary bootloader that's where the combos are contained.)
Make sure the usb chord is on a port attached to the motherboard (in the back of the pc), if it is already switch to another. Reboot the computer and try again.
But with such a close call like that, and the fact that you said it fails every time I would avoid it altogether I mean its a stock rom, is it worth bricking over??
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
ttr187 said:
Well, I really wanted to try the Cognition 5 v2 ROM. Instructions say to be on Samsung Gingerbread. So that's why I tried so many times and I am really more curious to find out why it's not working than I am worried about it bricking.
I was on a port directly on the motherboard Odin displayed as com10.
I was thinking that maybe it is my computer since most have success with this 1-click. I forget sometimes I'm running a 64-bit version of Windows 7 maybe that's the culprit. Is there anything I can check on my computer to keep this from happening again?
Click to expand...
Click to collapse
Use admin mode for Odin and change the compatiblity to Xp service pack 2. This is the best way to run Odin for Windows 7 x 64. Since I use Cog 5 v2, I strongly recommend following the instructions 100%. Please remember when you need to loading stock UCKF1 and when you load UCKF1, you are loading bootloaders, so any disconnection can brick you hard. Thank goodness for the simplified instructions there.
GB stock? I thougth captivate stock were eclair or froyo.
KF1 is the leaked gingerbread firmware for the captivate...
popfan said:
Use admin mode for Odin and change the compatiblity to Xp service pack 2.
Click to expand...
Click to collapse
After changing the compatibility mode to XP pack 2 everything worked like a charm. Then I was able to successfully flash Cognition 5 v2. Sweet!
Thanks.
Hello. I use Darky's rom 10.2. And I have problem with Dialer. It sometimes crushes and exits. Problem will be solved with reboot. how can I fix it? thanks.
I would try to flash again and make sure you do a data/cache wipe. I've had random issues with other ROMs when I did not wipe, and all was fixed once I flashed properly.
I know I'm not wiping everything while flashing, but I flash it as told as in FAQ. But my memory will stay unwiped after I run newly installed ROM.
When you say "memory" what exactly do you mean?
If you mean the /sdcard storage partition, that is normal.
yes, /sdcard storage partition.
Before flashing, I get warning message about wiping all data in my internal storage... what does it mean then?
The /data and /cache partitions. And the dalvik cache.
The first 2 are in the cwm main menu. Wipe data/factory reset and wipe cache. Dalvik is in the advanced sub menu.
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Griff1220 said:
When i flash this, my phone asks me for a password. It won't let me do anything without the password and I have no idea what it is. I've tried samfirmware.com and that most certainly is not it.
Click to expand...
Click to collapse
It appears to be asking for some encryption password according to one of these guys that posted in the following thread. But there is a way to get past it by the method in this thread...http://forum.xda-developers.com/show...02&postcount=7
Remove ur external sd and copy over/back up anything u want to save from ur internal sd before u do this, just in case.
data/chache wipe i should do right after flashing right?
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!
Hi there fellow time bomb owners!
Let me start out........... Ive had my note for many months now. Ive flashed many GB and ICS roms, both TW and AOSP.
Ive always been very careful with the brick bug issue and always flashed every rom via the OP's method to the letter.
I finally settled with Kingdroid. After running it for nearly 2 months without ever having a random reboot/FC or any issues at all it started to misbehave, crashing, freezing and somtimes making me resort to battery pulls!
This all culminated last night, when after installing an app, I tried to open the said app and the phone froze on me. I long pressed the power button to reboot and then got stuck in a bootloop. In all my months with my Note ive never had a bootloop. I could still get into recovery and download so I thought no big deal.
I tried to wipe the cache and davlik cache to see if there was any nasties in that causing the bootloop. They both wiped fine but when I rebooted the loop was still there. Still Not a problem I thought, I will just have to reflash. Pain in the ass I know, but at least Im not bricked. So I placed abyss kernel and kingdroid onto my SD booted into recovery and went to flash Abyss. All went well so went to reboot recovery and........Boom in some kind of elongated (graphically) version on the same recovery I had before? Not abyss? Ok, it must not have taken properly, flash it again, as soon as I went to move through the recovery menus the recovery restarted, not rebooted, just restarted? It did this everytime I tried to move in the menus? I though thats very odd indeed? then all on its own it started to restart? Then I worried, could this be damage to my partitions or emmc in general? Never done any wiping on unsafe kernels, surely it cant be?
So I resorted to Odin and the factory firmware I keep for warranty purposes. Plugged everything in and set it running. The phone was recognized, Md5 checked then.................Couldnt open COM port to device? S**T, F**K. I must be bricked now I thought. So as all good software people do, I unplugged everything rebooted my computer and tried again. It worked this time around!? I was a little nervous going through the FACTORYFS bit but it took, pass! Yes! Booted into stock recovery did the full wipe and now all is well with my note, all be it on stock nastiness.
I apologize for the lengthy post but I think its important to share potentially dangerous behaviour in depth with the note community. Many people may have had a panic and jumped straight on the Brickbug bandwagon (as I nearly did).
So after all that I would like to know if someone far more intelligent than me could give a possible cause? Not only out of curiosity but so that people (and me!) could avoid this worrying behaviour. And also how or if you can check your EMMC for bad blocks without Root and the emmc checker app?
If you read all this, well done! and thankyou for looking,
x5starguerillaa said:
Hi there fellow time bomb owners!
Let me start out........... Ive had my note for many months now. Ive flashed many GB and ICS roms, both TW and AOSP.
Ive always been very careful with the brick bug issue and always flashed every rom via the OP's method to the letter.
I finally settled with Kingdroid. After running it for nearly 2 months without ever having a random reboot/FC or any issues at all it started to misbehave, crashing, freezing and somtimes making me resort to battery pulls!
This all culminated last night, when after installing an app, I tried to open the said app and the phone froze on me. I long pressed the power button to reboot and then got stuck in a bootloop. In all my months with my Note ive never had a bootloop. I could still get into recovery and download so I thought no big deal.
I tried to wipe the cache and davlik cache to see if there was any nasties in that causing the bootloop. They both wiped fine but when I rebooted the loop was still there. Still Not a problem I thought, I will just have to reflash. Pain in the ass I know, but at least Im not bricked. So I placed abyss kernel and kingdroid onto my SD booted into recovery and went to flash Abyss. All went well so went to reboot recovery and........Boom in some kind of elongated (graphically) version on the same recovery I had before? Not abyss? Ok, it must not have taken properly, flash it again, as soon as I went to move through the recovery menus the recovery restarted, not rebooted, just restarted? It did this everytime I tried to move in the menus? I though thats very odd indeed? then all on its own it started to restart? Then I worried, could this be damage to my partitions or emmc in general? Never done any wiping on unsafe kernels, surely it cant be?
So I resorted to Odin and the factory firmware I keep for warranty purposes. Plugged everything in and set it running. The phone was recognized, Md5 checked then.................Couldnt open COM port to device? S**T, F**K. I must be bricked now I thought. So as all good software people do, I unplugged everything rebooted my computer and tried again. It worked this time around!? I was a little nervous going through the FACTORYFS bit but it took, pass! Yes! Booted into stock recovery did the full wipe and now all is well with my note, all be it on stock nastiness.
I apologize for the lengthy post but I think its important to share potentially dangerous behaviour in depth with the note community. Many people may have had a panic and jumped straight on the Brickbug bandwagon (as I nearly did).
So after all that I would like to know if someone far more intelligent than me could give a possible cause? Not only out of curiosity but so that people (and me!) could avoid this worrying behaviour. And also how or if you can check your EMMC for bad blocks without Root and the emmc checker app?
If you read all this, well done! and thankyou for looking,
Click to expand...
Click to collapse
Mate, feel for the brown pants time you've ordealed, glad you got out of it. I'm fairly certain, although no dev, that there is an incremental damage obtained via certain kernels, be it wipes or even large file transfers. There's an app that can judge if any sectors are past repair...
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check
So at least you know if it's an emmc issue. Let me know.
Sent from my GT-N7000 using xda app-developers app
Cheers for the link.
Do you know of a way that I can check for bad sectors without that app? It needs root and I dont really want to flash/root anything until I can (if possible) determin whether or not Im damaged.
The only reason I ask is that now is the phone is primed ready to go back to samsung if so.
No counter or triangle or reminants of root.
Sent from my GT-N7000 using xda app-developers app
accessing the internal NAND flash memory of your phone requires root privileges. Without Root, The System would simply deny you poking and probing on the internal storage of your phone.
That is why it is important to Root.
On the lighter side. You can actually Root your phone.. use that app to know if your phone has bad sectors and once you've done knowing it... you can simply UNROOT your device.
In that way, Samsung would never know the how's and wherefore's if you have tinkered your device or not.
Simple as that.
Ok. I rooted with a older version of GB.
Checked the NAND and everything says its ok. So I put it back to the latest GB uk firmware, updated via KIES to latest ICS and then rooted with the super su.zip and the full root busybox.zip from Dr Keatens post.
So im now running the latest stock firmware with full root. Can I install a rom from where Im at now? With stock recovery with full root? Or do I need to flash a kernel like abyss first to get the red pill recovery?
Sent from my GT-N7000 using xda app-developers app
Things may have changed but I think general guidance is to flash from rooted gb kernel like abyss or stock. Certainly for AOSP roms like cm9 variants or cm10 that's the case.
Sent from my GT-N7000 using xda app-developers app