I'm what you call a newbie to smart phones and have not a clue how to root but these steps to get Froyo on the incredible were straight to the point and I got 2.2 on my Dinc with ease. It also works great so thank you for this thread. It couldn't have been easier. Thanks again! No more waiting for the OTA. WOOT
You guys almost have me convinced to install the RUU tonite!
Very hesitant...I'm prepared to wait for the OTA - but I figured I'd give it a try. When I plug my phone in - the computer found new hardware "ADB" and wants a driver for it.....the PC finds the SD card fine...I tried the RUU - and it just stalled for 10 or more minutes. <shrug>
Very hesitant...I'm prepared to wait for the OTA - but I figured I'd give it a try. When I plug my phone in - the computer found new hardware "ADB" and wants a driver for it.....the PC finds the SD card fine...I tried the RUU - and it just stalled for 10 or more minutes. <shrug>
Same thing happened to me, and there is another link on the OP for specific errors, but it did not list the ADB error you mentioned. The only reason I know about it is because it happened to me.
Install HTC sync and have phone plugged in, it will install all the drivers it needs for the phone. If you have it installed already, uninstall it, reboot, reinstall it and plug in phone and let it re-activate all the drivers. Then do the RUU update with htc sync running. that did the trick for me.
The Following User Says Thank You to JuniorNA For This Useful Post:
You guys almost have me convinced to install the RUU tonite!
seriously, do it. it eases the pain of waiting. it's the stock release anyway, so no worries at all.
at first i didn't install htc sync for incredible and the update wouldn't work. i got three dancing android robots on the screen. still no worries. pulled the battery and while it was rebooting installed sync. tried again and 100% success.
contacts took like 30 seconds to sync, and i reinstalled all 40+ of my apps in like 10 minutes.
now i'm rocking perfect froyo goodness. like nike says, JUST DO IT!!!!
You guys almost have me convinced to install the RUU tonite!
I think you'll be just fine. The ONLY thing I did to prep for this was remove HTC Sync from my laptop running XP prior to running the RUU executable. It's painless and I'm sure it'll go smooth for you as it did for me. No problems whatsoever.
Had my buddy do his DINC today at work with the RUU. He followed the instructions and with a little of my help getting his apps from AppBrain and getting Swype back he is up and at it again. His flash on the ROM only took like 5 minutes which I thought was fast but everything is working great. Thanks again..
Device(s): Samsung Galaxy S III
Debloated SynergyROM (Nightly) R64
Carrier: Not Provided
Thanks: 7
Thanked 60 Times in 18 Posts
Quote:
Originally Posted by danielzink
Very hesitant...I'm prepared to wait for the OTA - but I figured I'd give it a try. When I plug my phone in - the computer found new hardware "ADB" and wants a driver for it.....the PC finds the SD card fine...I tried the RUU - and it just stalled for 10 or more minutes. <shrug>
i didnt run into that error so i didnt know it had happened a few times.
i edited the original post to include the link to the post by JuniorNA resolving the issue with htc sync.
simple enough!
__________________
..imagination is more important than knowledge... - a. einstein
Guess who just got Froyo... this guy. I like it, just a little laggy on the unlock screen... hopefully that will go away after everything get settled in. Is there a way to get the programs that keep coming on to stay off? Task killer is just assaulting but not murdering.
Device(s): Samsung Galaxy S III
Debloated SynergyROM (Nightly) R64
Carrier: Not Provided
Thanks: 7
Thanked 60 Times in 18 Posts
Quote:
Originally Posted by icrazy2u
Guess who just got Froyo... this guy. I like it, just a little laggy on the unlock screen... hopefully that will go away after everything get settled in. Is there a way to get the programs that keep coming on to stay off? Task killer is just assaulting but not murdering.
1. i noticed that NOT running any kind of task killer actually saves battery. go figure.
2. i ALSO noticed in my task killer that even though the processes were running, they were actually consuming 0% processor. i dont know if thats accurate, but i CAN say that not running a task killer saves battery life.
1. i noticed that NOT running any kind of task killer actually saves battery. go figure.
2. i ALSO noticed in my task killer that even though the processes were running, they were actually consuming 0% processor. i dont know if thats accurate, but i CAN say that not running a task killer saves battery life.
Alright, i'll try that. Thanks. Time to murder the Task Killer.
1. i noticed that NOT running any kind of task killer actually saves battery. go figure.
2. i ALSO noticed in my task killer that even though the processes were running, they were actually consuming 0% processor. i dont know if thats accurate, but i CAN say that not running a task killer saves battery life.
I agree, I just use System Panel to monitor everything. Has saved my battery, and a lot of wasted time.
Although everyonce in a while I will kill an app that I know is just sucking. What I noticed with 2.2, I wanted to just kill off some of the new bloatware. VZNav, Verizon Mobile, City ID.
But not 20 seconds after I kill it, it pops back up in my active list. Now I expect these things to be always present, but it kinda baffled me that they would pop up so quickly after killing it. Are these apps actually running?!? Otherwise why would the actively open itself just like that?
Last edited by pucrepeap; August 30th, 2010 at 10:03 PM.
nope....no love....installed sync.....redownloaded the ruu....got a gpf {blah blah blah aruwizard.exe}....had the HTC logo on my phone screen - unplugged the USB - got the three dancing droids - pert near peed my pants thinking I bricked my phone....that's enough f'in fun for one night...I'll just wait for the OTA.....sheesh....
Loaded the ruu tonight. Thanks for the easy instructions. Is anyone else having an issue with the menu button not working as a way to unlock the screen after you power on?
hey guys , update worked flawless for me. Is anyone else notice that there is no 'Photos' app or program anymore? How do I get this back? Other than that, loving Froyo!
Device(s): Samsung Galaxy S III
Debloated SynergyROM (Nightly) R64
Carrier: Not Provided
Thanks: 7
Thanked 60 Times in 18 Posts
Quote:
Originally Posted by sqerkl
"All too easy."
LOVIN' the update so far. Thanks for the awesomely uber-simplified info.
EDIT: Just outta curiosity: when and how does one upgrade from "new member" status to, well, whatever the next step is and so forth?
Quote:
Originally Posted by simmons_m
Loaded the ruu tonight. Thanks for the easy instructions. Is anyone else having an issue with the menu button not working as a way to unlock the screen after you power on?
Quote:
Originally Posted by upatoi15
hey guys , update worked flawless for me. Is anyone else notice that there is no 'Photos' app or program anymore? How do I get this back? Other than that, loving Froyo!
Sqerk, I think its 10-15 to "junior member."
Simmons, as opposed to sliding downward to unlock? I've never used that feature, but it doesn't work on mine either.
hey guys , update worked flawless for me. Is anyone else notice that there is no 'Photos' app or program anymore? How do I get this back? Other than that, loving Froyo!
Lol, it's Gallery. Thats the app your looking for.
Last edited by icrazy2u; August 30th, 2010 at 10:50 PM.
Reason: Messed up spelling
So I did everything and got error 170, then hit connect again and it worked till i got error 171. now the screen just says HTC with a black screen and white letters. did i just ruin the entire phone?
can i unplug it? can i take the battery out? wtf did i do?
and yes, im using windows 7. i saw others used it too and it worked once they followed the steps to error 170.
I agree, I just use System Panel to monitor everything. Has saved my battery, and a lot of wasted time.
Although everyonce in a while I will kill an app that I know is just sucking. What I noticed with 2.2, I wanted to just kill off some of the new bloatware. VZNav, Verizon Mobile, City ID.
But not 20 seconds after I kill it, it pops back up in my active list. Now I expect these things to be always present, but it kinda baffled me that they would pop up so quickly after killing it. Are these apps actually running?!? Otherwise why would the actively open itself just like that?
Hey Pucrepeap, I thought the same thing when i saw cityID/skype/Verizon Mobile...I would use ATK to kill it and come right back during my testing. As it turns out, the second you kill it, the OS tells those processes to be on standby using 0 cpu usage until needed. Sure they are running but not using any CPU power, or battery power. I've learned by killing these processes, I'm actually killing battery because the process restarts anyway and uses CPU usage to start them back up again. But that's a whole other thousand year debate.
True-Man, amazing job on answering all the questions.
Device(s): Samsung Galaxy S III
Debloated SynergyROM (Nightly) R64
Carrier: Not Provided
Thanks: 7
Thanked 60 Times in 18 Posts
Quote:
Originally Posted by vnyislesv
So I did everything and got error 170, then hit connect again and it worked till i got error 171. now the screen just says HTC with a black screen and white letters. did i just ruin the entire phone?
can i unplug it? can i take the battery out? wtf did i do?
and yes, im using windows 7. i saw others used it too and it worked once they followed the steps to error 170.
Device(s): Samsung Galaxy S III
Debloated SynergyROM (Nightly) R64
Carrier: Not Provided
Thanks: 7
Thanked 60 Times in 18 Posts
Quote:
Originally Posted by JuniorNA
Hey Pucrepeap, I thought the same thing when i saw cityID/skype/Verizon Mobile...I would use ATK to kill it and come right back during my testing. As it turns out, the second you kill it, the OS tells those processes to be on standby using 0 cpu usage until needed. Sure they are running but not using any CPU power, or battery power. I've learned by killing these processes, I'm actually killing battery because the process restarts anyway and uses CPU usage to start them back up again. But that's a whole other thousand year debate.
True-Man, amazing job on answering all the questions.
hey thanks!
i wouldnt think it right to make this thread then disappear.
answering these questions is kind of fun. im also learning a bit more about the phone by doing so.
your compliment means something, considering its coming from a GUIDE.
The Following User Says Thank You to true For This Useful Post:
hey thanks!
i wouldnt think it right to make this thread then disappear.
answering these questions is kind of fun. im also learning a bit more about the phone by doing so.
your compliment means something, considering its coming from a GUIDE.
Lol, I'll take that compliment, i think ?
Anyway, I installed the version of 2.0.40 which should be mentioned because i'm not sure if the newer version of HTC sync is fixing those with this issue. When i installed the 2.0.40 version, everything went flying through.
Device(s): Samsung Galaxy S III
Debloated SynergyROM (Nightly) R64
Carrier: Not Provided
Thanks: 7
Thanked 60 Times in 18 Posts
Quote:
Originally Posted by JuniorNA
Lol, I'll take that compliment, i think ?
Anyway, I installed the version of 2.0.40 which should be mentioned because i'm not sure if the newer version of HTC sync is fixing those with this issue. When i installed the 2.0.40 version, everything went flying through.
yeah, thats the one ive been telling people to use.
its the one that was mentioned in the error 170/171 thread and seems to have worked wonders over the past few days for people who have encountered those problems.
i'll be packing it in early tonight though.
long day ahead of me.
btw,
254 downloads of the RUU from Megaupload so far
157 from mediafire. and i cant tell how many used filedropper. i would estimate somewhere between 150-200.
just some interesting fyi.
Last edited by true; August 31st, 2010 at 12:09 AM.
The Following User Says Thank You to true For This Useful Post:
yeah, thats the one ive been telling people to use.
its the one that was mentioned in the error 170/171 thread and seems to have worked wonders over the past few days for people who have encountered those problems.
i'll be packing it in early tonight though.
long day ahead of me.
btw,
254 downloads of the RUU from Megaupload so far
157 from mediafire. and i cant tell how many used filedropper. i would estimate somewhere between 150-200.
just some interesting fyi.
You also cant tell how many people snagged it, upped it, and copied your post for their own forum. Im sure it has happened, i hope they gave credit.
SO I was still trying to get an answer for those of us who installed the leaked version of the OTA about a month ago and have not reverted, will RUU wipe my phone clean and give me 2.2 or will it brick my phone if I do not revert first due to the radio codes?? Any answer would be nice--sorry for the noobness!!
Just a shout out to true, thanks for providing this thread and info. I downloaded the RUU yesterday and did the update this morning without out a hitch. Got tired of waiting and wasn't sure if anyone was ever gonna get a zip in the other thread. I guess they finally did but oh well. Just a few extra steps to save my apps and easy as pie!
The Following User Says Thank You to oman321 For This Useful Post:
The first boot takes a bit longer than normal. stay calm
How long is "longer than normal"? I'm stuck at the grayscale HTC screen when it's plugged in and the mostly white screen with the 3 Androids on skateboards (with the HBOOT, date, and other info, also does say RUU highlighted in orange) when I unplug it. It's been this way for 15 minutes. This is the 2nd time; the first time after about 20 minutes I removed the battery and rebooted, and I still had 2.1. I'm not sure what I could be doing wrong, as your instructions are wonderfully dummy-proof and I've done much more complicated things to my phones, going back to Razr-hacking days!
I have a problem after updating this way. When I click on camera it opens fine but I am unable to take a picture using my optical joystick. It simply doesnt work. Is there a fix for this?
Edit: If I push on the screen it will focus and take a pic. I would still like to use my optical joystick if possible... Oh and I tried the video mode and I am unable to record anything...
Thanks for any response!
Last edited by mosabi; August 31st, 2010 at 09:36 AM.
nunyabizness, The part that I believe is referring to is the the first time the phone boots up after the update is complete. It took longer than the usual when powering up and you get the 1st HTC logo, like when a computer boots up from a completely off state.
The only time I saw the grayscale HTC logo is when I plug in the phone to my computer, set it to disk drives and then began the RUU. Once it started the grayscale was present until the RUU did its thing, phone rebooted and it worked. Took about 5 minutes for the RUU to load.
mosabi, I just tried my camera and video. Both worked with the optical joystick.
Worked as advertised on 32bit Vista! At first I ran into the ADB driver problem, but installing HTC Sync fixed the driver issues and after that the RUU ran like a charm. Thanks!
Tested this morning and last night.
Phone seems to be sluggish. I have rebooted a couple of times.
Flash video is choppy
Flash games (kid games) are choppy as well. I am using the dolphin HD browser.
I've rebooted a couple of times, and swapped my battery.
Is there a way to tell if something weird is going on with the phone?
Thanks
I just checked fox.com and that was choppy as you described. I went to M.flash.com to check there and it is nice and smooth. The fox website flashed a message just before starting the video that said "optimized for mobile device".