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
Related
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
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
nope_okay said:
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Click to expand...
Click to collapse
You need to replace CWM with the standard HTC recovery (you simply need to extract the recovery.img file from a RUU/ROM.zip file) and then relock the bootloader before the OTA will install correctly.
At hboot 1.16 and rooted all you should have to do is install Cwm and than you can flash custom ROM's..... Not sure what your problem is.
Sent from my anus using xda crap
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
nope_okay said:
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
Click to expand...
Click to collapse
Instead of trying to install the OTA update for Sense 3/2.3.5 why don't you flash the stock, rooted version of 2.3.5/Sense 3 ROM that I posted in the Dev section. With the unlocked bootloader and CWM you can flash this ROM and then manually flash the boot.img in that ROM's zip file and you should be good to go.
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
nope_okay said:
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
Click to expand...
Click to collapse
Here is the 2.3.5/Sense 3.0 stock, rooted ROM built directly from the OTA you were trying to install. You would flash it in CWM just like you did for CM7.
http://forum.xda-developers.com/showthread.php?t=1430535
Thanks for the link, will come in handy when I want to go back to a 'stock' setup... wasn't very impressed with CM7 so I then tried the Virtuous Affinity ROM (2.3.5/S3.5) - fantastic. Thanks again for your help!
G
Sorry in advance - I know there are a lot of guides for unrooting and re-flashing stock ROMs, but I've so far had no luck with any of those. I rooted a while ago and since then have been locked out of OTA and stock ROMS – I’m using a modified version of stock Gingerbread. I have downloaded the ICS update.zip and was hoping to flash this, however I understand this isn't possible (but tried anyway) with my current set up.
I know I can wait for some kindly soul to produce a 'cracked' version of the update but would rather be able to use stock and OTA a lot more easily. I think the issue is the root method I used, was the first available for Inc S at the time, so I think it was Unrevoked, although if not it was Revolutionary. Have had to update Hboot since then to get my GB ROM to load on.
My current boot info displays as:
Vivo Pvt Ship S-off RL
HBoot-7.00.1000 (it’s the 4pda.ru one)
Radio_3805.06.03.03_MeMMC-boot
I’m on 2.3.5 with Sense 3.0 and the software number is 3.08.405.3
If it’s relevant at all, when I first get in to bootloader I am greeted with some img32 errors.
Don’t think (read: hope) I’m not being too much of a noob here, although would love a quick fix! Does anyone have any suggestions or know of a guide to follow for this? Thanks a lot.
Hello Guys,
I got my New Incredible S two days ago but I am unaware of the rooting/unlocking process.
Here are my questions:
1. I am now on Stock Gingerbread 2.3.5 ROM. Is there anyway that I can root my device without having to unlock it.
2. If I do root the device then will I be able to unroot it and revert back to stock (Any risks)
3. If I choose to unlock the device, can I revert back and re-lock it.
4. What is the difference between S-ON and S-OFF (I dont understand the terms in the first place)
5. Difference between the rooting and unlocking process.
Please guys, i will be greatfull if any of you can help me out with my queries. I am new to HTC. I was previously using a Galaxy S and it was too simple for me to install custom roms. Came to HTC only for the Sense UI.
Thank you.
irfan88 said:
Hello Guys,
I got my New Incredible S two days ago but I am unaware of the rooting/unlocking process.
Here are my questions:
1. I am now on Stock Gingerbread 2.3.5 ROM. Is there anyway that I can root my device without having to unlock it.
2. If I do root the device then will I be able to unroot it and revert back to stock (Any risks)
3. If I choose to unlock the device, can I revert back and re-lock it.
4. What is the difference between S-ON and S-OFF (I dont understand the terms in the first place)
5. Difference between the rooting and unlocking process.
Please guys, i will be greatfull if any of you can help me out with my queries. I am new to HTC. I was previously using a Galaxy S and it was too simple for me to install custom roms. Came to HTC only for the Sense UI.
Thank you.
Click to expand...
Click to collapse
Welcome to HTC. I suggest you search and read the sticky posts in the forum. It will provide you with knowledge and answer your questions. On the HTC S-OFF provides you with a true unlocked system which makes it very easy to mod.
The official HTC unlock method does not really provide you with a flly unlocked system, so there are some mods that aren't as easy or impossible to perform.
tpbklake said:
Welcome to HTC. I suggest you search and read the sticky posts in the forum. It will provide you with knowledge and answer your questions. On the HTC S-OFF provides you with a true unlocked system which makes it very easy to mod.
The official HTC unlock method does not really provide you with a flly unlocked system, so there are some mods that aren't as easy or impossible to perform.
Click to expand...
Click to collapse
So If I do perform the S-OFF following ur posts, Will I be able to revert the device back to S-ON. My main question is, If I go the route of S-OFF then will I get official updates from HTC?
irfan88 said:
So If I do perform the S-OFF following ur posts, Will I be able to revert the device back to S-ON. My main question is, If I go the route of S-OFF then will I get official updates from HTC?
Click to expand...
Click to collapse
Yes the Revolutionary S-OFF can be undone and reverted back to S-ON. Yes if you S-OFF and keep your stock ROM, then you should get the ICS OTA notification, but you will have to revert back to stock in order to apply it.
tpbklake said:
Yes the Revolutionary S-OFF can be undone and reverted back to S-ON. Yes if you S-OFF and keep your stock ROM, then you should get the ICS OTA notification, but you will have to revert back to stock in order to apply it.
Click to expand...
Click to collapse
Sorry mate, that did not clear my mind. In simple words, If I choose to S-OFF and stay on the stock rom Gingerbread 2.3.5, will I be able to apply the official ICS update even though I have S-OFF with stock rom.
irfan88 said:
Sorry mate, that did not clear my mind. In simple words, If I choose to S-OFF and stay on the stock rom Gingerbread 2.3.5, will I be able to apply the official ICS update even though I have S-OFF with stock rom.
Click to expand...
Click to collapse
No the OTA update will fail because the S-OFF process write protects the bootloader and prevents anything from overwritng it to preserve S-OFF. The OTA will have a new version of the bootloader and since it will not be able to replace and update the S-OFF bootloader, you will end up with a phone that will not boot.
tpbklake said:
No the OTA update will fail because the S-OFF process write protects the bootloader and prevents anything from overwritng it to preserve S-OFF. The OTA will have a new version of the bootloader and since it will not be able to replace and update the S-OFF bootloader, you will end up with a phone that will not boot.
Click to expand...
Click to collapse
Thanks man. No more questions for now. I think I will wait for the Official update to arrive on my phone and then update to Custom roms if I dont find the OTA update interesting enough.
I am trying to work out whether to OTA update to ICS or go S-OFF, unlock and load a custom ROM.
I'm currently running locked BL, S-ON, Stock 2.3.5 (Sense 3.0) ROM.
I have read up on downgrading HBOOT to get S-OFF via revolutionary but I got HBOOT 2.01.0001 and haven't been able to find any thread saying whether tacoexploit works. I know if I OTA upgrade to ICS, and HBOOT 2.02.0000, I will only be able to unlock BL via HTCDEV and will not able to get full S-OFF until someone comes up with a method.
I have unlocked and flashed custom recovery/ROMs/Radios etc. on ZTE Blade, ZTE Skate, Motorola Atrix and HTC Desire (damn, I love 4Ext) without any problems but still consider myself a noob because, well you know, if you don't build your own ROMs...
I still have about a year or so on the warranty and custom ROMs always seem to have some kind of problem. So I just can't make my mind up as to what would be the right move.
Please, any info, suggestions or opinions would be greatly appreciated.
gandalf_grey91 said:
I am trying to work out whether to OTA update to ICS or go S-OFF, unlock and load a custom ROM.
I'm currently running locked BL, S-ON, Stock 2.3.5 (Sense 3.0) ROM.
I have read up on downgrading HBOOT to get S-OFF via revolutionary but I got HBOOT 2.01.0001 and haven't been able to find any thread saying whether tacoexploit works. I know if I OTA upgrade to ICS, and HBOOT 2.02.0000, I will only be able to unlock BL via HTCDEV and will not able to get full S-OFF until someone comes up with a method.
I have unlocked and flashed custom recovery/ROMs/Radios etc. on ZTE Blade, ZTE Skate, Motorola Atrix and HTC Desire (damn, I love 4Ext) without any problems but still consider myself a noob because, well you know, if you don't build your own ROMs...
I still have about a year or so on the warranty and custom ROMs always seem to have some kind of problem. So I just can't make my mind up as to what would be the right move.
Please, any info, suggestions or opinions would be greatly appreciated.
Click to expand...
Click to collapse
you can always try run this downgrader here.. http://forum.xda-developers.com/showthread.php?t=1705913 i would s off now because there might not be another exploit found for a very long time. you can always install a stock rooted rom through recovery. theres a thread on the development thread. thats if you still want stock rom.
gandalf_grey91 said:
I am trying to work out whether to OTA update to ICS or go S-OFF, unlock and load a custom ROM.
I'm currently running locked BL, S-ON, Stock 2.3.5 (Sense 3.0) ROM.
I have read up on downgrading HBOOT to get S-OFF via revolutionary but I got HBOOT 2.01.0001 and haven't been able to find any thread saying whether tacoexploit works. I know if I OTA upgrade to ICS, and HBOOT 2.02.0000, I will only be able to unlock BL via HTCDEV and will not able to get full S-OFF until someone comes up with a method.
I have unlocked and flashed custom recovery/ROMs/Radios etc. on ZTE Blade, ZTE Skate, Motorola Atrix and HTC Desire (damn, I love 4Ext) without any problems but still consider myself a noob because, well you know, if you don't build your own ROMs...
I still have about a year or so on the warranty and custom ROMs always seem to have some kind of problem. So I just can't make my mind up as to what would be the right move.
Please, any info, suggestions or opinions would be greatly appreciated.
Click to expand...
Click to collapse
The script and tacoroot exploit still work with HBOOT 2.01.0001, so you should be good to go.
naathaanb96 said:
you can always try run this downgrader here.. http://forum.xda-developers.com/showthread.php?t=1705913 i would s off now because there might not be another exploit found for a very long time. you can always install a stock rooted rom through recovery. theres a thread on the development thread. thats if you still want stock rom.
Click to expand...
Click to collapse
Yeah, that is my fear, it may be a long time before an exploit is found for the latest HBOOT. I also figure that there will never be an official JB ROM update from HTC for the beloved Inc S. While I have maintain my warranty for as long as I have, it does feel like the right time to fully unlock. My Inc S has never given me any trouble at all, so I'm not worried about losing the warranty. I just love the phone and want to keep it working well for as long a possible. ROM-wise, I think ARHD looks stock enough to be super stable and tweaked enough to be nice and slick.
tpbklake said:
The script and tacoroot exploit still work with HBOOT 2.01.0001, so you should be good to go.
Click to expand...
Click to collapse
Many Thanks for putting my mind at rest. That is what I needed to confirm before I started.
I did the downgrade from the latest ota and it worked perfectly
Sent from my HTC Incredible S using xda app-developers app