Hey, Original 2.2 Manual Updaters----

rugmankc

Well-known member
Jun 10, 2010
60
0
0
----would you do it again?

Looking for feedback from those that manually updated to 2.2 over two weeks ago. A lot of people seemed to do OK, some did not. I am stock N1 bought from Google Store running ERE27 on CBW. Had to select TMO 3G as carrier choice when I bought. I downloaded the update and saved to SD Card as "update" no .zip, has "passion" in link name. Other than that forgot where I downloaded from. Have done nothing since then and like a lot of others tired of waiting and know from Google employee posts, I will still get the OTA when it comes out.

I would like to know from any of you if you would do it again, since I read that some had problems only after several days after the update. Am aware of the bugs even though most, like I said, posted no problems at all.

Part of me says wait, it can't be that much longer. The other part says go ahead, you can always factory reset and reload. I use MyBackUp for apps and data.

Looking to see what percentage of responses are positive.


Any advice?
 
yes of course i would do it again. since i had to root to do it, i can bounce back and forth between froyo and cyanogen within a few minutes using my nand backups. so i dont exactly lose anything by trying the update.
 
Thanks RogerPodacter,

Was not sure anyone had any inputs. I guess you were already rooted then had to go back to stock then installed 2.2 and rerooted. Did you use CM's Quickrooter for 2.2? I thought that was not a complete ROM yet and only gave a couple of features. Thought for a more complete 2.2 ROM Google had to come out with something. Forgot what I read and new at this.


Ken
 
Thanks RogerPodacter,

Was not sure anyone had any inputs. I guess you were already rooted then had to go back to stock then installed 2.2 and rerooted. Did you use CM's Quickrooter for 2.2? I thought that was not a complete ROM yet and only gave a couple of features. Thought for a more complete 2.2 ROM Google had to come out with something. Forgot what I read and new at this.


Ken

No I wasn't rooted. I rooted to get froyo, and used stock for 3 months before rooting.
 
I am not good at these terms: root, flash, fastboot, bootloader etc. But, why did you need to root for froyo if you were stock prior to it. I just updated to froyo and it went great. Question is now should I wait to root if I even do it, before the official OTA comes out. If all is working well why install the official OTA over my current 2.2.

I want flash and not sure rooting gives me anything I still need, may be wrong.



Ken
 
I am not good at these terms: root, flash, fastboot, bootloader etc. But, why did you need to root for froyo if you were stock prior to it. I just updated to froyo and it went great. Question is now should I wait to root if I even do it, before the official OTA comes out. If all is working well why install the official OTA over my current 2.2.

I want flash and not sure rooting gives me anything I still need, may be wrong.



Ken

you are using the tmobile nexus one then. i am on the att nexus one, which cannot just update right to froyo. have to be rooted, so i decided to root.

you may not need to root right now. but the instant the official froyo is released, cyanogen is gonna start pumping out his excellent ROMs, which you must be rooted to use. half the time i am switching back to cyanogen 5.0.7 simply because i like it so much, even over froyo in many ways. a cyanogen froyo ROM will just be the ultimate!
 
Thanks Roger,

For some reason I am not getting emails to let me know of posts to my threads from Android Central. Hope it isn't 2.2 related.

I am now trying to justify rooting. I don't want to lose Adobe flash and Tethering. I know Flashlite can be put on a rooted phone, but what about tethering. May have to get a tethering app, don't know.

Since I am on TMO (Actually Cincinnati Bell) and have a stock Froyo N1, trying to find a good idiot proof step by step guide to rooting. Then I can flash clockworkmod do a nandroid backup and start flashing roms. I don't think flashlite is too far off 10.1 according to videos I have seen. And you have PDAnet for tethering. Once rooted don't you do a nand backup of your stock OS (full image) as part of flashing clockworkmod so you can go back to stock OS if you want?

I also read you don't normally lose all your apps and data when you root but you may. Is that true.

If I use quickrooter, sounds like you flash it just like flashing froyo. Do you still need to unlock bootloader first?


Lot's of questions, sorry. I would like to root if I had a good chance of not losing my current configuration/apps/data when I root and can then back that up by doing a nandroid backup. It is scary. More so than going to Froyo.


Any thoughts on my 1,000 questions.




Ken
 
Nahh.. It was good to see that I could get Bluetooth in my car working, but I've suffered through poor performance and my thinking the power button was flaking out.

Went back to Cyanogenmod and all is well again (maybe not Bluetooth) but it's more responsive, quicker, smoother, and my power button has been 100% perfect.

Froyo just needs a little more time to chill, close but not quite there yet.
 
I am using Nexus One with international edition. After Android 2.2 Froyo leaked I was try to update my phone by two way:

1. Check for update automatic but there are no available yet for auto
2. Update by manually but I got error status 7.

I really don't know why because I never rooted or hacked my phone before. Just download and install apps from Android Market.
 
I am using Nexus One with international edition. After Android 2.2 Froyo leaked I was try to update my phone by two way:

1. Check for update automatic but there are no available yet for auto
2. Update by manually but I got error status 7.

I really don't know why because I never rooted or hacked my phone before. Just download and install apps from Android Market.


techdaring,

You may want to start your own thread, this is for people who already updated to 2.2 several weeks and I am looking for their longterm experience. Sounds like you have a specific problem with updated and never had 2.2 on your phone.


Ken