Database Develop

[Q] Restoring Rogers HTC One M7 to Factory without RUU ?

Hello everyone,
This is my first post so I hope I don't end up being a "typical noob".
I'll try give the full info but keep it concise.
Background:
1) Carrier Unlocked HTC One M7 Originally on Rogers.
M7_UL PVT SHIP S-On RH
HBoot-1.44.000
Radio - 4A.14.3250.13
Open DSP 26.120.274.0202
emmc-boot
2) The phone was working perfectly after being hard reset, and configured without a sim.
3) After it was activated by the telco, the keyboard would would no longer work. Dialpad fine... menus fine... but no keyboard would pop up when selecting text fields. Did a full factory reset, and also tried clearing the Sense Touch data cache via Settings->App.
4) After trying various possible solutions I found online, I finally decided to try start from scratch by installing stock firmware.
WARNING: i'm the second owner of the phone. For warranty I would have had to send the phone to HTC. I suspect the HTC warranty won't apply to me anyhow. I suggest that in this situation, people just get the phone fixed on warranty if they have that option
First Steps:
A1) I unlocked the bootloader via HTCDev and used adb to flash CWM Touch Recovery.
A2) Restored the "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)"
A3) Phone now works correctly at this stage, but is still bootloader unlocked/tampered + CWM Touch Recovery
A4) While I may eventually flash the phone to an official Developer Edition
I would like to reinstall a factory recovery.img, then use revone to get rid of the bootloader "tampered" flag and relock it. (for OTA Updates, and the usual warranty concerns)
A5) I tried flashing both the boot.img and recovery.img from "OTA_M7_UL_JB_50_Rogers_WWE_1.29.631.17_R-1.29.631.4_release_318662" to get back to stock recovery, but I got a Red triangle.
Questions:
Q1): Does anyone know of a stock recovery.img I can use with Rogers firmware ? (SEE UPDATE BELOW)
Q2): Is there some trick to getting the OTA recovery/boot images I tried....working ? Is there some cache reset of somthing that needs to be done after flashing the stock recovery/boot imgs ? (SEE UPDATE BELOW)
Thanks in advance !

same issue
I too am looking for a rogers ruu or even the M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus) since bugsys page is down.
bump
LRail said:
Hello everyone,
This is my first post so I hope I don't end up being a "typical noob".
I'll try give the full info but keep it concise.
Background:
1) Carrier Unlocked HTC One M7 Originally on Rogers.
M7_UL PVT SHIP S-On RH
HBoot-1.44.000
Radio - 4A.14.3250.13
Open DSP 26.120.274.0202
emmc-boot
2) The phone was working perfectly after being hard reset, and configured without a sim.
3) After it was activated by the telco, the keyboard would would no longer work. Dialpad fine... menus fine... but no keyboard would pop up when selecting text fields. Did a full factory reset, and also tried clearing the Sense Touch data cache via Settings->App.
4) After trying various possible solutions I found online, I finally decided to try start from scratch by installing stock firmware.
So far:
A1) I unlocked the bootloader via HTCDev and used adb to flash CWM Touch Recovery.
A2) Restored the "M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)"
A3) Phone now works correctly at this stage, but is still bootloader unlocked/tampered + CWM Touch Recovery
A4) While I may eventually flash the phone to an official Developer Edition
I would like to reinstall a factory recovery.img, then use revone to get rid of the bootloader "tampered" flag and relock it. (for OTA Updates, and the usual warranty concerns)
A5) I tried flashing both the boot.img and recovery.img from "OTA_M7_UL_JB_50_Rogers_WWE_1.29.631.17_R-1.29.631.4_release_318662" to get back to stock recovery, but I got a Red triangle.
Questions:
Q1): Does anyone know of a stock recovery.img I can use with Rogers firmware ?
Q2): Is there some trick to getting the OTA recovery/boot images I tried....working ? Is there some cache reset of somthing that needs to be done after flashing the stock recovery/boot imgs ?
Q3) If I eventually decide to install the Developer Edition firmware.. will the phone be effectively be a Dev phone ? (OTA updates... factory recovery/locked bootloader... no ID issues in the future..)
Thanks in advance !
P.S. For pure curiousity.... Am I correct in believing that revone can't clear the "tamper" flag and lock the bootloader with the custom recovery ?
Click to expand...
Click to collapse

double post

omgkush said:
I too am looking for a rogers ruu or even the M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus) since bugsys page is down.
bump
Click to expand...
Click to collapse
A lot of the RUUs and nandroid files were apparently "saved" to "Crushalot's" site: htc1guru.com
you can also get the file links in this thread: http://forum.xda-developers.com/showthread.php?t=2428276
I used that nandroid backup. I don't think a Rogers RUU exists (yet).
UPDATE ON MY PROGRESS:
1) I had success with using revone to get my M7 S-Off and removed the tampered flag in the bootloader.
I suspected that SuperSU wasn't working right becaue i hadn't been getting a root permission popup window on the phone.
On I reinstalled SuperSU, I got the root rights popup window when running revone, and it then worked.
2) I have realized that the firmware.zip, which is contained in the OTA update, contains the factory recovery and boot image I needed.
(I kept thinking that it was an incremental update and not a complete image or something, due to it's size.)
Therefore, instead of flashing the images individually, I used the firmware.zip from the OTA update to do a complete firmware update.
3) The Red triangle I was getting was, normal. I couldn't find clear info, so I assumed it was a bad sign because the only time i had seen the factory recovery was when it was upating with a red circle/arrow. So.. I thought the red circle/arrow was the icon you wanted to see.
Eventually I found a thread for a different HTC Phone, that also works for the M7
Result: You can use the volume up + power buttons to enter the recovery once the red triangle appears.
4) After installing the firmware (extracted from the OTA update), I used revone to set the phone back to S-ON, then locked it.
5) The OTA update then automatically installed, as a stock phone would.
6) After the OTA update, for some reason the tampered flag is back. I'll be using revone today to fix that.
UPDATE 2
:
6) After the OTA update, for some reason the tampered flag was back. I unlocked the phone, used revone to to get S-OFF, then used revone to reset the tamper flag and relock the bootloader, and then "fastboot oem writesecureflag 3" to set S-ON.
After 2 reboots the Tampered flag was back !
I'm suspecting that for the tampered flag to stay off I need to keep it S-OFF, which defeats the whole idea of trying to return it to stock.
Any ideas ?
Anyone working for Rogers want to leak an RUU ? hehe

Did you use CWM to flash the firmware.zip in step 2? I'm trying to follow your steps to get back to stock to obtain my stock rogers update but i'm getting lost as to what you're using to flash, recovery or fastboot.

LRail said:
A lot of the RUUs and nandroid files were apparently "saved" to "Crushalot's" site: htc1guru.com
you can also get the file links in this thread: http://forum.xda-developers.com/showthread.php?t=2428276
I used that nandroid backup. I don't think a Rogers RUU exists (yet).
UPDATE ON MY PROGRESS:
1) I had success with using revone to get my M7 S-Off and removed the tampered flag in the bootloader.
I suspected that SuperSU wasn't working right becaue i hadn't been getting a root permission popup window on the phone.
On I reinstalled SuperSU, I got the root rights popup window when running revone, and it then worked.
2) I have realized that the firmware.zip, which is contained in the OTA update, contains the factory recovery and boot image I needed.
(I kept thinking that it was an incremental update and not a complete image or something, due to it's size.)
Therefore, instead of flashing the images individually, I used the firmware.zip from the OTA update to do a complete firmware update.
3) The Red triangle I was getting was, normal. I couldn't find clear info, so I assumed it was a bad sign because the only time i had seen the factory recovery was when it was upating with a red circle/arrow. So.. I thought the red circle/arrow was the icon you wanted to see.
Eventually I found a thread for a different HTC Phone, that also works for the M7
Result: You can use the volume up + power buttons to enter the recovery once the red triangle appears.
4) After installing the firmware (extracted from the OTA update), I used revone to set the phone back to S-ON, then locked it.
5) The OTA update then automatically installed, as a stock phone would.
6) After the OTA update, for some reason the tampered flag is back. I'll be using revone today to fix that.
UPDATE 2
:
6) After the OTA update, for some reason the tampered flag was back. I unlocked the phone, used revone to to get S-OFF, then used revone to reset the tamper flag and relock the bootloader, and then "fastboot oem writesecureflag 3" to set S-ON.
After 2 reboots the Tampered flag was back !
I'm suspecting that for the tampered flag to stay off I need to keep it S-OFF, which defeats the whole idea of trying to return it to stock.
Any ideas ?
Anyone working for Rogers want to leak an RUU ? hehe
Click to expand...
Click to collapse
Tampered will come back the second you flash a recovery. Best to stay S-OFF

I've been in a similar situation where I had to send my phone in for repair and couldn't get the tamper flag to stay off.
I found out it was because I was trying to remove the flag and lock the bootloader and S-On on 1.29.631.17
What I had to do was restore using CWM back to 631.4 then flash stock recovery then remove flag, lock bootloader, then S-On.
The tamper flag should stay off you can try rebooting a couple of times then boot into bootloader to check.
Then I ran the OTA updates and i'm on 631.17 at the moment and my tamper flag is still off.
Hope this helps.
PS. I believe the latest JB4.3 OTA update upgrades the hboot to 1.55 so revone would not work on it. Not planning to try it myself but if anyone can verify this would be great

ysl00 said:
I've been in a similar situation where I had to send my phone in for repair and couldn't get the tamper flag to stay off.
I found out it was because I was trying to remove the flag and lock the bootloader and S-On on 1.29.631.17
What I had to do was restore using CWM back to 631.4 then flash stock recovery then remove flag, lock bootloader, then S-On.
The tamper flag should stay off you can try rebooting a couple of times then boot into bootloader to check.
Then I ran the OTA updates and i'm on 631.17 at the moment and my tamper flag is still off.
Hope this helps.
PS. I believe the latest JB4.3 OTA update upgrades the hboot to 1.55 so revone would not work on it. Not planning to try it myself but if anyone can verify this would be great
Click to expand...
Click to collapse
Thanks for the heads up. If I get a bunch of free time I may just test that after doing a new full backup.
Not sure about the Rogers 4.3 OTA.
I'm running currently the phone with Developer Edition ROM+CID and can confirm that it's 4.3 OTA updates hboot to 1.55.
After the update my phone is still s-off.
I have previously rolled back to an older hboot via a firmware flash.
Since the phone is still S-OFF, I assume I can do that again if needed.

EddyOS said:
Tampered will come back the second you flash a recovery. Best to stay S-OFF
Click to expand...
Click to collapse
Thanks For the reply Eddy.
Recovery flashing sets the tampered flag even if it's a factory recovery from an OTA being flashed ?
I agree on the S-OFF normally.
This was a test to see if I could get it back to full stock for warranty if needed, and S-OFF would not be acceptable in that case.

please help!
PLEASE! I have been trying to get Rogers stock Canada back on my HTC since the day after release lol..
I have this nandroid backup but can't figure out how to flash it... I also can't relock to try and flash a legit version
So pleaseeee how do I install this!!! I am using cwm I tried making a folder called backups in clockworkmod dir but it doesn't pickup the nandroid backup... Help plz!!!!

So what do I do with the M7 CWM Nandroid Backup CID ROGER001 1.29.631.17 2013-06-03.zip
I can't flash it and it won't recognise it as a backup, how do I even install it?
Nobody has mentioned how to use this zip, it isn't a tar file or flashable so what do I do with it?

millarrjm said:
PLEASE! I have been trying to get Rogers stock Canada back on my HTC since the day after release lol..
I have this nandroid backup but can't figure out how to flash it... I also can't relock to try and flash a legit version
So pleaseeee how do I install this!!! I am using cwm I tried making a folder called backups in clockworkmod dir but it doesn't pickup the nandroid backup... Help plz!!!!
Click to expand...
Click to collapse
Esposition said:
So what do I do with the M7 CWM Nandroid Backup CID ROGER001 1.29.631.17 2013-06-03.zip
I can't flash it and it won't recognise it as a backup, how do I even install it?
Nobody has mentioned how to use this zip, it isn't a tar file or flashable so what do I do with it?
Click to expand...
Click to collapse
Simply doing a web search for info would have given you the answers on many many webpages and some youtube videos.
http://bit.ly/1a6d88A
http://bit.ly/1a6ewZ5
Quick answer:
1) Nandroid backups are created and used by the custom recovery "clockworkmod"
2)You need to install a CWM custom recovery (i like the touch version), then unzip the nandroid backup file to the /clockworkmod/backup/ folder. It will create a new folder there. I used the program "Android File Transfer" to copy the files from my laptop to the phone.
3) Once the backup file is on your phone, to restore the backup, you simply boot into recovery and restore the backup as explained in those web pages or youtube videos.
If you have specific things you have tried.... folder names... etc. then ask a question in detail.
You will then have a much higher chance of getting a correct answer (or even an answer at all)
Hope that helps a bit...
Cheers
PS:
millarrjm
FWIW: Simply asking general questions with "pleaseee" and a bunch of exclamation points is a quick way to be ignored (especially in this forum meant for people with some technical skill) See this video (which you should have seen on signup to the forum) for info: http://www.youtube.com/watch?v=JmvCpR45LKA

re.
LRail said:
Simply doing a web search for info would have given you the answers on many many webpages and some youtube videos.
http://bit.ly/1a6d88A
http://bit.ly/1a6ewZ5
Quick answer:
1) Nandroid backups are created and used by the custom recovery "clockworkmod"
2)You need to install a CWM custom recovery (i like the touch version), then unzip the nandroid backup file to the /clockworkmod/backup/ folder. It will create a new folder there. I used the program "Android File Transfer" to copy the files from my laptop to the phone.
3) Once the backup file is on your phone, to restore the backup, you simply boot into recovery and restore the backup as explained in those web pages or youtube videos.
If you have specific things you have tried.... folder names... etc. then ask a question in detail.
You will then have a much higher chance of getting a correct answer (or even an answer at all)
Hope that helps a bit...
Cheers
PS:
millarrjm
FWIW: Simply asking general questions with "pleaseee" and a bunch of exclamation points is a quick way to be ignored (especially in this forum meant for people with some technical skill) See this video (which you should have seen on signup to the forum) for info: http://www.youtube.com/watch?v=JmvCpR45LKA
Click to expand...
Click to collapse
I tried that. CWM version 6.+ doesn't save to the backup folder anymore. And won't read a restore I put in it either... Ie. The rogers off the bugzylawson site.

bklam said:
Did you use CWM to flash the firmware.zip in step 2? I'm trying to follow your steps to get back to stock to obtain my stock rogers update but i'm getting lost as to what you're using to flash, recovery or fastboot.
Click to expand...
Click to collapse
Hello bklam,
Sorry, I missed your question.
No. I used CWM only to restore the "Whampahoofus"' nandroid backup.
That backup is "almost" 100% stock. Unfortunately it contains a custom recovery and won't (in my experience) work for normal OTA updates.
To solve this I decided to extract the factory firmware from one of the old Rogers OTA ("unrar" will extact the files from the OTA), and flash that.
To flash it I used the quick instructions in the 1st post of this thread-->http://forum.xda-developers.com/showthread.php?t=2182823
(I believe there were more details instructions on firmware.zip flashing in another thread but I can't find it at the moment)
Note to other readers: There can be confusion about the word "firmware". Some people use it describe the Rom.
In this case, I'm referring to the hboot, boot and recovery images in a single special file called firmware.zip. I believe in some cases it can also include the radio software too.
If I ever get a chance to get this 100% tested and figured out, I'll post a step by step method.
At this point it's just a overview of what I tried, and looking for other members advice.
Unfortunately, as you can see from my posts, it didn't work 100% for me. It gave me the stock Rogers HTC One Rom/software with OTA updates, but the bootloader still had the tampered flag.
Check out ysl00's post above. He/She evidently had it working 100% without the tamper flag.
Not sure if Rogers has a 4.3 OTA yet, but that might fix the flag since it includes a firmware update along with the OS update.
Post back with your results !

Did you see my above reply lrail? .. just saw u post after thought you might have missed ot!! Thanks so much fpr the help and replies. You are the man!

figured it out.
I thoight the explorer I was using showed all files on phone. TO FIX this issue download root explorer and you can see the other directories... Goto data>media>clockworkmod>backups .. it isnt in the sd dir on your phone.

millarrjm said:
Did you see my above reply lrail? .. just saw u post after thought you might have missed ot!! Thanks so much fpr the help and replies. You are the man!
Click to expand...
Click to collapse
Sorry about that. No I didn't see it until just now. I guess thats the problem with having 20 browser tabs open at once. hehe
millarrjm said:
I thoight the explorer I was using showed all files on phone. TO FIX this issue download root explorer and you can see the other directories... Goto data>media>clockworkmod>backups .. it isnt in the sd dir on your phone.
Click to expand...
Click to collapse
Good to hear. I read your post. I thought..."Is he using a root file manager ?" then read your next post….
I was also going to suggest a guaranteed way to determine where the CWM backups are being stored on a phone.
This way it doesn't matter which version of CWM, which phone or if the back directory exists yet.
Simply create a test backup and see where it goes. Then copy the Nandroid backup that you want to restore, there.

I should mention that I'm currently running my phone as a Developer Edition (Brightstar) 4.3 with OTAs, S-OFF, and unlocked.
It's works perfectly. Only the Carrier ID (CID) needed to be changed. The MID is the same.
I assume that a brightstar RUU will work on it now, even if the phone was locked and S-ON.
I have a few more things I want to tweak on it, then I'll likely make a backup and try restore it to stock rogers again so that I can create a clear how-to.
What's interesting, is that the Developer Edition OS seems to be the same as the Rogers Edition OS (without the rogers apps which can be uninstalled).
The only reason I think it might be a better choice is that the Dev Edition should get OTA updates earlier than the Rogers Edition.
I tried the custom Viper Rom 2.6.x but couldn't get an LTE connection. I suspect that was due to APN settings, but I didn't confirm that.
Anyone got the Viper Rom fully working on a Roger HTC M7 ?

Alright so I've successfully re-installed that nandroid backup and enabled s-off, re-locked, and removed the tampered notification.
When I try to do the OTA update it just hangs at the bug fix1. It default opens and tries to install it through cwm recovery, I've never done any OTA updates before so I assume this is normal?
How can I fix it hanging at bug fix1?

Esposition said:
Alright so I've successfully re-installed that nandroid backup and enabled s-off, re-locked, and removed the tampered notification.
When I try to do the OTA update it just hangs at the bug fix1. It default opens and tries to install it through cwm recovery, I've never done any OTA updates before so I assume this is normal?
How can I fix it hanging at bug fix1?
Click to expand...
Click to collapse
The OTAs don't work with custom recovery. You need the factory recovery

[Q] Restoring OTA update capability

Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc

surgehtc said:
Hi All,
I'm new here and I came here because of some verizon HTC One (M7, cid = vzw001) troubles.
Last year when I got the phone I was intent on making it like a Google play edition phone. I did rumrunner to get s-off and I unlocked the bootloader somehow (I don't remember) and rooted it. I tried flashing a GPE rom but being a noob, I flashed a GSM rom and it did not boot. In a frantic effort to make my phone usable I downloaded a deodexed verizon stock rom and flashed it, and thankfully it worked. I was able to get the Sense 5.5 OTA update after that. A little while later, I installed TWRP because I did not have a recovery at all. Now the Sense 6 update has been out for awhile now and I had tried updating to it but it would take me straight to TWRP and stop. Later on I read about how TWRP stops OTA updates so I installed a stock recovery. I also uninstalled root. Today I looked at my mom's HTC One, and I looked at her stats under Recovery Menu:
hboot: 1.57
radio: 1.13.41.0.421
OS: 4.10.605
I flashed a 1.13.41.0.421 radio and updated somehow the hboot got updated when tinkering and now all those specs match my Mom's, but it is obviously not the same OS. My phone from the settings says it is 4.4.2, 3.11.605.1.
What can I do to essentially return it to fresh out of the box state with restored ota capability? I want to be able to update normally like my Mom's phone and I don't care about root access. I'm not sending it in for warranty do I don't care about turning S-ON or dealing with tampered flags.
Also I'm sort of a noob. I only have a basic idea on how to use fastboot, so a step by step walkthrough would be helpful.
Thanks,
sugehtc
Click to expand...
Click to collapse
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.

majmoz said:
Here is a step by step instructions for returning to stock. There is a Verizon HTC One Forum which has a ton of information much more than this forum. The Verizon phone is very different than the GSM version.
Click to expand...
Click to collapse
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.

surgehtc said:
I read the thread but the link to the decrypted ruu was gone.
---------------------------------------------------------------------------------------------------------------------
I flashed a 1.44 hboot
and the did fastboot reboot-bootloader
it went to a bootloop and I cant use fastboot
When I plug in my phone to the computer
my phone never says fastboot usb
Windows also says "malfuctioning device"
When I press power on
It goes to boot loop
I can enter the recovery menu
I have no idea how to use adb.
I think I'm screwed.
Click to expand...
Click to collapse
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.

majmoz said:
It looks like you got a corrupt hboot flash. I hope you got the hboot from the Verizon forum instead of this forum. This forum is geared to the GSM phones not the CDMA phones. You need to find a hboot for a Verizon phone in zip format to flash in recovery. The hboot controls the bootloader, so this could be the issue.
If you get that straighten out and you are able to use fastboot again, this post has a stock rom and firmware you can flash. Then you would have been back to stock. Spend time in the Verizon forum.
Click to expand...
Click to collapse
I did get it from the verizon section.
But I have no custom recovery and no fastboot
I can't adb sideload either.
What should I do?

Download - HTC One 7 OTA CID=TELST001 - 6.11.841.9

Download link to
OTA for HTC One 7 CID=TELST001 Software update 6.11.841.9 (181.54Mb) - December 23, 2014.
I unzipped this file, extracted the firmware.zip and upgrade my HTC One 7 (Telstra Australia) rooted and s-off.
I am unable to post link to this OTA file.
PM me if you like.
Crtl-Q

This could help me.
Hi,
I have my daughters HTC One M7, which is bricked after she tried to do a system update last weekend. It seems the battery ran out in the process and the handset is now in recovery mode. Telstra were no help to her in getting the problem fixed and sadly there are a lot of photos and other data on the phone.
Although I have an electronic/computing/comm's background I haven't done much with fixing HTC androids (my Sony's seem to not have any problems so far - touchwood) but I am comfortable enough to try and get the handset back up and working. So I have been trying without much success to find an RUU to match the info from getvar all.
: version-main: 6.11.841.9 , modelid: PN0714000 and cidnum: TELST001
Your post looked worth following up, so I have joined XDA so I can get some information.
Can you give me a clue as to where to find this RUU and also, do you have any other info that might help me in recovering the phone? There is quite a lot of information on this interweb about these handsets and similar problems but a lot of it doesn't match what I see on the handset and PC when trying to flash the device.
I am a newbie here so I am not fully conversant with the protocols so please go gentle on me

Hey mate.
Go to the XDA HTC one Australian users thread. @deeevan on that thread has supplied almost all the Telstra OTA's if you go through it. Was about to step you through flashing a stock RUU, but not sure if it's possible if the phone isn't rooted or s-off. Had your daughter got s-off before the accident? It's important that you only flash the RUU that is next in line from 6.11.841.9 or that exact version as you can re brick you phone if you skip an RUU.

Joeisgood99 said:
Hey mate.
Go to the XDA HTC one Australian users thread. @deeevan on that thread has supplied almost all the Telstra OTA's if you go through it. Was about to step you through flashing a stock RUU, but not sure if it's possible if the phone isn't rooted or s-off. Had your daughter got s-off before the accident? It's important that you only flash the RUU that is next in line from 6.11.841.9 or that exact version as you can re brick you phone if you skip an RUU.
Click to expand...
Click to collapse
Thanks for your help Joeisgood, I am having a look at that thread but as yet can't find the right RUU if there is one there. I am new to the forum as well so it isn't so intuitive to me as yet.
The handset is S-On (from getvars) so I am not sure what to do really. There is a lot of information available on fixing a bricked M7 but honestly, so of it isn't easy to understand and a lot of the guides seem to miss important steps (perhaps through a presumption that you already know/have that bit of info) or are aimed toward phones that are actually still working - such as references to turn on/off USB debugging which of course I can't get to. I haven't found a 'complete', easy to follow, step by step guide to cover my situation.
So I guess, that as the handset won't respond to any of the standard recovery options I am going to have to resort to other means. I am cautious about this - sure I can't make the phone worse than it is really, but there is data on it that I would like to try and recover (yes, I have jumped up and down time and again about backing up phone data!). I am not entirely sure that reloading the firmware will save that data anyway but I would still like to try.
So after all my research I am thinking that what I need to do is:
1. Flash a different recovery onto the phone (TWRP seems the most liked)? What version do I require or just the 'latest' one and how do I tell?
2. Get the Android SDK and in particular the ADB/Fastboot tools (I have the HTC tools, which I used fastboot to query the phone with getvars)? Again do I need a specific version for the M7? How do I know which version I am getting?
3. Use adb sideload to get the RUU (which I have yet to find the correct one) onto the phone? Is the Guru_Reset option the way to go if I can find a version, especiall with S-ON?
Anything else I need to consider or have to hand?

1. Flash a different recovery onto the phone (TWRP seems the most liked)? What version do I require or just the 'latest' one and how do I tell?
As well as S-ON, I assume it is also bootloader locked (as your daughter wouldn't have known/cared to unlock it). Unfortunately, flashing a custom recovery/going S-OFF etc requires unlocking the bootloader ... which means the data is wiped
2. Get the Android SDK and in particular the ADB/Fastboot tools (I have the HTC tools, which I used fastboot to query the phone with getvars)? Again do I need a specific version for the M7? How do I know which version I am getting?
You should already have adb along with fastboot. I do know there's issues with Win 8 so do some reading up on that, I don't have that OS so I can't help.
I don't have much experience with stock recovery, so I'm not sure what you can and can't do in it.
- Do the adb devices, adb shell, adb backup, adb pull commands work while in recovery?
- I think there's a menu option like 'install from phone storage'? When you select that, are you able to see the sdcard folder listing - that will at least confirm the data is still intact?
- If possible, try find the OTA file on the phone (look in the Downloads folder) and re-attempt the update.
3. Use adb sideload to get the RUU (which I have yet to find the correct one) onto the phone? Is the Guru_Reset option the way to go if I can find a version, especiall with S-ON
More bad news, with some hope
- HTC have never issued an RUU (which would wipe the phone so you don't want that) for any Australian version. But users have captured the OTA updates which will patch a phone to the next version
- All the files I uploaded are x.x.980.x while Telstra is x.x.841.x. They will not work on this phone.
- Flashing the Guru Reset requires a custom recovery which requires unlocking your bootloader which requires wiping data :-/
- Try sideloading the OTA from Qhaz. It may not work as you are already on that version, you may need to find the 7.x.841.x OTA

deeevan said:
1. Flash a different recovery onto the phone (TWRP seems the most liked)? What version do I require or just the 'latest' one and how do I tell?
As well as S-ON, I assume it is also bootloader locked (as your daughter wouldn't have known/cared to unlock it). Unfortunately, flashing a custom recovery/going S-OFF etc requires unlocking the bootloader ... which means the data is wiped
2. Get the Android SDK and in particular the ADB/Fastboot tools (I have the HTC tools, which I used fastboot to query the phone with getvars)? Again do I need a specific version for the M7? How do I know which version I am getting?
You should already have adb along with fastboot. I do know there's issues with Win 8 so do some reading up on that, I don't have that OS so I can't help.
I don't have much experience with stock recovery, so I'm not sure what you can and can't do in it.
- Do the adb devices, adb shell, adb backup, adb pull commands work while in recovery?
- I think there's a menu option like 'install from phone storage'? When you select that, are you able to see the sdcard folder listing - that will at least confirm the data is still intact?
- If possible, try find the OTA file on the phone (look in the Downloads folder) and re-attempt the update.
3. Use adb sideload to get the RUU (which I have yet to find the correct one) onto the phone? Is the Guru_Reset option the way to go if I can find a version, especiall with S-ON
More bad news, with some hope
- HTC have never issued an RUU (which would wipe the phone so you don't want that) for any Australian version. But users have captured the OTA updates which will patch a phone to the next version
- All the files I uploaded are x.x.980.x while Telstra is x.x.841.x. They will not work on this phone.
- Flashing the Guru Reset requires a custom recovery which requires unlocking your bootloader which requires wiping data :-/
- Try sideloading the OTA from Qhaz. It may not work as you are already on that version, you may need to find the 7.x.841.x OTA
Click to expand...
Click to collapse
Thanks Deevan.. all useful information and much appreciated as there are lots of different comments and advices out there, hard to know which one is correct.
1. Yes, the phone is Locked and S-ON - never any need to change it until this failed update.. From your comment do I assume that unlocking the phone will wipe all the data? Am I able to sideload an OTA with it locked and S-ON?
2. I am using Win 7 to do all this. Yes, adb is in the same folder as fastboot. Trying the adb devices command in recovery mode returned zilch (nothing lested). I haven't tried those other commands but I will do. Going into Fastboot in recovery I do get a fastboot usb indicator and fastboot devices command returns the handset listed. That is why I was wondering if I needed to unlock it or use something like TWRP to get more recovery options. The Install from Phone storage did nothing that I could see just back to the exclamation mark in a triangle screen.. none of the stock recovery options did anything else.. Maybe the data is already wiped? If it's gone then it's gone. The bright side is that then opens up more options for me to get the handset working again I guess?
3. OK, I will stop looking for an RUU and hunt an 6.x.841.x or 7.x.841.x OTA instead or is the Guru_Reset a better option - there is no need for anything other than what is on the stock device really. A very basic user.
Thanks again for offering your advice, I appreciate it.

A Guru Reset (if one existed for a Telstra phone) is a custom ROM (which just happens to install stock files) and can only be flashed via custom recovery, which you do not have. You can try sideloading an OTA (you can do this locked because it's an official signed package), anything else requires unlocking your bootloader which may affect your warranty with no guarantees it enables you to do anything that would fix the phone. Corruption is highly likely if it died halfway through updating.
If the data is gone, I would accept the replacement phone and go nuts playing with that

[Q] REPUBLIC XT1049 Custom ROMs

I have a Republic Wireless Moto x (XT1049) with an unlocked bootloader, and knowing how rare it is (literally 0 support on any thread/site/country), I'm still going to ask a few questions, maybe start a band of RWers with unlocked Moto Xs that will only survive by sticking together/cuddling for warmth.
Before anyone starts to disbelieve me, I do have an xt1049 (not confusing it) with an unlocked bootloader (not confusing it with simply being rooted). I achieved this by purchasing a $25 license for SunShine by the jcase crew, and it worked wonderfully for whoever is out there, looking to unlock you xt1049. Why did I want to fork out 25 bucks for this? I started to hate the grind with towelpieroot+xposed every time I turned my device on, plus things like Viper4Android (among others) don't work well with temp roots, plus no write protection off, which has its purposes.
So on to my questions, (1) are there any custom ROMs designed for XT1049? (Probably no, so before you tell me no, (1a) are there any that work with my model?)
(2) If no one knows 1 or 1a, theoretically, what would happen if I flashed a ROM, say, CM 11/12, onto my phone? Please, to avoid a clutter of responses that consist of "idk probs no," have some level of confidence before answering.
For the theorists, Republic has a bunch of republic things going on in the background for the plural wifis to work correctly, how would these services (wifi calling/stuff) be affected, but also how would more universal things (moto x line specifically, but universal across carriers)? I don't know a whole lot about carriers because I have a serious phobia of letter combinations like CDMA and LTE, but to help understanding the "universal things" I mentioned, looking at the CM11 download page, one ZIP file can be used to flash the XT1053, XT1056, XT1058, XT1060, XT1055, you get the point. OK you got me, to refine it down,(3) I'm just trying to get a complete understanding of what would happen without trying it. I might/probably/would try it some other day, I have a load of college on my plate so if I have to undo anything (another question: (4) would I be able to revert to republic stuff if I have the correct zip, or what would have to go wrong so that I wouldn't be able to get to my bootloader/recovery?) I don't pay my phone bill, and my pops would be pissed if he read this so that's why I might not want to test it, but if there is a way to return I will be ballsy anyway.
(5) A question that I've had for a while but I never needed it answered, bootloaders remain unlocked after an update, right? My old phone (RIP HTC design 4g ) lost support at 4.2 and I never updated it the entire time it was rooted/unlocked. My moto on the other hand has 4.4.4 coming out soon and yeah I don't know the answer to it. I think it's implied it stays unlocked, but no one ever says it directly...
Well, thanks if you made it this far! And I would link whatever I could but I am a new user to this site and I'm restricted, you can just look up Sunshine jcase if interested.

Hi, this is my first time posting on xda, so I apologize ahead of time if I don't do it correctly. I'm also very interested in what can be done with a Republic Wireless Moto X (2013) in order to update to 4.4.4 and still be able to use TowelPieRoot and Xposed. I also looked at the SunShine unlocker but have not tried it yet. I'm currently on 4.4.2 and I just go the update notification today for 4.4.4 (much later than my wife's phone, which does not have TowelPieRoot or Xposed). Just wondering if you had any success with updating and still remaining unlocked and able to use TowelPieRoot and Xposed. Thanks for any feedback!

Unlocked boot loader...
Today I unlocked the boot loader on my Republic Wireless XT1049, since they were trying to force me to upgrade to android 4.4.4 from 4.4.2, and I realized that running Sunshine on 4.4.2 would be my last opportunity for unlocking the boot loader, before upgrading. I haven't yet rooted or updated to 4.4.4. Have either of you upgraded to 4.4.4 android with an uplocked boot loader, and re-rooted? Is there anything different about root in 4.4.4 vs 4.4.2, if you have an unlocked boot loader? Would the "Rooting Unlocked Bootloader" instructions in this guide work in android 4.4.2 and/or 4.4.4? Or, would Sunshine SUInstaller make that unnecessary? (Hopefully SUInstaller would work in 4.4.4...)

I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.

bstevens23 said:
I'm on 4.4.2 with an unlocked bootloader from when the china man was giving out unlock codes. Having my code guarantees that I can unlock my bootloader even after locking it again for an update. I'm not sure how Sunshine works but be careful before taking the 4.4.4. update and do lots of research before doing anything to your device.
Click to expand...
Click to collapse
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
bstevens23 said:
To answer some questions:
CM11 and CM12 will flash fine. The problem you'll have is a loss of phone functionality. With Republic, their app is baked into their custom ROM. But you can use it like a tablet and get a feel for what lollipop will look like on our phone. Make sure you have a nandroid backup or you'll lose everything. CM11 requires a wipe before it will install and CM12 requires you have CM11 (at least it did the last I checked) so you'll want to make sure you have a backup so you can get your working RW ROM back. Otherwise you'll have to flash the Stock RW ROM and start from scratch.
I've done lots of digging and have been able to get the Republic app working on CM11 and CM12 but the functionality is still missing. My tweaks allow texts on CM11 but it's from the "hidden number" not the RW number and the formatting is messed up upon receiving a message. Calls don't work at all on either ROM.
I posted a thread in General with my instructions to get the app working. I'm hoping someone with more ROM knowledge than myself can take a look at the RW Stock ROM and see what else needs to be moved into a CM ROM to give us functionality. I tried moving everything over and skipping duplicates and now I've seriously messed my phone up and will likely have to relock, unlock, flash TWRP and hope I can restore from my TWRP backup.
I've only tried CM11 and CM12, I have no idea how another ROM will affect our phone. Chances are you'll end up in an endless boot after flashing. You could brick the phone though, or end up in a situation like I'm currently in.
Click to expand...
Click to collapse
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.

gxdaspark said:
Thanks for the warning about upgrading. I still haven't decided to allow my phone to upgrade to 4.4.4 android, but the most immediate issue I face with not upgrading is that my phone automatically downloaded the update, and now it is incessantly prompting me to install it. I have found any way to stop the annoying prompting. I would rather wait before updating, because there are always details you don't know about such upgrades, and I have no pressing need for the upgrade, except that ultimately I would like to be able to root my phone, also allow for writing to the system partition, so that recording calls would be possible.
You raise a good point in mentioning your capability to lock and unlock the boot loader. As far as I know Sunshine only unlocks the boot loader. I haven't seen that it provides any code or other means for re-locking it. It is also my understanding that technically there are 3 possible locking states of the boot loader. The factory state not only being locked but also indicating that it was never unlocked. It's my understanding that once a boot loader is unlocked, it can be re-locked, but never restored to the factory locked state that indicates it was never unlocked. That said, I don't know whether it matters if the boot loader is unlocked when running the Republic Wireless upgrade. In other threads I had read claims that once a boot loader is unlocked, that it should remain unlocked after OS upgrades, and as such, in a state that would allow for rooting. But, I am far from an expert on that.
Click to expand...
Click to collapse
I have yet to update to 4.4.4 because I've heard of people having problems with Messenger after the update. I'm waiting to see how my wife's phone functions on it before I make the leap and get the stock recovery back to take the OTA. Until then, I get the obnoxious update warning constantly as well. I could probably freeze the app with Titanium, we'll see if it bothers me enough in the next few days. I'm not sure if the bootloader will need to change for the update as I've only ever had 4.4.2 since I was bootloader unlocked. I know flashing the stock recovery is needed and I feel like that may require a relocked bootloader. As far as I know, from a software/OTA side at least, relocked and locked are equal. Republic/Moto would care about relocked but I don't think the system throws any flags for taking stock software updates because of it.
I hope there will be others who are willing to collaborate in your endeavors to reverse engineer the ROM that you are working on. Are you pursuing that because nobody has been able to root a Republic Wireless XT1049 on android 4.4.2 with a ROM? It seems that the original poster found some way to root 4.4.2 with his unlocked boot loader. I would be interest to know how he did that.
Click to expand...
Click to collapse
I'm pursuing this because I want CM12 to test out Lollipop since I have no idea when Republic is going to push it out to us. I haven't heard of Sprint getting soak tests yet and we're typically 2-3 months behind Sprint. Waiting until May when Google I/O takes place will be difficult for me, especially if they break their current trend and announce the next version of Android.
My goal is much more ambitious than just CM12 though. I got the Republic app to recognize CM11 as native, meaning if someone can figure out which radio portions I'm missing and get the phone functioning as if it were the Republic ROM, we would not be restricted to just the stock ROM/software anymore. I've been an Android user for a few years now and I've always had the ability to flash whatever I wanted if it was available for my device. Since joining RW, I'm extremely restricted. I have 1 ROM option, which is only helpful because it allows Xposed. But I no longer have the ability to test the newest version of Android whenever I please, or to give a custom ROM a spin if I feel like it. If we can figure out what makes the RW ROM function properly, that wouldn't be a restriction anymore. That's my goal.
Unfortunately, I have no idea what I'm doing. The best I can do is compare files and try pulling random things. I'm hoping someone with more ROM knowledge will be able to take a look at the RW ROM and see which pieces I'm missing. I feel like CM12 is going to be a bit more complicated though, and might not be possible at this time. We'll see though. I know something is getting screwed up with the MEID because the Republic app doesn't recognize an MEID at all. How to go about fixing that? Beyond me.

step-by-step, 4.4.4 root
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. Double check to make sure USB debugging has been enabled. Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. At the command prompt type: mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img to flash the custom recovery to your Moto X.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
12. You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!

PackerDroid said:
I think the steps would be: first Sunshine, then 4.4.4 OTA, then root, then Xposed. Is that correct? After I unlock with Sunshine, will my phone still prompt me to update to 4.4.4? Or do I need to need to download 4.4.4 and then flash it? After Sunshine, do I FIRST need to flash 4.4.2 custom recovery? If so, where can I get that? I should probably get a copy of that anyway, even if I don't need it now.
It seems pretty easy overall, but I think I need to refer to a step-by-step guide to make sure I do all of this correctly. If I start the guide below, can you please be so kind as to make corrections for me? Add, remove, or change steps? Thanks!!! Here it goes, this is my best guess at the steps I need to take:
1. Go to theroot.ninja and complete the unlock process.
2. Download and install Android SDK on PC (installer_r24.1.2-windows.exe).
3. Download and install Motorola Device Manager on PC.
4. Get mfastboot.exe and place it in the same directory as fastboot (fastboot is in the \sdk\platform-tools subdirectory of the Android SDK).
***Do I just drag this .exe to the said folder on my PC?***
5. Get the TWRP for Moto X 4.4 custom recovery for kit kat and place it in the same directory as fastboot.
6. Enable USB debugging and download SuperSU
7. Double check to make sure USB debugging has been enabled. Put your unlocked Moto X into bootloader mode by pressing the Volume Down button and then the Power button. Hold for about 3 seconds and release and you should be in bootloader mode. Connect your Moto X to your PC via a USB cable.
8. Open a command prompt on your PC and change directory to the folder where mfastboot.exe is.
9. At the command prompt type: mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img to flash the custom recovery to your Moto X.
***Is this the version of TWRP I need to root 4.4.2? What about 4.4.4? Or do I just flash the 4.4.4 OTA on top of 4.4.2?***
10. After the custom recovery has been flashed to your Moto X, at the command prompt type: fastboot reboot-bootloader to reboot into the bootloader.
11. Unplug your device from your PC. Then get into recovery mode by pressing the Volume Down button to highlight recovery mode and pressing the Volume Up button to select the recovery mode.
12. You should now have booted into the Team Win Recovery Project custom recovery. Click on Install to install SuperSu. Scroll down to find the sdcard and select it. Then scroll down to download and select it. Select the SuperSU zip file and swipe to install.
*** I also saw this:
"For new users who have only unlocked their bootloaders, flashed TWRP and rooted, then only make use of apps like RootExplorer, QuickBoot(reboot), Adfree, Wifi Tether for Root, etc.. that do NOT modify /System, the easiest way to take the OTA is to...
download the SBF/FXZ for your carrier and the Software Version currently on your phone. Do NOT use a lower Software Version, or the SBF/FXZ for another carrier or you will risk bricking your phone!!!
unzip it.
boot the phone into fastbootAP/bootloader mode
use mfastboot to flash the recovery.img to your phone - mfastboot flash recovery recovery.img
immediately reboot into fastbootAP/bootloader - mfastboot reboot-bootloader
select recovery.
once you've entered stock recovery, you can reboot back into normal system.
take the OTA when it gets to your phone.
you will likely remain rooted, and its optional to flash your custom recovery back on there via mFastboot
However, if you are running Xposed, did a wifi tethering hack, edited build.prop, DELETED bloat from your phone, your phone will fail the OTA Update's validation checks and it will fail. In that case, you can boot back into fasbootAP/Bootloader mode, use mfastboot to flash system.img (mfastboot flash system.img ) from the SBF/FXZ you already downloaded and unzipped. then reboot ( mfastboot reboot ), and try the OTA again. You will need to re-root by flashing custom recovery (like twrp), and re-install SuperSU."
***Is there any way to break down the whole thing into simpler steps???*** THANKS!!!
Click to expand...
Click to collapse
Were you able to break this down into simpler steps? Did the steps work for you?

[Q] Basic steps from unlocked to Sprint updates

I'm overwhelmed by all the shop speak regarding the android OS. Everything's an acronym, and everything sounds vaguely similar to everything else. Stock recovery, stock rom, stock firmware, factory reset, I'm a computer literate person, and I don't know what the difference is between any of these things, I only know that they're serious.
So here's my situation:
I have a Sprint HTC One M8, unlocked with s-off.
I have adb installed on my PC, TWRP and Super SU installed on my phone,
I need to install system updates, first to install KitKat 4.4.4, then immediately after, Lollipop.
When I go to install
my phone boots into TWRP mode
I go to update
select the update zip
swipe to flash
and get "updating partition details... failed"​
I gather that I'm supposed to first restore to a stock recovery, and I think I found the correct one here, but the instructions I'm finding are very convoluted. I need to either unlock or lock my bootloader using adb. I need to flash one of the downloads on that page, but I'm not certain which one, how to flash it.
I understand that this isn't a forum for newbies, but that's just the thing, I'm not usually lost when it comes to this stuff, which makes me think many others are probablylost as well.
Can anyone clearly explain the steps I need to take, with a minimum of acronyms, to do whatever you do with a stock recovery to then be able to install Sprint updates?
I posted this question in a different way back in November and had one member keep posting unhelpful answers until the whole thread got hijacked by piggyback questions. I've also found step by step guides that each conflict with one another. One may have 5 steps and the other may have 12, and in one way or another they've always gone off the rails until they no longer seemed to apply to my use case.
If you can help, thank you.

Dr.Zee said:
I'm completely overwhelmed by all the shop speak regarding the android OS. Everything's an acronym, and everything sounds vaguely similar to everything else. Stock recovery, stock rom, stock firmware, factory reset, I don't know what the difference is between any of these things, I only know that they're serious.
So here's my situation:
I have a Sprint HTC One M8, unlocked with s-off.
I have adb installed on my PC, TWRP and Super SU installed on my phone,
I need to install system updates, first to install KitKat 4.4.4, then immediately after, Lollipop.
When I go to install
my phone boots into TWRP mode
I go to update
select the update zip
swipe to flash
and get "updating partition details... failed"​
I gather that I'm supposed to first restore to a stock recovery, and I think I found the correct one here, but the instructions I'm finding are very convoluted. I need to either unlock or lock my bootloader using adb. I need to flash one of the downloads on that page, but I'm not certain which one, how to flash it.
I understand that this isn't a forum for newbies, but that's just the thing, I'm not usually lost when it comes to this stuff, which makes me think many others are probablylost as well.
Can anyone clearly explain the steps I need to take, with a minimum of acronyms, to do whatever you do with a stock recovery to then be able to install Sprint updates?
I posted this question in a different way back in November and had one member keep posting unhelpful answers until the whole thread got hijacked by piggyback questions.
If you can help, thank you.
Click to expand...
Click to collapse
First things first, this is a forum for all kinds but there is a Q&A section.
On to the update.
The first thing you need to do is boot to fastboot and type "fastboot oem lock" without quotes and press enter.
The device should be locked and from there you should be able to run the RUU (ROM update utility) that comes directly from htc, no need to do the incremental updates from KK (kitkat) to LP (Lollipop) unless you are looking to do something specific on a certain radio or firmware.
No need to flash stock recovery if you run the RUU, only lock the bootloader.
The RUU files are found on the HTC website or in this thread: http://forum.xda-developers.com/showthread.php?t=2729173 and you should find the directions there, just follow the S-on procedure if you are S-ON, you would know because at this point the only way to obtain S_OFF is to pay 25$ to use the Sunshine app.
This might be able to be moved to the Q&A by a mod and there are plenty of users and devs around here willing to help, just ask questions and try to follow the directions first.

dopy25 said:
First things first, this is a forum for all kinds but there is a Q&A section.
On to the update.
The first thing you need to do is boot to fastboot and type "fastboot oem lock" without quotes and press enter.
The device should be locked and from there you should be able to run the RUU (ROM update utility) that comes directly from htc, no need to do the incremental updates from KK (kitkat) to LP (Lollipop) unless you are looking to do something specific on a certain radio or firmware.
The RUU files are found on the HTC website or in this thread: http://forum.xda-developers.com/showthread.php?t=2729173 and you should find the directions there, just follow the S-on procedure if you are S-ON, you would know because at this point the only way to obtain S_OFF is to pay 25$ to use the Sunshine app.
This might be able to be moved to the Q&A by a mod and there are plenty of users and devs around here willing to help, just ask questions and try to follow the directions first.
Click to expand...
Click to collapse
Thank you very much, I'll run through these steps.
Question, I installed a couple firmware patches after I got s-off. when this is finished, will those be overwritten? Will my phone still be s-off, or would I have to pay to have that done again?

Dr.Zee said:
Thank you very much, I'll run through these steps.
Question, I installed a couple firmware patches after I got s-off. when this is finished, will those be overwritten? Will my phone still be s-off, or would I have to pay to have that done again?
Click to expand...
Click to collapse
So you are S-OFF, OK.
No, the S_OFF is tracked by the device I believe, and would still be able to be used without having to pay again. I have read that many places.
I would not do the full RUU if you are s-off, but the thread I linked has zips to flash firmwares and roms and keep S_OFF. I am still on so I have no experience with S-OFF but I would not lock the bootloader until another s-off user confirms.

dopy25 said:
So you are S-OFF, OK.
No, the S_OFF is tracked by the device I believe, and would still be able to be used without having to pay again. I have read that many places.
I would not do the full RUU if you are s-off, but the thread I linked has zips to flash firmwares and roms and keep S_OFF. I am still on so I have no experience with S-OFF but I would not lock the bootloader until another s-off user confirms.
Click to expand...
Click to collapse
I got a little wreckless and just went ahead and tried it. Everything worked. I'm running Lollipop, I still have S-off, and I just re-rooted through the HTC dev program. The firmware patches I installed were overwritten, but, you can't have everything.
Thank you very much, I'd been dealing with system update messages for months.

Dr.Zee said:
I got a little wreckless and just went ahead and tried it. Everything worked. I'm running Lollipop, I still have S-off, and I just re-rooted through the HTC dev program. The firmware patches I installed were overwritten, but, you can't have everything.
Thank you very much, I'd been dealing with system update messages for months.
Click to expand...
Click to collapse
What do you mean by patches? Just specific bits of firmware? I don't really know of any benefits to having specific bootloader or hboot or radio over another. It used to matter back in the day but I think it is best to have the most updated if you are going to run a newer ROM anyway.
Also, if you are S-OFF you can always downgrade any of them at any time. So if any of the patches you had before gave you any benefits you can always run them again.
Glad you got it taken care of. On any note, if you muck something up you can always run the RUU to get back to stock. HTC did us a huge favor with those.

dopy25 said:
What do you mean by patches? Just specific bits of firmware? I don't really know of any benefits to having specific bootloader or hboot or radio over another. It used to matter back in the day but I think it is best to have the most updated if you are going to run a newer ROM anyway.
Also, if you are S-OFF you can always downgrade any of them at any time. So if any of the patches you had before gave you any benefits you can always run them again.
Glad you got it taken care of. On any note, if you muck something up you can always run the RUU to get back to stock. HTC did us a huge favor with those.
Click to expand...
Click to collapse
It's a patch that adds Harmon Kardon sound. Then I incorrectly remembered an app that enables Snapdragon audio (which is far superior to HK sound) but that's not firmware, you just need a rooted phone to be able to drop it into the system folder.