Database Develop

[q] no os in htc one

Hi ,
i have a HTC ONE mobile phone, few days before i tried to install cyangonMod but unfortunately due to faulty USB my installation broke up.
so i ended up with no OS installed on my HTC ONE. later i searched out the forum and rooted back to the ROM as it was.
i founded links for the RUU zip files to install but since my phone is not linked with any operator, i have no clue which link to use.
my friend suggested me a link which was
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
when i try to install the zip using the following commands
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip
i received following error
sending 'zip' (1010948 KB)...
OKAY [ 46.936s]
writing 'zip'...
(bootloader) signature checking
FAILED (remote: 12 signature ve
finished. total time: 133.252s
I have been trying all different ways but so far no solution.
could any one help me get back to my Android please
if my question is not clear or need any explanation please dont hesitate
Thank you in Advance

aamalraj said:
Hi ,
i have a HTC ONE mobile phone, few days before i tried to install cyangonMod but unfortunately due to faulty USB my installation broke up.
so i ended up with no OS installed on my HTC ONE. later i searched out the forum and rooted back to the ROM as it was.
i founded links for the RUU zip files to install but since my phone is not linked with any operator, i have no clue which link to use.
my friend suggested me a link which was
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
when i try to install the zip using the following commands
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip
i received following error
sending 'zip' (1010948 KB)...
OKAY [ 46.936s]
writing 'zip'...
(bootloader) signature checking
FAILED (remote: 12 signature ve
finished. total time: 133.252s
I have been trying all different ways but so far no solution.
could any one help me get back to my Android please
if my question is not clear or need any explanation please dont hesitate
Thank you in Advance
Click to expand...
Click to collapse
post the output of ''fastboot getvar all' minus imei/sn, otherwise we can't help

output of ''fastboot getvar all'
alray said:
post the output of ''fastboot getvar all' minus imei/sn, otherwise we can't help
Click to expand...
Click to collapse
D:\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s

aamalraj said:
D:\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s
Click to expand...
Click to collapse
You need this RUU, and because its a downgrade, you will need to s-off first and then flash hboot 1.44. After your phone will be back to stock 1.28.401.7 and you will receive ota to latest version. Follow this procedure and don't forget to thanks the OP for his awesome guide :good:.
The other option if you don't want/can't s-off is to use this rom (guru reset). this is the stock rom for your version, and you will be able to update ota after. Instructions for guru reset can be found here

Still not working
alray said:
You need this RUU, and because its a downgrade, you will need to s-off first and then flash hboot 1.44. After your phone will be back to stock 1.28.401.7 and you will receive ota to latest version. Follow this procedure and don't forget to thanks the OP for his awesome guide :good:.
The other option if you don't want/can't s-off is to use this rom (guru reset). this is the stock rom for your version, and you will be able to update ota after. Instructions for guru reset can be found here
Click to expand...
Click to collapse
The first solution didnt work cause since i have no OS in my HTC so adb functions are not working, since adb functions are not working so i cant do an s-off
The second solution: i dont know how to get the zip file inside my phone cause i cant execute adb sideload, is there anyother way to trasfer the file to the phone or is there any other way of executing it guru reset.

aamalraj said:
The first solution didnt work cause since i have no OS in my HTC so adb functions are not working, since adb functions are not working so i cant do an s-off.
The second solution: i dont know how to get the zip file inside my phone cause i cant execute adb sideload, is there anyother way to trasfer the file to the phone or is there any other way of executing it guru reset.
Click to expand...
Click to collapse
Boot your phone in TWRP recovery, dont select any option, just let the phone boot in twrp main menu
then:
Code:
adb push name_of_guru_reset_file.zip /sdcard/
then in twrp select install, chose the .zip and follow instruction in aroma installer.

alray said:
You need this RUU, and because its a downgrade, you will need to s-off first and then flash hboot 1.44. After your phone will be back to stock 1.28.401.7 and you will receive ota to latest version. Follow this procedure and don't forget to thanks the OP for his awesome guide :good:.
The other option if you don't want/can't s-off is to use this rom (guru reset). this is the stock rom for your version, and you will be able to update ota after. Instructions for guru reset can be found here
Click to expand...
Click to collapse
Thank you very much i got my OS back,

aamalraj said:
Thank you very much i got my OS back,
Click to expand...
Click to collapse
Glad for you :highfive:

[Q] Bootloop, S-ON, HBOOT 1.55, version-main blank

TWRP 2.6.3.3 is installed, adb is working. Funny enough, adb stops working with TWRP 2.7.
..adb sideload of Android_Revolution_HD-One_53.0 seems to work, go through the install questions, but never gets past HTC logo on reboot.
...flashed boot.img from HD-53 after sideload just in case, no change
...did factory reset in twrp, as well as wiping cache in twrp.. no change
..tried relocking bootloader and flashing RUU zip for Telus001, but failed with error, FAILED (remote: 12 signature verify fail)
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 12345
(bootloader) imei: 12345
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4268mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
At a bit of a loss... but it doesn't seem dead just yet....

romansj said:
TWRP 2.6.3.3 is installed, adb is working. Funny enough, adb stops working with TWRP 2.7.
..adb sideload of Android_Revolution_HD-One_53.0 seems to work, go through the install questions, but never gets past HTC logo on reboot.
...flashed boot.img from HD-53 after sideload just in case, no change
...did factory reset in twrp, as well as wiping cache in twrp.. no change
..tried relocking bootloader and flashing RUU zip for Telus001, but failed with error, FAILED (remote: 12 signature verify fail)
getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 12345
(bootloader) imei: 12345
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4268mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.049s
At a bit of a loss... but it doesn't seem dead just yet....
Click to expand...
Click to collapse
Did you md5 checked both your recovery and your rom before flashing?
Btw, you need a locked or relocked bootloader to flash a ruu with S-ON... Thats why you got the signature fail.

alray said:
Did you md5 checked both your recovery and your rom before flashing?
Btw, you need a locked or relocked bootloader to flash a ruu with S-ON... Thats why you got the signature fail.
Click to expand...
Click to collapse
Didn't do md5 check, but twrp 2.6.3.3 comes up as expected, and AD-53 installs as expected.
The bootloader was relocked for the RUU zip install.. I thought I read somewhere that it was because there is no OS present, or something.

romansj said:
Didn't do md5 check, but twrp 2.6.3.3 comes up as expected, and AD-53 installs as expected.
The bootloader was relocked for the RUU zip install.. I thought I read somewhere that it was because there is no OS present, or something.
Click to expand...
Click to collapse
what ruu are you trying to flash?

alray said:
what ruu are you trying to flash?
Click to expand...
Click to collapse
RUU Zip M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted

romansj said:
RUU Zip M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted
Click to expand...
Click to collapse
you are S-ON, you can't use decrypted RUU! With s-on you can only use SIGNED ruu
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_351500_signed_2.exe

alray said:
you are S-ON, you can't use decrypted RUU! With s-on you can only use SIGNED ruu
Click to expand...
Click to collapse
Thanks, I'll give that a shot once it finishes downloading. I was coming to the same conclusion but was stuck on trying to figure out why sideloading wasn't working. I guess the firmware is corrupt or some such? First time messing with an HTC and the world of RUUs
Will report back..

alray said:
you are S-ON, you can't use decrypted RUU! With s-on you can only use SIGNED ruu
]
Click to expand...
Click to collapse
Fails with error 155... Here's the relevent log:
htc_fastboot -s serial getvar boot-mode</CMD>
Execution time is 3(ms)boot-mode: RUU</OUT>
htc_fastboot -s serial erase cache</CMD>
Execution time is 60(ms)erasing 'cache'... OKAY</OUT>
Try to read image count from android-info.txt in rom.zip
The rom is encrypted, read the header instead.
[getImageCount] Large and signed rom
getImageCount, nHR: 18
htc_fastboot -s serial -d flash zip C:\Users\rhino\AppData\Local\Temp\{8B222E2D-DAB9-49ED-9B39-D1FC22F745A1}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
sending 'zip'... (42406 KB) OKAY</OUT>
=====Sending zip OK=====
writing 'zip'... (bootloader) adopting the signature contained in this image...</OUT>
(bootloader) signature checking...</OUT>
(bootloader) rom parsing start ...</OUT>
(bootloader) rom parsing finish ...</OUT>
(bootloader) zip header checking...</OUT>
(bootloader) zip info parsing...</OUT>
(bootloader) Read zipped android_info fail</OUT>
Execution time is 10382(ms)</OUT>
FAILED (status read failed (Too many links))</OUT>

HTC One [M7] STOCK ROM *DECRYPTED*

I can't seem to find one of these thats decrypted and works. Im looking for any of the roms because from the i can just run software updates. It'd be nicest to have the KitKat STOCK rom for the phone. Please provide a link if you have one or suggest other ideas.

GamerUpToDate said:
I can't seem to find one of these thats decrypted and works. Im looking for any of the roms because from the i can just run software updates. It'd be nicest to have the KitKat STOCK rom for the phone. Please provide a link if you have one or suggest other ideas.
Click to expand...
Click to collapse
are you s-off ? you need s-off for a decrypted RUU

clsA said:
are you s-off ? you need s-off for a decrypted RUU
Click to expand...
Click to collapse
OH you do?!!! The steps didn't say that. I am currently trying to flash everything back to stock. Kinda played with the phone too much. You have a link to an article that says how to get S-off or could you tell me how? Wow this post is all wrong anyways. I am actually looking for an ENCRYPTED STOCK ROM file for the HTC One M7. Thanks for the help.

GamerUpToDate said:
OH you do?!!! The steps didn't say that. I am currently trying to flash everything back to stock. Kinda played with the phone too much. You have a link to an article that says how to get S-off or could you tell me how? Wow this post is all wrong anyways. I am actually looking for an ENCRYPTED STOCK ROM file for the HTC One M7. Thanks for the help.
Click to expand...
Click to collapse
yeah still not enough info
look here >> http://androidruu.com/index.php?developer=M7
to s-off search for firewater or rumrunner

clsA said:
yeah still not enough info
look here >> http://androidruu.com/index.php?developer=M7
to s-off search for firewater or rumrunner
Click to expand...
Click to collapse
Could I pm you? I just need a little more help to finish the process and you seem like you know what your doing.

GamerUpToDate said:
Could I pm you? I just need a little more help to finish the process and you seem like you know what your doing.
Click to expand...
Click to collapse
Just ask I'll be up for another hour or so

clsA said:
Just ask I'll be up for another hour or so
Click to expand...
Click to collapse
Ok awesome. So Originally this whole problem started when i wanted to get rid of CyanogenMod 11. I did it wrong was kinda a sloppy process so i fkd up a couple of things. Currently, im trying to get the phone back to everything STOCK. Like how i first had it before CyanogenMod (Android 4.4 or 4.2 dont remember doesnt matter, one of the two). So i found this thread:
http://forum.xda-developers.com/showthread.php?t=2251800
And it was working great, i had it all flowing smoothly until i got the error message:
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
And there was a reply to this which told me to find another ROM because i was either using one for the wrong phone or it was decrypted, which got me to create this thread to find others but so far ive tried about 10 none of them have worked.
SO thats my situation right now an thoughts?

GamerUpToDate said:
Ok awesome. So Originally this whole problem started when i wanted to get rid of CyanogenMod 11. I did it wrong was kinda a sloppy process so i fkd up a couple of things. Currently, im trying to get the phone back to everything STOCK. Like how i first had it before CyanogenMod (Android 4.4 or 4.2 dont remember doesnt matter, one of the two). So i found this thread:
http://forum.xda-developers.com/showthread.php?t=2251800
And it was working great, i had it all flowing smoothly until i got the error message:
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
OKAY [ 35.969s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 88.871s
And there was a reply to this which told me to find another ROM because i was either using one for the wrong phone or it was decrypted, which got me to create this thread to find others but so far ive tried about 10 none of them have worked.
SO thats my situation right now an thoughts?
Click to expand...
Click to collapse
Are you using a Sprint phone ?
post the results from fastboot getvar all (minus your serial no and imei)
where are you getting the rom.zip files from .. any links ?

clsA said:
Are you using a Sprint phone ?
post the results from fastboot getvar all (minus your serial no and imei)
where are you getting the rom.zip files from .. any links ?
Click to expand...
Click to collapse
The ROM zip files... jesus there been so many. I've downloaded over 9 of them none of the work. Mine is AT&T by the way not sprint.
ok here are the resuts:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3537mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s

GamerUpToDate said:
The ROM zip files... jesus there been so many. I've downloaded over 9 of them none of the work. Mine is AT&T by the way not sprint.
ok here are the resuts:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3537mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
Click to expand...
Click to collapse
yeah your s-on their are not many rom.zip that are not decrypted
your also on the new AT&T Firmware so you only have one choice in RUU
this one >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
You have to relock your bootloader to use it
fastboot oem lock

GamerUpToDate said:
C:\Android>fastboot flash zip Rom.zip
sending 'zip' (421214 KB)...
Click to expand...
Click to collapse
That filesize does not look good at all!! ruu's should be about 1GB. This 400MB file can't be an ruu!!
GamerUpToDate said:
The ROM zip files... jesus there been so many. I've downloaded over 9 of them none of the work. Mine is AT&T by the way not sprint.
ok here are the resuts:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: low
finished. total time: 0.044s
Click to expand...
Click to collapse
http://androidruu.com/getdownload.p...09_10.26.1718.01L_release_356565_signed_2.exe
That would be the RUU for you (based on MID and CID), though better check with @clsA, cause some of these newer RUUs don't always work.... and he's tried this one I think.
Oh and charge your battery before trying to run/flash ruu's!!!
.

clsA said:
yeah your s-on their are not many rom.zip that are not decrypted
your also on the new AT&T Firmware so you only have one choice in RUU
this one >> http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
You have to relock your bootloader to use it
fastboot oem lock
Click to expand...
Click to collapse
Ok. Im sort of lost wat ROM zip do i use? Because now i have that RUU but i don't know how to use it to revert everything back to stock...

GamerUpToDate said:
Ok. Im sort of lost wat ROM zip do i use? Because now i have that RUU but i don't know how to use it to revert everything back to stock...
Click to expand...
Click to collapse
it's a windows EXE file you simply run it with your phone plugged to your PC
just lock the bootloader first

How to restore to Stock Sense (6) with S-ON?

I have used the Guru reset from HTC 1 Guru to reset my HTC One M7 on Three (Hutchinson 3G) UK with version 7.19.771.1.
Like some others I have had the problem of a boot loop when getting the Android 4.3 OTA after 2 minor updates which worked fine.
I have learned that this happened because my firmware is higher than the firmware of the OTA.
I was able to get out of the boot loop fine by flashing TWRP recovery and restoring to my TWRP backup of CyanogenMod, but I still want to go back to stock Sense.
I can't S-OFF as Sunshine is the only tool for HBOOT 1.61 and that won't work on CyanogenMod as it says that I need to be using stock. Also, I don't have the money to pay for it anyway.
So I'm wondering if anyone knows how I can get to stock Sense with all updates applied.
I was wondering if I could do a Guru reset again without performing updates, and then use a RUU of a more recent version to get to updated stock. I thought this may work because the version of the RUU would be higher than that of the current software.
Or would I get something from the HTC Dev Center downloads? Etc
Or is there another way?
Thanks for reading!
(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.771.1
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3786mV
(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

Zannxdaaccount said:
I have used the Guru reset from HTC 1 Guru to reset my HTC One M7 on Three (Hutchinson 3G) UK with version 7.19.771.1.
Like some others I have had the problem of a boot loop when getting the Android 4.3 OTA after 2 minor updates which worked fine.
I have learned that this happened because my firmware is higher than the firmware of the OTA.
I was able to get out of the boot loop fine by flashing TWRP recovery and restoring to my TWRP backup of CyanogenMod, but I still want to go back to stock Sense.
I can't S-OFF as Sunshine is the only tool for HBOOT 1.61 and that won't work on CyanogenMod as it says that I need to be using stock. Also, I don't have the money to pay for it anyway.
So I'm wondering if anyone knows how I can get to stock Sense with all updates applied.
I was wondering if I could do a Guru reset again without performing updates, and then use a RUU of a more recent version to get to updated stock. I thought this may work because the version of the RUU would be higher than that of the current software.
Or would I get something from the HTC Dev Center downloads? Etc
Or is there another way?
Thanks for reading!
(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.771.1
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3786mV
(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
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=95916177934542817
Here's a RUU for you. It should work just fine
Poslano sa mog HTC One koristeći Tapatalk

donkeykong1 said:
Here's a RUU for you. It should work just fine
Click to expand...
Click to collapse
Thank you - so I flash this using TWRP then flash stock recovery using fastboot?

Zannxdaaccount said:
Thank you - so I flash this using TWRP then flash stock recovery using fastboot?
Click to expand...
Click to collapse
You flash it via fastboot in RUU mode. First command you need is "fasboot oem rebootRUU" That will boot your phone in bootloader mode ( black screen with silver HTC logo ). Then "fastboot flash zip (name of the zip).zip. You might want to rename that zip to something simple like "firmware" to avoid mistakes when writing in fastboot. And one mote note - you need htc fasboot to flash this, not the regular fastboot
Poslano sa mog HTC One koristeći Tapatalk

donkeykong1 said:
You flash it via fastboot in RUU mode. First command you need is "fasboot oem rebootRUU" That will boot your phone in bootloader mode ( black screen with silver HTC logo ). Then "fastboot flash zip (name of the zip).zip. You might want to rename that zip to something simple like "firmware" to avoid mistakes when writing in fastboot. And one mote note - you need htc fasboot to flash this, not the regular fastboot
Poslano sa mog HTC One koristeći Tapatalk
Click to expand...
Click to collapse
What is HTC fastboot and how do I get that?

https://www.androidfilehost.com/?w=...f812d4f8d7d551183257032e28f6937dd8bb61c6af2ca

donkeykong1 said:
https://www.androidfilehost.com/?w=...f812d4f8d7d551183257032e28f6937dd8bb61c6af2ca
Click to expand...
Click to collapse
C:\Users\\Desktop\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi

Zannxdaaccount said:
C:\Users\\Desktop\AndroidSDKSlim\android-sdk-windows\platform-tools>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
Put the fastboot.exe file in your regular fastboot folder. That should fix it. I forgot to write that, sorry

donkeykong1 said:
Put the fastboot.exe file in your regular fastboot folder. That should fix it. I forgot to write that, sorry
Click to expand...
Click to collapse
I had already done that. So there is the normal fastboot.exe that was already in there, and the htcfastboot.exe.

Zannxdaaccount said:
I had already done that. So there is the normal fastboot.exe that was already in there, and the htcfastboot.exe.
Click to expand...
Click to collapse
Try with "htc_fastboot flash zip..."

donkeykong1 said:
Try with "htc_fastboot flash zip..."
Click to expand...
Click to collapse
Alright, now on the command prompt it's saying flash zip complete but on my phone I've got the HTC silver logo with the green progress bar at about 80%, not moving by the looks of it?

Zannxdaaccount said:
Alright, now on the command prompt it's saying flash zip complete but on my phone I've got the HTC silver logo with the green progress bar at about 80%, not moving by the looks of it?
Click to expand...
Click to collapse
That's the way it should be. Now "htc_fastboot reboot" and wait till it finishes upgrading apps. Then set up, and enjoy

donkeykong1 said:
That's the way it should be. Now "htc_fastboot reboot" and wait till it finishes upgrading apps. Then set up, and enjoy
Click to expand...
Click to collapse
It's setting up apps now. Thank you very much!!

Zannxdaaccount said:
It's setting up apps now. Thank you very much!!
Click to expand...
Click to collapse
No problem mate. Glad I could help

Hi,
I have exactly the same issue, needing the same RUU. But the one linked to on android forums is corrupt. fastboot says it can't find the image title and if I open it in in WinRAR it fails the integrity test. I downloaded it three times and FC'd them. They are identicle but all corrupt. Is there another version out there or can you share one you've used? Thanks.

gunholio77 said:
Hi,
I have exactly the same issue, needing the same RUU. But the one linked to on android forums is corrupt. fastboot says it can't find the image title and if I open it in in WinRAR it fails the integrity test. I downloaded it three times and FC'd them. They are identicle but all corrupt. Is there another version out there or can you share one you've used? Thanks.
Click to expand...
Click to collapse
Don't try to extract a RUU zip, it will get corrupted because it's encrypted. Just download the zip, put it in your fastboot folder, and flash via fastboot with your phone in RUU mode

donkeykong1 said:
Don't try to extract a RUU zip, it will get corrupted because it's encrypted. Just download the zip, put it in your fastboot folder, and flash via fastboot with your phone in RUU mode
Click to expand...
Click to collapse
When I try to fastboot it I get an error
h ttp://imgur . com/a/cm8YL
I can't post images until I've posted more posts...
---------- Post added at 07:17 PM ---------- Previous post was at 06:58 PM ----------
I've tried that many things I forgot what I was meaning to show you. This is the error I get
C:\adbLink>htc_fastboot.exe flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420805_signed_.zip
sending 'zip'... (43287 KB) OKAY
sending time = 3.203 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 9(s)

My info is
C:\adbLink>htcfastboot2.exe 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.19.771.21
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(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!
Execution time is 69(ms)

C:\adbLink>htc_fastboot.exe flash zip PN07IMG_M7_UL_L50_SENSE60_MR_H3G_UK_7.19.771.1_Rad io_4T.35.3218.16_10.33Q.1718.01L_release_420805_si gned_.zip
sending 'zip'... (43287 KB) OKAY
sending time = 3.203 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 9(s)
Click to expand...
Click to collapse
gunholio77 said:
My info is
C:\adbLink>htcfastboot2.exe 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.19.771.21
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(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!
Execution time is 69(ms)
Click to expand...
Click to collapse
Your version-main is 7.19.771.21 so you need a RUU same or newer than that number. 7.19.771.1 will not work (its older). Unless you want to edit your version-main number from the /misc partition, the simplest is to flash the 7.19.771.21 RUU.
You can download it from here: https://www.androidfilehost.com/?fid=24052804347763965
There are some problems today on androidfilehost.com so if you have some issues downloading the file, try later :good:

I get the same failed message with that ruu - I've put cyangenmod back on for now, so I have a working phone. But I will return to this an get it working
Really appreciate your help with this - Thanks

HTC One M7 - Bricked?

Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ҟÀü«/륑-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(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:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!

Have you tried to flash stock recovery or RUU?

JB_ said:
Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ҟÀü«/륑-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(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:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Click to expand...
Click to collapse
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.

alray said:
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
Click to expand...
Click to collapse
Well as I want to remember it I don't think I have flashed a rom yet, I never got that far I just tried to flash twrp 2.8.4.0.
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.

JIMSHERIKO said:
Have you tried to flash stock recovery or RUU?
Click to expand...
Click to collapse
Well if I understand it right when I try to flash a RUU it just says unknown modelid and I think because it's corrupted or something. :/

JB_ said:
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
Click to expand...
Click to collapse
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.

alray said:
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
Click to expand...
Click to collapse
Ah so i need to get TWRP up and running for adb to work then.
Well looks like i got my awnser then. Thank you for your time!