Database Develop

[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

[Q] HTC One Bricked, Relocked, Tampered, S-ON, No operating system

Hello, I have a very big problem with my HTC One M7, it's bricked. It's with Hboot 1.57, tampered , relocked, No recovery, no rom and s-on.
I tried to flash a stock RUU.exe
For flashing it I had to lock the bootloader. So I run the ruu.exe and it deleted all from my phone and stuck on "Cheking header - 5%). When I rebooted the phone it was only with bootloader and everything else was wiped.
I tried to unlock it again but after unlocking i tries to get to recovery. But I don't have recovery. If I try to flash a recovery the phone should be unocked. I'm in a circle.
Please help me with this issue. I want to get back with working phone.
I have read all the threads in the forum about bicked htc one m7 but nothing helped me.
Here's my getvar all
C:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

zHi5k0 said:
Hello, I have a very big problem with my HTC One M7, it's bricked. It's with Hboot 1.57, tampered , relocked, No recovery, no rom and s-on.
I tried to flash a stock RUU.exe
For flashing it I had to lock the bootloader. So I run the ruu.exe and it deleted all from my phone and stuck on "Cheking header - 5%). When I rebooted the phone it was only with bootloader and everything else was wiped.
I tried to unlock it again but after unlocking i tries to get to recovery. But I don't have recovery. If I try to flash a recovery the phone should be unocked. I'm in a circle.
Please help me with this issue. I want to get back with working phone.
I have read all the threads in the forum about bicked htc one m7 but nothing helped me.
Here's my getvar all
C:\HTC>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4280mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
unlock the bootloader
flash a custom recovery (twrp 2.6.3.3 preferred)
push a custom rom or a stock reset rom (that match your version) to your phone storage using adb sideload or adb push
install the rom using twrp.

zHi5k0 said:
Hello, I have a very big problem with my HTC One M7, it's bricked. It's with Hboot 1.57, tampered , relocked, No recovery, no rom and s-on.
I tried to flash a stock RUU.exe
For flashing it I had to lock the bootloader. So I run the ruu.exe and it deleted all from my phone and stuck on "Cheking header - 5%). When I rebooted the phone it was only with.....
C:\HTC>fastboot getvar all
(bootloader) version-main:
Click to expand...
Click to collapse
Cheking header - 5% problem is because of version main not found
if you remember exact version then flash same firmware then Run RUU

yatindroid said:
Cheking header - 5% problem is because of version main not found
if you remember exact version then flash same firmware then Run RUU
Click to expand...
Click to collapse
But anyway there is no RUU available that can be used on 1.57 Hboot, S-on and CID HTC__032. So at this point he can only flash a rom using a custom recovery

alray said:
But anyway there is no RUU available that can be used on 1.57 Hboot, S-on and CID HTC__032. So at this point he can only flash a rom using a custom recovery
Click to expand...
Click to collapse
Ohhh Sorry I not noticed that just focused on He was trying flash ruu

The problem is solved Thanks for your help

Help me please
zHi5k0 said:
The problem is solved Thanks for your help
Click to expand...
Click to collapse
Hello, fried. Could you explain or contact me how do you solved this problem? I have the same :crying:

eaeguu said:
Hello, fried. Could you explain or contact me how do you solved this problem? I have the same :crying:
Click to expand...
Click to collapse
Excuse me for the late reply. I'm posting the post that helped me:
Use this recovery
http://techerrata.com/file/twrp2/m7/...2.6.3.3-m7.img
Download and put the file in your fastboot folder rename it recovery.img and use these commands to flash the recovery.
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu to boot TWRP Recovery
Put the stock Rom zip in your fastboot folder and rename it rom.zip
While on the TWRP home screen connect your usb cable. In the command window type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push is complete (Several Minutes) When its done Install the Rom with TWRP recovery.
When its done Reboot system the device should boot as normal.

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.

Black/White Screen and freeze boot up after OTA

Hi guys i had problem, few days ago phone notify me about update, i thought ok it nice, I restored stock recovery and I relocked bootloader in fastboot.
I clicked the install , process ran without errors. in stock recovery and BANG 3-4 first times phone stopped on boot, i tried factory reset after boot phone giving me black screen, next I tried to flash RUU's.
Before update a I had 7.19.401.22, i flashed this version - not working, flashed 7.19.401.2 - not working, flashed 7.19.401.30 - not working although it ,the same version is after update.
I don't know what to do :crying:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37RW902282
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flashed RUU's
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip

Jakqa said:
Hi guys i had problem, few days ago phone notify me about update, i thought ok it nice, I restored stock recovery and I relocked bootloader in fastboot.
I clicked the install , process ran without errors. in stock recovery and BANG 3-4 first times phone stopped on boot, i tried factory reset after boot phone giving me black screen, next I tried to flash RUU's.
Before update a I had 7.19.401.22, i flashed this version - not working, flashed 7.19.401.2 - not working, flashed 7.19.401.30 - not working although it ,the same version is after update.
I don't know what to do :crying:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37RW902282
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flashed RUU's
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Click to expand...
Click to collapse
The ota caused a bootloop because you have installed it on a rooted phone. Unlike older updates (6.xx.xxx.x and before), you can't simply reflash the stock recovery to update. Lollipop updates can only be installed on 100% stock and non-rooted rom. That wasn't a problem in the past but its now a well know problem with all newer updates.
Your version-main is now 7.19.401.30 because, unlike the software, the firmware updated fine. You can't flash the 7.19.401.22 RUU because its now a downgrade in version (because your firmware got updated). Downgrading using a RUU requires S-OFF, your phone is S-ON. Same reason why the 7.19.401.2 won't work.
7.19.401.30 ruu is a "combined" RUU so it can't be flashed on a s-on phone.
Your option are:
unlock the bootloader, flash twrp recovery and flash a rom
or achieve s-off using sunshine and flash the .22 or the .30 ruu (you'll need to do option 1 first because you need a working rom to be able to s-off the phone)
Or maybe someone already uploaded a nandroid backup of 7.19.401.30. If you find one you can restore the backup using a custom recovery and then reflash the stock recovery.

alray said:
The ota caused a bootloop because you have installed it on a rooted phone. Unlike older updates (6.xx.xxx.x and before), you can't simply reflash the stock recovery to update. Lollipop updates can only be installed on 100% stock and non-rooted rom. That wasn't a problem in the past but its now a well know problem with all newer updates.
Your version-main is now 7.19.401.30 because, unlike the software, the firmware updated fine. You can't flash the 7.19.401.22 RUU because its now a downgrade in version (because your firmware got updated). Downgrading using a RUU requires S-OFF, your phone is S-ON. Same reason why the 7.19.401.2 won't work.
7.19.401.30 ruu is a "combined" RUU so it can't be flashed on a s-on phone.
Your option are:
unlock the bootloader, flash twrp recovery and flash a rom
or achieve s-off using sunshine and flash the .22 or the .30 ruu (you'll need to do option 1 first because you need a working rom to be able to s-off the phone)
Or maybe someone already uploaded a nandroid backup of 7.19.401.30. If you find one you can restore the backup using a custom recovery and then reflash the stock recovery.
Click to expand...
Click to collapse
1.What Kind of rom? Stock or custom - without s-off?
3.Do You know anyone who could upload a backup of 7.19.401.30?

Jakqa said:
1.What Kind of rom? Stock or custom - without s-off?
3.Do You know anyone who could upload a backup of 7.19.401.30?
Click to expand...
Click to collapse
1.a stock or stockish rom is best if you want to achieve s-off, You don't need s-off to flash a custom rom, only an unlocked bootloader + a custom recovery.
3. No, might want to ask in the update thread in the general section (see sticky threads)