Develop Bugs

[Q] Need to flash firmware and radio

Hey,
I need to flash firmware and radio.
I am on ARHD 7 with PhilZ Touch 6.
Since i upgraded to ARHD 7 i've got very bad radio connectivity.
I've been browsing the forums to search for a firmware and radio file for my modelID and CID. I am unable to find them.
*** TAMPERED ***
*** UNLOCKED ***
M8_UL PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.15.2133156.UA13G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
Are there any files around that i can use?
I am kinda lost in the process...
Thanks in advance,

I've been thinking of going back to stock to get the latest update and then go back to ARHD! But i need some confirmation on this.
I am learning/reading myself into the getting back to stock procedure using the guide mike refers to in his ARHD post. ( http://forum.xda-developers.com/showthread.php?t=2265618 )
I have to go by the first method i guess, since method 2 and 3 are a no go. Can't find the RUU needed for method 2. And the nandroid backup i had done before flashing custom recovery and rom got deleted once all that worked fine!
So...
I've downloaded the following as mentioned in the guide. ( http://android-revolution-hd.blogspot.nl/p/android-revolution-hd-mirror-site-var.html )
- Download stock odexed 1.54.4015
- Download stock recovery 1.54.401.5
Procedure should be as below, if i am correct.
1. Place (One_M8_1.54.401.5_odexed.zip) file on virtual SDCard.
2. Get (recovery.img) file from Flash_recovery_1.54.401.5.rar and place it in fastboot folder. -- Or should i unrar the whole package and run the batch file as step 4.!?
3. Boot device in recovery, install zip (One_M8_1.54.401.5_odexed.zip) file.
4. Reboot device in bootloader, use cmd <fastboot flash recovery recovery.img>
5. Relock bootloader, use cmd <fastboot oem lock>
6. Reboot device? Get updates etc...

Any feedback please...? I am kinda worried I **** things up!

Above worked, no OTA though... Kept searching for updates, unlocked bootloader tried again and said there are no updates available.
So dumb that i've deleted the stock nandroid backup!
Guess i'll never really find out what version I originally had.

HTC One (M7) stuck in bootloader (Tampered, Relock, S-ON) - Please help!!

This thread is related to another thread that I posted a few months ago. Sorry for reopening just didn't know what to do since it is an old thread.
Before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3819mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
CURRENT STATE:
VZW Htc One (m7) *** TAMPERED ***, ***RELOCKED*** S-ON
This all started when using revone with a different firmware/hboot then the tutorial I was watching.
Any ideas at all before I quit completely?

HunterT said:
This thread is related to another thread that I posted a few months ago. Sorry for reopening just didn't know what to do since it is an old thread.
Before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3819mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
CURRENT STATE:
VZW Htc One (m7) *** TAMPERED ***, ***RELOCKED*** S-ON
This all started when using revone with a different firmware/hboot then the tutorial I was watching.
Any ideas at all before I quit completely?
Click to expand...
Click to collapse
Can you boot into a rom? You are on 1.56 so if you can, you will be able to use firewater to get back to s-off.
If you can't boot up.......idk you might be screwed, not sure there is a signed RUU available for hboot 1.56.
To send back to verizon you should have flash an RUU, then switched back on locked and s-on after the RUU. Not taking any updates so you can redo the s-off if needed.
If you can't boot up from where you are at, you might be screwed, short of getting someone with a java card to crack it.

HunterT said:
This thread is related to another thread that I posted a few months ago. Sorry for reopening just didn't know what to do since it is an old thread.
Before I started doing anything my phone had Cyanogen Mod on it. I have to return it back to Verizon within 5 days so I am trying to get it completely back to stock. I was following tutorials on how to LOCK the bootloader and turn S-ON. I ended up in the bootloader and there is no chance of starting the phone. I downloaded a couple of RUUs and tried flashing them from fastboot and the signature check fails because of S-ON most likely. Can someone please give me a short guide on how to get out of this whole mess and the proper order of how to do things. Unless someone knows where I can find a RUU that will pass signature check with S-ON.
Currently my bootloader screen looks like this:
*** TAMPERED ***
*** RELOACKED ***
*** Security Warning ***
S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3819mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
CURRENT STATE:
VZW Htc One (m7) *** TAMPERED ***, ***RELOCKED*** S-ON
This all started when using revone with a different firmware/hboot then the tutorial I was watching.
Any ideas at all before I quit completely?
Click to expand...
Click to collapse
Screwed man. Java card. Jtag. . Wait eternally for a signed encrypted ruu.
Sorry. S on and locked on vzw is not good

If you download the latest RUU posted in the development section and you can use a cool tool called ruuveal to recrypt it if you need to RUU your device without having s-off.

synisterwolf said:
If you download the latest RUU posted in the development section and you can use a cool tool called ruuveal to recrypt it if you need to RUU your device without having s-off.
Click to expand...
Click to collapse
Unfortunately that won't work.
As 're-encrypting it will not create the HTC signatures required for flashing to an s-on device.

santod040 said:
Unfortunately that won't work.
As 're-encrypting it will not create the HTC signatures required for flashing to an s-on device.
Click to expand...
Click to collapse
Removed by request.
Sent from my iPhone 5s using Tapatalk pro

synisterwolf said:
Actually the tool injects the signature during the encryption process and works as intended. I've done this a few times on a HTC One, Fireball, Max, thunderbolt, and sonic.
I will not post the re-encrypted file on xda due to other members being hit with DCMA takedowns and its against XDA rules.
Spoiler:
Google search will find what I've done and any user with a Linux machine can duplicate what I've posted above. That's all I will be saying on the subject so I don't jeopardize my ability to stay on this site.
Sent from my iPhone 5s using Tapatalk pro
Click to expand...
Click to collapse
Hmm, last I checked it wasn't able to re-create HTC's RSA signatures.
But that's very cool that you have been able to do so.
I think at the very least, that you would have to start with an actual RUU though, not just a zipped up dump of partitions, as is the kk ruu we currently have. Maybe I'm wrong.
But since that wasn't an actual RUU to begin with, you are saying the tool creates an HTC signature on its own?
Last I knew, the creator posted this regarding signatures:
The leading 256 bytes is the signature of the zip file, you'll need to disregard it. There's no way we can sign the zip correctly without HTC's private key.
The differing 5 bytes are the bytes I talked about.
The trailing bytes are probably a bug - I'll investigate further when I get some time but it's not a priority since it's not causing HBOOT to fail to flash the zip.
Thanks for the detailed analysis/comparison :+1:
I'm going to merge the encrypt branch onto the master branch in the next few days since it seems to be working okay.
Click to expand...
Click to collapse
Not in any way trying to argue or anything like that, just honestly didn't think it was possible to replicate an HTC signature,.
If I'm wrong, then that's great!

[Q] Stock M7 Bootlooping-Unable to boot recovery

OK, I've been scouring the web for the entire day. (devoted my Sunday to resolving this issue and have failed.)
I have received a Verizon HTC One M7. My wife wants to use it as her daily.
It's completely stock. Locked bootloader, S-on, stock ROM, Stock recovery.
Here's the issue:
Loading the ROM it bootloops the white HTC logo. Booting recovery it does the same. Trying to Factory Reset gets the same results.
I can access the bootloader and engage fastboot and my PC detects the phone fine but I am not able to Unlock the bootloader. i believe this to be because of the Hboot version.
can't boot to ROM and can't unlock bootloader means I can't achieve S-off, therefore I can't flash a custom recovery to enable me to flash a custom ROM.
I'm not looking to necessarily have the phone unlocked, S-off and rooted. (That would be nice but not a priority)
I would be happy with it being all locked and stock IF IT WAS SIMPLY USABLE. My wife currently has a Samsung SGS4 she started using after she broke her HTC DNA. She doesn't like it and wants to go back to HTC desperately.
I would be happy to simply restore the stock recovery and ROM so that she can use it and I can have my Sundays back.
HELP!!!!
Here is the fastboot getvar all. Any suggestions are greatly appreciated.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.605.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA43JS905180
(bootloader) imei: **************************
(bootloader) meid: ***************************
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

NFSP_SMD said:
OK, I've been scouring the web for the entire day. (devoted my Sunday to resolving this issue and have failed.)
I have received a Verizon HTC One M7. My wife wants to use it as her daily.
It's completely stock. Locked bootloader, S-on, stock ROM, Stock recovery.
Here's the issue:
Loading the ROM it bootloops the white HTC logo. Booting recovery it does the same. Trying to Factory Reset gets the same results.
I can access the bootloader and engage fastboot and my PC detects the phone fine but I am not able to Unlock the bootloader. i believe this to be because of the Hboot version.
can't boot to ROM and can't unlock bootloader means I can't achieve S-off, therefore I can't flash a custom recovery to enable me to flash a custom ROM.
I'm not looking to necessarily have the phone unlocked, S-off and rooted. (That would be nice but not a priority)
I would be happy with it being all locked and stock IF IT WAS SIMPLY USABLE. My wife currently has a Samsung SGS4 she started using after she broke her HTC DNA. She doesn't like it and wants to go back to HTC desperately.
I would be happy to simply restore the stock recovery and ROM so that she can use it and I can have my Sundays back.
HELP!!!!
Here is the fastboot getvar all. Any suggestions are greatly appreciated.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0421
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.605.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA43JS905180
(bootloader) imei: 990004297058814
(bootloader) meid: 99000429705881
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You could try finding the ota zip for 4.10.605.3. NOT the newest one. Do NOT use the new one. When you get the ota zip you can pull the firmware.zip out of that. Put it in your working fastboot directory
Then do
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Repeat the previous command if it tells you to flush immediately
Fastboot reboot

dottat said:
You could try finding the ota zip for 4.10.605.3. NOT the newest one. Do NOT use the new one. When you get the ota zip you can pull the firmware.zip out of that. Put it in your working fastboot directory
Then do
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Repeat the previous command if it tells you to flush immediately
Fastboot reboot
Click to expand...
Click to collapse
OK upon finding an OTA zip that I thought would work, I pulled the firmware.zip and flashed. It appeared to go fine.
I did have to repeat the flash zip command but it completed with no errors.
However, phone still bootloops. Still cannot access recovery.

M8 is broken?

Hey folks!
A friend of mine sent me his smartphone to repair but i'm sitting in a corner right now...
I never had a HTC before, not in my hands, not received by any other person - first try so far.
Here's the situation:
The battery from the smartphone was empty over a night.
Next day, when he want to start - it doesn't start and runs into bootloader.
He tried some things i think, but isn't really familiar with that.
The phone said in bootloader:
*** Software status: Modified ***
*** UNLOCKED ***
S-ON
For now i followed this tutorial "htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/".
I already received the "Unlock_code.bin" and uploaded to the phone - seems working, because it says "Unlocked".
After that i flashed the "openrecovery-twrp-2.7.0.2-m8.img" - seems working, because it says "OKAY".
Than, i erased the cache, try to enter recovery, but it returns immediately to bootloader. :crying:
What i've done wrong?
Any hints what happens with the phone? How can i restore to stock easily?
He don't need special tools or anything else, just a working phone so far

ambiente1 said:
Hey folks!
A friend of mine sent me his smartphone to repair but i'm sitting in a corner right now...
I never had a HTC before, not in my hands, not received by any other person - first try so far.
Here's the situation:
The battery from the smartphone was empty over a night.
Next day, when he want to start - it doesn't start and runs into bootloader.
He tried some things i think, but isn't really familiar with that.
The phone said in bootloader:
*** Software status: Modified ***
*** UNLOCKED ***
S-ON
For now i followed this tutorial "htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/".
I already received the "Unlock_code.bin" and uploaded to the phone - seems working, because it says "Unlocked".
After that i flashed the "openrecovery-twrp-2.7.0.2-m8.img" - seems working, because it says "OKAY".
Than, i erased the cache, try to enter recovery, but it returns immediately to bootloader. :crying:
What i've done wrong?
Any hints what happens with the phone? How can i restore to stock easily?
He don't need special tools or anything else, just a working phone so far
Click to expand...
Click to collapse
That recovery version is very outdated. You were using an old tutorial.
If it were me, I'd find an RUU to run. What do you get from fastboot getvar version-main? Or better yet, post the results of fastboot getvar all minus the IMEI and serial#, and someone can direct you to the proper RUU

fastboot getvar version-main
version-main: 1.16.401.10
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.16.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ******************
(bootloader) imei: ******************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8ql_ul
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PKV10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 1d456ef7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
Click to expand...
Click to collapse

ambiente1 said:
fastboot getvar version-main
fastboot getvar all
Click to expand...
Click to collapse
There's your problem. You don't have the M8. You have the M8S. The M8 recovery won't work on that.
The M8S has a separate forum here, and you can find the proper TWRP recovery for it in this thread.
You do have very old firmware though. Hopefully that recovery version will work as it is made for newer firmware. I think it will.

M8 stuck on bootup Security warning... Cant find correct RUU

Hi all,
I have an old HTC one m8 which was working fine when I stored it away last year. Today I tried to turn it on and found myself looking at safe mode menu with the heading
"Software status: Modified"
LOCKED
Security Warning
Now I have been going through the form for the last couple of hours trying different things but they dont seem to work.
e.g) I got a ver 4.20 RUU for my phone mentioned in this link
https://forum.xda-developers.com/htc-one-m8/help/finding-ruu-t3283633
but that does not work because my phone currently is on OS-6.13 and apparently I can not downgrade to OS-4 while my phone is S-ON. (I get ERROR 159 IMAGE ERROR)
So i tried to make it S-OFF. Unfortunately from what I have read they only way to do that is through the adb tool which does not work in the fastboot mode I am currently stuck on (fastboot commands work fine from my PC). So I can't downgrade to the only RUU I have found for my modelid and cid. I have no idea how to proceed now.
my phone specs
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any ideas?

mezomizz said:
apparently I can not downgrade to OS-4 while my phone is S-ON. (I get ERROR 159 IMAGE ERROR)
Click to expand...
Click to collapse
Correct. Downgrading is not allowed with s-on.
mezomizz said:
So i tried to make it S-OFF. Unfortunately from what I have read they only way to do that is through the adb tool which does not work in the fastboot mode I am currently stuck on (fastboot commands work fine from my PC).
Click to expand...
Click to collapse
There is no (current) valid method to s-off using adb. If you are talking about firewater, that method has not worked since 2014, and nothing you do will make it work.
The valid current method to s-off is with sunshine app ($25 US) but also requires a working OS.
You also do not need s-off to get the phone working again. Since a Marshmallow version RUU for your CID/MID is not available, you can restore the stock TWRP backup from the collection in the link below: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Unlock bootloader using HTCDev.com, install custom recovery TWRP, then restore the TWRP backup 6.13.206.5 using the instruction in the link above.