Database Develop

[Q]

I have the following setup:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.16.3250.24
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-OFF
serialno: MEH
imei: MEH
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4324mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
all: Done!
I have been reading around about HBOOT 1.54 and am wondering if anyone can give me a pros and cons list of going from 1.44 to 1.54 would be?
Thanks

incarceration said:
I have the following setup:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.16.3250.24
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-OFF
serialno: MEH
imei: MEH
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4324mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
all: Done!
I have been reading around about HBOOT 1.54 and am wondering if anyone can give me a pros and cons list of going from 1.44 to 1.54 would be?
Thanks
Click to expand...
Click to collapse
you can change your hboot to 1.54 during upgrading your firmware to 2.24(it comes together)
you can find steps there:
http://forum.xda-developers.com/showthread.php?t=2365506
good luck

99piotrek said:
you can change your hboot to 1.54 during upgrading your firmware to 2.24(it comes together)
Click to expand...
Click to collapse
Thanks. But I know how to do it, I'm just wondering if there are any pros or cons of going to the 1.54 HBOOT from 1.44

incarceration said:
Thanks. But I know how to do it, I'm just wondering if there are any pros or cons of going to the 1.54 HBOOT from 1.44
Click to expand...
Click to collapse
I believe the 1.54 cannot be S-OFF'd

killman2659 said:
I believe the 1.54 cannot be S-OFF'd
Click to expand...
Click to collapse
Ah ok. That's what I was looking to confirm.
Do you know anything of an ENG BOOT? Any pros\cons for that?

incarceration said:
Thanks. But I know how to do it, I'm just wondering if there are any pros or cons of going to the 1.54 HBOOT from 1.44
Click to expand...
Click to collapse
The latest firmware brings updated touch screen drivers and a newer radio amongst other things and it's worth flashing for that alone as many feel it makes the device feel that little bit snappier. If you already have s-off then you won't lose that updating the firmware but if you haven't then you will not be able to s-off with hboot 1.54 at the moment so s-off before updating.
However available roms based on 2.24 will run ok on your existing firmware and the radios can be flashed independently so it's not essential to update if you're happy with your current setup.
Regarding the eng hboot I would advise against that as any modified hboot brings with it an increased risk of permanently bricking.
Most say that updating the firmware improves the device but as I say it's not essential at the moment so basically it's your choice.

incarceration said:
Do you know anything of an ENG BOOT? Any pros\cons for that?
Click to expand...
Click to collapse
There is no eng hboot for this phone, at least not one that will boot.
Sent from my Nexus 7 using Tapatalk HD

rider5512 said:
The latest firmware brings updated touch screen drivers and a newer radio amongst other things and it's worth flashing for that alone as many feel it makes the device feel that little bit snappier. If you already have s-off then you won't lose that updating the firmware but if you haven't then you will not be able to s-off with hboot 1.54 at the moment so s-off before updating.
However available roms based on 2.24 will run ok on your existing firmware and the radios can be flashed independently so it's not essential to update if you're happy with your current setup.
Regarding the eng hboot I would advise against that as any modified hboot brings with it an increased risk of permanently bricking.
Most say that updating the firmware improves the device but as I say it's not essential at the moment so basically it's your choice.
Click to expand...
Click to collapse
Thanks a lot for the clarification!
I flashed the "Combo" RUU from this thread (http://forum.xda-developers.com/showthread.php?t=2316726) and removed the HBOOT and Recovery images from them to avoid updating my HBOOT and overwriting my current custom recovery.
Does this still achieve what you noted in the first paragraph of your response? Do I have to update my HBOOT to achieve any other benefits? I guess I'm just trying to get at, what exactly does updating the HBOOT (the phone's bootloader) achieve?
Currently as I see it, I see the "firmware" as something other than the "HBOOT" (the other files within that same "Combo" RUU), correct?

incarceration said:
Thanks a lot for the clarification!
I flashed the "Combo" RUU from this thread (http://forum.xda-developers.com/showthread.php?t=2316726) and removed the HBOOT and Recovery images from them to avoid updating my HBOOT and overwriting my current custom recovery.
Does this still achieve what you noted in the first paragraph of your response? Do I have to update my HBOOT to achieve any other benefits? I guess I'm just trying to get at, what exactly does updating the HBOOT (the phone's bootloader) achieve?
Currently as I see it, I see the "firmware" as something other than the "HBOOT" (the other files within that same "Combo" RUU), correct?
Click to expand...
Click to collapse
I'm not sure to be honest as I always flash the full firmware package so I don't know if there will be any mismatch if the hboot has been left out.
If you are already s-off then I would flash the full 2.24 firmware package from the thread you quoted and then reflash your recovery in fastboot (no need to reboot into RUU mode) either CWM here or TWRP here following finally by flashing your rom
I can't open the link to download the firmware package for that post..... I used this 2.24 firmware package which I assume is the same as in the page you used but I would suggest this as I know it works fine

I stumbled across this when trying to find out what parts do what and are apart of what:
http://forum.xda-developers.com/showpost.php?p=43328416&postcount=3375
Apparently the HBOOT is part of the "firmware"
So again, if I update the HBOOT to 1.54 from 1.44, could I theoretically go back and forth between 1.54 and 1.44 whilst S-OFF?
EDIT: I just upgraded using the RUU from the link I posted, using the non-"combo" version.
I modified the android-info.txt to match my CID with the SuperCID I currently have, and I reinstalled my choice of recovery afterwards (TWRP, same version I had before.)
I'm now getting these 2 lines at the end of my 'getvar all' command via FASTBOOT:
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
what do those lines mean?
EDIT #2: I successfully switched back to HBOOT 1.44 whilst still S-OFF and got rid of those weird messages
C:\droidsdk\sdk\platform-tools>fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-OFF
serialno: nah bro
imei: nah bro
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4233mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
all: Done!
finished. total time: 2.771s

here's a random, somewhat related question from left field
incarceration said:
I stumbled across this when trying to find out what parts do what and are apart of what:
http://forum.xda-developers.com/showpost.php?p=43328416&postcount=3375
Apparently the HBOOT is part of the "firmware"
So again, if I update the HBOOT to 1.54 from 1.44, could I theoretically go back and forth between 1.54 and 1.44 whilst S-OFF?
EDIT: I just upgraded using the RUU from the link I posted, using the non-"combo" version.
I modified the android-info.txt to match my CID with the SuperCID I currently have, and I reinstalled my choice of recovery afterwards (TWRP, same version I had before.)
I'm now getting these 2 lines at the end of my 'getvar all' command via FASTBOOT:
commitno-bootloader: dirty-d16dc66985
hbootpreupdate: 11
what do those lines mean?
EDIT #2: I successfully switched back to HBOOT 1.44 whilst still S-OFF and got rid of those weird messages
C:\droidsdk\sdk\platform-tools>fastboot getvar all
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.17.3250.14
version-cpld: None
version-microp: None
version-main: 2.24.401.1
version-misc: PVT SHIP S-OFF
serialno: nah bro
imei: nah bro
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4233mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
gencheckpt: 0
all: Done!
finished. total time: 2.771s
Click to expand...
Click to collapse
I have the 64 gb dev edition, non-carrier branded and using TMO network. Already updated to 2.24 with AndroidRevo12 and didn't have S-Off first, so I gather there's no going there for now w/o going back to pre-2.24. But the whole reason I started down that road was cuz I thought I needed S-Off to flash radio by itself. I just want the new radio for the LTE bump since I seem to have such good LTE coverage at home and work.
If I don't need S-off to flash radio as "that can be done independently," then can you offer any possible reasons why I'm getting a signature verify fail when trying to push first revone (via adb), then later (once I gave up on S-off) while trying to flash the new radio.img fia fastboot?
(radio img is the new TMOUS 4A.17.3250.20_10.440.1150.04L)
Fastboot and adb seem to be fine otherwise, and phone settings are all proper (debug/etc). Bootloader obviously unlocked, etc...HBOOT is 1.44.

[Q] Google CID, S-ON

Hello,
I've made a mistake. While trying to convert my HTC One to Google Edition, I've mistakenly turned S-ON.
The OS was running fine before it was S-ON. Now it boots up to Homescreen and reboots immediately.
The CID is the one from Google Edition. So I can't flash any RUU's.
I can lock and unlock the Bootloader, or flash another Recovery etc.
But since the OS keep rebooting I cant use ADB and turn S OFF.

missgestalt said:
Hello,
I've made a mistake. While trying to convert my HTC One to Google Edition, I've mistakenly turned S-ON.
The OS was running fine before it was S-ON. Now it boots up to Homescreen and reboots immediately.
The CID is the one from Google Edition. So I can't flash any RUU's.
I can lock and unlock the Bootloader, or flash another Recovery etc.
But since the OS keep rebooting I cant use ADB and turn S OFF.
Click to expand...
Click to collapse
" I've mistakenly turned S-ON." -> why, oh why?? dont you realize that's a one way ticket??
Anyway, are you saying you are able to UNLOCK bootloader, if so there may be hope: Unlock bootloader and use rumrunner to get s-off (AND STAY S-OFF)

missgestalt said:
Hello,
I've made a mistake. While trying to convert my HTC One to Google Edition, I've mistakenly turned S-ON.
The OS was running fine before it was S-ON. Now it boots up to Homescreen and reboots immediately.
The CID is the one from Google Edition. So I can't flash any RUU's.
I can lock and unlock the Bootloader, or flash another Recovery etc.
But since the OS keep rebooting I cant use ADB and turn S OFF.
Click to expand...
Click to collapse
Try sideloading another rom via recovery and flashing it..
Sent from my One using Tapatalk

@nkk71
Any way to use rumrunner without a working OS? As I stated above, I don't access to ADB.
@n1234d
I'll try sideloading via custom recovery. Any ROM suggestions?

missgestalt said:
@nkk71
Any way to use rumrunner without a working OS? As I stated above, I don't access to ADB.
@n1234d
I'll try sideloading via custom recovery. Any ROM suggestions?
Click to expand...
Click to collapse
post your "fastboot getvar all" (excluding IMEI and s/n)

version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-ON
serialno: ____
imei: _____
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: GOOGL001
battery-status: good
battery-voltage: 4307mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e82187e
hbootpreupdate: 11
gencheckpt: 0

missgestalt said:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main: 3.62.1700.1
version-misc: PVT SHIP S-ON
serialno: ____
imei: _____
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: GOOGL001
battery-status: good
battery-voltage: 4307mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e82187e
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
try installing a custom ROM for 3.62, such as ARHD 31.6 (rooted & unsecured kernel) and get S-Off using rumrunner.
(you may have to try different ROMs as you're on GPE hboot & firmware.)

Runs fine with the mentioned ROM. I'll keep it at S-OFF this time. Thank you very much :good:

missgestalt said:
Runs fine with the mentioned ROM. I'll keep it at S-OFF this time. Thank you very much :good:
Click to expand...
Click to collapse
Happy flashing
And keep S-Off, you are lucky you were able to unlock again, lots of people got stuck with unable to unlock again!!
S-Off = "get out of jail"

[Q] HTC One M7_UL . T-MOB101 . Can't S-OFF second time

Hi Dudes,
Needed to Relock and S-On My M7 to send it to HTC to change the camera and I followed GURU's videos (Return to 100% Stock Guide + Stock ROM Guru Reset Downloads {Guru Reset M7 2.24.111.3} + Guru Bootloader Reset Tool) and everything went perfect untill I decided to S-On and directly my phone got a "TAMPERED" in bootloader.
I unlocked the phone again via HTCDEV and I tried everything to S-Off without any success (Firewater, Rumrunner), can you please help, now I am stuck and the stock rom that I have is making tricks on me because the phone is unlocked and S-On, I am sort of (F....d)
Thanks in advacne for your kind help.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4D.18.3250.18
version-cpld: None
version-microp: None
version-main: 4.20.111.21
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: T-MOB101
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ae8bbb39
hbootpreupdate: 11
gencheckpt: 0
NB: I am from Holland.

Oss69 said:
Hi Dudes,
Needed to Relock and S-On My M7 to send it to HTC to change the camera and I followed GURU's videos (Return to 100% Stock Guide + Stock ROM Guru Reset Downloads {Guru Reset M7 2.24.111.3} + Guru Bootloader Reset Tool) and everything went perfect untill I decided to S-On and directly my phone got a "TAMPERED" in bootloader.
I unlocked the phone again via HTCDEV and I tried everything to S-Off without any success (Firewater, Rumrunner), can you please help, now I am stuck and the stock rom that I have is making tricks on me because the phone is unlocked and S-On, I am sort of (F....d)
Thanks in advacne for your kind help.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4D.18.3250.18
version-cpld: None
version-microp: None
version-main: 4.20.111.21
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: T-MOB101
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ae8bbb39
hbootpreupdate: 11
gencheckpt: 0
NB: I am from Holland.
Click to expand...
Click to collapse
Having a hboot 1.57 makes it difficult to S-OFF. You can keep trying various rom and kernel combinations or if you are timed crunched you might consider Sunshine S-OFF the downside is the $25 fee.

Thanks
majmoz said:
Having a hboot 1.57 makes it difficult to S-OFF. You can keep trying various rom and kernel combinations or if you are timed crunched you might consider Sunshine S-OFF the downside is the $25 fee.
Click to expand...
Click to collapse
I tried everything and unfortunately I went with Sunshine :crying:
it took them exactly 5 minutes for the whole procedure
Now I am S-Off and I installed the Official T-mobile rom, problem solved.
They deserve the 25 $.
Thanks again for the tip.
Peaaaace.

Oss69 said:
I tried everything and unfortunately I went with Sunshine :crying:
it took them exactly 5 minutes for the whole procedure
Now I am S-Off and I installed the Official T-mobile rom, problem solved.
They deserve the 25 $.
Thanks again for the tip.
Peaaaace.
Click to expand...
Click to collapse
What you should have done is to downgrade to earliest T-Mobile ruu with 1.44 hboot and then s-on. Anything higher can give you tampered status as you saw
Good luck now.

[Q] Tempered root and stucked

Hello,
My phone is Htc one m7 unlocked and tempered root, also my hboot is 1.57 and s on and clockwordmod recovery v6.0.4.8
I'm basicly stucked now cause i was planning to turn my phone gpe edition but cause of my hboot i can't be able to s off.
How can i turn back to stock recovery and get off that tempered root thing?

You should be able to return to Stock Software easily enough. Depending on your current os and what files are available for your device.
But to go back to 100% Stock with a ***LOCKED*** bootloader and no ***TAMPERED*** flag requires the device to be s-off.
Can you please post the output of
Code:
fastboot getvar all
. But remove your imei and serial numbers before posting :good:

Danny201281 said:
You should be able to return to Stock Software easily enough. Depending on your current os and what files are available for your device.
But to go back to 100% Stock with a ***LOCKED*** bootloader and no ***TAMPERED*** flag requires the device to be s-off.
Can you please post the output of
Code:
fastboot getvar all
. But remove your imei and serial numbers before posting :good:
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.09.401.108
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__M27
battery-status: good
battery-voltage: 4307mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Btw im still on stock rom didn't install any custom rom, just unlocked tempered root and clockword recovery :/

canberkc said:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.09.401.108
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__M27
battery-status: good
battery-voltage: 4307mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Btw im still on stock rom didn't install any custom rom, just unlocked tempered root and clockword recovery :/
Click to expand...
Click to collapse
Ok the fact your on the stock Rom still may help. Unfortunately there's not a lot of files about for your device. What su app do you have some have an option to unroot and uninstall. Then a factory reset with Stock recovery should do the job. Only problem then is missing preload data. This gets wiped when you unlock the bootloader and OTA updates won't work without it.
I'm still looking

Danny201281 said:
Ok the fact your on the stock Rom still may help. Unfortunately there's not a lot of files about for your device. What su app do you have some have an option to unroot and uninstall. Then a factory reset with Stock recovery should do the job. Only problem then is missing preload data. This gets wiped when you unlock the bootloader and OTA updates won't work without it.
I'm still looking
Click to expand...
Click to collapse
I have supersu, if i won't be able to back stock i should s-off my phone too but i searched a lot but they didn't work cause of my hboot is 1.57

canberkc said:
I have supersu, if i won't be able to back stock i should s-off my phone too but i searched a lot but they didn't work cause of my hboot is 1.57
Click to expand...
Click to collapse
Yeah unfortunately there's only one guaranteed method to s-off on the latest firmware and that's Sunshine app it costs $25

Danny201281 said:
Yeah unfortunately there's only one guaranteed method to s-off on the latest firmware and that's Sunshine app it costs $25
Click to expand...
Click to collapse
Hmm but i can back to stock recovery at least, but pointless to back that if i won't take OTA updates i guess thank you for your support anyway

canberkc said:
Hmm but i can back to stock recovery at least, but pointless to back that if i won't take OTA updates i guess thank you for your support anyway
Click to expand...
Click to collapse
All I can find is this and I'm not even sure what it is as I don't know the language of the website.
http://www.trandroidev.com/one-m7-r...09-401-108-yeni-guncelleme-190-mb-civari.html
I think it's an OTA .zip if I'm right you can download it. Open it on your pc and inside there will be a firmware.zip. extract it and open it. Inside the firmware.zip you'll find the stock recovery you need. You can flash it with fastboot like any custom recovery.

Danny201281 said:
All I can find is this and I'm not even sure what it is as I don't know the language of the website.
http://www.trandroidev.com/one-m7-r...09-401-108-yeni-guncelleme-190-mb-civari.html
I think it's an OTA .zip if I'm right you can download it. Open it on your pc and inside there will be a firmware.zip. extract it and open it. Inside the firmware.zip you'll find the stock recovery you need. You can flash it with fastboot like any custom recovery.
Click to expand...
Click to collapse
That is Turkish but they just talked about latest update htc one with sense got, but i will try to find that from somewhere else ^^

AT&T M7, Soft Brick, Desperate for help!

I post as a final measure, as after two days of being unable to use my AT&T HTC One M7, I am in need of help. Badly. I have tried everything I could find, it either errors, fails, or crashes, nothing is working for me. I am without an OS, and have an unlocked bootloader, TWRP, and sleep deprivation. This all started when attempting to update to the newest Android available, and has left me stranded with a soft brick. If anyone has any ideas for me, PLEASE speak up. My phone was working fine until yesterday, and I am NOT interested in going back to my Iphone.

ErrorSuccess said:
I post as a final measure, as after two days of being unable to use my AT&T HTC One M7, I am in need of help. Badly. I have tried everything I could find, it either errors, fails, or crashes, nothing is working for me. I am without an OS, and have an unlocked bootloader, TWRP, and sleep deprivation. This all started when attempting to update to the newest Android available, and has left me stranded with a soft brick.
Click to expand...
Click to collapse
What issue the update caused exactly? The phone is stick at the HTC splash screen?
Post the output of "fastboot getvar all" (remove you irmei/sn before posting)
Is you bootloader locked/unlocked?

alray said:
What issue the update caused exactly? The phone is stick at the HTC splash screen?
Post the output of "fastboot getvar all" (remove you irmei/sn before posting)
Is you bootloader locked/unlocked?
Click to expand...
Click to collapse
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4M.32.3218.06
version-cpld: None
version-microp: None
version-main: 7.23.502.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4207mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
The phone will freeze at the htc splash, and then reboot into TWRP.
Unlocked

1st install any lollipop recovery, latest would be good
2nd search for latest RUU.ZIP (Lollipop) and install with "htc_fastboot.exe" (google for these 2 terms!, follow the htc_fastboot.exe commands instructions which should be explained on that site of the file)
3rd be happy.

ErrorSuccess said:
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 4M.32.3218.06
version-cpld: None
version-microp: None
version-main: 7.23.502.1
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4207mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
The phone will freeze at the htc splash, and then reboot into TWRP.
Unlocked
Click to expand...
Click to collapse
This is the typical problem of updating a lollipop rooted rom. Relock your bootloader and flash the latest at&t ruu, then install all updates (if any) before unlocking and rootimg

alray said:
This is the typical problem of updating a lollipop rooted rom. Relock your bootloader and flash the latest at&t ruu, then install all updates (if any) before unlocking and rootimg
Click to expand...
Click to collapse
Thank you so much! This finally fixed it. I tried flashing the ruu, but I didnt realize my bootloader had to be relocked.

ErrorSuccess said:
Thank you so much! This finally fixed it. I tried flashing the ruu, but I didnt realize my bootloader had to be relocked.
Click to expand...
Click to collapse
yep when s-on you must re-lock the bootloader to flash a RUU