yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z General] Spastic909:
as of today rom manager does it for you without need to change file names or adb
[G2 and Desire Z General] greensnow:
is there a mirror of the cwm3? Every time I click the link in the villian thread it takes me to a page of code I cant dl it :(
[G2 and Desire Z General] Spastic909:
in rom manager just click flash clockwork recovery......really not that hard guys
[G2 and Desire Z General] coredalae:
yep and the new 3.0.0.5 also works with older roms :)
[G2 and Desire Z General] KingAndroid:
CWM 3.0.0.5 Refuses to Flash

I am currently using CM7 RC1. I like it, but really need the gapps back and I cannot get them without CWM 3.0.x or later, as it turns out. I have tried adb, terminal emulator, renaming files and flashing within rom manager, and fastboot. I cannot get the new version to work with my G2, and would like to know if there is any other possible way of flashing it over. In case this comes up, rom manager currently says I am on 2.5.1.3, which I am, and just says the rom was flashed successfully whenever I try to flash the new version. And reverting to legacy versions produces the same result and I still boot into 2.5.1.3. Any help?
[G2 and Desire Z General] Shabazkhilgi:
I did try to flash the recovery with this method on HTC Desire, but it doesnot work, when i checked in recoveries folder i didnt find any .img file, rather i found a .zip file, please guide how ca i flash the Clockworkmod 3 , currently I am having clockworkmod 2.5.0.7
[G2 and Desire Z General] Travenport:
Dont mean to bump an old thread, but thanks OP this method worked for me.
[Captivate General] xnoctis93:
Hi I am running Perception(ver 5.UGJK3) so an older ver. of Perception.. on my Rogers Samsung Captivate... and have been having major battery drain issues. I turn off 3G and before I sleep battery level is at 76%. When I wake up(late due to my alarm not ringing), the phone is dead...what should I do to fix this. Is it the phone itself, or the fact that I am using an old version of the perception build...or an entirely different issue...? Thanks
[Captivate General] ninjuh:
Hard to say
[Captivate General] mcord11758:
What kernel us in that build? Phone is off charger?

If it is an oc kernel are you under volting?

Do you have wifi on?

Sent from me
[Captivate General] Palmetto_X:
1st

try to run the battery all the way down. Charge it over night while powered off.

2nd

http://xdaforums.com/showpost.php?p=10183875&postcount=4

Scroll down to Wipe Battery Stats and follow the instructions.

These made a big difference for me
[Captivate General] CHorden:
Palmetto has the right direction.

Keep in mind that it might just be your battery that sucks balls. You can alwaus pick one up for around $30.
[Sony Ericsson XPERIA X10 Mini] solari182:
Hi, im from chile and i have a problem with my house conection wi-fi :confused::confused:

i have a d-link router, when I activate the wifi on my phone, the connection lasts a short time and off.

I think it's a problem with the phone because the ipod touch the Wifi connection is very good!

I'll have to configure anything on the router or the phone??

will appreciate any help to solve my problem!!

thanks!
[Captivate Q&A, Help & Troubleshooting] jerry b:
Hi all,

I'll start by apologising if this should be posted in Q&A, but my question relates to recommended practice when flashing ROMs, and I think the people with the necessary knowledge are mostly in here. But please do move this topic to Q&A if that's where it needs to be.

Also, I want to stress that I'm not trying to start any flaming, and I don't even expect to end up with a single "right answer".

My own experience...

I'm pretty new to this - maybe 5 flashes so far. I read everything I could before my first flash (you guys have been a huge help and I salute the community here). It seemed nearly everyone was recommending flashing back to stock first (and Master Clear). The reason seemed to be that it gives you (more or less) a clean slate, and therefore the best chance of a trouble-free flash.

I have no development background, so I thought "Well, that sounds sensible. That's what I'll do." Four flashes with no problems.

In the last few days over in the Phoenix thread, there's been some discussion about the wisdom of flashing to stock before flashing a new ROM. (In summary, every flash is risky, so why do flash to stock when it's not needed? It's another opportunity for the fickle hand of fate to brick your phone. sbl.bin has been identified as a particular risk)

So this morning I decided to try the other approach. I flashed Phoenix 2 over 1.5 and everything is working fine.

So I've had 5 successful flashes.

The first 4 I started by flashing to stock.

The last one I flashed straight over the previous ROM (same kernel, same lagfix etc).

Both approaches have worked for me, so I still have a genuinely open mind on this.

So let me try to phrase this right...

1. What are the risks involved in flashing back to stock, and how easy is it to recover if something goes wrong?

2. What are the risks of not flashing back to stock first, and how easy is it to recover if something goes wrong?

3. Are there any rules that can help us decide whether the risk of first flashing to stock is greater than the risk of flashing straight from Cool ROM A to Cool ROM B?

4. Are there any good dev practices that could reduce the risks either way?

Like I said, I'm not looking to start a war.

It's just that I haven't really seen much said at this level of detail (especially question 3), and my brain likes to understand stuff. :D
[Captivate Q&A, Help & Troubleshooting] majinzen:
Personally, I just do a factory reset in CWM recovery before I flash anything new. I only flash back to stock when I want to get rid of voodoo and use something thats not compatible. I know you can disable voodoo but that takes forever compared to odin. I'm not that experienced but I've flashed over 100 times and the only thing that has ever broken my phone was the over the air update from att. I will never do one of those again. I agree with the consensus that flashing back to stock is unnecessary. Oh, and get ready for the this is in the wrong thread replies ;-).

Edit: I also use regular Odin and not the one click. I don't know why everyone uses it when there are so many complaints about it. Regular Odin is maybe 3 clicks.
[Captivate Q&A, Help & Troubleshooting] lrs421:
Mikey you should make that your new wall paper :-)
[Captivate Q&A, Help & Troubleshooting] majinzen:
Original, and totally agree.
[Captivate Q&A, Help & Troubleshooting] jerry b:
Uh oh. Thanks for the warning :)

I wonder if I can get it moved before I'm the one that gets all the flames. :(

Mods - please can someone move this for me before I get wedgied?
[Captivate Q&A, Help & Troubleshooting] sold1erjjt:
Yeah totally kinda here with ya. It would be "preferable" to be able to flash on the go. Just looking at the Vibrant Thread most ROM's are just flashed through CWM, no ODIN, no Master Clear. I know every device is different, but if it is indeed unnecessary that would be great. As well as it would be very nice to know if you can upgrade a particular ROM without a computer. Nero and Axura VE can... Well the Dev's do great and I more importantly think it is for the protection of our device and not having to deal with people complain about "how to fix it..." and "whats wrong..."
[Captivate Q&A, Help & Troubleshooting] 1tontomato:
I had the same questions myself even read some of the same sort of posts recently in the perception thread. Its been about six months since this phone has been out and maybe it's time to reevaluate what should be common practice. What was true in the beginning might not be true now.

Sent via Santa Clause thru the gingerbread cookies
[Captivate Q&A, Help & Troubleshooting] jerry b:
Looks like I didn't need to worry about a flame war. We've got a group hug going on.

I'm still hoping for some more information though, especially question 3.

When is it ok to flash straight from A to B, and what risks are we accepting when we do that?

Likewise, when is it better to go from A to Stock to B, and what are the extra risks? If flashing to stock is necessary, is 1-click more risky than n-click?
[Captivate Q&A, Help & Troubleshooting] delutedsoul23:
So can I flash perception...then a couple days later disable voodoo lagfix go into clockworkmod and clear data and factory reset. Then flash to another rom like pheonix...I know that's how I would flash on hatch aria...but I want to check and see if that's possible on the captivate
[Captivate Q&A, Help & Troubleshooting] MikeyMike01:
When will you people stop disabling the lag fix...

Sent from my Captivate.
[Captivate Q&A, Help & Troubleshooting] wpb2:
I had problems flashing to a new ROM without disabling the lagfix, so I always disable.

I never do a master clear, or Odin back to stock. I just CWM to the new ROM, but have always had horrible battery.
[Captivate Q&A, Help & Troubleshooting] mikewong27:
It will be awesome if we can install roms without losing all of our apps, settings, contacts, email, ect.. I just hate reinstalling all of my apps and reconfiguring all of my email accounts.
[Captivate Q&A, Help & Troubleshooting] mikewong27:
When you CWM to new ROM, do you lose all of your data, settings, apps ect...?
[Captivate Q&A, Help & Troubleshooting] jerry b:
Ok, so here's a good example of where we might get a better understanding of one part of the flashing process...

So this sounds like disabling the lagfix is unnecessary. But on the other hand...

Wpb2, can you remember which old & new ROM(s) you were flashing when you got the problems? Maybe there are features of those ROMs that (in hindsight) we can understand why the flash didn't play nice without a lagfix.

Maybe it tells us "when flashing between ROMs that differ in feature X, we should always disable lagfix".

Or maybe it identities something that the flash scripts could do, to take the guesswork out of it.

Or mybe time has moved on, and the same problems wouldn't happen today - maybe the "disable lagfix" days are behind us, but we're continuing to do it when we don't need to?

I don't have OCD or anything. :) It just seems like each procedure (disable lagfix / flash to stock / other procedure) carries a risk. So if we can figure out when the procedures are necessary / redundant, it will help us reduce the risk of trying to flash a cool new ROM and ending up with an expensive brick?

BTW, I appreciate the replies so far, and I apologise for my delayed reply - I'm in New Zealand (and also I've gone for a few days mountain biking but left my charger cable at home, so I'm nursing my battery a little).
[Captivate Q&A, Help & Troubleshooting] existz:
The only time i disable lagfix before I flash a new rom is if, say i have all partitions formatted as JFS and the rom im flashing is using a kernel I want and it only supports ext4, for example voodoo, then I disable it, cause the new kernel wont support my old file system and that leads to something bad...but say I have Hardcores kernel already flashed, and all my partitions are ext4 and the rom im going to uses the same kernel or something similar (say Glitterballs, or Setirons kernel (something else that supports ext4) then there shouldnt be any reason to disable it.. Ive flashed probley, atleast 15-20 times from voodoo to either Setirons kernel or Hardcores kernel WITHOUT disabling voodoo for the simple fact of having /system ext4 instead of RFS...and ive never had a problem..thats just personal preference though, I just prefer my /system partition ext4
[Captivate Q&A, Help & Troubleshooting] Jirv311:
No offense to anybody at all but this thread is like a "should I format my hard drive before reinstalling Windows" thread. Sure it may work if you don't but why risk it? Especially if you're installing a ROM for testing purposes. Why not start clean and eliminate any bad/old files that could eventually cause problems? Just my $0.02.

I personally always Odin to stock, master clear and flash new ROM. Never an issue.
[Captivate Q&A, Help & Troubleshooting] jerry b:
No offence taken at all. Thanks for replying.

You're kind of right about the "should I format my hard hard drive" thing, and I wouldn't want to waste anyone's time just asking that kind of question. I'm actually asking for information that will help me know which approach to take, in which circumstances.

existz's post was exactly the kind of education I'm looking for...

So now I know how to decide whether to disable lagfix...

Do the old ROM & new ROM (kernels?) support the same file system?

If YES: I don't need to disable lagfix.

If NO: I do need to disable lagfix

This is probably obvious to you guys (thanks for not flaming me & my noob questions that might be in the wrong forum). But it's good education for folks like me. Now that I've learned that flashing to stock / disabling lagfix carry their own risks, so I don't want to do them if I don't have to.

Not much education so far about the risks of flashing to stock, but I should probably just let this thread die. It's a shame though. There are plenty of opinions for & against flashing to stock, and there seem to be smart & respected people on both sides. I just can't find any information.

Thanks everyone for your replies, and particularly to existz. I'm just a little bit smarter now than I was when I posted the topic. :)

As for flashing to stock - given that it carries the risk of serious brickery (and the risks of not flashing to stock seem minor by comparison), I reckon I'll be following the flowchart on page 1 from now on.

Unless someone posts some more education to explain why that's a dumb ass move. :D
[Captivate Q&A, Help & Troubleshooting] GGXtreme:
The response is going to vary based on both people's experience and their phones. I never flash to stock before installing a new ROM, I simply wipe data and cache using CWM before installing, then restore my apps and contacts with Titanium Backup. I've never had a problem with this method.

But here is where things get a bit complicated. Why don't I flash back to stock? It's not because I'm lazy or because I like taking risks. It's because (in my case, as well as with many others) my Captivate can't be flashed to stock JF6. The closest I can get is JH7, which requires flashing to JH2 first, a much riskier and less simple process.

For me (and supposedly others), attempting to 'one-click' my phone (or use another version of Odin, including the 3-button fix version) is a 'success' message in Odin, followed by a bricked phone, no ADB connection and no button combos. Time to break out the jig again...

I can't agree that it's generally less risky to flash back to stock first, as you still use a non-official method of writing to your phone's ROM, which is just an additional chance for a full-brick (corrupted sbl.bin means you need RIFF JTAG to fix). For custom ROM's that don't include this file (and no-wipe ROM's), there is a significantly reduced chance of really messing things up. At worst, you might not get past the boot screen, or you might get some FC's, and then you can either wipe and try again, or move onto flashing stock if nothing else works.
[Captivate Q&A, Help & Troubleshooting] 1tontomato:
I spent a lot of time reading threads again today serendipity and phoenix and noticed at least once someone had issues understanding how clockwork actually works. They didn't understand that the update zip that rom manager puts on the root of the sd card is what loads clockwork, and that reapplying the update zip loads it compared to applying a zip from sd_card is a different operation all together.they can be used the same, but they are missing the small diffences of the operation. Something that more experienced users are missing is just how much clockwork has changed in six months. Now it's in the kernal and has many more features. The problem is the stock answer for fixing problems flash to stock instead of learn to use clockwork better. As of yet I haven't seen any good guides for clockwork, and all the lag options, at least not the pages and pages of how to flash stock which really could use a good rehashing.

Sent via Santa Clause thru the gingerbread cookies
[Captivate Q&A, Help & Troubleshooting] alaimar:
I agree.

Sent from my GT-I9000
[Captivate Q&A, Help & Troubleshooting] opcow:
I personally always don't odin, master clear or disable lagfix and I have no problems.

As for your Windows install analogy, you aren't starting clean. What you are doing is more analogous to installing Windows 7 by formatting your hard drive, installing Vista, then formatting your hard drive again and installing Windows 7.

Have you ever looked at the cwm log when it's installing? Have you ever opened up an install script and read what happens? Partitions are formatted and directories are deleted. Everything is wiped. If that process fails somehow you damn sure don't want eclair files in the mix. You accomplish nothing by flashing to stock other than the inherent risk when flashing via a USB connection.

Disabling lagfix is almost always a waste as well. Have you noticed that your recovery can now work with ext4?
[Captivate Q&A, Help & Troubleshooting] jerry b:
I guess this sums up why it seems like flashing stock is a redundant extra step. Like I said up front, I'm not looking to start any wars. But if opcow's summary is correct, is there really any need to flash stock?

A guide like that would be great.
[Captivate Q&A, Help & Troubleshooting] GGXtreme:
Good way of putting it.
[Captivate Q&A, Help & Troubleshooting] dizx:
I'm gonna give this a shot for my next flash and see how it goes. Sacrificing a pig to the gods before I do can't hurt and hope for the best. :)

EDIT: Scratch that. I'm all themed out and from what I've recently read, it isn't too smart to flash over that stuff. Can anyone confirm that?
[Captivate Q&A, Help & Troubleshooting] jerry b:
From what I can figure out, the questions are:

1. Disabling lagfix - do the old ROM & new ROM have the same file system?

If YES, no need to disable lagfix.

2. Flashing to stock - I'm afraid I still haven't figured out if there's a question that helps you decide whether to flash stock.

All I can say is that, in the discussions I've been able to find, I've seen people explain why flashing stock is risky and also why it's not necessary, but I haven't seen any explanation about why it's more risky when you don't flash stock. (That's not to say that those reasons aren't out there. But if they are, I haven't been able to find them.)

So I'm going to continue following the flowchart on page 1.

Good luck with yours. :-)
[Captivate Q&A, Help & Troubleshooting] jerry b:
Yeah, I get that same impression. :)
[Captivate Q&A, Help & Troubleshooting] opcow:
What do you meant themed out? You added a theme? Makes no difference.

And if you are under the impression that flashing right over the old ROM is risky and flashing to stock is 'the better safe than sorry' route, quite the opposite. If your phone gets bricked it'd going almost always be either during the stock flash or because the stock flash disabled your button combos.
[Captivate Q&A, Help & Troubleshooting] dizx:
It was your previous posts that got me convinced to try the more "direct" method.

Yes, I added a theme.

Even before I saw your latest response, I decided to flip my middle finger at the whole thing and just go for it. Seems to be going fine at the moment. 50% done reloading apps with TiBu.

I was coming from Perception 10.1 themed with R64's look and got the itch to try out Cezar's Continuum SE ROM to see what that's all about.

Of course, having a jig just in case is a good thing, too. :-)

UPDATE: Everything seemed normal after the flashing, but I tried to reinstall Busybox and it was unable to due to Nandroid being locked. Never ran into that before, but then again, I always flashed back to stock before trying this. Was there something I should have done? All I did was went into CWM Recovery and flashed the new ROM. Flashing back to stock like I know how until I really know what I'm doing.
[Captivate Q&A, Help & Troubleshooting] jerry b:
I can't shed any light on that - I always just fire up Tibu & press the "problems" button which automatically installs the latest busybox.

Not that I know what a busybox is. :D
[Captivate Q&A, Help & Troubleshooting] 1tontomato:
This is exactly what I was thinking, but the part of the equation that is missing is the distinction between wiping a directory and formatting a drive, which I thought involved a zero back fill. Is this what happens in odin when we master clear? If I go into settings I also find a button for format sd. Inside of clockwork there are lots of places where I can "wipe" data. To make an even further distinction the rom I'm on now is "clockwork ultimate lag kernal" it has many places for deleting specific portions of the rom, as well as being able to mount Usb, possibly handy for recovery puroses, and nobody seems to try to use these features for recovery or getting that clean chaulk board we're chasing, by odin stock, master clear, flash rom.

After many pages of reading through rom threads yesterday any time someone says they have a problem The first reply is almost always, "did you flash stock?".

this often works but nobody is asking why it works, or what are the practices of the people who ignore this altogether and are just fine.

Just stating because I don't think we understand clockwork too well as a recovery tool, and steam recovery is just around the corner.

Pheonix 1.0 haters edition "best battery life ever"

Sent via Santa Clause thru the gingerbread cookies
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
I can usually get away with using CWM and re-flashing the new ROM.

But I will ODIN back to stock when going to a NEW ROM just to be on the safe side. But.. I don't usually have to do the extra steps of rooting and downloading ROM Manager... I just use the CWM Update.zip that I have on my SDCard.

It takes me 15-20 minutes to restore my phone back to the way I like it and ODIN usually takes like 2 minutes. So 2 minutes for my own feeling of security and well-being is worth it IMO. :)

And sure I know that the ROM's out there today format and re-write all of the directories, sbl.bin, etc.. - but if there were any gremlins from the prior ROM - I'd rather not take the chance to have it migrate to the new ROM I was flashing to.

For most people - especially the NEW PEOPLE TRYING TO FLASH (Looks at you n00bs out there...) I'd always take the safe route and not have to see another Q&A post of OMFGBBQSAUCE MY PHONE IS BRICKED !!!11110111!!!!!111!11001 thread. :rolleyes::D
[Captivate Q&A, Help & Troubleshooting] jerry b:
Hey, you're looking at me! :)

Thanks for the replies. I guess this is why I started this topic. There are so many people who feel more secure by flashing to stock, but from the stuff I've read, it seems to be an extra risk for no reason. I'm all about reducing the risk of bricking my phone, so I'll go with the approach that minimises that risk. Just based on what I've read, I feel like the safer route is to not flash to stock.

I do still have an open mind, and if there's an explanation somewhere of how flashing to stock reduces the risk of bricking, I'd go back to that approach. But that explanation doesn't seem to be out there, so I'm going with:

Plan A - flash the ROM without flashing stock.

If I get a problem - go to Plan B, and flash stock.
[Captivate Q&A, Help & Troubleshooting] avgjoegeek:
Just make sure you read the chef/dev's recommendation when installing the ROM - it will save you from Plan C - Returning back to AT&T for a Warranty replacement :D
[Captivate Q&A, Help & Troubleshooting] opcow:
Even if it is true that flashing to stock solves some problem, what does that tell you? Maybe the problem would have been solved by simply installing the ROM again. If you are particularly anal about these things you could just routinely CWM install twice (unless it's a DesignGears ROM with sbl.bin included, in which case I really wouldn't do unnecessary flashing).
[Captivate Q&A, Help & Troubleshooting] opcow:
But what are you saying is the safe route? For a noob, it's definitely not an odin flash of boot.bin and sbl.bin.