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...

No Custom roms are able to install after Axura 2.0

Every single one of them are failing @ System.
I have flashed many roms and have yet to see this issue.
I have even tried to install a nandroid and they say system.img not found, skipping restore of System
my quadrant before doing anything was ~950 so im assuming no lagfix was present.

did you flash back to stock with odin1click??

ed116 said:
did you flash back to stock with odin1click??
Click to expand...
Click to collapse
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...

iamamp3pimp said:
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...
Click to expand...
Click to collapse
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.

im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm

ccdoggy said:
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.
Click to expand...
Click to collapse
+100000000

iamamp3pimp said:
im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm
Click to expand...
Click to collapse
Because it is the phone...not the rom or kernel...unless you had a bad flash to begin with.
This is why it is recommended when switching to different roms...and even sometimes flashing updates to certain roms ...that it is the most prudent thing to do, to head off these types of issues that come up sometimes. It is also recommended to do a master clear as well...and I usually go one step further and wipe and format the drives and do a factory reset. Sometimes doing it more than just once too. It may be a royal PITA...but...the alternative is what you are experiencing it seems...
Mac

is there a way to tell which filesystem is being used?
i have CWM 2.5.1.2
my Axura restore did work.......so i at least have a phone for the moment

[Q] Restore to Stock

I was hoping to flash Paragon tonight, but it said to flash to stock first and I had a few questions.
Why do some ROMs have you flash to stock while others you can just flash through ROM Manager?
Is the Stock backup I made through ROM Manager sufficient as a subsitute for an Odin flash?
If not, are there any Mac alternatives out there?
I'm trying to get a good understanding of what I'm tooling around with so I don't brick my phone.
Thanks for the answers

I wish I could answer all your questions, I'm guessing it's because the recovery uses a zip file and it does not update everything that odin would. Anyways, if you need any help flashing to stock I know that the FAQ page of the cognition rom found here has directions.
cognition.theidiotshideout.net/mw/index.php?title=ODIN#One-Click_JF6

It is not needed but many think it is best. Depending on the rom you are on you have a cocktail of lag fixes and kernels. Flashing stock gives a clear slate.
You can disable lag fix, delete davlik cache, clear cache. You should be fine but you may run into issues. May.
What are you running?

It's some sort of ancient lore past down from priests of captivate forum antiquity.
As for 'cocktails of lag fixes and kernels,' there is no reason your cwm install can't format those partitions, particularly in light of the fact that it has built-in support for ext4. I don't know why people think the stock flash functions are particularly better at dealing with it.
Do yourself a favor, make sure you have a working download mode combo, purge your mind of the flash to stock FUD and obliviously commence to flashing one froyo ROM right over another. You'll be glad you did.

So if I'm hearing you correctly, it's more of a this will make sure you have no issues and are starting from a clean slate. It's not 100% neccessary to flash to stock before flashing a new rom?
Meanwhile, I was furiously trying to get Odin to work on an old laptop I scrounged up to no avail. Sometimes my need to tinker creates so many problems.
Thanks, guys!

wmbenham said:
So if I'm hearing you correctly, it's more of a this will make sure you have no issues and are starting from a clean slate. It's not 100% neccessary to flash to stock before flashing a new rom?
Meanwhile, I was furiously trying to get Odin to work on an old laptop I scrounged up to no avail. Sometimes my need to tinker creates so many problems.
Thanks, guys!
Click to expand...
Click to collapse
It is like a default disclaimer to flash stock. If you flash the rom and have an issue, one if the first things they will ask is did you flash stock. As mentioned almost all lag fixes use some form of ext 4 filing and most clockwork recoveries can now handle ext 4.
So in summation you do not need to, if you flash and get stuck in a boot loop you need to. I would make sure you can get odin up and running, and recognizing your phone in either case just so you know you can use it if needed

Absolutely no need at all to flash to stock
Would you install Vista in order to install Win7?
As long as you format everything in CWM before you flash a new ROM, then everything is a clean slate. It'll wipe your stock install, so why install stock first?
This and the 're-calibrating' your battery are the two biggest FUDs about Android.

[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

Anyone else paranoid about flashing ics?

With so many horror stories being posted, I don't know what to believe. When will it be relatively safe for us to update to ics?
I came from an HD2, and that was a treasure for flashing different roms. But it seems like the note is so easy to brick.
Edit: All I've done so far is root my note using Dr. Ketan's method.

It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.

I've flashed dozends of ROMs on my old HTC desire including ICS. At the end it worked always fine.
1. Backup
2. Wait after flashing - some roms need their time. After 10 min I've sometimes put out the battery to restart...
3. Enjoy
So don't fear!

I'm waiting for ICS OTA also. There have been lots of mixed reports with the previously leaked ICS ROMS - some bricked and some not. I've had a great run with flashing GB ROMs and Kernels but will wait for more official versions.
BTW - A colleague has a Note about four weeks old bought via the web. It turned out to be a German handset and he was successfully able to flash via KIES. I'm jealous - my Note 6 months old and I am still waiting for official ICS !

If you dont have any crazy combination of rom with custom kernel and cwm then is fine
Just dont wipe before flashing
And wipe after flashing
Sent from my iPad using Tapatalk

The fact that we have had ANY bricks at all suggests to me that this is not safe to flash, and even though I have been able to successfully flash LPY and run it, (not without problems), the bit that concerns me is the bricking due to large file copying which has been mentioned by various people.
Since I regularly copy large files to and from the device, I do not plan to subject my device to testing the theory.

I flashed ics yesterday and everything went fine, Iam always paranoid when comes to flashing but research before actual flash is vital! SEARCH button overheats and Iam ALWAYS following instructions!
Dont know what would I do without xda and those so capaple devs!
Galaxy Note!!!

I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.

nandihno said:
Just dont wipe before flashing
And wipe after flashing
Click to expand...
Click to collapse
Why is it safe to wipe after flashing and not before? I thought it was the other way around?

neos_83 said:
Why is it safe to wipe after flashing and not before? I thought it was the other way around?
Click to expand...
Click to collapse
It is the other way around.
Anyway, I fear this might be another superbrick in the making...
http://forum.xda-developers.com/showthread.php?t=1653290
And another one...
http://forum.xda-developers.com/showthread.php?t=1649982

vetchems said:
I have flashed LPY a total of 3 times so far without any problems. I have wiped/deleted cache etc etc. The Bricks are all related to modified kernels and CWM. If you you use the stock LPY kernel then all will be fine.
I have also flashed CM9 several times and had no issues what so ever.
If you need root on LPY best method is to flash a GB rom and get root, then use mobile odin with the everoot option to flash LPY.
DO NOT flash the CF Root kernel, This is where problems may start. Keep it Stock and all should be fine.
Click to expand...
Click to collapse
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.

to answer the original question... no... because i thoroughly read as much as i can find before i flash anything...even google it to see if there are problems ... hence i have ics rumming and running without any strange issues...

tbong777 said:
This is exactly what I did...
Mobile Odin Pro inject SuperSU and everroot......NO CF ROOT had a good GB ROM and Kernel. Only wipe done was done by Mobile Odin Pro
No I am 100% stock IPY with root...The fun will start when I begin flashing custom ROMS. Will need to flash CWR for that.
Click to expand...
Click to collapse
I decided I did not want to "tip toe" around my normal processes with this device and went ahead and flashed CF Root with CWM. Going to need CWM to flash Roms and the LPY kernel has nt proven to be all that safe either. There is at least one case of a Superbrick wiping from Stock Recovery.
I bought these devices to mess with. I have a back up S2 and the s3 is out....Worst that can happen is I sell for parts.

well i am lucky so far as i dint have any issue with my note even after flashing lpy somany times from cwm may b me lucky till now

I'm terrified of flashing any roms on now after all the horror stories. I honestly don't even really care if I have ICS. I just hate how slow the stock ROM is. I would be very very happy with CM7 with SPen functionality.
This kind of sucks coming from an LG G2X which had so many stable roms and kernals to choose from
I thought a Samsung phone would have had even more but I guess not.

Probably like everyone else, I read Entropy's thread and became SUPER paranoid. He said there's no way to tell if you're slowly degrading the emmc or not unless you're on a 100% safe kernel / rom. I'm confused about the rest of the details. Apparently cm9 is 100% safe, but even the official ics can brick our note if we still have reminants of a leaked ics rom / kernel?
People alot more knowledgable than me have been bricking their note, so I will wait for an idiot proof method.

I would luv to see a step by step guide on video.
Also still dont grasp the fact that even if we put an official ics from Germany will won't get upgrades.
Sent from my GT-N7000 using XDA

I've been using lpy since release, and although I've had no problems so far, don't have cwm just root, but the more posts IM reading about people experiencing bricks from many different methods is definitively scaring me.
Chasmodo is a very reputable developer as is Entropy. I heed their words and will flash back to GB today, it's just not worth the risk.
Sent from my GT-N7000 using xda premium

Thijsvr said:
It's mainly horror stories. Dozens, if not more already flashed to ICS without any problems. Of course there is occasionaly someone with bad luck, but that is also on the OTA updates. Every now and again something goes wrong, but it's a small chance and usually you are still able to fix it afterwards.
So just stick closely to the manual, don't cut corners and you'll probably be okay.
Otherwise, just wait for the OTAs. That's what I'm doing, but that is mainly because I'm a little lazy. However when I got the ICS kernel I'll put vanilla ICS over it.
Click to expand...
Click to collapse
I also initially thought it was all speculation and anecdotal evidence. However, it appears that at least one user who has upgraded a brand new Note via Kies to LPY and wiped immediately thereafter has bricked his device.
That being said, I updated via PC Odin, rooted with temp CWM and full wiped from stock recovery thereafter without any issues (so far, been 3-4 days now). The performance improvements that ICS brings are significant, IMHO.
Basically, update if you really want to and refrain from wiping if possible (i.e. if you are not facing any FCs etc).