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
I flashed 33 and my phone is stock. I need paid apps plus this build is bugging out on me alot. Stuff freezes, its just a bad build. How do I undo this without rooting?
Pretty sure you have to root.
If its like FRF91. Then it wont let you downgrade because it sees FRF91 as an "old version."
Download ere27 as passimg.zip. place in your sdcard root. Boot into recovery. Restore. Let it do its work. Put frf91 into sd card. Boot into recovery and load from zip. Ta da. You are on Frf 91
Sent from my Nexus One using Tapatalk
Or, if you want a shorter and more correct route:
Nexus One Wiki, "Restore", PASSIMG.ZIP method, use FRF91 complete stock image found in one of the threads in Q&A from the last day (or Google).
Don't use FRF91 update, since it's only an update - it's not a complete image.
whatever. Just use a passimg.zip to clean out all the crap. its basically the "do-over" method. Think etch-a-sketch flip and shake.
i tried passimg from http://forum.xda-developers.com/showthread.php?t=717870
it said failure because it was an older version. If i find that ere one will it let me do it? i dont mind going way back and working my way back to froyo, but i dont think i can passimg anything since its considered "older"
search the forum for how to downgrade your hboot- it exists just search for the thread
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258
androidjedi said:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258
Click to expand...
Click to collapse
Thank you. Looks like ill have to root for it which im sure ill find if i search how to root 33 so ill wait for a while to see if something else comes up but at least I know there's a way
There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.
Jack_R1 said:
There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.
Click to expand...
Click to collapse
i dont know, i did 1 click root a few times but every rom i tried- cyan, eno, modac, whatever were great but there was always some bug or something that was annoying enough that i just wanted stock instead. So i dont know how much i like the idea of permanent root, but theres probably a stock rom i can use so its not the end of the world. SDK/Terminal i did all that crap with my g1, personally i found it to be more of a hassle than it was worth. But not having protected apps is not going to cut it so ill cave soon im sure
Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?
Jack_R1 said:
Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?
Click to expand...
Click to collapse
the only way to go back from FRG33 is to unlock the bootloader at this stage, the PASSIMG method does not work
When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?
Why people can't understand?At this moment,if you've flashed stock FRG33 rom,using PASSIMG method,you can't root anymore!The only method to roll back to FRF91 is to unlock your bootloader,which is permanent and can't be un-done!
Cheers
Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".
Jack_R1 said:
When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?
Click to expand...
Click to collapse
Code:
[HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
Thanks to the guys in the Desire forums and help from the Nexus Q&A, I have reverted my phone to the original HBOOT so I can apply custom roms again.
First you need to root the Korean FRF91 that's on your phone using Paul's instructions for superboot FRF83.
If you are rooted already, skip this step.
http://android.modaco.com/content/go...the-nexus-one/
Code:
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then press and hold the trackball to enter the bootloader
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
Note: If you are using a retail Nexus One, you may need to unlock the bootloader first, as detailed here.
Ok, let's make some order:
1) PASSIMG can flash versions with the same or higher HBOOT version - to check: will the same version flash? I believe so.
The official FRF91 has HBOOT 0.33.0012, the Korean FRF91 has 0.35.0017, and I suppose the FRG33 also has 0.35.0017 - correct?
2) Rooting isn't possible on FRG33 yet. 1 report doesn't count.
So, looking at this:
Using PASSIMG with the Korean FRF91 (complete with HBOOT 0.35.0017) will work over FRG33, if the HBOOT is indeed the same version.
Korean FRF91 is rootable.
Rooting Korean FRF91 allows to downgrade HBOOT, which in order allows to use PASSIMG method to flash official FRF91 with older HBOOT.
So, did anyone try PASSIMG with Korean FRF91?
Jack_R1 said:
Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".
Click to expand...
Click to collapse
Downloading and testing, thanks for the tip, will report back.
Hello,
I have some question regarding HBOOT:
What is HBOOT?
What is the difference between Bootloader and HBOOT?
Why should I upgrade or why I shouldn't?
If I upgraded it is it easy to downgrade?
Mine is HBOOT-0.33.0012 and there is a version HBOOT-0.35.0017
Because some ROMs requires the newer version and I saw some article warn not to update!!
Thank you and Regards.
http://forum.xda-developers.com/showthread.php?t=910865
http://forum.xda-developers.com/showthread.php?t=913179
1. Hboot is the boot loader.
2. See above.
3. Upgrading to the new Hboot supposedly gives you some small benefits such as better reliability in certain cases. It is also supposedly required by gingerbread. Most of the AOSP builds of gingerbread don't require the updated Hboot, but the initial builds required it. If you upgrade to the new hboot, I believe you loose the ability to flash images by the PASSIMG method (renaming a signed image to passimg.zip). The new Hboot was rolled out as an update along with the FRG83D OTA. I see no real reason to upgrade it or downgrade it. Messing with it could be dangerous.
4. http://forum.xda-developers.com/showthread.php?t=726258 I wouldn't say it is easy, but it is possible to downgrade. Not sure why you would want to. Downgrading an SLDC Nexus will brick it.
The warning to not update was due to some ROMs not working on .35 as the update script was checking for .33, however this was months ago and is no longer an issue.
Thank you guys for the reply, I already upgrade it to use a gingerbread rom, I think I'm going to stick with it for awhile. If I needed urgent to downgrade it I will try it but not now.
Don't worry, you'll never need to downgrade it.
Rusty! said:
Don't worry, you'll never need to downgrade it.
Click to expand...
Click to collapse
You made me happy now
All,
I unlocked the bootloader (I see the unlocked padlock at the bottom of the screen at boot) some time ago on my N1. Now that the official 2.3.3 update is out, I thought I would give it a try.
I keep getting 'signature verification failures' when I tried to install either the official or other versions of 2.3.3
So, I learned it was likely because my HBOOT needed to updated. I downloaded an tried to install the new version (0.35.0017?) and it sorta acts like it is going to update it, reboots a couple of times, but doesn't seem to work.
Could someone please give me some guidance on exactly what I need to do from here to get the 2.3.3. update applied?
Thanks in advance,
-Rob
You most probably have custom recovery, and your problem isn't bootloader at all.
Flash the stock version packaged for custom recovery, found in Development section.
After downgrading my G1 to version 1.0. I installed a cupcake rom v1.5. rooted the phone..am having problem installing Gingerbread.. Any full help on how to go about it will be really appreciated. Thanks
the problem most likely is an incompatible radio/spl with the rom you are planning to use. most of the "newer" roms require the 2708+ update.
boot into hboot and check what you have