[RUU][Virgin Mobile] HTC desire 816 a5chl RUU file. - Desire 816 General

This is just a thread for the RUU file, relock your bootloader, rename the file to "0P9CDIAG.zip" and place on root of External SD card.
Then boot into Hboot, and Hboot will automatically detect it and flash it.
Download link: https://www.dropbox.com/s/ay5y8s8dg...S_0.57_003_release_385969_signed_2_4.zip?dl=0 Thank you @jaysoblitzed
Just to be clear, this is for the US a5chl (Virgin Mobile). If you flash this on any other Desire 816, it will most likely mess up your device. I've never flashed an incompatible RUU, but without one for your phone it might become unusable.
I'll upload mirrors if people ask

FoxyDrew said:
This is just a thread for the RUU file, if you want instructions on how to flash go to THIS thread. (Thank's @18th.abn)
It's simple, just make sure you follow all the instructions or you could screw up your device!
Download link (1.20.510.1): https://www.dropbox.com/s/l09xcmc55d7beak/a5chl_RUU.zip?dl=0
Just to be clear, this is for the US a5chl (Virgin Mobile). If you flash this on any other Desire 816, it will most likely mess up your device. I've never flashed an incompatible RUU, but without one for your phone it might become unusable.
I'll upload mirrors if people ask
Click to expand...
Click to collapse
I believe that is just the kernel source. Obtained from htcdev.com correct?
Also, here is the actual RUU . You can tell which is which by the size.
https://www.dropbox.com/s/ay5y8s8dg...S_0.57_003_release_385969_signed_2_4.zip?dl=0

jaysoblitzed said:
I believe that is just the kernel source. Obtained from htcdev.com correct?
Also, here is the actual RUU . You can tell which is which by the size.
https://www.dropbox.com/s/ay5y8s8dg...S_0.57_003_release_385969_signed_2_4.zip?dl=0
Click to expand...
Click to collapse
Ay thats a good look, I'm an idiot.
"Support" guy I was talking to definitely said it was a RUU. Considering his horrible English I should've assumed he didn't even quite know what I needed.

FoxyDrew said:
Ay thats a good look, I'm an idiot.
"Support" guy I was talking to definitely said it was a RUU. Considering his horrible English I should've assumed he didn't even quite know what I needed.
Click to expand...
Click to collapse
Edit: Just the kernel source in the 154MB .zip
Since the device still has S-ON and a closed CID the RUU would require you to be on stock and never have unlocked the bootloader. With S-OFF it skips the signature check to allow it to write regardless of if it's relocked or unlocked and can even allow downgrading. S-OFF accesses parts of the filesystem that is still currently sealed off; even imei writing in the bootloader.
[Deleted]

The Kitikat.zip file fails while flashing
The kitikat.zip file fails while flashing. It says "Device halted due to Large image update"
I have also tried the lollipop RUU file but the HTC Rom utility says Signature Error wrong Rom file.
Can yuo please upload the latest HTC desire Lollipop 5.0.2 RUU or zip file.

Related

Official Eris RUU

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

[GUIDE] Installing RUU's

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.

[REQUEST] Can anyone write a guide for Unrooting

Its only going to be a matter of time before people will need to send phones back under warranty for whatever reasons so a guide for unrooting will be needed.
Any takers?
G2 already has one, but obviously we will need different rom/hboot etc to go back to our stock.
Not just unrooting, but going completely back to stock, i.e. S-ON and stock ROM.
As you say, we should be able to base it on this - http://forum.xda-developers.com/showthread.php?t=835971
Although we have several different stock ROMs, e.g. European, Asian, Vodafone UK, etc.
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
gtrab said:
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
Click to expand...
Click to collapse
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
steviewevie said:
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
Click to expand...
Click to collapse
It does say to flash an RUU to S-ON which in the past I would have said would work, but seeing how the G2 forums are not suggesting that its that simple my guess would be that its not that simple.
I had to flash the PC10img thing taken from the stock ROM to restore root and s-on. But no idea how to extract that PC10img thing, not that I have looked into it either.
That info was from one of the guides in the dev section I'm sure.
Sent from my HTC Vision using XDA App
What might work now will probably not work once an OTA update comes out for the DZ though, as per the problem on the G2 they've had which has led to quite a few semi-bricks (possibly full bricks in some cases ?).
Done some research, it would seem that flashing an RUU would work fine for those of us already rooted, if an OTA were to come out those who rooted after the OTA would have issues unless an RUU for the same OTA was released as well. (this is basically because the RUU's currently available will be older than the software the phone is on so the RUU would fail leaving you with a semi-bricked phone as described above, basically it would flash stock hboot and recovery then fail to flash the /system so you would be left with no root or recovery and no rom.
Flashing the ruu would give rise to accepting the OTA too, if you really wanted to do that, but it might block root.
you just need the RUU for your correct original phone version
OR use a gold card
eg. I have debranded mine from bell NAM 1.34.666.5 to euro generic 1.34.405.5
To go back to stock, I can:
1.- grab the bell 1.34.666.1 RUU (its slightly previous, but is the correct original version for my phone)
OR
2.- run the euro generic 1.34.405.5 with a golcard inserted
gtrab said:
you just need the RUU for your correct original phone version
Click to expand...
Click to collapse
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
steviewevie said:
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
Click to expand...
Click to collapse
Yes thats what I was getting at in my post above, any RUU you flash needs to be of the same or newer version of what your previously flashing. You cannot GoldCard to flash an RUU to S-ON or you get left with the semi-brick where you have stock recovery and hboot, but no rom installed.
So if an OTA comes out, you can't accept it, s-off then use an older RUU to s-on again. You would have to flash an RUU of that OTA version (if one is released).
Basically its best to not accept any OTA if you can avoid it and just wait for a custom rom of the same, that way we can always use the older RUU's to s-on if we need it.
I successfully downgraded my rooted/S-OFF'd phone to an earlier ROM last night. I simply followed this method - http://forum.xda-developers.com/showthread.php?t=832503
I'm of the firm belief that this is the onyl way to do it if you are at S-OFF. If you have S-OFF, then flashing an older RUU will probably brick your phone.
Well yesterday I perm root and s-off my european Desire Z with World/Euro generic 1.34.405.5. Somehow everything went bad after flashing recovery mode, so I decided to unroot it and bring it back to original settings.
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Then entered to bootloader, and the phone recognize the archive, I simply apply it, and now I am back again to original stock.
However now I tried again and I am happily root, and S-Off following the amazing gtrab guide (http://forum.xda-developers.com/showthread.php?t=835777)
buzmay said:
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Click to expand...
Click to collapse
That's the thing I keep saying though, flashing the original RUU worked for you because you weren't trying to downgrade the ROM, it was the same version that you already had on (just S-OFF etc). If you had a later version on your phone (e.g. via an OTA update) and were trying to flash to an earlier one, you would have bricked it trying the straight RUU method.
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
By the way - that's a fake RUU
DanWilson said:
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
Click to expand...
Click to collapse
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
steviewevie said:
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
Click to expand...
Click to collapse
I hate HTC.
Love the phones, love the Sense, hate the security.
Why not give us a command like the N1? WHY!?
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
DanWilson said:
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
Click to expand...
Click to collapse
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
steviewevie said:
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
Click to expand...
Click to collapse
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Nice
DanWilson said:
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Click to expand...
Click to collapse
Following that guide that I linked worked for me. Yes, I turned my SD card into a gold card and edited the misc partition. Then it is fooled into thinking you're restoring a ROM of the same version that it already is running, so it lets you do it.
Actually, I do wonder whether both steps are necessary (i.e. gold card *and* editing misc), because I thought the whole point of the gold card was that it avoided those checks, so perhaps you can do one or the other ? I am only thinking out loud here, and may well be missing something, so I don't suggest trying it other than as in that guide.

Desire HD official rom needed

Hi everybody:
I'm in real trouble,i need original ruu rom for my desire hd,htc support site does not give me exe file.My phone sn is HT13ARX02053.Can you please share it with me?
Heres all the RUUs you need - LINK (credits go to andyharney)
CodeNameUnknown1 said:
Heres all the RUUs you need - LINK (credits go to andyharney)
Click to expand...
Click to collapse
I need ruu file just for this SN
Sorry for the late reply, but in not sure that they make RUU for each SN.
The SN is just an ID for the phone so the company can know where this certain phone was shipped to and where it was sold, etc...
But the Carrier does matter, which is why, on andy's website, he has different RUU for different carriers.
You can choose the WWE version (2.2 froyo-(1.32 FW) and 2.3 Gingerbread-(2.36 FW) are available) if you didnt buy it from a certain carrier
@OP what is your firmware version. Not your android version, your HTC firmware.
Failing that, make a gold card thus allowing you to negate the CID check and extract the Rom.zip file from the latest unbranded HTC RUU and apply it using the bootloader. Worked for me and dead easy too.
Sent from my Desire HD using XDA App
top really needed this!!!!!!!
Now i've downloaded 2 firmwares,the names follow below.I can't install any of them due to "Customer ID error",how can i install any original firmware?
RUU_Ace_Gingerbread_S_HTC_WWE_2.36.405.8_R_Radio_12.54.60.25_26.09.04.11_M2_release_187331_signed.exe
RUU_Ace_HTC_WWE_1.32.405.6_Radio_12.28b.60.140e_26.03.02.26_M_release_155891_signed.exe
PS:I have goldcard.
Your goldcard is required for flashing PD98IMG.zip's, I'm sure it has no relevance to RUU's.
You have a branded/network locked device, you need a matching RUU.
What is your HTC Firmware version.
Andy is right - if you want to just apply what is essentially an RUU of your choice you need to:
1. Run the RUU exe so that it fires up then find the ROM.zip file on your PC. Should be under your usernames temp folder somewhere. You only need to open it to it's first screen to get access to the files it extracts - no need to go any further.
2. Rename the file to PD98IMG.zip and put it onto the root of your Goldcard.
3. Boot the phone into the bootloader by holding the volume button down as you turn it on. Make sure the Goldcard with the zip file on is inserted at this point.
It'll check the zip and ask if you want to apply it, at which point it'll flash the lot as the Goldcard bypasses the CID check which is what's been stopping your RUU from working.
That's all I did but using a 1.32 stock ROM then applied the 2.3 RUU over the top to get me to Gingerbread from the horrible 1.72 HTC ROM riddled with bugs.
Andy, that process should work for anyone shouldn't it?
Yep, that is the process.
It worked for me thanks.
Can i flash my phone with cooked roms which have root access via the same method so that i won't need to do extra operatins.

[GUIDE] REVONE, MOONSHINE & RUMRUNNER Pre-S-OFF Steps.... READ FIRST

IMPORTANT INFORMATION!
READ THIS BEFORE GOING TO THE S-OFF THREADS​
This simple guide is aimed at giving you the best chance at achieving S-OFF on your device. Although not all of the steps listed below are 100% necessary if you are failing to achieve S-OFF or still receiving errors of any sort then you either cannot S-OFF your phone or you haven't followed the guide. In my opinion your best hope for S-OFF is by using RUMRUNNER. It supports the largest amounts of firmware and the support is great.​
You should only use MOONSHINE/REVONE to S-Off if......
1. You are on or flash a STOCK Sense 5, Android 4.1 ROM! (NOTE: 4.2 Software may be OK however for your best chances use the oldest you possibly can!!)
2. Have an old un-patched 1.44 HBoot or If on T-Mob or AT&T and on Patched 1.44 HBoot you have downgraded using one of the guides provided at the bottom of this post. (NOTE: To my knowledge patched 1.44 HBoot's are most likely those dated from June 2013 onwards, to check this reboot to bootloader and find the date there.)
3. Use the up to date 0.2.1 revone (the older ones give false successes)
4. Are Rooted (Not necessary but seems to improve chances of success)
5. Have the correct Moonshine package for your exact firmware and software version! If your firmware is not on the site and there is no way of you getting a matching firmware then you can't use it!
6. Are not on stock 4.2 software upgraded via OTA. (NOTE: Custom 4.2 Software may be OK as long as your HBoot is still 1.44)
7. Are not using a GE ROM, 4.3 Rom or on stock 4.3 software
8. Are not on HBoot 1.54 or higher
9. Are NOT on HBoot 1.54 or higher
10. ARE NOT ON HBOOT 1.54 OR HIGHER
11. Are not an Idiot! (Most important of all)
Before you try RUMRUNNER you must.....
1. Ensure you are on 100% Stock firmware/software that is supported. (note:you may be rooted or have custom recovery they should not effect success)
2. Ensure that if your device is carrier branded you are running stock firmware/software for your carrier (i.e H3G = 2.24.771.3)
3. Have your bootloader unlocked!
4. Use the correct RumRunner package for your device firmware. If you are not then flash Stock software matching your correct carrier firmware before starting.
5. Have HTC Sync removed from your computer!
6. Have firewalls, antivirus and anything else turned off or un-installed! (Ensure to turn back on after completion )
7. Have read the RumRunner thread and Site HERE and know you can email them with your firmware version so maybe they can S-OFF your phone! But DO NOT pester them on their IRC channel, that is for support only!!
8. Have more then 40% battery life.....
9. Not be an idiot! (Always the most important point!)
Notes:
1. If it still isn't working try a different stock rom and re-flash your correct stock firmware and try RumRunner again
2. If RumRunner gets to pouring (5)... Or higher it's more then likely failed already.
3. Some branded firmware's might work with the international package i.e 2.24.111.3 works with the 2.24.401.1 rumrunner package.
Again as I stated earlier some of these may not apply but if you want to guarantee revone or moonshine to work then you should follow these rules! Also in addition to this. READ THE OP of the threads in question (and POST 2 of revone!) They are your bible and will tell you what to do.
If you aren't sure what S-OFF is, does, why you might need it or how to achieve it safely then you DO NOT NEED S-OFF. You could ruin your phone and you really should start with more basic things first!!
WARNING Going back to S-ON isn't necessary for warranty, just lock the bootloader and go back to a stock rom/recovery if you do decide to be crazy and go S-ON again you may receive back a non-s-offable device that isn't supported by any of the above methods... YOU HAVE BEEN WARNED
Error codes and what they mean (from my experience, and what I've read!) ;-
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Error Code -6 = More then likely you're on either a patched or a 1.54 HBoot and you're not going to be able to S-Off. If you reboot to bootloader and you're on 1.44 then you might be able to downgrade using one of the guides on xda. Xboarder's guide on rootzwiki for TMob is a good one. In addition you may be on the right 1.44 HBoot but the software/ROM you're running could be the issue. In any case run a stock RUU for your CID and you should be sorted.
Error Code 1 = I've had this myself and this basically means it's not ever going to work. I think it's a variant on the -6 Error. If you see this, you're out of luck IMO.
Link for T-Mobile Device HBoot Downgrade to enable S-OFF HERE
Link for AT&T Device HBoot Downgrade to enable S-OFF HERE
Additional Info (On Downgrading HBoot from 1.54 with S-ON)
If after reading this guide you're thinking OK so I need to downgrade my HBoot, then to clear things up here is a list of methods that categorically do not and will not work to downgrade your 1.54 HBoot to 1.44 HBoot if your device is S-ON regardless of how much you think it should work because it did on your old phone.
Note these methods WILL NOT WORK to downgrade HBoot from 1.54 to 1.44 while S-ON!
1. Running an old RUU for your device with a lower HBoot inside
2. Writing directly to any of the board or hboot partitions mmcblk0p4, mmcblk0p5, mmcblk0p12. This includes:-
a) dd'ing your hboot/board image, editing the version then dd'ing it back
b) dd'ing any other hboot/board image to your hboot partition mmcblk0p12
c) dd'ing anything to anything!! HBoot and board are WP from low boot and cannot be written to or modified at all unless S-OFF
d) chmodding mmcblk0p12, deleting it, editing it, or anything else you might thing could work
e) using recovery to flash to mmcblk0p12 using busybox and dd command.
f) anything else I missed (I hope you're getting the picture here anyway) Oh and note, if you try to dd and it says it worked.... It didn't!
3. Modifying and flashing an encrypted or decrypted rom.zip, firmware.zip, PN07IMG.zip or RUU.zip from recovery, fastboot or RUU mode
4. Flashing an old encrypted or decrypted rom.zip, firmware.zip, PN07IMG.zip or RUU.zip from recovery, fastboot or RUU mode
5. Using a Y-Cable with or without a goldcard to flash an old PN07IMG.zip
6. Using a Y-Cable with or without a goldcard to flash a modified PN07IMG.zip
7. Running a modified RUU with old or editied HBoot version
8. *Not totally proven yet* Trying to brick the phone by shutting it off during RUU.zip install at the HBoot writing stage. (This has only been tried once so far and didn't pay off, I would not advise trying this unless you are a "VERY" confident/crazy android user/dev)
I hope this helps clear things up, have a nice day and happy flashing ​
The War Horse said:
OK so following my post of pretty much exactly this on the revone thread it seems that a lot of people still aren't sure what's going on so here is my simple guide to follow BEFORE you try to S-OFF your phone or post in the Revone or Moonshine threads.
You should/can only use revone or Moonshine(potentially different as I am not as familiar but I'm pretty sure the same rule apply) to S-Off if;-
1. You are on or flash a STOCK Sense 5, Android 4.1 ROM before you try!
2. Have an old un-patched 1.44 HBoot or If on T-Mob or AT&T and on Patched 1.44 HBoot you have downgraded using one of the easy to find guides provided.
3. Use the up to date 0.2.1 revone (the older ones give false successes) <revone only>
4. Are Rooted (Not necessary but seems to improve chances of success) <revone only>
5. Have the correct Moonshine package for your exact firmware and software version! If your firmware is not on the site guess what..... You can't use it! <moonshine only>
6. Are not using a 4.2 ROM
7. Are not using a GE ROM
8. Are not on HBoot 1.54
9. Are not on HBoot 1.54
10. ARE NOT ON HBOOT 1.54
11. Are not an Idiot! (Most important of all)
Some of these may not apply but if you want to garuntee revone or moonshine to work then you should follow these rules! Also in addition to this. READ THE OP of the threads in question (and POST 2 of revone!) They are your bible and will tell you what to do.
Notes on Error codes (from my experience, and what I've read!) <revone only>;-
Error Code -1 = Potentially you need to try a different ROM or it could just be random and after a few tries and reboots it might work. A few people have reported that rebooting and using -p rather than -P has worked but I'm not convinced as -p isn't built as a command but you're free to try whatever you wish.
Error Code -2 = I've seen people report this but revone has actually worked so should you see this try and reboot and carry on, if not then try changing ROMs and try again.
Error Code -6 = More then likely you're on either a patched or a 1.54 HBoot and you're not going to be able to S-Off. If you reboot to bootloader and you're on 1.44 then you might be able to downgrade using one of the guides on xda. Xboarder's guide on rootzwiki for TMob is a good one.
Error Code 1 = I've had this myself and this basically means it's not ever going to work. I think it's a variant on the -6 Error. If you see this, you're out of luck IMO.
I hope this clears things up. Please feel free to post your error code findings should they be any different from what I have stated. Also anyone familiar with moonshine please feel free to add anything I might have missed. Cheers.
Sent by homing dragon......
Click to expand...
Click to collapse
Can I get s-off with HBOOT 1.54???????? (joking BTW lol)
cheers for this should stop certain muppets asking silly things
Aditional Information - SuperCID
On a separate note If you are on an updated HBoot but SuperCID (11111111) Then the above rules may not apply. If this is the case for you and you are SuperCID, S-ON on HBoot 1.54 or Higher then you may have to try a few different routes as SuperCID bypasses some things on occasions. You may well be able to downgrade your HBoot and S-OFF.
exocetdj said:
Can I get s-off with HBOOT 1.54???????? (joking BTW lol)
cheers for this should stop certain muppets asking silly things
Click to expand...
Click to collapse
Lets hope so. Mods moved it from the Origional Dev forum though and I have a feeling a lot of Muppets will totally bypass this forum and go there and still crack on blindly...... Maybe if this was a sticky then it would be missed less.... I dunno..... MODS?
The War Horse said:
Lets hope so. Mods moved it from the Origional Dev forum though and I have a feeling a lot of Muppets will totally bypass this forum and go there and still crack on blindly...... Maybe if this was a sticky then it would be missed less.... I dunno..... MODS?
Click to expand...
Click to collapse
Think maybe you should put the title of the thread entirely in capitals and surround it with *********s or ###s so not even the dumbest noob will miss it lol!
exocetdj said:
Think maybe you should put the title of the thread entirely in capitals and surround it with *********s or ###s so not even the dumbest noob will miss it lol!
Click to expand...
Click to collapse
HAHA, I did actually try this but it converted the lot to lowercase randomly.... I assume you're not allowed all capitals? lol
The War Horse said:
HAHA, I did actually try this but it converted the lot to lowercase randomly.... I assume you're not allowed all capitals? lol
Click to expand...
Click to collapse
damn i assume so!!!! anyway soz for clogging up ur thraed mate! Try the symbols ~~~ *** (it will look like you are swearing at em hahaha!)
exocetdj said:
damn i assume so!!!! anyway soz for clogging up ur thraed mate! Try the symbols ~~~ *** (it will look like you are swearing at em hahaha!)
Click to expand...
Click to collapse
No worries man. Just spread the word. I've asked a mod if it can be stickied so we'll see.
posted a friendly link to this thread in the soff ones lol!
just have a look:laugh:
The War Horse said:
No worries man. Just spread the word. I've asked a mod if it can be stickied so we'll see.
Click to expand...
Click to collapse
the noobs dont even notice the stickies, they will still answer questions
IINexusII said:
the noobs dont even notice the stickies, they will still answer questions
Click to expand...
Click to collapse
I know. I'm thinking that at least from now on noone has to answer the questions though. they can simply send them to this thread lol.
I'd be better if this was in the Orig Android Dev forum imo, that way when they jump in there head first they might see it!
The War Horse said:
I know. I'm thinking that at least from now on noone has to answer the questions though. they can simply send them to this thread lol.
I'd be better if this was in the Orig Android Dev forum imo, that way when they jump in there head first they might see it!
Click to expand...
Click to collapse
the ONLY way is for XDA to automatically redirect the noobs to this thread whenever they click on a S-OFF thread. otherwise they wont see it
IINexusII said:
the ONLY way is for XDA to automatically redirect the noobs to this thread whenever they click on a S-OFF thread. otherwise they wont see it
Click to expand...
Click to collapse
Now that would be something!!
1.54 s off
just go my phone s-off on 1.54 h boot,check fone fun shop.was only achieved today.
doohdah said:
just go my phone s-off on 1.54 h boot,check fone fun shop.was only achieved today.
Click to expand...
Click to collapse
S-Off via jtag or by an external paid source is completely different to revone or moonshine. For one they're a lot cheaper!
Also the company you mention has been offering S-Off on the one for while now.
Sent from my HTC One using Tapatalk 4
good!:good:
1.54.s off
The War Horse said:
S-Off via jtag or by an external paid source is completely different to revone or moonshine. Fit's the onlone they're a lot cheaper!
Also the company you mention has been offering S-Off on the one for while now.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.
doohdah said:
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.
Click to expand...
Click to collapse
But by java card it is always possible, that's how htc does it, even on for the one x some shops offer it....
doohdah said:
For your information the 1.54.s-off was only achieved yesterday and is.by java card,it my be more expensive than revone but its the only solution at this time.
Click to expand...
Click to collapse
It was achieved by java card the day the phone was made. Lol.... Java card isn't an exploit.
Sent from my HTC One using Tapatalk 4

Categories

Resources