I'm sorry if someone already asked this question but I was not able find an answer. I am running a custom ROM now, do I have to go back to stock before flashing another ROM?
It is usually not necessarily to do it but it a very good idea to return to stock and master clear with the odin-1-click
Sent from my GT-I9000 using XDA App
No you don't need to go back to stock. Nor is is necessary to master clear. Most if not all the roms on here will do a full wipe of your SD card during the install. Flashing back to stock just adds another chance to mess up your phone. This was advised, several months back but it's not necessary now. This doesn't apply if you want to flash to CM7. They have their own install procedure that is different than anyone elses.
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
BWolf56 said:
Just to add to what the others said. Make sure u flash a 2.2 based rom over ur curent (if thats what u are.using atm). Also you cant restore system app, it will screw up with ur new rom!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
crystalhand said:
The 2.2 stock will not let you flash a rom over it. Go back to 2.1 stock
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not what I meant.
If he flashed, lets say, FireFly (which is 2.2 based) then he can't flash over with, lets say, CM7 (which is 2.3 based). Just simple logic
@ OP - You can look on the ROM's thread to see what it is based on.
Thank you for all your help. I'm using Phoenix Ultimate now and want to try out the other ROM.
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
One less time touching Odin is one less time tempting fate. But that's just me. I'm pretty sure every rom dev in here has bricked a phone at least once...
much agreed. less odin. less potential for problems.
roms do a wipe now. doesnt matter what you had on it 2.1 or 2.2
2.3 is the only rom version that has a different partition table.
there is no issue flashing a 2.2 rom over 2.1 or vice versa. how CAN you upgrade from 2.1 to 2.2?? CWM anyone? oh **** right!
the only issue with flashing over 2.2 is the 3e recovery... and thers a fix for that. you dont need to go back to 2.1 to avoid the signature verification error... @crystalhand...
quarlow said:
It takes like ten minutes to odin back to stock. I do it every time, just feels like a cleaner install. Plus all the devs put that in their instructions. I trust the devs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Not all devs put it in their op. Some devs say flash first thru clockwork and only use odin when there are problems. Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Sent from my SAMSUNG-SGH-I897
1tontomato said:
Odin could be better used as a recovery tool only, not the first thing you do whenever you want to flash a new rom. Just my opinion.
Click to expand...
Click to collapse
EXACTLY as it should be.....
No, odin is potentially more dangerous than any standard rom flash. as has been mentioned, use in case your in some s
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Juanmail15 said:
I've always flashed back to stock using Odin whenever I flash a new rom. Like someone else on this thread said, it just feels cleaner doing it that way. While I don't doubt you guys when you say it's dangerous, would anyone like to offer a brief explanation as to why that is? And would anyone be willing to guess at what the odds of a permanent brick might be? Are we talking something like 1 in every 10 flashes or more like 1 in 1000?
If it's closer to the first one then we really are playing with fire here but if the odds are more like the second one then I don't consider that much of a risk.
Click to expand...
Click to collapse
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
+1
Odin should only be used as a "Oh S**T I bricked my phone" program. But then again, if you read and know what you're doing than it should never be "needed"
axis01 said:
I highly doubt someone is going to give you a "odds" answer. Phones can be finicky and they often do weird things. The less you're "changing" things, the better. Odining back to stock then flashing again to the ROM of choice just adds another chance for something to go wrong. Not just cable falling out or battery falling out, just weird coincidence. When there's absoutely no reason to go back to stock, why take the chance? Just because you're programed to THINK it's cleaner doesn't mean it is. As has been said several times already, most roms do a complete wipe of the sd card so there's really no reason to odin or masterclear.
Click to expand...
Click to collapse
Completely agree just want to clarify 1 thing. The roms don't do a complete wipe of the sdcard. The wipe the /data /cache and /system partitions, leaving the /sdcard completely intact, just like flashing to stock would. Master clear just reformats /sdcard partition and is not really needed as the os doesn't use this to function and including this in a rom would be catastrophic if the zip is in fact on the /sdcard partition you are wiping with it.
The most I do is clear cache, data and disable lagfix.
quarlow said:
If you download the CWM update.zip before you Odin to stock and leave it on your phones internal SD card, you don't have to root or get ROM manager. Place your new ROM on the internal card too. Just Odin to stock, allow to boot, and restart into recovery (3 button combo), install updates (twice) then use CWM to install zip from card (ROM you downloaded).
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Lancered said:
So you'd just drop the update.zip on your internal drive, drop the ROM in as well, boot into recovery and flash it that way?
Click to expand...
Click to collapse
Yup. That's how u do it, if you have no need to root before hand and back up, I'm assuming you've done that if I remember right you are the girl I told to brick her phone yesterday to return, is the replacement on eclair or froyo? Ig it on froyo you will have to get past the 3e recovery that's why I ask.
Related
I made another thread asking about a problem I was having with Odin not recognizing my captivate, but with no solution there I have decided to try and install froyo a different way. It looks like the froyo guide that nbs11 wrote will work for me a lot easier than odin. I am just about to attempt it, but I have a major concern:
With odin not being able to recognize my phone at all when it is in download mode, what would happen if my phone were to become bricked? Is odin the only way to fix it then? I would not want to brick it and then have a program that will never recognize it...
,thanks
I would recommend not flashing froyo until you work out the odin problem. You will be fine the first time you flash most likely but will essentially be stuck with that one rom. Most roms will throw crazy errors and fcs if you don't go back to stock before flashing.
Also if you happen to brick your phone you will be stuck without odin. It might be tempting to flash a rom but there will be no way to go back to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
I was afraid of this... Do you know of any other way to flash back to stock without odin? I spent 6 hours trying to get it to work yesterday with no luck...
Oh wait! I would be using clockwork and RomManager in order to flash the phone to Froyo.... Does that mean when I am on Froyo I could use the same procedure to flash back to an older firmware all without the use of Odin?
That's^ exactly what I did, I used Rom Manager (clockwork, they're one and the same) to flash the recovery, backed up the stock Eclair and flashed Axura Froyo.
I also used Titanium to back up all my apps and restore them after switching to Axura. No Odin at all.
Had this phone short of a month. I'm trying to figure out how to flash Odin now.
gunmetaldroid said:
That's^ exactly what I did, I used Rom Manager (clockwork, they're one and the same) to flash the recovery, backed up the stock Eclair and flashed Axura Froyo.
I also used Titanium to back up all my apps and restore them after switching to Axura. No Odin at all.
Had this phone short of a month. I'm trying to figure out how to flash Odin now.
Click to expand...
Click to collapse
So you can confirm that it would be completely possible to flash back to Eclair with just clockwork? If so, it might be worth doing. Well, as long as I don't get bricked... That, im sure, would require odin
totally not worth the risk. figure out ODIN first, or we will be seeing a post in a few weeks from you screaming about bricking your phone.....
Pirateghost said:
totally not worth the risk. figure out ODIN first, or we will be seeing a post in a few weeks from you screaming about bricking your phone.....
Click to expand...
Click to collapse
Thats the thing though... I see no way to get odin to work with my phone. I have tried every thing that I know of.
*sigh* guess Ill have to wait for the official froyo update then...
I prettu much figured out how to recover using Odin, but before my question is now that I've rooted and applied a custom firmware, will using Odin now wipe all of my user data, root and rom?
Thanks.
I think i get it now, Odin IS a way to recover the stock firmware, it's not like clockwork where you backup your original and custom firmware and switch between them.
The fact that I was able to flash a custom firmware without bricking my phone sort of negates the need for me to use Odin.
I took that risk and it worked fine. Now for the OP, it's better to find out that you do have that option of reverting back to stock in case you brick in the middle of flashing. Therein comes the problem that Odin doesn't recognize your phone, hence the hesitation to flash.
I guess it's really up to you if you want to do it anyway without Odin...
I see no reason to risk it... I spent too much money on this thing to brick it without a way to fix it
Sent from my SAMSUNG-SGH-I897 using XDA App
yentlequible said:
I see no reason to risk it... I spent too much money on this thing to brick it without a way to fix it
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Don't you have warranty on it? well everything that goes flashing is always a risk if your going back to stock im prefer using the "odin stock with 3 button combo", it flashes the sbl.bin first which is the 3 button combo in cases it hangs up somewhere you can always unplug the usb then go to download mode again. In cases there is also a "homemade test jig" that can help you go to download mode. The benifits you get from flashing is a lot you can use your phone full potential. Correct me if im wrong as long as you can start your phone with a display you can always fix it. I would suggest to read all those with quote and theres also "ADB" which can help in some cases. just keep in mind before flashing make sure that the 3 button combo is intact first.
Nope, I have no warranty on this... I have t-mobile but didn't want the vibrant because I would need to pay the extra money for a data plan on it. With the captivate, I bypassed the requirement for the plan when I unlocked it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Ok time to re appear in this thread again. I have had a decent amount of flashing experience and want to make sure the right info us being shared.
Once again you can flash to any rom you want a couple of times.however after a few you are not found to be able to do it because what is going on in the phone of more complicated then you see on the phone. Most roms change the kernels and hardware software interaction. This can cause conflict resulting in fcs and excessive battery drain.
With all that being said I would still advise you to jump the bucket as king a you get odin to work. As long as you can figure that out you are golden. Once you have the hand of it you can flash to stock and to a rom in your sleep. I have managed to do it while on the highway.
Sent from my SAMSUNG-SGH-I897 using XDA App
A) You didn't install the driver (or the wrong driver)
B) You don't know what Download Mode is
C) Your phone is broken
D) You need to use a different USB port
Those are the ones that come to mind.
Alternatively, you could give Heimdall a try.
MikeyMike01 said:
A) You didn't install the driver (or the wrong driver)
B) You don't know what Download Mode is
C) Your phone is broken
D) You need to use a different USB port
Those are the ones that come to mind.
Alternatively, you could give Heimdall a try.
Click to expand...
Click to collapse
A) The drivers should be right, I downloaded them twice
B) I know exactly how to get to download mode.
C) Most likely
D) I Tried on 3 separate computers with different USB
Let me know if you have any other suggestions, I have tried everything.
What is Heimdall? Might be worth a shot...
Only idea i have is to pull your battery sim and sd card for a minut or two then flash odin with only your battery in.
Sent from my SAMSUNG-SGH-I897 using XDA App
I bricked my phone with an i9000 firmware. Since I was unlucky enough to have a phone without the 3 button combo, I was screwed.
Now, IF I decide to flash my new phone again, i'll make sure to put together the homemade jig which can put the phone into download mode without the phone needing to be able to do it itself.
crystalhand said:
Only idea i have is to pull your battery sim and sd card for a minut or two then flash odin with only your battery in.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
That is what I have been doing actually... I take everything out and enter download mode with just the battery in the phone
Sent from my SAMSUNG-SGH-I897 using XDA App
Moved to Q&A.
Ok i know and have seen that there are many experienced users in this forum, so i give you this!!Pls help sum1!!!
I think i bricked my fone, tried to get cwm 3 on it, then while rebooting, it wont reboot. went into download mode with odin (3 button fix) (i have done this 9-10 times before, not a noob to this), selected pit and tar and hit start. odin stuck on factoryfs and fully orange screen on fone. removed battery, fone, usb, odin restart, tried again, yellow screen. again. red screen. now got frustrated. tried normal odin(not the 3 button fix), again yellow screen.took out battery to try again, but fone wont start/go in dl/recvry mode anymore. tried on 2 different comps with xp/win7. no go.
SCREWED??
BTW, i ordered a jig.should arrive by end of week.
It'll be fine after you get your jig.
Sent from my SAMSUNG-SGH-I897
same thing happened to me...but i just got it replaced..as there was no way i could wake it up...but try Jig..or just get it replaced...every captivate is under warranty...tell them u were doing official Froyo update and lost electricity or something....
yes will try that and post.
In the meantime, can sum1 pls run me thru the steps to install custom ROM on preinstalled froyo cappy? My prev 1 was stock eclair, i filed 4 insurance and am sure the new 1s gonna b stock froyo. I have heard that there are a no. f probs with stock froyo phones????
Its a semi uncommon problem.I have had the random colored screens before and had to pull battery. Managed to get odin to work after a couple of times
Sent from my SAMSUNG-SGH-I897 using XDA App
psycho2097 said:
yes will try that and post.
In the meantime, can sum1 pls run me thru the steps to install custom ROM on preinstalled froyo cappy? My prev 1 was stock eclair, i filed 4 insurance and am sure the new 1s gonna b stock froyo. I have heard that there are a no. f probs with stock froyo phones????
Click to expand...
Click to collapse
flash to stock using full Odin(full odin to avoid loosing 3 button combo), flash CWM.Zip....flash any froyo custum rom
or just flash the fix for sign verification (its somewhere in the threads) then you can avoid flashing to stock....just flash CWM and Custom rom
viny2cool said:
flash to stock using full Odin(full odin to avoid loosing 3 button combo), flash CWM.Zip....flash any froyo custum rom
or just flash the fix for sign verification (its somewhere in the threads) then you can avoid flashing to stock....just flash CWM and Custom rom
Click to expand...
Click to collapse
YEA, I THOT SO 2... JUZ WANTED 2 VERIFY, WAT ABOUT WEN CHANGING ROMS?do i need to flash to stock every time, or can i just take a backup f froyo stock using cwm?(sorry 4 the caps...)
Most of the custom roms don't require flashing to stock now a days. But if its mentioned in the instructions than I would do it.
But definitely you should disable lagfix and stuff before flashing over new rom.
Sent from my SGH-I897 using XDA Premium App
viny2cool said:
Most of the custom roms don't require flashing to stock now a days. But if its mentioned in the instructions than I would do it.
But definitely you should disable lagfix and stuff before flashing over new rom.
Sent from my SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
no i meant with stock froyo and 3e recvry, should i flash to stock using odin or just backup/restore using cwm? m not familiar using stock froyo on cappy.
psycho2097 said:
no i meant with stock froyo and 3e recvry, should i flash to stock using odin or just backup/restore using cwm? m not familiar using stock froyo on cappy.
Click to expand...
Click to collapse
If u flash any zip from stock froyo it gives you sign verification error. So u need to fix that a nd than just flash custom rom as u normally do
Sent from my SGH-I897 using XDA Premium App
Crash N Burn....Owch!
psycho2097 said:
no i meant with stock froyo and 3e recvry, should i flash to stock using odin or just backup/restore using cwm? m not familiar using stock froyo on cappy.
Click to expand...
Click to collapse
Sounds as though your bootloader got hammered.
Yes, as another posted, with 3e recovery you'll get a signing error, but there is a workaround, depending on your device and ROM you're using to have files pass through as if it were on 2e recovery. Another method is if one passes files that are unsigned. (only load if it's from a trusted source)
Is it possible you performed a nandriod backup before this debacle occurred?
If so, try a restore from recovery with your last nandroid backup. This should restore the bootloader and correct partitioning on your disk.
HtH
Peace-
Liv33viL said:
Sounds as though your bootloader got hammered.
Yes, as another posted, with 3e recovery you'll get a signing error, but there is a workaround, depending on your device and ROM you're using to have files pass through as if it were on 2e recovery. Another method is if one passes files that are unsigned. (only load if it's from a trusted source)
Is it possible you performed a nandriod backup before this debacle occurred?
If so, try a restore from recovery with your last nandroid backup. This should restore the bootloader and correct partitioning on your disk.
HtH
Peace-
Click to expand...
Click to collapse
inncidentally i did do a couple of nandroids before "all the **** hit the fan". and i could use it to restore. but how? my fone simply wont turn on, neither go in2 recv/ dl. so how 2 restore???????
all 2.2 have 3e recovery, custom roms built on 2.2 come pre cracked.
here is the 3e recovery fix. http://forum.xda-developers.com/showthread.php?t=909213
it works on all 2.2 stocks with 3e.
if you are rooted using "one click root 1.7" (NOT ODIN ONE CLICK!!!) you dont need adb commands just root explorer to mount and replace file. or use adb to mount and push file. the instructions in the thread have the 2 methods mixed together.
no offence but ignore Liv33viL on this one
Trusselo said:
no offence but ignore Liv33viL on this one
Click to expand...
Click to collapse
Dude, that's just plain wrong. Let each person decide on their own who's advice to take and who's to ignore. It's an open forum and we all have the right to share our knowledge and experience. The focus here should be helping people get the assistance they need, not to diminish someone's credibility based on a personal opinion.
In short, grow up.
Trusselo said:
no offence but ignore Liv33viL on this one
Click to expand...
Click to collapse
ok, but then do u mean my bootloader is not damaged? can it be still repaired by using jig? can i restore nandroid?? but how 2 do so since my fone wont turn on at all?
What happens when you do turn it on- nothing? Or does it hang on the boot screen?
Sent from my SAMSUNG-SGH-I896 using XDA App
I had the very same problem. Your bootloater is boogered up now. I sent mine to an xda member and he fixed it.
Even with a jig I wasn't able to do anything. My phone would go into d/l mode with it but that was all it would do.
I paid $50 to have mine fixed which in my opinion is well worth it. That doesn't include shipping costs. I had connexion2005 fix it for me. He a great guy and does very fast work. It beats buying a new phone.
Hope this helps.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
All shameless advertising aside, it's worth trying a fix where others give up and pay someone. Through the process of elimination we can determine if you need professional help lol!
Sent from my SAMSUNG-SGH-I896 using XDA App
Thanks guys..will try connexion when the jig fails.
Sent from my SAMSUNG-SGH-I897 using XDA App
N does anybody know what to do, as my newly arrived cappy has a distinctive yellow tint to the screen. Do I call samsung and ask for a new one? Or is there some method to fix it by software?
Sent from my SAMSUNG-SGH-I897 using XDA App
Looking for data about flashing rom over other roms and their status of being stable. Feel free to tell whatever. Thank you.
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes. Try the serendipity q&a thread.
Caution swyping! Read at your own risk.
Thanks but I was hoping I could get serial flasher who flashes over this rom only to help me with this experiment. This experiment is only for froyo and not gingerbread.
Sent from my SAMSUNG-SGH-I897 using XDA App
I did, I flashed over serendipity and went to continuum. Serendipity works with ginger bread boot loaders.
Sent from my GT-I9100 using XDA App
Are you serious? Ginger bread bootloader? That is a first I heard. how you do it without getting bricked
Sent from my SAMSUNG-SGH-I897 using XDA App
Sigh...don't worry about gingerbread bootloaders unless you going to gingerbread. He was just saying the new bootloaders are backward compatible, why he brought that up idk.
Otherwise in cwm wipe data/factory rest, wipe cache, go into advanced wipe dalvik. Flash whatever froyo rom you want.
Thanks! Very much appreciated.
but I'm still looking for flasher who actually done it to list what type of rom they flash over serendipity and if it work properly.
I know some people who flashes and got good results and some with poor result.
Sent from my SAMSUNG-SGH-I897 using XDA App
studacris said:
Sigh...don't worry about gingerbread bootloaders unless you going to gingerbread. He was just saying the new bootloaders are backward compatible, why he brought that up idk.
Otherwise in cwm wipe data/factory rest, wipe cache, go into advanced wipe dalvik. Flash whatever froyo rom you want.
Click to expand...
Click to collapse
Beyond help.
jaydenboy said:
Thanks! Very much appreciated.
but I'm still looking for flasher who actually done it to list what type of rom they flash over serendipity and if it work properly.
I know some people who flashes and got good results and some with poor result.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
studacris wouldn't steer you wrong.
I gave you that suggestion because that's what I do I have been to stock like 6 times. Total. Flashed every rom over every rom.
If you have any problems after you flash over it, just flash back to stock like you normally do.
cappysw10 said:
Beyond help.
studacris wouldn't steer you wrong.
Click to expand...
Click to collapse
Lol, thanks for the endorsement ;p
Hold on a minute. no disrespect! I appreciate your response and answer. I'm looking for other people/flasher as well. I counted you already. I'm looking at the what rom and results after the flashing. That's all. So no disrespect to anyone. Trying to listen to whoever experience flashing over serendipity. And I thank you for your time.
Sent from my SAMSUNG-SGH-I897 using XDA App
jaydenboy said:
Hold on a minute. no disrespect! I appreciate your response and answer. I'm looking for other people/flasher as well. I counted you already. I'm looking at the what rom and results after the flashing. That's all. So no disrespect to anyone. Trying to listen to whoever experience flashing over serendipity. And I thank you for your time.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I don't really know what you are expecting to hear. A rom will wipe system/data/cache/dalvik so technically it IS a fresh rom. Flashing over an old rom doesn't affect ANYTHING in regards to the actual rom.
Sent from my HTC Desire Z
That is what I'm researching because others claim flashing over roms causes the new rom to not work properly while others have no problems at all. Then there are others who flashes back and forth to the same rom before and notice it doesn't work like it's suppose to when they had it the first time around.
Let me ask you...could it be titanium backup or bad flash. Could never really understand what a bad flash is technically.
Sent from my SAMSUNG-SGH-I897 using XDA App
lets put this into perspective, and think of it like your home computer.
on your phone, you have a few partitions. lets think of these combined, representing your C drive
/system /data /cache /datadata (these are the main ones to focus on)
when you format to load a new OS, there is NOTHING remaining of the OLD OS that could possibly cause conflicts. because essentially the drive is clean after the format and you load the new OS, and never see any traces of the old OS on the drive.
if you look at the update-script located in every single CWM flashable zip file, you will see a few things.
Code:
format SYSTEM:
format CACHE:
format DATA:
format DATADATA:
then after that you should see:
Code:
copy_dir PACKAGE:system SYSTEM:
copy_dir PACKAGE:data DATA:
copy_dir PACKAGE:updates TMP:/updates
this creates the new partitions, essentially for the system and data
as you can see, the rom flash will wipe the OLD system and data off and put a new one on. what is left from the old rom???
That about covers it lol
Thank you very much! So if some thing goes wrong then it's pretty much the file which results in a bad flash.
Sent from my SAMSUNG-SGH-I897 using XDA App
jaydenboy said:
Thank you very much! So if some thing goes wrong then it's pretty much the file which results in a bad flash.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
the only reason to go back to stock with ODIN prior to flashing is if you wanted to repartition and reset the file system. i did it many times while working on the Andromeda builds, because I wanted to make sure that coming from stock people would get the appropriate filesystem configuration and setup
Is there any problems you would encounter if you didn't have your partitions and file systems reset?
Sent from my SAMSUNG-SGH-I897 using XDA App
jaydenboy said:
Is there any problems you would encounter if you didn't have your partitions and file systems reset?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
very unlikely with the 2.2/2.2.1 roms. the kernel devs are pretty much all on the same page with using similar lagfixes that offer compatibility across the board. think of using ODIN and going back to stock as a last resort. 'when all else fails' type of thing
You said very unlikely. Its that part that I'm more interested in. The part that causes us to odin back to stock. When all else fail
Is there something that we do or is it the results from flashing too much that causes our partitions and file systems to go out.
Doesn't flashing reset our files systems and partitions?
Just letting you know that I am very grateful for your time and input. Your elaboration and explanation. You are helping way more than you know.
Sent from my SAMSUNG-SGH-I897 using XDA App
It's not caused by flashing too much, as far as your phone is concerned each fish is its first because it wipes first thing.
sometimes something just doesn't write correctly in cwm, for any number of reasons. thats whats known as a "bad flash." but that can be solved by a reflash. you would need odin if say the battery were to die during a flash and all you get is the "phone....!.....pc" screen
Hi all,
Sorry if i sound stupid, but I am new to all of this. I am trying to flash a gingerbread ROM onto my Rogers branded captivate. Currently I am running Rogers stock Froyo.
I have rooted and unlocked my phone using one click root, and the SGS unlock tool from the android market. I have also applied Ryans OCLF. I have busybox installed and the lasted version of Rom Manager.
However, every time i go to backup my stock rom using rom manager, nothing happens. I try to first flash the Clockwork Mod recovery, select the Captivate file and let the phone reboot, black screen with a yellow exclamation point in a white triangle with a Droid device laying under it. It will sit there forever until I manually restart the phone, at which point it acts fine.
I have backed up using titanium backup but cannot do it thru ROM manager. I have read countless forums, but it havent found a solution that works.
So i decided to proceed without a backup. I tryed to put the phone in download mode using the buttons so that I can flash it using ODIN but it doesnt go into download mode using any of the buttom press methods. I have tried to reinstall the packages from the boot menu, but i then get an error saying "e: failed to verify whole signature...."
I have also put a copy of the recently leaked gingerbread rom on my SD card and tried to install the ROM using rom managers install ROM from SD card, but i get the same black screen with yellow exclamation point and nothing happens until i maually start the phone.
I have no clue what I am missing? How to fix this? I have read and watched so many tutorials, followed all the steps. THey seem so easy on paper, but nothing that is supposed to happen, happens for me. Anyone have any suggestions on what I am doing wrong?
Please help!!
You need to follow installation instructions in the thread for whatever GB rom you are installing TO THE LETTER.
Which one are you trying?
You need to search for fixing the 3e recovery. 3e won't let you install custom roms. Also rom manager is just a gui interface for clockwork mod so in. wouldn't use it
Sent from my GT-I9000 using XDA App
cappysw10 said:
You need to follow installation instructions in the thread for whatever GB rom you are installing TO THE LETTER.
Which one are you trying?
Click to expand...
Click to collapse
I was trying to install the Official Gingerbread 2.3.3 for Captivate that was just leaked for the ATT captivate. I beleive the build number is I897UCKF1.
I do remember seeing the 3e recovery in the boot menu. Thanks alot, I will try to find a recovery fix and try that, then post the update.
Thanks alot for the suggestions so far. Its greatly appreciated!
Please for the love of all that is good in the world, do some research before you brick yourself for good. All of your issues would have not happened had you read more first before jumping in. I have seen far to many of these types if threads lately. Yes it takes a few hours to go through the threads but you save yourself the time you would spend (sometimes days) fixing your mistake.
zelendel said:
Please for the love of all that is good in the world, do some research before you brick yourself for good. All of your issues would have not happened had you read more first before jumping in. I have seen far to many of these types if threads lately. Yes it takes a few hours to go through the threads but you save yourself the time you would spend (sometimes days) fixing your mistake.
Click to expand...
Click to collapse
Your absolutely right, I did ALOT of reading, been doing so alot over a few weeks. Unfortunately, (or perhaps, I did not do enough digging) none of the tutorials, even the ones for beginners that i found on this forum mentioned anything about finding a fix for the 3e recovery. No one mentioned that the 3e Recovery bundled with the Rogers version of Froyo did not allow the install of custom roms, it also did not allow backups. Thanks to Crystalhand for letting me know this.
Anyway i found this link which helped:
http://forum.xda-developers.com/showthread.php?t=909213
I am FINALLY able to make a full backup image of my stock ROM and apps using CWM. This puts me more at ease now knowing i can also revert to stock if i install a rom that is not working properly for me.
The backup is completing as I type this. I will update again once I am able to install the gingerbread Rom I wanted to install.
Thanks again to all of you for the help!
that backup is not to restore the stock rom directly from whatever you flash. that is an imaage of your set up on stock rom. so you have to use odin to flash back to that stock rom you are on then restore that backup and it will be like you never flashed anything at all. if you just restore that backup onto the custom rom you flash it will not work properly.
the app backup your making with titanium backup will restore your apps on whatever you flash, but the rom backup doesnt work like that.
I would suggest using designgears odin 1 click, becuase no offence but you seen new and that would be least likely way for you to hard brick going to gb... Good luck
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Flashing is usually easy and safe (for the most part). But if something happends and it gets bricked u could always make/buy jigs. Easiest way to make I've seen is
forum.xda-developers.com/showthread.php?t=841512
Or you can buy them for about $8 maybe more depending your location (making em can cost less). The only thing I haven't tested the jig with is messed up bootloaders, example flashing gb bootloaders and flash froyo secundaries, everything else the jig works (atleast my experience)
Sent from my SGH-I897 running Cog 5 Beta 2
prbassplayer said:
Flashing is usually easy and safe (for the most part). But if something happends and it gets bricked u could always make/buy jigs. Easiest way to make I've seen is
forum.xda-developers.com/showthread.php?t=841512
Or you can buy them for about $8 maybe more depending your location (making em can cost less). The only thing I haven't tested the jig with is messed up bootloaders, example flashing gb bootloaders and flash froyo secundaries, everything else the jig works (atleast my experience)
Sent from my SGH-I897 running Cog 5 Beta 2
Click to expand...
Click to collapse
With messed up bootloaders you have to jtag
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
leezrd said:
With messed up bootloaders you have to jtag
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Well that's good to know. I'm not paying $150 for a jtag.
Sent from my SGH-I897 running Cog 5 Beta 2
$50 not $150.
prbassplayer said:
Well that's good to know. I'm not paying $150 for a jtag.
Sent from my SGH-I897 running Cog 5 Beta 2
Click to expand...
Click to collapse
Actually $50 by connexion 2005 but still expensive got something you don't need you to do
EDIT: Nevermind studacris beat me by a couple second to it
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
studacris said:
$50 not $150.
Click to expand...
Click to collapse
Oh? where?
Edit:
leezrd said:
Actually $50 by connexion 2005 but still expensive got something you don't need you to do
EDIT: Nevermind studacris beat me by a couple second to it
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Click to expand...
Click to collapse
Dosen't he charge $50 for a fix? not the jtag itself?
Mobiletechvideos.com
Hey hey hey....
i hav an captivate from at&t and its works perfectly fith the "stocks" firmwares, like 2.3.3, 2.3.4, 2.3.5, but when i flash something like CM10 or X-bean, salty etc, half times screen fault,
what can i do? i really want ics, or JB, i hate GB and froyo ....
Thanks!
joshua3001 said:
Hey hey hey....
i hav an captivate from at&t and its works perfectly fith the "stocks" firmwares, like 2.3.3, 2.3.4, 2.3.5, but when i flash something like CM10 or X-bean, salty etc, half times screen fault,
what can i do? i really want ics, or JB, i hate GB and froyo ....
Thanks!
Click to expand...
Click to collapse
We need more info.. What's your flashing process? Do you have gb bootloaders?
What exactly is the problem with the screen? Touch doesn't work? It flickers?
Sent from my SGH-I897 using xda app-developers app
First of all, forgive my English, im from Costa Rica
Right now, I have Gingerbread 2.3.5, baseband i897uckk4 with GB bootloaders, rooted with I897UCKF1-AutoRoot-DesignGears and CornKernel_UCKK4_v706 (sorry if I do not give good information, but I'm new at this ...), I can install any firmware 2.3.5 and down, but when I try to install a custom firmware, half of the screen fails to respond and other times if not, try many custom firmwares like: X-Bean 3.0, Cyanogenmod 10,9,7 stables, nightlies, AOKP, AOSP, MIUI (by flashing in CWM), and none served me perfectly, and I really want to at least have ICS, and if you could, JB, something I noticed is that whenever I installed a custom firmware, my baseband changed to "I9000UGKG3" when normally with stock firmware, was "I897UCKK4"
I hope it can fix it , thanks to everyone at XDA,
Greetings from Costa Rica,
BWolf56 said:
We need more info.. What's your flashing process? Do you have gb bootloaders?
What exactly is the problem with the screen? Touch doesn't work? It flickers?
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
First of all, forgive my English, im from Costa Rica
Right now, I have Gingerbread 2.3.5, baseband i897uckk4 with GB bootloaders, rooted with I897UCKF1-AutoRoot-DesignGears and CornKernel_UCKK4_v706 (sorry if I do not give good information, but I'm new at this ...), I can install any firmware 2.3.5 and down, but when I try to install a custom firmware, half of the screen fails to respond and other times if not, try many custom firmwares like: X-Bean 3.0, Cyanogenmod 10,9,7 stables, nightlies, AOKP, AOSP, MIUI (by flashing in CWM), and none served me perfectly, and I really want to at least have ICS, and if you could, JB, something I noticed is that whenever I installed a custom firmware, my baseband changed to "I9000UGKG3" when normally with stock firmware, was "I897UCKK4"
I hope it can fix it , thanks to everyone at XDA,
Greetings from Costa Rica,
joshua3001 said:
First of all, forgive my English, im from Costa Rica
Right now, I have Gingerbread 2.3.5, baseband i897uckk4 with GB bootloaders, rooted with I897UCKF1-AutoRoot-DesignGears and CornKernel_UCKK4_v706 (sorry if I do not give good information, but I'm new at this ...), I can install any firmware 2.3.5 and down, but when I try to install a custom firmware, half of the screen fails to respond and other times if not, try many custom firmwares like: X-Bean 3.0, Cyanogenmod 10,9,7 stables, nightlies, AOKP, AOSP, MIUI (by flashing in CWM), and none served me perfectly, and I really want to at least have ICS, and if you could, JB, something I noticed is that whenever I installed a custom firmware, my baseband changed to "I9000UGKG3" when normally with stock firmware, was "I897UCKK4"
I hope it can fix it , thanks to everyone at XDA,
Greetings from Costa Rica,
Click to expand...
Click to collapse
The I9000UKG3 is your modem(baseband), not your ROM (firmware), so don't worry about that. As long as you have signal, you're fine.
Before flashing a Jb ROM, do you factory reset, clear cache/dalvik? Is the screen problem right at the start? Do you restore your apps?
Do you have the I9000 bootloaders or the I897 bootloaders?
Hoy do i now what bootloaders i have ?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
joshua3001 said:
Hoy do i now what bootloaders i have ?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
When you boot your phone, do you see I897 or I9000?
Now do i now what bootloaders do i have?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
BWolf56 said:
When you boot your phone, do you see I897 or I9000?
Click to expand...
Click to collapse
It says at&t and a 3g animation and then galaxy s animation
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
joshua3001 said:
It says at&t and a 3g animation and then galaxy s animation
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Isn't there a black screen before the white AT&T screen? It would say SGH-I897 or SGH-I9000
BWolf56 said:
Isn't there a black screen before the white AT&T screen? It would say SGH-I897 or SGH-I9000
Click to expand...
Click to collapse
No wolf, it just boot directly to the white at&t logo
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
joshua3001 said:
No wolf, it just boot directly to the white at&t logo
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Ok, We'll start from the beginning then, You can get in download mode right?
Grab Odin KK4 without bootloaders, Corn kernel with Odin 1.85 and put the ROM (and Gapps) you wanna flash in the root of your internal SD. Flash KK4, boot up and make sure everything is fine. Once that's done, get back in download and flash Corn kernel.
From there, you can flash the ROM and the Gapps that go with it.
I believe you went through those steps already but hopefully we can find what's wrong by re-trying/reproducing the problem. Oh and don't restore any apps before trying it.
If that doesn't work, I'm thinking you might have the wrong Gapps or wrong bootloaders but first time I hear of a screen that doesn't work on JB but does on GB.
EDIT:
I just went through the thread to see that you already have KK4 and Corn on your phone. You don't need DesignGear to root, you can go in Corn's recovery to root your phone. Now, after re-reading, you said that sometimes it's iresponsive, what exactly do you mean by that? it takes a while to register your touch? locks up and you get no response for a few seconds?
Usually that's from lack of free ram. So a app sucking it all up. Have you tried JB (with the right Gapps) without restoring your apps?
PS.: You shouldn't restore your app with TiBu coming from GB, you can restore their data but should fresh download the apps from the market.
BWolf56 said:
Ok, We'll start from the beginning then, You can get in download mode right?
Grab Odin KK4 without bootloaders, Corn kernel with Odin 1.85 and put the ROM (and Gapps) you wanna flash in the root of your internal SD. Flash KK4, boot up and make sure everything is fine. Once that's done, get back in download and flash Corn kernel.
From there, you can flash the ROM and the Gapps that go with it.
I believe you went through those steps already but hopefully we can find what's wrong by re-trying/reproducing the problem. Oh and don't restore any apps before trying it.
If that doesn't work, I'm thinking you might have the wrong Gapps or wrong bootloaders but first time I hear of a screen that doesn't work on JB but does on GB.
EDIT:
I just went through the thread to see that you already have KK4 and Corn on your phone. You don't need DesignGear to root, you can go in Corn's recovery to root your phone. Now, after re-reading, you said that sometimes it's iresponsive, what exactly do you mean by that? it takes a while to register your touch? locks up and you get no response for a few seconds?
Usually that's from lack of free ram. So a app sucking it all up. Have you tried JB (with the right Gapps) without restoring your apps?
PS.: You shouldn't restore your app with TiBu coming from GB, you can restore their data but should fresh download the apps from the market.
Click to expand...
Click to collapse
All right, im gonna flash aokp_captivatemtd_jb_milestone-1.zip with gapps-jb-20121011-signed.zip, so, Turn off phone, enter cwm, wipe data/factory reset, wipe cache partition, wipe dalvik cache, flash aokp, flash gapps, fix permission and thats it right?
EDIT: I dont want to restore apps, i just want jb or ics, without that screen fail, the problem is that when i touch, it doesnt respond at all, but then 5 min later its works and then fail again, but just with the left side of the sceern....
joshua3001 said:
All right, im gonna flash aokp_captivatemtd_jb_milestone-1.zip with gapps-jb-20121011-signed.zip, so, Turn off phone, enter cwm, wipe data/factory reset, wipe cache partition, wipe dalvik cache, flash aokp, flash gapps, fix permission and thats it right?
EDIT: I dont want to restore apps, i just want jb or ics, without that screen fail, the problem is that when i touch, it doesnt respond at all, but then 5 min later its works and then fail again, but just with the left side of the sceern....
Click to expand...
Click to collapse
Sounds good. Quite often you don't need to fix permission, I never had to do it.
If screen fails again, I'm starting to think it might be a hardware issue.
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
Ok, We'll start from the beginning then, You can get in download mode right?
Grab Odin KK4 without bootloaders, Corn kernel with Odin 1.85 and put the ROM (and Gapps) you wanna flash in the root of your internal SD. Flash KK4, boot up and make sure everything is fine. Once that's done, get back in download and flash Corn kernel.
From there, you can flash the ROM and the Gapps that go with it.
I believe you went through those steps already but hopefully we can find what's wrong by re-trying/reproducing the problem. Oh and don't restore any apps before trying it.
If that doesn't work, I'm thinking you might have the wrong Gapps or wrong bootloaders but first time I hear of a screen that doesn't work on JB but does on GB.
EDIT:
I just went through the thread to see that you already have KK4 and Corn on your phone. You don't need DesignGear to root, you can go in Corn's recovery to root your phone. Now, after re-reading, you said that sometimes it's iresponsive, what exactly do you mean by that? it takes a while to register your touch? locks up and you get no response for a few seconds?
Usually that's from lack of free ram. So a app sucking it all up. Have you tried JB (with the right Gapps) without restoring your apps?
PS.: You shouldn't restore your app with TiBu coming from GB, you can restore their data but should fresh download the apps from the market.
Click to expand...
Click to collapse
BWolf56 said:
Sounds good. Quite often you don't need to fix permission, I never had to do it.
If screen fails again, I'm starting to think it might be a hardware issue.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
All right, i just flash the rom an gapps with this process...: wipe data/factory reset, wipe cache, dalvik, flash rom, gapps, and thats it....i will tell you how it goes...
Edit, im not gonna instal or update any app, just let it like that and see what happend....so now the boot process is, at&t white logo. the pink horse of aokp (XD), and thats it, no i897 or i9000 bootloaders, and when you say ¨it may be a hardware issue¨ what did you mean with that?
joshua3001 said:
All right, i just flash the rom an gapps with this process...: wipe data/factory reset, wipe cache, dalvik, flash rom, gapps, and thats it....i will tell you how it goes...
Edit, im not gonna instal or update any app, just let it like that and see what happend....so now the boot process is, at&t white logo. the pink horse of aokp (XD), and thats it, no i897 or i9000 bootloaders, and when you say ¨it may be a hardware issue¨ what did you mean with that?
Click to expand...
Click to collapse
Usually when you boot the phone, it shows SGH-897 but it doesn't matter, I could be wrong.
As for the hardware issue, just like some Sleep of Death (SoD) issue, it's something that a software can't fix, it's something broken within the phone (hardware). I don't know if it's the case here but it's always a possibility, especially if the phone was dropped before, the screen connector might need to be pushed back into place.
BWolf56 said:
Usually when you boot the phone, it shows SGH-897 but it doesn't matter, I could be wrong.
As for the hardware issue, just like some Sleep of Death (SoD) issue, it's something that a software can't fix, it's something broken within the phone (hardware). I don't know if it's the case here but it's always a possibility, especially if the phone was dropped before, the screen connector might need to be pushed back into place.
Click to expand...
Click to collapse
But why when I have the stock firmware that doesn't happend?
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
Usually when you boot the phone, it shows SGH-897 but it doesn't matter, I could be wrong.
As for the hardware issue, just like some Sleep of Death (SoD) issue, it's something that a software can't fix, it's something broken within the phone (hardware). I don't know if it's the case here but it's always a possibility, especially if the phone was dropped before, the screen connector might need to be pushed back into place.
Click to expand...
Click to collapse
Oh, and also, can I download I897 bootloader? and if I could, is gonna make any change?
Sent from my SGH-I897 using xda app-developers app
joshua3001 said:
Oh, and also, can I download I897 bootloader? and if I could, is gonna make any change?
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
You can get Odin KK4 with bootloaders. There's a risk of bricking your phone when you flash bootloaders though. There are needed to be on ROMs that are GB and up but I think you already have them.
As for the hardware thing, like I mentioned before, it could be like SoDs, where the phone will randomly shut off when you're using a ISC/JB ROM.
BWolf56 said:
You can get Odin KK4 with bootloaders. There's a risk of bricking your phone when you flash bootloaders though. There are needed to be on ROMs that are GB and up but I think you already have them.
As for the hardware thing, like I mentioned before, it could be like SoDs, where the phone will randomly shut off when you're using a ISC/JB ROM.
Click to expand...
Click to collapse
Hi wolf,
First of all let me thank you for all the help you gave me, let me tell you that if it was a hardware problem, then, as here in the office sometimes bring several of these phones, i change it for one XD and now it Works , im runnign aokp 4.1.2 Milestone 1 .... now, if not too much trouble, as last favor I say, you know if JB 4.2.1 roms for the captivate that are for everyday use?
really, really thank you......