Database Develop

Fixing some misconceptions about S-off

Alright, because there is constant stupidity regarding the bootloader security state for HTC devices. I feel that I can clarify and help remove some myths and misconceptions.
Let's start with the most important one:
What is S-off?
S-off is us turning off the security flag stored in the NV RAM of our device. This allows us to flash unsigned files (zips and images) to our device. The difference is stated below of why you need a zip vs an image.
S-off is not root either. Root is just a binary stored in /system and just doesnt get removed if the device has s-off. S-off just means integrity of file system / partitions aren't checked on the device. So this means the two are exclusive of each other from a user standpoint.
HTC IS JUST GOING TO TURN S-ON AND RUIN IT FOR EVERYBODY!
No, they aren't. For a few good reasons, one of which is their own engineers have s-off to begin with.
The @secuflag (S-on/S-off) is there to verify hboots and other various image files on the device to begin with. When we have s-off on a newer device but idiot user decides to turn s-on for whatever reason and we have a modified hboot? The device will brick because you broke its chain of trust. It thought you were friends but you slept with it's girlfriend or whatever. Now if HTC were to suddenly turn s-on, this would break chains of trust for those who used something like Moonshine with a patched hboot. It was their OTA that caused it. They are then held liable for it and they have to fix it under warranty. You know how much that costs them? Imagine giving 1000's of people new phones because you singlehandedly broke them all. Good job dude.
Not only that, they cant turn S-on by just updating images on the device. It's stored in the NV-RAM. They would need an entirely different method than just flashing through recovery.
Next point is:
S-off means you can flash whatever you want using fastboot flash.
Now because s-off processes before gave us patched hboots, we didnt know any better. This is all wrong. fastboot flash barely works on newer phones unless dev unlocked. Now that not all s-off's give a patched hboot it's good to know the following. The only way to install something with a locked bootloader but s-off, is to use flash zip. This means that you dont just "fastboot flash recovery" or boot.img. You need to create a zip with android-info.txt and whatever files your flashing. With the lock placed on devices, unless you htc dev unlock or flash a modified hboot, it wont allow you to flash because the dev unlock is a different part than what flashes the zips.
More info about patched / eng hboots:
Now that we've seen what we lose without a patched hboot, what does it add exactly? Well, a patched or engineering hboot allows you to fastboot flash pretty much every partition on the device with an unsigned image directly (such as fastboot flash hboot hboot.img or fastboot flash splash1 splash1.img) without giving you a not allowed or command error. The reason these are useful is because it saves time. I really dont want to always have to build a zip so I always use patched hboots. They also give you access to more commands as well which I can't remember off the top of my head. These are all commands mainly used by HTC engineers and software testers.
Final point that I can think of (may add more):
That green progress bar needs to be full when fastboot flashing a zip. While it's a pretty green bar and looks very useful...for whatever reason, htc has decided to make it wrongly report progress when in use. This can lead to users freaking out and just leaving their phone in RUU mode for however until someone tells them they're idiots for it. this progress bar means literally nothing and my favorite quote about it is: "Progress bar is like tits on a snake. Interesting but pointless." Ignore the progress bar. If the command line says the zip finished, just fastboot reboot or reboot-bootloader. It will help you finish whatever the heck you're trying to do.

Nice write-up I added it to the FAQ's thread Q9 Thanks

Very nice thread, thanks

+1 on that green progress bar, when I removed the red writing on the splash screen I saw the progress bar not don't but in command prompt it said finished so I said whatever and just rebooted
Sent from my HTC One using Tapatalk 2

Reminds me of a certain thread I wrote about a year ago
S-OFF explained - by a Developer

Didn't even know that existed.
Sent from my hidden jewel

Question, let's say I have s-off and flash the superuser app and all the required busybox files... Can I use root required apps like titanium backup and wireless tether?
I only ask because I've been hesitatent to root. I just don't want to Dev unlock via HTC and officially void my warranty. The sealed in battery has me extremely paranoid as its generally the first thing I've had to replace with previous HTC devices.
This leads me to the following question, if the response to the first was no... Is there a way to use root apps without using the HTC Dev tool
Please note: I'm not a developer and this was not clear to me in the write up.

You don't need s-off to root.
You do need to root to use apps that require root access.

budeone said:
You don't need s-off to root.
You do need to root to use apps that require root access.
Click to expand...
Click to collapse
You've stated the obvious...but thanks for the response!
I just want to know if we can get root without going through HTC, or if it will be possible in the near future thanks to the s-off development. It's my understanding that you do not need root to get s-off.

bnapy said:
You've stated the obvious...but thanks for the response!
I just want to know if we can get root without going through HTC, or if it will be possible in the near future thanks to the s-off development. It's my understanding that you do not need root to get s-off.
Click to expand...
Click to collapse
I found this link, may answer your question.
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html

As described in this thread an Android-info.txt file can be used to fastboot flash update.zip where the contents of the zip are TWRP and the .txt file.
I am S-OFF Locked on 1.31 stock
I want to flash TWRP via the method described above. (Or alternatively the superuser apk)
I have a img file of TWRP.
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?

Indirect said:
That green progress bar needs to be full when fastboot flashing a zip. While it's a pretty green bar and looks very useful...for whatever reason, htc has decided to make it wrongly report progress when in use. This can lead to users freaking out and just leaving their phone in RUU mode for however until someone tells them they're idiots for it. this progress bar means literally nothing and my favorite quote about it is: "Progress bar is like tits on a snake. Interesting but pointless." Ignore the progress bar. If the command line says the zip finished, just fastboot reboot or reboot-bootloader. It will help you finish whatever the heck you're trying to do.
Click to expand...
Click to collapse
I don't know about "tits on a snake," but many progress bars I've seen are both uninteresting and pointless. They do generally serve their purpose of keeping impatient/inexperienced users from hammering away at things they don't understand and inadvertently breaking them.

tws101 said:
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Click to expand...
Click to collapse
Here is the version straight from the 1.31..651.2 OTA firmware.zip. Although you may not need the "btype" or "aareport" lines. I have flashed TWRP in the past without those lines included.

tws101 said:
As described in this thread an Android-info.txt file can be used to fastboot flash update.zip where the contents of the zip are TWRP and the .txt file.
I am S-OFF Locked on 1.31 stock
I want to flash TWRP via the method described above. (Or alternatively the superuser apk)
I have a img file of TWRP.
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Click to expand...
Click to collapse
PillowMetal said:
Here is the version straight from the 1.31..651.2 OTA firmware.zip. Although you may not need the "btype" or "aareport" lines. I have flashed TWRP in the past without those lines included.
Click to expand...
Click to collapse
Another misconception about S-OFF is that you need a "valid android-info.txt" when flashing from fastboot. When you're S-OFF, the bootloader completely disregards that file. All you need is to make a zip with whatever you want flashed, and then add any android-info.txt file in there. The default one that I include in the plugin template for my Bootloader Customizer is actually completely empty and it works fine as well. As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.

regaw_leinad said:
As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
Click to expand...
Click to collapse
That's good to know, and thanks for the bootloader customizer, I have been using it for years, as well as your "rebooter" which is very convenient. Glad to see you in the One forums!

regaw_leinad said:
As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
Click to expand...
Click to collapse
Just to follow up, I discovered that at least with the Sprint HTC One, you need the following three lines at a minimum when flashing from rebootRUU or you will get an error stating:
FAILED (remote: 24 parsing android-info fail)
Code:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
So it looks like S-OFF validation of android_info.txt has stiffened up since the EVO 4G LTE days.

PillowMetal said:
Just to follow up, I discovered that at least with the Sprint HTC One, you need the following three lines at a minimum when flashing from rebootRUU or you will get an error stating:
FAILED (remote: 24 parsing android-info fail)
Code:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
So it looks like S-OFF validation of android_info.txt has stiffened up since the EVO 4G LTE days.
Click to expand...
Click to collapse
Ah, you don't have a bootloader that allows fastboot flashing? That must be why. If you were flashing straight from the hboot, you don't need it. Didn't realize you guys had to use RUU mode.

regaw_leinad said:
Didn't realize you guys had to use RUU mode.
Click to expand...
Click to collapse
I would LOVE to be able to flash from hboot, it was so convenient and didn't require a computer. But alas, no SD Card on the Sprint variant, so no hboot flashing.
It has been said that we can use USB-OTG to perform the hboot flashing, but I have yet to get a known compatible and working USB drive to be recognized or even looked at when starting up the bootloader, although the drive works fine when rebooted to system or even recovery. It just doesn't search for external mounts like the old EVO 4G LTE hboot did on startup.
There's a thread for the small number of us who care and wan't to do this, but can't...
http://forum.xda-developers.com/showthread.php?t=2320252
And specifically, my experiences trying to get it to work.
http://forum.xda-developers.com/showpost.php?p=44444102&postcount=9
http://forum.xda-developers.com/showpost.php?p=44494480&postcount=11
Any insight or things you can share regarding this would be greatly appreciated.

PillowMetal said:
I would LOVE to be able to flash from hboot, it was so convenient and didn't require a computer. But alas, no SD Card on the Sprint variant, so no hboot flashing.
It has been said that we can use USB-OTG to perform the hboot flashing, but I have yet to get a known compatible and working USB drive to be recognized or even looked at when starting up the bootloader, although the drive works fine when rebooted to system or even recovery. It just doesn't search for external mounts like the old EVO 4G LTE hboot did on startup.
There's a thread for the small number of us who care and wan't to do this, but can't...
http://forum.xda-developers.com/showthread.php?t=2320252
And specifically, my experiences trying to get it to work.
http://forum.xda-developers.com/showpost.php?p=44444102&postcount=9
http://forum.xda-developers.com/showpost.php?p=44494480&postcount=11
Any insight or things you can share regarding this would be greatly appreciated.
Click to expand...
Click to collapse
You know, it might depend on the type of drive, and it might depend on the file system your drive is formatted to. I have 0 experience using USB-OTG, so I'm probably not the best one to ask unfortunately But if you do get it working, be sure to make a guide or something! Try playing around with different formatting of your drive possibly

regaw_leinad said:
You know, it might depend on the type of drive, and it might depend on the file system your drive is formatted to. I have 0 experience using USB-OTG, so I'm probably not the best one to ask unfortunately But if you do get it working, be sure to make a guide or something! Try playing around with different formatting of your drive possibly
Click to expand...
Click to collapse
Ah, never thought of trying different formatting, there are different allocation unit sizes I could use... thanks! I will definitely make a guide if I get this resolved because it is driving me crazy, so I'm sure there are others too.

[Q] how to check original network HTC one,need to download RUU to flash stock ROM?

I got two HTC phones i bought them online and I am not sure about the original network of these phones. I would like to bring it back to stock roms but i do not know which RUU i should download , How would i know which network phones are these. Both of them are stuck at first screen and i cannot check them SIM card.
Please help ?

Brownpanda said:
I got two HTC phones i bought them online and I am not sure about the original network of these phones. I would like to bring it back to stock roms but i do not know which RUU i should download , How would i know which network phones are these. Both of them are stuck at first screen and i cannot check them SIM card.
Please help ?
Click to expand...
Click to collapse
What do you mean they are both stuck at the first screen ?
the bootloader ?
whats it say on the bootloader / power + vol down

clsA said:
What do you mean they are both stuck at the first screen ?
the bootloader ?
whats it say on the bootloader / power + vol down
Click to expand...
Click to collapse
Thanks for your reply .. lets start one by one .. attached is the screenshot for first phone
On XDA i have found some of the CWM backup files for Rogers canada, Both of phones have CWM installed. Could you please let me know if i can use these files for backup
M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)
I am trying to find on my end too , please let me know if u can find any link for canada HTC one RUU links ?

Brownpanda said:
Thanks for your reply .. lets start one by one .. attached is the screenshot for first phone
On XDA i have found some of the CWM backup files for Rogers canada, Both of phones have CWM installed. Could you please let me know if i can use these files for backup
M7 CWM Nandroid Backup / CID ROGER001 / 1.29.631.17 (Rogers - Thanks to Whampahoofus)
I am trying to find on my end too , please let me know if u can find any link for canada HTC one RUU links ?
Click to expand...
Click to collapse
You need @SaHiLzZ he's the Rogers guy
Sent from my HTC One using Tapatalk 4

Fastboot getvar all should give model id and main version. First stop would be to s-off.

I have CWRP installed in both of my devices, as i was researching on internet (mostly XDA) , i have found there is no RUU available for Canadian networks like bell , rogers. telus right now . i bought it in Canada so i assume they are on Canadian networks. Just want to know if i download CWM nandroid backup for different Canadian networks would it work ?
If yes, HTC one M7 does not come with any sd card slot and most of the procedure says CWM can restore files (cwm nandroid backups )from sd card. So how can i do it on HTC one M7 ?

Brownpanda said:
I have CWRP installed in both of my devices, as i was researching on internet (mostly XDA) , i have found there is no RUU available for Canadian networks like bell , rogers. telus right now . i bought it in Canada so i assume they are on Canadian networks. Just want to know if i download CWM nandroid backup for different Canadian networks would it work ?
If yes, HTC one M7 does not come with any sd card slot and most of the procedure says CWM can restore files (cwm nandroid backups )from sd card. So how can i do it on HTC one M7 ?
Click to expand...
Click to collapse
Have a look here
http://forum.xda-developers.com/showthread.php?t=2529225
if you still have questions I'm here

clsA said:
You need @SaHiLzZ he's the Rogers guy
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
i went thru his threadt SaHiLzZ , got very good information from that guy, In his thread, he suggested i should S-off to do any further work even other member suggested me same thing . I have downloaded ramrunner software to do that. But it came back with error message my phone is not rooted right now. Could you please let me know how can i root this phone in CWM mode ?
Thanks clsA for this link, thats the same link i followed from sahilz thread, As per step 10 I am trying to s-off my phone with ramrunner but its not rooted

Brownpanda said:
i went thru his threadt SaHiLzZ , got very good information from that guy, In his thread, he suggested i should S-off to do any further work even other member suggested me same thing . I have downloaded ramrunner software to do that. But it came back with error message my phone is not rooted right now. Could you please let me know how can i root this phone in CWM mode ?
Thanks clsA for this link, thats the same link i followed from sahilz thread, As per step 10 I am trying to s-off my phone with ramrunner but its not rooted
Click to expand...
Click to collapse
flash this in recovery same as a rom
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip

clsA said:
flash this in recovery same as a rom
http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
Click to expand...
Click to collapse
Please consider me as novice in CWM recovery, I have tried all options but cannot find how can i transfer superuser files from my PC to my phone now, I cannot go beyond CWM recovery so my PC is not recognizing my phone right now.

Brownpanda said:
Please consider me as novice in CWM recovery, I have tried all options but cannot find how can i transfer superuser files from my PC to my phone now, I cannot go beyond CWM recovery so my PC is not recognizing my phone right now.
Click to expand...
Click to collapse
I don't use CWM ..so you need to find sideload usually under some advanced setting.
you start the sideload and then from your pc fastboot / adb folder
you adb sideload <Name of file>.zip
just be sure the files your trying to sideload are in the same folder as adb / fastboot. the alternative is to Push the files
the command is
adb push <name of file>.zip /sdcard/ <don't forget the space between .zip /sdcard/
This works for any file you want to copy to your phone

clsA said:
I don't use CWM ..so you need to find sideload usually under some advanced setting.
you start the sideload and then from your pc fastboot / adb folder
you adb sideload <Name of file>.zip
just be sure the files your trying to sideload are in the same folder as adb / fastboot. the alternative is to Push the files
the command is
adb push <name of file>.zip /sdcard/ <don't forget the space between .zip /sdcard/
This works for any file you want to copy to your phone
Click to expand...
Click to collapse
I don't know where i went wrong but now I am stuck at this point. Please check attachment
My device is no longer recognized by my computer or adb , just got stuck in there, last thing i tried on this phone was ramrunner when it came back with error message " My phone is not rooted"
Now i cannot enter in CWM recovery , it come back to same bootloader screen everytime i try to entered recovery
EDITED :
Latest updates on my phone is
Just changed the USB port on my pc and it finally recognized my phone. Now in fastboot devices command i can see my device listed, but on adb it does not show my device listed
researched a little bit more so i found lot of people used different version of CWM or TWRP to make it work so tried few but got these error messages when tried to flash recoveries
FAILED : remote signature verify fail
any ideas ?
bootloader is still at Tampered, re locked and security warning screen !!!!

Brownpanda said:
I don't know where i went wrong but now I am stuck at this point. Please check attachment
My device is no longer recognized by my computer or adb , just got stuck in there, last thing i tried on this phone was ramrunner when it came back with error message " My phone is not rooted"
Now i cannot enter in CWM recovery , it come back to same bootloader screen everytime i try to entered recovery
EDITED :
Latest updates on my phone is
Just changed the USB port on my pc and it finally recognized my phone. Now in fastboot devices command i can see my device listed, but on adb it does not show my device listed
researched a little bit more so i found lot of people used different version of CWM or TWRP to make it work so tried few but got these error messages when tried to flash recoveries
FAILED : remote signature verify fail
any ideas ?
bootloader is still at Tampered, re locked and security warning screen !!!!
Click to expand...
Click to collapse
Unlock the bootloader so you can update your recovery
Sent from my HTC One using Tapatalk 4

clsA said:
Unlock the bootloader so you can update your recovery
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
I have tried to unlock it but its giving me some error messages, anyways now my bootloader is in relock position so i found this thread
http://forum.xda-developers.com/showthread.php?t=2251800
As suggested i downloaded Telus zip file and followed the procedure, it came back with error message.
signature failed ...............any ideas what does this error message means ??

clsA said:
Unlock the bootloader so you can update your recovery
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Brownpanda said:
I have tried to unlock it but its giving me some error messages, anyways now my bootloader is in relock position so i found this thread
http://forum.xda-developers.com/showthread.php?t=2251800
As suggested i downloaded Telus zip file and followed the procedure, it came back with error message.
signature failed ...............any ideas what does this error message means ??
Click to expand...
Click to collapse
This is going from good to bad to worse.
I recommend you relax a little, doing things in a hurry/rush/panic is not going to be good or get you anywhere !!
Now 1st go back to HTCdev, and unlock you bootloader using a new unlock token.... you shouldnt have locked in the first place, and reading guides dating back to April 2013 (ie pre S-Off days), is not going to help either.

nkk71 said:
This is going from good to bad to worse.
I recommend you relax a little, doing things in a hurry/rush/panic is not going to be good or get you anywhere !!
Now 1st go back to HTCdev, and unlock you bootloader using a new unlock token.... you shouldnt have locked in the first place, and reading guides dating back to April 2013 (ie pre S-Off days), is not going to help either.
Click to expand...
Click to collapse
Even i was thinking same thing , thanks for your help, I am not doing anything on this phone for next few hours now and will start from beginning ...please advice me how should i proceed ..

Brownpanda said:
Even i was thinking same thing , thanks for your help, I am not doing anything on this phone for next few hours now and will start from beginning ...please advice me how should i proceed ..
Click to expand...
Click to collapse
Do you have a functioning ROM?
If yes, then there could be multiple options, but the below will be the easiest:
If no, then you have to unlock using HTCdev: http://www.htcdev.com/bootloader/
you need to register an account with a real email (where you receive the unlock token)
in "Supported Devices" choose All other supported models, and follow the instructions.

Thanks , sorry I don't have functioning Rom , only had this RUU zip file from telus Canada , as I mentioned I did not know about original network of this phone , bought it from Canada so just assumed its on Canadian network , relock boot loader happened after I used ram runner software to s-off it , my phone was not rooted and it came with error message , so could not do s-off it , I am having nice break from this phone , as you suggested I will start from scratch tonight , will let u know guys , thanks for your help so far
Sent from my HTC One using Tapatalk

Short steps.
1. Unlock bootloader.
2. Place phone in fastboot mode and type fastboot getvar all, and copy paste the output here.
Wait for further instructions.
sent from my mobile device

SaHiLzZ said:
Short steps.
1. Unlock bootloader.
2. Place phone in fastboot mode and type fastboot getvar all, and copy paste the output here.
Wait for further instructions.
sent from my mobile device
Click to expand...
Click to collapse
Sorry I am trying to unlock my bootloader, After copying pasting my identifier token on HTC dev website it come back with this error message
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 140.
Error Reason: Token Decryption Fail.
after command fastboot getvar all I am getting this info if that helps
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.666.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34RW905405
(bootloader) imei: 354439053765923
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3789mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.076s

[Q] 100% stock ROM reset: how do I get LOCKED instead of RELOCKED?

Hello everybody!
I want to get back to 100% stock ROM (after having used Cyanogenmod previously) - with LOCKED, not RELOCKED.
Current phone: fastboot getvar all yields:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.161.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: MYSN
(bootloader) imei: MYIMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4184mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have already restored a Nandroid backup with the original software: that backup was taken from my own phone some months ago right after purchase. I only unlocked the phone for the very first time, flashed the CWMR and directly made the backup with that recovery. Then I pulled the backup to my PC my adb.
So far, I successfully got the phone to S-Off, using RumRunner and removed the TAMPERED flag using the following method with adb as described within this post: http://forum.xda-developers.com/showthread.php?t=2477792
However, now I seem to have run into a deadlock:
a) To gain LOCKED using the following method with adb as described within this post(http://forum.xda-developers.com/showthread.php?t=2475914) I need adb access to the phone.
As long the CWMR is on the phone, the device is listed as “Android ADB Interface” in the category “Android Device” in the Windows Device Manager. Fine, so I can access the phone through adb and can set the bootloader back to LOCKED successfully. But after locking I am not able flash the stock recovery any more.
b) If I flash the stock recovery and boot into it, then
- the stock recovery does not provide adb access. The phone is not listed in the Windows Device Manager.
- booted up into HTC Sense OS, it does not provide adb access, either .The phone is listed as “CD Serial” with a question mark in the category “Other Devices” and “HTC One” with a question mark in the category “Portable Devices”; Also it automatically mounts a drive that includes the HTC Sync Manager, Drivers, etc. [EDIT] Got rid of the question marks by re-assigning the correct MTP and CDC drivers; now I can see the emulated sdcard folder[EDIT OFF],
So, without adb access I cannot use the above method to get LOCKED (and fastboot oem relock lead to RELOCKED, which voids my warranty )-: ).
c) Having the matching stock recovery (3.63.161.6 - Vodafone.img downloaded from the internet somwhere, checksum OK) installed and trying to boot into a temporary CWMR by using fastboot boot myM7_UL_CWMR.img (I tried recovery-clockwork-touch-6.0.4.3-m7ul) does not work, the phone is stuck, if I sent that command. -Is it because, I have HBOOT 1.55, and fastboot boot recovery.img is only supported by HBOOT 1.44?
Question: Do I really have to go through the complete procedure described here, to get LOCKED ? :
http://www.htc1guru.com/guides/return-stock-guide/
That procedure seems to be a pain for me as my CID is VODAP102, and there seems no RUU to be listed for my phone, so I will have to change the CID during the process and execute some extra process steps - or I am just too dumb to identify the correct one for my phone:
http://forum.xda-developers.com/showthread.php?t=2428276
Or is there any alternative quicker way than that HTC Guru Guide?
As said, I have a CWR backup .zip from my original factory installation and I already have already downloaded the matching stock recovery image, so I can flash it on the phone. Does this help?
Regards
Steven

that's one hell of a long post and a lot of questions, well first of all i'll see if I can help you with this, link below is Vodafone backup which I created from my phone, unzip it, you will find a folder called backup, that contains the backup files, and another called recovery, that contains twrp that I used to create the backup, so flash that first.
STAY S_OFF, DO NOT SET BACK TO S_ON.
enter recovery, create a backup in order to create the required folders, then boot your phone back to android, once booted, plug into your computer, copy the backup folder from my zip to your internal SDcard/TWRP/BACKUPS/"device serial number"/
Reboot the phone back into recovery and restore that backup, you will now have Vodafone kitkat 4.4.2 on your phone, however one problem you may have is 4.4.2 comes with HBOOT 1.56 not 1.55, they may pick up on that.
https://drive.google.com/file/d/0B_nEcSZr5peRZnpMSHRPRjlzX2c/edit?usp=sharing

Dear Seanie,
thanks for willing to help!
Will restoring your backup replace the previously flashed TRWP recovery by the stock recovery?
If not, the TRWP recovery remains, and I cannot send the phone in for repair.
If yes, I cannot use adb to set the phone to LOCKED, as the stock recovery does not support adb.
I see no advantage over using the Nandroid backup from my own phone (see opening post).
I am confused - can you clarify, please?
Steven

ManyPhones said:
Dear Seanie,
thanks for willing to help!
Will restoring your backup replace the previously flashed TRWP recovery by the stock recovery?
If not, the TRWP recovery remains, and I cannot send the phone in for repair.
If yes, I cannot use adb to set the phone to LOCKED, as the stock recovery does not support adb.
I see no advantage over using the Nandroid backup from my own phone (see opening post).
I am confused - can you clarify, please?
Steven
Click to expand...
Click to collapse
check my guide, see if that makes sense to you: http://forum.xda-developers.com/showthread.php?t=2541082
reason why the CWM restore method is so long: http://forum.xda-developers.com/showpost.php?p=52430301&postcount=834
I recommend you stay S-Off, but that's a decision only you can make
---------- Post added at 04:03 PM ---------- Previous post was at 03:38 PM ----------
@ManyPhones
if you're going to follow my guide, these are the files you need (in case htc1guru.com is giving slow/corrupt downloads):
ruu.zip: http://www.androidfilehost.com/?fid=23329332407584993
nandroid: http://www.androidfilehost.com/?fid=23501681358543658
preloaded apps: http://www.androidfilehost.com/?fid=23329332407580574
and probably this stock recovery: http://d-h.st/XMA should work without hanging.

Dear nkk71,
thank you! I carefully read through your posting and the linked instructions. - your guide is excellent and foolproof!
I understood I had to use the Nandroid backup method, as there was neither an RUU.exe nor an RUU.zip file available for CID VODAP102.
Thank you for providing the explicit versions/links for my individual phone in the posting!
So the key is indeed downgrading to HBOOT 1.44 in order to be able to load a temporary custom recovery with fastboot boot temp_ recovery_name.img.
I am right after STEP 7. In Step 6 have made the first OTA update, updating from software 1.29.161.7 to software 2.24.161.1. A further update to 3.63.161.6 is offered.I understand, if I want to to S-On, I have to do it NOW, before doing that further update.
I guess, if I want to have full warranty, it is a MUST to set S-On. Right?
Why do you recommend to stay S-Off? - Isn't it possible to go S-On, OTA update to 3.63.161.6, let the phone repair and then later use RumRunner again (after unlocking and rooting again)?
Regards
Steven
P.S.: Someone provided another, shorter method (without downgrade) per PN:
1st download recovery flasher zip (LINK)
Open this zip with 7zip*
Put stock recovery in it simply but renamed recovery.img*
Close zip if it ask save it press yes*
Copy this new zip to phone storage*
Now download guru boot loader reset tool zip from this link & copy to your phone storage
Now reboot to TWRP recovery
*1 st flash recovery flasher zip*
2 nd flash guru boot loader reset tool zip with Locked & remove tempered options ( it tempered is there ) complete flash*
I have not tried it, as I was half through your method. But I can imagine, it maywork - as I do not need to use external adb to access the internal phone memory for the flags, and since I had my own factory-fresh HTC backup re-installed already before.

ManyPhones said:
I am right after STEP 7. In Step 6 have made the first OTA update, updating from software 1.29.161.7 to software 2.24.161.1. A further update to 3.63.161.6 is offered.I understand, if I want to to S-On, I have to do it NOW, before doing that further update.
I guess, if I want to have full warranty, it is a MUST to set S-On. Right?
Click to expand...
Click to collapse
Hi,
There are always different ways of doing things, some shorter, some longer. My guide was written after many many different one-on-one threads, and the conclusion of every possible outcome I have encountered.
(including IRC chats and teamviewer sessions, and even some shortcut methods were used in my thread, but on a one-to-one basis, not as a general rule)
this includes the infamous "tamper detected - rebooting" (mentioned in the guide) that may (or may not) happen when going from S-Off to S-On, this is why I always recommend that IF you intend on going from S-Off to S-On, you should do so on hboot 1.44 or 1.54
As to the question of S-On vs S-Off, it's really country/carrier/repair centre specific... in theory, it shouldn't matter, but in practice, it's dependent on the previous, so that is something you will have to decide.
For example: I've seen threads with people sending in their phone with a custom ROM, tampered, unlocked -> no problem
but i've also seen a post, 100% stock including S-On, but the repair guy said the power button was pressed with "too much force" and refused warranty (oh and it wasn't sent to repair for the power button!!)
cheers

I see, your's is a general approach that will work under any circumstances. I can imagine it is almost impossible to provide tailored solutions for each and every individual starting point of the restore. So, the long way is always the safe way (-:
It must have been a lot of work to assemble the guide and the case example.
Great work! You'll be thanked!

Final words
nkk71 said:
Hi,
this includes the infamous "tamper detected - rebooting" (mentioned in the guide) that may (or may not) happen when going from S-Off to S-On, this is why I always recommend that IF you intend on going from S-Off to S-On, you should do so on hboot 1.44 or 1.54
As to the question of S-On vs S-Off, it's really country/carrier/repair centre specific... in theory, it shouldn't matter, but in practice, it's dependent on the previous, so that is something you will have to decide.
cheers
Click to expand...
Click to collapse
Final words:
I decided to go S-On - as recommended I made it on HBOOT 1.54 (included in the aforementioned OTA update to OS software version 2.24.161.1). No problems, still LOCKED after three reboots.
Then I started the OTA to OS software version 3.63.161.6 (HBOOT 1.55), then another to OS software version 4.X (HBOOT 1.56), then another to OS software version 5.16.161.2 (HBOOT 1.57). If I ever want to go back to S-off, I'll have to use Firewater and hope, that it will work.

ManyPhones said:
Final words:
I decided to go S-Off - as recommended I made it on HBOOT 1.54 (included in the aforementioned OTA update to OS software version 2.24.161.1). No problems, still LOCKED after three reboots.
Then I started the OTA to OS software version 3.63.161.6 (HBOOT 1.55), then another to OS software version 4.X (HBOOT 1.56), then another to OS software version 5.16.161.2 (HBOOT 1.57). If I ever want to go back to S-off, I'll have to use Firewater and hope, that it will work.
Click to expand...
Click to collapse
you mean "go S-On", right?
and yes, for hboot 1.57 firewater is the only method at the moment that may work to get S-Off, hopefully sunshine will be updated to include the M7
(otherwise the only other solution would be using a JavaCard)

nkk71 said:
you mean "go S-On", right?
Click to expand...
Click to collapse
Yeah, that was a typo - I meant S-On (corrected in post #9, sorry for the confusion!
nkk71 said:
Hopefully sunshine will be updated to include the M7
(otherwise the only other solution would be using a JavaCard)
Click to expand...
Click to collapse
Those concepts are still inknown to me. Never mind, I'll check it out later as needed.
Thanks again, nkk71 for the excellent support - and the others, who wrote me PMs!

Returning Phone Question

So, my HTC One got hit with the unresolvable "Can't charge unless turned off" bug and I'm going to be forced to return it if I can. My HTC One is unlocked, rooted and CM11 is installed. I also have SuperCID and S-Off. I also do not have warranty anymore because it's been 1 year since I got my phone, so I'm not sure how well it's going to go by returning this phone and hoping for a replacement.
Has anyone else had any experience with this? Do I just return it to stock as best as I can (All of the Google links to doing this are outdated with broken download links now, so if anyone could link me to a full guide to address all of my "customizations" to my phone to return to stock, it'd be highly appreciated) and go into the AT&T store hoping for a refurbished model replacement at least? Is there a phone manufacturer warranty of sorts? Will they check my phone to see the bootloader unlock counter or whatever? I heard they use a tool/program that checks to see how many times your bootloader has been unlocked or something.
I really need to get this phone fixed because it's having an awful lot of issues with it and I rely heavily on this phone for work. Not only that, but I had to pay retail for this phone when I got it back in June or so of 2013 so I'd like to fix these issues or get it replaced so I can re-sell it once my upgrade is available in a year.
If anyone could please help me, give me advice or point me in the direction of 'returning to stock' guides in all of the customization categories I listed, I'd be tremendously appreciative. I'm assuming the best way to do it is just walk into the AT&T store after returning to stock and act like a moron that barely knows how to turn the phone on and ask them if I can get a replacement under manufacturer warranty for these electronic bugged problems.
What do you all think?

Leather Sock said:
If anyone could please help me, give me advice or point me in the direction of 'returning to stock' guides in all of the customization categories I listed, I'd be tremendously appreciative. I'm assuming the best way to do it is just walk into the AT&T store after returning to stock and act like a moron that barely knows how to turn the phone on and ask them if I can get a replacement under manufacturer warranty for these electronic bugged problems.
Click to expand...
Click to collapse
Can you post the output of "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
Can you post the output of "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4139mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s

Leather Sock said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
finished. total time: 0.078s
Click to expand...
Click to collapse
You said you were originally on AT&T right? in which case CID should be CWS__001
so set it back:
fastboot oem writecid CWS__001 <- two underscores
fastboot oem reboot-bootloader
Then follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
using RUU.ZIP method (posts #1, #2, and #4), using this RUU Zip M7_UL_JB_50_Cingular - 1.26.502.15 - decrypted.zip
Note, if you already have a custom recovery installed, you don't need to change it to set your phone LOCKED and untampered
I prefer staying S-Off, but that's something only you can decide.

nkk71 said:
You said you were originally on AT&T right? in which case CID should be CWS__001
so set it back:
fastboot oem writecid CWS__001 <- two underscores
fastboot oem reboot-bootloader
Then follow my guide: http://forum.xda-developers.com/showthread.php?t=2541082
using RUU.ZIP method (posts #1, #2, and #4), using this RUU Zip M7_UL_JB_50_Cingular - 1.26.502.15 - decrypted.zip
Note, if you already have a custom recovery installed, you don't need to change it to set your phone LOCKED and untampered
I prefer staying S-Off, but that's something only you can decide.
Click to expand...
Click to collapse
Thank you so much for your help! I figured I had to go to S-On to return it fully to stock. I don't want there to be any issues when I go to return it since I've done the naughty stuff behind the scenes and I'm trying to get the best possible chance I can at getting a replacement. I've also never returned a phone or anything of the sort so I'm not sure what to expect or how much I'll have to talk them into the replacement. I do have a custom recovery being TWRP's latest version but I'm not necessarily sure what you mean. I imagine once I begin the process I'll understand!

Leather Sock said:
Thank you so much for your help! I figured I had to go to S-On to return it fully to stock. I don't want there to be any issues when I go to return it since I've done the naughty stuff behind the scenes and I'm trying to get the best possible chance I can at getting a replacement. I've also never returned a phone or anything of the sort so I'm not sure what to expect or how much I'll have to talk them into the replacement. I do have a custom recovery being TWRP's latest version but I'm not necessarily sure what you mean. I imagine once I begin the process I'll understand!
Click to expand...
Click to collapse
you need custom recovery to use adb command or use the Guru Bootloader Reset (which allows you to remove TAMPERED and set the phone to LOCKED not RELOCKED),
so it should be straightforward for you:
1) use Guru Bootloader Reset or adb commands to remove TAMPERED and set LOCKED
2) flash ruu.zip twice
---> first flash will give you "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
---> second flash should give you: "(bootloader) ...... Successful, OKAY [200.187s], finished. total time: 242.101s"
3) bootup phone just to make sure everything is OK, do not take OTA updates!! (at least yet)
4) set S-On
5) take OTAs if you want

nkk71 said:
you need custom recovery to use adb command or use the Guru Bootloader Reset (which allows you to remove TAMPERED and set the phone to LOCKED not RELOCKED),
so it should be straightforward for you:
1) use Guru Bootloader Reset or adb commands to remove TAMPERED and set LOCKED
2) flash ruu.zip twice
---> first flash will give you "FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
---> second flash should give you: "(bootloader) ...... Successful, OKAY [200.187s], finished. total time: 242.101s"
3) bootup phone just to make sure everything is OK, do not take OTA updates!! (at least yet)
4) set S-On
5) take OTAs if you want
Click to expand...
Click to collapse
Thank you! Okay, from what I understand, I just need to do the following:
1. Put Guru Bootloader Reset + Ruu file you linked me to on my SD card like I would a custom ROM, ready to be unzipped.
2. Backup device stuff and reboot into TWRP
3. Install Zip for Guru Bootloader Reset and do the following in it's GUI to remove Tampered (I don't have it right now) and set my status to "Locked"
4. Reboot back into the recovery, not the ROM, and Install Zip "Ruu.zip" by flashing it. I'll get an error, and then I flash it one more time and I'm done and able to boot into stock Sense rom with OTA updates.
5. Remove S-On with that easy command via Fastboot. (However, didn't you say I needed a recovery to do this? Don't I do this while I still have TWRP or do I just keep TWRP on there? I don't see anywhere, where I'm removing TWRP)
Is that right? Am I missing any important details? Will this hide my past activities enough to get a replacement do you think?

Leather Sock said:
Thank you! Okay, from what I understand, I just need to do the following:
1. Put Guru Bootloader Reset + Ruu file you linked me to on my SD card like I would a custom ROM, ready to be unzipped.
2. Backup device stuff and reboot into TWRP
3. Install Zip for Guru Bootloader Reset and do the following in it's GUI to remove Tampered (I don't have it right now) and set my status to "Locked"
4. Reboot back into the recovery, not the ROM, and Install Zip "Ruu.zip" by flashing it. I'll get an error, and then I flash it one more time and I'm done and able to boot into stock Sense rom with OTA updates.
5. Remove S-On with that easy command via Fastboot. (However, didn't you say I needed a recovery to do this? Don't I do this while I still have TWRP or do I just keep TWRP on there? I don't see anywhere, where I'm removing TWRP)
Is that right? Am I missing any important details? Will this hide my past activities enough to get a replacement do you think?
Click to expand...
Click to collapse
Not really
First off, using ruu will completely wipe your phone!! everything including internal storage, so if there is anything on your phone you want to keep, you need to back that up to your PC.
Second, the fastboot commands are run on your PC, while the phone is connected and you are in bootloader showing FASTBOOT USB (just like you did to get the "fastboot getvar all"
So:
1- put Guru Bootloader Reset on your internal storage -> OK
2- use TWRP to "install" Guru Bootloader Reset -> OK, remove TAMPERED (even if it's not there), set LOCKED -> OK
go back to bootloader and confirm LOCKED
3- on your PC with phone connected in FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
4- reboot the phone (it will be wiped clean), just to make sure everything is OK, do not take OTA updates.
5- set S-On using
fastboot oem writesecureflag 3
done.

nkk71 said:
Not really
First off, using ruu will completely wipe your phone!! everything including internal storage, so if there is anything on your phone you want to keep, you need to back that up to your PC.
Second, the fastboot commands are run on your PC, while the phone is connected and you are in bootloader showing FASTBOOT USB (just like you did to get the "fastboot getvar all"
So:
1- put Guru Bootloader Reset on your internal storage -> OK
2- use TWRP to "install" Guru Bootloader Reset -> OK, remove TAMPERED (even if it's not there), set LOCKED -> OK
go back to bootloader and confirm LOCKED
3- on your PC with phone connected in FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE, the first one will report “failed flush again”, the second one will succeed.
fastboot reboot-bootloader
4- reboot the phone (it will be wiped clean), just to make sure everything is OK, do not take OTA updates.
5- set S-On using
fastboot oem writesecureflag 3
done.
Click to expand...
Click to collapse
Oh! Whew, glad I didn't do it yet then (still waiting for the RUU to download). Alright, apart from pictures/videos I don't think there's anything else on my Internal Storage that I care about unless there's other common stuff I'm forgetting. I also backed up my contacts and emailed them to me so I should be good there as well. Backed up my apps too.
One last final question and I promise I'll let you go! Will TWRP in this process, ever be removed or is it okay that it remains on there? When I flash the RUU, is that what removes it when it wipes the phone? If so, how will the fastboot work without TWRP if RUU removes it?
Oh, editing this in. When I go to install RUU, do I put the .zip file in my adb folder containing fastboot?

Leather Sock said:
Oh! Whew, glad I didn't do it yet then (still waiting for the RUU to download). Alright, apart from pictures/videos I don't think there's anything else on my Internal Storage that I care about unless there's other common stuff I'm forgetting. I also backed up my contacts and emailed them to me so I should be good there as well. Backed up my apps too.
One last final question and I promise I'll let you go! Will TWRP in this process, ever be removed or is it okay that it remains on there? When I flash the RUU, is that what removes it when it wipes the phone? If so, how will the fastboot work without TWRP if RUU removes it?
Click to expand...
Click to collapse
1- Everything (literally) will be removed / wiped / replaced after flashing a RUU... the phone will be just like "out of the box"
2- You only need TWRP to run the Guru Bootloader Reset, after that there's no more use for it, and you actually have to get rid of it for the phone to be 100% stock. (the ruu will replace twrp with the stock recovery)
3- fastboot commands are only run while the phone is in bootloader not recovery
fastboot.exe commands = bootloader/FASTBOOT USB
adb.exe commands = custom recovery or booted ROM with USB debugging enabled
EDIT: yes, rename the downloaded file to ruu.zip (for simplicity) and place it in your adb folder
make sure to check MD5 on the download
(and if you are using Windows Explorer to rename, be careful not to rename it to ruu.zip.zip)

nkk71 said:
1- Everything (literally) will be removed / wiped / replaced after flashing a RUU... the phone will be just like "out of the box"
2- You only need TWRP to run the Guru Bootloader Reset, after that there's no more use for it, and you actually have to get rid of it for the phone to be 100% stock. (the ruu will replace twrp with the stock recovery)
3- fastboot commands are only run while the phone is in bootloader not recovery
fastboot.exe commands = bootloader/FASTBOOT USB
adb.exe commands = custom recovery or booted ROM with USB debugging enabled
EDIT: yes, rename the downloaded file to ruu.zip and place it in your adb folder
Click to expand...
Click to collapse
Jeez, you're awesome. I really did not expect to get this much help, especially not this thorough and from the guy who wrote the guide himself! Thank you a ton, I extremely appreciate all of your help and I'll be returning this bad boy to stock in the coming hour or so. You took a lot of nerves off my mind and hopefully I'll be able to get this thing replaced!

Leather Sock said:
Jeez, you're awesome. I really did not expect to get this much help, especially not this thorough and from the guy who wrote the guide himself! Thank you a ton, I extremely appreciate all of your help and I'll be returning this bad boy to stock in the coming hour or so. You took a lot of nerves off my mind and hopefully I'll be able to get this thing replaced!
Click to expand...
Click to collapse
No problem, and Good Luck with replacement

nkk71 said:
No problem, and Good Luck with replacement
Click to expand...
Click to collapse
I'm having one problem. I don't know how to take off S-Off now that I've flashed the RUU. Everything is working perfectly and I don't have any OTA's done yet but I can't figure out how to get fastboot to work or whatever. It just says waiting for my device

Leather Sock said:
I'm having one problem. I don't know how to take off S-Off now that I've flashed the RUU. Everything is working perfectly and I don't have any OTA's done yet but I can't figure out how to get fastboot to work or whatever. It just says waiting for my device
Click to expand...
Click to collapse
Scratch that. Got it!

[Q] HTC One m7 Sprint no radio or main version after ROM install.

So I feel like I've pretty much shat on my myself here so now I'm finally coming for specific help.
Brand New Sprint HTC one m7 from the store after a purple camera replacement.
I unlock the bootloader, flash recovery. Still S-ON Somewhere along the way I can't get signal after I install the new ROM ( I assume from the wipe)
Try to manually input APN after I had to install an apk because APN wasn't a choice. Doesn't save.
Try installing a different rom. Either I can get into the rom and no signal or it will install and reboot after 5 min into the OS.
Restore from twrp recovery I moved to my PC before I did anything. Still nothing. possible cycling reboot.
Now here's the tricky part. (for me anyway)
So going into fasboot and inputting "getvar all" it returns with a version-main: none and version-baseband: N/A. Now trying to RUU the situation. With the windows program it gives me an error and when I "fastboot flash zip firmware.zip" it continually fails.
it says my CID is SPCS_001
RUUs i've tried:
1.29.651.10
1.29.651.7
4.06.651.4
I'm not exactly sure which one I'm meant to be using from this point because they all fail. I've them both locked and unlocked. And yes Inputted the flash command multiple times for each file.

what software version is currently installed in the phone? Post full pnone info
you must RUU the same version to get back to stock and eturn baseband if you are s-on.
I have had same situation. I was on 5.03.651.3. And i can only flash 5.03.651.30or newer (5.05.651.2), BUT NOT OLDER.
relock bootloader, enter fastboot usb, run AruWizard and wait. it may look loke process hangs while flashing, but just wait and be quiet. it can take 10-20 minutes

nick_fc said:
what software version is currently installed in the phone? Post full pnone info
you must RUU the same version to get back to stock and eturn baseband if you are s-on.
I have had same situation. I was on 5.03.651.3. And i can only flash 5.03.651.30or newer (5.05.651.2), BUT NOT OLDER.
relock bootloader, enter fastboot usb, run AruWizard and wait. it may look loke process hangs while flashing, but just wait and be quiet. it can take 10-20 minutes
Click to expand...
Click to collapse
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.

Synesthesis said:
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.
Click to expand...
Click to collapse
nobody can help you if you will not post full detailed phone info and detailed error description

Synesthesis said:
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.
Click to expand...
Click to collapse
We still have no idea what version your phone is ... if it just come back from servicing i would guess the updated it for you
What PC are you running the RUU from (OS / age of PC) ? what is the error you get when flashing just the firmware ?

Synesthesis said:
So I feel like I've pretty much shat on my myself here so now I'm finally coming for specific help.
Brand New Sprint HTC one m7 from the store after a purple camera replacement.
I unlock the bootloader, flash recovery. Still S-ON Somewhere along the way I can't get signal after I install the new ROM ( I assume from the wipe)
Try to manually input APN after I had to install an apk because APN wasn't a choice. Doesn't save.
Try installing a different rom. Either I can get into the rom and no signal or it will install and reboot after 5 min into the OS.
Restore from twrp recovery I moved to my PC before I did anything. Still nothing. possible cycling reboot.
Now here's the tricky part. (for me anyway)
So going into fasboot and inputting "getvar all" it returns with a version-main: none and version-baseband: N/A. Now trying to RUU the situation. With the windows program it gives me an error and when I "fastboot flash zip firmware.zip" it continually fails.
it says my CID is SPCS_001
RUUs i've tried:
1.29.651.10
1.29.651.7
4.06.651.4
I'm not exactly sure which one I'm meant to be using from this point because they all fail. I've them both locked and unlocked. And yes Inputted the flash command multiple times for each file.
Click to expand...
Click to collapse
post your getvar all here, remove your imei and serial number before posting.
No one can help you until we know exactly what firmware you already have on the device? And what Operating system you have on your pc? What recovery your using? and what Rom you tried to flash?
The side by side error can be addressed by installing a different or updated version of Microsoft c++ and your version main is missing because you used a version of TWRP recovery with the misc partition bug. But that's all I can tell you based on what you've shared already.

Danny201281 said:
post your getvar all here, remove your imei and serial number before posting.
No one can help you until we know exactly what firmware you already have on the device? And what Operating system you have on your pc? What recovery your using? and what Rom you tried to flash?
The side by side error can be addressed by installing a different or updated version of Microsoft c++ and your version main is missing because you used a version of TWRP recovery with the misc partition bug. But that's all I can tell you based on what you've shared already.
Click to expand...
Click to collapse
Ok to answer all the burning questions:
On the computer front I'm using a macbook pro with windows 7 Ultimate installed under bootcamp.
The phone is brand new. If it was serviced I'm not aware of it.
Recovery I'm currently using is TWRP 2.8.1.0. I was using 2.7 because I read a feint whisper in some other rom thread that the apn issue might be resolved that way. However since I was having intermittent OS cycling on reinstall to not have a mtp function during mount was frightening.
The first rom I tried to flash was ARHD 83.1 in an attempt to possibly s-off my device with firewater. Never got passed the rom flashing.
and for the big reveal:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4181mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse

Synesthesis said:
Ok to answer all the burning questions:
On the computer front I'm using a macbook pro with windows 7 Ultimate installed under bootcamp.
Click to expand...
Click to collapse
meh! I've no experiance with Mac, I don't know for sure but running Windows I assume as a VM could cause problems using the ruu.
The phone is brand new. If it was serviced I'm not aware of it.
Recovery I'm currently using is TWRP 2.8.1.0. I was using 2.7 because I read a feint whisper in some other rom thread that the apn issue might be resolved that way. However since I was having intermittent OS cycling on reinstall to not have a mtp function during mount was frightening.
Click to expand...
Click to collapse
Are you sure you flashed the Sprint compatible TWRP recovery. You can download them here http://techerrata.com/browse/twrp2/m7wls
The first rom I tried to flash was ARHD 83.1 in an attempt to possibly s-off my device with firewater. Never got passed the rom flashing
Click to expand...
Click to collapse
And here is what I believe is the root of your problem (hehe pun intended ) This Rom is definitely not Sprint compatible. Flashing this Rom would have messed up your partitions. It's for International Brand HTC one.
If your sure your recovery is the Sprint version. You probably just need to Format the device. With "Format Data" in TWRP then flash Sprint compatible Rom. Or if you think you need to, flash a TWRP from the above link.
Based on the fact your on Hboot 1.57 the latest Sprint RUU should work for you. But because your s-on you will need to relock your bootloader in order to flash it. Assuming you can get round the side by side error. But I think a proper Windows pc is whats required there. :good:
The Sprint Section of the forums here http://forum.xda-developers.com/sprint-htc-one is where you'll find roms for your phone. In Android Development and Original Android Development

Danny201281 said:
meh! I've no experiance with Mac, I don't know for sure but running Windows I assume as a VM could cause problems using the ruu.
Click to expand...
Click to collapse
bootcamp is a separate install. not a virtual machine
And here is what I believe is the root of your problem (hehe pun intended ) This Rom is definitely not Sprint compatible. Flashing this Rom would have messed up your partitions. It's for International Brand HTC one.
Click to expand...
Click to collapse
Yeah I realized that later but I even tried installing the Nocturnal Lollipop rom, the badboyz sense 6 rom which was what was on my last HTC one, viper, etc. with no good.
If your sure your recovery is the Sprint version. You probably just need to Format the device. With "Format Data" in TWRP then flash Sprint compatible Rom. Or if you think you need to, flash a TWRP from the above link.
Click to expand...
Click to collapse
going to try this part now. OK reformatted. so flashing 5.03.651.3 and 5.05.651.2 firmware full and modified gives me this:
sending 'zip' (25541 KB)...
OKAY [ 1.952s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.176s
I am locked again and in rebootRUU

Synesthesis said:
bootcamp is a separate install. not a virtual machine
Yeah I realized that later but I even tried installing the Nocturnal Lollipop rom, the badboyz sense 6 rom which was what was on my last HTC one, viper, etc. with no good.
going to try this part now. OK reformatted. so flashing 5.03.651.3 and 5.05.651.2 firmware full and modified gives me this:
sending 'zip' (25541 KB)...
OKAY [ 1.952s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.176s
I am locked again and in rebootRUU
Click to expand...
Click to collapse
Just flash a Sprint Rom with TWRP. The format will have sorted your partitions out. It should except a Sprint compatible Rom now.

Danny201281 said:
Just flash a Sprint Rom with TWRP. The format will have sorted your partitions out. It should except a Sprint compatible Rom now.
Click to expand...
Click to collapse
OK so I finally got to another computer last night. (which is a hassle since I travel all the time) and ran the ARUwizard that didn't work on my computer. THANK THANK THANK YOU YOU YOU.
And we're up and running with 5.03.651.3
So Now I'm back to square one. After the RUU it did removed the tampered flag which I thought was cool. But now I want to tamper again. :laugh:
So from this point any sprint based rom should be ok right? I feel like all this wasn't as hard when I was romstalling a year ago with my original phone or with the EVO.
Also what's this about the twrp partition error? What version of the recovery should I be using? I had been using CWM on the old phone because CM11 stopped installing correctly after a certain version of TWRP.

Synesthesis said:
OK so I finally got to another computer last night. (which is a hassle since I travel all the time) and ran the ARUwizard that didn't work on my computer. THANK THANK THANK YOU YOU YOU.
And we're up and running with 5.03.651.3
So Now I'm back to square one. After the RUU it did removed the tampered flag which I thought was cool. But now I want to tamper again. [emoji23]
So from this point any sprint based rom should be ok right? I feel like all this wasn't as hard when I was romstalling a year ago with my original phone or with the EVO.
Also what's this about the twrp partition error? What version of the recovery should I be using? I had been using CWM on the old phone because CM11 stopped installing correctly after a certain version of TWRP.
Click to expand...
Click to collapse
Ok cool, nice to hear your back up
You should be fine to flash any Sprint Compatible Rom also recovery must be Sprint Compatible. The reason is that Sprint HTC one's have a different partition layout the the International variants, so anything you flash must be specifically for your Sprint phone. Basically anything you find in the Sprint forums I linked previously should be fine :good:
The TWRP problem is that some version (unfortunately I don't know exactly which Sprint version) have a bug that inadvertently wipes the OS version information from the misc partitions. This is only a cosmetic bug and shouldn't cause any problems with your device but if your a little ocd like myself you'll preffer to avoid it. It can be rectified by flashing firmware.
For the International HTC One this happens with 2.7.x.x versions of TWRP with 2.7.1.1 being the worst offender. Best advice I can give is check in the Sprint forums use the search box to search for "blank os" or "blank version main" that should turn up something or ask your fellow Sprint users in the Sprint Q&A forums, they should be able to give you more direct advice on what versions to avoid