Database Develop

[Q] Help! lag fix problem

I was attempting to perform the lag fix on my phone and long story short, i pushed the wrong button. I now have the 1 gb partitioned somewhere on my phone, but that is where the process stopped. How can I get my memory back to normal so that I can perform the lag fix the correct way?? Any other ideas would be also be considered. Thanks for your help!

Which lag fix were you using? They all work a bit differently

Thats the bad part. Im not sure which version I was doing. I was attempting to do this through adb when the lag fix first came out for the Captivate. I was probably a little over my head but have always been pretty quick at picking up technical things. Would flashing back to stock rom using Odin fix this problem?

jdstigler said:
Thats the bad part. Im not sure which version I was doing. I was attempting to do this through adb when the lag fix first came out for the Captivate. I was probably a little over my head but have always been pretty quick at picking up technical things. Would flashing back to stock rom using Odin fix this problem?
Click to expand...
Click to collapse
An Odin flash should do it. If you're using one of the old style lagfixes like the Tayutama update.zip or the One Click Lagfix, it's just a bubble living on RFS so it gets wiped out with a flash easily. If it was voodoo the newer versions of it wipe with an Odin flash as well- so you should be fine

Zilch25 said:
An Odin flash should do it. If you're using one of the old style lagfixes like the Tayutama update.zip or the One Click Lagfix, it's just a bubble living on RFS so it gets wiped out with a flash easily. If it was voodoo the newer versions of it wipe with an Odin flash as well- so you should be fine
Click to expand...
Click to collapse
dont you need the disable-lagfix if he installed voodoo and wants to odin flash?

andy2na said:
dont you need the disable-lagfix if he installed voodoo and wants to odin flash?
Click to expand...
Click to collapse
Old versions required it... newer versions supposedly don't. I always manually disable it either way, I don't want to chance the BS that I had to put up with back in the day when odin didn't touch it =P

Zilch for mod...

New recovery 3.0.0.5

Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny

I don't see why not. You can try and if it don't work you can flash an older version in ROM Manager

vinnyjr said:
Can this new recovery be used to flash CyanogenMod 6.1.1??? I just got the new recovery update on rom manager and was going to flash cyanogenmod 6.1.1 and just checking. I thought the new recovery was for flashing Gingerbread roms?? Any help would be appreciated.
Thanks,
Vinny
Click to expand...
Click to collapse
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.

I guess I won't find out until I try. Newly rooted and going to give CyanogenMod a try. Know I am going to be happy as hell with it.
Thanks

The new recovery should be fine with flashing any roms. As for any standing problems with it, im am uncertain. You may want to wait 2 weeks or so to see if their are any problems from people using it. Personally I like Amon ra so i cant say.

ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
Click to expand...
Click to collapse
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?

mikeacela said:
A full wipe is necessary to upgrade to gingerbread roms from any lower android versions. Did u full wipe? + Dalvik cache wipe?
Click to expand...
Click to collapse
Yes. I did full wipe on everything. I even fix permission. No luck at all.

ricky9237 said:
I am not sure about that. But one thing for sure is it is not good for MM's CM7. I have loop-reboot problem with this. I cannot even restore to any custom roms except my froyo stock. :-( Now, I have to downgrade to 2.5.x.x to see if my custom roms work again.
See development section.
EDIT: I successfully restore other custom roms using lower version of Clockworkmod. But the loop-reboot problem of MM's CM7 remains the same.
Click to expand...
Click to collapse
I used it to flash and install tonight's build successfully...

I have a "side question".
To flash any GingerBread flavor, do we need 3.x.x.x ou 2.5.x.x is working?
I haven't give CM7 a try yet, but I'm not sure if I need/want to upgrade to 3.x.x.x, 2.5.1.4 work well for me.

DumbUglyDragon said:
I used it to flash and install tonight's build successfully...
Click to expand...
Click to collapse
I got it too. No more crazy rebooting. I solve it by reformatting my SD card and recreating ext3. I guess 3.0.0.5 recovery messed up my ext3 partition. Now, MM CM14 is working pretty well. FYI, I am using 2.5.1.4 recovery.

Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.

doesn't work with MIUI for me!
don't understand that, but luckily its not a big deal flashing older versions!

baseballfanz said:
Yeah it was working good till I try to do a restore, lets just say I;m up all night trying to restore my phone. I think my EXT partition messed up too as DTa2sd is giving me all kinda of headache.
Click to expand...
Click to collapse
I hear you there! That was me last night! DON'T USE 3.0.0.5! The only fix I found to actually work was to completely format my SD card and then re-partition it, then use RA and a fresh install. What a pain in the arse!

Same thing here. Switched to 3.0.0.5, and the next thing, my ext was fried and I had to reformat the entire card. Could be coincidence, but...
Sent from my Nexus One using XDA App

[Q]Do YOU Flash To Stock?

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

[Q] Why go back to stock 2.1 before each flash?

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

[Q] flashing custom rom 1st time

hi
im on 2.3.4 stock and rooted and i have converted file system to ext4 before backing up.(is that safe) or should i convert to rfs? and then backup?
im kind of scared to flash custom roms, i wana flash ics onecosmic.
i did a backup in CWM now if i flash ics rom and something goes wrong can i just revert back to previous firmware by doing a restore in CWM?

Sure!
If you had backup everything (most important thing is ROM) and with the term everything I mean EVERYTHING (mp3, images on SD etc etc) you can now flash from CWM the .zip you want.
I'm on teamhacksung's one (still ICS) so I don't know well the procedure to flash it,
but on the thread it's all documented!
Hope to have another ICS soon !

ext4 doesnt matter?
i just flash roms thats it?

If you wanna be 100% sure "downconvert" to RFS again, backup again, then flash what you want!
2 backups is better than 1.

xunair said:
hi
im on 2.3.4 stock and rooted and i have converted file system to ext4 before backing up.(is that safe) or should i convert to rfs? and then backup?
im kind of scared to flash custom roms, i wana flash ics onecosmic.
i did a backup in CWM now if i flash ics rom and something goes wrong can i just revert back to previous firmware by doing a restore in CWM?
Click to expand...
Click to collapse
I suggest you to revert back to rfs before flashing any custom ROM.
Lagfixes can cause problems when flashing and go back to rfs isn't harmfull or complicated.
Than follow exactly what is written on the OP of the Rom of your choice and you're ready to go.
When you have everything backed up, in the worst case of a bad flash you can always go backwhit your NANAD backup or to stock with Odin and Download mode. I was scared like you but now I flash ROMs like crazy even if I'm not so experinced!

ok im gona do it now
thanks alot guys

stesancri said:
I suggest you to revert back to rfs before flashing any custom ROM.
Lagfixes can cause problems when flashing and go back to rfs isn't harmfull or complicated.
Than follow exactly what is written on the OP of the Rom of your choice and you're ready to go.
When you have everything backed up, in the worst case of a bad flash you can always go backwhit your NANAD backup or to stock with Odin and Download mode. I was scared like you but now I flash ROMs like crazy even if I'm not so experinced!
Click to expand...
Click to collapse
man we are all crazy!!
flashing ROM is kind of a second job 4 me!!

bedo1987 said:
man we are all crazy!!
flashing ROM is kind of a second job 4 me!!
Click to expand...
Click to collapse
True! Once you try that...you'll never come back!

be sure
just be sure of what you were doing read understand all of the instructions, im a bit confuse lately but the urge of me having a custom ROMs running on my GS make's me realize i can do it, but of course by the help of our fellow android user..if i can do it u can also..anyways give it shot...

you are now entering a new and fantastic world,
dont be shocked when you struggle to keep the same Rom installed for a whole week

pzayx said:
you are now entering a new and fantastic world,
dont be shocked when you struggle to keep the same Rom installed for a whole week
Click to expand...
Click to collapse
Hehe, more like 2 days it seems for me..
Good luck.

I did it yesterday for the first time... (flashing a Rom ofcourse ) And it was easier than I thought! Just do it.

It's just about follow the instructions!

bedo1987 said:
It's just about follow the instructions!
Click to expand...
Click to collapse
And experience.

jsolhac said:
And experience.
Click to expand...
Click to collapse
bedo1987 said:
It's just about follow the instructions!
Click to expand...
Click to collapse
And self research with the help of XDA and Google

People are saying its hard to brick SGS.
There is 1 golden rule backup whatever you can before flashing (most important thing is backing up /efs partition because there are all data describing your individual phone egz IMEI number).
When I flashed ICS I couldn't get network signal so I had to restore my /efs and it worked.

It is hard to brick when you can get inside recovery & download mode, otherwise not so much ;-)
Only play around with ROM's if the 3 buttons combo work

Well i got my I9000 3 days ago and i already bricked it twice!
Well after you do the same thing with more than 2 phones, you set lol

josueciz said:
Well i got my I9000 3 days ago and i already bricked it twice!
Well after you do the same thing with more than 2 phones, you set lol
Click to expand...
Click to collapse
Twice same phone? then it look like you didn't bricked it at all.
For me and probably most of people definition of bricking is:
-you cant get into download mode (semi brick)
-you cant get into download mode using a jig plug (only service can help you then but warranty doesn't cover this so it depends on luck)
-you lost your /efs (no backup anywhere) (only service can help you then but warranty doesn't cover this so it depends on luck)
-and I guess other option could be you messed up with bootloader and cant reflash it ;/