Database Develop

[Q&A] [FIRMWARE] | [M7_UL] | [7.15.401.1] | Firmwares & HBoots

Q&A for [FIRMWARE] | [M7_UL] | [7.15.401.1] | Firmwares & HBoots
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [FIRMWARE] | [M7_UL] | [7.15.401.1] | Firmwares & HBoots. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I'm confused
in the first posting it is mentioned for the full stock, wipe zip's that they all need an additional rom to Flash afterwards....
what Kind of Rom is that and where can i get it....
on my htc one i installed the latest gpe Edition, but i dont like it so much so i want to go back to the latest sense Rom
and i dont know how to manage that
best regards
Martin

Handy-Muckel said:
in the first posting it is mentioned for the full stock, wipe zip's that they all need an additional rom to Flash afterwards....
what Kind of Rom is that
Click to expand...
Click to collapse
Well if you flash the 7.15.401.1 firmware then you probably want to flash a custom rom based on 7.15.401.1 software.
and where can i get it....
Click to expand...
Click to collapse
All roms can be found in the development sub forum
on my htc one i installed the latest gpe Edition, but i dont like it so much so i want to go back to the latest sense Rom
and i dont know how to manage that
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" but edit out the IMEI and Serialno before posting. You'll probably need to re-convert back to a Sense version using a RUU.

I hope you can help me ....my htc one is unlocked bootloader currently with hboot 1.57 so I was unable to make s-off ... ...
My question is ... can I upgrade the firmware to 7.15.401.1 of my m7 with s-on? There are some special way to update with s-on?
Thanks!!

Hello, thanks for the fast reply, here Comes the fastboot getvar all output
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------------
(bootloader) imei: 000000000000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.153s
Click to expand...
Click to collapse

emmanueldmc said:
I hope you can help me ....my htc one is unlocked bootloader currently with hboot 1.57 so I was unable to make s-off ... ...
My question is ... can I upgrade the firmware to 7.15.401.1 of my m7 with s-on? There are some special way to update with s-on?
Thanks!!
Click to expand...
Click to collapse
I have the same question.

kbal said:
I have the same question.
Click to expand...
Click to collapse
Me too have the same question

Handy-Muckel said:
Hello, thanks for the fast reply, here Comes the fastboot getvar all output
Click to expand...
Click to collapse
change your cid to HTC__001 and flash a x.xx.401.x ruu.
---------- Post added at 09:57 AM ---------- Previous post was at 09:45 AM ----------
emmanueldmc said:
1.57 so I was unable to make s-off ... ...
Click to expand...
Click to collapse
Why? Hboot 1.57 can be s-off'ed using Sunshine s-off.
My question is ... can I upgrade the firmware to 7.15.401.1 of my m7 with s-on? There are some special way to update with s-on?
kbal said:
I have the same question.
Click to expand...
Click to collapse
okkie said:
Me too have the same question
Click to expand...
Click to collapse
To flash a firmware on a S-ON M7 it must be:
A signed firmware (signed by HTC --> So an official firmware/not custom) to pass the bootloader signature verification
Higher (newer) version than what installed on the phone.
Your phone CID and MID must match the values in the android-info.txt file of the firmware (to pass the bootloader header check)
If you are asking this question, then (no offense) you are probably not ready to start messing with firmwares yet, remember you can brick your phone forever when flashing firmware incorrectly when s-off. S-ON will save your phone to be bricked from a bad firmware flash.

ok... it worked for me i'm back to sense.
many thanks.....
Martin

I tried flashing an FUU. My PC connects and recognizes my phone fine when in the OS and when in Fastboot.
I started the FUU, went through the Welcome screen and instruction screen. The Verification screen went through, I chose to update and went through the next confirmation screens...and the process started.
My phone rebooted to a black screen with the greenish HTC logo, and my PC showed the progress stuck at 2%..."waiting on bootloader" I think was the message. I sat there at 2% for 20 minutes. In finally pressed and held the power button on the phone until it rebooted. It rebooted fine...all is still as it was before I attempted flashing the FUU.
Any ideas on why it hung up at 2%? Any suggestions?
Sent from my HTC One using Tapatalk

Does this need S-off M7?
I have just updated my M7 to 5.0.2

Hello i was trying to flash the full version but i got this:
C:\HTC\ADB Drivers_Updated>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
C:\HTC\ADB Drivers_Updated>fastboot flash zip 7.19.401.2-FULL_STOCK_WIPE.zip
sending 'zip' (551346 KB)...
OKAY [ 22.759s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 24.331s
C:\HTC\ADB Drivers_Updated>fastboot flash zip 7.19.401.2-FULL_STOCK_WIPE.zip
< waiting for device >
target reported max download size of 1514139648 bytes
sending 'zip' (551346 KB)...
FAILED (status read failed (Too many links))
finished. total time: 92.300s
C:\HTC\ADB Drivers_Updated>fastboot flash zip 7.19.401.2-FULL_STOCK_WIPE.zip
^C
C:\HTC\ADB Drivers_Updated>
Click to expand...
Click to collapse
I can execute some comands like : C:\HTC\ADB Drivers_Updated>fastboot devices
HT35VW908752 fastboot
but not commands like: getvar all (it frezes and i have to Cntl+c to stop it)
I dont know if i should try to try to continue the proces or try to downgrade it.
Any help will be extremely appreciated

anyone have baseband: 4T.35.3218.16 flashable zip in recovery?bcause mine S-ON

MID and CID not listed
H, first of all thanks to the excellent job you all are doing to keep Android fun. Sorry I am android noob, currently I am running ViperOne 7.0.2 with TWRP. I want to move to Viperone 8.0 so went ahead and made S-OFF in my HTC One M7 device. I am in India and the device was purchased locally. I tried to flash the firmware as per the instructions in the OP but got "Error 41" first for MID and then for CID. I changed the android-info.txt for MID and it worked but when i added CID it gave me "24 error parsing android-info". Is it safe to add CID and MID and flash firmware, does it mean this firmware is not meant for my device/country?
My vars
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.106
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Modern TWRP Backup for CID: TELUS001

Hi everyone,
I have come across a friend's phone which is stuck in a bootloop since the battery died during an update. I am unable to run the Telus RUU (the only one I can find, from the collection thread, and it's very old). The RUU fails and I can not flash the zip from it manually using fastboot either. I can restore the TWRP backup from the collection but then the touch screen doesn't work (the backup must be much older).
So I am hoping someone on here has or can make me a TWRP backup of their latest stock HTC/Telus setup?
I am also going to see if I can get S-OFF and SuperCID so that I can try other RUUs. Thought that finding a backup would be a lot simpler/safer, though.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.661.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4231mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks!

There is a 7.17.661.7 RUU for Telus here. To use this RUU, the phone firmware must be at least 6.xx.661.x and not newer than 7.17.661.7. Read instructions how to flash the RUU in the OP (you must use htc_fastboot to flash it, not the normal fastboot). Post the output of "fastboot getvar all" (remove imei and serialno) if you need more help.

Thanks! I don't have the phone near me at the moment to get the vars however I do know that fw is 5.xx.661.x range

I've added the getvar output. Since it's not my phone I am trying to avoid S-OFF using Sunshine. Didn't think it would be so difficult to find an RUU or TRWP backup

Try the 7.17.661.7 ruu, it might work since the phone is already on hboot 1.57. Otherwise you'll need s-off to either update your firmware and flash this ruu or downgrade your hboot and flash the 4.19.661.8 ruu.
I might be able to provide you a nandroid backup of 5.11.661.8 if I have some spare time. I will need to flash the the 4.19.661.8 ruu on my phone, update it to 5.11.661.8 so I can make a backup and upload it for you. But I won't have the time to do it this week...

Thanks I'll give it a shot. I was hesitant since I heard that jumping more than 1 firmware version could be bad.. but I'll see what happens and let you know.

This firmware thing does not apply to ruu, only apply to firmware update extracted from ota updates . In the worst case, the pre check will fail and nothing will be flashed on the phone

I finally had a chance to try this out and the 7.17.661.7 RUU fails to flash. Guess I'll have to S-OFF.
C:\Users\ryan\Downloads\HTC One M7>htc_fastboot flash zip "C:\Users\ryan\Downloads\HTC One M7\TELUS ROMs\7.17.661.7 (RUU Zip)\PN07IMG_M7_UL_L50_SENSE60_MR_TELUS_WWE_7.17.661.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420202_signed.zip"
sending 'zip'... (43286 KB) OKAY
sending time = 2.633 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 8(s)

Well if you can s-off this phone it will be indeed possible to flash the ruu after updating the firmware.

Model id check fail while trying to flash new firmware

I'm trying to flash 7.19.401.22 firmware with no red text, & I've also tried 7.19.401.2 with the same result.
S-OFF, cid: 11111111, model id: PN0720000.
Current ROM/Kernel: ViperOne 9.0/ElementalX 19.2.
Have tried on Windows 10 and WinXP
C:\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (29678 KB)...
OKAY [ 2.334s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.750s
C:\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.096s
Thanks for any help. I've tried searching but no answers for my particular situation(correct cid/model id)

Wls is Sprint phone. You can't flash WWE firmware on Sprint phone. Also, WWE mid is PN0721000, that's why you're getting modelid error

aSilvrHaze said:
I'm trying to flash 7.19.401.22 firmware with no red text, & I've also tried 7.19.401.2 with the same result.
S-OFF, cid: 11111111, model id: PN0720000.
Current ROM/Kernel: ViperOne 9.0/ElementalX 19.2.
Have tried on Windows 10 and WinXP
C:\sdk\platform-tools>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (29678 KB)...
OKAY [ 2.334s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.750s
C:\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.096s
Thanks for any help. I've tried searching but no answers for my particular situation(correct cid/model id)
Click to expand...
Click to collapse
Good thing it did not worked. You have a M7_WLS (PN0720000) variant and you are trying to flash a M7_UL (PN0710000) firmware on it. Flashing a M7_UL firmware on your phone will brick it. Fortunately the MID check failed and it did not happened. Be extra careful when flashing files on a s-off phone. You want to flash files that are compatible with M7_WLS (Sprint HTC One) only, better to visit the Sprint HTC One forum. The sprint HTC One is a CDMA phone not the same as the GSM variant of this forum.

alray said:
Good thing it did not worked. You have a M7_WLS (PN0720000) variant and you are trying to flash a M7_UL (PN0710000) firmware on it. Flashing a M7_UL firmware on your phone will brick it. Fortunately the MID check failed and it did not happened. Be extra careful when flashing files on a s-off phone. You want to flash files that are compatible with M7_WLS (Sprint HTC One) only, better to visit the Sprint HTC One forum. The sprint HTC One is a CDMA phone not the same as the GSM variant of this forum.
Click to expand...
Click to collapse
and after checking the sprint section, i feel like a dummy. I just upgraded to Viper 9.0, noticed a few bugs and someone mentioned latest firmware, & my search pulled up non sprint firmwares, should have known better, thanks for pointing it out.

aSilvrHaze said:
and after checking the sprint section, i feel like a dummy. I just upgraded to Viper 9.0, noticed a few bugs and someone mentioned latest firmware, & my search pulled up non sprint firmwares, should have known better, thanks for pointing it out.
Click to expand...
Click to collapse
Afaik, the latest sprint firmware is 6.23.651.7, the one currently installed on your phone is 6.23.651.6 so its not really old and should work fine imo. Since ViperOne is said to be compatible with sprint variant since version 8.0 it should work fine your phone. Make sure to flash it using the recommended recovery version (if any) and also that you are using a sprint compatible recovery to flash it, like twrp for sprint.
Otherwise it might only be some bugs not corrected yet by the dev, might worth reading the discussion and q&a section of the ViperOne to see if anyone is having the same bugs and finally asking in the rom thread.
Good luck :good:
Btw if you want to update the firmware, you can use the 6.23.651.7 RUU from htc website: http://www.htc.com/us/support/rom-downloads.html
Remember that flashing a ruu will wipe everything from your phone, you'll have to reflash the custom recovery + custom rom after. Don't forget to backup your important data before flashing the RUU

Can't find any ROM stock to make SunShine works [HBOOT=1.61][CID=VODAP203]

Hello everybody,
Usually I used to find solutions through forums on Internet but riht now I'm completely stuck. I have spent few days to find how to come back with an official HTC ROM for my HTC One m7, but for several reasons it does not work and I can't find how to deal with.
Here some intel to help your analysis :
(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:
(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: VODAP203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1e7eeb73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
HBOOT version = 1.61
SunShine does not work because it asks a ROM closer to a stock one.
Can you please help me to find a way to get that Official ROM ? I guess I need to S-OFF before and to downgrade HBOOT and change my CID, but I don't find the solution with my situation.
Many thanks !!
Have a good day.

I found a cwm nandroid backup but it's CID VODAP102:
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-vodap102-1-29-161-7-7z/
it should work, but you'll probably have to apply ota updates before running sunshine. Oh, and you need to flash clockwork mod recovery.
let's see what @alray has to say about it. He's our heavy artillery here Wait for his response before you use that nandroid.

Hi monrokhoury,
Many thanks for your answer !
I already have cwm, while unlocking my hboot.
I should install it like a common .zip folder from cwm then Gapps .zip ? Then the same for OTA ?
I'll wait for the strike in response from the artillery then
Thank you !
Have a good day

You're welcome.. And Nope, you can't flash a nandroid backup like you would a regular zip. It could harm your device.
You need to unpack the contents into cwm default backup directory. try making a backup them look for it and you should find yourself in the default backup folder. delete the backup you just made and then unpack the nandroid backup in the above link into that folder. Boot into recovery, select backup and restore then restore, navigate to the nandroid backup you just copied and confirm the restore.
---------- Post added at 02:50 PM ---------- Previous post was at 02:44 PM ----------
Oh, and before you do anything backup all your valuable data and files, they will be wiped during the restoration process.
---------- Post added at 02:52 PM ---------- Previous post was at 02:50 PM ----------
One last PS: You don't need to (and shouldn't) flash any gapps.. They're included in the backup.

monrokhoury said:
I found a cwm nandroid backup but it's CID VODAP102:
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-vodap102-1-29-161-7-7z/
it should work, but you'll probably have to apply ota updates before running sunshine. Oh, and you need to flash clockwork mod recovery.
let's see what @alray has to say about it. He's our heavy artillery here Wait for his response before you use that nandroid.
Click to expand...
Click to collapse
Vodap102 is a x.xx.161.x base. Vodap203 is x.xx.163.x. So this cwm backup is not for this phone. OP's phone is hboot 1.61 so his firmware is 7.xx.163.x, your cwm backup is way to old, if he flash this, his touch screen won't even work.
Flash the 7.xx.163.2 ruu from the ruu thread in the general section, you'll possible have to follow the guide at the end of post #2 of that same thread if you were on a newer version than 163.2. S-off not required.
Sent from my HTC One using XDA Labs

Whoaoh , thanks alray,
Looks like what I was looking for, an entire thread dealing with my situation all along.. Moreover, you put explanations, for once I will do things knowing what I do and why. Good job, thanks for newbies like me :fingers-crossed:.
I've read a bit, I will try it comfy at home but it sounds good. Have I to be careful with the type of the version-main I choose ? The 7.xx163.xx has no url though I will need to do as you explain at the bottom of your post with another version.
I'll keep you posted soon.
Have a good evening.

I think this is the ruu alray means:
https://www.androidfilehost.com/?fid=95916177934554131
You know how to flash a ruu zip?
reboot fastboot, connect your m7 to your pc, fastboot oem rebootRUU, fastboot flash zip ruu.zip, fastboot flash zip ruu.zip, and finally fastboot reboot

Hello,
I did exactly what was indicated in the thread, both for version-main and RUU flashing, but I still have the same ROM with Android 6 and it seems that nothing has changed.. is it normal ? should it not be back to lollipop ?
But the version-main changed successfully !
What would I have done wrong ?
Thanks to both of you for your help !
Have a nice day !

wakeo said:
Hello,
I did exactly what was indicated in the thread, both for version-main and RUU flashing, but I still have the same ROM with Android 6 and it seems that nothing has changed.. is it normal ? should it not be back to lollipop ?
But the version-main changed successfully !
What would I have done wrong ?
Thanks to both of you for your help !
Have a nice day !
Click to expand...
Click to collapse
Was the ruu flash successful? I don't think so... Reflash the ruu and copy paste your commands window here so we can see what's wrong
Sent from my HTC One using XDA Labs

Ok, I will do it.
I remember one thing which could be a possible clue : when I relocked the Hboot, I remember that something went wrong. But the phone showed to be relocked, though I continued.
I'll keep you posted. Many thanks for your help !

Hello alray,
Actually I did not take the good RUU, sorry for that. Then I have flashed the good RUU given by monrokhoury. But right now, my phone is stuck with the HTC logo and the green loading bar almost at the end.
I copy/paste the commands until all the text given by the flash RUU :
Microsoft Windows [version 10.0.10586]
(c) 2015 Microsoft Corporation. Tous droits réservés.
C:\Users\**>cd AppData\Local\Android\sdk\platform-tools
C:\**\Android\sdk\platform-tools>adb reboot bootloader
C:\**\Android\sdk\platform-tools>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.163.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP203
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1e7eeb73
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.079s
C:\**\Android\sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (Invalid argument))
finished. total time: 1.149s
C:\**\Android\sdk\platform-tools>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 32(ms)
C:\**\Android\sdk\platform-tools>htc_fastboot flash zip RUU.zip
sending 'zip'... (43287 KB) OKAY
sending time = 2.852 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) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAIL90 hboot pre-update! please flush image again immediately
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
For "hboot-preupdate" response, restart the same procedure for device FA3CAW903233...
sending 'zip'... (43287 KB) OKAY
sending time = 2.855 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
etc...
Click to expand...
Click to collapse
Then what should I do with that stuck situation ?
Thanks !

Ah ! I did it dude.
I just reboot bootloader and re-unlocked the hboot.
The system had a first weird error / failed boot, but the second try was successfull.
I'm now with this new ROM which works fine apparently. I needed it to recover my online htc recovery. Now next step, s-off to change the CID (I guess you made a post about it, I'll try to find it) and flash another ROM with last android version. Any advice ?
Many thanks for your help !
Have a good evening.

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