Database Users

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

e:cant open/ cache/recovery/command????!!!

Posted this at the CM camp, three days now no answer so hopefully you guys can help me out...
Ok so I decided to unroot (mytouch 32b original) and Im having a problem getting back to 1.6. I got down to 1.5 no problem by applying SAPPIMG but its been three days and no ota 1.6 so I decided to manually apply the update but all I get is
e:cant open/ cache/recovery/command
--Install from sdcard..
Finding update package..
Opening update package..
E:Cant open /sdcard/update.zip
(no such file or directory)
Installation aborted.
Wtf?
I tried to use re-flash sappimg three times now which works until I try to manually update the 1.6 update always witht the same result. I have searched and searched but havent found any posts with the same problem...

Ok Im seriously about to DROWN my dam phone at this point
I have no clue what the heck is going on, I followed a thread on here to unroot to "Legal" 1.6 from I dont remeber who and now my phone is all screwy! Ive tried three different sdcards as a last resort , hard reset twice, flashed sppimg three times and have as a last resort decided to root again just to say screw it and I CANT EVEN DO THAT NOW! I tried flashrec to flash Ra recovery.......didnt work, flash recovery is grayed out...tried a different sdcard since that one was partitioned, same thing.......tried clockwork, Nope! unsuccesful. I was able to use universal androot with success until I try to flash a recovery image and .....FAIL.
WTF?!

OK... Calm down :0)
Start with basics...
Post here ALL fastboot info.
Then which recovery you are trying to flash.
We can fix this together... you just need some guidance because you have many info mixed up.
I got your back :0)

hahaha, Ya I did finally calm down sorry about that... So i was able to root and finally flash a recovery but I still need to get this 1.6 thing figured out.
Heres my hboot info
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.0006 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
MAY 27 2009, 19:06:41

What rom do you have now?

i just went into my recovery menu to flash the new 2.2.1 ota and had this same error message at the bottom of the screen.
I doubt its anything to worry about but just incase im going to go ahead and
wipe system thru fastboot
reboot into recovery
wipe cache
wipe system again
flash sappimg
reboot
if after that i dont get a cache error, ill wait 24 hours for the 1.6 ota. if it doesnt come, ill go ahead and repeat those steps with the 1.6 update.zip files

It didn't work....

after doing some reading and searching, i think its the SAPPIMG.nbh file that is causing this error. im trying to find one from another source.

I tried two different sappimg files no luck. Hmm, I have the new 2.2 ota posted in the other thread now and ......O!M!G!!!!! I Couldnt be HAPPIER :------D This thing is UNBELEIVABLELY FAST!! I dont think Im gonna worry about the ota ill just keep it rooted for now.
After CM6=(FAIL) (sorry CM camp but I cant live with something as unstable as that but thanks for all the Devs work it was a nice preview ) I thought there was no hope for the mytouch but tmo and google did an insane job. This thing runs as fast as my buddies incredible now

firedude12 said:
I tried two different sappimg files no luck. Hmm, I have the new 2.2 ota posted in the other thread now and ......O!M!G!!!!! I Couldnt be HAPPIER :------D This thing is UNBELEIVABLELY FAST!! I dont think Im gonna worry about the ota ill just keep it rooted for now.
After CM6=(FAIL) (sorry CM camp but I cant live with something as unstable as that but thanks for all the Devs work it was a nice preview ) I thought there was no hope for the mytouch but tmo and google did an insane job. This thing runs as fast as my buddies incredible now
Click to expand...
Click to collapse
I wouldnt mind doing the same but i dont want root anymore.
Too be honest, i dont even want this phone anymore....

Foo_Blyat said:
I wouldnt mind doing the same but i dont want root anymore.
Too be honest, i dont even want this phone anymore....
Click to expand...
Click to collapse
Thats what I said until I flashed the ota......just try it and trust me its AWESOME!!
I ran quadrant with cpu overclock to near 700mhz on cm 5.0.8 (what I consider "stable" of CM) after every config imaginable I could only peak at 212-15, the ota?
360-70

[Q] Bricked Wildfire after attempted Froyo Update, Please help!

First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !

Undeadllama said:
First of all, sorry if this is posted in the wrong place. Im pretty new to all this and don't really know how things work here.
I think im pretty buggered, and im pretty far out of my depth now. Im just posting to see if anything can be done or if it's already too late. Sorry if im missing something obvious that can fix this, however after 3 days of messing with this stuff my brain is starting to blur lol. Ok so here it is:
Tried updating to froyo via the OTA update pushed out recently. That failed and ive tried various ways of getting froyo to install over the last few days using Clockworkmod recovery. I ended up pushing a load of system files onto my phone via adb just to let the updater-script get past assert's. The point is, this was obviously a bad idea as I now have some kind of messed up copy of froyo installed which will not boot up past the HTC splash screen. Problem: the half-cocked update replaced the Clockworkmod recovery with the stock recovery so I now cannot use nandroid to push a backup back onto the phone
To make things worse when I boot into the stock recovery I also can't get into adb/shell, it detects the device but just says offline. Tried a lot of things to get round this but nothing has worked. So as ive got stock recovery and can't seem to get into adb anymore it would appear ive pretty much run out of options unless something can be done with fastboot... I don't know what im doing with that though so any help would be appreciated.
HTC Wildfire T-Mobile UK
S-ON
HBoot - 1.01.0001
Radio - 3.35.20.10
Recovery - Stock
Im at the end of the road here. If anyone has any ideas to try I would be very very grateful, otherwise il have to go see how much T-Mobile wants to repair it
Thanks in advance !
Click to expand...
Click to collapse
You'll need a goldcard and an RUU. Look up how to make a goldcard and let me know when you have one

Wow, thanks for the quick reply
I did try creating a goldcard yesterday (using android.modaco.com/content/software/308798/pc-application-goldcardtool/). So assume I DO have one for the time being...
however if it doesn't work and I need to create a new goldcard:
Since I can't get into adb or boot up android and therefore can't access my sd card through my phone I presume il have to go out and buy a cheap card reader tomorrow.
Also, I have to run this command again:
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
But if I can't get into adb how would I go about doing this, can I get the CID of the sd card from a card reader?
As for the RUU, there's many to choose from on shipped-roms.com, does this sound about right?
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35.15.19_release_130442_signed.exe
Thank you so much for your help.

This this a decent guide from Paul over at MoDaCo.

Ok disregard my last post about a card reader... I managed to borrow a friends android phone since it appears goldcard's are specific to the sd card, not the phone. So after following the instructions I now definitely have a goldcard.
Also have the RUU mentioned in the previous post.
RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed.exe
Is this right, and what do I do with these now to get them on my phone? Ive tried running the RUU whilst in Hboot and in recovery but it wont recognise my phone, presumably because adb isn't working.
Thanks again for the help.

There is another way to do it when it can only get into hboot. I'll look today for the method and let you know.
Sent from my HTC Wildfire using XDA App

Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions

Undeadllama said:
Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system.
Only worked because T-Mobile's OTA was a slightly older version 2.21.110.2, thank god there was a newer version available on the interwebs.
Probably not the best way of doing it but im just glad ive got a working phone again.
Thanks for replying though.
Just on a side note... its bloody ridiculous that its so hard to downgrade android!!! It causes people like me, who don't really know what they're doing, large quantities of banging-head-against-wall sessions
Click to expand...
Click to collapse
Yeah that's the method I was going to suggest, glad you sorted it out.
It's the fact that they lock out fastboot and stuff. If we had S-OFF from the factory, fixing these things would be so much easier

Hi,
how were you able to do this?
"Ah I did manage to get round it in the end. Using the PC49IMG.zip hboot method. Tried pulling the rom.zip from the temporary files that are made when running the 1.14.110.1 RUU. But obviously as I had a newer hboot or bootloader or whatever it was and it wouldn't let me downgrade back to this version. So I went for the newest one, 2.22.405.1 I think it was. With that in the root of the sdcard everything was up and running again after it had finished installing over the top of the messed up system. "
Thanks

Is my Hero bricked? What should I do?

Hello everyone!
First off I'd like to start by telling you I'm new here and I don't know much about rooting so I'm reffering to you for help... Here is what happened... I have a G2 Hero, running android 2.1. So one day I decided to root it and install a custom rom. I downloaded Universal Androot-1.6.2-beta5 and ran it on my mobile.
Afterwards I formatted my sd card then restarted the device and downloaded rom manager from the market and flashed Clockwork. After this I put CyanogenMod-6.1.0-RC1 in the root dir of my sd card, tried to install it from [HOME] + [PWR] buttons menu and an error saying [status 7] showed up... Now im stuck in an endless bootloop... I cannot sync the device with my computer, cannot hard reset.. I can access Hboot menu but there isnt anything I can do...
What should I do to restore it to stock and then try the whole thing again but with a new rom? Thanks in advance!

Anyone?

Have you tried running an official HTC RUU? They can be found in a thread on the development page
Sent from my HTC Hero using XDA App

you have to search for "RUU for htc hero gsm". There's an official website for that. Download RUU (about 80-90mbytes as i remember) and start it. As i remember you should power your phone in HBOOT mode (VOL DOWN + POWER), connct to PC and run RUU and follow the wizard.
It will flash stock 1.5 android.
After reeboot it should inform you that there's an update, but if you want to flash different recovery, you shouldn't update your phone.
Then you should follow "How To - Root Your HTC Hero in One Click" (can't post links yet).

Ok first of all thank you guys for the help! So I downloaded RUU_Hero_HTC_WWE_2.73.405.66_WWE_test_signed_NoDri ver.exe from the main thread. At first I had some connection problems but then I switched the front panel USB to one of the rear which are 2.0 and continued. Now I'm stuck at a later step. Tried to update it but an error message saying "ERROR[131]: CUSTOMER ID ERROR Please get the correct ROM UPDATE UTILITY and try again" displays. Which RUU would you recommend?

I used official RUU from htc.com site. It just worked for me.
This one is in Polish, but i believe, you will find one in your language or in English
http://www.htc.com/pl/supportdownload.aspx?p_id=283&cat=2&dl_id=671
//edit
You must provide a valid serial number from sticker behind the battery and select a corresponding file. It will be only one i think
//edit2
There's something more about this error 131:
http://androidforums.com/707610-post16.html
Apparently you just used wrong RUU... Try one from prev link.

Ok, soI downloaded RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver from the official HTC website and go past last error but afterwards I encounter another one. This time it is "ERROR[140] BOOTLOADER VERSION ERROR, Please get the correct ROM Update Utility and try again"
Any suggestions this time?

hskiller said:
Ok, soI downloaded RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver from the official HTC website and go past last error but afterwards I encounter another one. This time it is "ERROR[140] BOOTLOADER VERSION ERROR, Please get the correct ROM Update Utility and try again"
Any suggestions this time?
Click to expand...
Click to collapse
You could try the carrier one if you got it from Orange flash the ruu which is for Orange uk

Nope, my phone is from Europe but I dont think I got my cd... I'll sure search for it. Any other suggestions?

Maybe you can find a workaround there:
http://forum.xda-developers.com/showthread.php?t=684504

I am currently trying with this one:RUU_Hero_HTC_WWE_2.73.405.38_WWE_release_signed_NoDriver. But it seems to be stuck on "Sending.....Updating the ROM image on your Android phone" The progress bar on the phone's display is almost complete but wont move anymore. I have waited for 20 minutes now...
EDIT: I finally fixed it! I didn't realise I had to have the same RUU version like my software version. Thought I had to downgrade. Nevermind it's all OK now and it's time to try the whole rooting and custom ROM process again
I want to thank all of you guys that helped me!

Good for you man
Just out of pure couriosity, what rom will U use afrer your phone get rooted?

You have to use your carrier related stock rom/exe. What is your carrier?
Perdita2000
Sent from my Hero using XDA App

I havent decided yet. It will definitely be some Android 2.2 ROM Maybe Elelinux Speedmachine.

[Q] stock DZ bricked from OTA update

Hi guys,
before I start, I must say that I have spent 6 hours reading the forum and trying everything I could, whithout succes.
I have a Desire Z from HTC, the OTA update to 2.3 has just been offered to me this morning. My phone is not rooted and I've never tried anything that isn't a click away on the market.
Here is the problem, when I launched the update, I got a "red sign" screen. I search (too) quickly on the web and found a message saying "I got it, just remove the battery and all is well". I did that, and now my phone is stuck at the htc logo.
My sdcard seems dead, my computer doesn't see it. I put a blank one in the phone but no change at all.
I have since searched what to do and tried many things.
- adb doesn't see my device (>adb devices sends a blank)
- fastboot devices says > SH0CERT00230 fastboot but I don't kwow if this is my phone or not.
On the phone, I tried factory reset, recovery, but still no change.
I tried PC10IMG.zip, but it says "main version is newer". I'm currently downloading (slowly) the newest I could find (1.72.405.2) but since I did all the small OTA updates to this day, i'm not sure this will help.
Here is what the Hboot says:
Vision PVT SHIP S-ON
HBOOT-0.85.0010
MICROP-0425
RADIO-26.04.02.17_M2
eMMC-boot
Dec 27 2010,22:19:17
Can my phone still be saved?
Thanks a lot!

You might have the faulty emmc chip problem.
There's some info on it here
If not, you could maybe try using an RUU to downgrade, there's downgrade instructions here as well as a link to an RUU.
Your fastboot is working properly, but seeing as you won't have eng-hboot, you won't be able to use most of the fastboot commands.
-Nipqer

Thanks for the links, I'm on my way to read this.
I forgot to mention that I do have the message "E:Cant mount /cache/recovery/command"
I'll be back as soon as I'm done reading.

I'm back.
I'm not sure the eMMC problem is mine, my phone seems to be more damaged than the one in this thread.
I finally understood that I must put the phone in recovery mode to use adb (newbie inside) but I still can't get it to work, I got "SH0CERT00230 offline" and it won't accept any command.
I can't downgrade either, because it requires adb to run...
I'm going to try PC10IMG with the newer rom and if it doesn't work, I'll send the phone back to htc for a replacement I think (tomorow).

You could try flash the PC10IMG via fastboot, there's some instructions here
Returning it will probably be your best option though.
-Nipqer

I tried to flash via PC10IMG on the sd card, the file is found, but "main version is older" (I said newer before, I was wrong).
I'm calling htc tomorow :-(
Thanks for the help!
At least, now I now how to root and backup my next phone

Pretty sure that error you posted is a tell tell sign of the emmc being busted
Sent from my HTC Vision using XDA Premium App

My answer has been lost in time and space...
I tried installing the newest rom I could find, via PC10IMG on the sdcard. The file is detected but I still get the message telling that the phone version is newer.
I guess I'll have to return it to htc
Thanks for the help anyway!

Hello,
I tried another time with the gingerbread wee Ruu that has been added a few hours ago and it worked!
I will now root my device an be prepared for the next time.
Thanks for the help!