Develop Bugs

Can executable RUUs be used to downgrade?

There's something that I'm a bit unclear on when it comes to RUUs
Let's say that I'd like to try out the latest Marshmallow release without waiting for the OTA and use the HTC-provided RUU .exe (3.35.617.12)
I'm on a T-Mobile branded M9 and would like to keep WiFi Calling and Visual Voicemail. If I find that I am unable to use these features in the non-branded HTC MM release, will I simply be able to use the T-Mobile branded RUU .exe (2.11.531.19) to revert back or will I be unable to as it's an older version (Android 5.1)
I'm currently still locked and S-ON
I seem to remember downgrades not being possible on my M7 once the hboot was updated to a newer version, but am a bit confused about the specifics of the M9
Thank you, and my apologies if this is a dumb question -- I've done my best to find an answer through searching

You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.

But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)

asestar said:
You cannot flash RUU that does not match your device variant. In this case, you would need 3.35.531.xx RUU, to try marshmallow. 3.35.617.xx won't install on your phone, unless you S-off and change the variant CID.
Click to expand...
Click to collapse
Well, now I'm a bit confused as far as variants are concerned. This HTC release page states
This software upgrade comes in the form of two sequential updates. The first update will install software version 2.11.617.180 , which does not include the Android OS upgrades. The following update will install software version 3.35.617.12 , which includes the changes to the Android OS.
Click to expand...
Click to collapse
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Flippy498 said:
But once your phone is S-OFF then you are able to downgrade, too. (Although it doesn't matter whether you use a RUU.zip or a RUU.exe.)
Click to expand...
Click to collapse
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
(bootloader) kernel: lk
(bootloader) product: htc_himaul
(bootloader) version: 1.0
(bootloader) imei: REDACTED
(bootloader) version-main: 2.11.531.19
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440601_86.09.50731G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA12000
(bootloader) cid: T-MOB010
Click to expand...
Click to collapse

Miguel_Lancaster said:
Am I correct in understanding now that the '617' portion of those two versions is what indicates the device variant? And that my device's variant is '531'?
Click to expand...
Click to collapse
Correct. 617 is the SKU for the unlocked/developer edition and 531 belongs to T-Mobile US.
Miguel_Lancaster said:
So then it appears that the only ways for me to try out Marshmallow at this point would be:
1) Wait until HTC/T-Mobile unleash their official release and update via OTA or RUU
2) Unlock my bootloader, flash TWRP, and install whatever ROM I please
3) Unlock bootloader, S-OFF, and RUU as I please
Click to expand...
Click to collapse
1) Correct.
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Miguel_Lancaster said:
And so long as I'm S-OFF I could use this particular T-Mobile RUU executable to revert back to stock at any point and then re-lock my bootloader, correct? But as long as I'm S-ON, then downgrading is not an option, even using an RUU of the '531' variant?
Click to expand...
Click to collapse
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)

asestar said:
2) You can't flash Android M Sense roms when your phone is using the Android L firmware. So you need to look for the Android L versions of the roms (e.g. ARHD 14.0 or Viper 3.5). Sense-less Android M roms like CM should be fine, though.
3) Correct.
Click to expand...
Click to collapse
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
asestar said:
Correct (both times). Although you should keep in mind that your phone will bootloop if it's not 100% stock and you lock or relock the bootloader. (I personally think there is no benefit in locking/re-locking or even setting S-OFF back to S-ON unless you want to send your phone to HTC for warranty claims.)
Click to expand...
Click to collapse
Phone was just purchased used, so if there's any warranty period left it probably isn't for very much longer. In the past I've gone S-OFF for all my HTC devices (Incredible, then One S, then One M7) but they've always seemed to have their own unique quirks and this M9 appears to be no different.
My main reasoning for staying S-ON/Stock at the moment is just in case I find a reason to return the device to the seller. After a few days when I'm sure everything is alright with it, I'm sure I'll be less reluctant to tweak.
Is a bootloop easily fixable?
So, to clarify (again!) --
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Thanks a bunch for your responses. I'm sure this stuff gets answered all the time, but it can sometimes be difficult to find a specific answer in the depths of these boards. Plus, I find it hard to keep 100% on all development when I only buy a new device every couple of years.
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.

Miguel_Lancaster said:
Hmm, and here I was thinking that ROMS included the firmware and both could be flashed through TWRP. Guess I was mistaken. Or...
Click to expand...
Click to collapse
The difference between rom and firmware.
Miguel_Lancaster said:
Is a bootloop easily fixable?
Click to expand...
Click to collapse
Just reflash a RUU. The problem for most non-US firmwares is that HTC doesn't provide RUUs so sometimes there is no freely accessible RUU for a specific firmware version. (The only other method besides flashing a RUU is restoring a TWRP backup or re-/flashing a custom rom which needs an unlocked bootloader and TWRP.) If someone decides to re-S-ON and to lock/relock and the rom doesn't boot then that person might not be able to fix that bootloop without this RUU service. (The same applies to S-ON users who decide to relock if the rom doesn't boot.) HTC introduced a new security feature with Android 5.1 (firmware 2.x and higher). It prevents the bootloader unlock if the option OEM Unlock isn't activated in developer options. That's why I recommend everyone staying S-OFF and unlocked unless you need to send your phone back to HTC for a warranty claim since even OTAs can be installed with an unlocked bootloader. Well, RUU.exe deny to flash with S-ON and an unlocked bootloader but there are not many RUU.exe for non-US firmware versions and you can always extract the RUU.zip from a RUU.exe. (RUU.zip files can be flashed via an external SD card even if the bootloader is unlocked.)
Miguel_Lancaster said:
In my phone's current state, I would be limited to Lollipop ROMs when flashing via TWRP?
Click to expand...
Click to collapse
Correct if you're talking about Sense roms.
Miguel_Lancaster said:
So then, the shortest route to flashing custom Marshmallow ROMs would be to S-OFF and then RUU to an International Marshmallow firmware? Would I need to change CID manually or is that handled during RUU so long as I'm S-OFF?
Click to expand...
Click to collapse
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem writemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BS_US002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Miguel_Lancaster said:
And the safest route (in which S-OFF would be completely optional) would be to wait for the T-Mobile OTA release for Marshmallow before unlocking the bootloader and flashing TWRP?
Click to expand...
Click to collapse
Correct.
Miguel_Lancaster said:
I used the ARHD rom on my last device and quite liked it, but there was a T-Mobile specific variant that kept WiFi calling and all the other carrier-specific stuff. I'm pretty sure the developer has since long given up on maintaining those features., but it's my understanding that ViperOne may still have them.
Click to expand...
Click to collapse
Don't know about ARHD but Viper has that feature.
Btw: Getting S-OFF is quite easy but it costs 25 USD. You simply need to use the Sunshine App. (Or you look for someone who has a java card.)

Thank you for taking the time to answer all of my questions.

No problem. Maybe those detailed answers might help other users as well. (That's at least what I hope. )

Flippy498 said:
Or you use an unlocked/dev edition RUU. There is no big difference between the firmware of those two M9 versions. Nevertheless you need to change both the CID and the MID. The commands are fastboot oem writecid <enterwhicheverCIDisneeded> and fastboot oem changemid <enterwhicheverMIDisneeded>. (SKU 617 - unlocked/dev edition - CID: BSUS_002 - MID: 0PJA11000; SKU 401 - international version - CID: HTC__001 - MID: 0PJA10000; SKU 531 - T-Mobile US - CID: T-MOB010 - MID: 0PJA12000)
Click to expand...
Click to collapse
**** --
I changed my MID to the Developer edition, but I accidentally used the letter O and not the number 0 -- so OPJA11000
Then I attempted an RUU and now my phone is stuck in the RUU screen and I can't even turn it off. Is there any way to recover this? I don't even think I can use ADB anymore.
edit: I got it to reboot by holding BOTH volume buttons and POWER. What a stupid mistake. I'll leave this here though so hopefully no one else does anything so stupid.
Yikes :silly:
edit 2: Hmm, changed MID to the correct value but I'm still getting ERROR 131 CUSTOMER ID ERROR during RUU. Will have to investigate this further. Maybe I need to relock the bootloader.
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
edit 3: Relocking the bootloader still gives the same error RUU. Now I'm stumped.
edit 4: Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
edit 5: Yup, fixing the CID solved the problem

Miguel_Lancaster said:
P.S. The command to change the MID actually seem to be writemid, not changemid -- figured that out through trial and error
Click to expand...
Click to collapse
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Miguel_Lancaster said:
Turns out the CID should actually be BS_US002, not BSUS_002, as you told me in the earlier reply.
Click to expand...
Click to collapse
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.

Flippy498 said:
Ah, sorry. I don't know why I wrote changemid. It wasn't intended. Of course it has to be writemid. I will correct the post.
Sinc I don't know every CID by heart I copied it from a CID list I found with google. I'm going to correct that mistake, too. Thanks for clarifying.
Sorry for the hassle.
Click to expand...
Click to collapse
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.

Miguel_Lancaster said:
I didn't brick anything and got it all figured out in the long run, so no worries. I may not have attempted this in the first place without everything explained so concisely by you earlier, so thank you. Hopefully this thread (mistakes and all) can be beneficial to others.
Seriously though, who decided it was a good idea to put a zero before 'PJA' for the CID? That's just asking for trouble.
Click to expand...
Click to collapse
That whole "0" or "O" bull**** ...
Cost me 3 days of heartache getting errors...
Yeah....that structure is a horrible idea....g

Bootloop after Factory Reset

I have colleague that has problem with his phone, he did a factory reset and after that the phone just goes into boot loop.
He can get to HBOOT window and also inte Recovery. I tried doing a factory reset from the recovery but it did not help, the phone still gets stuck in boot loop, I guess since the reset now resets to the erroneous software.
He is completely on stock, locked bootloader and S-On .
What is the best way forward trying to get latest stock SW or unlocking bootloader, s-off and flashing 3: part SW?

Why always people think S-Off should fix their problem ? That should be the last choice after HTC Service Centre .. if the problem is related to hardware failure.
What you can try first as this is stock, S-On & locked device -
1. Flash a HTC Signed firmware for the firmware version that currently it's running.
2. If the above fails, try the official RUU if available
3. If the above fails, check the error listed when doing no. 1 - to see any hardware failure like EMMC failed & etc
What's the firmware no. ? You can see that on the bootloader - OS - x.xx.xxx.x
then check my thread for the signed firmware. I have almost all the Marshmallow firmware in the collection.
http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5

ckpv5 said:
Why always people think S-Off should fix their problem ? That should be the last choice after HTC Service Centre .. if the problem is related to hardware failure.
What you can try first as this is stock, S-On & locked device -
1. Flash a HTC Signed firmware for the firmware version that currently it's running.
2. If the above fails, try the official RUU if available
3. If the above fails, check the error listed when doing no. 1 - to see any hardware failure like EMMC failed & etc
What's the firmware no. ? You can see that on the bootloader - OS - x.xx.xxx.x
then check my thread for the signed firmware. I have almost all the Marshmallow firmware in the collection.
http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Click to expand...
Click to collapse
Firmware says OS-6.12.401.4
I will check your thread....
I tried the following this from an other thread and just flashing RUU but I got error message "FAIL12 signature verify fail" and "FAILED <remote: 12 signature verify fail>
Einwod said:
I recommend this file. It is the official RUU from HTC. Simply run it from your PC. If it fails, place your phone into bootloader mode and try again. This should not fail. Just be aware that you need a USB 2.0 port, not USB 3.0 as it doesn't play well with Android. This RUU will wipe your internal storage, so make a backup of anything you want to keep first.
Click to expand...
Click to collapse

To install the 6.12.401.4 RUU, check this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6

ckpv5 said:
Why always people think S-Off should fix their problem ? That should be the last choice after HTC Service Centre .. if the problem is related to hardware failure.
What you can try first as this is stock, S-On & locked device -
1. Flash a HTC Signed firmware for the firmware version that currently it's running.
2. If the above fails, try the official RUU if available
3. If the above fails, check the error listed when doing no. 1 - to see any hardware failure like EMMC failed & etc
What's the firmware no. ? You can see that on the bootloader - OS - x.xx.xxx.x
then check my thread for the signed firmware. I have almost all the Marshmallow firmware in the collection.
http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Click to expand...
Click to collapse
Tried this and it didn't work, took awhile too get the phone to flash the fw a second time after the first fail. I didn't realise that I had to disconnect and reconnect the phone to the pc so I was trying to rund the command directly after getting fail message.
ckpv5 said:
To install the 6.12.401.4 RUU, check this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
I haven't been able to flash RUU file linked in this thread because my company firewall is blocking me, so I will try this at home this afternoon.

Leo_83 said:
I tried the following this from an other thread and just flashing RUU but I got error message "FAIL12 signature verify fail" and "FAILED <remote: 12 signature verify fail>
Click to expand...
Click to collapse
You can't go backwards (downgrade) to 4.16.401 from 6.12.401 with s-on. Even with s-off, you can't flash the Lollipop RUU from Marshmallow, unless you flash the LP firmware first.
And I'm not suggesting s-off either, as you probably don't need it.

ckpv5 said:
To install the 6.12.401.4 RUU, check this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Click to expand...
Click to collapse
How long does the process take, to me it seems to be flashing the RUU file over and over again....

Leo_83 said:
How long does the process take, to me it seems to be flashing the RUU file over and over again....
Click to expand...
Click to collapse
It might take 5 or 10 minutes.
On your phone's screen, you may see the names of various modules being flashed, with (hopefully) a message showing each one confirmed/successful. The phone has something like 41 partitions, and all of them get flashed.

redpoint73 said:
It might take 5 or 10 minutes.
On your phone's screen, you may see the names of various modules being flashed, with (hopefully) a message showing each one confirmed/successful. The phone has something like 41 partitions, and all of them get flashed.
Click to expand...
Click to collapse
It worked... Patience is truly a virtue [emoji13]

Leo_83 said:
It worked... Patience is truly a virtue [emoji13]
Click to expand...
Click to collapse
Just about to write another method and it's great to know you solved it.

redpoint73 said:
It might take 5 or 10 minutes.
On your phone's screen, you may see the names of various modules being flashed, with (hopefully) a message showing each one confirmed/successful. The phone has something like 41 partitions, and all of them get flashed.
Click to expand...
Click to collapse
ckpv5 said:
Just about to write another method and it's great to know you solved it.
Click to expand...
Click to collapse
Thank you both for your help, much appreciated mates!

[GUIDE][DOWNGRADE][FLASHING] Downgrade and flashing discussion th

EDIT: For all of you that are wondering what the "fused" flag in download mode means, it's something related to the file system. Just read that
https://www.xda-developers.com/divi...les-fuse-replacement-will-reduce-io-overhead/
Hi XDA community.
Just feel free to post any problems you have and we will try to resolve them.
Two methods for S-ON or S-OFF device, please do it under Nougat 7.0 firmware installed. This refers we have to downgrade to nougat first and the running those commands.
S-ON only
1. Reboot to TWRP recovery
2. Use the command below to erase persist partition
Code:
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
S-OFF only
1. Reboot to bootloader (not download)
2. Use the command below to erase persist partition
Code:
fastboot erase persist
Is that possible to downgrade without S-OFF??
Please watch the video, HTC 10 can downgrade in the same method!!!
PS. This video is for HTC One M9, please use Nougat RUU/firmware for HTC 10 to do downgrading.
Credits for @sappro
------------------ GO FROM US UNLOCKED TO EUROPEAN OREO-----------------
This is for all people who are in US Oreo and are having stability issues. Be noticed you need S-OFF on your phone.
Change your CID and MID to a WWE ones: HTC__034 (you can choose other WWE one) and 2PS620000.
Download Oreo RUU and flash it: https://androidfilehost.com/?fid=746010030569969175
No need to wipe the persist partition, as we aren't downloading.
(OUTDATED) GO FROM US UNLOCKED TO EUROPEAN OREO
EDIT: This method is now outdated, as now we have stable Oreo RUU for US unlocked, but if you want to convert to WWE from RUU, you can follow this steps.
This is for all people who are in US Oreo and are having stability issues. Be noticed you need S-OFF on your phone.
Change your CID and MID to a WWE ones: HTC__034 (you can choose other WWE one) and 2PS620000.
Flash nougat firmware zip (htc_fastboot): https://androidfilehost.com/?fid=961840155545593694
Flash nougat RUU (htc_fastboot): https://androidfilehost.com/?fid=817550096634797504
Flash oreo OTA within stock recovery:
https://androidfilehost.com/?fid=890129502657577071
DONE.

One other note is that all of us that have flashed Oreo firmware have a "fused" status flag in bootloader and download mode. So far as I know, no one knows what this means.

PR4X15 said:
One other note is that all of us that have flashed Oreo firmware have a "fused" status flag in bootloader and download mode. So far as I know, no one knows what this means.
Click to expand...
Click to collapse
I have added your note into the OP:good:

I'm uploading a "different" 2.41.401.41 RUU for you to try.
Will post a link when it's complete.

Fused
PR4X15 said:
One other note is that all of us that have flashed Oreo firmware have a "fused" status flag in bootloader and download mode. So far as I know, no one knows what this means.
Click to expand...
Click to collapse
When you downgrade that flag disappears. So I will downgrade and flash the official RUU once released... Hopefully that will correct everything.
Also, thanks to everyone for trying to work through this problem, I know I have spent hours downgrading, then flashing radio images, downgrading further ( zips ), if I ever get it working I will let you know... Gonna try again after work...

Typically fused status is just a way for a manufacturer to know if you've modified the firmware on a device. Kind of like the old "Tampered" hboot status. I'm guessing it's the same kind of idea, a way for HTC to know that the system or firmware has been modified different than it shipped in the event they need it for diagnostics or evaluating a warranty claim. i need someone more knowledgable to confirm, but I'm throwing this out for conversation.

santod040 said:
I'm uploading a "different" 2.41.401.41 RUU for you to try.
Will post a link when it's complete.
Click to expand...
Click to collapse
What do you mean with "different"?? Sorry the stupid answer but I have spend so many hours on this

slysurfer said:
When you downgrade that flag disappears. So I will downgrade and flash the official RUU once released... Hopefully that will correct everything.
Also, thanks to everyone for trying to work through this problem, I know I have spent hours downgrading, then flashing radio images, downgrading further ( zips ), if I ever get it working I will let you know... Gonna try again after work...
Click to expand...
Click to collapse
I hope so, that official update fixes that. And also thanks to all people who are trying to find out that from my side too.:fingers-crossed:

fdgd1998 said:
What do you mean with "different"?? Sorry the stupid answer but I have spend so many hours on this
Click to expand...
Click to collapse
This is a combined/signed RUU zip.
They typically include whatever bootloader was needed to prepare the device for the one in the main RUU.
Sometimes these are contained in a smaller pre-update or small update shortly before the one with major changes, as well as any other files needed to process the RUU.
Similar to what this RUU was missing, a pre-update hboot to allow the RUU to flash properly.
They made a similar goof on the Sprint (I forget if m7, m8, or m9) but it was pulled for the same/similar reason.
Anyhow, feel free to try it, or not.
The choice is of course yours.
Although I'd be at least a little curious if it worked for you or not, or anyone else in the same boat.
(Yes it is a FULL WIPE RUU)
2PS6IMG_PERFUME[email protected]61226_79.07_F_release_509716_combined_signed_2_4.zip
---

santod040 said:
This is a combined/signed RUU zip.
They typically include whatever bootloader was needed to prepare the device for the one in the main RUU.
Sometimes these are contained in a smaller pre-update or small update shortly before the one with major changes, as well as any other files needed to process the RUU.
Similar to what this RUU was missing, a pre-update hboot to allow the RUU to flash properly.
They made a similar goof on the Sprint (I forget if m7, m8, or m9) but it was pulled for the same/similar reason.
Anyhow, feel free to try it, or not.
The choice is of course yours.
Although I'd be at least a little curious if it worked for you or not, or anyone else in the same boat.
(Yes it is a FULL WIPE RUU)
2PS6IMG_PERFUME[email protected]61226_79.07_F_release_509716_combined_signed_2_4.zip
---
Click to expand...
Click to collapse
I'm gonna try this as soon as I get home! Thanks for your time!

santod040 said:
This is a combined/signed RUU zip.
They typically include whatever bootloader was needed to prepare the device for the one in the main RUU.
Sometimes these are contained in a smaller pre-update or small update shortly before the one with major changes, as well as any other files needed to process the RUU.
Similar to what this RUU was missing, a pre-update hboot to allow the RUU to flash properly.
They made a similar goof on the Sprint (I forget if m7, m8, or m9) but it was pulled for the same/similar reason.
Anyhow, feel free to try it, or not.
The choice is of course yours.
Although I'd be at least a little curious if it worked for you or not, or anyone else in the same boat.
(Yes it is a FULL WIPE RUU)
2PS6IMG_PERFUME[email protected]61226_79.07_F_release_509716_combined_signed_2_4.zip
---
Click to expand...
Click to collapse
Well, I just flashed the RUU. Unfortunately I'm still without any cell connectivity I'm totally thrown for a loop on this thing. I've got no idea what's keeping it from working.

If someone can get ahold of an RUU for the official Oreo rollout in Taiwan, I wonder if using that RUU and then using an old RUU will fix the issue. @fdgd1998 @PR4X15

jackebuehner said:
If someone can get ahold of an RUU for the official Oreo rollout in Taiwan, I wonder if using that RUU and then using an old RUU will fix the issue. @[email protected]
Click to expand...
Click to collapse
It't very difficult it could work. Because I have actually tried the same with the US unlocked and doesn't work.
I am at the miment on Taiwanese Oreo, and my phone is working phone. We know the problem is with the radio, but we aren't able to find out what is....
Anyway, if I find the Oreo RUU I'll post it.

If I had to make a guess at this point, I'd say something to do with new lockbooter.img in firmware. (not boot"loader" but lockbooter).
Assuming it remains even after using an older RUU, as there was no lockbooter.img in previous versions.
I realize this isn't very helpful, only for informational purposes.
Here are some strings of bytes taken from the image:
\00Illegal byte sequence\00Domain error\00Result not representable\00Not a tty\00Permission denied\00Operation not permitted\00No such file or directory\00No such process\00File exists\00Value too large for data type\00No space left on device\00Out of memory\00Resource busy\00Interrupted system call\00Resource temporarily unavailable\00Invalid seek\00Cross-device link\00Read-only file system\00Directory not empty\00Connection reset by peer\00Operation timed out\00Connection refused\00Host is down\00Host is unreachable\00Address in use\00Broken pipe\00I/O error\00No such device or address\00Block device required\00No such device\00Not a directory\00Is a directory\00Text file busy\00Exec format error\00Invalid argument\00Argument list too long\00Symbolic link loop\00Filename too long\00Too many open files in system\00No file descriptors available\00Bad file descriptor\00No child process\00Bad address\00File too large\00Too many links\00No locks available\00Resource deadlock would occur\00State not recoverable\00Previous owner died\00Operation canceled\00Function not implemented\00No message of desired type\00Identifier removed\00Device not a stream\00No data available\00Device timeout\00Out of streams resources\00Link has been severed\00Protocol error\00Bad message\00File descriptor in bad state\00Not a socket\00Destination address required\00Message too large\00Protocol wrong type for socket\00Protocol not available\00Protocol not supported\00Socket type not supported\00Not supported\00Protocol family not supported\00Address family not supported by protocol\00Address not available\00Network is down\00Network unreachable\00Connection reset by network\00Connection aborted\00No buffer space available\00Socket is connected\00Socket not connected\00Cannot send after socket shutdown\00Operation already in progress\00Operation in progress\00Stale file handle\00Remote I/O error\00Quota exceeded\00No medium found\00Wrong medium type\00No error information\00\00"entering %s"\00lockbooter_read_rpmb\00"ERR: qsee_stor_device_init: [%d]"\00"qsee_stor_device_init: ok"\00"ERR: qsee_stor_open_partition: [%d]"\00"qsee_stor_open_partition: ok"\00"ERR: qsee_stor_read_sectors: [%d]"\00"qsee_stor_read_sectors: ok"\00"exiting %s, ret = [%d]"\00"RPMB didn't provisioned. No fuse?"\00lockbooter_write_rpmb\00"ERR: qsee_stor_device_get_info: [%d]"\00"deviceInfo: bytes_per_sector: [%u], total_sectors: [%u], available_sectors: [%u]"\00"ERR: qsee_stor_add_partition: [%d]"\00"qsee_stor_add_partition: ok"\00"ERR: qsee_stor_open_partition again: [%d]"\00"ERR: qsee_stor_client_get_info: [%d]"\00"clientInfo: bytes_per_sector: [%u], total_sectors: [%u]"\00"ERR: qsee_stor_write_sectors: [%d]"\00"qsee_stor_write_sectors: ok"\00"LOCKBOOTER init. Version: %x.%x"\00"ERROR: Response buffer len insufficient, ERROR OUT"\00"ERROR: Command pointer equals NULL!"\00"ERROR: Command buffer len insufficient for reading cmd_id, ERROR OUT"\00"TZ App cmd handler, cmd_id = %d"\00"Cmd/rsp buffer lens insufficient - %x, %x, ERROR OUT"\00"CMD: app version"\00"CMD: random generation"\00"CMD: smart card verification"\00"CMD: ks random generation"\00"CMD: ks verification"\00"CMD: set ks verification key"\00"CMD: get ks verification: [%u]"\00"CMD: clear ks verification"\00"CMD: decrease ks verification"\00"FIXME: CMD_SET_UNLOCK_FLAG"\00"Unsupported command: %d"\00"LockBooter App shutdown"\00sc_random_generation\00"ERR: size"\00"%s: return value is not long enough"\00"%s: it's good to go"\00"exiting %s"\00"ERR: size is not right (%d)"\00sc_card_verification\00"sl = %d"\00"ERR: random number is wrong"\00"random number is correct"\00"ERR: qsee_malloc (key)"\00"ERR: qsee_hash (%d)"\00"ERR: qsee_rsa_verify_signature (%d, %x)"\00"qsee_rsa_verify_signature is good"\00sc_main\00"len is %d"\00"ERR: qsee_register_shared_buffer"\00"ERR: qsee_prepare_shared_buf_for_secure_read"\00"ERR: qsee_prepare_shared_buf_for_nosecure_read"\00"ERR: qsee_deregister_shared_buffer"\00ks_random_generation\00"ERR: size is not right [%d]"\00"return value is not long enough: [%d]"\00"ERR: qsee_hash [%d]"\00"key malloc failed"\00"public enc failed: [%d] [%d]"\00"ks_request_type: [%u], ks_reboot_count: [%u] [%#x] [%zu]"\00"init public key failed"\00ks_verification\00"ERR: Exceeded retry count [%d]"\00"qsee_rsa_verify_signature is good, nResult: [%d], request_type: [%d], ks_reboot_count: [%u]"\00"ERR: RSA_verify_ext [%d, %#x]"\00set_verification_key\00"ERR: size is not right [%d] [%zu]"\00ks_main\00pgfs_data_update\00"ERR: Bad Parameters"\00"ERR: qsee_cipher_init"\00"ERR: qsee_cipher_set_parm (key)"\00"ERR: qsee_cipher_set_parm (mode)"\00"ERR: qsee_cipher_set_parm (IV)"\00"ERR: qsee_set_bandwidth"\00"ERR: qsee_cipher_decrypt"\00"It's WRONG pgfs data!!!"\00"sec_info.security_level = 0x%x"\00"sec_info.unlock = 0x%x"\00"sec_info.keycard_s_off_times = 0x%x"\00"sec_info.keycard_s_on_timestamp = 0x%x"\00"sec_info.keycard_s_off_timestamp = 0x%x"\00"sec_info.version_check = 0x%x"\00"ERR: qsee_cipher_encrypt"\00"everything looks good!"\00\C8\E0\E4X<;\F0\CC睤\DAA\00[stub]\00" In qsee_shared_buffer.c: ISharedBuffer_registerSharedBuffer returned =%d"\00" In qsee_shared_buffer.c: qsee_register_shared_buffer: Object is NULL!!!"\00" In qsee_shared_buffer.c: qsee_deregister_shared_buffer: Object is NULL !!!"\00-+ 0X0x\00(null)\00-0X+0X 0X-0x+0x 0x\00inf\00INF\00nan\00NAN\00.\000123456789ABCDEFT!"
K'hnopqb ($
%#\83\82}&*+<=>?CGJMXYZ[\]^_`acdefgijklrstyz{|\00lockbooter\00m=x;n=lockbooter;p=b:9b8208ff2d701\00p+s}-#Pxh7Z!<+`
Click to expand...
Click to collapse

santod040 said:
If I had to make a guess at this point, I'd say something to do with new bootlocker.img in firmware. (not boot"loader" but boot"locker").
Assuming it remains even after using an older RUU, as there was no bootlocker.img in previous versions.
I realize this isn't very helpful, only for informational purposes.
Here are some strings of bytes taken from the image:
Click to expand...
Click to collapse
That' a very interesting info.
Edit: I think that this might be the cause of the messages I got on fastboot saying "mismatched partition size" and also the one which are keeping as from downgrading.
Just a new partition in Oreo.

Anyone else having battery issues?

fdgd1998 said:
That' a very interesting info.
Edit: I think that this might be the cause of the messages I got on fastboot saying "mismatched partition size" and also the one which are keeping as from downgrading.
Just a new partition in Oreo.
Click to expand...
Click to collapse
So they are messing with the partition table anyway, so they may just as well had given us Treble. Oh well...

errikosd said:
So they are messing with the partition table anyway, so they may just as well had given us Treble. Oh well...
Click to expand...
Click to collapse
Messing with partition table is a posibility. And Google said thar Treble will only support to devices that comes with Oreo preinstalled.

Maybe because of this? Differs from this?
Sent from my HTC 10 using Tapatalk

cyrusct82 said:
Maybe because of this? Differs from this?
Click to expand...
Click to collapse
I don't understand your post. Is a bit confusing. What should be able to see in that screnshots?

Can't update firmware to Oreo.

Hey, I'm having a bit (or a **** ton) of trouble updating my firmware from Marshmallow to Oreo, and it's getting really frustrating.
I was on RR before, so I never really updated the firmware, but since Xposed for Oreo is out, I decided to update to LeeDroid. The problem is that, since LeeDroid requires the latest Oreo firmware, I had to update it (or try to), and no matter any method I've tried, it won't work. And the problem is, it doesn't even allow me to update for Nougat either.
At first I thought it was some issue with the CID (maybe I downloaded the wrong RUU), so I downloaded firmware for my CID and tried to update via both fastboot and download mode's SD card thing and neither worked. When using fastboot, it would give me "9 RU_SECURITY_FAIL" and when using SD card, it would give me "14 RU_ZIP_INFO_ERROR android-info missing or malformed" even though I checked the zip I was flashing, and the android-info text file was there (and this is Nougat firmware). Nothing is helping and it's becoming extremely frustrating.
I also tried using stock Marshmallow (which I was able to get via TWRP backup since that was the only way I could get pure stock) and tried just doing an OTA from there, but it didn't work, no update showed up.
Phone's info:
CID: HTC__J15 (which I believe is GCC).
MID: 2PS620000
Current Firmware: 1.95.401.4
S-ON
Bootloader unlocked (obviously).
I'm using Pure Fusion temporarily.
Update: I managed to go S-OFF but I still can't flash any RUUs. I can flash firmware files, but any RUU zip I've downloaded just causes some kind of error. I tried flashing some kind of stock recovery to apply an update (if that would even work) but I keep getting an error screen (the one with a phone and a red sign on its screen).
Phone's info (as of update):
CID: 11111111 (SuperCID).
MID: 2PS620000
Current Firmware: 1.95.401.4
S-OFF
Bootloader unlocked (obviously).
Update 2: Nevermind, I killed the phone and paid $25 for nothing. Yay.

You cannot just update the firmware if s-on... Thats first issue... You will need to revert to current build,flash stock recovery and take the ota's in sequence...As far as no notifications... It would be instant may take a bit
majidamiri15300 said:
Hey, I'm having a bit (or a **** ton) of trouble updating my firmware from Marshmallow to Oreo, and it's getting really frustrating.
I was on RR before, so I never really updated the firmware, but since Xposed for Oreo is out, I decided to update to LeeDroid. The problem is that, since LeeDroid requires the latest Oreo firmware, I had to update it (or try to), and no matter any method I've tried, it won't work. And the problem is, it doesn't even allow me to update for Nougat either.
At first I thought it was some issue with the CID (maybe I downloaded the wrong RUU), so I downloaded firmware for my CID and tried to update via both fastboot and download mode's SD card thing and neither worked. When using fastboot, it would give me "9 RU_SECURITY_FAIL" and when using SD card, it would give me "14 RU_ZIP_INFO_ERROR android-info missing or malformed" even though I checked the zip I was flashing, and the android-info text file was there (and this is Nougat firmware). Nothing is helping and it's becoming extremely frustrating.
I also tried using stock Marshmallow (which I was able to get via TWRP backup since that was the only way I could get pure stock) and tried just doing an OTA from there, but it didn't work, no update showed up.
Phone's info:
CID: HTC__J15 (which I believe is GCC).
MID: 2PS620000
Current Firmware: 1.95.401.4
S-ON
Bootloader unlocked (obviously).
I'm using Pure Fusion temporarily.
Click to expand...
Click to collapse

Wonders_Never_Cease said:
You cannot just update the firmware if s-on... Thats first issue... You will need to revert to current build,flash stock recovery and take the ota's in sequence...As far as no notifications... It would be instant may take a bit
Click to expand...
Click to collapse
The S-ON thing I get, but with current build, I sat there with stock MM and hit check for updates like a million times and nothing came up. Aside from that, I still don't know how to go S-OFF without having to pay that $25, because that much money just seems absurd to pay.

That 25 bucks is really good investment. Trust me. Makes your life with htc 10 much easier.

Zeezala said:
That 25 bucks is really good investment. Trust me. Makes your life with htc 10 much easier.
Click to expand...
Click to collapse
Hmmmmm, well I do have the money for it, but just a question: is it safe if I know what I'm doing, flash wise? Like my phone won't get screwed up for no reason?

In my case, S-OFF app did everything itself. If you know, what you are you doing with your phone, it shoulnt get screwed.
Do some reading about S-OFF and firmware updates and so on.
Honestly, i did some reading, but Im not 100% sure what Im doing. Fortunately, my phone is still alive...

Zeezala said:
In my case, S-OFF app did everything itself. If you know, what you are you doing with your phone, it shoulnt get screwed.
Do some reading about S-OFF and firmware updates and so on.
Honestly, i did some reading, but Im not 100% sure what Im doing. Fortunately, my phone is still alive...
Click to expand...
Click to collapse
Okay, what the hell? I decided to go with S-OFF and installed the SunShine APK, then did all the tests and whatnot and paid for the license. Then the phone rebooted, but when I went into the bootloader to check, it still said "S-ON."

Try run it againg or check some thread related to Sunshine. I can remember i installed app, paid, run it, i took some time, phone rebooted couple of times... Last thing was question, what i want. S-OFF locked, S-OFF unlocked...

Zeezala said:
Try run it againg or check some thread related to Sunshine. I can remember i installed app, paid, run it, i took some time, phone rebooted couple of times... Last thing was question, what i want. S-OFF locked, S-OFF unlocked...
Click to expand...
Click to collapse
I ran it 3 times so far, still the same thing. I just opened a ticket with SunShine and hope they reply soon.

And that sunshine test was ok? Your bootloader is unlocked?

Zeezala said:
And that sunshine test was ok? Your bootloader is unlocked?
Click to expand...
Click to collapse
Actually, nevermind that. SunShine replied and they helped me S-OFF, but the problem now is that I can't flash any RUUs for some reason. None of them work.

Try changing to Super CID, then you can flash any RUU made for the 10. You could also try an SD card-version of an RUU, "2PS6IMG.zip".
Just Google for:
Code:
htc 10 change to super cid

Sunshine
majidamiri15300 said:
I ran it 3 times so far, still the same thing. I just opened a ticket with SunShine and hope they reply soon.
Click to expand...
Click to collapse
Did you do a Google search for the video by rootjunky?
https://www.google.com/search?safe=...3i22i29i30k1j33i160k1j30i10k1.103.ONfztkfIoNc

roirraW "edor" ehT said:
Try changing to Super CID, then you can flash any RUU made for the 10. You could also try an SD card-version of an RUU, "2PS6IMG.zip".
Just Google for:
Code:
htc 10 change to super cid
Click to expand...
Click to collapse
The MID has to match as well

majidamiri15300 said:
Actually, nevermind that. SunShine replied and they helped me S-OFF, but the problem now is that I can't flash any RUUs for some reason. None of them work.
Click to expand...
Click to collapse
You must be flashing the RUU wrong. You never needed to go S OFF and you don't need supercid either. Here is the RUU you need
https://androidfilehost.com/?fid=817550096634797504
Rename to 2PS6IMG.zip
Place on ex SD card
Boot to download mode
Press vol up to flash.
RUU will erase everything. once the RUU has flashed turn you phone back on and take the OTA.

yldlj said:
You must be flashing the RUU wrong. You never needed to go S OFF and you don't need supercid either. Here is the RUU you need
https://androidfilehost.com/?fid=817550096634797504
Rename to 2PS6IMG.zip
Place on ex SD card
Boot to download mode
Press vol up to flash.
RUU will erase everything. once the RUU has flashed turn you phone back on and take the OTA.
Click to expand...
Click to collapse
THANK YOU SO MUCH, spent HOURS bricking my device trying to get oreo, this worked !

breakfrecell said:
THANK YOU SO MUCH, spent HOURS bricking my device trying to get oreo, this worked !
Click to expand...
Click to collapse
Your welcome
Sent from my OnePlus6 using XDA Labs

Given up!

I'm S-Off and can flash, however I get various error. I've read more and spent more hours than the phone is worth.
Are any recognized/known developers interested in taking a look at it? I will mail it to you, and if you can get it working on Verizon or ATT, we can talk reward.

tst1212 said:
I'm S-Off and can flash, however I get various error. I've read more and spent more hours than the phone is worth.
Are any recognized/known developers interested in taking a look at it? I will mail it to you, and if you can get it working on Verizon or ATT, we can talk reward.
Click to expand...
Click to collapse
What errors, start giving that info. Mailing it off to someone is a last resort. Why not just simply start with what tried, how you did that and what all outcome is.

I've tried so much I've lost track and hope. I'm at last resort, and already looking at other phones, figured this was better than throwing it in the trash.
Supposedly the phone is new, off eBay, but who knows. I'll send it to you, interested?

tst1212 said:
I've tried so much I've lost track and hope. I'm at last resort, and already looking at other phones, figured this was better than throwing it in the trash.
Supposedly the phone is new, off eBay, but who knows. I'll send it to you, interested?
Click to expand...
Click to collapse
Sorry no i am not interested, i will try to do my best to help people out here at software level but never go outside that box if you know what i mean.
Kind regards

Mr Hofs said:
Sorry no i am not interested, i will try to do my best to help people out here at software level but never go outside that box if you know what i mean.
Kind regards
Click to expand...
Click to collapse
Thanks, I posted some info over in https://forum.xda-developers.com/ht...7-fastboot-flashing-firmware-t3387520/page203 , as my issues seems related to flashing firmware.

tst1212 said:
Thanks, I posted some info over in https://forum.xda-developers.com/ht...7-fastboot-flashing-firmware-t3387520/page203 , as my issues seems related to flashing firmware.
Click to expand...
Click to collapse
I've seen it indeed, i would like to continue here if you don't mind.
First off did you try to flash the nougat US unlocked ruu ? And what is the info shown in download mode at the moment ?

I've tried flashing a lot of stuff. Each time, error or no error the OS always seem to say the one I flashed. DL Mode Info below;
Yes, I tried the RUU from HTC, the RUU_PERFUME_WL_N70_SENSE80GP_VZW_MR_NA_Gen_Unlock_2.51.617.32.EXE version, and got an ERROR [132]: SIGNATURE ERROR
hTC download mode
*** UNLOCKED ***
*** FUSED ***
htc_pmewl PVT S-OFF
CID-BS_US001
MID-2PS650000
ColorID-BLK00
LK-1.0.0.0000
[email protected]
OpenDSP-v23.0.8996.00007_1028
OS-3.16.617.2
Jan 2 2018,18:22:58(1012001)

So you want it on verizon, first change your CID to the verizon variant because this one is not good to start with.
"htc_fastboot oem writecid VZW__001" or "fastboot oem writecid VZW__001" the command depends on your adb/fastboot package. Then flash this RUU. Rename to 2PS6IMG.zip and copy it to the sdcard, then boot to download mode and confirm to flash.
https://androidfilehost.com/?fid=673956719939827070
Let me know how you get along.

Mr Hofs said:
So you want it on verizon, first change your CID to the verizon variant because this one is not good to start with.
"htc_fastboot oem writecid VZW__001" or "fastboot oem writecid VZW__001" the command depends on your adb/fastboot package. Then flash this RUU. Rename to 2PS6IMG.zip and copy it to the sdcard, then boot to download mode and confirm to flash.
https://androidfilehost.com/?fid=673956719939827070
Let me know how you get along.
Click to expand...
Click to collapse
No luck, I get the below error;
[email protected]
33 RU_UPDATE_FIRMWARE_FAIL
33 RU_UPDATE_FIRMWARE_FAIL
FAIL33 RU_UPDATE_FIRMWARE_FAIL
I then ran it a second time, same error. This is the same error, I receive when trying to flash various firmware.
Checked the MD5, it's fine. Will try and run it a few more times, I wonder if it could be a hardware error.

At this point i can't think of anything to be honest

Thanks! Guess I'll reach out to HTC, they'll probably laugh once they realize I'm S-Off. Now the question is, what phone do I get next.

tst1212 said:
Thanks! Guess I'll reach out to HTC, they'll probably laugh once they realize I'm S-Off. Now the question is, what phone do I get next.
Click to expand...
Click to collapse
Usually they don't really care about S-OFF or not.....at least not in the experiences i have seen here at xda.