Database Develop

[Q] Strange issues - Return to Stock Needed...

Hi guys,
This is mostly my fault I believe. Like a young boy, excited about a new toy that just came out, I tried to flash the new Sprint OTA update in TWRP. Well, it failed just as I thought it may. Later on, I read that flashing that OTA in any recovery was something that should not be done. At any rate, it is too late to change what has been done.
The issue that I am facing, which seems to coincide with the day that I flashed the OTA in TWRP, is that people are only receiving only one part of my text messages. For instance, say I type a long message which would equal the length of 3 SMS messages. The recipient will only receive part 1/3 or part 3/3.
I updated my PRL and Profile.... No change... So, I decided to go back to stock and endure the grueling process of restoring my phone's SMS logs, contacts, configuration, etc, etc. I know that Google will sync and most of my contacts will be replaced. But some things like games I pay money to play must be reconfigured and other customizations will have to be "re-customized".
Regardless, I need to go back to stock and start all over. I tried several methods, all required that the bootloader be re-locked. This is when the trouble started. I relocked the bootloader via Fastboot. But running the RUU for version 1.29.651.7 fails as I am on 1.31 I believe? I will paste my specs below.
Anyway, it all boils down to a couple of things.
1.) Returning to Stock using an image that is NOT roooted (and also encrypted)?
2.) Returning my Bootloader to stock so that I can run the latest OTA (Is it recommended to run the latest OTA?)
3.) Doing it without bricking my device. Lol!
Now, I have the latest SDK for ADB installed. I have several different Stock images I've downloaded and tried but they all fail. I'm afraid that I am going to have to use one that is 1.31.xxx..
So here is my info from Fastboot, I can provide more detailed information if needed.
C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4197mV
(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.194s
Click to expand...
Click to collapse
Again, the goal is stock (unrooted), just like it came out of the box. I will re-root again later but for now I need to fix this SMS issue as it's making it hard to communicate with my colleagues and friends. Again, should I flash the new Sprint OTA update that takes me up to 4.3.3? It does sound tantalizing to see what new features they have incorporated in this update. Here is the name of the OTA:
OTA_M7_WL_JB43_SENSE50_SPCS_MR_Sprint_WWE_3.04.651.2-1.31.651.2_release_335437r9p4z0zrva4gqsfs
Click to expand...
Click to collapse
As usual, any help or insight in to my problem(s) is appreciated. And for the record, the bootloader is again "unlocked". My plan as of right now is to recover using a NANDROID I made about a month ago. This should fix the SMS issue, but I still need to go back to stock so I can start from scratch.
Thanks in advance!
Regards,

Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app

Here is a helpful link also: http://forum.xda-developers.com/showthread.php?t=2277892
Sent from my HTCONE using Tapatalk

Konfuzion said:
Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Ok, I'll follow the instructions. Thank you for pointing me in the right direction. It does suck though, 4.3.3 is supposed to bring some new and exciting additions to the Android OS.
Anyway, I'll post if I run in to problems.
Thanks!

tonyrance said:
Here is a helpful link also: http://forum.xda-developers.com/showthread.php?t=2277892
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Thanks Tonyrance!

PAinguINx said:
Ok, I'll follow the instructions. Thank you for pointing me in the right direction. It does suck though, 4.3.3 is supposed to bring some new and exciting additions to the Android OS.
Anyway, I'll post if I run in to problems.
Thanks!
Click to expand...
Click to collapse
You can update to 4.3 manually after getting s-off
Shoot me a PM if you need help with any of it

Konfuzion said:
Whatever you do do not take the 4.3 OTA!
Get back to 1.29 and root and s-off, there is no RUU for 4.3 so if you get that and mess anything up your screwed unless you have s-off.
Follow this guide to RUU back to 1.29 on 1.31 (you will see an error in doing this just keep going)
http://forum.xda-developers.com/showthread.php?p=44243635
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?

PAinguINx said:
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?
Click to expand...
Click to collapse
Run the 1.29.651.10 RUU then use revone or mooshine to s-off

bigdaddy619 said:
Run the 1.29.651.10 RUU then use revone or mooshine to s-off
Click to expand...
Click to collapse
Ok, that's the RUU I have, well the only one I have that has a "Setup.exe" the others just contain misc files and a .img file..
Could you run through the process for installing revone via ADB please? I've seen several different methods. Just want to make sure everything works out properly.

Ok, following these instructions I still run in to issues with ADB. I was able to open a Shell while the phone was on and booted but when I boot in to recovery and try to start a shell it states "error: device not found".
This is what I'm doing...
Hello, here is a very simple guide to be able to use revone to s-off on the 1.31 update.
Make sure you have dev unlocked and you flashed a custom recovery (CWM or TWRP both work fine)
After that, you need to make sure adb works (if you can't figure out how to do any of this, I will not help you. If you can't find out basic things about Android, then you shouldn't have s-off)
So, as we all know, HTC has made it so with newer bootloaders, you cannot downgrade to older firmwares. Well, this is true except when the software version changes but the hboot version doesn't. So all we need to do is this:
Boot into recovery
adb shell
echo "1.29.651.10" | dd of=/dev/block/mmcblk0p19 bs=1 seek=160
adb reboot bootloader
fastboot oem lock
then just flash an RUU of 1.29 and it'll work out. All you do is flash the misc partition to contain the proper mainver and it works.
Click to expand...
Click to collapse
What am I doing wrong as to not obtain a shell?

PAinguINx said:
Ok, that's the RUU I have, well the only one I have that has a "Setup.exe" the others just contain misc files and a .img file..
Could you run through the process for installing revone via ADB please? I've seen several different methods. Just want to make sure everything works out properly.
Click to expand...
Click to collapse
Check PM

PAinguINx said:
Konfuzion,
After I complete this process, do I need to use revone to obtain S-OFF or is there another method?
Click to expand...
Click to collapse
This is the easiest way I know of to use Revone
http://forum.xda-developers.com/showthread.php?p=42452138#post42452138
However moonshine might be a better bet since it has the modified hboot which gets rid of the red warning text on boot. I am guessing bigdaddy pointed you in the right direction for the RUU.

bigdaddy619 said:
Check PM
Click to expand...
Click to collapse
I thought I messaged you man. But I didn't get a confirmation. Anyway, I donated $25 to you. Thanks again for your help bro. It has been appreciated!

[Q] Htc One return back to original stock ROM to get OTA

Hi,
Below are the details of my instrument HTC One and right now am on Revolution HD ROM 4.3+Sense5.5 rooted. I would like to go back to original stock ROM to get OTA. Kindly let me know complete detailed procedure to unroot and get back to stock as original factory reset.
C:\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4148mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Regards!
Kashif

http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Instal this. Stock rom and stock recovery in one zip. Version Stock rom and firmware must be the same. 2.24.401.8 propably will work good. I dont see 2.24.401.9. After this you have stock phone and you get OTA updates. (bootloader still be "unlocked") But you must know that some people write after back to stock and OTA from htc they phone dont bootup. OTA can brick your phone. Sorry for my english.

Htc One return back to original stock ROM to get OTA
xnobex said:
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Instal this. Stock rom and stock recovery in one zip. Version Stock rom and firmware must be the same. 2.24.401.8 propably will work good. I dont see 2.24.401.9. After this you have stock phone and you get OTA updates. (bootloader still be "unlocked") But you must know that some people write after back to stock and OTA from htc they phone dont bootup. OTA can brick your phone. Sorry for my english.
Click to expand...
Click to collapse
Hi,
Can I do S-Off and lock the bootloader after restoring guru reset and ota. Will it retain the stock and able to get future ota

kash_9763 said:
Hi,
Can I do S-Off and lock the bootloader after restoring guru reset and ota. Will it retain the stock and able to get future ota
Click to expand...
Click to collapse
Quick question (gotto go away for a bit): why do you want to go through all the hassle involved?

Htc One return back to original stock ROM to get OTA
xnobex said:
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Instal this. Stock rom and stock recovery in one zip. Version Stock rom and firmware must be the same. 2.24.401.8 propably will work good. I dont see 2.24.401.9. After this you have stock phone and you get OTA updates. (bootloader still be "unlocked") But you must know that some people write after back to stock and OTA from htc they phone dont bootup. OTA can brick your phone. Sorry for my english.
Click to expand...
Click to collapse
nkk71 said:
Quick question (gotto go away for a bit): why do you want to go through all the hassle involved?
Click to expand...
Click to collapse
I want to get back to the Stock ROM as original with lock bootloader, I did rooted to get OTA but now I want to regain the original one.

kash_9763 said:
I want to get back to the Stock ROM as original with lock bootloader, I did rooted to get OTA but now I want to regain the original one.
Click to expand...
Click to collapse
Don't really understand why anybody would want to go backwards, except for warranty, but in any case, your choice so here goes: you need s-off
1- So download Guru Reset 2.24.401.8 (closest available to your version): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Flash it, you do need to WIPE, deselect "stock recovery", select ROOT, radio doesnt matter
2- Download rumrunner package 2.24.401.9, and use it to get S-Off
once s-off
3- remove TAMPERED: http://forum.xda-developers.com/showthread.php?t=2477792
4- set your phone to LOCKED: http://forum.xda-developers.com/showthread.php?t=2475914
5- download and run the following RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- do not take any OTA YET
7- if you insist on S-On, then "fastboot oem writesecureflag 3", if you don't mind keeping S-Off keep it
8- take the OTAs
If I've helped hit the thanks button
Let me know if you need any more help

nkk71 said:
Don't really understand why anybody would want to go backwards, except for warranty, but in any case, your choice so here goes: you need s-off
1- So download Guru Reset 2.24.401.8 (closest available to your version): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Flash it, you do need to WIPE, deselect "stock recovery", select ROOT, radio doesnt matter
2- Download rumrunner package 2.24.401.9, and use it to get S-Off
once s-off
3- remove TAMPERED: http://forum.xda-developers.com/showthread.php?t=2477792
4- set your phone to LOCKED: http://forum.xda-developers.com/showthread.php?t=2475914
5- download and run the following RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- do not take any OTA YET
7- if you insist on S-On, then "fastboot oem writesecureflag 3", if you don't mind keeping S-Off keep it
8- take the OTAs
If I've helped hit the thanks button
Let me know if you need any more help
Click to expand...
Click to collapse
Thanks Dear! I will try and update you once done.

Htc One return back to original stock ROM to get OTA
nkk71 said:
Don't really understand why anybody would want to go backwards, except for warranty, but in any case, your choice so here goes: you need s-off
1- So download Guru Reset 2.24.401.8 (closest available to your version): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Flash it, you do need to WIPE, deselect "stock recovery", select ROOT, radio doesnt matter
2- Download rumrunner package 2.24.401.9, and use it to get S-Off
once s-off
3- remove TAMPERED: http://forum.xda-developers.com/showthread.php?t=2477792
4- set your phone to LOCKED: http://forum.xda-developers.com/showthread.php?t=2475914
5- download and run the following RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- do not take any OTA YET
7- if you insist on S-On, then "fastboot oem writesecureflag 3", if you don't mind keeping S-Off keep it
8- take the OTAs
If I've helped hit the thanks button
Let me know if you need any more help
Click to expand...
Click to collapse
Hi,
I have took TWRP backup of 4.2.2 but not in zip format. If I do restore that backup and do lock the bootloader then I will be on Stock original ROM? and also able to get OTA? Kindly help me out

kash_9763 said:
Hi,
I have took TWRP backup of 4.2.2 but not in zip format. If I do restore that backup and do lock the bootloader then I will be on Stock original ROM? and also able to get OTA? Kindly help me out
Click to expand...
Click to collapse
No need to lock bootloader to get OTA, you just need:
1- stock rom
2- (preferably) matching firmware
3- stock recovery
so if your TWRP backup is same version as firmware, then just restore it, that will get you back to stock rom.
after that, you still need to flash stock recovery; for you (2.24.401.9) you can use the 2.24.401.8 from here: http://forum.xda-developers.com/showthread.php?t=2463387 (it's in under the WWE section)

Htc One return back to original stock ROM to get OTA
nkk71 said:
No need to lock bootloader to get OTA, you just need:
1- stock rom
2- (preferably) matching firmware
3- stock recovery
so if your TWRP backup is same version as firmware, then just restore it, that will get you back to stock rom.
after that, you still need to flash stock recovery; for you (2.24.401.9) you can use the 2.24.401.8 from here: http://forum.xda-developers.com/showthread.php?t=2463387 (it's in under the WWE section)
Click to expand...
Click to collapse
Hi Dear! I really appreciate your quick response.

kash_9763 said:
Hi Dear! I really appreciate your quick response.
Click to expand...
Click to collapse
No problem, hit the thanks button if I've helped
Note: before flashing stock recovery copy everything to your PC, one time I did it and it fully wiped my /sdcard

Can't switch back to HTC One Stock ROM
I am Having troubles switching back to Stock HTC Sense ROM. I Rooted my Phone. S-Off Done, Bootloader Unlocked. And installed the Google Play Edition ROM RUU. Now I cant switch back to the HTC Sense India Stock ROM.
Phone Deatils,
M7_U PVT SHIP S-OFF RH
CID-11111111
HBOOT – 1.44.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
eMMC-boot
Apr 12 2013, 12:10:45:-1
Please help me in finding a solution and a proper RUU or Guru Reset or Stock ROM zip.
PS:- Also my bootloader is not detecting my device. It only detects the device when the phone is switched on.

nkk71 said:
Don't really understand why anybody would want to go backwards, except for warranty, but in any case, your choice so here goes: you need s-off
1- So download Guru Reset 2.24.401.8 (closest available to your version): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
Flash it, you do need to WIPE, deselect "stock recovery", select ROOT, radio doesnt matter
2- Download rumrunner package 2.24.401.9, and use it to get S-Off
once s-off
3- remove TAMPERED: http://forum.xda-developers.com/showthread.php?t=2477792
4- set your phone to LOCKED: http://forum.xda-developers.com/showthread.php?t=2475914
5- download and run the following RUU: http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
6- do not take any OTA YET
7- if you insist on S-On, then "fastboot oem writesecureflag 3", if you don't mind keeping S-Off keep it
8- take the OTAs
If I've helped hit the thanks button
Let me know if you need any more help
Click to expand...
Click to collapse
Hello, Thanks for your help. I have to clear a doubt before applying this.
Thanks for the guide.
I have 3.62.401.1 World Wide English (WWE) HTC ONE with the last JB 4.3 OTA update.
Unlocked, Custom recovery, Rooted and S-OFF, Hboot 1.55, Stock ROM (stocks apps deleted)
I have speaker issue so I need to send back my phone to customer service.
I find the right RUU.exe for my CID => RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
I think this is with hboot 1.44
1. I have to downgrade htboot 1.55 to 1.44 before running RUU.exe?
2. Stock recovery is it included in RUU ?
Thanks in advance

Ethan_93 said:
Hello, Thanks for your help. I have to clear a doubt before applying this.
Thanks for the guide.
I have 3.62.401.1 World Wide English (WWE) HTC ONE with the last JB 4.3 OTA update.
Unlocked, Custom recovery, Rooted and S-OFF, Hboot 1.55, Stock ROM (stocks apps deleted)
I have speaker issue so I need to send back my phone to customer service.
I find the right RUU.exe for my CID => RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
I think this is with hboot 1.44
1. I have to downgrade htboot 1.55 to 1.44 before running RUU.exe?
2. Stock recovery is it included in RUU ?
Thanks in advance
Click to expand...
Click to collapse
Hi there, that post you quoted me on is really old, since then things have progressed ; if you want to send to repair, check my guide (has all the info for you): http://forum.xda-developers.com/showthread.php?t=2541082
Check it out, and If you have questions let me know.

nkk71 said:
Hi there, that post you quoted me on is really old, since then things have progressed ; if you want to send to repair, check my guide (has all the info for you): http://forum.xda-developers.com/showthread.php?t=2541082
Check it out, and If you have questions let me know.
Click to expand...
Click to collapse
Thank you. It's more clear for me.
I'm going to apply the Post 2 method. Just a question, at what step we return back to STOCK RECOVERY please ? RUU.EXE will restore or I have to do it maually ?

Ethan_93 said:
Thank you. It's more clear for me.
I'm going to apply the Post 2 method. Just a question, at what step we return back to STOCK RECOVERY please ? RUU.EXE will restore or I have to do it maually ?
Click to expand...
Click to collapse
if you're using RUU.EXE method it will be restored automatically.
after "Step 2: Run your RUU.EXE", your phone will be 100% out-of-the box (also fully wiped!), if you decide to go S-On, do it after the RUU, and before OTA updates (hboot 1.55+ can be nasty!!)

[SOLVED - thx nkk71 !] Wiped everything & S-ON - Please help :(

Hi everybody,
I already checked a lot of threads in xda but it didn't solve my problem so I do it by myself...
Just got a HTC One and when I wanted to install the Google Edition ROM by bigxie with mini SDK, ADB and TWRP... I just messed up:
- OK to unlock bootloader
- S-OFF didn't work
- I accidentaly wiped everything: the OS...
I tried push a ROM with adb push rom.zip /sdcard/rom.zip but it didn't help:
- S-ON didn't allow me to install custom ROMs
- I couldn't turn my phone S-OFF because my PC didn't recognise it anymore + have no OS
- adb devices command didn't see my phone
Then I tried to relock it to install an official RUU from HTC but:
"(bootloader) signature checking...
FAILED (remote: signature verify fail)"
I guess it comes from my HBOOT-1.54, I red we have to be in 1.44 but one more time I can't downgrade my HBOOT because I'm not S-OFF.
Now my HTC One M7_UL is :
* TAMPERED *
* RELOCKED *
*** Security Warning ***
- S-ON
- HBOOT-1.54.0000
Checkmate ?
Thanks in advance...

can you unlock your phone using HTCdev? get a new token and try.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
samih7 said:
Hi everybody,
I already checked a lot of threads in xda but it didn't solve my problem so I do it by myself...
Just got a HTC One and when I wanted to install the Google Edition ROM by bigxie with mini SDK, ADB and TWRP... I just messed up:
- OK to unlock bootloader
- S-OFF didn't work
- I accidentaly wiped everything: the OS...
I tried push a ROM with adb push rom.zip /sdcard/rom.zip but it didn't help:
- S-ON didn't allow me to install custom ROMs
- I couldn't turn my phone S-OFF because my PC didn't recognise it anymore + have no OS
- adb devices command didn't see my phone
Then I tried to relock it to install an official RUU from HTC but:
"(bootloader) signature checking...
FAILED (remote: signature verify fail)"
I guess it comes from my HBOOT-1.54, I red we have to be in 1.44 but one more time I can't downgrade my HBOOT because I'm not S-OFF.
Now my HTC One M7_UL is :
* TAMPERED *
* RELOCKED *
*** Security Warning ***
- S-ON
- HBOOT-1.54.0000
Checkmate ?
Thanks in advance...
Click to expand...
Click to collapse
Do you still have a custom recovery installed?

nkk71 said:
can you unlock your phone using HTCdev? get a new token and try.
Click to expand...
Click to collapse
Thanks for your answer.
Yes, I can. Should I install TWRP or CWM afterwards ?

samih7 said:
Thanks for your answer.
Yes, I can. Should I install TWRP or CWM afterwards ?
Click to expand...
Click to collapse
doesnt matter, either will do. choose the one you prefer.
were you able to unlock bootloader?

nkk71 said:
doesnt matter, either will do. choose the one you prefer.
were you able to unlock bootloader?
Click to expand...
Click to collapse
Yes, it's now unlocked and I installed TWRP.

samih7 said:
Yes, it's now unlocked and I installed TWRP.
Click to expand...
Click to collapse
ok, can you post a "fastboot getvar all" (remove IMEI and s/n before posting)

nkk71 said:
ok, can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
Click to expand...
Click to collapse
Here it is :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxx
(bootloader) imei: xxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANGB10
(bootloader) battery-status: good
(bootloader) battery-voltage: 4286mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s

samih7 said:
Here it is :
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANGB10
finished. total time: 0.039s
Click to expand...
Click to collapse
another missing version-main , this is really getting weird.
are you still looking to go s-off? if so you're on hboot 1.54, which means a 2.24.xxx.? ROM, so download and try rumrunner with this
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
and/or
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
select WIPE, select ROOT, unselect "stock recovery"

nkk71 said:
another missing version-main , this is really getting weird.
are you still looking to go s-off? if so you're on hboot 1.54, which means a 2.24.xxx.? ROM, so download and try rumrunner with this
and/or
select WIPE, select ROOT, unselect "stock recovery"
Click to expand...
Click to collapse
If version main is the version of the OS, I don't have one. :-S
Yes I'm still looking for it and install the Google Edition ROM...
Ok I'll try it, it's downloading, I hope it'll recognise the phone.

samih7 said:
If version main is the version of the OS, I don't have one. :-S
Yes I'm still looking for it and install the Google Edition ROM...
Ok I'll try it, it's downloading, I hope it'll recognise the phone.
Click to expand...
Click to collapse
version-main is the firmware version of the phone, just seems it's disappearing a lot last couple of days.
hboot 1.54 has firmware 2.24.xxx.x, so one of the roms I linked will hopefully get you s-off using rumrunner

nkk71 said:
version-main is the firmware version of the phone, just seems it's disappearing a lot last couple of days.
hboot 1.54 has firmware 2.24.xxx.x, so one of the roms I linked will hopefully get you s-off using rumrunner
Click to expand...
Click to collapse
Ok.
So I need to push and flash the ROM on TRWP, boot on it and a screen will appear with "WIPE" then "ROOT" and unselect stock recovery ?
Thanks.
NB: When I try to do a Factory Reset in TRWP, it fails with an "Unable to mount cache" error message.
NB1: Can't flash the ROM you gave me. Since I did an "Format Data" wich removes datas & encryption on internal storage, I can't flash anything...
NB2: OK I can't mount /data, /sdcard either...

samih7 said:
Ok.
So I need to push and flash the ROM on TRWP, boot on it and a screen will appear with "WIPE" then "ROOT" and unselect stock recovery ?
Thanks.
NB: When I try to do a Factory Reset in TRWP, it fails with an "Unable to mount cache" error message.
NB1: Can't flash the ROM you gave me. Since I did an "Format Data" wich removes datas & encryption on internal storage, I can't flash anything...
Click to expand...
Click to collapse
say what?
unable to mount cache is OK, probably because of the fastboot erase cache
if push dosn't work , sideload it: http://forum.xda-developers.com/showthread.php?t=2317986

nkk71 said:
say what?
unable to mount cache is OK, probably because of the fastboot erase cache
if push dosn't work , sideload it: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
It's ok, I found an issue by formatting /data in CWM (I deleted TWRP)
The .8 ROM is installed but the fingertouch screen wasn't usable during the installation, I don't know if it means that's not a good version ?
--
Damn man you made my day, the ROM is installed and I can use my HTC again !
Is it the official RUU ?
But unfortunately it's still S-ON.
Thanks a lot

samih7 said:
It's ok, I found an issue by formatting /data in CMW (I deleted TRPW)
The .8 ROM is installed but the fingertouch screen wasn't usable during the installation, I don't know if it means that's not a good version ?
--
Damn man you made my day, the ROM is installed and I can use my HTC again !
Is it the official RUU ?
Click to expand...
Click to collapse
touchscreen wasnt working because you probably used 6.0.3.1, get the latest from here: http://forum.xda-developers.com/showthread.php?t=2173863 (though that one takes VERY long to backup/restore nandroids), so either get 6.0.3.2 or TWRP if you do nandroids frequently.
It's getting late for me, so have to sign off in a bit, and now that your phone is up and running, we can pick this up tomorrow....
you can try rumrunner now to get yourself s-off.
I'll check back tomorrow....
You can still hit the thanks button on my posts if i helped

nkk71 said:
touchscreen wasnt working because you probably used 6.0.3.1, get the latest from here: http://forum.xda-developers.com/showthread.php?t=2173863 (though that one takes VERY long to backup/restore nandroids), so either get 6.0.3.2 or TWRP if you do nandroids frequently.
It's getting late for me, so have to sign off in a bit, and now that your phone is up and running, we can pick this up tomorrow....
you can try rumrunner now to get yourself s-off.
I'll check back tomorrow....
You can still hit the thanks button on my posts if i helped
Click to expand...
Click to collapse
No problem, take your time. Thank you for helping me !!
I hit the "thanks" but it doesn't appear anything, is it normal ?
--
I red I didn't need to get myself S-OFF to install a Custom Rom, is it true ?
I'm trying to get the Google Edition ROM again... Without success.
I flash boot.img in fastboot (& make clear cache) + flash the ROM normally (wipe cache + dalvik cache) via TWRP but my device enter in a boot loop when I reboot after installation (I just see the Google language selection, just to make me more frustrated lol...). Same with CyanogenMod.
Root Checker says "Congratulations ! This device has root access" and I unlocked the bootloader so I don't understand...
Maybe because of the CID of my phone is from Orange Poland (ORANGB10) ? I maybe should get S-OFF & Debrand ?
Thanks for your answer.

Definitely do s-off if you can. It may save you if things go south..
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
However you need unlocked bootloader + custom recovery to install custom ROMs. Not S-off.

SaHiLzZ said:
Definitely do s-off if you can. It may save you if things go south..
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
However you need unlocked bootloader + custom recovery to install custom ROMs. Not S-off.
Click to expand...
Click to collapse
I finally got S-OFF and achieved to install the stock Google Edition 4.4 ROM with this thread : http://forum.xda-developers.com/showthread.php?t=2358781
I had to SuperCID (fastboot eom writecid 11111111) because changing the android-info.txt didn't work.
Could you tell me in which case is it useful to flash stock recovery (he says it's for future OTA's) ?
Does it mean I could do updates via Software Update in Android the menu ?
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Thank you.

samih7 said:
I finally got S-OFF and achieved to install the stock Google Edition 4.4 ROM with this thread : http://forum.xda-developers.com/showthread.php?t=2358781
I had to SuperCID (fastboot eom writecid 11111111) because changing the android-info.txt didn't work.
Could you tell me in which case is it useful to flash stock recovery (he says it's for future OTA's) ?
Does it mean I could do updates via Software Update in Android the menu ?
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Thank you.
Click to expand...
Click to collapse
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Click to expand...
Click to collapse
I wouldn't , but that's your choice :laugh:
Anyway, I didn't read the thread you linked, but to get OTAs, you need "odexed stock rom", and "stock recovery" for OTAs to work properly,
you also need to change your CID (and possibly MID) to GPe
I think GPE CID is "GOOGL001" and MID is "PN0712000" (I THINK)
So if you're stock rom + stock recovery + correct CID & MID, you'll receive future OTAs just fine,
remember to keep S-Off.
if all good, would you mind editing the main thread title to include [SOLVED]. thanks

nkk71 said:
I wouldn't , but that's your choice :laugh:
Anyway, I didn't read the thread you linked, but to get OTAs, you need "odexed stock rom", and "stock recovery" for OTAs to work properly,
you also need to change your CID (and possibly MID) to GPe
I think GPE CID is "GOOGL001" and MID is "PN0712000" (I THINK)
So if you're stock rom + stock recovery + correct CID & MID, you'll receive future OTAs just fine,
remember to keep S-Off.
if all good, would you mind editing the main thread title to include [SOLVED]. thanks
Click to expand...
Click to collapse
Why wouldn't you ? :laugh: I like Google's refinement, don't you ?
How could I verify I'm in stock recovery ?
I flashed it, and now when I click on RECOVERY in BOOT LOADER, it doesn't enter in recovery anymore: get that little Android green toy down with a red triangle.
Ok fine.

samih7 said:
Why wouldn't you ? :laugh: I like Google's refinement, don't you ?
How could I verify I'm in stock recovery ?
I flashed it, and now when I click on RECOVERY in BOOT LOADER, it doesn't enter in recovery anymore: get that little Android green toy down with a red triangle.
Ok fine.
Click to expand...
Click to collapse
"get that little Android green toy down with a red triangle" -> yep, that's stock recovery :good::good:
if you simultaneously and briefly press POWER + VOLUP + VOLDOWN, you'll get to the stock recovery menu (really tiny font). you'll have to try a couple of times to get the timing correctly.

[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!

RUU Stucking at 5% 'Checking Headers'

Hello guys! Ive been reading you all for a couple days now because i bought myself an used HTC One M7 from AT&T. Now, as soon as i got it i saw it was running android 4.1.2 and i can't live with that. I found a way to update it thru RUU up to 4.3 (before, i S-OFF and SuperCIDed) and now i'm trying to run a 4.4 RUU but it doesnt seem to work. It keeps on getting stuck at 5% even when ive followed some people comments as installing all versions of windows Visual C++, disabling usb debugging, also ive relocked bootloader because of it but nothing seems to work.
HBOOT: 1.55
Downloaded this RUU: http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Currently running: http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Heres my getvar:
Version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.19.3263.13
version-cpld: None
version-microp: None
version-main: 3.17.502.3
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: 11111111
battery-status: good
battery-voltage: 4168mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-2da61e5e88
hbootpreupdate: 11
gencheckpt: 0
Do any of you guys know how to proceed?
My goal is to get Lollipop STOCK.
Thank you!

If i remember correct u cant install a ruu while you are s-off, but the easiest way to update your device would be just flash twrp and than install a newer backup from here (in the forum you can find every Stock System as a twrp backup).

saturday_night said:
If i remember correct u cant install a ruu while you are s-off, but the easiest way to update your device would be just flash twrp and than install a newer backup from here (in the forum you can find every Stock System as a twrp backup).
Click to expand...
Click to collapse
Thank you very much for your quick answer. I have applied the 4.3 RUU while being S-OFF, but i think ive read the same as you... Now, is that possible? I mean, just restoring a nandroid backup to update to 4.4 then to lolli? I mean i am not that noob regarding messing with phones but HTC ones are too darn complicated haha @saturday_night

Luis_D1 said:
Thank you very much for your quick answer. I have applied the 4.3 RUU while being S-OFF, but i think ive read the same as you... Now, is that possible? I mean, just restoring a nandroid backup to update to 4.4 then to lolli? I mean i am not that noob regarding messing with phones but HTC ones are too darn complicated haha @saturday_night
Click to expand...
Click to collapse
Sure it is possible, i always did the same until HTC stoped updating this device. It is the esiest way to install Stock updates while you have done changes to the system and OTA Updates dont work. You can if, you want to, also install a MM or a N Rom (N Roms are still in development and not bug free) i´m using XenonHD (7.1) at the moment and looks really stable, just flashing the latest update from today now haha.

OMG thats so awesome! It looks like a silly thing but theres too much information around this forums and everything is so messy, even more for a someone whos not an english native speaker haha since im new to this device (i had one in 2014 for like a month but forgot everything i did to it) i just want to get it to the top it can be to try out sense 6 and all its features then ill be messing with it much more. Now that you're here and you're too kind would you recommend a lollipop rom that you liked the best? ill be trying MM but in a week or two when i get bored of these! @saturday_night

Luis_D1 said:
OMG thats so awesome! It looks like a silly thing but theres too much information around this forums and everything is so messy, even more for a someone whos not an english native speaker haha since im new to this device (i had one in 2014 for like a month but forgot everything i did to it) i just want to get it to the top it can be to try out sense 6 and all its features then ill be messing with it much more. Now that you're here and you're too kind would you recommend a lollipop rom that you liked the best? ill be trying MM but in a week or two when i get bored of these! @saturday_night
Click to expand...
Click to collapse
I just read that you dont need to be S-On to flash a ruu, just the bootloader must be relocked. You can easily download the first file in this thread and follow the instructions there in the first post and you should be done. http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944

saturday_night said:
I just read that you dont need to be S-On to flash a ruu, just the bootloader must be relocked. You can easily download the first file in this thread and follow the instructions there in the first post and you should be done. http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
You can flash RUUs with s-off without any problems, and you don't have to relock your bootloader. That is obligatory only for s-on devices. Why don't you download RUU.zip instead of RUU.exe, and flash it via fastboot?
Edit: Sorry, wrong post quoted, but everything applies to OP

saturday_night said:
I just read that you dont need to be S-On to flash a ruu, just the bootloader must be relocked. You can easily download the first file in this thread and follow the instructions there in the first post and you should be done. http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Click to expand...
Click to collapse
I believe I am not? That's lolli update and as far as I know I should be going by steps because of the hboot. I'm now on 3.x firmware, I shall go to 4 then 5 and then I can go all up to 7 isn't it? That's why i was so surprised regarding the nandroid information you gave me.
donkeykong1 said:
You can flash RUUs with s-off without any problems, and you don't have to relock your bootloader. That is obligatory only for s-on devices. Why don't you download RUU.zip instead of RUU.exe, and flash it via fastboot?
Edit: Sorry, wrong post quoted, but everything applies to OP
Click to expand...
Click to collapse
Well as said in other posts information is too messy with discontinued guides and stuff and I just find hard to do anything without compromising my phone just because of messy information but sure I will if I can't find any other solution to this matter I just hate downloading big files since my net speed goes up to 200kb/s lol

Luis_D1 said:
I believe I am not? That's lolli update and as far as I know I should be going by steps because of the hboot. I'm now on 3.x firmware, I shall go to 4 then 5 and then I can go all up to 7 isn't it? That's why i was so surprised regarding the nandroid information you gave me.
Well as said in other posts information is too messy with discontinued guides and stuff and I just find hard to do anything without compromising my phone just because of messy information but sure I will if I can't find any other solution to this matter I just hate downloading big files since my net speed goes up to 200kb/s lol
Click to expand...
Click to collapse
To flash RUU or Firmware on a S-ON phone:
Bootloader must be locked or re-locked
RUU or Firmware must be signed (Official ruu or firmware)
To flash RUU or Firmware on a S-OFF phone:
Bootloader locked/unlocked doesn't matter
RUU or Firmware can be signed or not (custom firmware/ruu or official firmware/ruu)
the "incremental way"to update apply only if you're flashing firmware.zip extracted from an ota update
If flashing a RUU you don't need to flash them all incrementally, just the latest one
BUT
to install a lollipop RUU, your phone must be running at least hboot 1.57 (firmware 6.xx.xxx.x) (there was no requirements of this kind before lollipop)
Since your phone is S-OFF, you could simply update your firmware to at least 6.xx.xxx.x and then flash the latest RUU (7.xx.xxx.xx)
And time to convert to another version if you don't care about the at&t bloatware (i.e developer edition which is basically the exact same rom as at&t minus the at&t' bloat)
Make sure to flash a complete firmware.zip (not one from an ota update) if you're going to do this.
btw +1 for using fastboot instead of ruu.exe. At least when someting goes wrong during the process, you can have some detailed info about the problem unlike when using an ruu.exe where you'll only get a generic error code.

alray said:
To flash RUU or Firmware on a S-ON phone:
Bootloader must be locked or re-locked
RUU or Firmware must be signed (Official ruu or firmware)
To flash RUU or Firmware on a S-OFF phone:
Bootloader locked/unlocked doesn't matter
RUU or Firmware can be signed or not (custom firmware/ruu or official firmware/ruu)
the "incremental way"to update apply only if you're flashing firmware.zip extracted from an ota update
If flashing a RUU you don't need to flash them all incrementally, just the latest one
BUT
to install a lollipop RUU, your phone must be running at least hboot 1.57 (firmware 6.xx.xxx.x) (there was no requirements of this kind before lollipop)
Since your phone is S-OFF, you could simply update your firmware to at least 6.xx.xxx.x and then flash the latest RUU (7.xx.xxx.xx)
And time to convert to another version if you don't care about the at&t bloatware (i.e developer edition which is basically the exact same rom as at&t minus the at&t' bloat)
Make sure to flash a complete firmware.zip (not one from an ota update) if you're going to do this.
btw +1 for using fastboot instead of ruu.exe. At least when someting goes wrong during the process, you can have some detailed info about the problem unlike when using an ruu.exe where you'll only get a generic error code.
Click to expand...
Click to collapse
Thank you very much for your quick answer! I understand that now very well, thanks! Now just another question before i proceed.... I know i have to upgrade my firmware up to 6.x in order to flash the RUU but my doubt comes to finding the 'complete firmware.zip ( not one from an ota update)' Ive found something done by mike1986 but there are no firmwares for 502 (AT&T/Cingular) devices. Else than that i just found pieces of firmware that just weight 20-30mb and i don't think thats what you mean... Also have found just lollipop ones like the one on your signature. I don't like to be begging for links but i can't seem to find it even on htc1guru.. Thank you very much and have a great day! @alray

Luis_D1 said:
Thank you very much for your quick answer! I understand that now very well, thanks! Now just another question before i proceed.... I know i have to upgrade my firmware up to 6.x in order to flash the RUU but my doubt comes to finding the 'complete firmware.zip ( not one from an ota update)' Ive found something done by mike1986 but there are no firmwares for 502 (AT&T/Cingular) devices. Else than that i just found pieces of firmware that just weight 20-30mb and i don't think thats what you mean... Also have found just lollipop ones like the one on your signature. I don't like to be begging for links but i can't seem to find it even on htc1guru.. Thank you very much and have a great day! @alray
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95897840722641956
You can use this one, its not .502, its .1540. It does not really matters since after that you'll be flashing the RUU and the firmware will be updated again to match the RUU.
If you don't want at&t bloatware you should flash the 7.17.1540.51 ruu, you can find it on htc's wesbite (google search for "HTC rom download", the first link should be the right one). Otherwise if you really want the at&t version, flash the last one from at&t.
Code:
fastboot oem rebootRUU
fastboot flash zip Firmware_6.07.1540.2.zip
fastboot flash zip Firmware_6.07.1540.2.zip
fastboot reboot-bootloader
(flash command must be done twice)
then launch your ruu.exe or if you'll be using a ruu.zip:
Code:
fastboot oemrebootRUU
htc_fastboot flash zip <filename>.zip
fastboot reboot
(flash command to be done only once and using htc_fastboot.exe not the normal fastboot.exe)