Just in case you need it, here it is.
http://www.pcdphones.com/downloads/Eris MR1.zip
This is the Dec 11th update?
Yes but it is the full ruu not just the update if you use this you will loose all of you data and settings.
This may be a work around for those experiencing problems since the update.
this works great for the phone os issues caused by the update. but there are apps in the market that cause your phone to freak out. it's not the eris's fault or the apps fault. when upgrades happen like the way htc did this one it bound to cause some apps to freak out cause of the update. htc has no obligaton to support these apps either that's on the app creator to fix htc is only fixing it's own issues.
this is the reason why htc doe not like quick patches to thier phones. if you look at the history of the dream/G1 this is the first quick patch other than 1.30. because 1.29 allowed root level commands in the contacts area but that was to fix that problem not to fix customer complaints. i just hope htc goes back to the we'll get you a patch when we get you a patch mentality. cause it seems less problematic that way.
just my feelings
binny1007 said:
Yes but it is the full ruu not just the update if you use this you will loose all of you data and settings.
Click to expand...
Click to collapse
Thanks! I did the manual update using RUU as soon as it came out and actually have been pretty lucky...None of the freezing up etc issues that people are having.
Anyone have an updated link?
Hungry Man said:
Anyone have an updated link?
Click to expand...
Click to collapse
I've got the EXE if you have something/somewhere I can upload it to?
You could use megaupload? Or try uploading it to this site aka xda?
If I were to just install the 2.1 leak wouldn't that do basically the same thing? Or is this easier?
The RUU in this thread was for MR1, which is still Android 1.5. I think you're looking for the newer RUU: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe
Ok so if I download that what do I do with it to unroot?
Hungry Man said:
Ok so if I download that what do I do with it to unroot?
Click to expand...
Click to collapse
Attach your phone to your computer with the USB cable, and run the RUU program in Windows. It will wipe all data from your phone and return it to the stock 2.1 software, complete with the 1.49 S-ON bootloader, the default recovery image, and no root.
If you want to re-root from there, you'll have to use one of the new root methods, since your phone will be identical to the phones that Verizon is currently shipping out (with Android 2.1), not the original Android 1.5 version of the software.
Awesome, thanks a ton.
i am trying to use this to unroot my phone so i can send in for a replacement and it goes through all the checks and verifications. it rebbots to the bootloader then while updating signiture i get error 140 bootloader version error saying the rom update utility cannot update your android phone please get the correct rom update utility and try again?? if this doesnt work is there another easy way to unroot?
yamaha83 said:
i am trying to use this to unroot my phone so i can send in for a replacement and it goes through all the checks and verifications. it rebbots to the bootloader then while updating signiture i get error 140 bootloader version error saying the rom update utility cannot update your android phone please get the correct rom update utility and try again?? if this doesnt work is there another easy way to unroot?
Click to expand...
Click to collapse
same here, ruu fails
sleepyastronaut said:
same here, ruu fails
Click to expand...
Click to collapse
If you get a version error, you need to first run jcase's "Flash any RUU" hack.**
Note that (strictly speaking) jcase should have entitled his post "Flash any PB00IMG.zip ROM" because of another small complication: some ROMs do not have a compatible version of the "reboot" command (the RUU utility first uses the reboot command to put the phone into oem-78/RUU mode). If you insist on using the RUU utility, you can overcome this minor problem by first flashing a compatible ROM, such as PlainJane.
But, it is just as easy to flash the Leak-V3 PB00IMG.zip ROM, which produces the identical result as the "Official" RUU.
Note also that if you have used the RUU utility, them you already have USB drivers installed on your PC, and so getting adb running on the PC does not require setting up the full-blown SDK (you don't need Eclipse set up) : just download the SDK, unzip it, and you are ready to rumble.
To reiterate: if you get a version error, you need to run jcase's "Flash any RUU" hack first; after that, you can either run the HBOOT+Leak-V3 PB00IMG.zip install, or the RUU. The PB00IMG.zip method has no dependencies, and is somewhat easier.
bftb0
** Note there is a minor mistake in the instructions given in the OP of the "Flash any RUU" thread; be sure to read the first dozen posts or so - the correction is given.
thenestor said:
The RUU in this thread was for MR1, which is still Android 1.5. I think you're looking for the newer RUU: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe
Click to expand...
Click to collapse
This is the exe that I used to restore my Eris from Kaos Froyo to Stock 2.1. All I did was run the exe file and follow simple prompts. It took about 10-15 mins and the Eris was ready to return to VZW.
Very nice work, Thank you Devs!!!
Does flashing RUU replace the kernel and/or radio? Just wondering
jsuh said:
Does flashing RUU replace the kernel and/or radio? Just wondering
Click to expand...
Click to collapse
I'm pretty sure it replaces both. That's how people discover new kernel and radio versions.
Sent from my xtrSENSE Eris using XDA App
Any idea what I'm doing wrong here?
Windows 7 SP1 x64
Related
So I'm assuming that the "One Click Root" method is not going to work in Donut. Is that correct?
If so, I'll need to downgrade to Cupcake first. Does anyone have a download link? Is there anything I need to do before applying the update.zip to downgrade?
Thanks for your support
OolonColuphid said:
So I'm assuming that the "One Click Root" method is not going to work in Donut. Is that correct?
If so, I'll need to downgrade to Cupcake first. Does anyone have a download link? Is there anything I need to do before applying the update.zip to downgrade?
Thanks for your support
Click to expand...
Click to collapse
Go read the many stickies on rooting. You don't downgrade to Cupcake, you downgrade all the way back to RC29.
cigar3tte said:
Go read the many stickies on rooting. You don't downgrade to Cupcake, you downgrade all the way back to RC29.
Click to expand...
Click to collapse
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
lbcoder said:
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
Click to expand...
Click to collapse
My apologies, only thought of the G1.
lbcoder said:
Your suggestion doesn't make any sense since there are plenty of devices that shipped with 1.5 (i.e. rogers dream), which happen to be quite incompatible with 1.0 firmware. It is therefore impossible to downgrade to rc29.
If you're *very lucky*, the bootloader you have won't enforce versions and might actually allow downgrading to 1.5, in which case the 1c-root procedure will work.
Click to expand...
Click to collapse
Are you saying that I wouldn't be able to root using the "traditional" method?
OolonColuphid said:
Are you saying that I wouldn't be able to root using the "traditional" method?
Click to expand...
Click to collapse
Post your phone info before you ask that.
cigar3tte said:
Post your phone info before you ask that.
Click to expand...
Click to collapse
Sorry. It's a US T-Mobile G1
I would like to know the answer to this too. I was updating to 4.1.999, something went wrong and now im on 1.6 dev phone firmware. Im not sure if i can go back to rc29 or not or if i should even try. Won't going back to RC29 with the new SPL brick my phone?
(Current) Details are
G1 / Dream phone
firmware 1.6
hard SPL
Build: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Normal recovery console
Thanks
HardSPL won't brick phones, not to the same degree as dangerSPL anyways.
If you have a REAL SPL (i.e. Engineering, or Hard -- can't imagine why anyone would want that though since it doesn't offer any real advantage over Engineering), then there is ABSOLUTELY NO REASON to go flashing nbh's/downgrade to rc29. The reason for this is that these bootloaders do NOT enforce signatures, and DO allow full access to the system. The only reason for going to rc29 is if you have a RECENT VERSION UNHACKED device that is CARRIER BRANDED (and happens to be compatible).
If you have Engineering SPL or similar, then the ONLY thing that nbh's will do is RISK CREATING A BRICK.
Yes, you can brick *any* time you write an NBH, IPL, or SPL (not just the deathspl). Chances are low, but if something goes wrong, its dead.
sprarky said:
I would like to know the answer to this too. I was updating to 4.1.999, something went wrong and now im on 1.6 dev phone firmware. Im not sure if i can go back to rc29 or not or if i should even try. Won't going back to RC29 with the new SPL brick my phone?
(Current) Details are
G1 / Dream phone
firmware 1.6
hard SPL
Build: dream_devphone-userdebug 1.6 DRC83 14721 test-keys
Normal recovery console
Thanks
Click to expand...
Click to collapse
lbcoder said:
If you have a REAL SPL (i.e. Engineering, or Hard -- can't imagine why anyone would want that though since it doesn't offer any real advantage over Engineering), then there is ABSOLUTELY NO REASON to go flashing nbh's/downgrade to rc29. The reason for this is that these bootloaders do NOT enforce signatures, and DO allow full access to the system. The only reason for going to rc29 is if you have a RECENT VERSION UNHACKED device that is CARRIER BRANDED (and happens to be compatible).
If you have Engineering SPL or similar, then the ONLY thing that nbh's will do is RISK CREATING A BRICK.
Yes, you can brick *any* time you write an NBH, IPL, or SPL (not just the deathspl). Chances are low, but if something goes wrong, its dead.
Click to expand...
Click to collapse
OK cool. Thanks for that. That confirms a few things for me.
Now this might seem a little ignorant but how do i get my root back now? I have done several searches but couldn't really find anything that confirms the exact method for this situation.
If there is no reason to go back to RC29 and do that whole process again then whats the other way of doing it?
As i now have the normal recovery console back any attempt to try and flash CM's just results in the phone telling me i cant su (or don't have root)
Thanks again
Sounds like you have acess to fastboot with your spl you could use fastboot to flash cyanogen's or whichever recovery image you choose, then you would be able flash any rom's you would like through recovery
jackslim said:
Sounds like you have acess to fastboot with your spl you could use fastboot to flash cyanogen's or whichever recovery image you choose, then you would be able flash any rom's you would like through recovery
Click to expand...
Click to collapse
Yeah i do! that sounds exactly like what i need to do. You know of a how-to anywhere for doing this?
Cheers
Do you already have fastboot installed on your pc?? If not a simple search of theese forums can yield you instructions on setting up fastboot. Once you have it installed you can open up a terminal and go the directory in which your recovery image is stored and run the command
fastboot flash recovery cm-recovery1.4.img assuming you're using cyanogen's recovery
jackslim said:
Do you already have fastboot installed on your pc?? If not a simple search of theese forums can yield you instructions on setting up fastboot. Once you have it installed you can open up a terminal and go the directory in which your recovery image is stored and run the command
fastboot flash recovery cm-recovery1.4.img assuming you're using cyanogen's recovery
Click to expand...
Click to collapse
Hey,
Thanks for your help. Managed to get it all working they way you described after some searching and a few hours. Thanks again dude.
OolonColuphid - Hope i didn't hijack your thread too badly. Does any of the above information help you out at all? I found it fairly easy to flash the recovery from fastboot then flash back to whatever i want via the recovery console.
Cheers,
Sean
Alright, I've been doing some reading up on rooting and it sounds interesting. I tried following the steps on theUnlockr.com but keep running into issues. Just FYI, I recently upgraded to 1.6 Donut from 1.5 thru a phone update so it is NOT stock in my phone. Please let me know what I need to do (in lamens terms) so I can get this going.
G1/Dream
Firmware 1.6 Donut
Build Number: DRC83
Please let me know what I need to do (in lamens terms) so I can get this going.
ephayzee said:
Alright, I've been doing some reading up on rooting and it sounds interesting. I tried following the steps on theUnlockr.com but keep running into issues. Just FYI, I recently upgraded to 1.6 Donut from 1.5 thru a phone update so it is NOT stock in my phone. Please let me know what I need to do (in lamens terms) so I can get this going.
G1/Dream
Firmware 1.6 Donut
Build Number: DRC83
Please let me know what I need to do (in lamens terms) so I can get this going.
Click to expand...
Click to collapse
You're phone is still considered stock because it has unmodified software on it, even though you have 1.6 it's through the official OTA update whether installed manually or recieved in due time over your network. You can root your phone, pretty much just follow the steps outlined in this guide found on theese forums
http://forum.xda-developers.com/showthread.php?t=442480
jackslim said:
You're phone is still considered stock because it has unmodified software on it, even though you have 1.6 it's through the official OTA update whether installed manually or recieved in due time over your network. You can root your phone, pretty much just follow the steps outlined in this guide found on theese forums
http://forum.xda-developers.com/showthread.php?t=442480
Click to expand...
Click to collapse
Good looking man, thanks!
Does FlashRec still work on donut, or have they patched that exploit?
OolonColuphid said:
Does FlashRec still work on donut, or have they patched that exploit?
Click to expand...
Click to collapse
OMG! can u not read!
I have searched and searched, tried every method, but I am offically stuck (I think) - I'm prepping a rooted Eris for return - i had previously been able to flash the 2.1 RUU to return to stock, but it now will not work - I guess somewhere along the lines of rooting/ROM flashing my bootloader has changed (it is now v1.49.000) - I can't get any RUU to work (get ERROR in RUU interface) - I have also tried flashing a P00IMG through HBOOT, but it also errors out (something is older than something else - forgot exactly) - I have tried flashing new HBOOT/Recovery Image through ADB per a JCASE post, but that will not work either - I've gotten older ROM's loaded that will allow for new OTA updates, but they ultimately will not work (signature issues i believe) -
So the question is, is there a method that will get me back to 2.1 "stock" & get rid of Amon Ra recovery?
Again, I have searched and tried every method I could find - I have updated my SDK - help anyone?
Ive seen people just send in rooted ones without any problem, so I dont know if they'll check. But if your worried, i would just flash a 2.1 rom that looks like the stock, cause i dont think they'll know the difference.
Do you have a Nandroid backup from when you first rooted?
crax0r said:
Do you have a Nandroid backup from when you first rooted?
Click to expand...
Click to collapse
Unfortunately I don't have it - you wanna loan me yours?
I'm only kind of kidding....
download unzipme.zip which jcase removed on xda from here http://androidmobileos.com/?p=14928 Inside theres dowgrade rom that you flash through custom recovery (which ever one you use). After that you just follow the instructions (adb parts). Works very well. If you will have any issues with adb part as far as flashing back to stock recovery and hboot than check your hboot version and make sure its s-off. If its not you can get it s-off with batery pull trick.
i had an issue like this where the ruu would say that my phone was disconnected and told me to connect it to the computer,i was on a froyo rom,i flashed a 2.1 rom and the ruu worked,just an fyi just incase this might help if you want to return to stock 2.1,once you run the ruu and sync with google you wiil receive the july update also.
sent from my Eris using Tapatalk pro
Everywhere in this wonderful forum I read that it is very easy to go back to a shipped rom. Just download it, click the exe-file and follow instructions.
BUT: I unrooted my WF and flashed the Puzzlerom (very good rom, by the way). Now when I try to install original rom, it says that I've got the wrong bootloader on my device. The one on my device seems to be newer than the one the shipped rom expects before install. So the RUU halts and no flashing.
I think we have to have this sorted out. I think many people will want to try the new official Froyo for Wildfire, which will be out soon, we all hope. So you have to go back to original rom, don't we?
Anyone who knows how to handle this?
jfcc58 said:
Everywhere in this wonderful forum I read that it is very easy to go back to a shipped rom. Just download it, click the exe-file and follow instructions.
BUT: I unrooted my WF and flashed the Puzzlerom (very good rom, by the way). Now when I try to install original rom, it says that I've got the wrong bootloader on my device. The one on my device seems to be newer than the one the shipped rom expects before install. So the RUU halts and no flashing.
I think we have to have this sorted out. I think many people will want to try the new official Froyo for Wildfire, which will be out soon, we all hope. So you have to go back to original rom, don't we?
Anyone who knows how to handle this?
Click to expand...
Click to collapse
extract the update.zip from the rru (google it), copy to sd and choose install update.zip in fastboot
Also try:
Boot up in Bootloader
Then chose Fastboot.
plug phone to pc and run patch. worked for me
brilldoctor said:
extract the update.zip from the rru (google it), copy to sd and choose install update.zip in fastboot
Click to expand...
Click to collapse
That's definitely something i would love to know.
Thanks.
Btw, any chances you might know how to go back to original recovery rom? Now I got clockworkmod done in by unrevoked3. Not sure if there is one thou as I only come to know the existence of recovery portion after unrevoked.
Just asking for knowledge. Thanks.
mod: If this should be in DHD General, please move it
At the moment, sometimes current RUUs (ROM Update Utility) do not flash from the latest RUU exe - many times it will not recognise the Desire HD.
If you are having this problem, this is how to flash the latest stock RUU.
The latest RUU at the time of writing is 1.32.405.6.
You can download the RUUs from xmoo's thread or from mousey_'s site.
note: This is mainly for stock phones, for vendor-derived ones (e.g Vodafone DHDs in Australia) you will also need a goldcard.
Common Steps
Download the latest RUU (1.32.405.6).
Run it as administrator.
Tick the 'I understand the caution indicated above...' box, and click next.
At this point do not go any further.
Navigate to C:\Users\Ivo\AppData\Local\Temp (Replace my username with yours; AppData is a hidden folder)
You should see one or two folders like this:
{719CE201-7B12-4A13-9AF6-8F359FE69C7B}
Go into the one with dotnetinstaller.exe in it.
Open up the next folder.
Copy rom.zip into another folder (outside of temp).
At this point just Cancel and quit out of the ROM Update Utility.
A) Install through PC
Download and install HTC Sync 3.0 and restart.
Download the 1.15.405.1 Test RUU. It is the only one currently known to find the Android DHD.
Start it the same way as before, get to the
1. Connect the Smartphone to the USB Cable.
step. (but no further)
Again, go to the AppData local temp directory (same as above), and find the folder with dotnetinstaller.exe and inside that, rom.zip
You want to delete the rom.zip (which is the 1.15 version) and replace it with (copy back) the 1.32 rom.zip you copied out earler.
DO NOT UPDATE WITH 1.15 ROM, IT IS NOT DESIGNED FOR RETAIL DHDs.
Now click through the next buttons.
The 1.15 Utility should now be set to update with the 1.32 rom. You will see the version number of the rom at the final step.
Click update and watch the magic happen
B) or Install through Phone
With the rom.zip you copied out earlier, rename it PD98IMG.zip
Copy this onto the root of your microSD card through some means (disk drive, ftp, wireless).
Restart your phone and boot into the bootloader by holding power and volume down at the same time as it restarts.
It should go into the bootloader, take a fair while to check the zip on the sd card, and then ask you if you want to flash it.
Say yes!
Hope this can help some people for whom the 1.32 RUUs aren't working for them
Thanks for putting up this post! I was about to request one last night.
Now if only there could be a similar guide to flashing custom ROMs
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems, a bit longer than updating/reinstalling a WinMo 6.5.x rom (my former HD2), but it went through...
Thanks Ivolol this worked a treat
Appreciate your guide and efforts.
I am running Win 7 64. folowed 1.15 method now running latest 1.32.405.6
Howling Wolf said:
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems, a bit longer than updating/reinstalling a WinMo 6.5.x rom (my former HD2), but it went through...
Click to expand...
Click to collapse
Weird; I tested a couple of RUUs (not as many as xmoo did) and all of them couldn't connect to my phone (whereas 1.15 could).
It'd be interesting to find out what the factors are that cause this. ATM the guide above is what to do if someone finds themselves in the same situation (the current ROMs won't find the phone).
Howling Wolf said:
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems.
Click to expand...
Click to collapse
+1 here, went through the normal RUU process fine just for ****s and giggles. I've extracted the ROM.zip though in case it's needed for future use.
sorry for the noob question..just had my DHD for the last 5 days. I come from galaxy S, and in there whenever we flash a rom all the data gets wiped out.
is it true also when we flash a RUU??
also if I do that...would i still be able to get OTA updates??
nandihno said:
sorry for the noob question..just had my DHD for the last 5 days. I come from galaxy S, and in there whenever we flash a rom all the data gets wiped out.
is it true also when we flash a RUU??
also if I do that...would i still be able to get OTA updates??
Click to expand...
Click to collapse
I haven't got complete knowledge of the entire subject yet, but:
a RUU will completely wipe all user settings / apps. Won't do anything to the sd card though.
An update.zip is akin to an OTA update, it does not wipe user settings.
Flashing with a stock RUU will mean that you can still get OTA updates.
I've tried using the phone method and unable to flash successful. I believe you need a valid GoldCard to use this method.
Can you confirm if the GoldCard is required for doing it with the phone method?
In addition, once the unit (especially our Voda branded one) is flashed with the latest ROM, OTA may not run properly which will result in disabled functionality (as recorded in this thread: forums.whirlpool.net.au/forum-replies.cfm?t=1575514, wifi stopped working). Theory said you'll need a GoldCard to get OTA to work properly (from another thread in XDA).
Thanks.
Great Guide thank you very much. Now i know to flash back to stock now if something gose wrong as iam a noob to android it took some time to work it out even tho it is a simple guide now i wanna know after getting perm root how do i flash a custom rom ? do i need clockwork mod?
tleehm said:
I've tried using the phone method and unable to flash successful. I believe you need a valid GoldCard to use this method.
Can you confirm if the GoldCard is required for doing it with the phone method?
In addition, once the unit (especially our Voda branded one) is flashed with the latest ROM, OTA may not run properly which will result in disabled functionality (as recorded in this thread: forums.whirlpool.net.au/forum-replies.cfm?t=1575514, wifi stopped working). Theory said you'll need a GoldCard to get OTA to work properly (from another thread in XDA).
Thanks.
Click to expand...
Click to collapse
There is a big reason I decided to buy my DHD outright and not through Vodafone
I'm pretty sure that Vodafone's OTAs will be different from HTC's. In order to get OTAs from Vodafone you will need their image on it.
Also with vodafone's ROM installed, I wouldn't think it would accept HTC's vanilla ROM/RUU without going through the entire root process (it would only accept Vodafone signed ROMs). So in order to get onto HTC's ROMs I would think you need to follow http://forum.xda-developers.com/showthread.php?t=841076 before the phone will let you run a HTC RUU on it.
I haven't explored goldcards as I personally have no use for one, but you might also need one by the sounds of it for the Vodafone ROM to let you replace it. (edit: yes it looks like you need one to officially flash from a Vendor ROM to a generic one.)
So this guide is mainly for people with vanilla HTC phones. Although someone has posted a stock rooted Vodafone ROM on the phones so you might be able to use the same techniques outlined here with that.
ssimmmo said:
Great Guide thank you very much. Now i know to flash back to stock now if something gose wrong as iam a noob to android it took some time to work it out even tho it is a simple guide now i wanna know after getting perm root how do i flash a custom rom ? do i need clockwork mod?
Click to expand...
Click to collapse
clockwork mod is useful but not entirely necessary. You might be able to use this guide's method to flash a custom ROM onto it (haven't tried yet), but otherwise I think what you need is a recovery img that will let you upload custom/unsigned ROMs onto it. And also S-OFF I imagine.
ok so i have S-OFF and clockwork mod recovery...
if i have the rom.zip and rename it to PD98IMG.zip and run bootloader.
i shouldnt have any problems flashing this rom??
BTW am using Aus branded Vodafone HDH.
also..IF i flash this rom..would i loose S-Off and clockwork recovery mod??
would flashing this allow me to gain OTA???
nandihno said:
ok so i have S-OFF and clockwork mod recovery...
if i have the rom.zip and rename it to PD98IMG.zip and run bootloader.
i shouldnt have any problems flashing this rom??
BTW am using Aus branded Vodafone HDH.
also..IF i flash this rom..would i loose S-Off and clockwork recovery mod??
would flashing this allow me to gain OTA???
Click to expand...
Click to collapse
If you flash a stock RUU rom.zip then you will loose all custom apps, data, s-off, recovery, etc. It puts it to factory settings. If you are in the business of flashing ROMs then I wouldn't worry about OTA because the developers here will integrate HTC updates as they come out, if they come out
However yes I think if you flashed a stock RUU then you will be able to get OTA. You might still need a goldcard, I'm not exactly sure.
ivolol said:
mod: If this should be in DHD General, please move it
At the moment, sometimes current RUUs (ROM Update Utility) do not flash from the latest RUU exe - many times it will not recognise the Desire HD.
If you are having this problem, this is how to flash the latest stock RUU.
The latest RUU at the time of writing is 1.32.405.6.
You can download the RUUs from xmoo's thread or from mousey_'s site.
note: This is mainly for stock phones, for vendor-derived ones (e.g Vodafone DHDs in Australia) you will also need a goldcard.
Common Steps
Download the latest RUU (1.32.405.6).
Run it as administrator.
Tick the 'I understand the caution indicated above...' box, and click next.
At this point do not go any further.
Navigate to C:\Users\Ivo\AppData\Local\Temp (Replace my username with yours; AppData is a hidden folder)
You should see one or two folders like this:
{719CE201-7B12-4A13-9AF6-8F359FE69C7B}
Go into the one with dotnetinstaller.exe in it.
Open up the next folder.
Copy rom.zip into another folder (outside of temp).
At this point just Cancel and quit out of the ROM Update Utility.
A) Install through PC
Download and install HTC Sync 3.0 and restart.
Download the 1.15.405.1 Test RUU. It is the only one currently known to find the Android DHD.
Start it the same way as before, get to the
1. Connect the Smartphone to the USB Cable.
step. (but no further)
Again, go to the AppData local temp directory (same as above), and find the folder with dotnetinstaller.exe and inside that, rom.zip
You want to delete the rom.zip (which is the 1.15 version) and replace it with (copy back) the 1.32 rom.zip you copied out earler.
DO NOT UPDATE WITH 1.15 ROM, IT IS NOT DESIGNED FOR RETAIL DHDs.
Now click through the next buttons.
The 1.15 Utility should now be set to update with the 1.32 rom. You will see the version number of the rom at the final step.
Click update and watch the magic happen
B) or Install through Phone
With the rom.zip you copied out earlier, rename it PD98IMG.zip
Copy this onto the root of your microSD card through some means (disk drive, ftp, wireless).
Restart your phone and boot into the bootloader by holding power and volume down at the same time as it restarts.
It should go into the bootloader, take a fair while to check the zip on the sd card, and then ask you if you want to flash it.
Say yes!
Hope this can help some people for whom the 1.32 RUUs aren't working for them
Click to expand...
Click to collapse
As I am Newbie of Android and I have noob quesitons. Could you please explain what is RUU and use this for what purpose?
Yeah. I got a goldcard inside of my phone but the bootloader doesn't recognize the P98IMG on my sdcard even though its there for sure. No idea how to fix this
Dr. lele said:
Yeah. I got a goldcard inside of my phone but the bootloader doesn't recognize the P98IMG on my sdcard even though its there for sure. No idea how to fix this
Click to expand...
Click to collapse
How big is ur sd-card, and also what brand. Sometimes this is also a issue....
It's a kingston 8 gb class 4, but thanks for the tipp, I'll try another.
Yep, it was the sdcard xD. It's updating as I type
Carnt I just use the updater on the pc with the Rom? I have tried the method and I don't see a Rom file just a data1 file which is a ear file. I really would like stock ROM on my device
edit: i just used the exe and it installed perfect, so now it should be stock with no root,and sn
cxeka7 said:
As I am Newbie of Android and I have noob quesitons. Could you please explain what is RUU and use this for what purpose?
Click to expand...
Click to collapse
An RUU is an exe which contains the stock 'firmware' from HTC to flash to your device. Basically it will do a full factory reset of your device. It won't wipe your sdcard but it will overwrite everything else.
it didnt asked me for anything on option B) or Install through Phone. i didnt get the option to flash it.
Right now, the previous rage/Visionary rooting methods do *not* work with the latest 1.72 ROMs for the Desire Z.
UPDATE - If you have upgraded to 1.72 already without S-OFF, then a temp root has been achieved for 1.72, which gives you the capability to downgrade to an earlier ROM (e.g. 1.34) where you can permanent root. The "psneuter" procedure is at via this procedure - http://forum.xda-developers.com/showthread.php?t=905261
UPDATE 2 - This "psneuter" procedure can be used to achieve permanent root. If you obtain S-OFF at an earlier ROM level, *then* update to 1.72, you can get permaroot with psneuter, then use the usual methods to lock this in as a permanent root. This is because the S-OFF means the NAND write protection will not be enabled. If you are already at 1.72 without S-OFF, you will have to downgrade, obtain S-OFF, then upgrade again.
This ROM version is being rolled out as an OTA update to European DZ users. So far it doesn't seem to have been rolled out to other DZ carriers, e.g. Bell, Vodafone, though I suspect that it is only a matter of time.
This update does not *yet* affect the G2 running the stock T-Mobile ROM, though again I suspect this update will make its way to the G2 in time (so you might wish to turn off automatic checks for updates if you want to avoid the possibility).
This is an example of what is in the warning thread at the top of the forum, i.e. don't upgrade to this until we know how you can root it, assuming you are interested in root (which I think most, though not all, people here are).
I've tried all kinds of stuff but nothing works.
I've even made a goldcard with a PC10IMG.zip (rom extracted from RUU) but it gives me an error: MAIN VERSION OLD
So flashing back to an older version.............forget it!!
RUU, Visionary and Gfree method will not work with this stupid update!
Does anyone know what's in the 1.72 release that we're missing ? (And therefore whether its worth S-On & de-rooting)
Ramsfan_Jim said:
Does anyone know what's in the 1.72 release that we're missing ? (And therefore whether its worth S-On & de-rooting)
Click to expand...
Click to collapse
The Virtuous ROM includes all the stuff in 1.72 already. So there's no point derooting and going S-ON, just install Virtuous.
Sticky worthy untill a solution is found.
rmk40 already found a solution to rooting these newer builds, but it requires changes to the SuperUser app. He's submitted those to the author but there hasn't been a new version release yet.
Hm,I`m now on stock 1.34.405.5 Firmware (RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e _26.03.02.26_M)
but rooted and S-OFF with UBERROOT method!
Now if I flashing this Firmware I still have S-OFF but I lose
Root and can`t Root again right?
The same happens if I trie this Root and S-OFF method and flashing
the new Firmware:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
If you are desperate to try it, nandroid backup, google "extract rom.zip from ruu" and install through recovery.
..sent from my CyanogenMod'd HTC Vision
That will not work. I've already tried it.
maus010 said:
That will not work. I've already tried it.
Click to expand...
Click to collapse
Why not?
..sent from my CyanogenMod'd HTC Vision
Glad there is a dedicated thread for this. I have applied the OTA (stupid me... should have read this forum first) and am now looking forward to getting root again so i can do SetCPU to underclock when screen off..
I'm happy to do any testing for those who get anythin working.
Also noticed in this new ROM (OTA) that when i plug in my wall charger, it goes straight into "CAR PANEL"?!
When i use the official HTC cable it does not - but when using a mini USB cable + micro USB adapter, it goes straight into car mode.
Does this have the same issue if you just flash the radio?
wileykat said:
Why not?
Click to expand...
Click to collapse
Because it gives me an error: MAIN VERSION OLD
So it wil not flash.
As long as you still have a custom recovery (i.e. Clockwork), I can help. See the thread I just created here:
http://forum.xda-developers.com/showthread.php?t=886999
If not, sorry I cannot help. Obtaining root again is for the black hats around here.
I wont root my DZ since setCPU profiles dont work.
rmk40 said:
As long as you still have a custom recovery (i.e. Clockwork), I can help. See the thread I just created here:
http://forum.xda-developers.com/showthread.php?t=886999
If not, sorry I cannot help. Obtaining root again is for the black hats around here.
Click to expand...
Click to collapse
Thanks for your help.
But the OTA update also flashed the bootloader and recovery back to stock.
The only thing positive with this update is the batterylife.
It hase improved bigtime!
Agree - battery seems heaps better.
Is anyone working on this? Got my DZ and subconsciously accepted.
Am now because I need to keep using the damn power button to wake it up!
zappoo said:
Also noticed in this new ROM (OTA) that when i plug in my wall charger, it goes straight into "CAR PANEL"?!
When i use the official HTC cable it does not - but when using a mini USB cable + micro USB adapter, it goes straight into car mode.
Click to expand...
Click to collapse
There's a note in the manual for the DZ that says if you use an adapter it will think it's plugged into a car kit.