Verizon Replacement came with HBOOT 1.49

[Gnomesarealive]

I had a legitimate problem with my Eris that I sent it back for, but was still hoping to be able to root again when I got my replacement. Turns out it has HBOOT 1.49. Any one else encounter this?

 

[xAusTiN]

Yes there has been a thread on this before. Wonder how Verizon is supposed to do the next update with two different HBOOT numbers on phones.

 

[Gnomesarealive]

Yeah, I don't understand why. Seems to me like they installed the v3 leak onto the replacement phones. I'm not too happy.

 

[DroidJW]

Seems new Eris buyers are also receiving units with 2.1 installed

http://androidforums.com/htc-droid-eris/90290-getting-my-eris-today.html

Would be interesting to know if these are 1.5 units that have had the 2.1 "update" applied (leaving the HBOOT at 1.46 or 1.47) or if they have been flashed with the full 2.1 ROM (and likely the 1.49 HBOOT).

 

[rick311]

you guys are gettin leakers phones that they sent back. thats my theory.

 

[xx_bishop_xx]

Supplies!

 

[greyhndz]

Got my replacement today with 2.1 already installed. How can I check the HBOOT?

 

[surgeon0214]

Got my replacement today with 2.1 already installed. How can I check the HBOOT?

First power down. Then hold VOLUME DOWN and Power and a screen with skateboarding droids should come up with text, it will be on that page. Then just battery pull and reboot.

 

[senfoo]

ROFL. this is too funny.

 

[greyhndz]

Thanks, surgeon. I've got 1.49. So this was a legitimate 2.1 update as opposed to a "leaky" 2.1?

 

[Gnomesarealive]

To me this seems like they flashed the v3 leak onto it. Users who manually updated to 2.1 still had their 1.47 hboot, allowing them to root. Hopefully a way will be found to root with the new hboot. My replacement doesn't have the problem I sent my first Eris back for though, so with that I can be happy at least.

 

[DroidJW]

Thanks, surgeon. I've got 1.49. So this was a legitimate 2.1 update as opposed to a "leaky" 2.1?

It could be either a returned 2.1v3 leak OR it means Verizon is flashing replacements with the same ROM as the v3 leak (hence both having HBOOT 1.49)

Either way you are fine its been shown here in other threads that the 2.1v3 leak and the OTA 2.1 update are the same (except for the HBOOT version, and thus the ability to root)

 

[DroidJW]

To me this seems like they flashed the v3 leak onto it. Users who manually updated to 2.1 still had their 1.47 hboot, allowing them to root. Hopefully a way will be found to root with the new hboot. My replacement doesn't have the problem I sent my first Eris back for though, so with that I can be happy at least.

I believe this was because the manual update, like the OTA, did not wipe the phone, but rather updated the necessary files. The v3 leak was a full ROM image that resulted in a full wipe upon install.

Note the 2.1v3 ROM was over 100MB vs 77.7MB for the update file (smaller as it only included files that required updating and no new HBOOT)

 

[gpa111]

Mine just came with 1.47.

 

[Demache]

I'm legitimately concerned about this. Verizon is sending me a replacement because my current phone is nearly unusable due to the trackball scrolling left constantly. I really hope I get a phone with a 1.47 hboot. I really like having root.

 

[greyhndz]

This is an interesting topic. The phone I received has a date of 5/15 as the date of refurb (I assume). I also assume they would have done a factory reset prior to installing 2.1? If a phone has a leaked 2.1v3, would it be wiped by the factory reset? If so, wouldn't that make it more likely that phones coming out with after refurb would probably not have 2.1v3?

I know they're one and the same -- just curious.

 

[Gnomesarealive]

I think it is due to what DroidJW said. They are flashing the phones with the new ROM, causing the new hboot. They come with 2.1 now, so that it my theory as well.

 

[dewalist]

A friend of mine just got a brand-new Eris this week and was interested in rooting, only to find out that his hboot is indeed 1.49... :-( I really hope the devs can root that soon...

 

[hallstevenson]

Wonder how Verizon is supposed to do the next update with two different HBOOT numbers on phones.

First, they can remove any "checks" that looks at versions of s/w. Two, the current update-script used by OTA does not check 'hboot'.

 

[SirEagle]

............... Two, the current update-script used by OTA does not check 'hboot'.

Then why didn't anyone with a leak (1.49 HBoot) get the OTA?

 

[bjanow]

Then why didn't anyone with a leak (1.49 HBoot) get the OTA?

Excellent point. You can't even say that the OTA and the leak were the same because V.1 and V.2 were not the same and no leakers with any version got the update.

 

[SirEagle]

Excellent point. You can't even say that the OTA and the leak were the same because V.1 and V.2 were not the same and no leakers with any version got the update.

The only thing said was leak v3 was the same as the OTA, except for the HBoot.

 

[SirEagle]

But all three leaks have HBoot 1.49.

 

[MrChips]

Excellent point. You can't even say that the OTA and the leak were the same because V.1 and V.2 were not the same and no leakers with any version got the update.

That is probably because the OTA was for updating Android 1.5 to 2.1 not 2.1x to 2.1x. ...I mean, it makes complete sense right? I know the updates my company sends out are targeted to specific versions of our software and skipping of versions is not allowed.

 

[hallstevenson]

Then why didn't anyone with a leak (1.49 HBoot) get the OTA?

The update script checked the OS version, not 'hboot'. It was looking for "1.5" only. This is a fact, not speculation.

assert compatible_with("0.2") == "true"
assert file_contains("SYSTEM:build.prop",  "ro.build.fingerprint=verizon/htc_desirec/desirec/desirec:1.5/CUPCAKE/104882:user/release-keys")  == "true" || file_contains("SYSTEM:build.prop",  "ro.build.fingerprint=verizon/htc_desirec/desirec/desirec:2.1/ERD79/165907:user/release-keys")  == "true"
assert getprop("ro.product.device") == "desirec" ||  getprop("ro.build.product") == "desirec"