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] S-OFF a GPE Phone

I have a genuine Htc One Google Play Edition Phone.
Get Vars :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(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: 3992mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
Phone was unlocked (fastboot oem unlock) and rooted 2 months ago.
Now I messed things up by trying to install the 4.4 OTA using TWRP. With the OTA, I get a nice blue-screen. I had a backup so the phone is booting correctly now.
I want to install a factory image. From what I can gather, this is not like a Nexus phone and I cannot simply use fastboot to get back to stock. I must use RUU. Now : for RUU to work, I need to be S-OFF.
I searched a lot and there does not seem to be a way to put a GPE to SOFF. I tried RumRunners but it fails saying I'm not rooted (which is wrong since I'm rooted) and I'm not running an unsecure kernel (which is true). - again, this is a factory GPE HTC One.. unlocked and rooted. That is all.
So, am I missing something? I'm running HBOOT 1.54. Can I get this phone to turn the security off?

Whatever you do, do NOT lock the boot loader. Can NOT unlock boot loader, otherwise.

deleted

SaHiLzZ said:
Whatever you do, do NOT lock the boot loader. Can NOT unlock boot loader, otherwise.
Click to expand...
Click to collapse
Yeah, I figured that much.
I was finally able to update to 4.4. I simply flashed the stock recovery and it worked.. BUT now my phone boot loops!

Restore your nandroid. Or issue fastboot erase cache and do a factory rest from bootloader.

"fastboot erase cache" is the first thing I did. That's the thing : all the recoveries I try boot loop. The only one working is the stock one! With the stock one I sis a factory reset. Still no go.

[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] Rooting after 5.03.651.3 OTA Update Questions

Sprint HTC ONE
Background:
Just spent the last 15 hours flashing back to 4.06.651.4 stock rom in order to take the new OTA update 5.03.651.3. Somehow I managed to brick my phone to where it would only stay stuck on the green HTC with white background. The only thing that I was able to get to work was booting into the bootloader and play with fastboot commands. I had CWM recovery installed but could never get adb to discover the phone to sideload a rom onto the memory card. I had no backup, and pretty much had everything wiped and formatted on the phone. I went througt installing back and fourth twrp, cwm, and different stock recoveries, and hours of trying different things to no avail. What got my phone back up and going was at some point changing my cid to 11111111(not sure if this did anything for me), flashing 4.06.651.4_firmware.zip, then running Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip (ARUWizard.exe) while in fastboot oem rebootRUU mode. Since then I have installed the 4.06.651.9 OTA and then the 5.03.651.3 OTA which is where I stand at this point.
That being said, here's the state of my phone currently:
No Root
CID: 11111111 ( I don't remember what it should say incase I need to warranty the phone)
S-off
bootloader unlocked (did lock it but found out I didn't have to since I was s-off and since then unlocked)
hboot went from 1.56 to 1.57
___________________________________________
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35RS900979
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now this here are my questions.
Can I gain Root on being on 5.03.651.3?
If I have to reinstall a custom recovery to gain root, would I be able to flash back to the current stock recovery?
Having the new ver. of hboot 1.57, would I be able to downgrade back to 1.56 using the 4.06.651.4_firmware.zip, to flash back to stock 4.06.651.4 if I want to factory reset and unroot, s-on, and lock the bootloader if necessary?
And last of all what should the CID show from factory on the new OTA?
Basically what I want is to have factory everything rooted so I can get rid of the bloatware. Nice and simple that's all.
Much appreciated!!!

Rare5spd said:
Sprint HTC ONE
Background:
Just spent the last 15 hours flashing back to 4.06.651.4 stock rom in order to take the new OTA update 5.03.651.3. Somehow I managed to brick my phone to where it would only stay stuck on the green HTC with white background. The only thing that I was able to get to work was booting into the bootloader and play with fastboot commands. I had CWM recovery installed but could never get adb to discover the phone to sideload a rom onto the memory card. I had no backup, and pretty much had everything wiped and formatted on the phone. I went througt installing back and fourth twrp, cwm, and different stock recoveries, and hours of trying different things to no avail. What got my phone back up and going was at some point changing my cid to 11111111(not sure if this did anything for me), flashing 4.06.651.4_firmware.zip, then running Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip (ARUWizard.exe) while in fastboot oem rebootRUU mode. Since then I have installed the 4.06.651.9 OTA and then the 5.03.651.3 OTA which is where I stand at this point.
That being said, here's the state of my phone currently:
No Root
CID: 11111111 ( I don't remember what it should say incase I need to warranty the phone)
S-off
bootloader unlocked (did lock it but found out I didn't have to since I was s-off and since then unlocked)
hboot went from 1.56 to 1.57
___________________________________________
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35RS900979
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now this here are my questions.
1. Can I gain Root on being on 5.03.651.3?
2. If I have to reinstall a custom recovery to gain root, would I be able to flash back to the current stock recovery?
3. Having the new ver. of hboot 1.57, would I be able to downgrade back to 1.56 using the 4.06.651.4_firmware.zip, to flash back to stock 4.06.651.4 if I want to factory reset and unroot, s-on, and lock the bootloader if necessary?
And last of all what should the CID show from factory on the new OTA?
Basically what I want is to have factory everything rooted so I can get rid of the bloatware. Nice and simple that's all.
Much appreciated!!!
Click to expand...
Click to collapse
Alright, so answering your questions:
1. Yes you can get root being on 5.03.651.3.
2. 99% sure you can't, unless you RUU; but if you RUU you completely lose everything including root.
3. Yeah you can if you're S-OFF.
ROOTING INSTRUCTIONS:
http://download.chainfire.eu/450/SuperSU/UPDATE-SuperSU-v2.00.zip
Try downloading that file and then flashing it in TWRP. I haven't tested this though as the ROM that I'm using is prerooted.
There's a video by fellow member @zedomax that tells you how to do this, although the SuperSU zip in his video is outdated as the video's made in 2013 , so I linked you the latest one above.
EDIT: Oh and the factory CID for the Sprint HTC One is SPCS_001.

Thank you for taking the time to reply to my thread and answering all of my questions. I will try rooting when I get home tonight. Thanks again!!!

Rare5spd said:
Thank you for taking the time to reply to my thread and answering all of my questions. I will try rooting when I get home tonight. Thanks again!!!
Click to expand...
Click to collapse
You could also use these commands if you are S-off
fastboot oem rebootRUU
fastboot flash zip recovery.zip
fastboot reboot
this could flash a recovery since you are S-off and flash back your stock recovery... Make sure you include an android-info.txt file...
In the android-info.txt file include this:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
with that txt file and a recovery be it stock or a custom you can do what you like.

StormyNight said:
Alright, so answering your questions:
1. Yes you can get root being on 5.03.651.3.
2. 99% sure you can't, unless you RUU; but if you RUU you completely lose everything including root.
3. Yeah you can if you're S-OFF.
Click to expand...
Click to collapse
In reference to your answer on #2, Why can't you flash back to current stock recovery?
I'm curious to know because, i'm stocked ROM rooted, TRWP (lastest version), s-On. and i've been updating my firmware OTA.
I download the OTA firmware then flashboot stock recovery, reboot phone and perform the update. Once it's done, i then flashboot custom recovery (TWRP) and flash SuperSU to gain root again. The firmware version I"m on now is 5.03.651.3.
So basically, i'm concerned that i won't be able to flash stock recovery whenever the next firmware update occurs, using the method i've just described.

The Glow said:
In reference to your answer on #2, Why can't you flash back to current stock recovery?
I'm curious to know because, i'm stocked ROM rooted, TRWP (lastest version), s-On. and i've been updating my firmware OTA.
I download the OTA firmware then flashboot stock recovery, reboot phone and perform the update. Once it's done, i then flashboot custom recovery (TWRP) and flash SuperSU to gain root again. The firmware version I"m on now is 5.03.651.3.
So basically, i'm concerned that i won't be able to flash stock recovery whenever the next firmware update occurs, using the method i've just described.
Click to expand...
Click to collapse
Huh, didn't know that. My apologies. By the way, you still be able to do it even when the next firmware update occurs.

Yesterday i tried to update my phone without success
fisrt i tried to install roms but it didnt work
then i tried to update my main version and fail also
then i dont know why i change mi CID number to HTC__001
it started to brick the screen turn gray but i solved it i don´t know how
but i noticed my phone changed to S-ON
i tried many times with many ruus to restore but i can´nt Problems CID and 152 images i locked before doing this
i insert a rom with the same rom 5.03.651.3 success at installing
it started good still the part i have to write language it stayed in HTC logo and then restart
Now im trying to get S-OFF and change my CID to another number but i don´t know wich
and try RUU again but i can not IT gave error and Rumrunner adb didnt find my device
i don´t know what else to do im also 2 days awake :crying:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA358S900105
(bootloader) imei: 99*****************
(bootloader) meid: 99***************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
PS sorry im not a native english speaker. try to understand me
i can understand english very well
THANX ALL OF YOU

HTC One M7 trying to return to stock to allow me to network unlock the phone

I have a HTC One M7 on EE that is no longer used at work and thought I would snaffle it to use at home, I got the network unlock code from EE and tried to apply it and found it didn't work, on digging about I assume it doesn't work as the phone has been updated to Android 5.1 Google Play Edition Kernel Version 3.4.10-ge0627be so it now has the wrong modelid and cidnum. I didn't update it originally and don't know its history I have just picked it up as it was going spare.
So I thought no problem I will just put it back to a stock rom and run the network unlock again, I don't really like the 5.1 GPE anyway and would prefer it on Lollipop 5.02.
This was some 8 hours ago and I have tried everything and I cannot unlock the bootloader (Its relocked), whatever I try just does nothing, the Recovery doesn't work I just get the red triangle, I have tried a stock Guru RUU but this wont work as I assume it now has the incorrect modelid and cidnum, I am just going round and round in circles. I cannot change the modelid as I cannot unlock it
This is the getvar all for the phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(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-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
Am I on a hiding to nothing or should I be able to reverse it back to stock to network unlock it ?
Info on the recovery screen as follows
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.36.3218.06
Open DSP-v34.120.274.0429
OS-6.04.1700.6
eMMC-boot 2048MB
Apr 28 2015,09:16:24:0
Can anyone point me in the right direction of show me the error of my ways before it drives me crazy.
Thanks Sean

Sean1971 said:
I have a HTC One M7 on EE that is no longer used at work and thought I would snaffle it to use at home, I got the network unlock code from EE and tried to apply it and found it didn't work, on digging about I assume it doesn't work as the phone has been updated to Android 5.1 Google Play Edition Kernel Version 3.4.10-ge0627be so it now has the wrong modelid and cidnum. I didn't update it originally and don't know its history I have just picked it up as it was going spare.
So I thought no problem I will just put it back to a stock rom and run the network unlock again, I don't really like the 5.1 GPE anyway and would prefer it on Lollipop 5.02.
This was some 8 hours ago and I have tried everything and I cannot unlock the bootloader (Its relocked), whatever I try just does nothing, the Recovery doesn't work I just get the red triangle, I have tried a stock Guru RUU but this wont work as I assume it now has the incorrect modelid and cidnum, I am just going round and round in circles. I cannot change the modelid as I cannot unlock it
This is the getvar all for the phone
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.36.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.04.1700.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(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-0ddc65a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.042s
Am I on a hiding to nothing or should I be able to reverse it back to stock to network unlock it ?
Info on the recovery screen as follows
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.36.3218.06
Open DSP-v34.120.274.0429
OS-6.04.1700.6
eMMC-boot 2048MB
Apr 28 2015,09:16:24:0
Can anyone point me in the right direction of show me the error of my ways before it drives me crazy.
Thanks Sean
Click to expand...
Click to collapse
You'll need s-off to unlock the bootloader since there is an issue with bootloader unlock on GPE (both htcdev.com and fastboot oem unlock method doesn't work).
Use Sunshine s-off to s-off and unlock the bootloader

alray said:
You'll need s-off to unlock the bootloader since there is an issue with bootloader unlock on GPE (both htcdev.com and fastboot oem unlock method doesn't work).
Use Sunshine s-off to s-off and unlock the bootloader
Click to expand...
Click to collapse
Great thanks for your help, I will give that a try today.

Sorry me again, Sunshine passes the pre checks apart from it reports my phone is not rooted. I cannot run SuperSU Installer to root the device because, recovery doesn't work and whatever I try to get TWRP on the phone fails. I just seem to be going round in circles. When I Fastboot Flash Recovery the TWRP img file it says its copied the correct file size but I don't get the finished okay message just a fail.
I didn't put the 5.1 GPE on the phone, is it normal for the phone to be relocked and S-On after putting on the 3.4.10-ge0627be 5.1 GPE rom on the phone ?
Any advice welcomed as I am well out of my depth with this.

Sean1971 said:
Sorry me again, Sunshine passes the pre checks apart from it reports my phone is not rooted. I cannot run SuperSU Installer to root the device because, recovery doesn't work and whatever I try to get TWRP on the phone fails. I just seem to be going round in circles. When I Fastboot Flash Recovery the TWRP img file it says its copied the correct file size but I don't get the finished okay message just a fail.
I didn't put the 5.1 GPE on the phone, is it normal for the phone to be relocked and S-On after putting on the 3.4.10-ge0627be 5.1 GPE rom on the phone ?
Any advice welcomed as I am well out of my depth with this.
Click to expand...
Click to collapse
You can't flash a custom recovery, your bootloader is locked...!
Try to achieve temp root so you can use sunshine like they do in the verizon htc one forum.

alray said:
You can't flash a custom recovery, your bootloader is locked...!
Try to achieve temp root so you can use sunshine like they do in the verizon htc one forum.
Click to expand...
Click to collapse
Thanks for your help, really appreciate it. See I said I was out of my depth ....
I tried Toweroot and that wouldn't work for my device, so then tried Kingroot and that sorted it so I was able to run Sunshine and I now have it S-OFF and Unlocked, I can now try to get it back to stock and get it network unlocked.