Database Develop

HTC One Developer Edition: WiFi and Bluetooth fail

Hello friends. First of all, I apologize if I am not very clear, but I have little knowledge of English, and to be faster I'll use a translator...
Since about a week ago, my HTC One Developer Edition is showing me errors with WiFi and Bluetooth. These are off steadily even when in use. At first I thought it was a failure of the last installed ROM (ARHD 40.1), but I've tried others such as CM11 without installing any mod and restore my latest nandroid backup, but I have had the same result.
Apart from changing the ROM all I remember doing is to update the firmware, so yesterday I upgraded to the new firmware version to see if solved, but still follows the failure. Do not think it's a hardware failure because the mobile is not second hand, has not suffered any drop and was always working perfectly, so I ask your help and attached the information that shows the phone using fastboot getvar all command if serving them for a diagnosis. Thanks in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3993mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s

You are Soff. Why not reflash official dev ruu?

SaHiLzZ said:
You are Soff. Why not reflash official dev ruu?
Click to expand...
Click to collapse
What should I use? Because I see several for Dev Edition on this list:
[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads

[email protected] said:
What should I use? Because I see several for Dev Edition on this list:
[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads
Click to expand...
Click to collapse
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!

nkk71 said:
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
Click to expand...
Click to collapse
Well, thank you very much. Be right back after process.

SaHiLzZ said:
You are Soff. Why not reflash official dev ruu?
Click to expand...
Click to collapse
nkk71 said:
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
Click to expand...
Click to collapse
I downgrade to hboot 1.44 and reflash the official ruu (RUU M7 JB UL 50 BrightstarUS WWE 1.29.1540.16), but still blinking on and off wifi and bluetooth.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3994mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.065s

Time to call HTC for warranty support. No other ideas.

Hey this is off topic but SaHiLzZ, is your name Sahil?
Sent from my HTC_PN071 using Tapatalk

SaHiLzZ said:
Time to call HTC for warranty support. No other ideas.
Click to expand...
Click to collapse
Well, I bought this phone in the United States.... I live in Dominican Republic...

@SaHiLzZ @nkk71 I was using the bluetooth headphones faultlessly for more than 4 hours, and when I get home WiFi even longer, so I know that still work but are turned on and off when it wants ...

[email protected] said:
@SaHiLzZ @nkk71 I was using the bluetooth headphones faultlessly for more than 4 hours, and when I get home WiFi even longer, so I know that still work but are turned on and off when it wants ...
Click to expand...
Click to collapse
did u try changing some of the advanced settings i mentioned?

nkk71 said:
did u try changing some of the advanced settings i mentioned?
Click to expand...
Click to collapse
Yes, but I don't see changes. (Later, I change the "Keep WiFi on during idle" to Always), but just keeps running and then switching off when it want, and when it goes off, just says "activating", infinite loop until I restart.. Same for bluetooth.

SaHiLzZ said:
Time to call HTC for warranty support. No other ideas.
Click to expand...
Click to collapse
@nkk71
Well, without ideas, I sent the phone to HTC America, for guarantee. I had to pay $ 70 shipping because I live in Dominican Republic (No HTC), but after 15 days I received my phone in perfect working (they did not even scratch), and by the way, apparently they changed my camera ... It's not purple! :laugh:
Thanks for all your help friends. :highfive:

[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

[Q] Back to Stock for Bell HTC One

I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.

Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting

kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s

Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature

kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)

kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.

Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now

I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.

Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?

Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.

Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse

As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.

SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.

Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.

SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.

Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!

Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched

ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.

Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s

ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process

[Q]Restore my GPE M7

Hey guys I really need to restore my phone to a stock experience (factory settings, whether it be Sense or GPE) and here is my info:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -----------------------------
(bootloader) imei: ---------------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4155mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My bootloader is unlocked and I know I need to get s-off and Sunshine isn't an option for me. I have tried both Rumrunner and Moonshine and they don't work either. Can someone please help me? If you need any more information, please do ask.
Any help is appreciated. Thanks.

ANDR01DN00B said:
Hey guys I really need to restore my phone to a stock experience (whether it be Sense or GPE) and here is my info:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -----------------------------
(bootloader) imei: ---------------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4155mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My bootloader is unlocked and I know I need to get s-off and Sunshine isn't an option for me. I have tried both Rumrunner and Moonshine and they don't work either. Can someone please help me? If you need any more information, please do ask.
Any help is appreciated. Thanks.
Click to expand...
Click to collapse
can you tell me how you unlocked the bootloader ? was it a simple Fastboot oem unlock ? or something different ?
What custom recovery do you have ?
No matter what DO NOT LOCK the BOOTLOADER !!!! your phone will be Toast for sure if you do !!

clsA said:
can you tell me how you unlocked the bootloader ? was it a simple Fastboot oem unlock ? or something different ?
What custom recovery do you have ?
No matter what DO NOT LOCK the BOOTLOADER !!!! your phone will be Toast for sure if you do !!
Click to expand...
Click to collapse
I have TWRP (2.8.3.0) and yes, I did use the good 'ol fastboot oem unlock
EDIT: forgot to say thanks for the quick response.

ANDR01DN00B said:
I have TWRP (2.8.3.0) and yes, I did use the good 'ol fastboot oem unlock
EDIT: forgot to say thanks for the quick response.
Click to expand...
Click to collapse
You should be able to use any rom you want ... with no s-off you just can't downgrade your firmware or change your CID / MID
This Stock Rom should work fine on your phone >> http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
If you have a problem flash TWRP 2.6.3.3 it works best with ARHD Roms
and Here's the Stock GPe Rom .. it may need s-off not sure on your phone
http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927

clsA said:
You should be able to use any rom you want ... with no s-off you just can't downgrade your firmware or change your CID / MID
This Stock Rom should work fine on your phone >> http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
If you have a problem flash TWRP 2.6.3.3 it works best with ARHD Roms
and Here's the Stock GPe Rom .. it may need s-off not sure on your phone
http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927
Click to expand...
Click to collapse
By stock I meant like full factory settings (I will update the OP)

ANDR01DN00B said:
By stock I meant like full factory settings (I will update the OP)
Click to expand...
Click to collapse
Then all need to do is TWRP / Wipe / Factory Reset
your phone will be back to stock

clsA said:
Then all need to do is TWRP / Wipe / Factory Reset
your phone will be back to stock
Click to expand...
Click to collapse
No like full RUU kind of thing

ANDR01DN00B said:
No like full RUU kind of thing
Click to expand...
Click to collapse
theirs nothing for s-on GPe / factory reset is the same thing

ANDR01DN00B said:
No like full RUU kind of thing
Click to expand...
Click to collapse
As @clsA said unfortunately nothing you can do with s-on. You need s-off to downgrade and there is no ruu for your current version.
You need to get s-off or flash a custom Rom
Do you mind if I ask, did you unlock your bootloader when your device was on Android 4.3 or just recently?

Danny201281 said:
As @clsA said unfortunately nothing you can do with s-on. You need s-off to downgrade and there is no ruu for your current version.
You need to get s-off or flash a custom Rom
Do you mind if I ask, did you unlock your bootloader when your device was on Android 4.3 or just recently?
Click to expand...
Click to collapse
Back on 4.3 yes. But my hboot is 1.54

ANDR01DN00B said:
Back on 4.3 yes. But my hboot is 1.54
Click to expand...
Click to collapse
Yeah sorry, mine and @clsA questions about your unlocking the bootloader were about a different discussion. http://forum.xda-developers.com/showthread.php?p=57932209
As clsA warned, DO NOT relock your bootloader for any reason. You probably won't be able to Unlock it again.

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.