[Q] RUU will NOT install, help? - Droid Incredible Q&A, Help & Troubleshooting

I know I've seen a post simular to this but it's buried and what little was there did not help.
I have a Win 7 Home Premium 64-bit system, and tried installing the RUU that leaked Thursday. I installed the latest HTC Sync prior to running the RUU.
Made it as far as the screen on the phone going all black with chrome looking HTC logo, at which point the PC wanted to reboot and I got the error [170]. Per the instructions on the other post, I rebooted the PC and pulled the battery on the DInc.
Afterward, no amount of plugging, unplugging, running the RUU again, booting into hboot, booting into recovery, etc. would ever even get me back tot he black HTC screen. I just keep hitting the error [170] after the "verifying contents" file.
I managed to just power down the phone and turn it back on, despite seeing that scary looking screen with the Dinc under a big red ! icon, and it boots up like nothing ever happened.. all apps and contacts there.. etc.
Can someone PLEASE help me get this stinking RUU to install properly? Or failing that.. is there a way to put the contents into the internal memory of my phone and trick it into thinking it's recieved the OTA and I declined, so that I can install from the settings menu? Is it possible to even do that? If one of us gets the OTA, can we jack the OTA out of our internal storage and post it here to allow that to be done?
TIA..
NinjaRicky, UberNoob Extrordinaire

This sounds like the same stage I am at, but I am terrified to remove the battery for bricking my phone.
Right now I have the chrome htc screen when plugged in and the hboot ruu screen (mostly white with green text) when not.
My hboot ver is .79 and radio is 1.00.03.04.06. I also have the S-OFF.
What is the best way to return to the stock rom?

If you have S-Off, I'm guessing you have rooted your phone a little. I don't think security off is a default the RUU would have done.
I have zero experience with rooting, so I have no idea how to return you to stock. Honestly, unless you changed your radio version.. which it looks like you didn't.. you probably could run Unrevoked and Forever, then use one of the guides here to flash your ROM with the stock kernal. I'm sure I've seen a zip file of it floating around in the guides.
Hope that helps. I'm just going off what I've read. I think my problem is strictly because of the 64 bit Windows, but I'm hoping for a workaround.

Is your sdcard formatted to fat32
Sent from my ADR6300 using XDA App

jdkoreclipse said:
Is your sdcard formatted to fat32
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Not sure if you meant me or Rutledge, but no.. my card is FAT.. not FAT32. I'm about to reformat it now. How does that effect the RUU?

The hboot can only correctly read filed from q fat32 card
Sent from my ADR6300 using XDA App

I know I'm going to come off thick witted and slow for this.. but my question is about running the RUU from Windows 64-bit and getting an error [170] indicating that the computer thinks the USB cable isn't connected. I'm not trying to root my phone or install anything from the SD Card.. I wouldn't know what to do with hboot anyway.. I just put the phone in hboot mode and tried running the RUU again because I was grasping at straws.
What does the SD card have to do with the communication error I keep getting?

Use the extracted PB31IMG.zip from the ruu (tis can be found in the thread) and flash feom hboot....that is easier.,
Sent from my ADR6300 using XDA App

NinjaRicky said:
I know I'm going to come off thick witted and slow for this.. but my question is about running the RUU from Windows 64-bit and getting an error [170] indicating that the computer thinks the USB cable isn't connected. I'm not trying to root my phone or install anything from the SD Card.. I wouldn't know what to do with hboot anyway.. I just put the phone in hboot mode and tried running the RUU again because I was grasping at straws.
What does the SD card have to do with the communication error I keep getting?
Click to expand...
Click to collapse
I'm having the same error and found no way to fix it. I was forced to flash the update via my SD card. I had tried 3 computers with no luck ..

Really want to not root my phone yet.. I have a strong conviction I'd brick it. Just not confident yet.

NinjaRicky said:
Really want to not root my phone yet.. I have a strong conviction I'd brick it. Just not confident yet.
Click to expand...
Click to collapse
Just flashing the file from the RUU via your SD card does not require root since its signed by HTC. You do how ever must rename the file to PB31IMG.zip and make sure the card is formatted as FAT32
I did it with no issues but I wont recommend you to do it. I can recommend in this case just waiting the week or how ever long it takes for Verizon to push to the OTA to your phone then.
If you do want to see what I did just look for my question thread in this section called "[Q][RUU]extracting rom.zip file and flashing not rooted and s-on"

And this can be done with a stock DInc with factory defaults, such as S-On and all in place? No Unrevoked first?
Edit: Ignore the above. I R an idiot. Answered the question in your post. And ... it's updating right now witht he ROM.zip renamed. You are the man today, sir. I appreciate all the advice. boomertwo.. this bud's for you!

you need to have htc sync installed to run the RUU.
also your phone needs to be in HTC sync mode with usb debugging enabled.
i have 7x64.

k.electron said:
you need to have htc sync installed to run the RUU.
also your phone needs to be in HTC sync mode with usb debugging enabled.
i have 7x64.
Click to expand...
Click to collapse
That does work to get the phone into RUU mode but after that then the program lost connection to the phone completely. This was the wall I hit and found no way around it after trying it on 3 different machines. All running windows 7 but only 2 of them were 64 bit.

boomertwo said:
That does work to get the phone into RUU mode but after that then the program lost connection to the phone completely. This was the wall I hit and found no way around it after trying it on 3 different machines. All running windows 7 but only 2 of them were 64 bit.
Click to expand...
Click to collapse
I think someone mentioned that you could just let it do the usb error, the close the RUU and restart it and it should work from there.

Related

How to Unroot/go back to STOCK after installing Rooted versions of 1.47/2.05

Pretty sure most people know how to do this but for some who are having issues with drivers n such this might help, wouldn't hurt imo.. I'm on Windows 7 Ultimate (x86)
*** Reportedly Will not work with Official OTA 1.47/2.05 Updates, only Rooted updates, I have not personally tried. The Wizards @ the dev forums are working on a fix: http://forum.xda-developers.com/showthread.php?t=714157 ***
The steps below worked for me. I had the latest clockwork recovery,Damage Control DC 3.2.2.1 deodexed and The latest rooted ota updates installed (EVO_1.47.651.1_De-odex'd_Rooted.zip, 2.05.00.06.10 update.zip)
Download and install HTC Sync Update http://www.htc.com/us/support/evo-sprint/downloads/ (if you already have it installed then click the repair option,
or better yet uninstall your current one even if it is the same one, reboot your computer and then install this one again, for good measure.)
1. I unplugged/plugged my phone into the computer a couple times,switched to htc sync mode when it asks what type of usb connection I wanted, to install more driver updates if any
and did 2 reboots on my computer to get all the drivers updated/installed and working as they should.
2. Turn off the phone, hold volume down and hold down power button to get to bootloader,
pressed Power button one more time to get to the menu where you can reboot bootloader,
rebooted bootloader once and twice BEFORE the unrooting process for good measure.
3. Download either one of the RUU Stock Roms, I would try RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe and then RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe if the first one fails.
http://shipped-roms.com/shipped/Supersonic/
Alternate Link http://tinyurl.com/2fq4dzk
4. Plug your phone into your computer, make sure ALL Drivers installed properly if any, you may already have drivers installed, but double check, switch to HTC Sync mode
and let it install any drivers, then turn off your phone and start it in bootloader (Hold Volume Down +Power button) Reboot your computer also
to make sure everything has been properly installed.
5. Then you can finally double click (right click run as admin imo) the RUU.exe and start the unrooting process, good luck!
I try it and it don't work. I mean yet it detect my ota version but after I click update than for a while it said that my phone is not plug from the computer. I'm running windows 7 ultimate 64bit, eva x58 core i7-920
Thanks for the write-up, does this take the phone completely back to out-of-the-box stock?
yang704 said:
I try it and it don't work. I mean yet it detect my ota version but after I click update than for a while it said that my phone is not plug from the computer. I'm running windows 7 ultimate 64bit, eva x58 core i7-920
Click to expand...
Click to collapse
Make sure your in HTC Sync mode or Disk Drive Mode on your phone, also try rebooting your computer & phone, plugging your phone into a different usb port, etc, have to tinker with it a bit.
jasongthang said:
Thanks for the write-up, does this take the phone completely back to out-of-the-box stock?
Click to expand...
Click to collapse
Yes.
Worked for me earlier today. Failed the first time, but i just ran it again and it went through. Thanks for the writeup!
Np glad I could help
Sirchuk said:
Worked for me earlier today. Failed the first time, but i just ran it again and it went through. Thanks for the writeup!
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
do you have to have either 1.47 or 2.05 to use this method, or will the rooted supersonic 1.32.651.1 be able to do it?
because I installed htc sync, set the phone to HTC Sync, but the phone says it cant find it on my computer.
jasongthang said:
do you have to have either 1.47 or 2.05 to use this method, or will the rooted supersonic 1.32.651.1 be able to do it?
because I installed htc sync, set the phone to HTC Sync, but the phone says it cant find it on my computer.
Click to expand...
Click to collapse
Yes it will work for that version, you only set HTC Sync mode up to install any missing drivers, then you switch back to disk drive mode if you want your computer to gain access to your phones SD card.
Tundricles said:
Yes it will work for that version, you only set HTC Sync mode up to install any missing drivers, then you switch back to disk drive mode if you want your computer to gain access to your phones SD card.
Click to expand...
Click to collapse
so are you saying the htc sync doesnt have to actually sync? the phone never finds the htc sync on the computer. But I can get the computer to see the phone and access the sd card no problem.
Thanks for the write-up it worked just like planned. And with so many people returning for some reason or another this is just what we need
Im returning one and buying another at bestbuy HEHE
so will this return the Evo to shipped stock rom IF i did the OTA update? and will i be able to root if i have the OTA update?
thanks
I had the .6 stock(not root)and OTA updated to 1.47,how can I go back to .6 stock,I ran the .6 RUU,but it said main version older and refused to downgrade,anyone knows how do I reload the .6 back?my EVO ever rooted.
As far as I've been able to find by SEARCHING the forums:
NO
Once you do the OTA update you can NOT go back or downgrade or uninstall it or whatever.
This method posted is for installing a ROOTED ota update. ie, it was hacked, and rooted prior to being installed. If you downloaded it from sprint on your phone and installed it, your are SOL for now.
Sirchuk said:
As far as I've been able to find by SEARCHING the forums:
NO
Once you do the OTA update you can NOT go back or downgrade or uninstall it or whatever.
This method posted is for installing a ROOTED ota update. ie, it was hacked, and rooted prior to being installed. If you downloaded it from sprint on your phone and installed it, your are SOL for now.
Click to expand...
Click to collapse
That sucks...oh well,thanks for the info.
They're working on a fix, but I wouldn't hold your breath. Most of the devs are taking the weekend off for one reason or another.
Here's the discussion thread:
http://forum.xda-developers.com/showthread.php?t=714157
jasongthang said:
so are you saying the htc sync doesnt have to actually sync? the phone never finds the htc sync on the computer. But I can get the computer to see the phone and access the sd card no problem.
Click to expand...
Click to collapse
Yes, sync be damned!
Thanks for the write up.
Couldnt get it to go. Tried EVERYthing mentioned. Keep running into Error 170 USB connection error. I did dl HTC sync and let all the drivers install and rebooted my PC. And the phone.
Also tried multiple USB ports.
Nada.
not sure if this is any help, but I think the person in this thread had that same error, I hate to have you dig through the thread but I want to say it was mentioned on one of the later pages. Not sure if this is applicable to what you are doing.
http://forum.xda-developers.com/showthread.php?t=723236
elegantai said:
not sure if this is any help, but I think the person in this thread had that same error, I hate to have you dig through the thread but I want to say it was mentioned on one of the later pages. Not sure if this is applicable to what you are doing.
http://forum.xda-developers.com/showthread.php?t=723236
Click to expand...
Click to collapse
Thanks but sadly I've been through all the steps mentioned in all those links.
My USB is fine as I have been using it without issue.
I definitely cannot flash the .1 or .6 RUU.
I tried liquid jesus's method and it would not go either.
I'm stumped
Have u tried to flash the ruu as a zip?

[Q] Some Things Not Working On Desire [Q]

Anyone that can help me with this one, can be my new bestfriend
After getting really really depressed over being on the Official HTC Sense ROM with my Desire, I decided to change to the Starburst ROM. As the new Unrevoked doesn't work with the latest official build of Froyo from HTC I always, always use this when I want to downgrade and root, to install new roms.
Normally, I will use the utility as indicated, everything will go smoothly, Eclair 2.1 will install, however normally my phone will be locked, and I will have to remove my SIM, update to 2.2, my phone will become Unlocked after updating, and I will root. However this time, when the utility copied a misc_partition or something like that to my SD Card, it came up with a load of write errors, saying there wasn't enough room on my SD Card, which I know is wrong as there is well above 6GB on there, and it's a Goldcard. One advantage of the utility is, if anything goes wrong you can press CRTL-C and the utility will stop with no changes made to your phone, however in my case this wasn't so. I stopped the utility, thinking if I continued due to the write error I would encounter some more errors, and I decided to do a complete wipe of my phone using the on-board Factory Reset in the Setting's menu. After doing this, I started to encounter some problems.
First of all, when the phone enters the setup wizard, it says I have 4 bars of signal, and a 3G connection. After around 15 seconds of being in the Wizard, I will suddenly loose all mobile connection. After completing the setup wizard, I will be prompted by a notice telling me I need to Insert an SD Card. Well my card is in there, and I know its working because after these problems I put it into my brothers phone, and formatted it, and it showed up as working just fine. If an LG POP can mount my phone, surely a frigging HTC Desire can?
I have noticed that if I remove my SD Card, then the problems with the Network will go away and I will be able to connect, however sometimes when I boot it my phone will connect to the Network for about 5 minutes with the SD inserted, then return back to Limited Service. *I have attached a picture of what I am seeing.* This is really annoying me, I am going to download the Froyo 2.2 ROM from Shipped-Roms as the SD Card seems to mount fine in HBoot. Please though, can anyone help me. Thanks.
*This is starting to become very annoying now, I have been working on this for several hours now, and I still have no fix or nothing. I can't exactly be patient and I don't mean to sound like a tech addict, but my world revolves around my phone, I use it for business ect. When I connect my phone to my computer, I get a message saying 'Install Drivers For Qualcomm CDMA Technologies MSM' I have heard of CDMA before, but I don't think my phone is CDMA? My phone was originally branded Orange in the UK? Anyone that can help, just please please help me!
Hi, sorry I can't help with your problem as it seems too complicated to me (noob here) but reading what you wrote sort of alarmed me as I've been reading/watching videos on rooting and I thought that unrevoked (latest version) worked on any desire. It says so on the unrevoked site but you wrote you can't do it on yours because of new build of froyo.
Don't understand that, I'm on vodafone and asked advice to a few people about rooting and nobody told that I couldn't use unrevoked. Are you sure you can't use it. How about you do a factory reset and reflash rom and see how it goes. I do hope you're wrong about unrevoked though as I'm about to use it any day now (building up the courage...) Hope you get your problem solved.
well try to reinstall whole software via pc ...............
but check download latest version of official rom
back up your data as ur whole system sofware will be replaced
and do format ur sd in pc ( not a quick format )
hopefully it might resolve ur issues ( otherwise it seems a hardware issue >>>>>)
and i am not responsible for any sim locking or data loss sort of problems
wilborama said:
Hi, sorry I can't help with your problem as it seems too complicated to me (noob here) but reading what you wrote sort of alarmed me as I've been reading/watching videos on rooting and I thought that unrevoked (latest version) worked on any desire. It says so on the unrevoked site but you wrote you can't do it on yours because of new build of froyo.
Don't understand that, I'm on vodafone and asked advice to a few people about rooting and nobody told that I couldn't use unrevoked. Are you sure you can't use it. How about you do a factory reset and reflash rom and see how it goes. I do hope you're wrong about unrevoked though as I'm about to use it any day now (building up the courage...) Hope you get your problem solved.
Click to expand...
Click to collapse
Basically on the latest Froyo build from HTC (2.29.405.5) if you use Unrevoked, everything will go fine until it boots out of the bootloader to the actual software. On reboot Unrevoked will say 'Waiting for system to Settle'. This will never dissappear and it will wait for the system to settle forever and ever. However becuase you are branded on Vodafone, the chances are you're not running Froyo build 2.29.405.5, but a slightly older one. This is because when HTC release an update the phone companies have to put their software onto it, the the 2.29.405.5 update was only 5Mb, barely enough for the companies to be even bothered messing around with, so chances are you WOULD be able to root anyway, thanks for commenting.
commando0 said:
well try to reinstall whole software via pc ...............
but check download latest version of official rom
back up your data as ur whole system sofware will be replaced
and do format ur sd in pc ( not a quick format )
hopefully it might resolve ur issues ( otherwise it seems a hardware issue >>>>>)
and i am not responsible for any sim locking or data loss sort of problems
Click to expand...
Click to collapse
Oh I know about data loss, Sim Locking and all that, been there, done that, got the T-Shirt, I've got a Utility on my computer that will unlock my phone and as for Data Loss, Google servers have it all
I've got a bit of an update though, I know your saying it's a hardware error but I think there are two key components here that aren't working.
- The SD Card
- The SIM Card
I have come to believe this, because I managed to use the PB99IMG file to update to the latest Froyo, and now my phone is saying there is an SD in there, but stats about the SD are unavailable in my phone, and also when trying to connect to the network, my phone will not connect to Orange. If I click on Manually Select, and I click on Orange, I get a message saying SIM won't allow connection to this network, if I do it with Automatic however, it just says unable to connect to the network at this time. I'm gutted I haven't been able to fix this yet, it's really annoying me because normally I would be able to sort this, been up all night trying to do it, any help is greatly appreciated.
2.29.405.5 roots absolute fine with unrEVOked - if it didn't I wouldn't be rooted!!
EddyOS said:
2.29.405.5 roots absolute fine with unrEVOked - if it didn't I wouldn't be rooted!!
Click to expand...
Click to collapse
Possibly a problem with my Device or HBoot? Could anyone point me to the correct RRU for me to reset my phone with? I am running the latest software version with a goldcard, the card won't mount when the phone is turned on, thanks.
This is for the 2.29.405.5 RUU
http://www.multiupload.com/LEJCW182AH
EddyOS said:
This is for the 2.29.405.5 RUU
http://www.multiupload.com/LEJCW182AH
Click to expand...
Click to collapse
Really appreciate it mate, thankyou
*Update, I flashed this RRU, it's not working though :/
When you say not working what do you mean? More info needed!
Also, edit the 'Qualcom CDAM' thingy, that means its trying to install modem drivers - sounds you USB-bricked the phone
EddyOS said:
When you say not working what do you mean? More info needed!
Also, edit the 'Qualcom CDAM' thingy, that means its trying to install modem drivers - sounds you USB-bricked the phone
Click to expand...
Click to collapse
Yeah it won't connect in any way USB wise, and when IS ay not working, the OS works fine, connects to the network for the first 5 minutes, SD card won't mount, then after 5 minutes I get locked out of the network, and if I try and connect I get a message saying my sim won't allow connection to Orange :/ Think you can help?

[Q] Bricked Evo Help!!!

So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Do you have htc sync installed? It won't work unless you have the actual htc sync suite installed. Just google it won't cost you anything. I semi bricked my phone but I fixed it. Maybe some things I done in this thread could help you. Just skim through a few of my posts'.
http://forum.xda-developers.com/showthread.php?t=1100781
Sent from my PC36100 using Tapatalk
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
My last tip would be to put the phone in fastboot and then run the 3.29 ruu exe. It worked for me, here's the link. Just make sure you have htc sync installed and it's not running when u try to run the ruu (from fastboot in bootloader).
http://goo-inside.me/supersonic/sto...0.09.01_NV_1.77_CNV_release_150224_signed.exe
Sent from my PC36100 using Tapatalk
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
Was the phone rooted when he updated. In Hboot does it say s-off. If so try running the pc36img.zip of amon ra and see if you can get a recovery image back on the phone to work out of.
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
The RUU you used is pretty old, I would try a newer one, such as the 3.70 software. What version is your hboot, and is it S on or S off? Where is it bootlooping at? (the white HTC EVO 4G screen, or the actual boot animation?)
I selected the old one because that one never gives me issues, the 3.30 and 3.70 never work for me
Sent from my PC36100 using Tapatalk
k2buckley said:
The RUU you used is pretty old, I would try a newer one, such as the 3.70 software. What version is your hboot, and is it S on or S off? Where is it bootlooping at? (the white HTC EVO 4G screen, or the actual boot animation?)
Click to expand...
Click to collapse
My hboot is: HBOOT-2.16.0001
S-ON
Its bootlooping at the white HTC EVO4 screen.
Any ideas.
I have tried RUU:
3.26.651.6
3.29.651.5
3.29.651.6
3.29.651.5
3.70.651.1
The only one that actually does anything is 1.32.651.1 The rest just fail giving me an ERROR [170]: USB CONNECTION ERROR. Could be because HTC sync cant install the driver. How Can I get that driver installed. Could it be my OS?
lokoalex said:
My hboot is: HBOOT-2.16.0001
S-ON
Its bootlooping at the white HTC EVO4 screen.
Any ideas.
I have tried RUU:
3.26.651.6
3.29.651.5
3.29.651.6
3.29.651.5
3.70.651.1
The only one that actually does anything is 1.32.651.1 The rest just fail giving me an ERROR [170]: USB CONNECTION ERROR. Could be because HTC sync cant install the driver. How Can I get that driver installed. Could it be my OS?
Click to expand...
Click to collapse
I would try running the RUU as a PC36IMG, if you haven't already. Download PC36IMG of the RUU you wish to use, and put it on the main directory of your SD card. Then boot to the bootloader, and let it detect the PC36IMG. It should scan it, then ask you to update. Select volume up for yes, and let it run it's course. Perhaps that method will work out better for you.
Dirk, thats odd that you get errors on the new RUU's. Sometimes if the hboot and radios don't match up the RUU won't run.
EDIT: And yes, you definitely could be getting that error (most likely are) because HTC won't install the driver. You need to get that installed. I would still just try the PC36IMG though.
A1Lonestar said:
Was the phone rooted when he updated. In Hboot does it say s-off. If so try running the pc36img.zip of amon ra and see if you can get a recovery image back on the phone to work out of.
Click to expand...
Click to collapse
The phone was not rooted. I dont even know how to do that. LOL. I will try that pc36img file.
lokoalex said:
The phone was not rooted. I dont even know how to do that. LOL. I will try that pc36img file.
Click to expand...
Click to collapse
Just make sure that the file is named PC36IMG.zip (exactly that).
Sorry but I have to ask why your friend didn't bring it right to sprint and get them to fix it they would have replaced it in a second for a bad upgrade?
Sent from my PC36100 using XDA App
k2buckley said:
Just make sure that the file is named PC36IMG.zip (exactly that).
Click to expand...
Click to collapse
I ran it. It scanned it checked it and then nothing. Goes right back to the screen where it asks you to choose fastboot, recovery, ......
I did notice that my battery needs charging. Im gonna try again when the battery has some juice.
Also got HTC sync installed on my Windows & machine.Will give it a try too.
linsalata28 said:
Sorry but I have to ask why your friend didn't bring it right to sprint and get them to fix it they would have replaced it in a second for a bad upgrade?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My brother is impulsive and he didnt like the fact that it bricked on him. If it was me I would have definitely taken it to sprint.
You could try this don't know if they will or not but I'm kind of cool with some guys at one of those little stands in a mall now they are sprint but not really they helped me with an old phone I was having problems with that wasn't activated they don't really care and they have the tools to fix things but the one I go to like to show me just how much they know about androids witch isn't much LOL.
Might be worth a shot you might find a guy thats into moding and would like to show off.
Sent from my PC36100 using XDA App
linsalata28 said:
You could try this don't know if they will or not but I'm kind of cool with some guys at one of those little stands in a mall now they are sprint but not really they helped me with an old phone I was having problems with that wasn't activated they don't really care and they have the tools to fix things but the one I go to like to show me just how much they know about androids witch isn't much LOL.
Might be worth a shot you might find a guy thats into moding and would like to show off.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not a bad idea. Might have to find some of those guys.
k2buckley said:
I would try running the RUU as a PC36IMG, if you haven't already. Download PC36IMG of the RUU you wish to use, and put it on the main directory of your SD card. Then boot to the bootloader, and let it detect the PC36IMG. It should scan it, then ask you to update. Select volume up for yes, and let it run it's course. Perhaps that method will work out better for you.
Dirk, thats odd that you get errors on the new RUU's. Sometimes if the hboot and radios don't match up the RUU won't run.
EDIT: And yes, you definitely could be getting that error (most likely are) because HTC won't install the driver. You need to get that installed. I would still just try the PC36IMG though.
Click to expand...
Click to collapse
I've been trying man. Im getting nowhere with this. I tried the RUU 3.70 and it just crashed asked me if I wanted to debug. So im gonna try one of the older versions. At least its seeing these with the HTC sync working.
lokoalex said:
I ran it. It scanned it checked it and then nothing. Goes right back to the screen where it asks you to choose fastboot, recovery, ......
I did notice that my battery needs charging. Im gonna try again when the battery has some juice.
Also got HTC sync installed on my Windows & machine.Will give it a try too.
Click to expand...
Click to collapse
Yea, I would either try an RUU again now that you've got HTC Sync installed, or format your SD card, and put ONLY the PC36IMG on there, then try it again. The only time I've seen a PC36IMG file not ask you to update is if the card needed to be formatted for one reason or another.
k2buckley said:
Yea, I would either try an RUU again now that you've got HTC Sync installed, or format your SD card, and put ONLY the PC36IMG on there, then try it again. The only time I've seen a PC36IMG file not ask you to update is if the card needed to be formatted for one reason or another.
Click to expand...
Click to collapse
I tried the RUU again and it gotas far as the signature and then it crapped out again.
Error [140] BOOTLOADER VERSION ERROR.
Have no idea what the problem could be. Gonna try reformatting the card one more time and see what happens. So frustrating!!!
Maybe try to update or downgrade your hboot version.
Sent from my PC36100 using XDA App
*Assuming you're working on a windows machine*
Go to this site http://shipped-roms.com/index.php?category=android&model=Supersonic
and download ruu 3.70.
Without your phone connected, run the ruu until it gets to the first dialog box (it should have a checkbox that says "I understand the caution..." blah blah).
With this dialog still open, go to start > run and type "%TEMP%" without quotes.
Inside this folder look for a file called "rom" or "rom.zip" (you are going to have to go through all subfolders) depending on your windows settings (Hide extensions for known file types).
When you find it move it to your desktop and rename it to "PC36IMG" or "PC36IMG.zip" accordingly.
Get a card reader and take your sdcard out of your phone and place it in the card reader. Place the PC36IMG file you renamed on the root of the sdcard. Install your sdcard back into the phone and boot into bootloader. This should scan the card and find the PC36IMG and reinstall a bone stock non-rooted 2.2 rom.
If this method fails, it's possible the nand may have been corrupted in the update process. I'm better at troubleshooting if I have the device with me so this is the best I can do.
lokoalex said:
I tried the RUU again and it gotas far as the signature and then it crapped out again.
Error [140] BOOTLOADER VERSION ERROR.
Have no idea what the problem could be. Gonna try reformatting the card one more time and see what happens. So frustrating!!!
Click to expand...
Click to collapse
That is frustrating. It sounds like there may be a problem with your current boot.img, and maybe that's why it won't let the RUU re-write the boot.img when it's trying. That would also explain you not being able to boot, because if your bootloader is corrupted somehow, then you won't be able to get anywhere at all. Unfortunately, the bootloader you're on (HBOOT-2.16)isn't downgradeable. I'm starting to suspect that you're getting the bootloader version error because when you run the older RUU, it will try to flash an older version of hboot. Since the version you're on is NOT able to be downgraded, it's probably erroring out when it tries to downgrade, but it can't. I would suspect that if the RUU for the 4.22 software was available and you were able to run that one, then it would succeed. The problem is that you're trying to downgrade, and you can't do that. I'm not sure what went wrong when the OTA was accepted, but it seems like something did, and now you're stuck. I would guess that the only way to fix it would be to reflash the OTA (which you can't because you can't boot), or run the RUU for 4.22, which isn't available yet. My speculations may not be accurate, but that's my guess!

Help! Semi-Bricked Evo... Despairing, here

OK, I posted in the Q&A section, but not finding much love. Hopefully someone here might be more help.
The first thing to put out there is that I did not accept the Gingerbread OTA. Still on 2.2.
Here's the story: A couple of days ago I tried running unrevoked on my Evo. One month old, HW version 0004. I'm pretty sure I did everything as instructed, but the procedure failed. Machine would run for 30 seconds or so then drop into diagnostic mode (5 vibrations & lock).
So I tried re-flashing back to stock. The first stock image I tried screwed the phone up in that: (1) it would no longer see USB connections (2) no longer saw my Micro SD card (3) would no longer charge when the phone was on.
So I tried flashing a newer stock image, the third one on this page:
http://forum.xda-developers.com/showthread.php?t=884060
That only made matters worse, as now I've lost bluetooth, too.
Keeping in mind that I cannot communicate with the phone via USB (unrevoked now just keeps waiting for me to plug the phone in, as does HTC Sync, which I installed after everything else as a last shot) and am not rooted, what are my options here? I really want to get this device back to stock, because I need a phone that works.
If I take it back to a Sprint repair store will they even look at it? Can they flash it back to stock for me or am I SOL there?
I've been thinking that I could let the OTA install and if everything's still broken take it to Sprint and tell them the OTA screwed up my phone, but I'm worried I've left traces that would tell them I'm bullshitting.
Hell at this point I'm willing to pay $$ to get this thing fixed, motherboard swap or whatever, but I'm not sure Sprint will even do that.
Gotta have my phone back guys, any help greatly appreciated.
Let me clarify... So at the moment you have a version of a stock rom on the phone, and it will actually turn on?
However, you can't "connect" per se to the phone?
You could either email yourself the files you need or use "Awesome Drop"
OR
I've read that if you've bricked or screwed your phone around the time of an OTA happening to come out, you can go to Sprint and tell them you tried to accept the OTA update, Make up some BS about blah blah blah, and then you're left here with a phone that's acting really weird and is borked.
Generally the tech will re-flash as they are familiar with the issues OTAs can cause.... Or they may give you a refurb.
TF1984 said:
Let me clarify... So at the moment you have a version of a stock rom on the phone, and it will actually turn on?
However, you can't "connect" per se to the phone?
You could either email yourself the files you need or use "Awesome Drop"
OR
I've read that if you've bricked or screwed your phone around the time of an OTA happening to come out, you can go to Sprint and tell them you tried to accept the OTA update, Make up some BS about blah blah blah, and then you're left here with a phone that's acting really weird and is borked.
Generally the tech will re-flash as they are familiar with the issues OTAs can cause.... Or they may give you a refurb.
Click to expand...
Click to collapse
I'm not rooted, though, so I doubt any files I could e-mail myself would do any good.
I am considering taking the phone back to Sprint, but I don't know whether to accept the OTA then make up some story about losing Bluetooth, SD Card access and USB, or just being honest and telling them what I did.
At this point I just want to get my phone back to stock and working as it should. I'll leave the rooting adventures to others. Rooting my Nook Color is one thing, since it's basically a $250.00 toy, but I can't live without my phone.
Try this:
http://forum.xda-developers.com/showthread.php?t=695243
However, will need root to fix the USB problem. You should look into some temp root options that will allow you to use a terminal emulator to fix the USB issue. I've never tried a temp root method, so you're going to have to do some digging around for that. Maybe someone who knows more about temp root can chime in and help.
You could start one of two ways...
Either email yourself the S-Off and Recovery Image files, move them to proper place
Or take it to Sprint. Just tell them teh OTA messed something up. Don't think up a whole world of stories or truths. Trust me, they're used to it.
TF1984 said:
You could start one of two ways...
Either email yourself the S-Off and Recovery Image files, move them to proper place
Or take it to Sprint. Just tell them teh OTA messed something up. Don't think up a whole world of stories or truths. Trust me, they're used to it.
Click to expand...
Click to collapse
So, accept the GB OTA, then?
My Sprint store is also a repair facility. Do they have hardware and tools that can re-flash the device to stock regardless of what you've done to it? because that's what I'm thinking of doing at this point.
My biggest problem with attempting to fix it myself is that not being rooted and not having USB access I seem to be SOL.
BTW: I just testes WiMax and it works, so at least my WiMax key is good.
Will your phone recognize the SD at all? If you can get another card to work, you could theoretically run a PC36IMG of the RUU through the bootloader. However, you'll need your SD card working. If your computer will recognize it but the phone won't, you can try backing up the contents, then formatting/partitioning the card. Then move just the PC36IMG to the card, boot into the bootloader, and hopefully it'll ask you to update.
If you can't get anything to work, then download the OTA and start installation. The OTA may fix it... but probably not. If it does fix it, hooray!, but you're stuck without root until an exploit is found. If it doesn't fix it, take it into Sprint and tell them you took the update and your phone is acting funny. Technically if you word it that way, you're not lying
If the card can't be recognized, don't worry about the files on it. If it can, just delete any PC36IMGs or other files related to rooting/troubleshooting. Other than the SD card, there shouldn't be any way to tell you attempted to root as long as you're s-on & cannot access recovery.
If you don't have insurance, I'm not sure how Sprint will handle it. If you do, they should either fix it or replace it for free.
(from... Evo/MIUI/Tapatalk)
plainjane said:
Will your phone recognize the SD at all? If you can get another card to work, you could theoretically run a PC36IMG of the RUU through the bootloader. However, you'll need your SD card working. If your computer will recognize it but the phone won't, you can try backing up the contents, then formatting/partitioning the card. Then move just the PC36IMG to the card, boot into the bootloader, and hopefully it'll ask you to update.
If you can't get anything to work, then download the OTA and start installation. The OTA may fix it... but probably not. If it does fix it, hooray!, but you're stuck without root until an exploit is found. If it doesn't fix it, take it into Sprint and tell them you took the update and your phone is acting funny. Technically if you word it that way, you're not lying
If the card can't be recognized, don't worry about the files on it. If it can, just delete any PC36IMGs or other files related to rooting/troubleshooting. Other than the SD card, there shouldn't be any way to tell you attempted to root as long as you're s-on & cannot access recovery.
If you don't have insurance, I'm not sure how Sprint will handle it. If you do, they should either fix it or replace it for free.
(from... Evo/MIUI/Tapatalk)
Click to expand...
Click to collapse
When boot into the bootloader and choose "restore" it does recognize the SD card. That's how I managed to flash this image (third klink on page) and get back to stock:
http://forum.xda-developers.com/showthread.php?t=884060
So it's definitely a software issue with the phone preventing me from seeing the card/USB or connecting to bluetooth.
At this point I don't mind not being rooted. Having a working phone is more important.
And unfortunately I don't have insurance, but I'll pay the repair fee if they ask me to.
dsf3g said:
When boot into the bootloader and choose "restore" it does recognize the SD card. That's how I managed to flash this image (third klink on page) and get back to stock:
http://forum.xda-developers.com/showthread.php?t=884060
So it's definitely a software issue with the phone preventing me from seeing the card/USB or connecting to bluetooth.
At this point I don't mind not being rooted. Having a working phone is more important.
Click to expand...
Click to collapse
Did you try the SD card fix I posted above? I think with the SD card fixed and temp root you'll be able to fix both problems.
rugedraw said:
Did you try the SD card fix I posted above? I think with the SD card fixed and temp root you'll be able to fix both problems.
Click to expand...
Click to collapse
Thanks, I'll try that. I saw that thread earlier, and I just noticed that someone answered my question about fastboot. So I'll see if I can fix USB using that.
What really bugs me now is the lack of Bluetooth!
XDA search is down right now so I can't see if there are any others who have experienced this.
Please note that with the link I gave you, you can fix the SD card not being detected issue, but to fix the USB port using those instructions, you need root. Since Unrevoked won't work without the USB, you would have to either try a temp root method (I've never used it so I can't offer you much help there) or some other manual root method where the USB port isn't needed.
Step 1, Go into Device Manager
Start Device Manager.
Windows 7
Click Start > Control Panel > System and Security > Device Manager.​ Windows Vista
Click Start > (Settings) Control Panel > (System and Maintenance) > Device Manager.​ Note If prompted, click Continue.​ Windows 2000 / XP
Click Start > (Settings) Control Panel > (Performance and Maintenance) > System > Hardware > Device Manager.​
Step 2, These Devices are typically installed when you Install HTC Sync or Just connect your Android Device, If their are no conflicts uninstall all of them and restart your PC, Then Reconnect your android Device
The following devices are normally installed:
If a red X, yellow ! or yellow ? is displayed to the left of a listed device, a conflict is present and the drivers must be updated or reinstalled.
Note Driver conflicts may also be indicated by a device entry labeled Other Devices or Unknown.
Android USB Devices
My HTC​Disk drives
HTC Android Phone USB Device​Modems
HTC Modem (if using as a tethered modem)​Portable Devices
E:/ (Where E represents the assigned drive letter.)​Universal Serial Bus controllers
USB Composite Device​ USB Mass Storage Device​
kingakuma said:
Step 1, Go into Device Manager
...
Click to expand...
Click to collapse
Thanks, Kingakuma, I'll try that, but I don't think the problem is on the PC side. My Evo won't recognize the charger when it's plugged in, so I'm pretty sure the issue is on the Evo.
dsf3g said:
Thanks, Kingakuma, I'll try that, but I don't think the problem is on the PC side. My Evo won't recognize the charger when it's plugged in, so I'm pretty sure the issue is on the Evo.
Click to expand...
Click to collapse
are you using the same usb cable for the charger?
if so try a different usb cable
so rom boots but somethings just do not work correct? bluetooth and usb and sdcard correct? follow the above advice to fix sdcard as mentioned then download z4root from here, to try and root since you are still on froyo temp root should work, at which point download rom manager. use rom manager to install either clockwork or amon ra recovery, boot to recovery, flash rom, profit!
link for z4root
http://forum.xda-developers.com/showthread.php?t=833953
DomSim said:
so rom boots but somethings just do not work correct? bluetooth and usb and sdcard correct? follow the above advice to fix sdcard as mentioned then download z4root from here, to try and root since you are still on froyo temp root should work, at which point download rom manager. use rom manager to install either clockwork or amon ra recovery, boot to recovery, flash rom, profit!
link for z4root
http://forum.xda-developers.com/showthread.php?t=833953
Click to expand...
Click to collapse
Thanks, but how can I download or install this without an SD card mounted?
dsf3g said:
Thanks, but how can I download or install this without an SD card mounted?
Click to expand...
Click to collapse
ok, we can't help you if you do not follow directions. read my post, and those of the others who posted. one contains a link to a thread to fix the sdcard. you have been told to do this several times. i told you to do this first then get z4root. im done helping you, good luck.
Use z4root in order to achieve temp root for previous mentioned fixes.
Wohooo! I've fixed the SD Card issue! Thanks all, even DomSim, who's apparently given up on me in frustration. Give a noob a break, DomSim. I'm new to all this and am trying to balance reading this stuff with a family that also needs my attention.
I've got Z4Root installed and verified root, too. I'll probably fix the USB issue at work, since I don't need a computer connection for that and it's getting late (yeah, I usually leave for work just after 5:00 AM).
Once I've got the USB issue sorted I'll have to take a look at the bluetooth issue. I'm hoping its related to the USB situation and will be cured at the same time, but suspect that's just wishful thinking on my part.
Just completed the USB repair portion and.... SUCCESS!!!!! BEYOND MY WILDEST DREAMS, actually, as Bluetooth now works also.
I was hoping that the bluetooth functionality depended on USB (I think I recall that the bluetooth module on my Dell Mini 9 was USB based) and lo and behold, it does!!!!
Thanks again to everyone who helped out. You guys are first class!

[ROM] Gingerbread for Incredible 2 is coming

RUU(full rom):
http://www.megaupload.com/?c=premium&l=1
It seems an offical version, but maybe a test one.
It includes many languages to select, e.g. Simple Chinese, English and so on..
Update before, you'd better make your phone S-off !!
Drool
Sent from my ADR6350 using Tapatalk
I've flashed this, with out root (Don't need it). Everything is pretty solid. There's a 5th metal skin i've seen included with the incredible S, The Get more htc widgets works, quadrant gives me a 1510 or so.
Anyone who has experienced the 'input lag', where typing to fast will cause the phone to lock up for a sec then spit out the text, should know that gingerbread fixes that.
The only issue I've seen so far is the vzw app crashes constantly if you update it. If you don't update it, it's fine, but you can't access usage info.
This is 2.3.3, so it doesn't have the updated Gtalk video chat, If you root, there should be a way to install it.
excuse me for being such a noob,
i admit. the force is not strong with this young padwon..
how do i go about flashing this update to my stock unrooted dinc2?
i remember how i flashed my OG D1 but was having some troubles with this new beast,
thanks for any advice in advance boys!
This would be done through fastboot... it will will recognize the leak as a real update and flash for you.
But in doing so, like it has been said in other posts: You will lose the capacity to root with Alpharex.
no renaming the file to update.zip or anything? nothings poping up through the fastboot screen other than the standard options
does it do a wipe or is it an actual update (No Data Loss)?
bigslam123 said:
does it do a wipe or is it an actual update (No Data Loss)?
Click to expand...
Click to collapse
The installer warns of a full data wipe, but i cannot get the ruu installer to find my phone connected to the system...anyone have any insight?
would it be possible to go back to froyo once s-off is released? i do want to check this out but not at the expense of not being ready for s-off once it is made public.
mikejaret said:
The installer warns of a full data wipe, but i cannot get the ruu installer to find my phone connected to the system...anyone have any insight?
Click to expand...
Click to collapse
This is what I did using win7 x64: *BECAUSE I DO NOT CARE FOR ROOT*
First, download the latest version on HTC sync... it has all the drivers you need, and takes care of error 171 (when the phone reboots and the RUU is waiting)
Next, enable USB debugging, this takes care of error 170. You can do this by going to menu>settings>applications>development
If you encounter any other errors, try running the RUU program as admin, and using vista sp2 compatablity mode.
Edit: also, no you don't have reboot into fastboot. The RUU program does some initial checks (software ver. battery %, other bs) then reboots the phone for you.
HTH
bigslam123 said:
does it do a wipe or is it an actual update (No Data Loss)?
Click to expand...
Click to collapse
YES. you lose all data (text, phone log, programs).
The programs reinstalls automagically for the most part though, since it's backed up with android market. I thought that wifi passwords would be backed up with this system as well (it does with CM7) but no dice.
cougar618 said:
This is what I did using win7 x64: *BECAUSE I DO NOT CARE FOR ROOT*
First, download the latest version on HTC sync... it has all the drivers you need, and takes care of error 171 (when the phone reboots and the RUU is waiting)
Next, enable USB debugging, this takes care of error 170. You can do this by going to menu>settings>applications>development
If you encounter any other errors, try running the RUU program as admin, and using vista sp2 compatablity mode.
Edit: also, no you don't have reboot into fastboot. The RUU program does some initial checks (software ver. battery %, other bs) then reboots the phone for you.
HTH
Click to expand...
Click to collapse
So grab the file.. Then what?
where does the file go? Assuming it's on the SD card? (Sorry, first HTC phone since G1) and then once the phone is detected and in USB debugging then what?
@cougar618, besides for that typing lag fix you mentioned, are there any other upgrades/changes that you noticed so far? i'm real curious and want to check this out but also so eager for root... AHHH!!!!
presence06 said:
So grab the file.. Then what?
where does the file go? Assuming it's on the SD card? (Sorry, first HTC phone since G1) and then once the phone is detected and in USB debugging then what?
Click to expand...
Click to collapse
You don't put it on your SD card. The File is actually an EXE file, you run it on your computer. .. it took me quite a while to figure that out when I had the OG inc lol. so dl the file, dl the HTC sync and install for the drivers, and run the RUU program that you dl.
For me, the Typing lag fix was the sole reason for me to install the GB update. asides from that, GPS seems to work much better, and it seems very stable. Batter life is not that geat, but it was not that great for me on froyo (I use my phone as an mp3 player, etc).
and a bit off topic, but I can't check partial wake usage on GB. Anyone with froyo able to? I tried with spare parts, and I know there's a code you can dial, but can't find it.
what's partial wake usage?
cougar618 said:
You don't put it on your SD card. The File is actually an EXE file, you run it on your computer. .. it took me quite a while to figure that out when I had the OG inc lol. so dl the file, dl the HTC sync and install for the drivers, and run the RUU program that you dl.
For me, the Typing lag fix was the sole reason for me to install the GB update. asides from that, GPS seems to work much better, and it seems very stable. Batter life is not that geat, but it was not that great for me on froyo (I use my phone as an mp3 player, etc).
and a bit off topic, but I can't check partial wake usage on GB. Anyone with froyo able to? I tried with spare parts, and I know there's a code you can dial, but can't find it.
Click to expand...
Click to collapse
Ok.
According to some including Droid Life, you need to be root to install the RUU? Is that true?
nope root not needed
presence06 said:
Ok.
According to some including Droid Life, you need to be root to install the RUU? Is that true?
Click to expand...
Click to collapse
False.
There are two files out there, one on this forum by jcase, for rooted users, and the official RUU from HTC, that removes the root exploit someone found. once rooted, you can do S-off, which allows for you to root the phone later.
As i've said, I don't care for root, so I just used the RUU from htc.
Please do some more research on this before trying anything...
Also, off topic again, partial wake usage is when the cpu is woken from sleep for an application, such as listening to music.
alright guys here we go.
i figured it out ! LOL
you must install the htc sync program so that your DINC2 and SYNC link up through your WINDOWS based pc.
after that you download the RUU in the original post,
run it and it will open on its own.
that is all you gotta do.
however,
I do not think there is a way to uniinstall this update and it has been mentioned that this build may NOT link to future ota's
can anyone provide more insight on the ota part?
I'm going to be one sad panda if i can't get any updates because i jumped the gun with this RUU
cougar618;15134771
Also said:
ahh.. icic.. hmm i didn't even know you could see a stat like that in froyo haha.
Click to expand...
Click to collapse

Categories

Resources