Database Develop

i need help i think my device is bricked

okk so i was trying to flash a rom for the first time and i really went at it the wrong way. i didin't backup my original RUU and now my device is stuck on the bootloader screen and i really have no idea what to do. i just want to get an OS running on my phone right now cause im freaking out. my company carrier is rogers and this is what my phone is showing right now:
***tampered***
***relocked***
m7_ul pvt ship s-on rh
hboot-1,55,0000
radio-4a.20.3263.16
opendsp -v32,120.274.0909
os-
emmc-boot 2048mb
i try looking for another ruu to flash in my phone but i cant seem to find one that works with my phone..even when i try using the flashboot getvar command to check for the version this is all i got.. : C:\Users\david\Desktop\sdk-tools>fastboot getvar version-main
version-main:
finished. total time: 0.001s
any help at this point would be greatly appreciated i need to get my phone up working so i can receive my calls
i have managed to bring back recovery mode by re-unlocking it via htcdev..now when the phone boots it goes to the google logo and then the language selecting screen then restarts after 10 secs everytime

Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.

fenstre said:
Instead of the fastboot command you typed, write:
Code:
fastboot getvar all
Then look for "CID". Search for a RUU for that CID. If you can't find one, we'll discuss other solutions.
Click to expand...
Click to collapse
this is what i got from the fastboot getvar all command :
C:\Users\david\Desktop\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA346W904162
(bootloader) imei: 354439050131335
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4290mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.053s
cidnum says ROGER001? im i don't think ive seen cid what that number around
edit: could it be possible that this is what i need ? "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17"
since i did not make a backup is there a chance i can restore this ? ive tried the method that suggest sideloading but it didn't work or maybe i didin't do it right but it didn't wanna recognize my phone when i tried the command'
edit 2: also, im using twrp instead of cwm if that information can help in any way.

If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.

gffmac said:
If you can let us know which rom you attempted to install and what you managed to do. Did you install custom recovery etc.
Click to expand...
Click to collapse
well all i was trying to do was install the goole play edition rom (bigxie_m7_GPe_KRT16S_odexed-signed.zip) but after the installation it kept restarting after the language selection screen. i used twrp to flash the rom. right now all im able to do is cycle through the booloader, the recovery screen and to the language selection screen

Unless you have another rom (4.3 rom) copied onto the storage on your phone you will probably have to flash stock recovery and recover by installing a stock RUU for your carrier/CID version.
---------- Post added at 11:59 AM ---------- Previous post was at 11:54 AM ----------
Out of curiosity try going into twrp and doing a factory reset (wipe) and reboot see if you have the same issue.

is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?

deerome said:
is there such thing as a stuck RUU for rogers in canada? ive been looking on the internet but i can't seem to find anything that could works for my phone. maybe you could point me in a direction so i could look ?
Click to expand...
Click to collapse
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.

gffmac said:
Cant see any for rogers
Just found this http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/ if you can copy a rom to the phone it will probably work.
A nandroid backup for rogers is here http://forum.xda-developers.com/showthread.php?t=2207874 or you could flash a pre 4.4 rom. CWM needed to recover a CWM backup and backup would need to be in right directory.
You would need to unlock bootloader to do these things.
If I was you I would download a custom rom like Android Revolution HD 40.3 copy over via above process, do a wipe and install, without s-off you probably have to flash kernel via fastboot.
Click to expand...
Click to collapse
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.

deerome said:
thanks for your answers
i definitly am gonna try installing the android revolution hd rom to see if i can at least get an OS running on my phone. what command do i have to use to flash the kernel ?
also, i have tried sideloading/pushing the nandroid backup before but that didint seem to work, not sure if i did something wrong.
Click to expand...
Click to collapse
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.

gffmac said:
To flash a kernel via fastboot 'fastboot flash boot boot.img'. Make sure the boot.img (if thats what its called) is in the same folder as fastboot. The corresponding kernel(boot.img) is inside the zip file of most roms.
Click to expand...
Click to collapse
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until im better at this thing.
anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:

deerome said:
thanks to your help i was able to install an earlier version of android hd so after many hours of headache i somehow managed to install the android hd rom by sideloading it with cwm. what a pain in the arse -_-. nonetheless that was a great help, what should i do now so something like this don't happen again? i wanted to have the google edtion on my htc but i think im gonna wait until Im better at this thing.
Anyways thanks again man i really appreciate you have no idea how frustrated i was lol :good:
Click to expand...
Click to collapse
No probs glad you got it working again.
If you really want to try a Google Edition rom you would need to s-off your phone which is trickier than what you have done so far so may want to read up some more.

I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk

deerxmoose said:
I had the exact same problem while i was flashing a GEdition ROM. The problem here is that my volume Keys dont work and i cant manage to enter recovery/bootloader over ADB. Tried all usb cords and porta. Still giving me Device not found. Any tricky way to access bootloader or recovery?
I've already sent it to warranty but without the original software.... Blablabla they told me that it would only work
with a board replacement... 180€
Any help?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??

gffmac said:
You can get to bootloader and recovery via adb commands but thats from a running rom I presume http://forum.xda-developers.com/showthread.php?t=1853159
How come your volume keys dont work, did it come that way? I presume you have tried holding power and volume down for a prolonged length of time??
Click to expand...
Click to collapse
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk

deerxmoose said:
For no reason they stop working. And i think its a hardware malfunction. Besides that, i cant manage to enter bootloader or recovery to instala other ROM.
I guess with Samsung Phones there is a doubletap on the screen to enter bootloader.
Im really stressing here.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.

gffmac said:
I would contemplate opening the phone up to check the behind the volume buttons but that is very risky.
Click to expand...
Click to collapse
Before trying that ill prefer to try Any other solutions. Anyone?
Sent from my Desire HD using Tapatalk

There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery

SaHiLzZ said:
There is no bootloader in Samsung phones, and no doubletap. You need to hit the buttons as well. If you are able to boot into the phone and adb devices shows the device, you can do
adb reboot-bootloader or adb reboot recovery
Click to expand...
Click to collapse
Tried that over and over and it keeps saying device not found.
Sent from my Desire HD using Tapatalk

Then you should fix your computer/adb issues.

[Q] I've fallen and I can't get up!

I've successfully played with custom roms for years, but I managed to completely corrupt my Sprint HTC One M7 and I'm having a hard time figuring out how to get it back to being a working phone.
It's rooted and unlocked. I think a bad download of a recovery or rom corrupted either the storage or firmware or both.
When I first rooted it, I did have some problems. However, I was able to recover and successfully ran the Revolution ROM for about a month. I wanted to try the Viper ROM and that action (not the ROM itself, of course) put the device into its current bricked state.
I can still flash different recoveries. I can install new ROMs. I've even attempted to flash stock recoveries and run a factory reset to completely reset the phone's partitions. However the phone is unusable. I even have a OTG cable to grab ROMS from a USB stick. TWRP doesn't recognize the internal storage of the phone, but it does recognize the USB stick on the OTG cable. ClockWork can see all of the storage on the phone.
I have tried relocking and running RUUs, but I think I am doing it incorrectly because my phone is still S-ON and if that is the case, you have to find the right version of RUU that is an upgrade rather than a downgrade of the phone. The RUUs always error out. Perhaps someone will be able to provide a correct link as I have screen pictures and Model ID info I can include.
Behavior: As I try to show in the pictures I've attached, I can install customer ROMS or alleged stock ROMS onto the phone. When the process completes, I am presented with the stock lock screen for the M7. When I swipe the screen I am presented with a white HTC screen that is similar to the boot screen, but note there is no other writing. This is not the boot screen. Rather, it is all you get.
If you are tethered to a PC, you can see the storage on your list of drives.
However, after about 90 seconds, the phone auto reboots, and you are in a loop.
The phone is 13 months old, so I don't think I can just relock it and walk into a Sprint store and ask for a replacement.
Moreover, I think this is fixable, I just don't know how quite yet.
Thanks for those pros out there who can help me get out of this mess of my own making.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4242mV
(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
all: Done!
finished. total time: 0.035s

It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904

There is no RUU for 4.06.651.9.
This guide will get you fixed up use either the 4.06.651.9 or 5.03.651.3 s-on firmware
http://forum.xda-developers.com/showthread.php?t=2503646

twisteddan said:
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
That RUU won't work it's super old

BD619 said:
That RUU won't work it's super old
Click to expand...
Click to collapse
Oh ok.....Sorry about that.

twisteddan said:
Oh ok.....Sorry about that.
Click to expand...
Click to collapse
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
The question is, does such an RUU exist?
If it does not, is there a stock or custom ROM Zip that, while not packaged in an RUU, might work? Although if that were the case, the ROM's I've already tried to use might actually work.
Or, should I attempt to S-Off the phone (something I've never done before) in order to try an RUU to work?
Thanks for your initial answers. Sounds like I don't have enough to move forward quite yet.

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?

bethesdaadk said:
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
Click to expand...
Click to collapse
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.

BD619 said:
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
Click to expand...
Click to collapse
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
I use this one http://forum.xda-developers.com/showthread.php?t=2651035

BD619 said:
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
I've tried to parse out your directions to make sure I do this correctly. Can you please check to make sure I'm understanding you correctly?
First step is to flash the firmware:
I've downloaded 4.06.651.9 s-on firmware per your suggestion becuase that's the current version of my phone.
Then I need to rename it to just plain firmware.zip
Then on the phone:
Boot to bootloader and lock the bootloader by typing:
fastboot oem lock
in my ADB/Fastboot dos session.
Then use these commands:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
which will flash the firmware.
Then: If you get this error after the second command (most likely will)
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again. Essentially, you are flashing the firmware a second time.
Then, unlock the bootloader again
fastboot flash unlocktoken Unlock_code.bin
Here's the part where I'm a little uncertain. You state:
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Also, earlier in the guide, you state:
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Do I need to worry about that since I'm flashing the s-on firmware and not the s-off firmware?
Thanks for your help on this. If I were this careful the first time around, maybe I wouldn't have gotten to this point. Luckily, my old Evo4G is in good condition so I've put it into service while I try and fix the HTC One.

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
tdhite's 2.7.0.9 worked fine for me?

Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Click to expand...
Click to collapse
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Click to expand...
Click to collapse
This only applies to folks that are s-off.

BD619 said:
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
This only applies to folks that are s-off.
Click to expand...
Click to collapse
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.

bethesdaadk said:
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
Click to expand...
Click to collapse
Well the 5.03.651.3 firmware and rom are sense 6

BD619 said:
Well the 5.03.651.3 firmware and rom are sense 6
Click to expand...
Click to collapse
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?

bethesdaadk said:
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
Click to expand...
Click to collapse
Did you remember to flash the radio?

BD619 said:
Did you remember to flash the radio?
Click to expand...
Click to collapse
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.

bethesdaadk said:
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
Click to expand...
Click to collapse
Nope just flash the radio from recovery

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:

[Q] urgent help please

Hi, really need some help as i have no clue whats happening, installed Lollipop update on my htc one tonight, when it went to start up it got stuck at htc one screen, tried rebooting several times with no change, the phone was previously unlocked, rooted and had a custom rom installed, but i did the stock RUU, which relocked the phone and allowed me to do OTA back to Kitkat 4.4.3. I can get into the bootloader which shows *Tampered* (i know that one) but underneath its saying *Unlocked* ? please help

johnrc_uk said:
Hi, really need some help as i have no clue whats happening, installed Lollipop update on my htc one tonight, when it went to start up it got stuck at htc one screen, tried rebooting several times with no change, the phone was previously unlocked, rooted and had a custom rom installed, but i did the stock RUU, which relocked the phone and allowed me to do OTA back to Kitkat 4.4.3. I can get into the bootloader which shows *Tampered* (i know that one) but underneath its saying *Unlocked* ? please help
Click to expand...
Click to collapse
Very strange, can you link the RUU that you used to get back to stock ? never known an RUU to relock the bootloader for you.

Seanie280672 said:
Very strange, can you link the RUU that you used to get back to stock ? never known an RUU to relock the bootloader for you.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=23501681358543706
guru reset file, select stock radio and stock recovery during the flash, when the flash is finished and phone reboots, start updating., the guru reset will wipe everything so be sure to backup anything you want to keep first.
It was you who pointed me to it,

johnrc_uk said:
https://www.androidfilehost.com/?fid=23501681358543706
guru reset file, select stock radio and stock recovery during the flash, when the flash is finished and phone reboots, start updating., the guru reset will wipe everything so be sure to backup anything you want to keep first.
It was you who pointed me to it,
Click to expand...
Click to collapse
LOL, yeah that seems about right, and did it update ok after that ? before Lollipop ?
Sorry could you post your fastboot getvar all again please without imei and serial

Seanie280672 said:
LOL, yeah that seems about right, and did it update ok after that ? before Lollipop ?
Click to expand...
Click to collapse
yeah i did about 4 OTA updates back to 4.4.3 and phone worked perfect, so when i got the lollipop update i wouldnt think anthing would be different. now i cant get past the htc one screen :/
c:\fastboot>fastboot getvar all
< waiting for device >
(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.2
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3783mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s

johnrc_uk said:
yeah i did about 4 OTA updates back to 4.4.3 and phone worked perfect, so when i got the lollipop update i wouldnt think anthing would be different. now i cant get past the htc one screen :/
Click to expand...
Click to collapse
I would say, try again, start again, its possible that the Lollipop update has got a bit corrupt along the way somewhere, maybe the download, thankfully your only soft bricked, you will need to get back to the bootloader, flash a custom recovery and then push that guru reset to your internal SDCard and flash it again, very strange that all of the KK updates worked fine but the LP one bricked you.
Before you do try that, have you tried a factory reset from the bootloader ?
Damn, hang on, the firmware part of the LP update seems to have worked fine, I can see thats all updated, you probably wont beable to use the guru reset again due to HBOOT conflicts.

Seanie280672 said:
I would say, try again, start again, its possible that the Lollipop update has got a bit corrupt along the way somewhere, maybe the download, thankfully your only soft bricked, you will need to get back to the bootloader, flash a custom recovery and then push that guru reset to your internal SDCard and flash it again, very strange that all of the KK updates worked fine but the LP one bricked you.
Before you do try that, have you tried a factory reset from the bootloader ?
Click to expand...
Click to collapse
havent tried a factory reset, should i try that first. and what steps would i take if that didnt work? would i have to root phone etc again first?

johnrc_uk said:
havent tried a factory reset, should i try that first. and what steps would i take if that didnt work? would i have to root phone etc again first?
Click to expand...
Click to collapse
try the factory reset first, if that doesnt work, as you have the newer firmware on your phone already, I would flash a custom recovery (TWRP 2.8.4.0) and then flash this rom, its basically stock Lollipop with future OTA ability.
https://www.androidfilehost.com/?fid=95916177934533366

Seanie280672 said:
try the factory reset first, if that doesnt work, as you have the newer firmware on your phone already, I would flash a custom recovery (TWRP 2.8.4.0) and then flash this rom, its basically stock Lollipop with future OTA ability.
https://www.androidfilehost.com/?fid=95916177934533366
Click to expand...
Click to collapse
tried factory reset...still hangs on htc one screen, still plays startup music.

johnrc_uk said:
tried factory reset...still hangs on htc one screen, still plays startup music.
Click to expand...
Click to collapse
This is very strange, im tempted to say try and relock the bootloader first and then try and boot, but im worried that if it still doesnt boot you may not be able to unlock the bootloader again, then you'll be right up the creek without a paddle.

Seanie280672 said:
This is very strange, im tempted to say try and relock the bootloader first and then try and boot, but im worried that if it still doesnt boot you may not be able to unlock the bootloader again, then you'll be right up the creek without a paddle.
Click to expand...
Click to collapse
ok no idea if this was me but i relocked bootloader, then did htcdev unlock again and flashed custom recovery. rebooted the phone and now its booted up and optimising android apps, what ever it did now seems to have got out of the boot loop.

johnrc_uk said:
ok no idea if this was me but i relocked bootloader, then did htcdev unlock again and flashed custom recovery. rebooted the phone and now its booted up and optimising android apps. weird!?!
Click to expand...
Click to collapse
:silly:, thats a new one on me, glad it working though, very weird.

Seanie280672 said:
:silly:, thats a new one on me, glad it working though, very weird.
Click to expand...
Click to collapse
Had a funny feeling id be on stock android after i did the factory reset lol..phone has booted up, and im on lollipop, rooted again but never mind!

johnrc_uk said:
Had a funny feeling id be on stock android after i did the factory reset lol..phone has booted up, and im on lollipop, rooted again but never mind!
Click to expand...
Click to collapse
Its still stock mate, just rooted and custom recovery, I cant live without root

Seanie280672 said:
Very strange, can you link the RUU that you used to get back to stock ? never known an RUU to relock the bootloader for you.
Click to expand...
Click to collapse
I have an almost similar problem.
I own the European model, unbranded.
Got the OTA tonight, after installing I got stuck ed on the HTC WHITE screen.
My device has never been rooted nor S- Off.
The boot screen reads as follow.
***LOCKED***
M7 SHIP S-ON RH
HBOOT- 1.57.000
RADIO -4T. 29.3210.00
OPEN dsp v32. 120.274.0909
OS-6.09.401.11
Emmc-boot 2048mb
Nov 12 2014.22:00:05,0
Neither Recovery nor factory reset worked
Can you provide me some advice.
Thanks
Henry Paris
Sent from my GT-N8010 using XDA Free mobile app

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