Database Develop

HBOOT 0.35 update and S-OFF question

Hi!
I've got a Nexus One with HBOOT 0.33 and S-OFF. I guess it's a developer version. I'm wondering if anyone with S-OFF tried updating to HBOOT 0.35 and if their phones remained S-OFF or of they lost it. Not sure about updating just yet, but my boot partition has some bad blocks, so I guess I could benefit from it. Please let me know.

wrong section

Sorry, mods, please move this to the correct sub-forum.

I have S-ON since I updated to 0.35, but I still can flash ROMs etc.. whats the difference between S-ON and S-OFF if I still can flash ROMs and the AMON_RA Recovery still works?

[email protected] said:
I have S-ON since I updated to 0.35, but I still can flash ROMs etc.. whats the difference between S-ON and S-OFF if I still can flash ROMs and the AMON_RA Recovery still works?
Click to expand...
Click to collapse
You can relock the bootloader.

Not sure about "wrong section". My personal advise: If you haven't realized or felt the need for S-OFF its not really important, devices have a short life time, make sure you don't waste too much time on this subject as it is really for system developers.
Warranty theoretically expires by unlocking the boot loader, as for real life I haven't heard yet of a single "rejection" by HTC due an unlocked boot loader.. except if you brick your screen by dropping the device etc.
Hope this helps.

Well, I guess I'm just proud of having an S-OFF version of the phone, but no real use for it. I'll leave it for now, I guess and will let you know the result if I do update it.

completely pointless, however I think I'd feel the same ;-)

(Now sitting at a real keyboard, easier to type)
RunTimeWorld is correct, these devices do have a short life time, so it would be a shame to wast it on waiting for an answer/explanation of a small thing like S-OFF on a Nexus One. However, I figured it like this: Seeing as I can run Kang-o-Rama with IR's kernel properly on my current HBOOT/Radio config, I'm not changing it until I need to. I see that my phone frequently is checking (and finding) the HBOOT update, but we'll just see when CM7 is closer to release. All that 0.35 would profit me would be a smaller recovery partition but a larger boot partition. If I need to flash a larger kernel, I'll definitely switch.

Mine remained S-OFF after updating to .35

Rusty! said:
Mine remained S-OFF after updating to .35
Click to expand...
Click to collapse
Sounds reassuring.
Exactly how did you update to 0.35? Using the official zip file downloaded from the Google servers or through the Korean OTA/RUU?

Via the recent 2 part OTA update (not Korean).

Aha, so I guess I'll just try it then.

Success
Here's the result, for you other Nexus One owners with S-OFF. Like i said, it's pretty much only for personal pride, but it's still nice to see my phone didn't loose it's "Developer phone" status when upgrading the HBOOT.

I believe the 'developer' ones say "ENG S-OFF", not "SHIP S-OFF"... ours are freaks and probably just a mistake by HTC.

Well, I guess you could be right. Mine was bought second hand in late May 2010 from a person who's mother (the actual previous owner) works for the Swedish telecommunication company Ericsson. One can only guess that she got it at some Google event or something similar. Anyway, I'm quite pleased to have something special.

Help with network branded firmware

Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.

bobsie41 said:
Yesterday I received my one from T-Mobile UK with 1.28.61.7 on board. I am not quite a noob but I have always had devices with WWE un-branded firmwares. There is no bloatware on the device but I guess that, until s-off, I am dependant on T-Mobile to provide updates.
I am not particularly bothered about custom roms and, in the past I have usually gone with stock rooted roms so that I can go add-free and remove anything that I do not require.
Last night I lied awake thinking about the implications about what I have and I really need some informed advice about it.
If I root my device, how can I return it to stock in the future so that I can receive any ota updates that T-Mobile may eventually offer without a RUU which appear to be quite scarce?
Am I able to install custom firmwares based on higher firmwares ie. 1.29.401.12 and, if yes, will I be able to return my device back to stock without an RUU as backup?
I am most confused about the scenario which I have. I love the device apart from the 3 dot menu bar which is doing my head in and am confident in my ability to remove it but am worried about my safety net if something goes wrong. Please somebody enlighten me as to what I am and are not able to do. Thanks in advance.
Click to expand...
Click to collapse
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.

wnp_79 said:
You have options. Firstly S-Off is not likely to come soon if at all. HTC made it such a pig to crack, the entire year I had my One X it was never (to my knowledge) posted here how to do it. But it's not really that necessary. S-Off just adds convenience for flashing kernels in recovery at the same time as a ROM. With S-on you just have to accept that a bit more faff is required using fastboot to change a kernel.
(Side note: I have not had my device arrive yet so I am staying out of the development threads. I heard a rumour you can have a flashable kernel for this phone with S-On. Anyone know if this is true?)
Once a custom recovery is on, take a backup of your stock ROM. That way if you ever really wanted to go back for an official OTA update, you could restore the backup, flash back the stock recovery and relock the bootloader. Not sure why you'd want to go this route though.
Being on XDA and knowing how to do this stuff means you can get all the features an official update will bring you, usually months before any carrier will be providing it. You'll just be going through all this extra work to get an update that has been in the custom ROMs for ages.
Click to expand...
Click to collapse
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
S-off together with super cid would give us the ability to use any RUU for this device which gives us an excellent safety net.

bobsie41 said:
Thanks for your answer. As I said, I am not quite a noob :silly:. The reason I am looking to go back to stock at a later date is that I believe (rightly or wrongly you tell me) that to update firmware in it's entirety, it is necessary to use an official update from the provider.
If I back up my official stock rom after I root, are you absolutely sure that when restoring this backup, I will be able to receive official ota updates? It is not that I don't believe you, just want to be 100% sure.
Edit Perhaps we are more likely to get s-off now that we are on Quallcom not Tegra?
Click to expand...
Click to collapse
It's ok. It's always best to be sure before attempting something!
You will not loose out on anything by not using an official update. All it will be is the stock firmware with T-Mobile's add touches. More often than improvements to the stock firmware, carries tend to restrict the features of a ROM and add bloatware (like game demos you can't uninstall) because they have made a deal with a game developer to make some money forcing them upon you.
Even without a nandroid backup you'll still be able to download and flash the stock firmware somewhere here. Basically anything you do to your phone you will be able to undo if you so choose. The only exception to this is that if you re-lock your bootloader, HTC will still be able to tell that it was at some point unlocked if you wanted a warranty return.

Yeah, as long as the stock bootloader is available, you just need to flash it after restoring the backup, and the updates should arrive.
The firmware might be flashable without the RUU or OTA, it was on the One X, but it was necessary to relock the bootloader.
I say go for it, mike1986 has the stock ROM in the dev section as well as his stock like improved ROM.

[Q] AT&T OTA Not working - Stock

Hey guys, I just bought this phone yesterday from AT&T. Just out of the box I received an OTA update, which I thought was the KK update. But no, I am stuck on android 4.1.2 and Sense 5.0, and when I try to update, all I get is a message saying that everything is up to date and there are no updates available for me.
I am on the AT&T network at the time, and my phone is completely stock, no mod whatsoever. Any ideas what is going on????

You might want to exchange for a new unit or request for them to update, for all we know applying solutions suggested by us might just void the warranty instead.
Sent from my HTC One using Tapatalk

Piachnp said:
Hey guys, I just bought this phone yesterday from AT&T. Just out of the box I received an OTA update, which I thought was the KK update. But no, I am stuck on android 4.1.2 and Sense 5.0, and when I try to update, all I get is a message saying that everything is up to date and there are no updates available for me.
I am on the AT&T network at the time, and my phone is completely stock, no mod whatsoever. Any ideas what is going on????
Click to expand...
Click to collapse
use this RUU to get to 4.3 >> http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
you need locked / relocked bootloader
being your on 4.1.2 now would be a great time to get s-off before doing the ruu update. check this guide for getting s-off
http://forum.xda-developers.com/showthread.php?t=2365506

clsA said:
being your on 4.1.2 now would be a great time to get s-off before doing the ruu update. check this guide for getting s-off
http://forum.xda-developers.com/showthread.php?t=2365506
Click to expand...
Click to collapse
+1 .. do it now!

Lets say I don't do S-Off (i don't really know what that is, my earlier phone was a crappy samsung) and I do the update with the RUU, will I be able to do S-Off later???
The thing is that i don't want to void the warranty. Coming from a really bad phone, where I had to mod EVERYTHING to get it working acceptably, I would really like to settle down and be stock for a while. Of course, that feeling will probably last a few months and then I will be flashing roms every 2 days lol.
If I flash the RUU manually, that doesn't void the warranty right? I mean, its an official firmware i suppose. On the other hand, if I can only do the S-Off thing right now, i might consider staying a while longer with 4.1.2 ... after all it is not so bad.

Piachnp said:
Lets say I don't do S-Off (i don't really know what that is, my earlier phone was a crappy samsung) and I do the update with the RUU, will I be able to do S-Off later???
The thing is that i don't want to void the warranty. Coming from a really bad phone, where I had to mod EVERYTHING to get it working acceptably, I would really like to settle down and be stock for a while. Of course, that feeling will probably last a few months and then I will be flashing roms every 2 days lol.
If I flash the RUU manually, that doesn't void the warranty right? I mean, its an official firmware i suppose. On the other hand, if I can only do the S-Off thing right now, i might consider staying a while longer with 4.1.2 ... after all it is not so bad.
Click to expand...
Click to collapse
Yes it is HARDER to do S-OFF on later updates.

SaHiLzZ said:
Yes it is HARDER to do S-OFF on later updates.
Click to expand...
Click to collapse
Mmm I think I'll start reading more before I make any decisions. Eventually I will root and install custom rims and kernels, so I'd like to keep my options open. If it's HARD but not impossible I might upgrade and stay stock.
Would you say there's a big difference between 4.1.2 / Sense 5.0 and 4.3 / Sense 5.5 ???

It's not that hard really.. i decided to s-off when im already running a KK rom. Firewater worked like a charm.
Sent from my HTC One using XDA Premium 4 mobile app

Gain S-Off now, and forever be happy. I never cared about OTA when I had that phone, I could run any RUU I wanted to, I changed from ATT to Dev, to GPE and back so many times. Just awesome.

JiroPrinz8 said:
It's not that hard really.. i decided to s-off when im already running a KK rom. Firewater worked like a charm.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Until you get whelped..

New N6 owner with a quick question

Mine just came in today (64 GB Cloud White). Very impressed so far. I'm going to unlock, root, ROM. I'm not a noon in this area - been doing it since the OG Droid days. Not going to do it with a toolkit.
Anyway, it came with 5.0 (build number LNX97M) but I have a notification for a system update. Shows it's the update for 5.0.1, but I imagine the 5.1 update will follow shortly. Can these updates be unlocked/rooted? I assume so, but I like to be certain first. Thanks in advance for your help.

Rodeojones said:
Mine just came in today (64 GB Cloud White). Very impressed so far. I'm going to unlock, root, ROM. I'm not a noon in this area - been doing it since the OG Droid days. Not going to do it with a toolkit.
Anyway, it came with 5.0 (build number LNX97M) but I have a notification for a system update. Shows it's the update for 5.0.1, but I imagine the 5.1 update will follow shortly. Can these updates be unlocked/rooted? I assume so, but I like to be certain first. Thanks in advance for your help.
Click to expand...
Click to collapse
all nexus updates can easily be bootloader unlocked and rooted. google makes any nexus device easy to be bootloader unlicked and rooted, that who put in the option of fastboot oem unlock

simms22 said:
all nexus updates can easily be bootloader unlocked and rooted. google makes any nexus device easy to be bootloader unlicked and rooted, that who put in the option of fastboot oem unlock
Click to expand...
Click to collapse
Thanks. I figured as much, but wanted to be certain. Haven't had a Nexus since the Galaxy Nexus, so I'm used to being extra cautious about these things. I'll go ahead with the OTAs then unlock and root.

Rodeojones said:
Thanks. I figured as much, but wanted to be certain. Haven't had a Nexus since the Galaxy Nexus, so I'm used to being extra cautious about these things. I'll go ahead with the OTAs then unlock and root.
Click to expand...
Click to collapse
you'll get an update for 5.1 after updating to 5.0.1, then later on, you'll get an update for 5.1.1. or, you can also flash and use M

Nexus 6 5.1 Bootloader

When I first got the N6 in June I immediately unlocked the bootloader and flashed CyanogenMod 12. Now I remember reading beforehand that if you updated your device to 5.1 via the factory images or OTA, that the bootloader cannot be downgraded anymore. I made sure to not do this so my N6 is on the very first bootloader still and I haven't had any issues.
Now, I feel like I read that there was a reason to want to downgrade and a reason for not wanting this new bootloader but I can no longer find any information on this whole topic, other than people saying yo ucannot downgrade.
I'm asking if there are potentially issues if I do update or if it's ok to stay on my current old bootloader when I update to 6.0 soon?

admiralspeedy said:
When I first got the N6 in June I immediately unlocked the bootloader and flashed CyanogenMod 12. Now I remember reading beforehand that if you updated your device to 5.1 via the factory images or OTA, that the bootloader cannot be downgraded anymore. I made sure to not do this so my N6 is on the very first bootloader still and I haven't had any issues.
Now, I feel like I read that there was a reason to want to downgrade and a reason for not wanting this new bootloader but I can no longer find any information on this whole topic, other than people saying yo ucannot downgrade.
I'm asking if there are potentially issues if I do update or if it's ok to stay on my current old bootloader when I update to 6.0 soon?
Click to expand...
Click to collapse
You couldn't downgrade from a 5.1 bootloader to a 5.0 bootloader, because the 5.1 bootloader brought some new security features in. I don't know of any reason why you would want to downgrade the bootloader.
There is no reason to not upgrade it either, though as far as I am aware, 6.0 will work with a 5.1 BL, just don't think it will work with a 5.0 one.

I see, thank you!