Related
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
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
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
first, yes i know how to search!
i've found out that when you want to unroot your phone you have to do it using ruu's.
how do i know wich Ruu i should use?
when i install the Ruu, is it just like installing a new rom using clockwork?
and when i've installed the Ruu how do i uninstall clockwork and all the other things that comes with the root?
i am currently using the standard 2.1 update 1 rom for wildfire (original rom)
if you plan not to do rooting and flashing anymore, just update to 2.2. Everything will get original, but you will lose the opportunity to root it again. Otherwise, flash a kinda of unroot image, which comes with unrevoked, i didn't hear about it anyway. Try yourself.
To install the RUU, Download it (It will be an EXE File), install HTC Sync on your PC, Connect your device, and, run it. You will lose Clockworkmod and all root associated apps and priveleges when you unroot it.
First check that you can root your phone.
If you already have Froyo installed on your phone then you will have the new Hboot.
If can root use the old unbranded Eclair Ruu from shipped rom's.
It's in the guide (turkeys guide i think) stickyd at the top of the page.
I also want to go back to using stock ROMs. Froyo actually. The only reason I rooted was to gain app2sd facility which was not there in Eclair.
Now that Froyo is out for wildfire spare me the unstable ROMs. I will go for the Stock one.
I have the RUU for my mobile. But When I run it from PC, I get cannot upgrade your phone. I understand this is because I am having a custom recovery (Mine is ClockworkRecovery).
Now can anyone tell how I can get the stock Froyo ?
Do I need to get the stock recovery back ? Is there a bypass for this ?
Or is there a .zip file intead of RUU.exe files for Stock Froyo ?
i want to root my wildfire but before doing it i want to be shure i could unroot it just in case i will ned warranty support.
so im trying to install the ruu, ive an italian small carrier wildfire, ive tried the h3g (that is not the phone carrier) and ive tried the generic wwe htc ruu (not thhe one for asia), different versione 14, 25, 37 but its not working anytime.
this is what happen when i run the ruu: the ruu after running says is waiting for bootloader, after waiting one minute it says error 171 usb connection so at this time the phone is in boot mode with the black background and the big htc write. i restart the ruu and this time goes on, but after saying its copying the firmware gives again error 131 client id and stop. after this the phone restart.
what can i do? do this means that theres no ruu for my phone to restore so i cant root or if i will i just wont be anyway able to unroot and will lose any warranty support?
Error 131 is generally issued when you have a specific operator Wildfire. You will need to create a goldcard to install the generic RUU then. Is your wildfire operator locked?
the only carrier customization is that theres only the carrier logo when the phone start up for the first seconds on the screen but the phone has no carrier lock or any other lock and no other customization, its totally a free lock phone.
just the phone is bought from a carrier that is like H3G and the froyo update too its not yet been released cause the carrier should do it.
its hard to do the goldcard? and if i restore the phone with a ruu that is not from the same carrier i will lose warranty support? only italian ruu ive found is from H3G, i know this is a totally not customized rom from H3G. Should i lose the warranty as this is anyway a factory ruu that will install the factory rom and is italian too?
Creating Goldcads is easy. There is a guide here on XDA, Just search for it.
As for whether you will lose warranty or not if you flash a WWE RUU, there is no way I can answer that, because, different companies follow different rules across the globe. Ex: Here in India, I am pretty sure they wont be bothered which RUU you have, as long as it is an RUU. (Coming to think of it, they are so unbothered they may even accept WF's with Custom ROMs )
calling htc tech support in italya they told me i cant change the ruu, if i put a different one i will lose warranty
theres a way to save the rom in my phone to revert to it? or theres a way to save the OTA to 2.2 that i will receive (i think this month) from my carrier to use it to revert to the official rom? or any other way to find my ruu from my carrier to download it from htc or web?
There is a way to backup the original ROM, but, that requires root itself. (Nandroid, available in ClockWorkMod). Since there is no RUU available for your carrier, and, since warranty support seems important to you, I would recommend you keep your phone as it is.
Also, one more thing, when you update to 2.2 OTA, you will lose the ability to root.
yes i know but i think soon there will be a wildfire 2.2 new unrevoked version so if i can save or download the ota to use it like a ruu i could update to 2.2 than root and use the old ota to restore the phone
the first reason i wanted to root the phone was to increase the cpu, theres no way to do it with the unrooted phone right?
actually i think i got to wait
raniero1 said:
yes i know but i think soon there will be a wildfire 2.2 new unrevoked version so if i can save or download the ota to use it like a ruu i could update to 2.2 than root and use the old ota to restore the phone
Click to expand...
Click to collapse
I would actually wait till the tool releases, before updating to the new OTA, because, there is a lot of uncertainty when the new Unrevoked will release. As for downloading the OTA, I dont think there is a way again (atleast as far as I know) , if it is not listed at Shipped ROM's. If you download it, it installs itself.
raniero1 said:
the first reason i wanted to root the phone was to increase the cpu, theres no way to do it with the unrooted phone right?
actually i think i got to wait
Click to expand...
Click to collapse
Correct. It most certainly requires root.