Database Develop

[Q] What does this mean in my bootloader?

Ok, this is my fasboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
My phone is back to completely stock now and I need to return to s-on for repairs
What does the dirty bootloader mean and how will that affect my phone if I do fastboot oem writesecureflag 3?

stovie_steve said:
What does the dirty bootloader mean
Click to expand...
Click to collapse
touch of jobo said:
The commit number refers to the code repository that devs at HTC use. Every time a dev commits code to the repo, that commit gets a unique number.
Their build server checks out the repo and adds the latest commit number to some macro or header, so that products can report it.
A dirty build only recompiles the files that were modified and their dependencies. A clean build removes all object code and recompiles everything.
So the commitno is an identifier that HTC devs can use to go back in time and checkout the exact same code that your hboot was built from.
Click to expand...
Click to collapse
stovie_steve said:
how will that affect my phone if I do fastboot oem writesecureflag 3?
Click to expand...
Click to collapse
It will turn you phone back to S-ON and it will look like this:
stovie_steve said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse

Lol I know it will do that, but will it result in a tampered message in my bootloader even if I'm completely back to stock, no modified hboot and locked bootloader?

stovie_steve said:
Lol I know it will do that, but will it result in a tampered message in my bootloader even if I'm completely back to stock, no modified hboot and locked bootloader?
Click to expand...
Click to collapse
it shouldn't

Many thanks for replying
I originally downgraded my hboot to 1.44 after getting s off with rumrunner. I then restored a 1.29 base nandroid and proceeded to take all the ota updates for my 02___001 cid. So this would have flashed stock Rom, stock recovery and stock hboot yes? So going to s on should work yes?

stovie_steve said:
Many thanks for replying
I originally downgraded my hboot to 1.44 after getting s off with rumrunner. I then restored a 1.29 base nandroid and proceeded to take all the ota updates for my 02___001 cid. So this would have flashed stock Rom, stock recovery and stock hboot yes? So going to s on should work yes?
Click to expand...
Click to collapse
yes it should work without any issue

It didn't work!
When I reboot my phone I got a message saying tampered detected - rebooting
Now my phone reads locked, tampered and s-on

stovie_steve said:
It didn't work!
When I reboot my phone I got a message saying tampered detected - rebooting
Now my phone reads locked, tampered and s-on
Click to expand...
Click to collapse
you should never have gone back to s-on, the only way to get rid of the tampered is to run a RUU, now you are s-on you will no longer be able to do this. so you will be stuck now with what you have I believe, you can remove tampered but you need to be s-off to run code.
sorry, believe you are stuck where you are.

scifitrekkie said:
you should never have gone back to s-on, the only way to get rid of the tampered is to run a RUU, now you are s-on you will no longer be able to do this. so you will be stuck now with what you have I believe, you can remove tampered but you need to be s-off to run code.
sorry, believe you are stuck where you are.
Click to expand...
Click to collapse
No I am not stuck where I am - I can unlock the bootloader again via HTC dev, install custom recovery and do a Guru reset to achieve S-off again. I've done this before.
I can get s-off again and I have a RUU for a stock european firmware. I can change my CID for HTC__001 and update right up to 3.62.401.1 firmware. That'll put my device to complete stock
Do HTC know that my device was originally locked to O2-UK?
If so, will o2 care that my phone is s-off? Cos I can get s-off and leave the bootloader locked

[Q] HTC One stuck in white starting screen

Hi!
My brother tried to update the latest update for his HTC One and at some point it restarted and is now stuck in the white starting screen.
It's stock, I just unlocked the bootloader, but apart from that I would like to not root the phone.
I tried several things - I can get into the bootloader and also into fastboot, I did a factory reset and wiped the cache, nothing helped.
For some reason I can't do some things through fastboot, if I try for example to do "fastboot continue" I get "resuming boot... FAILED (remote: not allowed)".
Here is the bootloader information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.206.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also, I'm using Mac.
If you need anymore information led me know and I will try to provide them.
Can anyone help?

Never post your IMEI and Serial Number.

khandelwalsiddharth said:
Never post your IMEI and Serial Number.
Click to expand...
Click to collapse
Thanks for the advice, edited them out!

I'm not too familiar with restoring a stock phone, but I would try running an RUU.
As you phone is stock anyway you should only need to run the RUU.exe.
I would try following this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
You might need to gain S-OFF to then downgrade your HBOOT version for some RUUs to work.

JasSingh93 said:
I'm not too familiar with restoring a stock phone, but I would try running an RUU.
As you phone is stock anyway you should only need to run the RUU.exe.
I would try following this guide:
http://forum.xda-developers.com/showthread.php?t=2541082
You might need to gain S-OFF to then downgrade your HBOOT version for some RUUs to work.
Click to expand...
Click to collapse
The problem with running an RUU is that there isn't one for this version.
It's a O2 Germany, with the cidnum: O2___102 - I googled a lot, but I couldn't find a RUU for this, only a nandroid backup, which I can't use because I haven't CWM or a different CR.
Also to get S-OFF I need to root the phone which I didn't want to do.
Problem is solved anyways, my brother brought the phone to the store to get it fixed - let's hope he doesn't have to pay because I unlocked the HBOOT.
Thanks for your help!

ClouDtheStrifE said:
The problem with running an RUU is that there isn't one for this version.
It's a O2 Germany, with the cidnum: O2___102 - I googled a lot, but I couldn't find a RUU for this, only a nandroid backup, which I can't use because I haven't CWM or a different CR.
Also to get S-OFF I need to root the phone which I didn't want to do.
Problem is solved anyways, my brother brought the phone to the store to get it fixed - let's hope he doesn't have to pay because I unlocked the HBOOT.
Thanks for your help!
Click to expand...
Click to collapse
Shouldn't have to pay, I know all this thing about warranty voiding if you unlock the boot loader, but i've never had this issue or know anyone that has. My brother took his HTC back as the USB port became loose and developed a faulty connection, fully rooted, s-off and unlock boot loader!
They fixed it no questions asked, only they did flash an RUU so the phone was s-on and locked again.
Should be fine

[SOLVED] HTC One Debranding

I just bought an HTC One which is unlocked but it shows the O2 bootscreen. I wish to debrand the phone but will that lock the phone? I am not sure how the phone was unlocked by the previous user. Thanks

Klejdi90 said:
I just bought an HTC One which is unlocked but it shows the O2 bootscreen. I wish to debrand the phone but will that lock the phone? I am not sure how the phone was unlocked by the previous user. Thanks
Click to expand...
Click to collapse
No it will not lock the phone, unless you want it locked. Post a fastboot getvar all except remove the imei and serialno and we will be able to direct you how to rebrand your phone.

Klejdi90 said:
I just bought an HTC One which is unlocked but it shows the O2 bootscreen. I wish to debrand the phone but will that lock the phone? I am not sure how the phone was unlocked by the previous user. Thanks
Click to expand...
Click to collapse
Install a custom ROM.

SaHiLzZ said:
Install a custom ROM.
Click to expand...
Click to collapse
I wish to install a stock htc rom with ota can I do this without losing the unlock?

Klejdi90 said:
I wish to install a stock htc rom with ota can I do this without losing the unlock?
Click to expand...
Click to collapse
I dont know if you are talking about sim unlock or bootloader unlock but anyway, both sim and bootloader will stay unlocked even if you flash another rom or if you debrand the phone.

I see
@alray Yeah I mean sim unlock, Can you post a link of a guide to install stock htc rom to debrand. Will I be able to get OTA updates? What steps are needed Unlock bootloader, s-off, change cid custom recovery and install rom? Can you link me to a stock rom with ota for europe or international version. I had a look at the first link in your sig but its kinda confusing.
@nkk71 can you help?
I did a fastboot getvar all and here it is;
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.187s

Klejdi90 said:
@alray Yeah I mean sim unlock, Can you post a link of a guide to install stock htc rom to debrand. Will I be able to get OTA updates? What steps are needed Unlock bootloader, s-off, change cid custom recovery and install rom? Can you link me to a stock rom with ota for europe or international version. I had a look at the first link in your sig but its kinda confusing.
@nkk71 can you help?
I did a fastboot getvar all and here it is;
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.187s
Click to expand...
Click to collapse
If you want a full conversion, you can s-off the phone, change cid to HTC__001 and flash a x.xx.401.x RUU. Your best option to s-off on hboot 1.57 is probably sunshine s-off but its a paid exploit (25 USD) or you can try firewater, its free but it will require more steps and you have like 50% chance it will not work.
or the easier way, if you only want a debranded rom, you could only unlock the bootloader, flash twrp 2.6.3.3 and then flash a rom (like arhd 71.1)

alray said:
If you want a full conversion, you can s-off the phone, change cid to HTC__001 and flash a x.xx.401.x RUU. Your best option to s-off on hboot 1.57 is probably sunshine s-off but its a paid exploit (25 USD) or you can try firewater, its free but it will require more steps and you have like 50% chance it will not work.
or the easier way, if you only want a debranded rom, you could only unlock the bootloader, flash twrp 2.6.3.3 and then flash a rom (like arhd 71.1)
Click to expand...
Click to collapse
@alray Hey I did everything and am now trying to get the right RUU for europe or international. I flashed this : RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe and it seems to be fine except I am still s-off and an for some reason an option while doing the initial wizard called Tell HTC tells me this is a test device so this option will remain on. What is causing this? My device is a test device?! Wrong RUU?
Edit: I am updating the phone but it wont find the latest after every boot it finds the next. Now installing 4.3, it was 4.1.2 to begin with..

Klejdi90 said:
@alray Hey I did everything and am now trying to get the right RUU for europe or international. I flashed this : RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe and it seems to be fine except I am still s-off and an for some reason an option while doing the initial wizard called Tell HTC tells me this is a test device so this option will remain on. What is causing this? My device is a test device?! Wrong RUU?
Edit: I am updating the phone but it wont find the latest after a boot it finds the next? It was 4.1.2 to begin with..
Click to expand...
Click to collapse
Tell HTC/test device is normal. You'll always get this message at the initial setup with s-off phones, don't worry with this.
The ruu will not turn back s-on and thats a good thing. Keep your phone s-off.

alray said:
Tell HTC/test device is normal. You'll always get this message at the initial setup with s-off phones, don't worry with this.
The ruu will not turn back s-on and thats a good thing. Keep your phone s-off.
Click to expand...
Click to collapse
Yeah I thought it was the s-off causing this. Thanks for you reply, gonna install update after update and see if it comes up with the latest. Bit strange it doesn't install the absolute latest, but I guess the final update size would be huge to have all the fixes in previous versions in one.

Klejdi90 said:
Yeah I thought it was the s-off causing this. Thanks for you reply, gonna install update after update and see if it comes up with the latest. Bit strange it doesn't install the absolute latest, but I guess the final update size would be huge to have all the fixes in previous versions in one.
Click to expand...
Click to collapse
updates must be installed incrementally, don't worry you'll eventually be on the latest version.

alray said:
updates must be installed incrementally, don't worry you'll eventually be on the latest version.
Click to expand...
Click to collapse
Yep installed 4.4.3 just now. Thanks for all your help guys :good: Got me a debranded HTC One now. Hated the O2 bootscreen :silly:

[SOLVED] at&t m7 relocked, s-on, tempered, security warning

To begin with, I'm not a very smart man. Some would call me an idiot. I started clicking things and I'm afraid I screwed up my phone
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

ajr901 said:
To begin with, I'm not a very smart man. Some would call me an idiot. I started clicking things and I'm afraid I screwed up my phone
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Try a different RUU like this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3_radio_4a-19-3263-13_10-38j-1157-04_release_334235_signed_2-exe/ In the future, don't use toolkits it is easy to lose track of what is really happening to your phone with them. It is better to stick with the raw commands of fastboot and adb. Use this tool to install them and most sites will give you the appropriate commands to perform the various tasks.

Try a different RUU like this one: http://www.htc1guru.com/dld/ruu_m7_u..._signed_2-exe/ In the future, don't use toolkits it is easy to lose track of what is really happening to your phone with them. It is better to stick with the raw commands of fastboot and adb. Use this tool to install them and most sites will give you the appropriate commands to perform the various tasks.
Click to expand...
Click to collapse
Holy **** you are the man! That worked! How did you know that was going to work?!?!
Thank you soooooo much! I love you. I owe you one.

HTC One M7 GPE won't update from Jellybean

I have an HTC One M7 Google Play Edition running Jellybean (4.2.2). This lags well behind the current version of android for this version of the phone. Unfortunately, I am unable to receive an OTA update (everytime I check, I get a message stating that my phone is up to date). Is there anything I can do to force an OTA update short of rooting the device and manually installing the updates? I am currently on a BYOD plan with T-Mobile if that matters at all.

nocipher said:
I have an HTC One M7 Google Play Edition running Jellybean (4.2.2). This lags well behind the current version of android for this version of the phone. Unfortunately, I am unable to receive an OTA update (everytime I check, I get a message stating that my phone is up to date). Is there anything I can do to force an OTA update short of rooting the device and manually installing the updates? I am currently on a BYOD plan with T-Mobile if that matters at all.
Click to expand...
Click to collapse
Can you please post the output of "fastboot getvar all" (remove your imei and serialno information before posting).

alray said:
Can you please post the output of "fastboot getvar all" (remove your imei and serialno information before posting).
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.176s

nocipher said:
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.176s
Click to expand...
Click to collapse
Everything looks good. Is your bootloader locked/unlock/relocked?
You could use a RUU to update your phone, flashing a ruu will wipe everything from the phone, like if it was brand new. Backup your important files before.
If you ever considered S-OFF for your phone, better to do it before updating using rumrunner exploit for free. If you update to the latest version, you will need to use Sunshine s-off which cost 25$.

alray said:
Everything looks good. Is your bootloader locked/unlock/relocked?
You could use a RUU to update your phone, flashing a ruu will wipe everything from the phone, like if it was brand new. Backup your important files before.
If you ever considered S-OFF for your phone, better to do it before updating using rumrunner exploit for free. If you update to the latest version, you will need to use Sunshine s-off which cost 25$.
Click to expand...
Click to collapse
My bootloader is locked. (I pulled the phone out of the unopened box just yesterday).
I tried to get S-OFF using rumrunner so I could update using the HBOOT recovery feature, but there was an issue with my phone not being rooted or something along those lines. Maybe the failure was due to a locked bootloader? (I'm new to all of this.)
If I set my phone to S-OFF, would it be better to just manually apply the updates or use an RUU?

nocipher said:
My bootloader is locked. (I pulled the phone out of the unopened box just yesterday).
I tried to get S-OFF using rumrunner so I could update using the HBOOT recovery feature, but there was an issue with my phone not being rooted or something along those lines. Maybe the failure was due to a locked bootloader? (I'm new to all of this.)
If I set my phone to S-OFF, would it be better to just manually apply the updates or use an RUU?
Click to expand...
Click to collapse
Achieving s-off requires root. Root requires a custom recovery, Custom recovery requires an unlocked bootloader.
Unlocking the bootloader will void your warranty if you have one.
S-OFF is not something everyone needs but its very useful when you have to flash files in case the phone is somehow bricked. If you are not planning to flash custom roms or any other custom files I would recommend staying S-ON. In the worst case, you'll have to pay 25$ for s-off if you really need it later.
better to use the RUU to update the phone imo, much faster than applying all ota updates from your current version. The only downside of using a ruu is that it will wipe your phone data (which shouldn't be a big issue since your phone is 1 day old). Much convenient to update using ota update after so you'll not have to deal with the wipe each time.

alray said:
Achieving s-off requires root. Root requires a custom recovery, Custom recovery requires an unlocked bootloader.
Unlocking the bootloader will void your warranty if you have one.
S-OFF is not something everyone needs but its very useful when you have to flash files in case the phone is somehow bricked. If you are not planning to flash custom roms or any other custom files I would recommend staying S-ON. In the worst case, you'll have to pay 25$ for s-off if you really need it later.
better to use the RUU to update the phone imo, much faster than applying all ota updates from your current version. The only downside of using a ruu is that it will wipe your phone data (which shouldn't be a big issue since your phone is 1 day old). Much convenient to update using ota update after so you'll not have to deal with the wipe each time.
Click to expand...
Click to collapse
I am having trouble finding an RUU for the google play edition. I've been googling and searching the forums for a while now, but most of the RUU's and ROMs I find are for the Sense version. Would the RUU here: http://forum.xda-developers.com/showthread.php?t=2358781 work?

nocipher said:
I am having trouble finding an RUU for the google play edition. I've been googling and searching the forums for a while now, but most of the RUU's and ROMs I find are for the Sense version. Would the RUU here: http://forum.xda-developers.com/showthread.php?t=2358781 work?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B17smFr95pleX29Wamg2c3pRWTQ/view?pli=1

Thanks for the all the help! I used the RUU to update to 5.0.1. That, unfortunately, did not allow an OTA update directly, but I did manage to sideload the 5.1 update via abd.