Database Develop

[HELP] Revert to 0.33.0012 SPL

Hi all,
I foolishly flashed the Korean FRF91 onto my N1 and now I have SPL 0.35.0017 instead of the normal 0.33.0012 version.
To downgrade, I have tried:
- repacking the 0.33.0012 HBOOT into an update.zip (Looks like it worked, but it didn't)
- Flashing 0.33.0012 through FASTBOOT (Verification failed)
- Applying an older Google update (Main version is older)
Any ideas?
Thanks!

http://android.modaco.com/content/htc-desire-desire-modaco-com/310970/how-to-downgrade-hboot/

OK, I think that worked...
But now my N1 has an HTC logo on the screen for FASTBOOT.

can you explain how do you have made .
i don't understand the tutorial. (i m french :s)
if you can link the file you have apply.
thank's

cursordroid said:
OK, I think that worked...
But now my N1 has an HTC logo on the screen for FASTBOOT.
Click to expand...
Click to collapse
Probably because the link given by baseballkyle is in the "HTC Desire" section of the modaco forum, not nexus one.

Yes,
I would also appreciate an explanation on how you did it.
I tried it but it didn't work for me.
The hboot.img doesn't work. If I try a zip version it seems that the device accepts it and flash it but i keep having the wrong version installed.
Could you explain how you made the mtd0.img (with which numbers) and provide a link to the hboot version that worked for you?

PLs Help Also
Pls tell us also how u did it, thanks..

http://forum.xda-developers.com/showthread.php?t=726258
I have posted instructions here.

Great!!!
The key was applying the hboot file through the PASSIMG.ZIP and not just alone.
Fantastic.
Thanks a lot

nexus Hboot
What happen if I install the korean hboot. Because everybody is complaining about it. They want to return back to stock Hboot.

Though that hboot is newer currently all the signed firmwares (original ones, CM6, and whoever provide signed builds) check that the hboot version installed in the phone is 0.33.2012.
If you don't have that one then you will not be able to install any of this firmwares directly.
With some manual work you can make it happened but forget about OTA updates (stock OTA updates, CM-updater OTA updates, Rom Manager OTA updates).
If you don't care about that then you are fine.

help
i cant install any ota update can someone please help i went to erd 79 hoping that would fix everything

So what is the correct hboot version to use? I currently have 0.33.0012
Sent from my Nexus One using XDA App

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

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

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

Thread moved to Q&A.

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?

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?

hayden1987 said:
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?
Click to expand...
Click to collapse
Yes, it is safe. And no,you will not lose root.

hayden1987 said:
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?
Click to expand...
Click to collapse
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

[Q] Flashing: Main Version is older

Hey guys
I'm preparing my N1 for 2.3.3 and since I had it repaired I'm now stuck with some weird Vodafone(?)-FW.
2.2.1
2.6.32.9-g6624e39htc-kernel [ät] and18-2
5.12.00.08
HBOOT 35.0017
Anyways, I tried to flash it back to stock 2.2.1 but when I apply the PASSIMG.zip it says "Main version is older. Update failed!"
Is there a workaround?
I read something about downgrading HBOOT to a lower version?
Thanks!

If FRG33 isn't flashing by PASSIMG method - then you can't use it. If you exercise your abilities to search the forum, you'll find a thread where people were trying to circumvent that - updating from Eclair to Froyo (just like now) - and those attempts failed.
If you have SLCD phone - and if recently repaired, you definitely have it - downgrading HBOOT will leave you with a nice brick.
Root your phone, install custom recovery, flash whatever you want from there.

I'll try that. Thank you very much.

Now running on Cyanogen.
Thanks again!

You're welcome

[ROM]OTA_Vivo_Gingerbread_S_HTC_WWE_2.12.405.7-1.36.405.1

This just in:
http://fotadl.htc.com/OTA_Vivo_Ging...1.36.405.1_release_1877251m0fkulovs00nwzq.zip
At last
multiupload mirrors:
http://www.multiupload.com/17S46R9DWY

can one apply this without losing the S-OFF?

the OTA didn't like my rooted phone + recovery.

Wow... that's cool... my IS is coming home in some days..would put it through it shortly.

mindas69 said:
the OTA didn't like my rooted phone + recovery.
Click to expand...
Click to collapse
because the recovery is changed.... u cant do an ota...

I have a s-on bell device can I put on SD card as update zip and flash it?what is proper way on this device
Sent from my HTC Incredible S using XDA App

Is it possible to flash the european ota on an Asian incredible s? I am s-on
Sent from my HTC Incredible S using XDA App

i'm using RUU_Vivo_Gingerbread_S_Virgin_Mobile_AU_2.12.981.2 _R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_ 185029_signed,
to update new version,does my phone have to come back factory default rom???
I'm using vietnamese network!
help me! upgrate OTA!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

gemini002 said:
I have a s-on bell device can I put on SD card as update zip and flash it?what is proper way on this device
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
I'm in the same situation, trying to figure out if I can install it on my Bell IS (I'm unlocked on AT&T). Anybody tried it yet?

Can we install this OTA ROM on indian IS s-on?

How can I install this one?
I've got a S-ON Incredible S, tried to rename to PG32IMG.zip and put it at the root of my sd card but no luck.
So I've extracted firmware.zip inside the file and renamed to PG32IMG.zip. Incredible S upgraded my hboot and radio but no the os version and now I can't get my wifi working anymore (got error as soon as I turn on wifi).

If I were you, I would use the official RUU instead.
http://www.multiupload.com/7KZ26DUGJ8
It will wipe your phone, but I think you will not be stuck in between 2 versions.
Just my 2 cents though
<EDIT>
That is, if you have a european IS, by the way.
</EDIT>

I'm trying right now, but if I launch the updater from booted os it gives me error 155 which readme says is an incorrect rom image for my phone.
If I try to upgrade from the HBOOT, the updater says I've got not enough battery (30% min) but my battery is full of charge.

Is your phone branded? I think this RUU is for unbranded phones only.. but I am not sure.

I'm trying with the goldcard method, it's flashing at the moment, I'll post my results as soon as it's finished

[Q] Error when Updating manually

Hi, i got this new nexus one and its running on Android 2.2 and i want to update it 2.2.2, i downloaded the update, put it in the root of the SD card, entered the boot menu and clicked on apply update.zip and i got the following message, why am i getting this error:
"Finding update package, Opening update package, verifying update package,
E: Failed to verify whole -file signature
E: Signature verification failed
Installation aborted"
I am running on Android 2.2
Bandbase version 32.41.00.32U_5.08.00.04
Kernel version 2.6.32.9-27227-g3c98b0d [email protected]#1
Build number 2.16.405.1 CL223106 release-keys
I have already unlocked the bootloader.
The boot menu says NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0c15

No one to give an idea?
Sent from my Nexus One using XDA App

It's because you got the phone from videotron of vodafone. I can tell because of your build number it means that you can't update because your are on a carrier tweaked ROM for instructions on how to get back to stock see wiki http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus after you follow this tutorial you will be on frg33 then you can update what ever your want from there.

Thanks so much. I shall try that and let you know if it worked or not. Thanks so much for the info.
Sent from my Nexus One using XDA App

Hey, i used the PASSIMG method and it worked, thanks, i am now running gingerbread and in the process of rooting it.. thanks
Sent from my Nexus One using XDA App

Thank you both for this thread. I bought a Nexus One off of eBay recently and it must have come from the same batch. I had the same build number and could not update manually or otherwise.
Minutes after I installed the stock firmware, the phone was automatically updating to 2.3.4.
I am a happy camper now.