Database Develop

[Q] HTC M7 Dev Edition *Factory Rom Lost*

Hey everyone new poster to the forums here . Have a question about loosing the stock ROM for my HTC M7 Dev edition. I made the backup but I think when I formatted I formatted more then I should have because when I pull up TWRP recovery mode to restore a backup nothing is listed in the window. However when I go into the internal storage in windows on my computer with the phone connected and look inside HTC One\Internal storage\TWRP\BACKUPS I found a folder called HT34GW9xxxxx and a sub directory with a date on it and it looks like the date that I did the flash in the first place. That folder also has 13 files in it equaling out to 4.25GB in size. So basically what I'm getting at is how come I can see this folder here but not in recovery and even if I could see it in recovery this seems like it's not large enough to be HTC Sense 5.0 according to this thread and the downloads attached to it.
http://forum.xda-developers.com/showthread.php?t=2248997&highlight=nandroid
Also speaking of that thread considering the original M7 Dev rom is gone can I use that thread to restore my phone even though I am using TWRP and not clockwork. I'm not the greatest at these type of things, I don't want to brick my phone, and I never have enough time invest in this stuff. If I knew this was going to happy I probably wouldn't have done it in the first place lol.
Thank you in advance and sorry if this has already been talked about, I did a search but I must have skipped over it if it was already out there :\.

dont worry if u have htc one 64gb dev edition go to htcdev..com and download ruu file lock the bootloader and run ruu thats all

Follow up
ccpzcp said:
dont worry if u have htc one 64gb dev edition go to htcdev..com and download ruu file lock the bootloader and run ruu thats all
Click to expand...
Click to collapse
Thank you for the help. A follow up question would be is there a place to get someone's previous backup and download it like the link I put up in the previous posts user did. I really don't want to lock the boot loader and I would love to just be able to easily get Cyanogenmod back on the phone easily. Reason being is that right now the Cm camera just isn't up to pay with the Sense camera software and if I go to an event like I am tonight I would like to be able to swap back and fourth.

TWRP and CWM backups aren't compatible with each other. You'd have to flash the relevant recovery to use a corresponding backup.
You still have your backup though. You said as much in your OP. You just need to go into TWRP settings and specify the default location for your backups.
As mentioned above however, you can just flash the official RUU to return to stock

Thanks a ton!
Just wanna say thanks to the both of you for your help. I went with option 2 for now because I want to switch back to CM after the Cardinals MLB game tonight. I never lost the backup and you were right I just had to find the folder. It was weird I didn't see any button to search for a folder kinda odd how TWRP is layer out in that interface. Yet I found the backed up file and took about 10 minutes from start to finish. The device is still unlocked to so I can reflash CM when I'm ready.
A little off topic but does anyone know what the difference between the GSM Cyanogenmod ROMs and the AT&T ROMs are? I have the Dev version but flashed the AT&T version and it ran fine made calls and had no data transfer issues at all.

Ok so I actually started having issues after that last post. What was happening was I kept getting this HTC system update my guess the Camera software update but whatever. So I clicked on the update now and it downloaded like normal then reboot. After it reboot it booted into TWRP recovery well at that point I didn't know what to do so I just went a head and rebooted into System. Well here is where the issue started it said again system update avalible ok great install, same deal it just booted back into TWRP after the download. Back into system I went and again same thing.
At this point I desided to go into TWRP and do a system restore and I thought that worked cause it wasn't notifying me immediately after the launcher loaded to install the update. So I checked for it manually and of course there was one. Tapped on Install it downloaded and asked to reboot so I did...
SAME ISSUE AHHHHGGG! Lol
This will be the end of me haha.
Is there something I'm missing here? Can I not have root access or a a third party boot loader like TWRP or both modifying the system. What am I missing?
Ok thanks again, sorry for the multiple posts I'm just so frustrated at this point.
Sent from my HTC One using xda premium

This my very wild guess. Try flashing stock recovery first and then install the OTA update again. That's just my wild guess I'm not saying it will 100% work.

No luck
shadowboy23 said:
This my very wild guess. Try flashing stock recovery first and then install the OTA update again. That's just my wild guess I'm not saying it will 100% work.
Click to expand...
Click to collapse
Nope no luck

Hopefully this helps..
What I did find was this link here...http://forums.androidcentral.com/htc...ml#post2827047 that's where someone else is having the same issue but on Sprint I'm guessing. So that doesn't really apply to me. However a poster further down the thread gave another link to all these "nandroid?" files. I'm not really sure what a nandroid is haha I'm such a noob at this. Basically what they are saying is that unrooting it then i guess somehow putting this "nandroid" file on it somehow. Anyone have any idea on this. I'm terribly sorry for my noobishness but I'm trying to learn all this and it's really frustrating at first..
Here's the link to the nandroid files. http://forum.xda-developers.com/show....php?t=2207874 funny thing is that I actually found that link on Android Central website so that I could come back here and repost about it again heh. Anyways does that look like something that might fix the issue that I'm having?
Even if this file does help I have no idea what to do with it but that first link seemed to have some video's attached to it although I worry about following them because it's for Sprint and I really don't want to brick my phone. (another reason I am being so careful) You pay over 600 dollars for a device you tend to be super careful with anything you do with it.

Nvidiafanboy said:
Nope no luck
Click to expand...
Click to collapse
Sorry about that.

All fixed!!
Ok so I got it. I ended up finding this http://qbking77.com/development/how-to-unrootunbrick-the-htc-one-to-stock-2/
Worked great fixed everything. Linked to the RUU on HTC Dev website also so its official.:good:
So basically if Anyone need to restore to factory from a mess they have made follow this guide it works perfectly and he does an execelent job of describing how to do it in a video he posted step by step.

One on the verge of bricking! Help would be appreciated.

Sooooo today I read this article (http://www.androidcentral.com/google-play-edition-htc-one-bootloader-and-recovery-now-available) and I was siked to try to get vanilla android on my One. Unfortunately, I'm no whiz when it comes to these things and usually just try and follow step by step directions I find on forums. I found this page (cdforum.xda-developers.com/showthread.php?t=2316726) and in all my excitement I completely missed where it said S-off is required and began the process. Booted the phone into bootloader, flashed the zips, and ended up with "error: cannot load 'descenpet_HBOOT_1.54_2.24_MOD'. Now I'm stuck with my phone still plugged into my computer only showing the black screen with the HTC logo. I read on to find out if I mess with it anymore it could possibly be bricked...not something I want.
Some quick facts, it's running stock sense software which came on it when I bought it and I rooted it a month or two ago. I hadn't even upgraded the software version to .10 (instead I still have the .7 at the end). Any kind of help would be great and please feel free to ask questions because I'm completely out of my element here and I don't what else you guys need to know in order to help me out. Thanks anyways!

its a bad idea to flash GSM firmware onto a CDMA phone... I would just RUU the whole thing back to stock

RUU may be your best option, but if you managed to flash the modified hboot/bootloader with S-ON you may be hosed OP. S-ON won't let the tampered boot-time code run if you overwrote it. Look in the forums for the RUU guide (search tool) and give it a go, but it doesn't look great.

cowkong said:
Sooooo today I read this article (http://www.androidcentral.com/google-play-edition-htc-one-bootloader-and-recovery-now-available) and I was siked to try to get vanilla android on my One. Unfortunately, I'm no whiz when it comes to these things and usually just try and follow step by step directions I find on forums. I found this page (cdforum.xda-developers.com/showthread.php?t=2316726) and in all my excitement I completely missed where it said S-off is required and began the process. Booted the phone into bootloader, flashed the zips, and ended up with "error: cannot load 'descenpet_HBOOT_1.54_2.24_MOD'. Now I'm stuck with my phone still plugged into my computer only showing the black screen with the HTC logo. I read on to find out if I mess with it anymore it could possibly be bricked...not something I want.
Some quick facts, it's running stock sense software which came on it when I bought it and I rooted it a month or two ago. I hadn't even upgraded the software version to .10 (instead I still have the .7 at the end). Any kind of help would be great and please feel free to ask questions because I'm completely out of my element here and I don't what else you guys need to know in order to help me out. Thanks anyways!
Click to expand...
Click to collapse
you may just need to flash the kernel for .10, don't know your whole situation.

[Q] Please help, oh wise & experienced ones of XDA

Hi folks. So I haven't been on this site in a good while, but I've come across an issue that requires the help of someone with wisdom about the issue at hand. Up front, you should know that I'm not familiar with the whole rooting thing and even the technical terminology of most of it.
A little back story...I've recently purchased a Sprint HTC One M8 from someone. Everything works fine with the phone, there's nothing wrong with it at all. It's rooted and has s-off. I bought it that way. I asked the seller if he could unroot and take the phone back to full stock before the deal, but turns out he had someone else root and soff for him so he wasn't able to take it back to full stock. But he put the stock ROM back on it for me, though it's still rooted and has s off. I've provided pictures for those who are in the know to see for yourself, because I don't know what any of that software info means on those screens.
Here are my questions, and I'll put them in numerical format so there won't be any confusion in replying back:
1. From what you see in the pictures provided, are you able to to tell if it is in fact on the stock ROM or not?
2. I am receiving notifications that an official OTA update is available from Sprint/HTC:
A. What are the consequences of downloading and installing the OTA update(s)?
B. Will s-off be effected?
C. Will the root block the update from happening, or will it work fine since it's on stock ROM and has s-off?
D. Will it brick my phone if I update, or is there a chance at all that my phone will get bricked or stuck?
3. If I want to revert my Sprint M8 back to full stock (unroot and s-on), or maybe even put on a different ROM, how can I go about doing it?
4. What benefits do I have in keeping my phone in the state that it is currently in, that is, having rooted and s-off? And how can I take advantage of those benefits?
5. If I want to flash a different ROM or revert back to full stock (unroot and s-on), will it delete everything off my phone, including specifically my synced Gmail accounts?
6. As you can see in the picture with the 3 Android figures, at the top it says "tampered" and "unlocked." Does the "unlocked" mean that the phone is fully unlocked and can be used on any other service provider network, domestically and internationally?
Sorry about the length of this message, but I know there are some knowledgeable people on here who have wisdom and experience on the issue, so I would greatly appreciate any productive and helpful replies to my questions. If you have any questions for clarification please feel free to ask. Thanks!

If you choose recovery from the menu option in your first screenshot, what happens?

Captain_Throwback said:
If you choose recovery from the menu option in your first screenshot, what happens?
Click to expand...
Click to collapse
Hi Captain. I haven't tried anything because I wanted to seek help first and get answers to my questions before doing anything. That would be much appreciated. I also didn't want to risk bricking since I don't know anything about this stuff. What is recovery, what is it supposed to do?

1. Yes, it appears to be a stock rooted ROM. Appears to be the first update. There have been two since, including the most recent one from this past week.
2.Your software & firmware version will be updated. S-off won't be affected. You simply have to have the stock recovery installed to take the OTA. Taking the OTA won't brick your phone.
3. You can revert to S-on but I'm not even sure why you'd want to. If you want to unroot simply take the OTA after installing the stock recovery.
4. Hit the second link in my sig for more info.
5. If you flash a different ROM yes, your phone will get wiped and you'll need to set up your accounts again. If you take a OTA update your data won't be affected.
6. "Unlocked" means your bootloader is unlocked, plain and simple. See my answer to question #4 for more info.
As far as what recovery is, think of it as a very small and separate OS from the Android OS. It allows for the flashing of .zip files (ROM's, kernels, mods, etc.). It also allows you to back up your entire phone to either the internal storage or micro-SD card, among other things.
Take a look at this thread if you haven't already.

Magnum_Enforcer said:
1. Yes, it appears to be a stock rooted ROM. Appears to be the first update. There have been two since, including the most recent one from this past week.
2.Your software & firmware version will be updated. S-off won't be affected. You simply have to have the stock recovery installed to take the OTA. Taking the OTA won't brick your phone.
3. You can revert to S-on but I'm not even sure why you'd want to. If you want to unroot simply take the OTA after installing the stock recovery.
4. Hit the second link in my sig for more info.
5. If you flash a different ROM yes, your phone will get wiped and you'll need to set up your accounts again. If you take a OTA update your data won't be affected.
6. "Unlocked" means your bootloader is unlocked, plain and simple. See my answer to question #4 for more info.
As far as what recovery is, think of it as a very small and separate OS from the Android OS. It allows for the flashing of .zip files (ROM's, kernels, mods, etc.). It also allows you to back up your entire phone to either the internal storage or micro-SD card, among other things.
Take a look at this thread if you haven't already.
Click to expand...
Click to collapse
Thank you very much Magnum_Enforcer for the detailed and organized response. I will definitely be looking into the links you've mentioned/provided. Ideally, it would be great if I can somehow keep it rooted and have s-off while being able to take OTA updates. From that point I clean learn about and use the benefits from it being rooted with s-off, although I need to keep my Google accounts synced, so no flashing of ROMs for me.
So after reading your reply, I went ahead and tried taking the OTA, and after it turned off, it loaded up in the screen in the pic I've attached to this message. I'm assuming it doesn't seem I have the stock recovery as you said is required to take the OTA. How do I get the stock recovery on my phone in place of this "Team Win Recovery Project" recovery so that I can be able to take the OTA update properly? And will removing the current recovery and putting on the stock recovery effect s-off, root, or my synced accounts in any way?
P.S. I see you're in Birmingham. I actually grew up all over B'ham. Which part of town are you from?

L A Z I Z A said:
Thank you very much Magnum_Enforcer for the detailed and organized response. I will definitely be looking into the links you've mentioned/provided. Ideally, it would be great if I can somehow keep it rooted and have s-off while being able to take OTA updates. From that point I clean learn about and use the benefits from it being rooted with s-off, although I need to keep my Google accounts synced, so no flashing of ROMs for me.
So after reading your reply, I went ahead and tried taking the OTA, and after it turned off, it loaded up in the screen in the pic I've attached to this message. I'm assuming it doesn't seem I have the stock recovery as you said is required to take the OTA. How do I get the stock recovery on my phone in place of this "Team Win Recovery Project" recovery so that I can be able to take the OTA update properly? And will removing the current recovery and putting on the stock recovery effect s-off, root, or my synced accounts in any way?
P.S. I see you're in Birmingham. I actually grew up all over B'ham. Which part of town are you from?
Click to expand...
Click to collapse
That's why I asked you to select recovery in the first place. I could've told you whether it would've worked based on that.
I recognize you wanted answers to your questions, but in order to give you the most complete and accurate answer, all I asked was for you to check your recovery.

Captain_Throwback said:
That's why I asked you to select recovery in the first place. I could've told you whether it would've worked based on that.
I recognize you wanted answers to your questions, but in order to give you the most complete and accurate answer, all I asked was for you to check your recovery.
Click to expand...
Click to collapse
There's no need for quarrel or to take anything personal. It's not as if I ignored you, I replied back to you. I'm here to seek answers and help, I've no interest in disagreements. Sorry if you feel that way. I'm sure you're quite knowledgeable and experienced enough to have been able to tell me the same, if not more. The response I received from Magnum just happened to be complete and informative enough to me to let me know it was ok to try it out. I like to know at least a little about what I'm doing before jumping into something. That's just the way I am, people are different.
I sought help again in my last response though, and if you're still interested in helping, it would be appreciated. If not, I would understand, no worries or hard feelings.

You won't be able to take the OTA with TWRP installed. You can find the stock recovery in the first post of the link below. There are also instructions on how to install it. Once installed you can boot back to the OS and take the OTA.
Stock Backups + OTA's
To answer your other question, I've lived in several different places all over the state over the years but now live in the northern part of Jefferson county, outside of the city of Birmingham (you couldn't pay me to live in the city limits of B'ham).
Sent from my HTC M8

[Q] RUU

Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx

Linkalex1 said:
Hi, I did a lot of things with my One Mini 2 and I actually really don't know what to do anymore... So much options and yet there always seems to be a problem. Let me explain everything.
What I did:
-flashed a custom rom, then went back to a stock rom of this forum
-flashed the dt2w kernel, it messed up my phone so I then flashed the liberty one, which worked
But with the liberty one I had some memory problems, for exemple I couldn't take screenshots... That's why I decided that I wanted to put my phone just as it was when I bought it, I really hope that's possible, by that I mean having official firmwares etc, therefore being able to do official upgrades from my phone (is that what OTA is?).
I looked on internet and it looks like what I need is RUU, as it includes everything (from what I understood)... I know a lot of threads were made about this, but quite a few months ago, so that's why I'm making a new one, and to make things clear.
Also, I downloaded an official kernel from htcdev.com, but each time I tried flashing it with TWRP, it "failed".
So, if you guys have an answer, solution or, in best case, the actual RUU, that would be great.
Thanx
Click to expand...
Click to collapse
Still no RUU's avaiable as HTC wont release them. your best option is to use TWRP backup and restore.
Original stock backup

Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?

Linkalex1 said:
Thank you, but my backup kind of disappeared... I saw your post where there was the "HTC Original Backup.zip", I tried to flash but again it failed... Am I supposed to flash it as a backup?
Click to expand...
Click to collapse
You need to send it as it is to your phone and use TWRP > restore. choose file and done.

Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?

Linkalex1 said:
Thanx so much for answering... I uses the backup you told me to. Although I had to use the "install" option instead of the backup one, it now works perfectly! But how do I know if my phone is "official"? Are the upgrades going to be made straight from the phone?
Click to expand...
Click to collapse
Yes OTA updates should work just fine. just look for updates in settings>about >software update.
you may have one for polaris office.

Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)

arm1e said:
Hi, I just want to check this too before I screw up wife's phone..
She has CM12 on her phone now as I replaced recovery as well as unlocking bootloader. Now she wants it back to stock as too many things crash on her. I get that I can install your backup but what worries me is that other posts have said you need the stock recovery to allow for OTA updates to work and the link to this no longer works.
She MUST have OTA updates or my balls will be removed, so can you please confirm this, but also explain why.
Thanks (on behalf of my testicles and unborn children!)
(Oh, and she wants it unrooted ant the bootloader relocked)
Click to expand...
Click to collapse
Stock Recovery
To unroot just lock bootloader:
fastboot oem lock

How many people took the 5.1.1 and are stuck with the "locked" bootloader

If you didn't know the 5.1.1 update comes with a "locked" bootloader (G920T) that does not allow you to flash custom recoveries. I would like to know what your status is if you don't mind because I think the more people who are stuck like me the more developers will say we need to come up with a fix for flashing custom recoveries issue.

The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops

Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1

mikeyinid said:
The bootloader isn't locked. Twrp just needs to be updated. Won't happen til kernel source for 5.1.1 drops
Click to expand...
Click to collapse
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.

se1000 said:
Did we really need another thread about this?
Edit: Please explain how someone "accidentally" upgraded from rooted 5.0.2 to 5.1.1
Click to expand...
Click to collapse
What I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade

ethanscooter said:
Accidently* wasn't really paying while typing and what I mean by that is if you had no knowledge of the changes in the bootloader and the fact you can't downgrade
Click to expand...
Click to collapse
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"

ethanscooter said:
That is why I put "locked" in quotes and no I am not sure of that the phone blocks any custom recovery installed and I explained in another thread how cf-auto-root is just a recovery that is why it isn't working either.
Click to expand...
Click to collapse
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.

se1000 said:
So what you meant is, "If you downloaded a 1.3GB file and ODIN'ed back to stock just to upgrade and ignored the big bold warning that you couldn't downgrade" OR "If you downloaded a 1.3GB file and ODIN'ed to a new version of android that there was an active thread where it was CLEAR there was no root method"
"Accidentally"
Click to expand...
Click to collapse
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me

mikeyinid said:
You don't have to take my word for it. But I'm telling you, the bootloader is not locked.
Click to expand...
Click to collapse
I understand it isn't locked but what I mean is for the time being it feels like it is locked considering we can't root or install a custom recovery or downgrade.

ethanscooter said:
LOL some people did it look in the Q&A section people are posting things about recovery not being seandroid enabled because of the bootloader for me I was actually in a boot loop so I just downloaded the latest version from Sammobile
OH and sorry for the last typo I thought you were correcting me
Click to expand...
Click to collapse
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.

se1000 said:
Of course people did it, but don't make it seem like you clicked one button and the upgrade went through and now you're stuck. You ACTIVELY went through the upgrade process to force it through.
Plus, you don't need THREE threads on the same subject.
Click to expand...
Click to collapse
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.

ethanscooter said:
I didn't make the 3 threads others did I just responded to all 3. Also the whole point of that one choice in the poll is for people who were expecting a normal tmobile update and didn't get what they thought they would usually tmobile let's you downgrade and you can flash a recovery right away but this time it was different and not a ton of people knew it was going to be different maybe I should've worded it better I am sorry.
Click to expand...
Click to collapse
You have 2 threads in the QA section that are on this same subject.
Look, if you want to have a rooted, custom recovery, custom kernel device, don't be the first to update. That's just how things go.

From the Moderator
Redundant Thread ......... So........
..............THREAD CLOSED...........