Database Develop

[SOLVED][Q] Fully backing up before tampering (CID HTC__332) [Conversion to WWE]

Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it

mbinic said:
Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it
Click to expand...
Click to collapse
I just went through this a couple days ago with someone
go here and read pages 2-5 and see if you understand or still have questions read it all before moving on
http://forum.xda-developers.com/showthread.php?t=2593387&page=2

Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone

mbinic said:
Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone
Click to expand...
Click to collapse
yes after the conversion to .401 you will have a EU device and can update and flash all the new roms as they come out.
make note of the 2 links posted about changing your MID / CID their important steps in the whole process
http://forum.xda-developers.com/showthread.php?t=2535365
this guide by @nkk71 is a good source of information your just doing a few things differently
http://forum.xda-developers.com/showthread.php?t=2541082

OK, so part one is going mostly smoothly for now - unlocked bootloader, flashed TWRP, backed up (uploading for sharing) + saved partitions for rumrunner if I end up needing them (also uploading), had a few bootloops but managed to get ARHD 31.6 running. Now onto rumrunner...

I got S-OFF with rumrunner in the first try! Now to re-read and change CID and MID (4:40 AM, fingers crossed, heart pounding)

I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Click to expand...
Click to collapse
and then run 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'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?

mbinic said:
I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
and then run 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'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?
Click to expand...
Click to collapse
Almost
1- change you MID to PN071000 using the tool
2- with SuperCID you cannot receive OTAs, so you need to change CID to European unbranded, there are several (this will affect the country/language options): http://forum.xda-developers.com/showpost.php?p=48195855&postcount=98 (instructions are also in that post)
so for example, if you wanted Eastern European languages you would need to set CID to HTC__032
3- since you're on hboot 1.55, you need to downgrade that separately to 1.44
4- you can leave the phone UNLOCKED, and even TAMPERED, but if you prefer to set them LOCKED and remove TAMPERED you can follow my guide.
5- run the RUU you mentioned
6- KEEP S-OFF!!
OTAs will not be affected by unlocked bootloader, or S-Off
let me know if you need more details

Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!

mbinic said:
Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!
Click to expand...
Click to collapse
yep, that works!
don't want to confuse you , but 1 2 and 3 can be run in any order, most important is to do run the ruu as last step, once the ruu has completed you should immediately receive OTAs.
remember, stay S-Off, consider it your "get out of jail" card, in case you ever want to change something again.

Thanks again I'll try it in a couple of hours and report my progress.
Edit:
OK, got CID HTC__032 and changed MID successfully. AROMA hung at 0.00%, but a restart helped like it was described in the post. Now onto HBOOT and RUU.
Edit 2:
Installed HBOOT 1.44 and the Guru Bootloader reset - removed tampered and set locked (why not ). Running RUU in a few minutes...

So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there

mbinic said:
So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there
Click to expand...
Click to collapse
Congrats mate
Can you also edit main thread title to include [SOLVED], thanks

Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end

mbinic said:
Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end
Click to expand...
Click to collapse
4.4 (hopefully 4.4.2) not out yet for most, only US Dev Edition, and has a few "bad habits" for the rest of the world... no need to change CIDs, it'll come soon enough....
ARHD 41.0 and MaximusHD are based on the US Dev Edition, not the WWE edition.

I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!

my htc
mbinic said:
I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!
Click to expand...
Click to collapse
hi friends first my english is not so good so excuse me i a have some mistakes, then i want to say i was reading your experience, i got the same version of htc one HTC_332 this is the cid for latin america this is what htc supports tell me by email, ok i got a little questions maybe u can help me
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
for last i want to thanks for the time you take to anwer me

Hello edulaffont,
edulaffont said:
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
Click to expand...
Click to collapse
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here

first
mbinic said:
Hello edulaffont,
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here
Click to expand...
Click to collapse
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english

edulaffont said:
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english
Click to expand...
Click to collapse
I also got that update as soon as I bought the phone, some time in October/November I think, it's old.
I didn't change the firmware when I was converting to WWE, a .401 version wasn't out yet.
I did change it last night though, and installed ARHD 51 (it gives me more options than stock) and everything went smoothly (I even did a dirty flash).
Anyway, I recommend you stick to the original instructions (use old ARHD for rumrunner), and when you're done converting to WWE, ran the RUU and everything works you can choose wheter you want to get the OTAs and stay stock (KitKat 4.4.2 OTA for WWE just came out, with new firmware), or root and install any ROM you wish

[Q] Error after Lollipop update

Hoping someone here might be able to help as nothing on the HTC website did.
My phone updated yesterday to Lollipop 5.0 (through EE in the UK)...well it it had a go, but failed. I'm left with just an exclamation mark of helpfulness. I've tried all of the basic recovery options but it just restarts a few times and goes back to said exclamation mark.
The error is..
DEVICE_CW_Install: Can't mount /cwprop
Then stuff about failing to mount the SD card (that it doesn't have).
Are there any tools that might help me sort this out? I don't particularly want to install something none standard on it but if that's all I can do to get it working, it would be ok.

Jxt. said:
is your bootloader is unlocked and are you on complete stock.
Click to expand...
Click to collapse
It's totally stock.

alfev said:
It's totally stock.
Click to expand...
Click to collapse
post your fastboot getvar all please without imei and serial number.
however if it is totally stock and the bootloader is locked, then id suggest you send it back under warranty.

Thanks for replying and trying to help. It's out of warranty this is just a last ditch attempt before getting a new one really. I have zero knowledge in this area but have installed the sdk and run that command...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: sssh
(bootloader) imei: ssshh
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3778mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.088s

Seanie280672 said:
post your fastboot getvar all please without imei and serial number.
however if it is totally stock and the bootloader is locked, then id suggest you send it back under warranty.
Click to expand...
Click to collapse
Is it possible to unlock it, is there anything I can do with it, or is it a paper weight now?

alfev said:
Is it possible to unlock it, is there anything I can do with it, or is it a paper weight now?
Click to expand...
Click to collapse
If it's still under warranty, better send it back to service center since it is an OTA failure, not your fault.

eyeyousee said:
If it's still under warranty, better send it back to service center since it is an OTA failure, not your fault.
Click to expand...
Click to collapse
I would do but as I say, it's out of warranty so just making the best of it.
I'm downloading this at the moment RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
No idea if that's a good idea but I can't be any worse off than I am at the moment.

alfev said:
I would do but as I say, it's out of warranty so just making the best of it.
I'm downloading this at the moment RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
No idea if that's a good idea but I can't be any worse off than I am at the moment.
Click to expand...
Click to collapse
If that RUU fails, the best thing to do is to unlock your bootloader, you can find the unlocking instructions here search for it. Then install custom recovery, and then install custom rom.
Just post the results of your RUU setup.

eyeyousee said:
If that RUU fails, the best thing to do is to unlock your bootloader, you can find the unlocking instructions here search for it. Then install custom recovery, and then install custom rom.
Just post the results of your RUU setup.
Click to expand...
Click to collapse
The RUU update got to 1/5 checking header then crashed with "htc_fastboot.exe has stopped working." Then Error 171: USB connection error. Not sure if their is a problem with a driver or something.

alfev said:
The RUU update got to 1/5 checking header then crashed with "htc_fastboot.exe has stopped working." Then Error 171: USB connection error. Not sure if their is a problem with a driver or something.
Click to expand...
Click to collapse
171 is a USB error, means therres a problem with your drivers, sorry been a bit busy today, car problems, but that RUU is wrong for your phone anyway, that's a 401 RUU (4.19.401.2), you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher

Seanie280672 said:
171 is a USB error, means therres a problem with your drivers, sorry been a bit busy today, car problems, but that RUU is wrong for your phone anyway, that's a 401 RUU (4.19.401.2), you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher
Click to expand...
Click to collapse
I've sorted of veered off the RUU route and unlocked the phone. I've installed twrp... I'm winging it completely. Trying to get a ROM on it now... or something.

alfev said:
I've sorted of veered off the RUU route and unlocked the phone. I've installed twrp... I'm winging it completely. Trying to get a ROM on it now... or something.
Click to expand...
Click to collapse
you will have problems with Lollipop based roms, so use this one which matches your firmware: https://www.androidfilehost.com/?fid=95897840722644627
your best bet if you want it full stock is to get s-off using sunshine once you get a rom on it and convert it to a 401 WWE phone, which gets one of the fastest updates, sunshine however will cost you $25 via paypal.

I'm not familiar with M7 software numbers but, yes maximusHD custom roms are good to begin with.

Seanie280672 said:
you will have problems with Lollipop based roms, so use this one which matches your firmware: https://www.androidfilehost.com/?fid=95897840722644627
your best bet if you want it full stock is to get s-off using sunshine once you get a rom on it and convert it to a 401 WWE phone, which gets one of the fastest updates, sunshine however will cost you $25 via paypal.
Click to expand...
Click to collapse
Thanks,I will probably have a go at putting different rom's on at some point and was wondering what people thought the best option is for the M7.
I managed to get sorted using Guru_Reset_M7_2.24.401.8.zip. I had some problems uploading it to begin with, I think the usb issue stopped the ruu and abd working but not fastboot. I have a working phone now, which seems like a bonus after thinking the phone was maybe a goner. It's been a massive learning curve having known absolutely nothing about any of this stuff on Monday, I know how to put different rom's on now which is handy to know. The phone is still unlocked at the moment, I don't know what the cons of that are. Would this rom maybe update if I locked it again?

alfev said:
Thanks,I will probably have a go at putting different rom's on at some point and was wondering what people thought the best option is for the M7.
I managed to get sorted using Guru_Reset_M7_2.24.401.8.zip. I had some problems uploading it to begin with, I think the usb issue stopped the ruu and abd working but not fastboot. I have a working phone now, which seems like a bonus after thinking the phone was maybe a goner. It's been a massive learning curve having known absolutely nothing about any of this stuff on Monday, I know how to put different rom's on now which is handy to know. The phone is still unlocked at the moment, I don't know what the cons of that are. Would this rom maybe update if I locked it again?
Click to expand...
Click to collapse
no, don't try and update either, you'll stand a high chance of seriously bricking your phone, it will try and install 401 firmware which isn't for your phone, hence 2.24.401.8 like I said before, your firmware is 61. orange / EE.
the numbers work like this, 2.24.401.8 ( the 2 is android version) the 24 is part of the build number, the 401 is carrier / region (401 is WWE world wide English) yours is 61 orange / EE and you can only use these files same or above the one your currently on as your phone is s-on, and the last number 8 is build number, or alternatively you can flash any custom rom you like upto KitKat as your firmware on your phone is currently 6.xx.61.x
you are stuck with custom rom's only up to KitKat, the one I linked earlier is Maximus HD 50.0 which is as close to stock Kitkat as you will get for now, but still a custom rom. Lollipop rom's will play up as your on firmware 6xxxxxxx unless you s-off and convert your phone or unless you can get hold of the 7.xx.61.x firmware and manually upgrade your firmware, you need to have, or find someone who has the 7.xx.61.x OTA and grab the firmware.zip out of it and flash that in fastbootRUU mode.

I think I've been pretty lucky to get the thing up and running really could've gone badly but I didn't think I had anything to lose. With all of the different firmware and rom version that I wasn't aware of it sounds like there was actually a lot I could've lost with my wing it aproach.
This oldish Android version I'm on now seems to use a lot of battery, presumably connected to the additional "HTC Pocket Radiator" feature which it also turns on sporadically. It's not a big problem but I think I'll have a bash with the MaximusHD you suggested. Question though, Googling for a bit more info on MaximusHD 5.0 it appears to be Lollipop, am I right? If so, just to confirm, you're saying that I could have problems with Lollipop because of my firmware but this version of it should work ok with my current firmware? From googling I found a description of the rom that said "Firmware 7.15.401.1 is recommended to install". Sorry, just making sure because my luck is likely to run out soon.
EDIT
Also, if I do need to S-OFF, you mention Sunshine and you mention $25, this is a 3 year old phone with a slight crack in the screen so I'm not going to throw any money at it but I found Squabbi's tool kit which uses Revone for S-OFF, would this be no good?

Seanie280672 said:
(..)you need a 61 RUU if one exists, you will need an RUU labelled as 6.16.61.8 or higher
Click to expand...
Click to collapse
There is a 6.16.61.8 signed RUU available but unfortunately, its only available at ir-file.com and you need a paid account to download from that website.
http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/
Seanie280672 said:
no, don't try and update either, you'll stand a high chance of seriously bricking your phone, it will try and install 401 firmware which isn't for your phone, hence 2.24.401.8 like I said before, your firmware is 61. orange / EE.
Click to expand...
Click to collapse
Right the update will not work but there is no chance of bricking here, the ota install process will only stop before flashing anything since the Orange CID and .61 Firmware of the phone doesn't match the WWE CID and .401 base of the OTA
alfev said:
EDIT
Also, if I do need to S-OFF, you mention Sunshine and you mention $25, this is a 3 year old phone with a slight crack in the screen so I'm not going to throw any money at it but I found Squabbi's tool kit which uses Revone for S-OFF, would this be no good?
Click to expand...
Click to collapse
No, Revone is only for hboot 1.44 pre-June 2013 version. For hboot 1.57 and above, Sunshine is the only way.

alray said:
There is a 6.16.61.8 signed RUU available but unfortunately, its only available at ir-file.com and you need a paid account to download from that website.
http://www.ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/M7_UL/
Right the update will not work but there is no chance of bricking here, the ota install process will only stop before flashing anything since the Orange CID and .61 Firmware of the phone doesn't match the WWE CID and .401 base of the OTA
No, Revone is only for hboot 1.44 pre-June 2013 version. For hboot 1.57 and above, Sunshine is the only way.
Click to expand...
Click to collapse
Ok, MaximusHD was mentioned. 50.0 looks to be the latest version and that's the version posted above but that's Lollipop, would 40.0 be the right one for me?
I might be best just leaving it as is. I've successfully upgraded it from a paperweight to a phone, if I twist I might bust and end up back with a shiny paperweight again.

alfev said:
Ok, MaximusHD was mentioned. 50.0 looks to be the latest version and that's the version posted above but that's Lollipop, would 40.0 be the right one for me?
I might be best just leaving it as is. I've successfully upgraded it from a paperweight to a phone, if I twist I might bust and end up back with a shiny paperweight again.
Click to expand...
Click to collapse
sorry my bad, I thought 50 was a KitKat rom as its sense 6, use this one instead which is a KitKat 6xxxx as close to stock rom as possible: https://www.androidfilehost.com/?w=files&flid=22071 (Maximus HD 46.0)
custom rom based on 6.09.401.11

Seanie280672 said:
sorry my bad, I thought 50 was a Ki
Code:
tKat rom as its sense 6, use this one instead which is a KitKat 6xxxx as close to stock rom as possible: [url]https://www.androidfilehost.com/?w=files&flid=22071[/url] (Maximus HD 46.0)
custom rom based on 6.09.401.11
Click to expand...
Click to collapse
Excellent, thanks, I think I'll have a pop at that then.

Please help me revive this sick m7

Hi Guys,
Bought an m7 cheap on ebay. I don't know anything about the history, except to say it's been fiddled with...
It powers up but it won't boot up; it hangs on the HTC logo.
Bootloader's unlocked, it's been rooted... S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ** edited out **
(bootloader) imei: ** edited out **
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm thinking I should try and take it back to stock, but I don't know where I should go from here and I'm worried I might screw it up.
Any help would be greatly appreciated
Thanks in advance!

Go to RUU mode and flash an RUU. There's a lot of threads explaining how to go to back to stock on this forum. If it still doesn't work, it might be an internal issue like the motherboard.

Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Thanks

Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up

mdb said:
Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Click to expand...
Click to collapse
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
mdb said:
Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up
Click to expand...
Click to collapse
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.

alray said:
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.
Click to expand...
Click to collapse
Thanks so much for this... I've been learning more all day (traditionally an iOS guy)...
Am I right in thinking I would need to sideload a custom rom through twrp and then install it? If so, I'm having an issue getting my laptop to talk to the phone - "adb devices" is pretty flakey to say the least, sometimes it works sometimes it doesn't... I've read various things about Windows 8 and that adb works best on Windows 7, can you please confirm I'm on the right track here. I'd like to put the Viper rom on it.
Thanks again

In order to flash custom recovery you need to be booted to bootloader menu, and use fastboot commands. If you flash TWRP 2.8.6.0 or later, there's no need to sideload a ROM because newer TWRP recoveries have MTP option, so you use that. Try to go to bootloader, connect your phone to your laptop or PC, and issue a command fastboot devices. If it shows your phone, you're good to go

Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance

mdb said:
Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance
Click to expand...
Click to collapse
flash the 7.19.401.2 firmware and then the 7.19.401.2 RUU. If you still have imei problem after that, its most likely an hardware defect.
relock your bootloader if not already locked or re-locked:
Code:
fastboot oem lock
Code:
fastboot orm rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastbppt flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
fastboot reboot
*** use htc_fastboot.exe for flashing the ruu (linked below). Save all files in the same folder where you already have fastboot.exe and adb.exe on your computer.
M7_UL_Firmware_7.19.401.2.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
htc_fastboot.exe

Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!

mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
To flash a ruu on a s-on phone there are many prerequisites:
The RUU must match your MID: 7.19.401.2 is for PN0710000
The RUU must match your CID: You have superCID so its not a problem.
The RUU must be the same version or an upgrade from your actual version, we don't know your actual version because of your blank versio-main but you have 1.57 hboot which suggest a 6.xx.xxx.x version. So 7.19.401.2 should be an upgrade.
The bootloader must be locked or re-locked.
There is no risk trying it, the worst that can happen is that the phone won't accept the ruu and nothing will be flashed.

mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
Super CID + your MID. WWE firmware should work just fine. Right @alray?

donkeykong1 said:
Super CID + your MID. WWE firmware should work just fine. Right @alray?
Click to expand...
Click to collapse
:good:

Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.

mdb said:
Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.
Click to expand...
Click to collapse
Try to bend your sim tray just a little bit. Maybe your sim card is not reaching the contacts inside the phone. Or put a piece of paper under the sim and see what happens

Thanks donkeykong1, I've tried but it's not working... The fact the IMEI / IMEI SV and baseband are unknown though... they're not sim related...
It does show the baseband and IMEI in fastboot getvar all though?...

There were a lot of people with that same issue, and their phones worked fine, so I doubt it has anything to do with your sim. Your sim works in another phone?

Yeah, the sim's fine. @alray said it's likely a hardware issue if the firmware / rom didn't repair the IMEI issue, and the other threads I've looked at with the same issue are all saying the motherboard's faulty.

Although I am baffled as to why it is showing the IMEI / baseband in the bootloader, in fastboot etc. but not once the phone has booted up?...
I read on another thread (http://forum.xda-developers.com/showthread.php?t=2253514) that maybe flashing a kernal and/or radio might solve it?
Just wondering whether I should try flashing an official HTC rom? I've been in touch with the guy I got it off and he said it was originally on Orange, UK:
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 6
One M7 / Orange / UK / CRC / 3.4.10 / v5.0.2 / 539.0 MB / 7.19.61.10
Was also thinking of...
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 1
One M7 / HTC / EU / MR 3 / 3.4.10 / v5.0.2 / 486.0 MB / 7.19.401.22
If I did that would I need to update the firmware first like you advised originally @alray?
If I know I can revive the IMEI etc. I'll be happy to go ahead and pay to S-OFF
Thanks in advance

You need a kernel to match your firmware. If you're on 7.19.401.2, then you need 7.19.401.2 kernel. I can give you boot.img, but I don't have the whole zip, with modules. Then again, if your phone boots fine, maybe boot.img will help. I'd [email protected] to confirm my thoughts though. He's much more into this than I am

Upgrading to stock from custom 4.4.3 ROM via RUU

Hello,
I have a number of questions before I jump in and update my phone, so I'm hoping to get some advice on the best way to upgrade from a 4.4.3 custom rom (ARHD 83.1) to the latest stock (rooted) rom - it looks like the custom 6.0 roms aren't so stable at the moment, so best to avoid them for now?
I'm also looking to update my radio with the hope of getting a better signal, or is the radio not really affected by the rom version? Hoping to get better battery life and general stability too.
I understand that I can't just install a custom 5.0.2 rom (e.g. ARHD 93.0) or custom 6.0 rom via recovery (as I normally would do) because of firmware/radio miss-matches? I need to update this first (must be S_OFF) before I can flash.
Some details:
M7_UL
HTC_039
Unlocked
S-ON
HBOOT-1.44.0000
Current: 6.09.401.11 / 4A.14.3250.13
Carrier: Telstra (AU)
From what I can tell, my two main options are either using ruu.zip/ruu.exe or Guru Reset.
I'm S-ON, so I can use Guru Reset, but I can't seem to find the latest firmware with this.
I understand I can flash ruu.zip/ruu.exe with S-ON if the firmware is newer?
Am I better off going S-OFF now (it's easier while on 1.44?)? Do I need to be S-OFF?
How do I know which firmware version to choose? Can I jump straight to 7.19.401.2?
Will OTA work after this?
Does it matter if I use x.xx.401.x (WWE?) or x.xx.908.x (Optus?) or x.xx.841.x (Telstra??) ... I don't want any carrier software, but I would like the best radio for my carrier (Telechoice/Telstra).
I understand that HTC_039 is Optus, but my current firmware is using WWE - these don't have to match?
So, if I need to do S-OFF, should I just use revone using this method https://www.youtube.com/watch?v=J4BWxtjaamM and this file http://forum.xda-developers.com/showpost.php?p=63834144&postcount=6943 .. or using the toolkit http://forum.xda-developers.com/showthread.php?t=2364445 ?
Then, which is the preference for ruu.zip vs ruu.exe? e.g. https://www.youtube.com/watch?v=ybu7fZa41so
Once all is installed, I can re-root and install xposed for stock rom tweaks? I may or may not need to reinstall TWRP...?
I'd just like to be sure of what I'm doing before I start as there's so much information out there and I don't want to brick my phone!
Any help and advice is much appreciated - thank you!

Finner42 said:
Hello,
I have a number of questions before I jump in and update my phone, so I'm hoping to get some advice on the best way to upgrade from a 4.4.3 custom rom (ARHD 83.1) to the latest stock (rooted) rom - it looks like the custom 6.0 roms aren't so stable at the moment, so best to avoid them for now?
I'm also looking to update my radio with the hope of getting a better signal, or is the radio not really affected by the rom version? Hoping to get better battery life and general stability too.
I understand that I can't just install a custom 5.0.2 rom (e.g. ARHD 93.0) or custom 6.0 rom via recovery (as I normally would do) because of firmware/radio miss-matches? I need to update this first (must be S_OFF) before I can flash.
Some details:
M7_UL
HTC_039
Unlocked
S-ON
HBOOT-1.44.0000
Current: 6.09.401.11 / 4A.14.3250.13
Carrier: Telstra (AU)
From what I can tell, my two main options are either using ruu.zip/ruu.exe or Guru Reset.
I'm S-ON, so I can use Guru Reset, but I can't seem to find the latest firmware with this.
I understand I can flash ruu.zip/ruu.exe with S-ON if the firmware is newer?
Am I better off going S-OFF now (it's easier while on 1.44?)? Do I need to be S-OFF?
How do I know which firmware version to choose? Can I jump straight to 7.19.401.2?
Will OTA work after this?
Does it matter if I use x.xx.401.x (WWE?) or x.xx.908.x (Optus?) or x.xx.841.x (Telstra??) ... I don't want any carrier software, but I would like the best radio for my carrier (Telechoice/Telstra).
I understand that HTC_039 is Optus, but my current firmware is using WWE - these don't have to match?
So, if I need to do S-OFF, should I just use revone using this method https://www.youtube.com/watch?v=J4BWxtjaamM and this file http://forum.xda-developers.com/showpost.php?p=63834144&postcount=6943 .. or using the toolkit http://forum.xda-developers.com/showthread.php?t=2364445 ?
Then, which is the preference for ruu.zip vs ruu.exe? e.g. https://www.youtube.com/watch?v=ybu7fZa41so
Once all is installed, I can re-root and install xposed for stock rom tweaks? I may or may not need to reinstall TWRP...?
I'd just like to be sure of what I'm doing before I start as there's so much information out there and I don't want to brick my phone!
Any help and advice is much appreciated - thank you!
Click to expand...
Click to collapse
Please post the output of "fastboot getvar all" (remove your imei/sn before posting)

alray said:
Please post the output of "fastboot getvar all" (remove your imei/sn before posting)
Click to expand...
Click to collapse
I've just spent the last hour trying to get fastboot working on Windows 10 with no luck (adb was working, but not any more). Is there any other way of getting that information?
I'll keep trying anyway, I'll need it. . .
Edit:
Just got it working thanks to this Win 10 reg edit - http://forum.xda-developers.com/showpost.php?p=63454708&postcount=59
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.980.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4282mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT

You could use the 1.29.980.2 CWM backup to restore your phone back to stock and from there you could either attempt to s-off your phone using Revone and do whater you want (like converting your phone to another version) or simply update your phone until you are on the latest version for your phone.
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__039-1-29-980-2-2013-05-11-zip/

alray said:
You could use the 1.29.980.2 CWM backup to restore your phone back to stock and from there you could either attempt to s-off your phone using Revone and do whater you want (like converting your phone to another version) or simply update your phone until you are on the latest version for your phone.
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__039-1-29-980-2-2013-05-11-zip/
Click to expand...
Click to collapse
Thanks for this. I'm currently running TWRP, but it looks like there's only a CWM version for this.
So, do I need to S-OFF? If I do this, and don't S-OFF, do I just get all the OTA updates, or is there something else that needs to be done for that to work?
To confirm, I can't just install the latest 5.0.2 ARHD over the top (with full wipe), because of firmware differences?

Finner42 said:
Thanks for this. I'm currently running TWRP, but it looks like there's only a CWM version for this.
So, do I need to S-OFF? If I do this, and don't S-OFF, do I just get all the OTA updates, or is there something else that needs to be done for that to work?
To confirm, I can't just install the latest 5.0.2 ARHD over the top (with full wipe), because of firmware differences?
Click to expand...
Click to collapse
You need to use CWM recovery to restore CWM backup so you'll need to flash that recovery. You don't need S-OFF to flash the recovery, restore the backup and update your phone but if you want it, better to do it before updating. After restoring the backup, you'll need to flash back the stock recovery over CWM so you can install ota update. The stock recovery can be extracted from the ota update, download it and select "install later". Once downloaded, go to your Downloads folder and copy the zip file starting with "ota" to your computer. Open the zip file and you'll see another zip named "firmware.zip", extract that one to your desktop and finally open the firmware.zip file and extract the recovery.img file from it. This file is the stock recovery to be flashed before trying to install the previously downloaded ota update.
You can't install latest ROM (sense + lollipop) because your firmware is to old. Doesn't matters if its a x.xx.401.x or x.xx.780.x base but it must be 7.xx.xxx.x

Awesome, thanks for the guidance
Again, to clarify - is S-OFF something I need, or do the risks outweigh the benefits, once everything is up to date? Once S-OFF, this will remain S-OFF? Best to do this first while still on a rooted ROM, before loading stock nandroid?
Sorry for all the questions, but your help has been great, thanks!
Sent from my HTC One using Tapatalk

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)