FORUMS

What Are the Best Looking Apps on Android?

As more developers are updating their apps with Material Design elements, we’re … more

Cyngn Explained: Who’s Cyanogen, What’s Cyanogen OS?

While Cyanogen, Inc has been the source of many headlines lately, there … more

Verizon Moto X 2014 Receives Root On Kitkat 4.4.4

The Verizon Moto X 2014 has finally received root, albeit only on Kitkat 4.4.4 … more

Android 5.1.1 Released, Google Cell Service – XDA TV

Android Lollipop 5.1.1 has been released. That and much more news is covered … more
Post Reply Subscribe to Thread Email Thread

[Q] What is d6096cac5e9f.signed-hboot-0.35.0017.zip ?

15th October 2010, 07:52 PM |#1  
mlevin's Avatar
OP Senior Member
Flag Fairfax, VA
Thanks Meter: 0
 
More
Hi,

I'm on MoDaCo r21 (FRF91). Every few days, I get alerts that there's an update. There seem to be some problems that haven't quite been worked out with MoDaCo r22 (FRG83), so I'm holding off on upgrading. So every few days, I get an alert that there's an OTA update available. I go into /cache and delete the .zip file that was downloaded, then "accept" the update, which of course fails because the file isn't there, and then I proceed on my way until it happens again.

Up until recently, it always said the update was "Android 2.2 Update" or something and the filename was

Code:
c8847c98b948.signed-passion-FRG83-from-FRF91.c8847c98.zip
This was, as far as I know, a few minor fixes and was just an update to the /system partition.

Now, I've just noticed that the file I was pushed is

Code:
d6096cac5e9f.signed-hboot-0.35.0017.zip
and this appears to have an hboot.img embedded in it. I don't know how to crack open an .img file, so my question is, what the heck is this update? The update screen says "Update 1 of 2: This is the first part of an update and it must be installed before the second part is installed" or something like that.

I'm getting paranoid here. Is this some trick from HTC to get me to update my bootloader with a locked-down one like the G2?

The thing I love about the Nexus One is that the whole thing can be legitimately unlocked -- so I hope there's not an update that will change that.

I actually rooted my phone without doing the "fastboot oem unlock" as I didn't want to void my warranty (despite the many claims that HTC still honors claims for things that are clearly hardware-related), but I've always felt safe that I have that option in my back pocket in case I ever screw up so bad that I can only recover via fastboot.

Or maybe this is just a new radio and I'm over-reacting

Can anyone confirm? Or point me to some info on how to examine an .img file?

Thanks
 
 
15th October 2010, 07:59 PM |#2  
Zane Lee's Avatar
Member
Thanks Meter: 0
 
Donate to Me
More
I got exactly the same update and I thought it was Gingerbread since this became a 2-part update. I searched around and the new hboot has always been shipped with Korean and SLCD Nexus One(s), and I guess they wanted to update our hboot to the new one as well.

I updated to it, but well you can still install custom roms when you're rooted, and it doesn't affect your current rom as well. So I guess it's perfectly fine, or if someone else wants to correct me.

My bootloader now displays:
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-4.06.00.12_7
Oct 12 2010,14:33:16
15th October 2010, 08:32 PM |#3  
egzthunder1's Avatar
Moderator Committee Lead / Member Advocate Admin - Spirit of XDA
Flag At The Good End Of My Hammer, Likes: My Family & XDA, Dislikes: Incompetence
Thanks Meter: 6,010
 
More
Thread moved to Q&A.
24th November 2010, 01:26 AM |#4  
El Daddy's Avatar
Forum Moderator
Flag Roseville, MN
Thanks Meter: 5,090
 
More
I never got an on-screen prompt about it but I did notice while watching ddms after flashing a new rom that hboot-0.35.0017 was pushed to my phone and the verification failed.

I'm oem fastboot unlocked and running CM 6.1 nightly build 262.

Has anyone determined the new bootloader is needed for future things? i.e. Gingerbread?
24th November 2010, 11:49 PM |#5  
Member
Flag Toronto
Thanks Meter: 2
 
More
can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?
25th November 2010, 02:07 AM |#6  
efrant's Avatar
Senior Moderator
Flag Montreal Bow2DaCow
Thanks Meter: 8,653
 
Donate to Me
More
Quote:
Originally Posted by hayden1987

can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?

Yes, it is safe. And no,you will not lose root.
25th November 2010, 02:47 AM |#7  
danger-rat's Avatar
Senior Member
Flag USA
Thanks Meter: 316
 
More
Quote:
Originally Posted by hayden1987

can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?

Well, so far, the 0.35 hboot won't let you use the PASSIMG method to re-image your phone, and doesn't appear to like Amon Ra 2.0 (not confirmed, but I've noticed a few issues). I've also seen potentially related problems with fastboot privileges...

Sent from my Nexus One using XDA App
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes