I got a 2nd hand Bell Galaxy S Vibrant off craigslist. It is rooted (when I got it). It's still running 2.1 and the 2.2 update is available.. Now before I proceed with updating it, I want to make sure that there's no lagfix installed. How can I tell? I already did a factory reset. I also went to recovery mode and wiped the phone from there. Anything else I should do?
Could just run quadrant, unlagfixed phones would probably be about 1k or less, those with the fix are way higher
thanks for the tip!
Related
Hi my phone has recently had the froyo build from keis using the reg hack and it's definately worse than before. I want to do the following but just want to check its a good idea/ best way.
I want to do a factory reset (to clear out any 2.1 garbage hanging around)
root the phone
install a lag fix
possibly install another fw
I have backed up the apps I car about with astro I was then going to do a factory reset
Then root the phone with SuperOneClick
Then install CFLagFix
Then hopefully my phone would stop behaving badly.
Also a bit worried about the fact I used the keis hack should I have waited for the uk release? How will I be able to install the uk froyo build when it is released?
Is there a fw with all this stuff pre done which would work better?
(another question is there any fw out yet which support the wii mote?)
Thanks
Sorry also had another question. Is it a good idea to install another launcher and if so whats the best way to do this is there some kind of lite rom I can install which wouldn't come with all the anoying smasung stuff and touch wiz?
I upgraded to Froyo via the reg hack, and having not done a factory reset, it was slow as **** even with OCLF.
But once I installed voodoo, it was like night and day. Vastly faster than 2.1 ever was, even with OCLF. And I still haven't done a factory reset, and probably won't.
Hi, im planning to do a sidegrade from doc's jpa v7.5 to the kies one.
And really would like to know how to get my phone as close to fresh as possible.
Like how to get rid of clockworkmod(or does it get gone by flashing a new firmware with odin?) Also how can i delete vodoo for good? i used it on a earlier firmware and used the disable lagfix folder way to disable it. Will it work just by deleting the whole folder?
The reason im asking this is tht i feel theres getting a lot of junk in my sd card and would be really nice to know how to get it away .
Well as no one wanted to tell me , i did a try and figured it out myself .
First removed lagfix(wich bricked my phone), luckely i had download mode.
Flashed jm2 with odin, let kies update my phone to jpa.
Then i did a factory reset,wipe cache, and format sd card!.
Installed Voodoo 5 pre6 , busybox, superuser.
Then i had jpa with vodoo and rooted so i could use titanium to get my apps back .
Gotta say so far this is a very good firmware, except the browser maybe, havent tested it so much yet.
I have a Stock 2.1 Samsung Galaxy S I9000M from Bell and suddenly I noticed it would not boot anymore. It shows the model number, then the "M" would disappear and go on with the boot movie (for a good 5 min) then just blank out and freeze.
I had the Voodoo lag fix applied to it but it has been working fine until today.
What should I try doing on it?
Thanks!!
knightdaemon said:
I have a Stock 2.1 Samsung Galaxy S I9000M from Bell and suddenly I noticed it would not boot anymore. It shows the model number, then the "M" would disappear and go on with the boot movie (for a good 5 min) then just blank out and freeze.
I had the Voodoo lag fix applied to it but it has been working fine until today.
What should I try doing on it?
Thanks!!
Click to expand...
Click to collapse
That is strange. From what I read here in the fourms, the symptom of the missing "M" is related to flshing an international firmware but you say your device is stock... Is that correct?
I would start by removing the voodoo lag fix and then doing a factory reset. If that does not work then you may be one of the unlucky people (mostly us here in Canada with the i9000M) whos internal sd card has failed after applying the lagfix.
If anyone else has any info to share or if Im incorrect then please let me know.
Yes, the device is stock (updated through unhacked Kies) + Voodoo.
SO I have disabled Voodoo and then performed a reset in recovery mode. Then another reset through the phone's normal interface.
Currently restoring everything through Titanium then reapplying Voodoo.
knightdaemon said:
Yes, the device is stock (updated through unhacked Kies) + Voodoo.
SO I have disabled Voodoo and then performed a reset in recovery mode. Then another reset through the phone's normal interface.
Currently restoring everything through Titanium then reapplying Voodoo.
Click to expand...
Click to collapse
The other thing to keep in mind is that the voodoo lag fix actualy flashes a "non stock" kernel to your device so again... It MAY be the voodoo fix that is causing the "M' to disappear as it is compiled on an "international" kernel.
Perhaps if you NEED a lagfix you should use oe that does not modify the kernel itself but be warned... It seems that the lagfixes contribute to the internal sd card deaths that I previously mentioned.
PS... I thought Titanium coul only be used on a rooted device? Are you rooted? If so then your device is NOT "stock".
It would make sense for the "M".
Yes, I'm rooted, I thought root doesn't redefined stock
knightdaemon said:
Yes, the device is stock (updated through unhacked Kies) + Voodoo.
Click to expand...
Click to collapse
Wait, "updated through unhacked Kies"? Is it on JH2 eclair, or on some froyo variant? If the m disappears, it sounds like you used the reg hack on kies to update to an i9000 version of froyo
It is JH2, I bought the first batch of Samsung Galaxy S in Canada, it had another version beforehand. I do not have froyo yet, waiting on the official version.
knightdaemon said:
It is JH2, I bought the first batch of Samsung Galaxy S in Canada, it had another version beforehand. I do not have froyo yet, waiting on the official version.
Click to expand...
Click to collapse
Ah, ok, I understand now. I have no idea. I've only seen the m disappear when you run a i9000 firmware
Hello Experts,
I'm looking for some sort of check list when I receive my phone to ensure that my phone does not brick again or that I have a solid phone at that.
What sort of things should I be looking for in terms of firmware date, what type of firmware is installed etc?
Should I be seeing JL2 on it? Should the date be 10.12 or higher? Should I ensure download recovery works? etc, ,,, Does anything else come to mind?
Previous phone was an unlocked Bell GT-I9000M with stock JK4 installed, Froyo 2.2, rooted with lagfix. No other custom roms installed.
Thanks in advance.
You might want to tell us 'how' you bricked it?
sturmeh said:
You might want to tell us 'how' you bricked it?
Click to expand...
Click to collapse
Updated the phone to Froyo 2.2 via keis.
Rooted it with SuperOneClick
Installed OCLF.
That's it. Worked great for 3 weeks, then noticed some force closures occurring. Reformatted the phone, pulled down all my apps from myroot backup. Updated all the apps that I had installed. Apps kept crashing and FC's still occurred. Pulled the battery, restarted the phone and that was it.
I have a Galaxy S which i rooted and installed a lagfix on. I think it was Ryans OCLF i used for the lagfix.
I want to update to the official Froyo available from T-mobile via kies but having lots of problems getting it to connect (as everyone does). I have backed up contacts etc. I havent bothered backing up apps as i just wrote down the settings i have in each one and will just reinstall them after the upgrade.
What im planning on doing was completely resetting the phone back to factory settings and wiping it altogether so i have a clean phone to do the upgrade.
The problems im expecting or want to know how to avoid is with the root and lagfix i have installed. Will doing a factory reset or other reset (hopefully somebody can tell me another way of resetting) get rid of the root and lagfix or do i need to do something manually before wiping the phone? I know of something about the lagfix creating partitions etc so would a factory reset cancel the lagfix or would it cause all sorts of problems?
How do i go about removing the lagfix and resetting to the standard software that came with the phone? Also i have apps that require root so if i unroot the phone will this cause problems when they try to start or will they just not work and not be an issue?
Im not running any custom roms just the original one that came on the phone.
Sorry for all the questions and a rather long first post but im hoping to do this soon as the phone is running like a bag of smelly brown stuff lol.
Disable the lagfix first and then wipe. Root will not go away but I dont think that would be problem.PS. If I would be you I would just use odin to upgrade, there is plenty of good guides including how to use odin
Undo lagfix before any firmware upgrade .Then factory reset then go to Kies .
Remove lagfix as per the instructions with whatever lagfix you used .
Unroot not a problem its only a user administrative rights fix giving you greater access .
Personally i undo anything i can before an upgrade .
jje
Yes i would definitely undo everything before upgrading its just a question of how i do it.
I used Ryans OneClickLagFix app that was on the market at the time but now it has been altered because it allowed you to root and google didnt like this. I still have the original version i downloaded on the phone so is it just a case of clicking on "remove lagfix" and that will sort it?
Also if the root remains on the phone after i have wiped it, will this cause any problems when i put froyo on it? Is there not a different method or file for rooting froyo to the one i have used on 2.1?
on "remove lagfix" and that will sort it?
Correct .
jje
Also click Remove Ext2 Tools, and the go into the Scheduler changer and return it to CFG and uncheck the tweak buttons, if you messed with any of that.
In which order should i do all of those?
Should i remove the ext2 tools and return cfg settings etc to default before i remove the lagfix or after?
So just a quick update.
Something went totally wrong the other night on its own. This is before i had even thought of upgrading that night. Was sitting on facebook happily playing away when it started force closing within a few seconds of opening. Tried to open the market to reinstall the facebook app and the market force closed in a few seconds. It did this with every app including the email and phone etc. Even the RyansOCLF would forceclose so i couldnt remove the lagfix or unroot etc. All my settings for apps and launcher pro settings had disappeared. Only a couple of icons i had set on the home screen of launcher pro remained but i couldnt use any of them. All my phone logs were there and so were my texts etc but everything else had reset. When i tried to reapply some of my settings and then restart the phone, when i had finished the restart the settings i had reapplyed had defaulted again. Disaster!!
The only thing i could do was run a factory reset from the options menu. I crossed my fingers hoping this wouldnt brick the phone and alas it worked perfectly. Sorted out kies and connected the phone and installed 2.2.1 android. The lagfix had been cleared by the factory reset. I keep wondering if this is why i had so many problems with it taking ages to start up before. Maybe because the lagfix never really worked properly it never fully rebuilt the file system so was removed easily? Although the benchmarks were coming up double the speed of the fastest device on the results so not too sure how it was performing so fast with a duff lagfix...who knows. Anyway got it all up and running and rooted and lagfixed using the voodoo fix. Stuck launcher pro on setup everything. Got the apps i previously purchased reinstalled and restored any apps i wanted from titanium backup. Works like a dream and alot better memory usage aswell.
Thanks for all the help guys but it seems although i didnt follow any of the instructions you all posted (not out of choice...just because the phone physically wouldnt let me) it seemed to get the upgrade done without any problems.