• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Who got the update??

I got the email last night and thought it was strange because it said it was for v2.1.

I am on Lv3 and the phone is now updating - First one I ever had!

Took about 5-6 minutes.

Software Information:

Firmware version
2.1

Baseband version
2.42.01.04.27

Kernal version
2.6.29-8a03cb9a

Build number
2.37.605.4 CL185970 release-keys

Software number
2.37.605.4

Browser version
WebKit 3.1

PRI version
2.11_002

PRL version
51866

ERI version
3
 
Upvote 0
I got the email last night and thought it was strange because it said it was for v2.1.

I am on Lv3 and the phone is now updating - First one I ever had!

Took about 5-6 minutes.

Software Information:

Firmware version
2.1

Baseband version
2.42.01.04.27

Kernal version
2.6.29-8a03cb9a

Build number
2.37.605.4 CL185970 release-keys

Software number
2.37.605.4

Browser version
WebKit 3.1

PRI version
2.11_002

PRL version
51866

ERI version
3

I also got the v2.1 email yesterday. That is not related to this update. We got it because we were on v2.1l3 and did not receive the official 2.1OTA. They still think we are on v1.5. This new update should bring us up to par as far as their database is concerned.

I was part of the few to receive this current update a couple of weeks ago. Other than version number differences, I have seen no difference in phone performance. I had not experience the silent phone bug so don't know if this update addressed that.
 
Upvote 0
Been seeing this comment often, and don't know what its about...
"50% bug"? What is that in reference to?

Its a bug with your battery, if you go into settings>about phone>battery>cell standby and you see "TIME WITHOUT SIGNAL 50%" it means you have the bug. Technically no-one knows what it actually does but some people believe it has an effect on battery life. To get rid of the 50% number go into airplane mode, put phone to sleep, wait for about 15 seconds, turn screen back on and turn airplane mode back off. The number will slowly drop to 0%, which is good.
 
Upvote 0
I got the new update...or maybe got the newest 2.1. I was on Lv3...so I guess I am a LEAKER that is up-to-date now!

I have the 50% bug and have not seen any change...:( I was wondering how everyone had all these screens of widgets and such and I have 2 and can't keep a battery for the life of me. I also use a task killer or my batter is 1/2 gone by 10AM without use.

Do you suggest a factory reset after this update?

Thank you for your time!
Trisha
 
Upvote 0
ALL: Remember to capture the URL so that the developers can extract the fixes and put them in other ROMs or roll them in a package for all of us that have OTA disabled:

FYI: OTA URL capture - xda-developers

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
 
Upvote 0
W/SystemUpdateHelper( 74): !!! REBOOTING TO INSTALL /cache/8e3b63f96149.OTA_Desire_C_Verizon_WWE_2.37.605.4_2.36.605.1_release.zip !!!

D/ ( 74): unable to unlink '/cache/recovery/command': No such file or directory (errno=2)

D/ ( 74): unable to unlink '/cache/recovery/log': No such file or directory (errno=2)
-----------------------------------------------------------------------------
The moment you've all been waiting for!
 
  • Like
Reactions: MrDangerous
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones