Database Develop

[Q] Restoring and removing root from HTC One - CID Optus001

Hello all.
I made a mistake and didn't update to 4.2.2 before I unlocked and rooted my HTC One M7.
I downloaded the OTA System update and tried to install before I realised I can't update after rooting.
I've been trying to find how to remove root, update to 4.2.2 then root again, however I can't find the right RUU file to do this.
Could some please help out a newly converted Android user?
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main: 1.29.980.17
version-misc: PVT SHIP S-OFF
serialno: removed
imei: removed
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: OPTUS001

So far I've restored to factory and that's it. Should I re-root?
Or would a better option be to relock and start again?
Any help would be much appreciated.

Do you still have a custom recovery installed?
AT&T HTC One
GPe 4.3

Hello Cory.
Yes I have CWM Still installed

I've tried flashing firmware after relocking
I get this error while trying to do so.
sending 'recovery' (6816 KB)...
OKAY [ 1.037s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.855s
At a guess I've got the wrong RUU / Stock firmware file.
I've looked around and I can't find it.
I did however find a nandroid optus file from buggy lawson with the correct CID and version main 1.29.980.x
Can I somehow use that?

Duraze said:
I've tried flashing firmware after relocking
I get this error while trying to do so.
sending 'recovery' (6816 KB)...
OKAY [ 1.037s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.855s
At a guess I've got the wrong RUU / Stock firmware file.
I've looked around and I can't find it.
I did however find a nandroid optus file from buggy lawson with the correct CID and version main 1.29.980.x
Can I somehow use that?
Click to expand...
Click to collapse
You should be able to get the recovery.img from the nandroid _IF_ he took it without actually flashing the CWM or TWRP recovery to the phone when taking it. I do have a stock recovery from a Vodafone 4.1.2 (1.29.980.17) here that _should_ work on yours ...

thoptsY History
bwhinnen said:
You should be able to get the recovery.img from the nandroid _IF_ he took it without actually flashing the CWM or TWRP recovery to the phone when taking it. I do have a stock recovery from a Vodafone 4.1.2 (1.29.980.17) here that _should_ work on yours ...
Click to expand...
Click to collapse
I can't actually flash anything though. I get the signature verify fail every time I try.
But yeah the stock Vodafone one should work right?
Any chance you could help with a noob friendly guide for a former iPhone jailbreaker turned Android rooter?

Duraze said:
I can't actually flash anything though. I get the signature verify fail every time I try.
But yeah the stock Vodafone one should work right?
Any chance you could help with a noob friendly guide for a former iPhone jailbreaker turned Android rooter?
Click to expand...
Click to collapse
Why isn't there one of those super simple RUU.exe files to use

Duraze said:
I can't actually flash anything though. I get the signature verify fail every time I try.
But yeah the stock Vodafone one should work right?
Any chance you could help with a noob friendly guide for a former iPhone jailbreaker turned Android rooter?
Click to expand...
Click to collapse
In theory it should as the Optus phone is supposed to be the "unbranded" version which Vodafone also uses. But I don't know to be honest. This is my first Android device and the first thing I did was to (take a backup) and then convert to the Google Play Edition RUU
I'll send you a PM with the file location and you can download it if you want.

So I've just tried to reboot in recovery mode.
I currently have this showing
***TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
and now I can't go into recovery it just keeps going back to the bootloader screen.
I've soft bricked, right?

Ok so at the moment I can't actually do anything in the bootloader even though it loads.
I can't even factory reset.
Do I need to root again to do anything?

Don't you need an unlocked boot loader to be able to flash a new recovery.img ?

Ok I've clearly done something very very wrong.
Is there anybody about who's able to help me out?
Starting to worry a little

Duraze said:
Ok I've clearly done something very very wrong.
Is there anybody about who's able to help me out?
Starting to worry a little
Click to expand...
Click to collapse
Apparently I'm still rooted according to root checker basic.

So I've just tried to flash it. I get a signature verification error.
Also, if I go into the boot menu and select recovery it goes back to the boot menu again and displays *** Security Warning ***

So you obviously have the phone working again?
You can be rooted and be on the stock recovery. I am on my Google Edition, I flashed TWRP and used the latest SuperSU to root and when that was complete flashed the stock 4.3 recovery back on. I did receive my 4.3 OTA while rooted, but with stock recovery, BUT will lose root when the OTA applies.

Well it's loading but it's not working properly.
I don't know how to flash things over I keep getting a signature problem.

Basically I want to do a OTA upgrade to 4.2.2 or 4.3 whatever is available then root and start again .

From what I can gather my root is not working because I can't flash anything across.
Every time I try I get the signature failed error.

So you can boot into Android and have the phone running, it is on 4.1.2 and still rooted? Yes? You are still running the old CWM recovery as well?
For me what I would do if I were in that situation.
1) plug phone into computer
2) Make sure that HTC sync is not running
3) Go to my platform-tools folder and run adb reboot bootloader for a Mac use ./adb reboot bootloader
4) Make sure the bootloader screen has FASTBOOT (USB) between the date and the menu for Vol up and down etc
5) Then flash the stock recovery with fastboot flash recovery recovery.img for a Mac use ./fastboot flash recovery recovery.img
6) That should work fine and then you are back to stock with the exception of being rooted.
7) You can then either select Reboot in the menu or fastboot reboot on a Mac ./fastboot reboot
Of course that is assuming that the recovery.img from 1.29.980.17 is compatible with your Optus Phone and is located in the same folder as the adb and fastboot commands.
This is the way I do it to re-flash a recovery on mine between TWRP or CWM and the stock recovery.img ...

Unable to root Htc one (sprint)

I am unable to root my htc one with sprint. I write the recoveries, to the deivce, and fastboot says it was ok.
When I try and boot to recovery, it hangs for approx 30 sec, then reboots to the OS.
I am currently running Android 4.3
S=Off
cid = spcs_001
hboot = 1.55.0000
radio = 1.00.20.0913_3
opendsp = v31.120.274.0617
os = 3.04.651.2
eMMC = boot 2048MB
tried to use fastboot erase cache a few times also
Any assistance would be greatly appreciated!
Thanks

abs7125 said:
I am unable to root my htc one with sprint. I write the recoveries, to the deivce, and fastboot says it was ok.
When I try and boot to recovery, it hangs for approx 30 sec, then reboots to the OS.
I am currently running Android 4.3
S=Off
cid = spcs_001
hboot = 1.55.0000
radio = 1.00.20.0913_3
opendsp = v31.120.274.0617
os = 3.04.651.2
eMMC = boot 2048MB
tried to use fastboot erase cache a few times also
Any assistance would be greatly appreciated!
Thanks
Click to expand...
Click to collapse
I forgot to mention, I have tried to use fastboot boot (image), and it freezes, no matter which recovery image I try. I have tried twrp, and clockwork so far.

Fastboot flash recovery twrp.img
Make sure you are getting the newest img file from twrp site. Make sure it's the Sprint ver.

an0ther said:
Fastboot flash recovery twrp.img
Make sure you are getting the newest img file from twrp site. Make sure it's the Sprint ver.
Click to expand...
Click to collapse
Double checked, it is the latest file, and I also verified it is for Sprint. Thought the same thing.

I assume it used to work? I see you are s-off? I don't see what could be going on. You can always do a full ruu reboot and start over but it will wipe your phone.
I just saw you did a Fastboot boot img. Not sure what that could have done. Boot.img is your kernel. When your phone boots , does it work?

an0ther said:
I assume it used to work? I see you are s-off? I don't see what could be going on. You can always do a full ruu reboot and start over but it will wipe your phone.
I just saw you did a Fastboot boot img. Not sure what that could have done. Boot.img is your kernel. When your phone boots , does it work?
Click to expand...
Click to collapse
The phone it self, does work. Boots fine. My problem, is I cant get root anymore. It worked until I went back to factory on everything, so I could get the updates. Even recovery worked when I got that back to stock. I took the Ota updates, no I cant get into recovery, so I can re root it.
Tried to go back to stock like i did before, same issue on 4.22 now. followed same procedures for re lock, un lock bootloader, both times, and this time it wont load anything into recovery.

Go to settings, power when phone is booted. Make sure fastboot is not selected.
Sent from my One using XDA Premium 4 mobile app

CoryTallman said:
Go to settings, power when phone is booted. Make sure fastboot is not selected.
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Shouldnt try this when tired lol. That was checked. Unchecked it, and got the following error this time :
sending 'recovery' (391888 KB)...
OKAY [ 13.413s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 13.456s

abs7125 said:
Shouldnt try this when tired lol. That was checked. Unchecked it, and got the following error this time :
sending 'recovery' (391888 KB)...
OKAY [ 13.413s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 13.456s
Click to expand...
Click to collapse
also, I tried to use rom manager, to download and install clockworkmod. It says an error occurred while flashing your recovery.

abs7125 said:
also, I tried to use rom manager, to download and install clockworkmod. It says an error occurred while flashing your recovery.
Click to expand...
Click to collapse
So after 2 days, it looks like I got this working.
Not sure why this fix made a difference, however it worked, for me.
I ended up having to flash an older recovery twrp image of 2.5.0.0 first. That atleast allowed me to boot into recovery, finally. Problem was, nothing on the touchscreen would work.
I rebooted the device back into the bootloader, then installed twrp 2.6.3.0
That worked great!

[Q] Boot Loop Newly upgraded GPE HTC One 4.4 SuperSU 1.8

I have a Google Play Edition (the real deal from Google, not flashed from something else) was on 4.3, was trying to upgrade to 4.4 using the OTA upgrade. I'm now in a boot loop. I'm *think* my issue is related to SuperSU v.1.8: http://forum.xda-developers.com/showthread.php?p=47868582
I was on Rooted 4.3 with SuperSU 1.8 running properly. Got the OTA message to upgrade. Flashed my Recovery Image back to 4.3 stock from this image: http://forum.xda-developers.com/showthread.php?t=2358781 in the 4.3 RUU Zip.
Ran the OTA update, everything seemed to install correctly.
I can still get into the Bootloader, Fastboot, and Recovery.
On regular boot I get to the select your language screen and then the phone reboots. Just guessing that something is happening between S-On and SuperSU that is causing problems. I've tried a couple older versions of SuperSU pushed with adb in CW and have the same problem.
If anyone have a link to a stock system.img I could flash for 4.3 or 4.4 that would solve all my problems. The system.img I thought I had for 4.3 out of the 4.3 RUU Zip is too large, as is the 4.4 RUU Zip.
Thanks in advance for the help - please be gentle if I'm violating an unknown procedure. I've searched an this for a few hours and haven't been able to find anything that might help me.
Thanks,
Matt

I've upgraded 3 phones so far (all converts, not real GPE) that had super SU installed and not had this issue.
if your seeing select language it means either 1. you wiped data before the OTA? or 2. something went wrong when converting your data.
It's doubtful but possible that anything is wrong with /system. The update script checks for specific versions of files and would have error ed rather than patched a mismatch. Lets start by wiping data and cache.
fastboot erase userdata
fastboot erase cache
fastboot reboot
since your S-On you can't use the RUU's and I'm pretty sure those system.img files are not signed; they are just dumps in img format so even if they weren't too big they still wouldn't work.
mthomas1262 said:
I have a Google Play Edition (the real deal from Google, not flashed from something else) was on 4.3, was trying to upgrade to 4.4 using the OTA upgrade. I'm now in a boot loop. I'm *think* my issue is related to SuperSU v.1.8: http://forum.xda-developers.com/showthread.php?p=47868582
I was on Rooted 4.3 with SuperSU 1.8 running properly. Got the OTA message to upgrade. Flashed my Recovery Image back to 4.3 stock from this image: http://forum.xda-developers.com/showthread.php?t=2358781 in the 4.3 RUU Zip.
Ran the OTA update, everything seemed to install correctly.
I can still get into the Bootloader, Fastboot, and Recovery.
On regular boot I get to the select your language screen and then the phone reboots. Just guessing that something is happening between S-On and SuperSU that is causing problems. I've tried a couple older versions of SuperSU pushed with adb in CW and have the same problem.
If anyone have a link to a stock system.img I could flash for 4.3 or 4.4 that would solve all my problems. The system.img I thought I had for 4.3 out of the 4.3 RUU Zip is too large, as is the 4.4 RUU Zip.
Thanks in advance for the help - please be gentle if I'm violating an unknown procedure. I've searched an this for a few hours and haven't been able to find anything that might help me.
Thanks,
Matt
Click to expand...
Click to collapse

ipfreelytech said:
I've upgraded 3 phones so far (all converts, not real GPE) that had super SU installed and not had this issue.
if your seeing select language it means either 1. you wiped data before the OTA? or 2. something went wrong when converting your data.
It's doubtful but possible that anything is wrong with /system. The update script checks for specific versions of files and would have error ed rather than patched a mismatch. Lets start by wiping data and cache.
fastboot erase userdata
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks so much for the reply.
I did wiped AFTER installing the OTA as part of my troubleshooting. I did it through CWM recovery and regular recovery to see if it made any difference. I can do it again through fastboot if you think that will have any affect. Thanks again for the reply, appreciate it.

dunno about stock recovery but CWM doesn't actually do a proper wipe. it leaves /data/media intact. fastboot erase will rewrite the file-system.
mthomas1262 said:
Thanks so much for the reply.
I did wiped AFTER installing the OTA as part of my troubleshooting. I did it through CWM recovery and regular recovery to see if it made any difference. I can do it again through fastboot if you think that will have any affect. Thanks again for the reply, appreciate it.
Click to expand...
Click to collapse

ipfreelytech said:
dunno about stock recovery but CWM doesn't actually do a proper wipe. it leaves /data/media intact. fastboot erase will rewrite the file-system.
Click to expand...
Click to collapse
get the error "FAILED (remote: not allowed)" when I attempt to erase and format user data
I think I'm ready to just push a stock backup nandroid on to the device - any recommendations as to which I should use?

sorry. I didn't realize the one blocks that command. I use it all the time on other devices.
I actually made a stock 4.4 nandroid last night that I'll upload soon. I haven't seen any untainted GPE nandroids posted. with a clean nandroid and the firmware.zip from the ota you should be pretty much the same as running an RUU.
mthomas1262 said:
get the error "FAILED (remote: not allowed)" when I attempt to erase and format user data
I think I'm ready to just push a stock backup nandroid on to the device - any recommendations as to which I should use?
Click to expand...
Click to collapse

ipfreelytech said:
sorry. I didn't realize the one blocks that command. I use it all the time on other devices.
I actually made a stock 4.4 nandroid last night that I'll upload soon. I haven't seen any untainted GPE nandroids posted. with a clean nandroid and the firmware.zip from the ota you should be pretty much the same as running an RUU.
Click to expand...
Click to collapse
That would be awesome. If you don't mind sharing the link when you do I'd appreciate it.
Cheers

Here you go:
https://mega.co.nz/#!TMlgWLDJ!ZfFlcxcRkebpb3cciULnlTf4GMJfy4grwOLi-Ied3Tg
extract the zip, then copy the folder to your recovery's backup location. I made it with CWM.
If your using CWM you can use the command adb push 2013-11-28.07.23.56 /data/media/clockworkmod/backup/GPE/
then restore it from the menu
Here's a link to the untouched firmware.zip from the OTA:
https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
flash that zip from fastboot.
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 firmware.zip
fastboot reboot
should be good to go then. You'll have stock /system and stock recovery so future OTA should work.
mthomas1262 said:
That would be awesome. If you don't mind sharing the link when you do I'd appreciate it.
Cheers
Click to expand...
Click to collapse

I'm hoping this will also work for my situation as I am stuck. I purchased a pre-owned GPE HTC One. The previous owner re-loaded JB stock but left clockwork mod on there. Last night I discovered the stock recovery image and loaded that successfully (wanting a stock experience now). This morning the phone successfully upgraded to the most recent jelly bean. Soon after that upgrade kitkat was ready for download.
As soon as the install finished the phone was stuck in a boot loop. I have tried numerous things to get it to stop but i have been unsuccessful. It appears that it is S-On, which I believe is also adding to my issues. Do you think the situation and nandroid you posted above will work in my situation (total stock recovery and no superSU)?
Thank you!

s-on is not the problem unless the previous owner lied and that's a converted phone and not a legit GPE.
I assume you've done a factory reset from recovery or bootloader?
Feel to try flashing CWM then restoring my nandroid and then flashing the firmware.
The_Doctor_Who said:
I'm hoping this will also work for my situation as I am stuck. I purchased a pre-owned GPE HTC One. The previous owner re-loaded JB stock but left clockwork mod on there. I wanted a totally stock experience. Last night I discovered the stock recovery image and loaded that successfully. This morning the phone successfully upgraded to the most recent jelly bean. Soon after that upgrade kitkat was ready for download.
As soon as the install finished the phone was stuck in a boot loop. I have tried numerous things to get it to stop but i have been unsuccessful. It appears that it is S-On, which I believe is also adding to my issues. Do you think the situation and nandroid you posted above will work in my situation (total stock recovery and no superSU)?
Thank you!
Click to expand...
Click to collapse

ipfreelytech said:
s-on is not the problem unless the previous owner lied and that's a converted phone and not a legit GPE.
I assume you've done a factory reset from recovery or bootloader?
Feel to try flashing CWM then restoring my nandroid and then flashing the firmware.
Click to expand...
Click to collapse
It did come in the GPE box, so I hope he didn't go that much out of the way to lie! lol It is the official GPE.
I did do a factory reset with no luck.
I have tried using the RUU files I found on another thread to flash through fastboot but I get a failed 99 error.
When I attempt to find device with adb, it does not list a device ( I assume b/c of debugging), but finds fine the phone fine on fastboot device.
Also, I thought about reflashing to CWM but when I try to bring up the bootloader after flashing the CWM recovery nothing will come up at as far as a recovery and will just begin to boot the phone.
Thank for any help you may offer and I apologize in advance for my noob questions. I've flashed recoveries and ROMs on the past on other devices but this one has me stumped.

there is no legit RUU for GPE! The conversion RUU only works with s-off because it is not properly signed!
flash this CWM: http://flyhalf205.com/recoveries/recovery-clockwork-touch-6.0.4.5-m7ul.img
fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
after flashing fastboot erase cache
select reboot bootloader on your phone. then select recovery.
then continue with restoring my nandroid and then flashing the firmware in RUU mode.
The_Doctor_Who said:
It did come in the GPE box, so I hope he didn't go that much out of the way to lie!
I did do a factory reset with no luck.
I have tried using the RUU files I found on another thread to flash through fastboot but I get a failed 99 error.
When I attempt to find device with adb, it does not list a device ( I assume b/c of debugging), but finds fine the phone fine on fastboot device.
Also, I thought about reflashing to CWM but when I try to bring up the bootloader after flashing the CWM recovery nothing will come up at as far as a recovery and will just begin to boot the phone.
Thank for any help you may offer and I apologize in advance for my noob questions. I've flashed recoveries and ROMs on the past on other devices but this one has me stumped.
Click to expand...
Click to collapse

looking great - enjoying me some kit-kat right now! thanks a ton!

Awesome. So I take it my nandroid plus the firmware zip worked for you?
mthomas1262 said:
looking great - enjoying me some kit-kat right now! thanks a ton!
Click to expand...
Click to collapse

ipfreelytech said:
Awesome. So I take it my nandroid plus the firmware zip worked for you?
Click to expand...
Click to collapse
The nandroid worked great - not sure what you wanted me to do with the firmware.zip, I *think* the link to the firmware.zip was the same as the nandroid link. Let me know if I'm missing something. Just need to install SuperSU and then I can restore everything from Titanium.
Again, thanks a ton!

That's what I get for listening to other NOOBs when it comes to this. I did as suggested below re: CWM
here are my command lines
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.674s]
finished. total time: 1.861s
c:\And> fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.056s
When I reboot the bootloader and select recovery it reboots and starts the loop over again. that's where I was stuck. I figured if I could load another ROM I'd at least be okay, but I can't get the darn recovery to work.

Ok - at least I know what my issue was before. I attempted to install SuperSU.zip 1.8, installs fine, but when I go into regular boot get boot looping again. Looks like I'll need to wait for an update to SuperSU.zip - if someone with authority can post in the SuperSU thread that might be really helpful.
Thanks!

good eye. I have fixed the link. here's the right one: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
The purpose of the firmware.zip is to get all your firmware on the correct version as well as writing the stock recovery so that future OTA will work without issue [assuming of course you don't screw with /system by deleting apk you don't use or editing files].
you flash it using fastboot after rebooting to ruu mode. re-read my post.
I think you have a bad super su installer. I've installed super su 1.8 on three ones so far all running the 4.4 GPE and not had issue; however those were all converts and are s-off so that may have something to do with it. However it doesn't make a ton of sense.
mthomas1262 said:
The nandroid worked great - not sure what you wanted me to do with the firmware.zip, I *think* the link to the firmware.zip was the same as the nandroid link. Let me know if I'm missing something. Just need to install SuperSU and then I can restore everything from Titanium.
Again, thanks a ton!
Click to expand...
Click to collapse
---------- Post added at 11:28 AM ---------- Previous post was at 11:22 AM ----------
fastboot getvar all
paste the results here with imei and serial redacted.
The_Doctor_Who said:
That's what I get for listening to other NOOBs when it comes to this. I did as suggested below re: CWM
here are my command lines
c:\And>fastboot flash recovery recovery-clockwork-touch-6.0.4.5-m7ul.img
target reported max download size of 1526722560 bytes
sending 'recovery' (8746 KB)...
OKAY [ 1.185s]
writing 'recovery'...
OKAY [ 0.674s]
finished. total time: 1.861s
c:\And> fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.056s
When I reboot the bootloader and select recovery it reboots and starts the loop over again. that's where I was stuck. I figured if I could load another ROM I'd at least be okay, but I can't get the darn recovery to work.
Click to expand...
Click to collapse

I greatly appreciate the help (and apologize for stepping on the toes of the OP).
c:\And>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(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: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.056s

ipfreelytech said:
I think you have a bad super su installer. I've installed super su 1.8 on three ones so far all running the 4.4 GPE and not had issue; however those were all converts and are s-off so that may have something to do with it. However it doesn't make a ton of sense.
Click to expand...
Click to collapse
I got the installer from:
download (dot) chainfire (dot) eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
(can't post URLs yet)
I haven't tried to get s-off, on on the 1.54 version so that makes things a little harder, I've seen some posts about it.

[Q] Brick or saveable? Red triangle - SOLVED!

I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.

Well... There is one thing you could do.
squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.
Click to expand...
Click to collapse
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
2.Flash a custom recovery.
You flash a custom recovery like this using fastboot.
Code:
fastboot flash recovery <recoveryName>.img
3.Use TWRP to copy the ROM zip file to your internal storage.
4.Do a nandroid backup.
5.Do an advanced wipe (Wipe data, system, cache and dalvik cache partitions).
6.Do a factory reset (Wipe Data/Factory reset).
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
7.Flash your preferred ROM.
8.Tell me if it worked and enjoy!

squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!".
Click to expand...
Click to collapse
This screen is the stock recovery main page.
Volume up and power work, and give 5 fails to mount the sd card.
Click to expand...
Click to collapse
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Click to expand...
Click to collapse
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
Is there anything else I can do with it? or is it just a paperweight now?
Click to expand...
Click to collapse
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant
Click to expand...
Click to collapse
Yes rogers are M7_UL too.
so you can just go ahead and root your phone then flash a ROM of your choice.
Click to expand...
Click to collapse
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
-Windows computer (WIndows 8.1 is fine).
Click to expand...
Click to collapse
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
Click to expand...
Click to collapse
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.

alray said:
This screen is the stock recovery main page.
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
Yes rogers are M7_UL too.
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.
Click to expand...
Click to collapse
The last HTC device that lasted 3 years with me was the One X (my AT&T M7 either got bricked or had battery issue) and I never tried to get it S-OFF'ed since I really did no't see any use for it back in the day plus its screen was having problems anyway. This is new knowledge for me thanks!
and to the OP, if you need more help the quote button is your friend.
Good luck!

The Android Manual said:
The last HTC device that lasted 3 years with me was the One X
Click to expand...
Click to collapse
Wow mine (Tegra version) only lasted 13 months, had the infamous wifi issue (repaired myself) , overheat issue and motherboard finally died. I was very reluctant to buy htc again but finally I'm very satisfied with my M7.

Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.

squidstings said:
Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.
Click to expand...
Click to collapse
You can try the Roger's RUU in this post. You will need to follow the instructions in the OP. I believe in your case, since there is no 6.xx version for Roger's you can go directly to the Lollipop version.

The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
Click to expand...
Click to collapse
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.

squidstings said:
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.
Click to expand...
Click to collapse
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.

alray said:
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.
Click to expand...
Click to collapse
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0

squidstings said:
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.

mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM? is one custom and the other carrier generated?). I managed to get the identifier token last night, but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.

mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
I downloaded the ruu from the link on XDA but the .zip won't extract.

squidstings said:
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM?
Click to expand...
Click to collapse
A RUU stands for Rom Update Utility. Its an official file from HTC that flashes many partitions like the system partition (the rom/OS), the recovery partition, bootloader, radio partition, touch drivers, IR drivers...... well all partitions that are not specific to your phone and that will make it stock again. The only partition that are not flashed when using a RUU are those containing unique info about your phone like the MFG partition containing your IMEI number, Serial number, Date of manufactures etc.
A rom is only the /system partition flashed using a custom recovery. So when you flash a ROM (eiither custom or stock) you only flash the system partition and all other are kept like they was before the flash.
but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.
Click to expand...
Click to collapse
You don't need usb debugging when flashing a RUU. USB debuging is only needed to use ADB commands when booted in the OS. A RUU is flashed using FASTBOOT commands when booted in the bootloader.
squidstings said:
I downloaded the ruu from the link on XDA but the .zip won't extract.
Click to expand...
Click to collapse
This is explained in the same post from where you have downloaded the file.... You might want to read the OP of the thread you are downloading files from :good: Not trying to be rude btw but lack of reading can sometime makes the situation worst. so just for you here it is again: The ruu are encrypted so they can't be extracted or opened and don't need to be, only flash it on your phone.
This is a collection of lollipop ruu.zip files for our beloved htc one m7 801.
I cannot test all of these files so any feedback will be welcome.
Also I have no responsibility if you phone explodes after flashing any of these files, I am just the uploader.
As many in this thread, ask about zip corruption, zip are not corrupted they are encrypted and can't open normally , they need decryption check md5 and dont try to unzip them
Click to expand...
Click to collapse
and instruction how to flash the ruu are posted just below these warnings, just click on the "show more" button.
---------- Post added at 05:12 PM ---------- Previous post was at 04:54 PM ----------
@squidstings
Might be easier to just unlock the bootloader, flash a recovery and then a rom like suggested at post #2
Youv said you already have your identifier token, go ahead and submit it to htcdev.com/bootloader (must create and account first). They will reply with an e-mail containing a file named Unlock_code.bin. Download and save the file in the same folder where you have adb and fastboot installed on your computer.
Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.

Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.[/QUOTE]
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
C:\Android>
I did read everything. got a bit confused by different methods and files suggested (maybe just different wording for the same proceedure?). I've been looking for ROMs and RUUs all day. after I've fixed this phone (hopefully) i want to root my m7.

squidstings said:
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Click to expand...
Click to collapse
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired

alray said:
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired
Click to expand...
Click to collapse
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!

squidstings said:
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!
Click to expand...
Click to collapse
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.

mb_guy said:
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.
Click to expand...
Click to collapse
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.

squidstings said:
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.
Click to expand...
Click to collapse
Ok, let me try again.
If you want to flash a rom,
1) unlocked bootloader (you have)
2) Flash custom recovery like twrp (I don't see that you have done this) so may be easier to go the ruu route.
3) Use custom recovery to install rom. I like the arhd ones
If you want to flash the RUU
1) relock the bootloader
2) flash the ruu, once this is done and the phone rebooted and running it will be at 7.17.631.7, go to settings about and check for system updates. You should receive an OTA which is 7.17.631.35. Install it.
3) You can leave the phone like this, or re-unlock the bootloader and flash a custom recovery like twrp. This will give you the ability to do nandroid backups, root the phone or install custom roms if you want.
Either method should work, the choice is yours
Hope this is clearer.

Need Assistance getting my phone HTC One 802d Indian version back to working.

Hi,
I've kind of soft bricked my phone. Good thing is still able to fastboot as my PC detects it via USB.
I am new to Android rooting, flashing etc.
I had android Lollipop before I messed up phone. I've downloaded Nandroid backup and RUU for Indian version of HTC One 802d from other threads on XDA.
I am not sure of process to use that Nandroid backup. I've CWM recovery but don't have root access. Bootloader iss unlocked.
For other thing i.e. RUU that I downloaded is a zip file. But for some strange reason I'm not able to extract it on windows 7. It says compressed zip folder is invalid. I also downloaded Chinese RUU which is again zip and doesn't extarct, gives same error.
I am new to all this though I've some knowledge about computers and gadgets.
Please help me on how to get back my phone working may by Nandroid or RUU or anything else.
Please let me know if any details or information is needed.
Greatly appreciate any help in this regard. Thank you!

Hi,
Can someone please help me with this? :crying:

First of all, you can't unzip RUU.zip because it's encrypted. And why are you trying to unzip it anyway? Other thing - your phone is most likely S-on, so, in order to flash RUU.zip, you need stock recovery and locked or relocked bootloader. My suggestion is to go and do some reading on how to flash RUU. There are loads of tutorials online. And make sure you understand everything before you go ahead with flashing

donkeykong1 said:
First of all, you can't unzip RUU.zip because it's encrypted. And why are you trying to unzip it anyway? Other thing - your phone is most likely S-on, so, in order to flash RUU.zip, you need stock recovery and locked or relocked bootloader. My suggestion is to go and do some reading on how to flash RUU. There are loads of tutorials online. And make sure you understand everything before you go ahead with flashing
Click to expand...
Click to collapse
Thanks a lot for your reply!
Okay I get a point about RUU.zip not opening. I was trying it at first place cause I saw it some video that he opens it and then runs a setup file in it which opens windows wizard which then guides step by step to flash RUU from GUI.
Yes, my phone is S-On and I've been doing quite a lot reading since past couple of days and understading things better with every reading.
Now, I need further help. I'll first briefly explain how I messed up my phone. I had android L with Sense 6 in my cellphone before I started playing with it and decided to root. After watching few tutorials I first unlocked Bootloader then flashed cwm recovery. After that I took a backup from cwm and then installed SuperSu.zip from cwm recovery and rebooted phone normally. It started but SuperSu installed earlier was stopping regularly throwing error messages. I also downloaded rootChecker app and it showed that I didn't have root access.
Here, I slightly panicked as this is first time I was playing around with it. I rebooted my phone, went to cwm recovery and tried restoring back up that I took earlier as said above. But I didn't have root access and since then my phone went in bootloop and not starting.
My PC detects it when I connect in fastboot USB and i am able to execute fastboot commands.
=======================================================================================
Now, I,ll explain steps I am following to get my phone working :
1) I downloaded few RUU zip latest being from here --> http://www.mediafire.com/download/k...1_09B_release_391798_signed+by+jamesjerss.zip
2) Downloaded stock recovery for KITKAT from other xda thread --> http://forum.xda-developers.com/showthread.php?t=2617159
3) flashed this stock recovery then relocked my phone. fastboot oem lock.
4) executed fastboot oem rebootRUU
5) executed fastboot flash zip ruu.zip with the ruu zip downloaded in step 1 above
but it fails with version check failed , some error like this don't remember exact wording of it. I can get you that if needed by trying one more time.
Also, I can provide other information like getvar all and hboot version etc if required but kindly help me get out of this. Really appreciate your help.
I just want to highlight one more thing that I visited HTC care centre yesterday and without looking much at device just by looking at bootloader and cwm recovery he said that OS is corrupt and I'll need to replace mother board which costs half the price of phone. I don't believe him. It is just soft bricked and am able to connect in fastboot USB.
Please guide me on how to proceed further ahead.
Thank you once again!
<<Just getting you the output after running flash zip>>
C:\Users\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>fastboo
t flash zip ruukkn.zip
target reported max download size of 1542111232 bytes
sending 'zip' (1344718 KB)...
OKAY [ 75.112s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 190.871s

Post a fastboot getvar all please. Don't forget to remove your IMEI and serial no. That guy at HTC care is an idiot ?

donkeykong1 said:
Post a fastboot getvar all please. Don't forget to remove your IMEI and serial no. That guy at HTC care is an idiot
Click to expand...
Click to collapse
Lol. He certainly seems to be one.
Below is result of getvar all -->
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: 2.04.30.0316
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.720.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: A1000037A674B4
(bootloader) product: m7cdwg
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0751000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

OK. The reason for "signature verify fail" error is because you're trying to flash older firmware than your current one. Find a matching or newer firmware, and flash away. Just don't unzip it ?

donkeykong1 said:
OK. The reason for "signature verify fail" error is because you're trying to flash older firmware than your current one. Find a matching or newer firmware, and flash away. Just don't unzip it
Click to expand...
Click to collapse
he he I won't do that definitely.
But earlier yesterday I had tried with Lollipop RUU downloaded from -->
androidfilehost.com/?fid=24052804347774374
but that too failed with similar signature verify fail.
What should I do?
<<<<<<<<<<<<<<Just to point out>>>>>>>>>>>>>>>>>>>>>>>>>>
Lollipop RUU that I downloaded is like PN07IMG_M7C_DWG_L50_SENSE60_MR_hTC_Asia_India_]7.17 .720.6_Radio_1237.29.35.0903 release_426120_signed.zip whereas from getvar results shared above it shows version like --> bootloader) version-main: 7.17.720.15
does it make a difference? if yes, that's the latest RUU I can find online.
How can I proceed in this scenario?

So, you can't flash a RUU, because there isn't one for your phone. Now, unlock your bootloader again, and flash TWRP recovery for your phone

donkeykong1 said:
So, you can't flash a RUU, because there isn't one for your phone. Now, unlock your bootloader again, and flash TWRP recovery for your phone
Click to expand...
Click to collapse
Okay but what after flashing TWRP recovery? How will it help?

yogeshchaudhari21 said:
Okay but what after flashing TWRP recovery? How will it help?
Click to expand...
Click to collapse
We'll find a TWRP nandroid backup and restore it [emoji6]

donkeykong1 said:
We'll find a TWRP nandroid backup and restore it [emoji6]
Click to expand...
Click to collapse
oh I see.
In that case I've CWM nandroid backup again downloaded from other XDA thread I shared earlier though it's for android 4.2.2
CWM Nandroid Backup (Android 4.2.2):
M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB
But as I'm doing all this for first time and am pretty much noob , I'm not sure how to use it to my benefit.
Can you please guide how can I use that nandroid back up to restore it in my phone?
Thank you!

yogeshchaudhari21 said:
oh I see.
In that case I've CWM nandroid backup again downloaded from other XDA thread I shared earlier though it's for android 4.2.2
CWM Nandroid Backup (Android 4.2.2):
M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB
But as I'm doing all this for first time and am pretty much noob [emoji14] , I'm not sure how to use it to my benefit.
Can you please guide how can I use that nandroid back up to restore it in my phone?
Thank you!
Click to expand...
Click to collapse
For that one you need CWM recovery. I'll be home in about 20 minutes and I'll walk you through the process

donkeykong1 said:
For that one you need CWM recovery. I'll be home in about 20 minutes and I'll walk you through the process
Click to expand...
Click to collapse
Oh sure! I'll be waiting.
I do have a cwm recovery although it's not touch version but that doesn't matter I guess.
Really appreciate your support. Thanks!

I'm back. did you flash the recovery yet?

donkeykong1 said:
I'm back. did you flash the recovery yet?
Click to expand...
Click to collapse
Hey hi!
Yes, I did.

yogeshchaudhari21 said:
Hey hi!
Yes, I did.
Click to expand...
Click to collapse
OK. Now enter your recovery and choose backup. Wait till it's done, so we can put your new backup in the same folder

donkeykong1 said:
OK. Now enter your recovery and choose backup. Wait till it's done, so we can put your new backup in the same folder
Click to expand...
Click to collapse
OMG something weird. Phone is not entering recovery after I flashed cwm recovery again. It's coming to bootloader but not going to recovery and just restarting. :| Let me keep trying.

yogeshchaudhari21 said:
OMG something weird. Phone is not entering recovery after I flashed cwm recovery again. It's coming to bootloader but not going to recovery and just restarting. :| Let me keep trying.
Click to expand...
Click to collapse
Did you unlock your bootloader again?

donkeykong1 said:
Did you unlock your bootloader again?
Click to expand...
Click to collapse
Yes I did unlock and then flashed recovery. I've been doing it quite a few times since yesterday so got used to it. This is something strange happening.