Database Develop

Phone randomly reboots after 20-30 seconds. Help?

Decided to rewrite this as the problem is different now, not as bad, but a lot weirder! I can't get my head round whats up
Description of Problem
Right, so simplistically, the phone boots up, and you can use it (sort of) for about 30 seconds, before it reboots. Whilst its on, you can open apps, but there is definite issues with menu's not opening and you cant set a wallpaper, but its almost fully working. Then without any warning it just reboots, and does the same thing again.
I'm just confused at how it can boot up and almost fully work before rebooting. Failing to boot at all or bootlooping at the start animation, I can understand that, but not this.
Video of the Problem
What Caused the Issue
Its been a week or so since it first died, so I cant fully remember exact things that happened (I appreciate this will not be helpful!)
I had converted the phone to a google edition version using the tutorial here: http://forum.xda-developers.com/showthread.php?t=2358781
Changed the MID and CID, flashed the bootloader, recovery and RUU and the whole thing worked great.
Then I got my Xperia Z, so wanted it back to stock to be sold. Problem is I locked the bootloader and went S-ON before flashing the stock bootloader because i'm an idiot! Then obviously it wouldn't boot due to locked bootloader and custom recovery, so I tried to flash stock RUU, failed naturally due to upgraded bootloader, so I unlocked the bootloader again, flashed stock, and now this happens
Things I've Tried
Factory Reset
Flashed Stock Roms (1.28 / 2.17 / 2.24 and google edition) via both flashable zip and CWM backups - flashing in fastboot doesnt work because of signature error
Revone to re S-OFF (On HBOOT 1.54 so get a -6 error)
Maybe some other things?
Does anyone have any ideas? Any help is appreciated at the moment, don't want to wait for S-OFF on 1.54 or a 2.24 RUU as that could mean a brick on my shelf for a while.

Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium

redbull123 said:
Can't you use revone to unlock? Or did you do s-on as well?
Edit: didn't mean to thank you there - this app is killing me..
Have you tried downgrading your firmware to give you the old 1.44 bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?

dh2311 said:
Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't downgrade when you're s-on.

iElvis said:
You can't downgrade when you're s-on.
Click to expand...
Click to collapse
Thats what I thought, hence why I got a bit concerned earlier. Phones not fixed yet, stuck in a bootloop but my internet is slow for downloading firmwares

If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.

dh2311 said:
After hours of playing round I managed to get it to unlock the bootloader, so I should be fine, no idea what changed to make it work, but now it does. Out of interest for the future, how can you downgrade via fastboot with locked bootloader and S-ON?
Click to expand...
Click to collapse
You can't - I thought you were s-off since I didn't read in your post that you went back to s-on, that's what I was asking..
Sent from my HTC One using xda premium

iElvis said:
If you're unlocked, you should be able to flash a new recovery, and from there a new rom. You've probably mucked up something with the OS, so hopefully a wipe and flash should do the trick.
Click to expand...
Click to collapse
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!

dh2311 said:
The partition tables are ******, dont know why, sd card partition is unreadable and an ADB sideload still causes bootloops, this phone is really messed up and i dont know what i did
Usually I can figure the problem out. No idea now. Going to try and get the SD card back and restore an RUU from a CWM backup, then RUU it and should be fixed!
Luckily I have my trusty Xperia Z to use whilst I sort this out!
Click to expand...
Click to collapse
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.

iElvis said:
Did you try formatting your sdcard partition from your computer? That sounds like the issue. Likely you corrupted something with all those changes. Remember revone is a hack, so it;s not 100% reliable.
Click to expand...
Click to collapse
Genius! Dont know how i didnt think of that. Now i have an accessible SD card, just still bootlooping, itll work with the 1.28 backup and then the RUU will correct everything I've messed up

Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU

dh2311 said:
Okay, this needs a bump since this problem is weird now. The phone boots, with a number of roms, but after about 15 seconds, crashes and reboots every single time, no matter what ROM.
I have wiped system, data, cache everything, and it still does this!
Any ideas? an RUU is out of the question since i am on 2.17 and there is no RUU
Click to expand...
Click to collapse
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Edit: n/m, just saw you're s-on. I think the problem is that you've got an incompatible mix of firmwares from trying to convert to GE. You need to get s-off again somehow.

iElvis said:
Sounds like a kernel or firmware conflict. Try flashing 2.24 and see if that helps.
Click to expand...
Click to collapse
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
EDIT: same problem! :'(

dh2311 said:
Thats what I thought, tried 1.28, 2.17 and 2.24 with still no success. It doesnt make sense to me.Trying flashing CM10 as i saw someone else suggest
Click to expand...
Click to collapse
Are you flashing firmware or just roms?

iElvis said:
Are you flashing firmware or just roms?
Click to expand...
Click to collapse
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of

dh2311 said:
I cant flash RUU's becuase of my firmware version (2.17) flashed 1.28 via a CWM backup and the other 2 via ARHD stock odexed roms, best I think i can get becuase theres no 2.17 or 2.24 RUU that I know of
Click to expand...
Click to collapse
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.

iElvis said:
I don't mean RUUs, I mean one of the custom firmware packages that you flash in fastboot. But you need to be s-off to do that. You did something like this when you converted to GE.
This is one of the risks of going s-off, unfortunately. It lets you do stuff to your phone that can really screw it up.
Click to expand...
Click to collapse
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?

dh2311 said:
Going back to S-ON was my mistake, if this phone was still S-OFF I'd have been able to fix it. But i still cant explain why it bootloops? All I did was change the MID and CID, which are now back to stock (HTC_001) and (PN07100) but it still has the Google edition bootloader, surely if that was the issue then it wouldnt boot past the bootloader, so where does the issue lie?
Click to expand...
Click to collapse
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.

iElvis said:
It could be any number of things. You changed a lot going to GE, and with S-on, the phone is now doing all its usual security checks. Something somewhere got bollixed up. It could be the GE firmware is conflicting with your CID or MID.
One way or another, you've got to get back to s-off.
Click to expand...
Click to collapse
Thats the solution. Or a 2.24 RUU from HTC could also do it. But revone requires a booting phone, which mine cant do, doesnt work out of recovery unfortunately. and moonshine is only for older versions. Tempted to just put this phone on a shelf and wait for an RUU. Carry on using my Xperia Z

Dont know if this will be of any help for sorting the issue, but this is all the hboot info from getvar all
Code:
(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.17.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <removed for safety>
(bootloader) imei: <removed for safety>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3821mV
(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
Definitely cant seem to get this to work, upon booting i get lots of force closes like the messaging app and contacts storage. That a clue for anyone?
Or if anyone knows how to S-Off without a working F/W that would be a help but I doubt it can be done

[Q] HTC One unlocked, tampered, S-ON and custom recovery - Can I do OTA

Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND

Torcidas1950 said:
PLEASE RESPOND
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH

alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH
Click to expand...
Click to collapse
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery. And how do I do that?

Torcidas1950 said:
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery.
Click to expand...
Click to collapse
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
And how do I do that?
Click to expand...
Click to collapse
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #

Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.

So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?

iElvis said:
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.
Click to expand...
Click to collapse
alray said:
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #
Click to expand...
Click to collapse
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?

Torcidas1950 said:
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
Click to expand...
Click to collapse
post your "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
post your "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3894mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Torcidas1950 said:
Here it is:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock

nkk71 said:
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock
Click to expand...
Click to collapse
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.

Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
1- If you are 100% stock then Settings -> About should also show your correct version number
2- you rooted the phone, so that may or may not have changed some system files, so OTA may not work
3- once S-Off stay S-Off, my personal opinion
In my humble opinion, three choices really, when it comes to "modding" or not your phone:
A) stay stock and don't mess with it to get OTAs
B) you cannot achieve S-OFF (due to newer hboots, or device problems) -> fine live with an unlocked bootloader, and accept the fact that you cannot install OTAs .... you can however "download and install later" the OTA, then pull it to your phone, and use the signed firmware.zip in it
C) you can achieve S-OFF and want to mod your phone -> then do it, get S-Off and enjoy the freedom (but don't flash things not meant for your phone!! this goes for S-On too)
Of course you're going to say that "but S-Off is dangerous", it's a double edged sword... sometimes you are able save your phone thanks to S-Off, and sometimes you can brick it completely.
But then again, you can easily brick an S-On phone too (especially one that is modded), and much more difficult to save than an S-Off phone.
^^ All that is my personal opinion, and I'm not suggesting you S-Off, but if you want to mod your phone (whether S-On or S-Off), you need to be aware of what may, or may not, go wrong, and have done some reading and research
Good Luck

Well, its not worth it. I wont risk bricking my phone again

Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
Torcidas1950 said:
Well, its not worth it. I wont risk bricking my phone again
Click to expand...
Click to collapse
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes

nkk71 said:
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes
Click to expand...
Click to collapse
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me

Torcidas1950 said:
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me
Click to expand...
Click to collapse
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this

nkk71 said:
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this
Click to expand...
Click to collapse
Well, I am not planing to unplug the cable haha.. well if someone else knows please tell, the update is coming soon so I would like to know, but if its risky, there is no way I'm doing it

Torcidas1950 said:
but if its risky, there is no way I'm doing it
Click to expand...
Click to collapse
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71

nkk71 said:
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71
Click to expand...
Click to collapse
So, yesterday the OTA was finally released, and today I have flashed stock recovery... Now waiting for the OTA notification to come
Sent from my HTC One using XDA Free mobile app

hello guys,
i did a deep search, but nothing found about it, or found but did not understood, so i will ask you. if in my stock recovery it also says (TAMPER), will be possibly to instal OTA?
L.E. - rest is like the title of the topic - Unlocked, S-ON, tampered..

Stock Rom 4.2.2 update to 4.3 = brick

I put stock back on my phone "Guru_Reset_M7_2.24.771.3.zip" which I have done before without any problem.
Stock rom flashed fine, boots up fine and start reinstalling apps etc, OTA firmware starts downloading sense 5.5 etc
Install OTA update and then restart then phone just shows white background with htc logo then bootloops.
Tried going into recovery, restarting, power down, factory reset etc, doesn't work so I do fastboot oem relock to see if it helps.
So basically it's boot looping and now I have no idea how to fix it
EDIT: - I Wiped, reinstalled stock rom and tried again, SAME PROBLEM.

Anarchy89 said:
Hey guys I'll try and keep it short and sweet.
So here's what happened.
I installed android revolution HD 71.1 no problems, notice mobile signal is weak 1-2 bars I normally have 4-5 so I searched and someone said maybe firmware is not up to date.
So I wipe the rom and put stock back on there "Guru_Reset_M7_2.24.771.3.zip" which I have done before without any problem.
Stock rom flashed fine, boots up fine and start reinstalling apps etc, OTA firmware starts downloading sense 5.5 etc
Install OTA update and then restart then phone just shows white background with htc logo then bootloops.
Tried going into recovery, restarting, power down, factory reset etc, doesn't work so I do fastboot oem relock to see if it helps.
So basically it's boot looping and now I have no idea how to fix it, please help, it will be so appreciated
Click to expand...
Click to collapse
If you can flash and access custom recovery, adb push or adb sideload a custom rom..

thanks, I'm making progress, I unlocked the bootloader again and am reflashing the stock firmware...

I flashed stock firmware and stock recovery and downloaded and installed the OTA update and it's doing the same thing!! why?
Just bootlooping

Anarchy89 said:
I flashed stock firmware and stock recovery and downloaded and installed the OTA update and it's doing the same thing!! why?
Just bootlooping
Click to expand...
Click to collapse
Links to stock firmware and stock recovery?
Maybe something is wrong with the phone??
Your best start will be to flash a custom recovery and then flash a custom rom. What is the output of your fastboot getvar all ? (remove IMEI)

SaHiLzZ said:
Links to stock firmware and stock recovery?
Maybe something is wrong with the phone??
Your best start will be to flash a custom recovery and then flash a custom rom. What is the output of your fastboot getvar all ? (remove IMEI)
Click to expand...
Click to collapse
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.

Seanie280672 said:
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Click to expand...
Click to collapse
yes that's the exact one I am using

Seanie280672 said:
He is using this correct ?: http://www.htc1guru.com/dld/guru_reset_m7_2-24-771-3-zip/
He is having exactly the same problem as someone I was trying to help out who is having exactly the same issue and may join in this thread.
The guru reset puts them on 4.2.2 which works fine then they get a small OTA which installs fine, then a big update to 4.3 which installs, but upon restart for some reason gives a boot loop, doesn't get past the HTC quietly brilliant logo, im at a loss.
Click to expand...
Click to collapse
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?

SaHiLzZ said:
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
Click to expand...
Click to collapse
I did suggest that, but, somehow he never got the sense 6 update but is on hboot 1.57 and cant s-off

SaHiLzZ said:
Oh ok.. Interesting.
S-OFF, and move to .401 base perhaps?
Click to expand...
Click to collapse
Sorry I don't understand.
Also couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752

Seanie280672 said:
I did suggest that, but, somehow he never got the sense 6 update but is on hboot 1.57 and cant s-off
Click to expand...
Click to collapse
ODD! 4.2/4.3 should be on 1.55 Hboot..
@OP.. whats your fastboot getvar all ?

C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3838mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s

couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752

Its strange that you too have HBOOT 1.57, did you get the sense 6 update ?

Seanie280672 said:
Its strange that you too have HBOOT 1.57, did you get the sense 6 update ?
Click to expand...
Click to collapse
nope

Anarchy89 said:
couldn't I circumvent this hassle just by installing this ROM?
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
Yes... You have 1.57 HBOOT.. you should NOT be using 2.x.771.x files. It does NOT gel well.
You have to stick with custom roms, just use adb push or adb sideload..

Anarchy89 said:
nope
Click to expand...
Click to collapse
Well you could try flashing twrp 2.6.3.3 and then flash that ROM your interested in, but it could make things worse, you have a very strange problem, I would love to know why custom rom's work and the guru-reset file, but the OTA's pretty much kill your phone.

SaHiLzZ said:
Yes... You have 1.57 HBOOT.. you should NOT be using 2.x.771.x files. It does NOT gel well.
You have to stick with custom roms, just use adb push or adb sideload..
Click to expand...
Click to collapse
Okay, well I don't know a lot about all this stuff, for example I don't know what HBOOT is, S-OFF/ON etc, I just look for ROMs I'm interested in, optimizing my phone, I just read guides and 99% of the time I don't have a problem.
Do you think my problem would go away if I had HBOOT 1.55? Is it even possible to downgrade?
I'll just flash the ROM I mentioned...but doesn't that mean I won't be able to get OTA updates? (because of the nonstock recovery)
IDFK

Don't know why your HBOOT is 1:57 while your device is not OTA to Sense 6.0. Certainly you can't downgrage HBOOT to 1:55 without S-OFF. You should flash TWRP 2.6.3.3, then adb sileload a custom rom to install

I just wiped and put android revolution hd 71.1 on there and it seems fine now, the other stock rom I mentioned earlier I flashed and I kept getting errors "unfortunately updater has stopped working" every 3 minutes.
I had a go at S-OFF with rumrunner but it didn't work on two ROMs, someone said to try it on linux as it's more reliable, any suggestions for how I can easily S-OFF? thanks :good:

[SOLVED] [Q] HTC Stuck on Boot Screen, here's what I did

Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
Some info about the phone:
S-ON
TWRP ver 2.6
rooted
can access recovery
don't need anything on the phone
I'm looking for a solution to get this phone going again.. any solution. I'd prefer to be on stock ROM. I'd love some help on this. I'm here.

post your fastboot getvar all please

2dayquestion said:
Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
don't need anything on the phone
Click to expand...
Click to collapse
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good

alray said:
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good
Click to expand...
Click to collapse
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.

2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
post the ouput of fastboot getvar all

Seanie280672 said:
post your fastboot getvar all please
Click to expand...
Click to collapse
(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: 1.00.000.0
(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: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One

yatindroid said:
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One
Click to expand...
Click to collapse
The factory reset isn't working. It still hangs. I did the initial backup through TWRP. Will Titanium backup be compatible with that backup?
Now the phone is currently locked, no OS.Should I flash another ROM?

http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match

Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The OS is set to 1.000.000. I used some **** utility that reset it. I started clicking things... lol
One thing I'm wondering is since this phone is S-ON, will I be able to even flash a ROM? Could that be the reason that the TWRP restore function isn't working? As far as I know... SON would prevent system files from being written.. correct me if I'm wrong
..downloading that file as I write this

Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.

2dayquestion said:
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.
Click to expand...
Click to collapse
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.

Seanie280672 said:
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.
Click to expand...
Click to collapse
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?

2dayquestion said:
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?
Click to expand...
Click to collapse
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.

Seanie280672 said:
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.
Click to expand...
Click to collapse
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers

2dayquestion said:
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers
Click to expand...
Click to collapse
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.

Seanie280672 said:
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.
Click to expand...
Click to collapse
That may have been the issue. Thanks for your time. Another 'thanks' is in order. Cheers

Softbrick Going From CM12.1 to Stock

Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...

scirto said:
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...
Click to expand...
Click to collapse
Ignore my last paragraph. I completely misread what that file was providing (stock recovery, duh, of course that's what it's providing. Not what I need).

Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

scirto said:
Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
EDIT: I will also note that my last attempt with an RUU was with my phone starting on the home screen. Not sure if starting in bootloader/fastboot is better or worse or makes no difference? I'll try that too

scirto said:
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
Click to expand...
Click to collapse
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk

deleted

Danny201281 said:
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!

scirto said:
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
Click to expand...
Click to collapse
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Exactly... Might be the software developer in me, but I feel a huge sense of relief as long as I start to see something different happening. OTA is downloading, no root is detected, so the process should complete successfully. Major kudos to you, my friend.

So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!

scirto said:
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!
Click to expand...
Click to collapse
Your Welcome. Enjoy
Sent from my SM-T230 using Tapatalk