Root Verizon's RUU for the Official 2.1 for Droid Eris

[bsutton1]

I was on Leak 3. I tried the RUU Rom and everything is working fine so far. I made one phone call afterwards and everything was fine. Hopefully, I won't be getting the silent bug.

 

[josh44]

i keep on hearing about this silent bug, what is it??

 

[hallstevenson]

Dial phone #, hit SEND ... silence.

 

[ttran97]

The silent bug is also when you receive an incoming call, there's no ring and when you answer, you can't hear the other person and the other person can't hear you. The only way to resolve it is to reboot the phone. The bug comes and goes seemingly randomly. I always thought it might be some sort of buffer or memory problem, but who knows...

 

[AwesomeIT]

Just to clear up some things for those who don't want to, or have reading comprehension problems in this thread.

This "official" release from Verizon for those on Leak v3 is pointless. If you were running the leak v3 before this RUU, then you already have the official ROM from Verizon. This will not make your phone different. People who received the 2.1 ROM via OTA updating do not have a different version of the ROM than somebody running the leak v3. You will receive updates from VZW whether you are on 1.5 or 2.1 regardless of how or when you installed 2.1, or what version of 2.1 you are running. The bootloader has nothing to do with the functioning OS on your phone. All the bootloader does is load the kernel and pass off control of the hardware to the kernel.

Again, if your running the leak v3, you do not need this update. All it will accomplish is a waste of your time reinstalling all your applications.

 

[jreed2560]

From what I found. The OTA file is much much lighter (by 20mb or so) from the leaks. that alone would be enough of a reason for some to flash it. With 20 or so apps on the OTA I still had over 100 mb of free space on the phone. With the leak I was always around 70 or 80. I'm not sure what the file size of this RUU update is, but if this is the case I would do it.

 

[jreed2560]

I was on Leak 3. I tried the RUU Rom and everything is working fine so far. I made one phone call afterwards and everything was fine. Hopefully, I won't be getting the silent bug.

you can flash all the software or firmware you want, unfortunately the silent bug is a hardware issue and will not be fixed with an update.

 

[hallstevenson]

From what I found. The OTA file is much much lighter (by 20mb or so) from the leaks. that alone would be enough of a reason for some to flash it. I'm not sure what the file size of this RUU update is, but if this is the case I would do it.

Your theory is unsubstantiated. It's just packaged differently... The OTA likely also leaves out some files. According to this post at XDA, http://forum.xda-developers.com/showpost.php?p=5793684&postcount=1, the OTA actually patches files vs replaces them. That alone can allow for smaller files.

And for what it's worth, the RUU is 124mb. Even bigger than the "leak". Why ? It includes "installer" type files.

 

[thenestor]

I've emailed PCD twice now (three weeks ago and again this week) to ask why they haven't posted the RUU on their site as they did with MR1 and MR2, but I haven't gotten a response yet.

 

[hallstevenson]

I'm confused who PCD actually is as they don't appear to be part of HTC nor VZW. Since they're not (or don't appear to be), they will only post what a vendor supplies them. They will NOT list things like this on their own.

 

[adam29617]

I have downloaded the ruu and tried to let it work but nothing???? I'm on the v2 leak and all the ruu does is say sending it was running over an hour before I brought up task manager to stop the applacation from running when I stoped it it told me the app was not responding?? PLEASE HELP I CAN'T ACCESS ALL APP IN THE MARKET!!

 

[doogald]

In that case, I'd suggest just downloading the v3 leak and flashing that instead. You will end up with the same 2.1 version as the RUU gives.

 

[adam29617]

I can't do that eather when I did it told me can't find file when I know its on my sd card!!! it says unable to load from sdcard???

 

[hallstevenson]

If it can't find it, it's NOT THERE or it's not named properly.

 

[adam29617]

PROUD TO SAY FINALY GOT IT TO WORK AND HAPPY NOW GOT ALL MY LOST APPS BACK!!! O'YEA AND ALSO EVERYONE i HAVE NO PROBLEMS YOU ALL SPEAK OF NO BUGS WHAT SO EVER!! AND IN ALL MY ERIS IS WAY FASTER AND MORE RESPONSIVE THEN BEFORE (LEAK V2 THAT IS)

 

[ckali7]

Hasn't anyone noticed that the name of this download is RUU_Desire..... Seems to me like this is for the HTC Desire, not the Eris.

RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe

 

[xx_bishop_xx]

Hasn't anyone noticed that the name of this download is RUU_Desire..... Seems to me like this is for the HTC Desire, not the Eris.

RUU_Desire_C_Verizon_WWE_2.36.605.1_release_signed _with_driver.exe

I think I remember someone commenting on that when the OTA was first released.

 

[erisuser1]

The Desire "C" or "desirec" is HTC's name for the Eris.

PCD is a phone distributor.

The OTA is smaller because it patches 500+ files rather than replace every file. This is done to conserve VZW's network traffic and also allow the phone software to be upgraded, rather than erased & replaced.

BTW, for the first two OTAs, (Dec 10th and Jan 10th, approx.), the MR1 and MR2 RUUs appeared on PCD's web site simultaneously with the OTA rollout from VZW. As of today - more than a month after the 2.1 OTA, it still has not appeared on PCD's site. I find it rather strange that people call something which shows up on a "leaker" site "Official"

Sigh.

 

[doogald]

The Desire "C" or "desirec" is HTC's name for the Eris.

+1. And, interestingly enough, HTC's internal name for the phone that became the Desire was the Bravo.

 

[thenestor]

I contacted PCD about it, and they said that verizon isn't allowing them to post this RUU on the site. It's only available to verizon tech support.

 

[majorpay]

you can flash all the software or firmware you want, unfortunately the silent bug is a hardware issue and will not be fixed with an update.

^^^I'm not sure I'm buying this answer anymore...

#1. This problem was non-existent in 1.5
#2. I REPLACED my phone and rooted it and am having similar issues.
#3. My phone does not meet the requirements for the bug (date range).

It doesn't make logical sense anymore for this to be a hardware issue. There has to be a pattern or a leak here that hasn't found because the focus has been on the hardware. A possible software compatibility issue? More likely than a hardware issue that didn't surface until 2.1.

 

[jreed2560]

Its widely accepted that the problem was dormant in 1.5 and the and 2.1( in any variation be it OTA, leak or root) woke it up.

 

[thenestor]

I just want to reiterate that people who are still on "leak v1" or "leak v2" might as well use this to upgrade to v3/OTA. You still can't root, but at least you'll have protected apps back in the Market, pictures in Gmail, and a bunch of other bug fixes. This is the same as installing "leak v3", but a whole lot easier. And when you're done, your phone will be completely identical to Verizon's own 2.1-loaded refurbs.

 

[scary alien]

I just want to reiterate that people who are still on "leak v1" or "leak v2" might as well use this to upgrade to v3/OTA. You still can't root, but at least you'll have protected apps back in the Market, pictures in Gmail, and a bunch of other bug fixes. This is the same as installing "leak v3", but a whole lot easier. And when you're done, your phone will be completely identical to Verizon's own 2.1-loaded refurbs.

Are you sure its identical? jk

guys, thenestor knows what he's talking about...check out this thread for his analysis:

http://androidforums.com/htc-droid-eris/78692-checksum-proof-2-1-leak-v3-99-identical-ota-2-1-a.html

and another thread over at xda that backs him up:

[FYI] Minor Differences: OTA-2.1 vs. Leak-V3 - xda-developers

 

[OUScooby]

I have a rooted eris running 2.1. I AM NOT RUNNING LEAK. I need to put my phone back to 100% stock so I can take it to verizon for a replacement do to a headset issue.

Will this method put be back to stock with the current OFFICIAL OTA 2.1 update, and will it hide all traces that I rooted my phone?