Should I update to froyo? - Droid X General

I just got my droid X, and heard that the froyo update ota was having a lot of bugs and such, but that was a while back. My droid is still in 2.1, is it best to leap onto 2.2, or just stay at 2.1 until 2.2 bugfixes are made? thanks.

It's got its bugs. Battery Manager details crashes most of the time (Vz found the issue in early Oct and will inlcude in a soon to happen maintenance release) and exchange push doesn't work unless you're on E2K10. Most everything else reported (slowness/lag) is because ppl didn't hard reset after the OTA push.
Not the best release on the planet but worth it IMO.

I'd update and the do a factory reset (wipe data/cache). If you don't want to reset your phone don't bother. It will have issues.

I've noticed huge improvements regarding battery life. Also, having Flash has been nice, I've used it quite a bit with Local News sites. But yes, there are bugs. You will definitely want to do a hard reset after update, or else you'll constantly get apps needing to be forced closed and it will run sluggish.
Get Appbrain before hard reset, it will sync and push all your apps back after reset. Quite nice for lazy people like me.

Same kinds of questions. Droid X, still at 2.1, rooted with EasyRoot, and I have heard all kinds of conflicting info on the upgrade to Froyo and its many variations.
I know enough to be dangerous, and not enough to feel safe.
First, I have downloaded all the TeamBlackHat ROMs including their deodexed 2.3.1.5, and I think I perhaps would like to try that one first, if it is any better than the Verizon standard upgrade.
It is, or does it have the same issues?
Is any other ROM better and more stable ... eg the Tranquility 3 from the BlackHatters?
I hear that the EasyRoot does not work with the Froyo ... and does the phone stay rooted if I do the ROM, does it risk a crash and burn in the middle of the process, should I do the SuperOneClick rooter either now to replace EasyRoot or later or both or.....??
Can I start from where I am, or do I need the Verizon upgrade first or some other way to go?
Am I asking the right questions here? I have read so much about bricks on the upgrade process, especially with the early Froyo leak, and do not know just what to do. The answers on the web keep changing.
Thanks for any help and advice!

Don't worry about bricks. That's why we have the SBF. It fixes that. Also, upgrade to OTA then swap ROMs. If I'm not mistaken, the new ROMs run on the newest bootloader.

Verizon upgrade to Froyo and then ROM remaining questions
Thanks ... am downloading the SBF now in the form of the_gift2.zip so I have it if I need it.
So I understand that I do the Verizon official Froyo update, then I guess I need to reroot the phone as mentioned above (?). Then I can do ROM installs from that point, and have the SBF as a failsafe if it messes up (?)
Anything else that I need to know or be ready for?
Does re-doing the root now with SuperOneClick do any good, or will it all need to be redone after the Verizon update? The root issue is my biggest question. Do I need to kill EasyRoot , and should I go to superoneclick now, and will it hold through the Vz upgrade?
Seems I need the hard reset in the middle of this, after Vz install, with data/cache wipe, as Sleuth225 and Toddman mentioned above, (preceeded by Appbrain backup of the data), ... but is it needed if I will go to a subsequent ROM install such as the TeamBlackHat 2.3.1.5 anyway (That is, will the ROM install fix the issues mentioned by Toddman and Zehkaiser above?).
Maybe this is a dumb question, but I am just trying to understand the steps. I have Titanium backup rooted, but again, if I loose root, will that one leave me hanging without a way to get back? Is Appbrain the one that is most reliable for this situation?
I really appreciate the help ... am a noob at this and tying to learn as fast as I can. Want to be sure I get it right the first time.

Related

trying to understand my options

I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom? I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
dbldown768 said:
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
Click to expand...
Click to collapse
As of right now; many people are cautious about testing the latest 2.1 leak; because of the concerns you expressed earlier -- having your phone unrooted by the 2.1 leak when you flash the new update. So, with that said; the current 2.1 ROM's are all pretty stable. This new leak, however probably is as well, but again... I don't know whose all tested it, for fear of loosing root access.
dbldown768 said:
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom?
Click to expand...
Click to collapse
No. Damageless ROM's are also based on the latest Sprint leaks. All ROM's you see should tell which ROM they are based off of. Almost all 2.1 ROM's are currently built from any of the Damageless ROM's -- just read the front page of the ROM you're looking into.
dbldown768 said:
I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
Click to expand...
Click to collapse
1. Possibly. The lag problem is relative to the person/device. Not everyone experiences this problem. However, turning off "Vibrate when typing" apparently helps with the lag issues. YMMV.
2. Please see first post I made.
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
As far as how to root, I recommend the command line method. While the auto-root methods are nice, actually doing it yourself will give you some experience with things you're gonna be using.
Yes, loading the update.zip to the root of the SDCard is the standard way to flash.
No, not using Apps2SD is not a problem, most people use it because they have a faster SDCard, which gives better performance when loading apps.
A Nandroid backup is something that you will do before you flash any update.zip (At least you're supposed to). It's basically an "Image" of your phone exactly how it was the point in time that you made it, so if you flash something and everything goes horribly wrong, you can restore said nandroid, and it will be like it never happened. (The exceptions are flashing a radio and screwing with the PRL/PRI, nandroid doesn't touch those.)
dbldown768 said:
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
Click to expand...
Click to collapse
Fresh's kitchen will allow you root your phone and yes it's stable. However, it's best you try doing it via ADB commands, as there will come a time when you'll want to create things for the community and wished you had prior experience using it. I recommend you trying to root via this tutorial HERE If you follow the directions, you shouldn't have any problems whatsoever.
Stock card is perfectly fine; you're able to use Apps2sd, but don't have to.
dbldown768 said:
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Click to expand...
Click to collapse
To try out different ROM's -- the process is to download the file (which is a update.zip file in itself), but has been renamed to match the name of the ROM. All you have to do is; copy to your sd card, boot into recovery, flash ROM from the sd card, reboot.
abcdfv said:
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
Click to expand...
Click to collapse
There's your real answer. Thanks.
I'm having a hard time understanding why i would need the flash recover image in this tutorial (http://forum.xda-developers.com/showthread.php?t=583291)? I understand i would want to do a backup of the current phones state, but why would i flash anything before actually making this backup? Maybe i'm not understanding the process correctly, but i just want to get "su" ability and then do the nandroid backup? Is the nandroid backup an app i use?
Nandroid is built into the recovery image you're flashing. Before flashing the recovery image, there is no way for you to nandroid.
thanks! after watching the youtube video posting that mad more sense. So i know there is a chance of bricking your phone during all of this, where does that chance increase? Is it during the flashing of the customs roms, not so much the rooting process?
It is safe to say once the "official" 2.1 android comes out there will always be a custom rom based on it? meaning that if chosen by developers here there could be a build off the "official" 2.1 with the only difference is the rooted user is still allowed? I know that most dev are going to change the build in someway to "improve" on what the official build is done.
The only proven way to brick this phone is by flashing a GSM radio, or by having a failed RUU. I've never heard of anyone getting a "true" brick from rooting/flashing ROMs.
Yes, once the official build is released, all ROMs from then on are most likely going to be based of off it.
Ok, stupid question. I just followed the guide to rooting my phone, doing the nandroid backup and copying the backup to my pc. There are a lot of guide to root, but how to you actually flash the custom rom? I saw something about holding down the 'home' button when starting up? Does this bring you to the recovery image again? Do the roms have to be named something specifically?
Place the ROM in the root of your sdcard, and boot into recovery by holding Home+Power. From then select the "Flash update.zip" option and it will show all of the .zip files in the root of your sdcard. Just pick which one you want to flash.
great! thanks for all the help.
ok, so i decided to load damage's sprint leak that would still give me root access, well it doesnt boot. just goes to the "sprint now" screen and reboots over and over again? any ideas?
Did you wipe data and Dalvik?
Anytime you go from one ROM version to another (1.5 to 2.1, 2.1 to 1.6, 1.6 to 1.5, etc etc) you have to wipe, or if there's major changes between rom versions.
what do you wipe the data? i just picked the flash from zip file from sd card?
In recovery there's a catagory for wipe. Wipe data and Dalvik, then reflash and you'll be fine.
cool. thanks. trying that now.
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
There's Easytether and PDAnet. I haven't tried Easytether, since last I've heard it's x86 only, but PDAnet was a horrible experience. I just flashed an Eris based ROM, broke my PRI, and it enabled the built in USB tethering.
dbldown768 said:
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
Click to expand...
Click to collapse
go to market and download barcode scanner
open up barcode scanner and go here and then just point the camera at the qr code and it'll download to your phone.
remember to check 'unknown sources' > setting > applications
wifitether 1.6. works flawlessly on either fresh or damageless latest 2.1

[HOW TO] Steps to Take to Prepare a Rooted Phone for Warranty Exchange

I recently had to give up my rooted preordered Incredible for a refurb due to heat issues and reboot (loop) issues. For those looking for a guide as to what to do if you have to return your phone to Verizon and want to unroot. I welcome any comments to update/add to this information:
1) Make a NANDROID Backup if you want to simply port it over to your new phone
2) Mount your phone as DISK DRIVE
3) Walk the directories and delete any cached thumbnails of web sites you have visited
4) Copy any pictures you want to keep which were saved on the phone
5) Reboot into ClockWork recovery
6) Wipe the Dalvik Cache
7) Wipe the Data/Factory Reset
8) Go back
9) Wipe Data (main menu)
10) Power Down your phone
11) Remove your SD Card
12) Download one of the RUU's which are hosted around the web:
http://www.shipped-roms.com/shipped/Incredible/
13) Turn on your phone and plug it in to your USB
14) Run the RUU and let it do it's thing. When its done, so are you
15) If you have a screen protector, remember to remove it.
Any additions are welcome!
Yes it will revert everything back to normal, that's called an RUU btw
Cool
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
if i root and uninstall some apps, will this restore my phone to stock and allow me to get all future HTC updates?
jdmba said:
Anyone know if this also removes the more hidden data, such as the cached images of the web sites you have visited? In other words, if I run the RUU, is the phone ready to just be handed over?
Click to expand...
Click to collapse
I don't think so, but it's easy enough to do a wipe and then apply the RUU (and hey, for the hell of it, you could wipe again).
Steps?
[deleted ... first post updated]
I'm pretty sure the RUU will completely wipe your phone. However, you can take giantcrazy's advice and wipe before running the RUU.
One more try
[deleted ... first post updated]
Ok, here is what you want to do.
there would be two things you need to un do before sending them back this phone.
make sure it says S-ON.
and then make sure you have stock recovery.
If you have these two things, your gold bod.
Probably to noob to know any better
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, big thanks for any suggestions
A Lex and Er said:
After going through a lot of threads this one seems appropriate. I am looking for how to go back to stock DI. After Unrevoked3, ota leak and unofficial froyo leak, my DI wont connect to VZW anymore, all out going calls are busy. Talked to my VZW guys, they are cool with me, tried to help nothin'. Today tried Unrevoked forever and official froyo leak, still no VZW connection. I looked into this a lot before I tried these mods I don't know what went wrong, I would not have been able to do this with out such easy tools as are provided today. "I NEED HELP" to get back to stock, "PLEASE". I have looked into SDK and Adb, as I have been lead to believe there is no way to return to 2.1 and the right radio without these tools. At this moment I have not been able to find clear enough explanations on how to use these tools, this is where I maybe over my head. I assume my radio is fried, I don't care if no "S on", I just need those obvious things; version, kernel, baseband, to be stock. Any help will be appreciated, thanks
Click to expand...
Click to collapse
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
ACD168 said:
Ok, there is so much here I will do my best.
number one, having s-on is just as important as having a radio thats either 2.15x or 1.x, now that the OTA 2.2 update is sending out, you can send the phone back with 2.2 and 2.15x radio.
what you need to make sure of, is two things, you have s-on,
and you have stock recovery.
Click to expand...
Click to collapse
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is not as thrilled about my learning experience as I am.
I already rooted and unrooted once, will I get stock recovery back after unrooting?
A Lex and Er said:
Thank you, and really they wont know if the ota was pushed to me? I found the S on tool, I didn't know there was one, I had only read on about S off. I don't know how to find/replace stock recovery, I will start searching though. Much appreciation, my better half is as thrilled about my learning experience as I am.
Click to expand...
Click to collapse
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
A Lex and Er said:
I already rooted and unrooted once, will I get stock recovery back after unrooting?
Click to expand...
Click to collapse
To find out real fast if you have the stock recovery or clockwork-mod recovery, boot into HBOOT, (power off phone, hold vol down and power til screen turns on) and then vol down to select recovery and push the power button I think to select and then if you get a red triangle that means stock recovery.
Also need to return phone
I just got off with Asurion and they are over nighting a replacement. I had rooted my phone, installed some root only apps like wireless tethering and set cpu, removed some bloat like CityID and Tweet/Peep, and changed the boot animation. No custom ROM or radio update.
Then I wanted to get the OTA update so I applied s-off and flashed back to stock recovery.
So what do I need to do to return this phone. I know I will need to apply s-on. Then should I flash a stock 2.1 or just revert the changes I made to boot animation, restore the bloatware, and remove the root apps? Do I need to remove any other files that go with being root?
Thanks.........MM
ACD168 said:
Your welcome, I'm happy to see you are learning so quickly. S-on is very helpful for those warranty returns of the phone.
Verizon has no idea whether or not you got the ota, or better yet what version you have or if you are rooted, ect.
If you tell me what your hboot it, radio, software version, s-on or s-off, if rooted or not, and if you have the stock recovery or clockwork and I will try and guide you to where you want to be..
if you need help getting to the stock recovery this must mean you are rooted, and this can be achieved by downgrading the phone by un-rooting, I'd suggest running s-off while you are rooted, then
androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html
sorry can't post links yet,
to help you un-root and get that stock recovery back.
Click to expand...
Click to collapse
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
A Lex and Er said:
Hello,
I wanted to thank you again for the help this last weekend. I apologize for not returning for more of the help you offered me. My wife only has every other weekend off and we have an 18mo. old son, both of whom deserved my time more than my DI. I love my DI but it wasn't giving me much love.
Although VZW isn't always the nicest to my pocket book, I have never been taken care of as well by any other provider(s) employees, thank you. As I mentioned in my first post, my VZW guys are cool with me. Yesterday I went into the store and the manager offered to help me. He managed to reconnect my DI to the network but no 3g's. He believes my problem is just a coincidence because he had another customer with a similar problem over the weekend, with no mod's. Still I need to exchange my DI, it doesn't look like 3g's is going to turn on.
My real issue is still getting custom recovery off and stock recovery back on, then unrooting will be a breeze. The videos you lead me to are one of the sources I have been working with, however to reverse the leaked ota, Downgrade leaked ota video, requires SDK and adb knowledge, this is where I am noob. At this time my VZW manager who is in school for programing is attempting to help me (he has a over clocked Palm Pre Plus, 1Ghz), this is very cool of him, well beyond what is expected. (I am in no way encouraging anyone to rely on their VZW employees for this kind of help, this is a unique situation, I have been building a relationship with my VZW guys for two years+, not all VZW employees have a clue about mod's, and mod's technically void the warranty) I am hoping to learn enough about these tools, SDK and adb, to help myself before the next time, and I will hopefully be gaining some of this knowledge from my friends at my VZW store soon. I will also be looking forward to the help I receive from fine people such as yourself and people in this community in future endeavors.
I will stop basically hijacking this thread now
Thanks to all of the people who support these community's, with out whom many of us would never get our foot in the door. Much appreciation to ACD168 for being there to help me.
Take the time and learn to do it right the first time.
Click to expand...
Click to collapse
First off, you are very welcome my friend, anything I can do to help do hesitate to ask!, and your not hijacking any thread brother, that's what these threads are for!!!
Thats real cool of the VZW employees!!
adb and sdk isnt that difficult I can help you!!
Read my post about warranty exchange.
I know alot of people are "better safe than sorry" mentality. but I have returned 2 phones that were fully rooted, updated, s-off running custom roms and I had no issues. in fact ive never had an issue using warranty exchange. ive exchanged phones that I broke (like broke.. with pieces coming off). I just call and tell the operator lady my phone doesnt work, i dont know why.. it was just working earlier and now it wont turn on.. they send me a new phone and I send back the broken one and everyone is happy.
They only confirm that the numbers on the phone match your account. Not the reasons you are sending it Back. the warhouse guy that opens your box isnt the same guy you talked to, nor do they have information about your phone call to the tech. They simply open the box, scan the numbers and move on.
dont stress to much about it
Great info here
Thanks to every one of you on this thread. I am finally breaking free from WinMo and getting Dinc after a lot of research. I like Verizon but hate the bloatware they pack onto Androids and all the other phones, so I will be fiddleing with ROMs. If I screw up I am looking here first to see how to get it back to stock so I can get my new one with the insurance coverage.
Everytime I get to serouosly looking around these forums I learn great new stuff. I will donate to the XDA someday soon!
Okay. so im a noob. Just need to ask. What do you guys mean by stock recovery? I just rooted my phone but need to unroot to send it in for work at Verizon. Could you help me out?

You probably shouldn't delete stuff from /system after OTA...

Just my $0.02
I don't necessarily think it is a good idea to delete stuff from /system after applying the OTA. From what I understand, there is no (known) way to revert to the original firmware, and if you happen to delete something on /system POST-OTA, there is a very good chance that you will not be able to apply future updates, due to the recovery not finding the file(s) necessary to patch. Same issue people who deleted Google Goggles had prior to this OTA, however, in this case, we did have the escape route of flashing the stock firmware, then applying the OTA...
Best bet at the moment:
Temp-root via VISIONary, fire up adb shell or a terminal:
Code:
# pm disable [i]package_name[/i]
Or use the "freeze" function in Titanium Backup.
Thanks, rmk40!
yea thats what i was thinking also. paulobrien made a theard about titanium removing apps from /system but how would your be able to revert in case of an update?
I dont think you can because we cant downgrade
I agree.
Besides, using "pm disable <package_name>" via adb shell is just as effective as removing any app, without any of the risks.
its easy to revert back to stock... so its not really a big deal, I removed a Sh1t load of apps I don't use and will continue to mod anything electronic i own.. its called customizing and modification which this forum seems to be mainly for.. but u'd def make a good htc rep.
wheeliest said:
its easy to revert back to stock... so its not really a big deal, I removed a Sh1t load of apps I don't use and will continue to mod anything electronic i own.. its called customizing and modification which this forum seems to be mainly for.. but u'd def make a good htc rep.
Click to expand...
Click to collapse
it was easy to revert....THIS TIME. from what i can gather, the g2 isnt able to be downgraded. witht he last ota...people flashed the base over to get the apps back to original....but next time you wont be able to flash the same file cuz it'll be considered a downgrade.
i'm definatlely gunna stay clear of /system til the great devs we rely so much upon finally scream victory against HTC/eMMC. then i'll be back to the heavy mods.
the stock rom isnt bad. its vinilla, and the hardware of the g2 makes up for it. everything seems to fly without a hiccup of anykind.
wheeliest said:
its easy to revert back to stock... so its not really a big deal, I removed a Sh1t load of apps I don't use and will continue to mod anything electronic i own.. its called customizing and modification which this forum seems to be mainly for.. but u'd def make a good htc rep.
Click to expand...
Click to collapse
With the quality of your thoughts HTC wouldn't hire you to be their janitor. Good luck with the next OTA!
wheeliest said:
its easy to revert back to stock... so its not really a big deal, I removed a Sh1t load of apps I don't use and will continue to mod anything electronic i own.. its called customizing and modification which this forum seems to be mainly for.. but u'd def make a good htc rep.
Click to expand...
Click to collapse
What did you gain from removing them, though?
Nobody is saying you shouldn't remove them because it is naughty or immoral or icky. It's true that we have the capability of removing the apps if we want to, and that is a good thing. But, in practice, this interferes with upgrading when fixes come out and it may be a lot more of a hassle the next time than we saw with this OTA(*). So, for now, until permanent root comes along and we can flash whatever ROM we want, it's not a smart thing to do when there are other ways to achieve the same ends.
It would be one thing if you actually got the space back, but since the pre-installed apps are on a fixed partition that you don't need extra space on, removing them provides no more value than disabling them.
(*) I'd be curious, though, to know if anyone has proven that flashing the original stock system doesn't work after the OTA. As far as I know the Android update mechanism doesn't enforce strictly increasing ROM versions (people were flashing the original G1 ROM after several updates had happened - it was the standard way to root the device). All it would take would be one guinea pig to do the fastboot reflash of the original ROM on top of their OTA'd device to know if it will work.
Minimally, though, having to reflash the original ROM in order to add a patch or update means your phone gets wiped and you have to deal with the hassle of restoring it to working order - hardly a decent tradeoff if disabling the apps does the trick with fewer ramifications...
havikx said:
but next time you wont be able to flash the same file cuz it'll be considered a downgrade.
Click to expand...
Click to collapse
Being a devil's advocate here - is that really true?
Other Android phones have been able to flash back to prior ROMs in the past (the standard way to root the G1 was to flash one of the original shipped ROMs and it would flash regardless of which version you were on).
Having to flash the original ROM does reset your phone and that, to me, is a more obvious and practical drawback to removing built-in apps, especially if disabling them is just as easy (and you don't get any useable file space back when you remove them anyway).
Someone in the G2-Root channel tried and it failed. The phone checked to see what version it was flashing and if it was older than what is already on it, it will fail.
From what I remember... the hardboot/spl version has to be different (older) in order for it to fail... of course this is speculation.
In fact the hardboot version hasn't changed so it should revert. Weird that it failed... I don't understand why it would.
After applying the OTA manually, I just tried to flash back to the pre-OTA stock using fastboot.
I get an error:
FAILED (remote: 43 main version check fail)
**** lol. I've already used titanium backup to remove that damn photobucket app that kept posting notifications on why I should use their crappy service. Any hope for me?
Sent from my T-Mobile G2 using XDA App
the truth is, in 6 months there will be a better phone... and ill end up getting it.. and if worse comes to worse, i can pan up $130 for a new g2...
i had to do alot of my **** to my phone inorder to apply the ota update.... i wil not remove one app of the phone until its rooted
I don't think it will come to that. I am currently trying to re-apply to OTA to see if it will just reinstall the missing apps and get it back to where it was.
If that doesn't work, I'll wipe through recovery, and then apply the OTA.
After that, though, I'll wait until someone smarter does something about it.
Will post results in a few.
EDIT: The OTA applied just fine, but the missing apps were not restored. Hopefully, since the OTA applied, even with missing apps, future OTAs will also apply.
Another solution would be for someone to extract the ROM and apply the full ROM, as opposed to just the OTA patch.
Already tried. You can't use hboot to go back to 1.19, you can't you fastboot-windows, and factory restore just deletes your data XD
Looks like I'm totally screwed. I hope paul (or anyone for that matter) finds a solution. I really don't want to be stuck with a phone that can't update, all because T-Mobile decided that they really liked photobucket.
ibemad1 said:
Already tried. You can't use hboot to go back to 1.19, you can't you fastboot-windows, and factory restore just deletes your data XD
Looks like I'm totally screwed. I hope paul (or anyone for that matter) finds a solution. I really don't want to be stuck with a phone that can't update, all because T-Mobile decided that they really liked photobucket.
Click to expand...
Click to collapse
i'm super confused with this thread. how could you have deleted a program from /system when we dont have full root yet? just powering down the device and powering it back on would essentially re-install that app would it not? unless you applied the ota before rebooting your phone in which case i dont know what would happen, but if you shut down your phone and power it back on on the original firmware, all modifications to /system should be undone. so after a reboot, applying the ota shouldnt be a problem
*sigh* You CAN make modifications to /system. There's no "restore" that happens on reboot, it's just that it appears r/w to android and android caches the writes to /system.
You can delete files(and apps obviously) from /system by telling android to restore off of that file. Here's how the restore process is supposed to work:
Restore recieves the .zip containing firmware
Restore verifies firmware
Restore flashes firmware
Restore deletes old .zip containing firmware
However, if you tell it to restore off of a file that doesn't contain firmware (such as an apk) this happens:
Restore recieves .apk
Restore verifies apk for firmware install
Restore says WTF THIS IS NOT FIRMWARE
Restore deletes the .apk even though the restore didn't work.
And that's how we are able to delete files in /system ^_^
shizenyasuya said:
i'm super confused with this thread. how could you have deleted a program from /system when we dont have full root yet? just powering down the device and powering it back on would essentially re-install that app would it not? unless you applied the ota before rebooting your phone in which case i dont know what would happen, but if you shut down your phone and power it back on on the original firmware, all modifications to /system should be undone. so after a reboot, applying the ota shouldnt be a problem
Click to expand...
Click to collapse
Paul came up with a method that tricks the phone into thinking something is an update.zip, which, when it cannot be applied, is then deleted. It's creative, but many of us jumped the gun, and deleted a bunch of stuff, which me might regret later. See this thread on MoDaCo.
Great, i hope we're not screwed because i deleted a bunch of the bloatwares =/
Sent from my T-Mobile G2 using XDA App

[Q] OTA 2.2.1 update manually

I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
Call T-Mobile customer service and verify with them that the IMEI number they have in your account is the correct one. This is the number one reason for not getting the update. I had a phone for over a month and they never changed the IMIE # until I called. The IMEI is on your box or under your battery.
Please post questions in the Q&A section.
remijenkins said:
I am looking to download and installed 2.2.1 on my MT4G but I can't find a download link anywhere. I can only find 2.2. It tried to do a OTA but when it rebooted it never installed and when I pulled the battery an hour later it deleted the update on boot. I've performed *#*#checkin#*#* and it said succeeded but I still haven't had an update since. I don't want a custom ROM on this phone for a while since it's under warranty. I have a MT3G for that...
BTW, I did use the search feature for who ever was going to say use it, I even used this thing call Google. It was quite fascinating!
Click to expand...
Click to collapse
[GUIDE] Forcing update 2.2.1 and re-rooting after downgrading This was on the same page you posted.... have you by chance read it?
I'd recomend using the force method...I spent almost three weeks waiting on it after being put on a "push list", verifying IMEI, and other things. Some phones "won't update" for whatever reason and they will eventually tell you to swap it. I did the manual update from the thread linked above without issue after T-Mo was unable to resolve my issue and I wasn't willing to swap for a potential refurb after having to pay full $450 retail price on the phone.
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
remijenkins said:
I actually did read the post about forcing the update about I don't want to have to root my phone or turn S off. I'm wanting to leave it 100% stock. The forcing the update post mentions that wifi stops working when you update and that you have to do some stuff to get it working. I actually spent almost 2 hours on the phone with CS for Tmobile and at the very end they told me that they can't push an update, that I can only do the checkin option which has been done. Most of my time was spent on hold. That's why I'm just looking for someone who happens to have a copy of the update that I can copy to what ever folder is needed to get my phone to update. They did mention it can be at the end of the push out by Google before I get another chance to update which is several months of bugs to deal with.
Click to expand...
Click to collapse
THE update is in the post... if you want to try and copy it to every folder on your phone fine... try it... but it is in that post
and if you want you could turn s-off to flash it then turn s-on when you're done... and you won't be rooted after the update applies so you won't have to unroot
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
remijenkins said:
If that is the update then why does wifi stop working when you flash it? And how are you suppose to get it working again after it stops?
Click to expand...
Click to collapse
there is more than one file posted there... The one named "PD15IMG.zip" is part of the update. It replaces the kernel and some other system files, but does not include the patches from the update, which is why wifi breaks. The one labeled The OTA is the full OTA pulled from a phone and the filename is "update.zip" I could not get the full update to flash with S-ON because it has to do some commands on the system to let it know it's going to flash becuase the phone temporarily disables the write through in place... (not sure if i explained that right). My solution is to flash the partial update which gets your kernel up to date then patch the kernel (turning s-off) and then flashing the entire update. If you're really against root you can undo all the root stuff and S-Off after the update hits... but what's wrong with root? You should still get new updates if you're still running stock, but are rooted. BUT, if you uninstall programs the updates will most likely not take (I recommend a nandroid be made before removing things so you can flash back to it get the update, make a new nandroid, then reremove software.)
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
remijenkins said:
Well I was actually concidering rooting updating and unrooting when my phone goes, "downloading new firmware"... It's amazing how you ***** and moan to Tmobile and things just happen. :: shrugs :: I'm happy, now I wish they would let me remove bloatware without rooting.
Click to expand...
Click to collapse
Why the aversion to rooting? it's really not that hard and there are at least 4 or 5 of us in irc that will walk you through it
Rooting is nasty
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Flash PD15IMG-->temporary root-->permanent root (lot of jibberish)-->flash rest of update-->unroot
This is an intimidating process which is nowhere given in simple and complete steps but yet is often described as "simple" or "took minutes." Maybe for some, but the "simple" suckers in a lot of people who stumble along the way.
As I did; all I wanted was an unrooted phone with 2.2.1 and I had given TMo a couple of weeks to do it. A few hours into the process and a few steps beyond trashing WiFi I realized I didn't want a rooted phone and decided either to pay somebody who knows a lot more about this subject than I do to fix it or, preferably to convince TMo to give me a new one. So I went to sleep.
And guess what? At 6AM TMo said they wanted to do a firmware update, to which I agreed, and the legit OTA over-rode that damned PD15IMG and cajoled my WiFi back to life. And as far as I know Tmo doesn't have my IMEI either, because they say on their site they don't know what kind of phone I have.
And none of that snarky "if you don't know what we're talking about you shouldn't be here," either. If she didn't know she could get pregnant from it she shouldn't have done it. The whole rooting business is nasty: there are no simple comprehensive directions, there are too many ROMs and there is too little honest description of where they fail.
It would be nice also if Google would save up its incremental improvements and let them loose at longer intervals, as Apple does, to reduce the frustration of those interested in Being First. It would also be nice if the Google open system had required carriers to be able to absorb the latest updates within a fixed time, regardless of whatever crud they lay over the basic Android. The software may be "open" as far as Google and Tmo are concerned, but between TMo and me the relationship is different.
ecdy said:
The problem with the description of the method for manual install of 2.2.1 is that it is misleading; the author said HIS WiFi stopped working after installing PD15IMG but should have said from the start that PD15IMG is only part of the OTA; that EVERYBODY's WiFi would stop working after installing PD15IMG; and that the entire following process is required to get to 2.2.1 if all you want is an unrooted phone with 2.2.1:
Click to expand...
Click to collapse
I'm sorry you had problems, but when doing anything that has a set of instructions it is wise to read the entire thing before starting. This will ensure you are fully prepared instead of lost in the sauce halfway through... Piss Poor Planning leads to Piss Poor Performance.

Still on 2.1. Source says 2.3 is available for Galaxy S

I haven't been around for a while and could not quickly get up to date despite going through thread after thread here. I would appreciate some advice and clarification.
First, you guys are saying that GB won't be available for Vibrant, but this article clearly states that it is already available:
“update news! the android 2.3 gingerbread update for the samsung galaxy S vibrant is good to go. connect to samsung kies to hook it up.”
Could you please clarify? The problem is that I downloaded Keys 2.0, but my phone, which is 2.1 and rooted (nothing else done, no roms, etc), is not being recognized. Keys says that my phone isn't supported.
Could you guys please clarify what is really going on in terms of 2.3? Also, how can I get the update? Assuming that the article is false, many here say that 2.3 roms are battery hogs and it looks like I would have to update to 2.2 and then root it. If so, I'd appreciate a link to a pure 2.2 to be installed via Odin. Reading all these threads doesn't convince me that getting a rom, a modem, or a kernel really does that much to improve our phones.
Thanks!
Thats for the Bell/ Virgin Mobile Vibrant theres a difference ya know...
I thought that the phone is the same so it wouldn't matter or perhaps the devs could use it to create a better ROM. If not, I guess the situation is even worse because Samsung actually released the update for Vibrant but T-mobile is refusing to allow users to have it! Clusterf*ck. Steve Jobs was right about android when he talked about market fractionization last year. Oh well.
Ok, well given the bad news, I would appreciate some help from those of you who have flashed your phones to hell and back. I know there are different ROMs etc with different features. I don't use my phone heavily. Actually, the main feature I care about is 1.Good GPS and 2.Good battery life. I go on long cycling trips and my phone is the only thing I use to track my stats (sometimes five hours or longer).
Based on this info, could you guys tell me if upgrading to Android 2.2 be good enough or do any of the ROMs, kernels, and modems provide a clear advantage over stock 2.2? If so, could you recommend a few? Right now my phone is in a very bad shape - the GPS is often dying in mountains and the battery doesn't last much. At this point I have to upgrade just to clean up my phone, especially since it's not clear if/when 2.3 will be released. I am hoping that at least 2.2 should be very stable by now.
only thing in common is the name and the fact that they are both Galaxy S series phones, the canadian bell Vibrant is different hardware then our Vibrant.
I'd say go with something stable such as Bionix 1.3.1 or Trigger 3.2. If you wanna go with 2.2.1 go with a Darky ROM's port or Bi- Winning 3. All good ROMS I'd recommended. Regardless that's what I prefer pperhaps just play around with all types of ROM's you may like something else its not for me to decide.
Sent from my SGH-T959 using XDA App
i would suggest cm7 if u like gb its almost fully functitioning except gps is weak
Would you guys say that you have seen significant performance improvements (~30% or more) of ROMs over rooted stock 2.2? If so, have you also seen significant improvements by adding a kernel and/or a modem?
I know that it's not supposed to be too hard to flash and find out for myself, but I have never flashed anything and evaluating all the different combos can be quiet time consuming. Given that I work and study so much I barely have enough time to date, I was hoping that I could get some succinct advice that will cut my Android pains in half. I have read the thread about different modems and know that something like KB5 is a pretty good modem (still have no idea what it is or where do you get it and how you flash it); however, that thread missed one key comparison - the actual performance and battery improvement of a given modem (and even a kernel) over stock 2.2/2.3 or even over a ROM like Bionix. I'd appreciate any info/links regarding this.
Thanks.
Stop writing walls of text for no reason ... kernel will make your phone faster, particularly if you enable voodoo lagfix (helluvah lot faster >30% over stock)... modem will not make it faster but may make your data connection faster and battery last longer as well as morr signal ... look for the modem page for dl link....
Now go flash a rom!! All the roms here are amazing and huge improvements over stock, as are the kernels. Suggestions??? Print out all the names, put em on notecards and throw a dart... flash whatever you hit.
Sent from a cell tower to the XDA server to you.
Bell vibrant is completely different from ours ... the 2.3 for them is no help to us.. lol were not lying to you
Sent from a cell tower to the XDA server to you.
None of the Gingerbread roms are anywhere near where some of the Froyo roms are.
Team Whiskey Bionix 1.3.1 is the best I've used. NextGen V2 isnt' bad either. I just tried Simply Honey 5 RC1 and CM7 nightly #84. Out of the 4 roms I just listed, I flashed back to Bionix 1.3.1. It has the best speed and is the most stable I've ever used.
If you don't have the time to read about flashing your phone, I would suggest you either not do it or pay someone to do it for you. Set aside 2-3 hours if you want it done properly otherwise say goodbye to your phone.
I am in SoCal too and wouldn't mind paying someone to do it for me. The problem is then a whole other set of headaches: how do you trust someone to get hold of your private info? What about doing a good job? Arranging a pickup/dropoff, etc, etc. Also have no idea how much people charge for this service. Expensive enough and it might just be worth it to get a new phone, especially after I sell the Vibrant. Maybe that's what many of us need to do.
Im sure you can find someone nearby thatll do it as a favor and let you watch... problem solved
Sent from a cell tower to the XDA server to you.
I would never pay anyone to flash anything for me. Its a simple process.
To figure out what ROM's go good with what Modem I would go to this thread http://forum.xda-developers.com/showthread.php?t=959088 and a good kernel would be Bali or SuperDragonModz both great.
Excelsius said:
I am in SoCal too and wouldn't mind paying someone to do it for me. The problem is then a whole other set of headaches: how do you trust someone to get hold of your private info? What about doing a good job? Arranging a pickup/dropoff, etc, etc. Also have no idea how much people charge for this service. Expensive enough and it might just be worth it to get a new phone, especially after I sell the Vibrant. Maybe that's what many of us need to do.
Click to expand...
Click to collapse
I recommend listening to some of the other folks in the thread and flash bionix 1.3.1. The stock kernel is fine, as is the modem it ships with. Battery life will be as good as just about anything else.
If you really want to flash a custom kernel, go with Bali 1.8.8. Battery life will be similar, but that kernel has some additional features like voodoo sound, which uses the audio hardware more effectively. If that doesn't seem like something you care about I wouldn't worry about it.
The only catch is that you will need to flash bionix through CWM recovery, there are no prepackaged odin files that I am aware of. There are numerous threads to help you getting CWM installed, just check out the stickies.
Don't pay anyone, if your still not comfortable flashing anything, but you still really want to, PM me and I'll help you through it.
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
I'm in SoCal, running Cyanogen7 nightly 81. (Android 2.3)
I am running Bali, and did both the hardware GPS fix, and the software GPS fix using the terminal scripting.
I get around 10-12 locks, accuracy tends to be in the 12-14 foot range, so the GPS works flawlessly.
I've been a lurker on these forums for a LONG time now, but decided to register and post to kinda give back. In this case, to someone looking to fix up their Vibrant.
If you're interested, PM me. I work for Microsoft, and you're welcome to stop by and I'll show you everything I've done. (Yes, I have an Android phone, and a WP7 phone, both of which I love) If you like what you see, (You will) I'll set your phone up as my way of kinda returning all of the favors other users on this site have done for me, even though they didn't know it.
Excelsius said:
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
Click to expand...
Click to collapse
If you already have ROM manager, and have "Flashed Recovery" then you have Clockwork Mod. At this point, should be able follow the Bionix instructions after the CWM point.
Nandroid backs up EVERYTHING, including the Android OS version you are running. If you want to back up just your apps, use Titanium Backup, the premium version lets you do a "One touch" batch restore of all user apps. One thing to remember about Titanium: do NOT back up system data. Easiest rule of thumb for it, "Menu--> Batch--> backup all user apps" then let it do it's thing. flash your ROM, then go into Titanium (Almost positive the free version is part of Bionix) "Menu--> Batch--> Restore missing apps with data" If you have the premium version, you can restore them all with no further input, if you have the free version, you will have to accept and install each app as you go, but they all come back with your saved data.
If you are going to do a FULL wipe (Format storage so the phone is empty) first connect to USB Storage, and move your "Titanium Backup" folder from the root of your internal SD card to your PC. Then, before you run titanium for the first time after wiping, reverse the process. Apps are back.
Excelsius said:
Thank you so much for the more precise advice. That's exactly what I needed. It's not that I want to upgrade, but rather that I have to because my phone has become unstable. It freezes almost every time I open Voice or Maps, among other problems.
So I will get the Bionix 1.3.1 and worry about Bali 1.8.8 at a later time. I came across this guide: http://forum.xda-developers.com/showthread.php?t=925400
Is it the guide for CWM? My phone is rooted (ODIN) and has paid version of Root Explorer and BusyBox. I was wondering if I still have to install SuperOneClick or if my root is fine already.
By the way, I'd appreciate a link to some guides that you guys have used to install your Bionix. I read this: http://forum.xda-developers.com/showthread.php?t=732458, but the CWM and Rom Manager points are moot. Like I don't know if installing Rom Manager already includes CWM with it. Here are the steps:
Installation instructions:
1.Download ROM Manager from the Market.
2.Flash Recovery.
3.Choose Vibrant as your phone.
4.Accept the Superuser prompt.
5.On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
6.Watch the backup go!
If this is it, then I'll just do it (after I do a nandroid backup, which will hopefully backup all my paid applications).
Click to expand...
Click to collapse
The steps you listed are correct. You also of course need to have downloaded the bionix 1.3.1 zip file and placed it somewhere on your SD card (I make a ROMS folder on mine). As the instructions noted, you'll have to do reinstall packages twice (ie you do it once and the phone reboots into recovery and it looks like nothing happened, you do it again and go immediately to CWR recovery where you can select "install ROM from SD" or similar). From this point on you won't have to worry about CWR recovery, it will always be there. As StarGazer mentioned, when you flash this it will wipe your phones settings and all the apps (but not the SD card). There are a variety of backup apps that can help restore them, but I usually don't mind starting fresh once in a while, especially if your contacts are stored on Google.
Finally, once the bionix finishes flashing and the phone reboots for the first time, expect to hear a voice start talking to you about backing up partitions, estimated times, etc. This is the "voodoo lagfix" being applied, which is converting internal phone partitions from the Samsung RFS to ext4, which noticeably reduces lag on the phone when opening apps and so forth. Good luck
Thank you for your help, everyone. I was able to dedicate a few hours and just take care of it since it didn't feel right to waste someone else's time. Please note that I haven't PMed anyone and if there are readers here who are technologically challenged, perhaps they can take my place and get help from some of the generous people who offered help here.
I currently have Bionix 1.3.1, Bali 1.8.8, and KB5.
To give back to the community, I wanted to post benchmarks. I have some amazing results:
Android 2.1 (everything stock, rooted) - Quadrant benchmark 852 (average of 2 tests)
Bionix 1.3.1 (with stock kernel) - 1504 (average of 3 tests). That's a 43% improvement! Now this is likely due to Android 2.2 rather than Bionix. It's definitely worth going from 2.1 to 2.2.
Bionix 1.3.1 + Bali 1.8.8 (after adding the kernel) - 1852 (average of 3 tests). That's 19% more than stock 2.2 and 54% more than 2.1! This isn't 30%+ improvement that some people here think kernels provide, but ~20% is still not bad, considering that battery life is also very important.
Now as far as the KB5 modem goes, I saw no improvements using GPS Test and Speed Test. My GPS is still at about 50ft accuracy and internet speed is 6000x2300kbps. The real test will come during my 60 mile ride on Saturday.
Right now I am only hoping that the battery will last at least as long or more than on 2.1, despite the kernel.
Question: before flashing with Bionix I had applied the software GPS fix to my phone a year ago. Do I have to do it again or does Bionix already include the software tweak?
Once again, thanks everyone.
P.S: My clock on the phone is off by two minutes from the atomic clock. I noticed that the "Autoupdate" of date and time message doesn't appear when I start the phone. Is there a time syncing issue with Bionix?

Categories

Resources