Database Develop

[Q] How htc-dev ruu and zip files work?

Hi guys! I have a question...
I was thinking about using a RUU to clean install a stock rom on my one...so, I was at htc-dev site and looked at downloads...
I find: the developer edition RUU, android 4.3 (the last one)...ok, this is the classic RUU, I have to execute it when I'm on "fastboot oem rebootRUU", I'm s-off, it wipes everything and I have the stock firmware and rom...and it's ok...have I got to relock the bootloader?
then....I see, just below, a zip file, as big as the RUU one, but is a zip...what is this? is the zip that the RUU flashes, but for a different use, with the raw method, on the terminal?
and, another one...I looked at the google play edition section...and I founded two zips for each version: one "stock ui" and one "framework support files"....ok, what is this?! isn't there a RUU? what if I want to flash a clean google play edition, with full wipe and stock clean firmware? what can I do with these files?
thank you for listening, and sorry for my bad english

throcker said:
Hi guys! I have a question...
I was thinking about using a RUU to clean install a stock rom on my one...so, I was at htc-dev site and looked at downloads...
I find: the developer edition RUU, android 4.3 (the last one)...ok, this is the classic RUU, I have to execute it when I'm on "fastboot oem rebootRUU", I'm s-off, it wipes everything and I have the stock firmware and rom...and it's ok...have I got to relock the bootloader?
then....I see, just below, a zip file, as big as the RUU one, but is a zip...what is this? is the zip that the RUU flashes, but for a different use, with the raw method, on the terminal?
and, another one...I looked at the google play edition section...and I founded two zips for each version: one "stock ui" and one "framework support files"....ok, what is this?! isn't there a RUU? what if I want to flash a clean google play edition, with full wipe and stock clean firmware? what can I do with these files?
thank you for listening, and sorry for my bad english
Click to expand...
Click to collapse
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"

an0ther said:
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"
Click to expand...
Click to collapse
ok, thanks for your answer, first....
I already tried the conversion, and it worked fine...but that's not what I'm looking for
I was asking how does the official source files work...

delete me

throcker said:
ok, thanks for your answer, first....
I already tried the conversion, and it worked fine...but that's not what I'm looking for
I was asking how does the official source files work...
Click to expand...
Click to collapse
What do you mean 'work'? They are used to put the phone back to a factory state, a hard reset if you will. It means you can always revert back to stock should you want/need to send it in for repair
As for GPe files, they are not for flashing and are source files to make your own software

EddyOS said:
What do you mean 'work'? They are used to put the phone back to a factory state, a hard reset if you will. It means you can always revert back to stock should you want/need to send it in for repair
As for GPe files, they are not for flashing and are source files to make your own software
Click to expand...
Click to collapse
OK that's the answer! GPE files are the source? same for the zip file next the ruu?

No, the RUU and the 1GB ZIP are the same thing but flashed in different ways...
The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation

Basic Steps but...
Not worked for me, i downloaded right htcdev rom for my desire c
Waiting for device... is appeared and no way out.
Any Ideas??
EddyOS said:
No, the RUU and the 1GB ZIP are the same thing but flashed in different ways...
The RUU is your normal, executable program and does everything for you. The ZIP is an RUU but you have to set the phone up to flash it by using fastboot commands. the process is:
1. Connect phone in fastboot mode
2. Run the command 'fastboot oem rebootRUU'
3. Once the phone is at the HTC screen, you run the command 'fastboot flash zip name_of_zip.zip'
4. It will flash the first part and then give an error and you run the same command as above a second time straight away
5. Once the second flash sequence has finished, you the type 'fastboot reboot' and it will reboot the phone and finish the installation
Click to expand...
Click to collapse

an0ther said:
You must have s-off and super cid "11111111" to flash ruu that are not specific to your phone. You do not have to lock your bootloader. Again, you MUST have s-off and super cid! As long as you have those, you can pretty much convert your phone to whichever you want. I always recommend downgrading your hboot to 1.44 before doing this. You need encrypted ruu's to use the "fastboot oem rebootRUU" mode. Remember to flash stock recovery if you want OTA updates. I have never used the .exe files. I converted my att htc one to google edition, then back, then developer, then back. Its really no different than just running roms, but at least you get a new splash screen and bootloader with each.
http://forum.xda-developers.com/showthread.php?t=2358781 This is the google edition conversion link I used my first time converting my phone. if you look at post 2, it shows how to go back to stock "or pretty much any ruu"
Click to expand...
Click to collapse
Hey, sorry for bothering you, i am trying to revert my Htc desire 510 to stock, i do not have a backup. I found files on the htcdev.com and thought they were Roms (easy catch). Unfortunately they are not. I dont even know what to do with these files inorder to get my rom in place. pleace help me.

Zubagy said:
Hey, sorry for bothering you, i am trying to revert my Htc desire 510 to stock, i do not have a backup. I found files on the htcdev.com and thought they were Roms (easy catch). Unfortunately they are not. I dont even know what to do with these files inorder to get my rom in place. pleace help me.
Click to expand...
Click to collapse
There are no more RUU on htcdev.com, these files are kernel source code and not useful to restore your phone. Can you post the output of "fastboot getvar all" (hide your IMEI and serialno), I'll check if I can find something for you.

alray said:
There are no more RUU on htcdev.com, these files are kernel source code and not useful to restore your phone. Can you post the output of "fastboot getvar all" (hide your IMEI and serialno), I'll check if I can find something for you.
Click to expand...
Click to collapse
Thank you for your response. This is what i get
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 01.02.012_U10251_39.08.40922
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: xxxx
INFOimei: xxxx
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: a11_ul
INFOplatform: hTCBmsm8916
INFOmodelid: 0PCV20000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 295e1798
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOmfg-name: 1001
all: Done!

Zubagy said:
Thank you for your response. This is what i get
INFOversion: 0.5
INFOversion-bootloader: 3.19.0.0000
INFOversion-baseband: 01.02.012_U10251_39.08.40922
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: xxxx
INFOimei: xxxx
INFOimei2: Not Support
INFOmeid: 00000000000000
INFOproduct: a11_ul
INFOplatform: hTCBmsm8916
INFOmodelid: 0PCV20000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 0mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 295e1798
INFOhbootpreupdate: 11
INFOgencheckpt: 0
INFOmfg-name: 1001
all: Done!
Click to expand...
Click to collapse
There are 3 RUU for Vodafone UK's Desire 510:
1.51.161.10
1.51.161.11
1.51.161.12
Unfortunately these files are only available from a paid site (ir-file)
Not sure which one you'll need since your version-main is blank
Here are the files name just in case you can find elsewhere than ir-file:
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.10_Radio_01.02.012_U10251_39.08.40922_release_416938_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.11_Radio_01.02.012_U10251_39.08.40922_release_427262_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.12_Radio_01.02.012_U10251_39.08.40922_release_450233_combined_signed.zip

alray said:
There are 3 RUU for Vodafone UK's Desire 510:
1.51.161.10
1.51.161.11
1.51.161.12
Unfortunately these files are only available from a paid site (ir-file)
Not sure which one you'll need since your version-main is blank
Here are the files name just in case you can find elsewhere than ir-file:
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.10_Radio_01.02.012_U10251_39.08.40922_release_416938_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.11_Radio_01.02.012_U10251_39.08.40922_release_427262_signed.zip
0PCVIMG_A11_UL_K443_DESIRE_SENSE60_Vodafone_UK_1.51.161.12_Radio_01.02.012_U10251_39.08.40922_release_450233_combined_signed.zip
Click to expand...
Click to collapse
Thankyou for your help, ill get started on looking for them. does this work, found it but still have my doubts... not yet downloaded it.
https://www.dropbox.com/s/cp3hif7sg...51_39.08.40922_release_398419_signed.rar?dl=0

Zubagy said:
Thankyou for your help, ill get started on looking for them. does this work, found it but still have my doubts... not yet downloaded it.
https://www.dropbox.com/s/cp3hif7sg...51_39.08.40922_release_398419_signed.rar?dl=0
Click to expand...
Click to collapse
no, your phone is S-ON and branded to vodafone UK so you can only use RUU for vodafone UK (x.xx.161.x).
1.51.401.1 is for HTC Europe WWE not vodafone.

alray said:
no, your phone is S-ON and branded to vodafone UK so you can only use RUU for vodafone UK (x.xx.161.x).
1.51.401.1 is for HTC Europe WWE not vodafone.
Click to expand...
Click to collapse
A developer sent me this link, looks like it is The ONE. But it looks a lower version than the ones that u mentioned above.
https://mega.nz/#!d4ZknKYT!ZhCHoiBSNJl3pBO_G-uv518ssNrGDY6UPH4EpqZ7qog

Zubagy said:
A developer sent me this link, looks like it is The ONE. But it looks a lower version than the ones that u mentioned above.
https://mega.nz/#!d4ZknKYT!ZhCHoiBSNJl3pBO_G-uv518ssNrGDY6UPH4EpqZ7qog
Click to expand...
Click to collapse
I would try this one

alray said:
I would try this one
Click to expand...
Click to collapse
Oh, ok, then let me get started with it. By the way, do u happen to know where i can also pick any custom ROMs for the 64bit, i checked out the cm12, but its gat bugs

Zubagy said:
Oh, ok, then let me get started with it. By the way, do u happen to know where i can also pick any custom ROMs for the 64bit, i checked out the cm12, but its gat bugs
Click to expand...
Click to collapse
not sure for x64 but everything should be here: http://forum.xda-developers.com/desire-510

[Q] HTC One unlocked, tampered, S-ON and custom recovery - Can I do OTA

Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND

Torcidas1950 said:
PLEASE RESPOND
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH

alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH
Click to expand...
Click to collapse
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery. And how do I do that?

Torcidas1950 said:
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery.
Click to expand...
Click to collapse
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
And how do I do that?
Click to expand...
Click to collapse
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #

Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.

So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?

iElvis said:
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.
Click to expand...
Click to collapse
alray said:
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #
Click to expand...
Click to collapse
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?

Torcidas1950 said:
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
Click to expand...
Click to collapse
post your "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
post your "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.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-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3894mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Torcidas1950 said:
Here it is:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock

nkk71 said:
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock
Click to expand...
Click to collapse
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.

Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
1- If you are 100% stock then Settings -> About should also show your correct version number
2- you rooted the phone, so that may or may not have changed some system files, so OTA may not work
3- once S-Off stay S-Off, my personal opinion
In my humble opinion, three choices really, when it comes to "modding" or not your phone:
A) stay stock and don't mess with it to get OTAs
B) you cannot achieve S-OFF (due to newer hboots, or device problems) -> fine live with an unlocked bootloader, and accept the fact that you cannot install OTAs .... you can however "download and install later" the OTA, then pull it to your phone, and use the signed firmware.zip in it
C) you can achieve S-OFF and want to mod your phone -> then do it, get S-Off and enjoy the freedom (but don't flash things not meant for your phone!! this goes for S-On too)
Of course you're going to say that "but S-Off is dangerous", it's a double edged sword... sometimes you are able save your phone thanks to S-Off, and sometimes you can brick it completely.
But then again, you can easily brick an S-On phone too (especially one that is modded), and much more difficult to save than an S-Off phone.
^^ All that is my personal opinion, and I'm not suggesting you S-Off, but if you want to mod your phone (whether S-On or S-Off), you need to be aware of what may, or may not, go wrong, and have done some reading and research
Good Luck

Well, its not worth it. I wont risk bricking my phone again

Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
Torcidas1950 said:
Well, its not worth it. I wont risk bricking my phone again
Click to expand...
Click to collapse
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes

nkk71 said:
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes
Click to expand...
Click to collapse
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me

Torcidas1950 said:
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me
Click to expand...
Click to collapse
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this

nkk71 said:
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this
Click to expand...
Click to collapse
Well, I am not planing to unplug the cable haha.. well if someone else knows please tell, the update is coming soon so I would like to know, but if its risky, there is no way I'm doing it

Torcidas1950 said:
but if its risky, there is no way I'm doing it
Click to expand...
Click to collapse
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71

nkk71 said:
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71
Click to expand...
Click to collapse
So, yesterday the OTA was finally released, and today I have flashed stock recovery... Now waiting for the OTA notification to come
Sent from my HTC One using XDA Free mobile app

hello guys,
i did a deep search, but nothing found about it, or found but did not understood, so i will ask you. if in my stock recovery it also says (TAMPER), will be possibly to instal OTA?
L.E. - rest is like the title of the topic - Unlocked, S-ON, tampered..

[Q] Flashed Wrong RUU Trying to go back to Stock, Booloop and Recovery Won't Work

Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?

bradreputation said:
Hey guys and girls. A little backstory:
New to android
Use Cyanogenmod Installer
Get Purple Camera. Need to go back to stock.
Stumble upon guide by nkk71 http://forum.xda-developers.com/showthread.php?t=2541082
Botch last step
So I found an ruu with my CID and MID, but it was the GPE ruu not the ATT RUU! The ATT RUU zips don't list CID and MID so I assumed I should not use them and all that matters is matching those.
I had locked and went back to s-On when following the guide.... big mistake.
I've since unlocked and tried to root so that I could go back to S-Off.
Flashed several different correct recoveries and none will work. I am erasing the cache, but nothing works. I've tried the most recent versions of CWM and TWRP and can't get anywhere.
What should I try next?
Click to expand...
Click to collapse
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)

nkk71 said:
Sorry to hear that, I thought my guide was pretty clear
please post
1- a fastboot getvar all (excluding IMEI and s/n)
2- a screenshot of your bootloader
3- more details of what you have flashed (with links to the threads)
Click to expand...
Click to collapse
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: CWS__001
battery-status: good
battery-voltage: 4291mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.

bradreputation said:
Your guide is very good and I thank you for it. I just messed up. I think it would be good to clarify that a person should reboot after flashing RUU before going back to S-On. I had the impression that was my only chance to go back S-On.
Click to expand...
Click to collapse
Technically, you can, but shouldn't reboot the OS because of the OTA notification, which may make it tempting to take, but I'll try and rephrase the guide.
bradreputation said:
version-bootloader: 1.54.0000
version-main:
version-misc: PVT SHIP S-ON
product: m7_ul
modelid: PN0712000
cidnum: CWS__001
http://imgur.com/yXDR6lr Shot of my Bootloader
This is what I flashed for RUU http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
I've flashed the latest TWRP and CWM. The problem really started when I installed CWM and Su from this guidehttp://forum.xda-developers.com/showthread.php?t=2292729.
Click to expand...
Click to collapse
bootloader is unlocked, good... do NOT try and lock it!!
reflash TWRP and a custom ROM (you can try ARHD 31.6 or similar), and get S-OFF using rumrunner and/or firewater
i'm off for tonight, sorry about the mess

The stock att RUU's would almost certainly have the stock CWS_001 Cid. You just need one that is the same or postdated to your current hboot version since you are s-on now. Unfortunately, now that you are s-on, you will also need to relock the bootloader to flash an RUU. I would do that and then use firewater/rumrunner/latest s-off method to get s-off and unlock boot loader. Then you want to fix the "relocked" flag to "locked", and s-on again, and get it repaired.

I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE: http://androidruu.com/getdownload.p...13_10.38j.1157.04_release_334235_signed_2.exe
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_cingular-1-26-502-15-decrypted-zip/
AFH Mirror: http://www.androidfilehost.com/?fid=23501681358544977

nkk71 said:
I would try to get S-OFF where you are now.
I'll keep this here just in case
Otherwise, you can use the 3.xx RUU.EXE:
this will upgrade to hboot 1.55, and rumrunner and/or firewater should work on it.
(remember you need to relock bootloader for that to work with S-On, that's why i'm recommending to try where you are now, so you don't lock bootloader)
there is also a 4.xx RUU but do not use it, because it will upgrade your hboot to 1.56, making it even more difficult to S-OFF.
and once you're S-OFF, you should use this ruu.zip for my guide (which is for PN0712000 + CWS__001):
]
Click to expand...
Click to collapse
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.

bradreputation said:
I was able to get TWRP (newest version) and ARHD (31.6) running. I then got S-OFF using Firewater. I'll use the RUU and follow the guide again.
I saw another one of your posts that suggested S-OFF may not effect warranty claims. Any further thought on that?
Thanks again for all your contributions.
Click to expand...
Click to collapse
It's really very country/carrier/people specific, in theory, S-Off shouldn't matter as some phones accidentally ship S-Off (ok, it's very very very rare), but S-Off shouldn't void warranty https://twitter.com/htc/status/377422743626842112
Then again, in practice some carriers/technicians may try to use any excuse to refuse warranty.

[Q] Restore to Stock ROM and Lock BL

Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance

sheppy1 said:
Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance
Click to expand...
Click to collapse
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.

majmoz said:
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.
Click to expand...
Click to collapse
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks

sheppy1 said:
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks
Click to expand...
Click to collapse
Based on your getvar all you have a Int'l (.401) phone not an O2 UK branded phone. You will need to follow the directions of this site for stock rom 5.11.401.10 and you should be back whole. You can get the stock firmware if you need it from this site: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One%2F401%2F Just select the 5.11.401.10 firmware.
For S-OFF, you need to be as close to stock as you can. If you are getting "whelp not able to S-OFF" then you might look at Sunshine S-OFF, but there is a price use it.

I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?

sheppy1 said:
I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?
Click to expand...
Click to collapse
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.

majmoz said:
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.
Click to expand...
Click to collapse
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?

sheppy1 said:
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?
Click to expand...
Click to collapse
Yes, you will have stock recovery, stock radio and stock hboot.

majmoz said:
Yes, you will have stock recovery, stock radio and stock hboot.
Click to expand...
Click to collapse
Thanks for all your help!

Should my bootloader still say "tampered"?

sheppy1 said:
Should my bootloader still say "tampered"?
Click to expand...
Click to collapse
Yes, you would have to be S-OFF to reset it.

Okay thank you! Was just thinking that something sill wasn't back to stock so thought I'd check

Screen not responding to touch in TWRP

was trying to root my one for the first time. I followed someone's tutorial online, and everything was perfect at first, until I got into using TWRP for recovery. I used version 2.5. After I got into it, the touch screen is not working. I stuck in the lock screen now, not able to unlock, not able to restart, not even able to power off. After some digging, I found out that probably I should have used the version 2.6 instead in the first place. Now my question is, do I need to wait until the power drains out before I could do anything else, or if there is anything I could do to restart the phone and do this recovery process again with TWRP v2.6? Thanks.
Click to expand...
Click to collapse
have exactly the same problem.
But I can't hard reset the HTC ONE via volume down + power button...
Can't access the phone via USB attached cable and the common tools... :///
Do I have to wait till the battery is empty or is there a further solution?

vin4ester15 said:
have exactly the same problem.
But I can't hard reset the HTC ONE via volume down + power button...
Can't access the phone via USB attached cable and the common tools... :///
Do I have to wait till the battery is empty or is there a further solution?
Click to expand...
Click to collapse
Try the reset with device under a bright light.
What device do you have and what twrp did you flash.

mb_guy said:
Try the reset with device under a bright light.
What device do you have and what twrp did you flash.
Click to expand...
Click to collapse
Looks like its 2.5.0.0 from the picture

mb_guy said:
Try the reset with device under a bright light.
What device do you have and what twrp did you flash.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=rRkAHw_GmIs&list=FLp-bV1_Di0EtsQXswt1FQuQ&index=2

vin4ester15 said:
https://www.youtube.com/watch?v=rRkAHw_GmIs&list=FLp-bV1_Di0EtsQXswt1FQuQ&index=2
Click to expand...
Click to collapse
? what does that tell me about your actual device, carrier, model etc.

mb_guy said:
? what does that tell me about your actual device, carrier, model etc.
Click to expand...
Click to collapse
look 2:05 https://www.youtube.com/watch?v=6fjBcnEJYbI

Ohhh, i reboot it with brith light. But now how to install a normal TWRP? Phone is unlocked. S-off

vin4ester15 said:
Ohhh, i reboot it with brith light. But now how to install a normal TWRP? Phone is unlocked. S-off
Click to expand...
Click to collapse
Why not giving us your phone info here instead of playing this "look at this youtube video" game? If you want help, please answer the questions asked above, better to post a complete "fastboot getvar all" output (excluding your IMEI/MEID/Serialno) so we know everything about your phone an can help you better.
If you have a sprint HTC one, then flash a sprint twrp recovery. You can find the file on the twrp website.
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader

vin4ester15 said:
Ohhh, i reboot it with brith light. But now how to install a normal TWRP? Phone is unlocked. S-off
Click to expand...
Click to collapse
Sorry, but I'm going to let @alray help with this one. Looks like you have 5.05.651.2 rom installed. Is this a sprint device or some other m7_wls device? I have no experience with these, and see many posts with folks flashing wrong recovery or rom and bricking devices.

mb_guy said:
Sorry, but I'm going to let @alray help with this one. Looks like you have 5.05.651.2 rom installed. Is this a sprint device or some other m7_wls device? I have no experience with these, and see many posts with folks flashing wrong recovery or rom and bricking devices.
Click to expand...
Click to collapse
What of them I can install? http://www.htc.com/us/support/rom-downloads.html#unlocked
My phone is unlocked, i can use Any SIM card

vin4ester15 said:
What of them I can install? http://www.htc.com/us/support/rom-downloads.html#unlocked
My phone is unlocked, i can use Any SIM card
Click to expand...
Click to collapse
I don't think you can install any ruu, yet. I also noticed from your video that your device is s-off (security off) no problem, but also supercid (11111111), this is a problem. I don't think a ruu will flash until the cid is reverted to what ever it was initially from the installed ruu carrier. Sprint cid is SPCS_001 for example. I think you will have to rewrite this from adb, but getting out of my knowledge zone here, sorry.

mb_guy said:
I don't think you can install any ruu, yet. I also noticed from your video that your device is s-off (security off) no problem, but also supercid (11111111), this is a problem. I don't think a ruu will flash until the cid is reverted to what ever it was initially from the installed ruu carrier. Sprint cid is SPCS_001 for example. I think you will have to rewrite this from adb, but getting out of my knowledge zone here, sorry.
Click to expand...
Click to collapse
You can flash a RUU with supercid, no problem. But since his phone is a sprint variant, having supercid is somewhat useless since he can only flash RUU for sprint (SPCS_001). Having supercid on a sprint M7 won't hurt but its pretty useless imo... (unlike having supercid on a M7_U/M7_UL which will allow you to flash any RUU you want)

alray said:
You can flash a RUU with supercid, no problem. But since his phone is a sprint variant, having supercid is somewhat useless since he can only flash RUU for sprint (SPCS_001). Having supercid on a sprint M7 won't hurt but its pretty useless imo... (unlike having supercid on a M7_U/M7_UL which will allow you to flash any RUU you want)
Click to expand...
Click to collapse
ohh, i'm a really noob, i install this RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.05.651.6_Radio_1.00.20.1108_NV_SPCS_4.38_003_release_348053_signed_2 Now, i don't have GSM\3g and sim is lock :crying: how to fix?

vin4ester15 said:
ohh, i'm a really noob, i install this RUU_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.05.651.6_Radio_1.00.20.1108_NV_SPCS_4.38_003_release_348053_signed_2 Now, i don't have GSM\3g and sim is lock :crying: how to fix?
Click to expand...
Click to collapse
Sprint M7 is a CDMA phone and will only work on the Sprint network (it can connect to other gsm networks for roaming but you won't get full connectivity), its not the result of the RUU. And btw a RUU can't sim lock a phone, its not possible. The ruu doesn't write anything to the partition where the sim lock info are stored.
can't help any further if you don't post the output of "fastboot getvar all" like asked previously. I don't have time right now to watch some youtube video to figure out what device you have etc.

alray said:
Sprint M7 is a CDMA phone and will only work on the Sprint network (it can connect to other gsm networks for roaming but you won't get full connectivity), its not the result of the RUU. And btw a RUU can't sim lock a phone, its not possible. The ruu doesn't write anything to the partition where the sim lock info are stored.
can't help any further if you don't post the output of "fastboot getvar all" like asked previously. I don't have time right now to watch some youtube video to figure out what device you have etc.
Click to expand...
Click to collapse
C:\Users\Vitalie01\Desktop\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>fast
boot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA36BS907523
(bootloader) imei: 355859056246580
(bootloader) meid: 99000146869492
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3976mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Before that, it worked. The phone was like out of the store without being tied to an operator. Due to the fact that I could not be updated to Android 5.0, I downloaded the firmware from the official site and set it. With the new firmware the connection was lost. Now I can not use 3G. From the beginning, radio was 1.00 and android 4.4.2. The other parameters are listed in the video at minute 2:05

I tried to install a new version via exe files and zip through. Even I tried to put ViperOne, but once it is installed, an error, TWRP and firmware is deleted. I again through fastboot TWRP load and backup. Otherwise, when you turn on it immediately goes into fastboot, and so on. Something is missing this phone for the proper installation of new versions of android.