MR4 update for the Eris questions - Droid Eris Q&A, Help & Troubleshooting

As some of you know, MR4 is set to roll out in stages starting today (July 16th) and is said to have many updates. Here is a list: Click
Does anyone know if this maintenance release will fix the "Silent Call" bug?

---

Looks as if that pdf is incorrect. The way that is describing its 2.1. I think Verizon forgot to update that particular pdf.

---

MR4 update is not Froyo. It should however fix the silent call bug on the device. I care not anymore as I have root, but it is still indeed going to be 2.1. I don't think the Eris is capable of having Froyo with HTC sense uploaded into the device. It might be too much for it, and that's ASSUMING that VZW will get the update sent out correctly this time.
Shadow

---

Just root and get KaosFroyo!

---

I already know it isn't 2.2. I was just asking if it would fix the particular bug I was talking about...
I actually called customer service and they told me it was rolling out on July 16th and my device would get it within 7 days. I didn't think I would get it 10 minutes after getting off the phone with her! I am now on MR4. Only time will tell to see if this "Silent Call" bug is fixed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

---

its kind of impossible for anyone to answer your question since youre the first report of someone receiving the update that Ive read ........ so how would anyone know?
of course the only way someone will know is for a person who likes to come to forums and ask alot of questions about will this do this or this do that to actually capture the link when they do the d/l so that the devs can pick it apart
this way instead of just asking questions that are impossible to answer..... the person might actually provide the information to make receiving an answer possible
just my 2 cents early morning rant

---

HTC Legion said:
I already know it isn't 2.2. I was just asking if it would fix the particular bug I was talking about...
I actually called customer service and they told me it was rolling out on July 16th and my device would get it within 7 days. I didn't think I would get it 10 minutes after getting off the phone with her! I am now on MR4. Only time will tell to see if this "Silent Call" bug is fixed.
Click to expand...
Click to collapse
If anyone else gets this, please capture your URL.
bftb0 said:
The OTA .zip files which are downloaded from a Google server are not signed the same way as the RUU "rom.zip" files - they use the app .apk manifest signing method. (manifests and certs a la "jarsigner").
If you are interested in looking at the process that HTC/Verizon uses for the OTA updates, you can get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/desirec-ota-104882.7b1e5cca.zip !!!
Then, take the name of the file and paste it on the end of android.clients.google.com/updates/partner, for instance, for the Eris 1.17.605.1 OTA, the complete url is:
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
Note: because the 2.1 release is so vastly different than the 1.5 release, an OTA (if that's the way VZW/HTC rolls it out) for that will probably be very different than a patch release like this example ... but it would still be very useful for anyone who gets notice of an update to capture the URL using the "logcat" method shown above. There might be "interesting" tools included that could be exploited.
I don't think this will help get an "early OTA" - I'm not sure that hboot/fastboot methods can make use of an "update.zip" with an unrooted phone. Someone can correct me if I am wrong about that.
bftb0
Click to expand...
Click to collapse

---

Sorry, I didn't know. I just though it would be some information that I missed. I know I'm new here, but you don't have to treat me like I'm an idiot. Jeez. =[
Sent from my Eris using Tapatalk

---

I was just wondering if anyone who has gotten this has tested the root methods to make sure they still work, or if Verizon has patched them.