Develop Bugs

[Q] RUU will NOT install, help?

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.

Desire Won't Recognise SIM following update

I have just updated my Desire to what I think was 2.29 following a system software notification. It went through ok, rebooted and said sucessful, however, it will not recognise my SIM, I keep getting "No SIM card in phone error". The SD card is mounted ok, and from what I can see everything else appears to be working.
Info;
Software number;
2.29.405.5
I haven't rooted the phone, messed about with it in ANYway...I have rebooted the phone and reseated the SIM about 10 times now, no change...
Please please is there anything I can do? Am I going to have to factory reset?
thanks
Anthony

Any ideas?? Sorry I'm completely stuck and won't be able to get hold of T-mobile for days yet....

Try another sim card in the phone, test your sim card in another phone, post back after you have done that as you can see what is at fault.

Arrgh, sorry I was sure I'd typed all that down...
Yes I already have put another SIM in, a pay as you go which also doesn't work. I have tried putting my SIM in another phone and it works fine...so definitly not that.
T-Mobile have no ideas, they hadn't heard of it, they gave me HTC's number but they shut naturally....and will be until Wed at the earliest

Sounds to me as the sim reader on the phone is faulty, you can try pushing on it and holding it and see if that helps, if not you are stick till you can send the phone away for repair, seems odd tho that it happened after the update.......

I have the same problem with my Desire. After the update, it won't recongnize the SIM.

Can you some how re-run the update or do a ruu file update.

I tried with another SIM in my phone and it's working. So is it possible that the update damaged the SIM?
Sent from my HTC Desire using XDA App

I would not think so, sometimes if you have a older sim it does not work, it looks like you sim card is at fault, phone up your operater and see if you can get a newer one.

Ok then. Thank you for the advices.
Sent from my HTC Desire using XDA App

The OP's problem maybe because of the new radio that is included in this OTA.
It's a bit strange as this is the first reported issue with a sim that isn't working after an applied OTA (as far as I know).
It's a general rule of the thumb that, if you have a problem occurring right after an OTA, then you should reinstall it. So you might give it a try - download the OTA, and reapply it manually.

Yes the SIM works in another phone. And I hadn't touched the phone after the update, just let it reboot and it failed to recognise.
This is a good idea though, I will try and download the update and install it again.

Am I gonna have to flash the whole phone to do this? From what I've read you can't just apply the small (5mb update) you have to do the big 168mb one? Sorry, n00b at this.

Only the update (5MB).
If you flash the 168MB one you'll lose your data, as it's a complete ROM, not an update.
Edit: The OTA seems to be missing from shipped roms but I've found it over at some german blog and uploaded it here.

Thanks for the info. Ok I manually updated, which went through ok again, but no change
I will have to try factory reset, I just can't see what would stop the SIM being recognised.....
Unless theres anything else you can think of? I will perform hard reset...really don't want to though.
Hoping my phone isn't knackered.

If you were fine before going to the latest update, you could try to revert back by flashing the 2.29.405.2 rom which is in essence the same as the latest. Download this 161MB zip http://www.shipped-roms.com/downloa...9.00.32U_5.11.05.27_release_151783_signed.zip
Then rename it to "PB99IMG.zip" (zip is the extension, not part of the name)
Put in in your sd card, without placing it in any folders
Turn off, Turn on holding the volume down key, and you shall be asked to apply it.
This will erase all your data, just like a factory reset.

any luck with this, just done the same on mine NOT rooted and NOT branded Desire on Orange. I can see all the networks when I scan for them but whem I try and connect to one it says 'your SIM card does not allow these services' or something similar

What version did you update to the 405.2 or 405.5?

now running 405.5

Go back to 405.2 if you can seems the 05 update is the problem here.

[Q] Another Bricked Desire

Yes, this is another HTC Desire bricked thread.
Also very yes, I've read a plethora of what I considered similar threads, on this forum and others.
THE HARDWARE:
Us Cellular Branded HTC Desire.
THE PROBLEM:
I rooted the phone without problems. I then attempted to flash several (read: a dozen or so) different ROMS following tutorials to the letter. Most were Froyo ROMS with Sense UI. I like HTC Sense.
So, after trying dozens of different ROMs, none of them gets past the white boot screen with green "htc" text. Sometimes the phone would auto reboot a few times and then shatter my hopes by getting stuck again, and again... and again.
WHAT I HAS DONE:
After proving the cake was no lie, I created a gold card. I then followed some nice instructions about using previously mentioned card to flash non-branded ROMs. After I mopped up my tears of rage and frustration from all these ROMS still getting stuck on the same white boot screen, I wrote this post.
Also, I went in to my local us cellular store (I know the tech who works there) hoping he could do me a favor.. but since the phone was rooted (yes i know i'm an idiot for trying) he could do no such thing.
Also, I tried downloading .exe (RUU files?) that set up a wizard on my pc to fix my desire but they couldn't connect to my device... connection error message kept coming up.
I am willing to crawl up a temple on my knees for penitence if need be to get this fixed. But please don't *only* send a few links to "similar" threads...

Sounds like an usb brick. Follow this guide to repair:
http://forum.xda-developers.com/showthread.php?t=691639
If finished, try to unroot your phone by flashing fitting ruu again.
Btw, a question: which hardwarerevision does your desire have? You find this out, when you boot into hboot and read the number behind the word pvt (first line). Another question: which recovery system do you have?
No warranty for any damage!

Sry for the post, Mat was quicker

The hard part is finding a fitting RUU... since the US Cellular brand does not seem to be popular.
I *FINALLY* got a RUU to flash via fast bootusb.... and it looks like i am in the clear... as far as that goes.
We shall see how this works out.
Thank you (I hit thanks button too)

MasterofAll said:
The hard part is finding a fitting RUU... since the US Cellular brand does not seem to be popular.
I *FINALLY* got a RUU to flash via fast bootusb.... and it looks like i am in the clear... as far as that goes.
We shall see how this works out.
Thank you (I hit thanks button too)
Click to expand...
Click to collapse
Good luck!

If flashing of the US cellular rom fixes it then odds are the goldcard did not work. Goldcards can be temperamental to setup and keep setup correctly.
If you repartition you need to set it up again. I have had a lot of annoyances due to this on my phone.

Thanks all
Everything works great... save for my SD card (which was a gold card). I ended up formatting it with my pc, then reinserting and everything seems fine.

MasterofAll said:
Thanks all
Everything works great... save for my SD card (which was a gold card). I ended up formatting it with my pc, then reinserting and everything seems fine.
Click to expand...
Click to collapse
Congratz!

Another victory for the community.
Good job all !

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