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
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
JW 301 said:
Hi, i have a problem, I need some help solving it.
I have branded Hero (G2 Touch) on T-Mobile. Being tired of waiting for T-Mobile to release their branded 2.1, I followed some instruction on this board and installed generic 2.1. Sadly, the instruction used the RUU for directly installing 2.1 and I did this^^
When I try to install an old 1.5 RUU (t-mobile or generic) I always get the error 140 bootloader version.
I then tried the rooting method, now I managed to install the Amon Ra's Hero Recovery and that works quite good, as I now can use nandroid again (I couldn't do since the 2.73 update).
I managed to restore some backups that were on 1.76, and I had android 1.5 installed again, but still I couldn't install the 2.73 RUU, still getting the bootloader error.
Now, either somebody can tell me how to install the RUU, so I can get back to original t-mobile ROMs and can use OTA to get from 2.73 to android 2.1,
or, somebody could send me a nandroid backup with 2.73 installed.
there might be another possibility: I extracted the rom.zip from the T-mobile 2.73 RUU and tried installing it via recovery... I got an error while opening the file (bad).
has anybody an idea how to solve my problem? pls don't tell me 'install custom roms' i heard that often enough and simply don't want to (though I might give it a try as soon as working sense 2.2 ROMs are ready)... i want to get back to official T-Mobile ROMs
thanks
Click to expand...
Click to collapse
You'll need to use this guide (http://villainrom.co.uk/viewtopic.php?f=46&t=375) to make a goldcard, and downgrade using the HEROIMG.zip method (google it)
it doesn't work... I took the rom.zip, renamed it HEROIMG.zip and put it on my sdcard.
hboot finds it, loads it and then says "Main Version is older! Update Fail! Do you want to reboot device?"
what can I do now?
Have you checked to see if your goldcard has definitely worked?
it definitively is a goldcard, as I used it to install generic ROM on T-Mob device... still doesn't work now... but the problem is not that I try to install a ROM that's not meant for my device (thats what I understood goldcard does), but the problem seems to bee the bootloader-version the 2.1 RUU brought.
what can I do now?
Same thing happened t me a while back, I just re-tried every step from scratch and it worked the third time...!
what exactly did you do then? I tried so many things, at least I want to know, which steps to repeat over and over again
Just going to have a look at it for you, I am going through the processes as we speak so if I find a solution I will post back.
@JW 301 post the info in settings > About Phone
- Model number
- Firmware version
- Baseband version
- Kernel version
- Build numbr
- Software version
- Model number: HTC Hero
- Firmware version: 2.1-update1
- Baseband version 63.18.55.06PU_6.35.15.11
- Kernel version: 2.6.29-063c4d24 [email protected] #1
- Build number: 3.32.405.1 CL191507 release-keys
- Software version: 3.32.405.1
I want to get back to 2.73.111.26 (that is a T-Mobile ROM) so I can apply official T-Mobile OTA updates (by the way, I managed to get to VillainROM 12.0 yesterday, but went back. I want to use official ROMs...)
See new post here;
http://forum.xda-developers.com/showthread.php?p=7600524#post7600524
Had the same problem, I mean, EXACTLY the same.
This is what sorted it for me:
http://forum.xda-developers.com/showthread.php?t=726118
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
Hi
I have the following problem:
I've tested FroyoRedux Mod v1.9.5 with the requested radio and hboot. After that I've tried to install the original stock ROGERS 2.1 ROM. Now, the problems appeared. somehow I'm stack with the
1.76.0010 hboot, with security ON
Radio 3.22.20.17 (which should be 6.35.xx.xx) after flashing (don't ask why the update didn't take place because there was no error)
and the phone hangs at the ROGERS screen (just before start loading android).
I've tried reflash SAPPIMG from flashboot but it detects is already there and won't flash. I can not use fastboot from computer because security is ON, i don't have recovery installed because ROGERS rom took it away.
Any ideas on how I can fix this mess?
UPDATE: After reading tons of forum pots, seems I have found the source of the problem and seems that became a common issue: I've installed Rogers 2.1 manually over CM custom ROM with froyo (SPL 1.33.xxxx and RADIO 3.22.xx.xx) without knowing that Rogers will not update both RADIO and SPL.
Now all of us who did this need a solution. Anyone has an ideea?
Thanks
how did u install the rogers 2.1?
from the RUU?
u have a rogers magic+ phone?
blizard80 said:
how did u install the rogers 2.1?
from the RUU?
u have a rogers magic+ phone?
Click to expand...
Click to collapse
Hi, Yes, I've instaled Rogers 2.1 but not from RUU but from fastboot with SAPPIMG.zip
and u installed hboot from the ruu?
i think u must make a gold card... but wait for the experts
When I've installed the SAPPIMG using a goldcard, it automatically overwiten hboot, recovery and radio.
BTW: if I've formatted the goldcard, how can I create a new one now that i don't have a linux pc and i can only enter fastboot.
Thanks
Why did you post this in Development?
I'll move it to General... but I fail to see how this is development related.
Binary100100 said:
Why did you post this in Development?
I'll move it to General... but I fail to see how this is development related.
Click to expand...
Click to collapse
sorry, i was reading in development and post the thread here from mistake
any solution please?
Now I can access teh memoy card again. Please give me a solution using RUU. Maybe a valid RUU which works on all devices because when I've tried to flash a RUU it sais whong RUU version and I must get another one.
No one can help?
http://rapidshare.com/files/421772202/SAPPIMG.nbh
Try flashing the above.... using a goldcard and from fastboot/hboot.
Thank you for answering
I will try now
I've tried it but it say "Main Version is older". Can you tell me how can I fix that or how to make a SAPPIMG.nbh file with Rogers update or even android 2.2. Or do you have such thing?
Thanks a lot.
Anyone with a solution please !?!?
Got your PM... normally i don't respond help request over pm, but i'll make an exception.
You need to redo your goldcard... all the errors you get points to a faulty goldcard.
You can post/pm the cid nr you get from the htc device + the reverse nr. you used to make the goldcard... then i can verify that you have done it correctly.
You should have made it work with the sappimg.img i have provided earlier....
All points to a bad made goldcard!
Thanks so much for your reply.
So, Let's get started . My SD CID is
035344535530324780109ac8ee0093aa
After using http://hexrev.soaa.me/
My reversed CID is
009300eec89a10804732305553445303
(first two zeros already present)
Now, I've used this code here http://psas.revskills.de/?q=goldcard
and get the goldcard in the attachment.
Can you check please?
Thanks a lot
Well all ok from here.
The only thing left is how you made the hex-changes to the goldcard...
Which guide did you follow?
Read your pm!
i have exactely the same problem so when you get the solution can post it please !!!
Sure I will
Try this...
http://rapidshare.com/files/424005789/sappimg.zip
Put it on the goldcard and reboot by holding volume_down + power.
Then let it work...
Make sure there is nothing else on the goldcard!
Do not rename or anything.
This sappimg.zip is the new rogers 2.1 update... it should work :0)
Please report back :0)
From the Android Community blog:
Vodafone UK has begun the release of its Android 2.2.1 update for the HTC Magic. According to the company’s forum, the Magic Froyo update will be a two-stage OTA affair: one update to prep the phone, and the second to actually install Android 2.2.1.
The update’s release will be staggered, so you’ll have to wait for your Magic to flag up that new software is available; there doesn’t appear to be a way to manually trigger the install. Still, we’re glad to see that the ageing Magic hasn’t been left out in the cold.
“Android 2.2.1 will give customers a number of improvements including: latest Gmail and Android Market clients; ability to save applications directly onto an SD card; support for USB tethering so the phone can be used as a modem; improved support for Active Sync Exchange (email, contacts and calendar sync); enhancements to Bluetooth; and enhancements to the camera. The update also includes the latest Google security patches.”
Click to expand...
Click to collapse
The update is coming for France too.
SFR begins the FOTA update today, in ends on thrusday.
vodafone magic is 32A ???
did any one get hands on ruu ??
ahmgsk said:
vodafone magic is 32A ???
did any one get hands on ruu ??
Click to expand...
Click to collapse
No, is a Sapphire 3B. Exactly the same hardware than My Touch 3G in America.
Hopefully someone can check their log cat for the URL, or extract the update.zips from /cache before upgrading.
This if this is an OTA it will not have an ruu.. but it is interesting to see if we get yet another radio or if there is any changes from the tmobile image.
ezterry said:
Hopefully someone can check their log cat for the URL, or extract the update.zips from /cache before upgrading.
This if this is an OTA it will not have an ruu.. but it is interesting to see if we get yet another radio or if there is any changes from the tmobile image.
Click to expand...
Click to collapse
Hi,
is it possible to restore an original 1.6 backup over HBOOT 1.33.0013d and
RADIO 2.22.27.08 to catch the ota?
Thanks
giucip
giucip said:
Hi,
is it possible to restore an original 1.6 backup over HBOOT 1.33.0013d and
RADIO 2.22.27.08 to catch the ota?
Thanks
giucip
Click to expand...
Click to collapse
You will need the old radio + old rom (you can keep 1.33.0013d it will prob. block the actual install but with some hackery in /cache using exploid or androot you could make it work. To get the files.
The problem from my point of view is its not exactly trivial and I don't have the same hardware.
Chances are the 1st part is 1.33.0013 like the t-mobile update, and the second part the 2.2.1 update. But maybe they have another spl for us.
ezterry said:
You will need the old radio + old rom (you can keep 1.33.0013d it will prob. block the actual install but with some hackery in /cache using exploid or androot you could make it work. To get the files.
The problem from my point of view is its not exactly trivial and I don't have the same hardware.
Chances are the 1st part is 1.33.0013 like the t-mobile update, and the second part the 2.2.1 update. But maybe they have another spl for us.
Click to expand...
Click to collapse
I can do it following your post, isn't it?
Sapphire (MT3G)
1) Download SAPPIMG.nbh
2) enter fastboot and run 'fastboot flash nbh SAPPIMG.nbh'
3) Continue as per one click (flashreq) root instructions:......
giucip said:
I can do it following your post, isn't it?
Sapphire (MT3G)
1) Download SAPPIMG.nbh
2) enter fastboot and run 'fastboot flash nbh SAPPIMG.nbh'
3) Continue as per one click (flashreq) root instructions:......
Click to expand...
Click to collapse
For steps 1&2:
If you have 1.33.0013d yes just make sure its the Vodafone nbh otherwise the update won't be fetched.
This will install the original spl + radio + rom + recovery
As for step3.. you want root to poke things but best to leave recovery alone.. androot or exploid are your better bets.
Mind you once you upgrade I can't promise you can re-root (likely the method used on the t-mobile phone will work but androot/exploid are patched iun 2.2.1)
ezterry said:
Hopefully someone can check their log cat for the URL, or extract the update.zips from /cache before upgrading.
This if this is an OTA it will not have an ruu.. but it is interesting to see if we get yet another radio or if there is any changes from the tmobile image.
Click to expand...
Click to collapse
Update Nr. 1:
http://dl.dropbox.com/u/3308532/sapphire_32b_ota/126221163a9c.hboot-1.33.0013.vfpioneer.12622116.zip
Update Nr. 2:
http://dl.dropbox.com/u/3308532/sap...gned-vfpioneer-FRG83D-from-DRC92.735b0bf4.zip
th2811 said:
Update Nr. 1:
Update Nr. 2:
Click to expand...
Click to collapse
lol that first one is almost exactly the same as the 1.33.0013d SPL that rolled out to the mytouch
Edit: ok and update 2 includes RADIO-2.22.28.25
HammerT said:
lol that first one is almost exactly the same as the 1.33.0013d SPL that rolled out to the mytouch, so probably the same memory update?
Click to expand...
Click to collapse
Yes.
In this video
http://www.youtube.com/watch?v=sQdbaqOOXGs
you see that it is the same Baseband-Version
HammerT said:
lol that first one is almost exactly the same as the 1.33.0013d SPL that rolled out to the mytouch
Edit: ok and update 2 includes RADIO-2.22.28.25
Click to expand...
Click to collapse
Yes same as t-mobile:
HBOOT: 1.33.0013
Radio: 2.22.28.25
Rooted devices probably best stick with 1.33.0013d.
Same languages as ASOP builds:
de, en, es, fr, it, nl
Keyboard dictionaries included (will need to add that to my language packs)
If someone has this installs re-roots and is willing to give me the system image from a nandroid poke me a PM
it will make it easier to "extract" bsdiffs without the previous rom's files
ezterry said:
Yes same as t-mobile:
HBOOT: 1.33.0013
Radio: 2.22.28.25
Rooted devices probably best stick with 1.33.0013d.
Same languages as ASOP builds:
de, en, es, fr, it, nl
Keyboard dictionaries included (will need to add that to my language packs)
If someone has this installs re-roots and is willing to give me the system image from a nandroid poke me a PM
it will make it easier to "extract" bsdiffs without the previous rom's files
Click to expand...
Click to collapse
If some1 can also send me whole nandroid pls PM me thx alot in advance
i have some problem with the second part.
i have everything stock (universal androot only - de-rooted).
i'll try manual way, maybe will work, otherwise will post info on the error.
update:
need to have vodafone live installed to run the update... i got rid of it lately
!!!
does anyone have a backup of vodafone live app??? i screwed sth wih titanium and backedup only the application data not the app itself...
please help!!!
em666 said:
i have some problem with the second part.
i have everything stock (universal androot only - de-rooted).
i'll try manual way, maybe will work, otherwise will post info on the error.
update:
need to have vodafone live installed to run the update... i got rid of it lately
!!!
does anyone have a backup of vodafone live app??? i screwed sth wih titanium and backedup only the application data not the app itself...
please help!!!
Click to expand...
Click to collapse
sent you PM
how can we install those files without recovery?
skyleth said:
how can we install those files without recovery?
Click to expand...
Click to collapse
You have to rename it to update.zip and after that install it with bootloader (turn your phone off and turn it on with [Volume Down] + [ON/OFF] ).
When it's finished reboot it and tadaaaa FROYO.
how to root it now??
my universal androot doesnt seem to be working...
and where are live wallpapers???
em666 said:
how to root it now??
my universal androot doesnt seem to be working...
and where are live wallpapers???
Click to expand...
Click to collapse
*Androot won't work its patched in asop:
See: http://forum.xda-developers.com/showthread.php?t=803682
Can't say I've ever used it.. but that is the re-root of the t-mo ota.
*Live wallpaper picker is not in the sapphire asop build .. just push the apk from cm6.1
Once that is installed get some lwp from market