Database Develop

[Q] HTC One fail big time

I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(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
Pls pls help.Thank You.

erinar88 said:
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(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
Pls pls help.Thank You.
Click to expand...
Click to collapse
Couldn`t work as you are S-On. I think you`re stuck bro afaik. Maybe someone else knows a solution. Good luck.

That's odd. It shouldn't have run at all since you can't downgrade using a RUU without s-off. It should have prompted a RUU error noting that you were on a later version.
Is your phone rooted and unlocked yet? Did you do anything to it besides run the RUU?

Can't you just use fastboot to push a custom recovery and then sideload a custom or stock ROM?

AllAboutTheCore said:
Can't you just use fastboot to push a custom recovery and then sideload a custom or stock ROM?
Click to expand...
Click to collapse
Looks like his only option. Surprised that the RUU wiped his device before getting the error.
There's no way to downgrade hboot with s-on atm.

I'm gonna be 'that guy'... What the heck were you doing flashing an RUU on S-on with 'limited IT knowledge'...
There's a reason RUUs aren't released. It's to prevent this.
On a side note I would try another RUU download. Where are you getting the error at? What's the phone doing?
Sent from my HTC One using Tapatalk 4 Beta

I'm wondering now. Did you actually try to fastboot flash the 1.44 WWE firmware.zip in RUU mode despite being s-on? Because if you really did that, the phone is dead. You're getting a signature error because the phone is s-on and you managed to corrupt something important. Being s-on, I doubt there is any way to fix it.
An expensive lesson, but maybe you'll be more careful next time. Gaining s-off isn't worth bricking your phone.

This is confusing as the official RUU's (exe's and zips) will simply not allow you to downgrade the hboot or to flash an older version of the firmware without having s-off so my thoughts are exactly the same as iElvis.
I cannot see how you managed to do what you did.
So questions....
Are you running a custom recovery?
Is your bootloader locked or unlocked?
Have you tried holding vol down and power for about 15 to 30 seconds to see if you can get into the bootloader?
Did you do something like reboot into bootloader, fastboot oem rebootRUU and then fastboot flash zip firmware.zip?
TELL US the exact steps you went through so we can try to help you and worst case scenario you have bricked your phone.

I am having a similar problem only i have S-off but i cant find the right RUU or the right recovery.img to fastboot it .
If you have rumrunner_HTC_0.5.0.zip you could gain s-off very easy .

erinar88 said:
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(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
Pls pls help.Thank You.
Click to expand...
Click to collapse
Sorry m8. Hate to break it to you but I accidentally did this too and I've found no solution for it. Ended up buying a new One...... I don't think there is a fix for this at all.
Sent from my HTC One using xda app-developers app

[Solved] S-off with hboot 1.55 issues, need help.

I cannot seem to get s-off with rumrunner. I'm rooted on hboot 1.55. I've tried on xp and Windows 8 on a few different pc's to no avail. I last followed a guide and did it on a live Ubuntu USB as my laptop runs the 64bit distribution. I get to a line that says "sanitizing, skunky rum" and then says wait. Then periods fill across the line and it sits for a while. Then several T's are displayed and the command prompt comes back up. S is not off.
I'm at a loss here. Anyone have any ideas? I've read pretty exhaustively and I'm not finding any solution.
Thanks.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Try this... It's actually really easy... Good luck
http://forum.xda-developers.com/showthread.php?t=2606577
Sent from my LG-D803 using xda app-developers app

I tried that. That resulted in the line of T's and did not give me s-off.
Sent via MobileBlast!

Bradlees said:
I tried that. That resulted in the line of T's and did not give me s-off.
Sent via MobileBlast!
Click to expand...
Click to collapse
Could be because you ran it on 64bit and it's stated on rumrunner 's site and in step one of my instructions to use a 32bit version. For some reason 64bit isn't supported. You don't have to install it just throw it on a disk and boot into the "try" mode.
Anyways, good luck
Sent from my LG-D803 using xda app-developers app

No, I ran it on a live USB with a 32 bit distribution after I realized my mistake when it failed on my 64 bit. I tried the process 3 times on the the 32 bit all with the same result before I gave up and asked for help.
Sent via MobileBlast!

Bradlees said:
No, I ran it on a live USB with a 32 bit distribution after I realized my mistake when it failed on my 64 bit. I tried the process 3 times on the the 32 bit all with the same result before I gave up and asked for help.
Sent via MobileBlast!
Click to expand...
Click to collapse
what's your "version-main"? or even better post a "fastboot getvar all" (excluding IMEI and s/n)

Bradlees said:
No, I ran it on a live USB with a 32 bit distribution after I realized my mistake when it failed on my 64 bit. I tried the process 3 times on the the 32 bit all with the same result before I gave up and asked for help.
Sent via MobileBlast!
Click to expand...
Click to collapse
That sucks... The only other suggestion is something I was just informed of but didn't have to do myself.
In Ubuntu they had to open the Ubuntu software Centre, edit tab, software sources and make sure that "supported free and open source software" is selected.
Sorry wish I had more ideas
Sent from my LG-D803 using xda app-developers app

nkk71 said:
what's your "version-main"? or even better post a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
version: 0.5
version bootloader: 1.55.0000
version baseband: 4A.21.3263.03
version cpld: none
version microp: none
version-main: 3.24.531.3

Bradlees said:
version: 0.5
version bootloader: 1.55.0000
version baseband: 4A.21.3263.03
version cpld: none
version microp: none
version-main: 3.24.531.3
Click to expand...
Click to collapse
and the rest please , eg:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also what ROM are you on?

nkk71 said:
and the rest please , eg:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3801mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also what ROM are you on?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3896mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm on just on stock rooted. Is that why? Do I just need to flash a ROM?

Bradlees said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3896mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm on just on stock rooted. Is that why? Do I just need to flash a ROM?
Click to expand...
Click to collapse
from rumrunner: "as long as you have root) and also custom roms. We DO prefer users have an unsecure kernel", so try ARHD 31.6 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (it's already rooted & unsecured kernel)
though I have to mention that other T-Mobile users are having issues, but usually on firmware 3.63.111.x
Good luck

nkk71 said:
from rumrunner: "as long as you have root) and also custom roms. We DO prefer users have an unsecure kernel", so try ARHD 31.6 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (it's already rooted & unsecured kernel)
though I have to mention that other T-Mobile users are having issues, but usually on firmware 3.63.111.x
Good luck
Click to expand...
Click to collapse
So I'm sure I'm reading this right: I don't need a custom ROM, correct? Its not listed as a prerequisite on the rumrunner site, just root. I could perhaps just flash an unsecure kernel over my stock rom?
Thanks, btw

@nkk71 for the win...the kernel was going to be my next suggestion. After doing some googling lol
Hope it works. If anyone can helps its nkk71

Bradlees said:
So I'm sure I'm reading this right: I don't need a custom ROM, correct? Its not listed as a prerequisite on the rumrunner site, just root. I could perhaps just flash an unsecure kernel over my stock rom?
Thanks, btw
Click to expand...
Click to collapse
yes you could try it that way (ie flash custom kernel), but why not go for ARHD 31.6? it's already rooted, unsecured kernel, has USB debugging enabled, has Power->Fast boot disabled (I think), has adb shell su already granted.
if it's just about not wanting to erase apps+data+settings, then just do a nandroid of your current setup, flash ARHD 31.6, get S-Off (hopefully) and restore nandroid afterwards.

I just picked up a new ONE after returning it for the camera colors in dark light (had it for 3-4 months HBOOT 1.44)
this new one is on HBOOT 1.55 to use rumrunner I had to:
1) HTC DEV unlock
2) flash custom recovery
3) install CM 10.2 (the final release works best CM 11 did not work)
4) flash SU zip
5) run rumrunner
With this process it had to pour less than with hboot 1.44 and cm 10.2. went pretty quickly if you have done it before. But the kernel is almost definitely the problem.
have faith it can be done

nkk71 said:
yes you could try it that way (ie flash custom kernel), but why not go for ARHD 31.6? it's already rooted, unsecured kernel, has USB debugging enabled, has Power->Fast boot disabled (I think), has adb shell su already granted.
if it's just about not wanting to erase apps+data+settings, then just do a nandroid of your current setup, flash ARHD 31.6, get S-Off (hopefully) and restore nandroid afterwards.
Click to expand...
Click to collapse
Success! First try it worked after flashing the ARHD ROM on windows xp pc. Thanks.

tobesedated said:
@nkk71 for the win...the kernel was going to be my next suggestion. After doing some googling lol
Hope it works. If anyone can helps its nkk71
Click to expand...
Click to collapse
It worked with a custom ROM. Didn't even need to do it on Ubuntu, it worked on winxp. Thanks

tmckenn2 said:
I just picked up a new ONE after returning it for the camera colors in dark light (had it for 3-4 months HBOOT 1.44)
this new one is on HBOOT 1.55 to use rumrunner I had to:
1) HTC DEV unlock
2) flash custom recovery
3) install CM 10.2 (the final release works best CM 11 did not work)
4) flash SU zip
5) run rumrunner
With this process it had to pour less than with hboot 1.44 and cm 10.2. went pretty quickly if you have done it before. But the kernel is almost definitely the problem.
have faith it can be done
Click to expand...
Click to collapse
That was the solution. I'm now S-Off. Thanks.

Bradlees said:
Success! First try it worked after flashing the ARHD ROM on windows xp pc. Thanks.
Click to expand...
Click to collapse
Congrats, good to hear
can you edit main thread title to include [SOLVED] so others can refer to it too. thanks

Bradlees said:
It worked with a custom ROM. Didn't even need to do it on Ubuntu, it worked on winxp. Thanks
Click to expand...
Click to collapse
That's great... Isn't it awesome how so many people are willing to help someone out?
Sent from my LG-D803 using xda app-developers app

Getting an error trying to install latest RUU.

I'm rooted/s-off and trying to install the latest Sprint RUU, but run into an error. It happens on the black screen with the HTC logo, right after the RUU boots up the bootloader.
Any ideas on how to rectify this?
Also, is the latest fw able to be rooted, just in case I don't like it I can restore the backup I made?
Sent from my HTC One using XDA Premium 4 mobile app.

johnequickiii said:
I'm rooted/s-off and trying to install the latest Sprint RUU, but run into an error. It happens on the black screen with the HTC logo, right after the RUU boots up the bootloader.
Any ideas on how to rectify this?
Also, is the latest fw able to be rooted, just in case I don't like it I can restore the backup I made?
Sent from my HTC One using XDA Premium 4 mobile app.
Click to expand...
Click to collapse
Do you have more info on the bootloader?
Also, just for reference, can we see your fastboot getvar all ?
Remove IMEI, serial No and MEID.
To answer your second questions, yes. I am running the latest firmware with no root issues.

I totally forgot to mention that it was supposed to be the progress bar screen that's black with the HTC logo in the middle.
I'll be back with a getvar later on probably.
Sent from my HTC One using XDA Premium 4 mobile app.

johnequickiii said:
I totally forgot to mention that it was supposed to be the progress bar screen that's black with the HTC logo in the middle.
I'll be back with a getvar later on probably.
Sent from my HTC One using XDA Premium 4 mobile app.
Click to expand...
Click to collapse
What does that mean? Can I see a video or pics?

Better yet, the getvar.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(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: 4167mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

johnequickiii said:
Better yet, the getvar.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(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: 4167mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Getvar looks normal
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.651.2
(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT
(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: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So now that we know there's nothing really wrong with your firmware, what exactly is the problem?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Where, relative to these commands is the error happening?
Also remember to quote, or else I don't get notifs.

johnequickiii said:
Better yet, the getvar.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.05.651.6
(bootloader) version-misc: PVT SHIP S-OFF
(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: 4167mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-35824024
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I have noticed the latest RUU's will not run properly (M7 and M8) if the hboot does not match. The latest hboot for the M7 is 1.57.
You may have to flash the latest Full Firmware to update your hboot then run the RUU.

sauprankul said:
Getvar looks normal
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.651.2
(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT
(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: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So now that we know there's nothing really wrong with your firmware, what exactly is the problem?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Where, relative to these commands is the error happening?
Also remember to quote, or else I don't get notifs.
Click to expand...
Click to collapse
I attempt to run the RUU straight from my desktop.
What happens is the phone does it's initial restart into RUU mode in the bootloader, then the very next screen is the HTC logo on a black screen, which is seemingly supposed to have a progress bar right under the logo. Right there is where the error is thrown.
The RUU program suggests I unplug the phone, which I do, and it's just the bootloader screen with only RUU the only highlightable option. From there, I have to hard reset the phone and I'm back to the start, which is my phone as usual, so it doesn't seem like it ever gets to copy a file or format anything.

johnequickiii said:
I attempt to run the RUU straight from my desktop.
What happens is the phone does it's initial restart into RUU mode in the bootloader, then the very next screen is the HTC logo on a black screen, which is seemingly supposed to have a progress bar right under the logo. Right there is where the error is thrown.
The RUU program suggests I unplug the phone, which I do, and it's just the bootloader screen with only RUU the only highlightable option. From there, I have to hard reset the phone and I'm back to the start, which is my phone as usual, so it doesn't seem like it ever gets to copy a file or format anything.
Click to expand...
Click to collapse
So what's the exact error message? And no, the progress bar only appears after you issue the flash command.
Also, what OS are you using?

BD619 said:
I have noticed the latest RUU's will not run properly (M7 and M8) if the hboot does not match. The latest hboot for the M7 is 1.57.
You may have to flash the latest Full Firmware to update your hboot then run the RUU.
Click to expand...
Click to collapse
What's the latest full one? I'll grab that and give it a shot.
The only reason I'm trying to update now is because I have this issue that seems to kill my battery within 3-4 hours, and I can't figure out why. I thought I'd give a full update a try to see whether it's my phone or something in my setup doing it.
Stock 3.05.651.6, but when I did it I had to start with the very first fw the phone had and take each ota til I was where I am now. That was a long time ago, and this issue only started a week or two ago at most.
Any potential ideas in that realm would be super appreciated.

johnequickiii said:
What's the latest full one? I'll grab that and give it a shot.
The only reason I'm trying to update now is because I have this issue that seems to kill my battery within 3-4 hours, and I can't figure out why. I thought I'd give a full update a try to see whether it's my phone or something in my setup doing it.
Stock 3.05.651.6, but when I did it I had to start with the very first fw the phone had and take each ota til I was where I am now. That was a long time ago, and this issue only started a week or two ago at most.
Any potential ideas in that realm would be super appreciated.
Click to expand...
Click to collapse
5.05.651.2 is the latest

BD619 said:
5.05.651.2 is the latest
Click to expand...
Click to collapse
I probably should've mentioned this in the first post, but that's the RUU I'm trying to use.
I meant to ask which was the first one with the updated bootloader.

@BD619 should he try to flash each partition individually via fastboot?

johnequickiii said:
I probably should've mentioned this in the first post, but that's the RUU I'm trying to use.
I meant to ask which was the first one with the updated bootloader.
Click to expand...
Click to collapse
Flash the 5.05.651.2 Full Firmware then flash the 5.05.651.2 RUU
sauprankul said:
@BD619 should he try to flash each partition individually via fastboot?
Click to expand...
Click to collapse
Nah that would be a PITA lol.

BD619 said:
Flash the 5.05.651.2 Full Firmware then flash the 5.05.651.2 RUU
Click to expand...
Click to collapse
Where would I find the full one? I got the RUU from HTC.

johnequickiii said:
Where would I find the full one? I got the RUU from HTC.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2795856

BD619 said:
Flash the 5.05.651.2 Full Firmware then flash the 5.05.651.2 RUU
Click to expand...
Click to collapse
Now I'm confused. Is there a difference between flashing the firmware and flashing the RUU?
which one is this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
?

sauprankul said:
Now I'm confused. Is there a difference between flashing the firmware and flashing the RUU?
which one is this:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
?
Click to expand...
Click to collapse
The firmware will update hboot,radio, ect.
The RUU will update the firmware aswell as the OS.

Got this trying to update with the full firmware.
Sorry about the crappy pic quality. Sensor blew long ago.
Sent from my HTC One using XDA Premium 4 mobile app.

johnequickiii said:
Got this trying to update with the full firmware.
Sorry about the crappy pic quality. Sensor blew long ago.
Sent from my HTC One using XDA Premium 4 mobile app.
Click to expand...
Click to collapse
Make sure it's in the folder you are using to open the cmd window.
Make sure it names firmware.zip not firmware.zip.zip

Return to stock Htc One

So I've had this One m7 for 2 years now and have gotten a new phone. I plan to give it to an older member of my family but will ned to return to stock before I can any help?
BTW: I am S-On since I cannot gain s-off due to the H-boot limitations (trust me i have tried)
H-boot 1.61
any help would be greaty apprectiated thank you.

ShaheenXE said:
So I've had this One m7 for 2 years now and have gotten a new phone. I plan to give it to an older member of my family but will ned to return to stock before I can any help?
BTW: I am S-On since I cannot gain s-off due to the H-boot limitations (trust me i have tried)
H-boot 1.61
any help would be greaty apprectiated thank you.
Click to expand...
Click to collapse
What is the output of "fastboot getvar all" (dont post imei/serialno)

bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.22
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3850mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Sent from my HTC One using XDA Free mobile app

ShaheenXE said:
bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-main: 7.19.401.22
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) security: on
Click to expand...
Click to collapse
you can find ruu in @alray's post: http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
(look under: M7_UL version 7.19.401.22)
since you're s-on, you'll need to relock bootloader then properly flash the ruu, instructions can be found in post #1 http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
under "How To Flash" at the beginning of that post
btw, for S-OFF you would need to use Sunshine

Ok so I've downloaded the zip but command prompt cannot use the zip as it says the zip file is invalid.
Sent from my HTC One using XDA Free mobile app

ShaheenXE said:
Ok so I've downloaded the zip but command prompt cannot use the zip as it says the zip file is invalid.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
You don't have to open the zip and you can't open it anyway, its encrypted. Just flash the whole zip file using the instructions linked above by nkk71 (post #1 of the ruu collection thread).

Command prompt can't seem to run it either
Sent from my HTC One using XDA Free mobile app

ShaheenXE said:
Command prompt can't seem to run it either
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
can you post a screenshot of your command prompt please?

Looking for correct RUU.exe

Hello all XDA members,
I am looking for the correct RUU.exe for my HTC One M7. Its on Vodafone UK (VODAP001) and HBOOT 1.61.000 and is S-On. I have already relocked the bootloader and flashed the stock recovery back. I have found and tried many RUU.zip from here and HTC but I have learned that as I am S-on I am unable to go this route. This HTC One m7 was running a custom ROM and TWRP but since I am giving it my Father I needed it back to stock and ready to receive any OTA updates that Vodafone throw out.
Thank you all
Andrew

worf105 said:
Hello all XDA members,
I am looking for the correct RUU.exe for my HTC One M7. Its on Vodafone UK (VODAP001) and HBOOT 1.61.000 and is S-On. I have already relocked the bootloader and flashed the stock recovery back. I have found and tried many RUU.zip from here and HTC but I have learned that as I am S-on I am unable to go this route. This HTC One m7 was running a custom ROM and TWRP but since I am giving it my Father I needed it back to stock and ready to receive any OTA updates that Vodafone throw out.
Thank you all
Andrew
Click to expand...
Click to collapse
Can you please post the output of "fastboot getvar all" (hide your imei and sn before posting)
Will be easier to point you the correct RUU.
Btw is KatKiss 5.1 working fine? Haven't played with my tf101 for a while!

Thank you for your quick reply and as requested here is the output to fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Sxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4154mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-92aee636
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Kind Regards,
Andrew

Btw is KatKiss 5.1 working fine? Haven't played with my tf101 for a while!
Click to expand...
Click to collapse
Yes Lollipop 5.1 is working great and I have had no problems. Hopefully TimDuru will be presenting Marshmallow soon for the TF101

worf105 said:
Thank you for your quick reply and as requested here is the output to fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Sxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4154mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-92aee636
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Kind Regards,
Andrew
Click to expand...
Click to collapse
The latest RUU for that version is 7.18.161.21. Since your phone is S-ON you can only flash RUU that are the same version or higher than your actual version (7.18.161.30). There is a way to bypass this. Go to this thread and read at the end of my post (post #2) under "how to downgrade with s-on". Once done and your version-main is showing 7.18.161.2 instead of 7.18.161.30 , flash the 7.18.161.21 RUU using instructions of post #1 (RUU file is at post #2). Don't forget to use the fastboot version provided at post #1, the normal fastboot version won't work to flash a lollipop RUU.
worf105 said:
Yes Lollipop 5.1 is working great and I have had no problems. Hopefully TimDuru will be presenting Marshmallow soon for the TF101
Click to expand...
Click to collapse
Its amazing how this dev is still supporting this device, will try to update :good:

Thank you alray
Will let you know how I get on with your instructions.
Ye TimDuru has done a great job in supporting the TF101. If he never I would have bought another tablet years ago.
Kindest Regards,
Andrew

I worked a treat, thank you alray for your expert help in this matter.
Gratefully yours,
Andrew

worf105 said:
I worked a treat, thank you alray for your expert help in this matter.
Gratefully yours,
Andrew
Click to expand...
Click to collapse
You're welcome :good:

alray said:
The latest RUU for that version is 7.18.161.21. Since your phone is S-ON you can only flash RUU that are the same version or higher than your actual version (7.18.161.30). There is a way to bypass this. Go to this thread and read at the end of my post (post #2) under "how to downgrade with s-on". Once done and your version-main is showing 7.18.161.2 instead of 7.18.161.30 , flash the 7.18.161.21 RUU using instructions of post #1 (RUU file is at post #2). Don't forget to use the fastboot version provided at post #1, the normal fastboot version won't work to flash a lollipop RUU.
Its amazing how this dev is still supporting this device, will try to update :good:
Click to expand...
Click to collapse
hi do you can helme whith my HTC wls RUU :crying:

jhon8500 said:
hi do you can helme whith my HTC wls RUU :crying:
Click to expand...
Click to collapse
Yes, what is the problem?

alray said:
Yes, what is the problem?
Click to expand...
Click to collapse
okay thanks for replying I have a htc one m7 wls I tried to install a rom of cyanogen but I could not install it I decided to return my htc to s-on with the intention of reinstalling the rom stock of factory but I could not find it the intetnado install by SDK but I get the error "error: device '(null)' not found" and by means of the installer of the ruu by means of .exe says it is not appropriate if you can help me I would appreciate this,
this information of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33YS901134
(bootloader) imei:xxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3841mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

jhon8500 said:
okay thanks for replying I have a htc one m7 wls I tried to install a rom of cyanogen but I could not install it I decided to return my htc to s-on with the intention of reinstalling the rom stock of factory but I could not find it the intetnado install by SDK but I get the error "error: device '(null)' not found" and by means of the installer of the ruu by means of .exe says it is not appropriate if you can help me I would appreciate this,
this information of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33YS901134
(bootloader) imei:xxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3841mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Sorry for the delayed answer.
First, going back S-ON wasn't required and it's also a bad move. Having S-OFF can help a lot when troubleshooting your phone. I don't know what cyanogenmod rom version you tried to install (cyanogenmod roms are so old) but are you sure the one you tried was compatible with the M7_WLS variant? This phone variant will only work with custom roms made specifically for this variant and must also be flashed with a custom recovery compatible with WLS . Just saying because this is the most common error made by people having this phone variant.
Now, what ruu version are you trying to install? The one you need is 6.23.651.10 and can be found here:
http://dl3.htc.com/application/RUU_...99.2143463114.1556074529-999987239.1556074529
Don't forget that since you went back S-ON you now must have a locked or re-locked bootloader to install a RUU. It won't install if it's unlocked.
If not already done, you can re-lock your bootloader using fastboot from a command window using this single command:
Code:
fastboot oem lock
then install the RUU