when i turn on my htc m9 it goes to bootloader and i have access to download mode and recovery mode (rooted TWRP) and i tried with so many RUU but always i get error 131 (RUU not matched with your CID )
my phone is UNLOCKED and S-ON i cant get it to S-OFF and change the cid :/
kernel: lk
product: htc_himawhl
version: 1.0
imei:
version-main: 2.11.651.19
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 0PJA10000
cid: SPCS_001
any solution ? or RUU for my MID and CID ?
Have you identified your MID & CID? This will be key in finding the correct RUU. The best resource is the SKU/CID/MID list by Sneakyghost & Behold_this (url below). Yes, we could look it up for you, but it's best to learn firsthand and will take just a minute or two.
Once you know your carrier and model, we can start searching for the matching. From your information, it looks like you're currently on Lollipop firmware, so we're talking about moving you to Marshmallow if it's available. This will get you the latest firmware and enable you to run the latest custom ROMs, if you should choose to do so.
Useful links for modding your HTC M9
Flippy498's Google Sheet
- the end-all, be-all resource for HTC M9 restoration
SKU-, CID- and MID-List by Sneakyghost and Behold_this
- a spreadsheet for using your CID & MID to identify your phone
HTC Sync Manager
- installs the necessary drivers & ADB tools for the HTC M9
Instructions for obtaining your CID, MID & software version on Windows:
a. Install HTC Sync Manager (this will install the necessary drivers & ADB tools)
b. Boot your phone into download mode (from a powered off state, turn on by holding the POWER+DOWNVOL)
c. Connect your phone to your PC
d. Open a command prompt window
e. Navigate to the ADB tools folder, typically C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
- assuming the path is correct, you can cut & paste this command into your terminal: cd C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync
f. Execute the following command in a terminal (command prompt): fastboot getvar all
g. Copy the lines that mention product, version-main, mid, and cid.
@computerslayer: It's actually easier to look at the line with "OS" at the beginning which can be found in download mode (it states the same information as version-main from getvar all) and to search for a RUU that corresponds to that firmware version. There is no need for finding out the device's CID or MID.
Edit: Besides of that all the needed information can already be found in the OP.
@djope47: Visit HTC's US website. They provide RUUs for US carriers. The search function of your browser and your version-main will probably lead you to the correct RUU. Newer versions with the same SKU (the numbers behind the second dot in the firmware version and before the third dot) should be fine, too.
Edit2: Or you look at the RUU collections which are linked in my thread (located in the general section).
Sent from my HTC One M9 using XDA Labs
i got my firmware from HTC site (sprint) and in the begging of flashing (0%) it gives me error-155 (same result with unlocked/relocked bootloader and S-ON) and when i try with zip file it tells me i dont have the correct CID
Flippy498 said:
@computerslayer: It's actually easier to look at the line with "OS" at the beginning which can be found in download mode (it states the same information as version-main from getvar all) and to search for a RUU that corresponds to that firmware version. There is no need for finding out the device's CID or MID.
Edit: Besides of that all the needed information can already be found in the OP.
Click to expand...
Click to collapse
Thanks Flippy! I appreciate the chance to learn more about the M9.
djope47 said:
i got my firmware from HTC site (sprint) and in the begging of flashing (0%) it gives me error-155 (same result with unlocked/relocked bootloader and S-ON) and when i try with zip file it tells me i dont have the correct CID
Click to expand...
Click to collapse
So you tried the M9 x.xxx.651.xx RUU from HTCs website while your phone was relocked and booted to download mode? Your phone definitely has the correct Sprint CID therefore it's not normal that you face that error. How did you try to flash the *.zip from stifilz's collection (or did you extract the *.zip from the *.exe by yourself - if so: what have been your exact steps?)? Did you use fastboot or have you tried the SD card method described in my google sheet?
I personally don't like the *.exe files or the fastboot method (which actually work the same way). They fail so many times due to little mistakes a user can make. The SD card method on the other hand doesn't rely on working USB cables, drivers, the correct USB port, and a relocked bootloader (so you can use it with an unlocked bootloader, too) or in some cases the correct windows version (some people have problems with win 10 whereas the same setup with win 7 doesn't produce a single error for them).
ive tried the sd card method (go to download mode then press volume up button ) and i got the failed msg ,i tried it with different x.xxx.651.xx RUUs all gives the same result
Is it possible to install ruu from the US developer version to HTC One m9 bought from other country ? (Dubai version )
i found this https://www.youtube.com/watch?v=xWmnHwkDrKk ,its the same problem that i have but its for htc one ,ist safe if i try it on htc m9 ?
djope47 said:
i found this https://www.youtube.com/watch?v=xWmnHwkDrKk ,its the same problem that i have but its for htc one ,ist safe if i try it on htc m9 ?
Click to expand...
Click to collapse
I didn't watch the video, but I can tell you that he is using an HTC One M7 and that I wouldn't follow instructions for anything other than your phone model (HTC One M9).
i noticed that all RUU.zip files that i downloaded are corrupted i cant extract them ,and the size of zip file is more than 2GB but the total size of the files inside it is like 70MB is this normal ? ive downloaded several RUUs and they are all with the same problem
They're encrypted and not meant to be unzipped. Therefore many programs can't handle those archives. If you use 7-zip and the #-method then you're able to unzip a RUU. However there is absolutely no reason why you should do that since they get flashed as a zip.
Sent from my HTC One S using XDA Labs
so what should i do ive tried what u said and didnt work out ! should i try this method https://www.youtube.com/watch?v=xWmnHwkDrKk ?? and in those RUUs they have the same CIDnum with my phone but the MIDnum mine is 0PJA10000 and the sprint RUUs have 0PJA20000
any solution ?
Oh yeah, I totally missed that. The MID with the 2 is the correct one for sprint. Did you buy your phone second hand? It looks like someone set is S-OFF, changed the MID and set it S-ON, again. Maybe that person flashed a RUU that's not compatible with that phone, too. You should try to find out the Serialnumber of the phone and contact HTC for finding out whether it really is a sprint phone or whether someone borked an international M9 (your current MID is the international one). GSM firmware and CDMA hardware are not compatible and vice versa. In the worst case it's unrecoverable.
If we know it's original firmware we might be able to fix the phone with a RUU. However I can't guarantee anything.
Btw, instructions how to flash RUU.zip files can be found in my google sheet, too.
Sent from my HTC One S using XDA Labs
all what you said i was the one who done that ! i bought it with s-off and with TWRP and i was trying to get it back to stock so i followed a guide that told me to change my MID to 0PJA10000 (its was 0PJA20000 at first )then i flashed a wrong RUU that was in the guide and i set it S-ON again ! i contacted htc they told me its sprint
any solution now ?
Flippy498 said:
Oh yeah, I totally missed that. The MID with the 2 is the correct one for sprint. Did you buy your phone second hand? It looks like someone set is S-OFF, changed the MID and set it S-ON, again. Maybe that person flashed a RUU that's not compatible with that phone, too. You should try to find out the Serialnumber of the phone and contact HTC for finding out whether it really is a sprint phone or whether someone borked an international M9 (your current MID is the international one). GSM firmware and CDMA hardware are not compatible and vice versa. In the worst case it's unrecoverable.
If we know it's original firmware we might be able to fix the phone with a RUU. However I can't guarantee anything.
Btw, instructions how to flash RUU.zip files can be found in my google sheet, too.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
all what you said i was the one who done that ! i bought it with s-off and with TWRP and i was trying to get it back to stock so i followed a guide that told me to change my MID to 0PJA10000 (its was 0PJA20000 at first )then i flashed a wrong RUU that was in the guide and i set it S-ON again ! i contacted htc they told me its sprint
any solution now ?
I guess you're talking about the "100%" guide here in the general forum. The problem is that it only applies to the international version of the M9. Since many users don't know that there is a dedicated forum for every US branded version of the M9 mistakes like yours may occur.
If possible flash a custom rom that is compatible with your current firmware and based on sense (like an old viper version for example). Then get the sunshine app and try to re-S-OFF your phone. If you're lucky and the previous owner used sunshine, too, you won't have to pay. If not you need to invest 25 bucks to recover your phone. After you got S-OFF you change the MID back to its original state. Afterwards you should be able to use the RUU.zip as described in my sheet.
Sent from my HTC One S using XDA Labs
Flippy498 said:
I guess you're talking about the "100%" guide here in the general forum. The problem is that it only applies to the international version of the M9. Since many users don't know that there is a dedicated forum for every US branded version of the M9 mistakes like yours may occur.
If possible flash a custom rom that is compatible with your current firmware and based on sense (like an old viper version for example). Then get the sunshine app and try to re-S-OFF your phone. If you're lucky and the previous owner used sunshine, too, you won't have to pay. If not you need to invest 25 bucks to recover your phone. After you got S-OFF you change the MID back to its original state. Afterwards you should be able to use the RUU.zip as described in my sheet.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
where can i find that custom rom ?or which one is the right one for my phone ? can you give me a link to it ? help me please im a noob
Being a noob is not an excuse for not using the xda search or google. The rom is even linked in my signature.
Link to Team Venoms Website
I guess version 3.5 should work fine for you.
Flippy498 said:
Being a noob is not an excuse for not using the xda search or google. The rom is even linked in my signature.
Link to Team Venoms Website
I guess version 3.5 should work fine for you.
Click to expand...
Click to collapse
damn man it worked thanks a lot
Related
Q&A for [OTA] 1.32.401.15 + Firmware + NoRedText ABOOT + RUU
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 [OTA] 1.32.401.15 + Firmware + NoRedText ABOOT + RUU. 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!
HTC One M9
Hello,
I wonder why the HBOOT is now called ABOOT with the One M9.. is it just because it`s new design.. or are there more changes that we should be careful with?
Thanks a lot
pipapoananas said:
Hello,
I wonder why the HBOOT is now called ABOOT with the One M9.. is it just because it`s new design.. or are there more changes that we should be careful with?
Thanks a lot
Click to expand...
Click to collapse
I think its mainly like the HBOOT on the M8, maybe only a name change, but i can't say, because i did not diff the files and i'm not really into digging into
bootloader images, i only do the needed edits and then i'm done.
Mismatched MID and CID
Hello. I just got S-off on my HTC one M9 Developer Edition in order to flash this firmware, but found (through getvar all) that my MID and CID are not the same. Why is this, and is there a way to fix it?
MID: OPJA11000
CID: BS_US002
BananaMasamune said:
Hello. I just got S-off on my HTC one M9 Developer Edition in order to flash this firmware, but found (through getvar all) that my MID and CID are not the same. Why is this, and is there a way to fix it?
MID: OPJA11000
CID: BS_US002
Click to expand...
Click to collapse
Of course they're not the same it wouldn't be good for your device if they were.
MID: a combination of numbers, letters and/or additional characters that identify your the device (as for example a HTC M9)
CID: a combination of numbers, letters and/or additional characters that identify the country of origin of your device and whether it's branded and sold by a carrier or not.
For example the MID and CID of an european M9 which is unbranded and sold in Germany are 0PJA10000 (that's a zero at the beginning not an O) and HTC__102.
Edit: Both, your MID and your CID, are the correct ones for the developer edition.
Sorry
Flippy498 said:
Of course they're not the same it wouldn't be good for your device if they were.
MID: a combination of numbers, letters and/or additional characters that identify your the device (as for example a HTC M9)
CID: a combination of numbers, letters and/or additional characters that identify the country of origin of your device and whether it's branded and sold by a carrier or not.
For example the MID and CID of an european M9 which is unbranded and sold in Germany are 0PJA10000 (that's a zero at the beginning not an O) and HTC__102.
Edit: Both, your MID and your CID, are the correct ones for the developer edition.
Click to expand...
Click to collapse
I didn't mean mismatched as in not the same, I meant as in unable to flash this firmware for that reason (that they do not match any provided MID or CID).
BananaMasamune said:
I didn't mean mismatched as in not the same, I meant as in unable to flash this firmware for that reason (that they do not match any provided MID or CID).
Click to expand...
Click to collapse
Ok, sorry for missunderstanding your post. Well, the x.xx.401.xx firmware versions are meant to be used on the international version of the M9 which can be identified by the supported MID and CIDs. You could change both IDs using fastboot commands but since the hardware of the U.S. variants is slightly different* I don't think it is a good idea to flash this firmware on your phone. In the worst case you might get a nice new paperweight if your phone is not compatible with that firmware. Besides I don't think it'll take too long until the official 1.40.xxx.xx firmware is going to be distributed via the OTA function of the stock HTC rom.
*Blame the fact that U.S. carriers use the CDMA network standard while most other parts of the world are using GSM.
Isn't it GSM?
Flippy498 said:
Ok, sorry for missunderstanding your post. Well, the x.xx.401.xx firmware versions are meant to be used on the international version of the M9 which can be identified by the supported MID and CIDs. You could change both IDs using fastboot commands but since the hardware of the U.S. variants is slightly different* I don't think it is a good idea to flash this firmware on your phone. In the worst case you might get a nice new paperweight if your phone is not compatible with that firmware. Besides I don't think it'll take too long until the official 1.40.xxx.xx firmware is going to be distributed via the OTA function of the stock HTC rom.
*Blame the fact that U.S. carriers use the CDMA network standard while most other parts of the world are using GSM.
Click to expand...
Click to collapse
Last I checked, only Verizon and Sprint are CDMA. Does Developer Edition include that functionality?
BananaMasamune said:
Last I checked, only Verizon and Sprint are CDMA. Does Developer Edition include that functionality?
Click to expand...
Click to collapse
Seems like you're right. As far as I read the developer edition is almost the same as the AT&T version which uses GSM. I thought every U.S. carrier uses CDMA. Nevertheless there must be a difference since your MID differs from the international one. If the hardware were the same there would be no need to use a different MID. Of course you could try installing the 1.40.401.xx firmware using the commands in the hide box but I cannot garantee that it will work or that your phone is still usable afterwards. I would actually suggest you to ask here whether you won't brick your phone by flashing the x.xx.401.xx version.
Code:
fastboot oem writecid <input desired CID without "<" and ">"here>
Code:
fastboot oem writemid <input desired MID without "<" and ">" here>
Edit: Seems like it won't "hurt" your phone to convert it to the international version.
developer editions on GSM
Hi all
i am wondering if the 1.32.617.30 developer firmware and RUU stuff will work on a GSM phone or more to the point a European phone.
The phone in question is mine it is unlocked and s-off and on super sid i just wanna make sure i still get phones call and stuff
any help or advise would be great
thanks guys
Hi thabks..is there any release date for the internatuonal 2.10 ruu??
Hi guys, need help here
I relocked my M9 and make it S-ON. im using firmware 2.7.401.1 I cannot install from any RUU, it seems there is no RUU that match with my firmware. I make mistake should S-ON the device later, but i already did it, so now i cannot use the phone because there is no OS on it.
I try to unlock bootloader, and cannot retrieve the token when using fastboot oem get_identifier_token. I read that since 5.1 you need to turn on unlock option in developer options, but i cannot do that, since the OS is already wiped
Is there any solution for this ?
Thanks.
when will we have the ruu zip 2.10.401.1 so we may be able to apply the SDCARD method to have a full clean stock flash?
I would like to have flashed in this way instead of going all the hard way in flashing ruuzip stock 1.40 and then upgrading by ota´s.
Thanks for all efforts, Nepht Legion.
need help to remove red text
Hi,
I have a HTC m9 asian variant ( on the download menu i get 2.1.709.1) . I have an unlocked bootloader, twrp , root, S-off, supercid installed.
I am running Maximus 6.0 rom based on 2.1.401.
I need to get the red text removed and have tried all the mentioned ways via adb to no success. I have very limited knowledge in this area, Can someone please help me ?
Thanks in Advance.
hi peep's, can we downgrade firmware with s-on and locked boot-loader. or do i need s-off and unlocked boot-loader sorry noob to htc devices regard's Joe.
joecool666 said:
hi peep's, can we downgrade firmware with s-on and locked boot-loader. or do i need s-off and unlocked boot-loader sorry noob to htc devices regard's Joe.
Click to expand...
Click to collapse
hi, you need s-off and a locked bootloader to be able to do that
maxx2210 said:
hi, you need s-off and a locked bootloader to be able to do that
Click to expand...
Click to collapse
okay thanks for your time and help regard's Joe.
Hi All,
Apologies if this is the wrong thread to post this in, just wanted to find out if anyone else has tried to manual install an ota on a M9 s-off.
I copy it to my SD and select to install it via stock recovery. It checks the file and starts the update and not once have i spotted an error, but once it is back up and running android, it is still on the old version.
I'm currently trying to go from 2.10.401.1 to 2.10.401.180, and if I go to aboot, it actual says the new version, but the OS version is still the old.
I would seem that the system partition isn't being updated.
Is there something i'm doing wrong? I tried the usual, googling and searching xda, but haven't found a solution yet.
Thanks
Sent from my HTC One using Tapatalk
Anyone can tell me how to extract the firmware from an OTA zip so I could upgrade my M9 firmware while being S-on? Thank you
Sent from my HTC One M9 using Tapatalk
http://forum.xda-developers.com/showthread.php?t=3378388
Sent from my HTC One M9 using XDA-Developers mobile app
I recently got my hands on a One M9 but I'm having trouble updating anything on it. I check for updates and it says there aren't any available. However, my software version is 1.14.531.1, which is older than anything I've seen in any threads anywhere.
Here's the readout from fastboot getvar all:
kernel: lk
product: htc_himaul
version: 1.0
vzwisLTE:
vzwmid: HTC
max-download-size: 800000000
imei:
battery-status: good
version-main: 1.14.531.1
boot-mode: download
version-bootloader: 1.0.0.0000
mid: 0PJA12000
cid: 11111111
It doesn't say it here, but the phone is s-off.
I started by following the instructions at Cyanogenmod: unlocked, installed TWRP, installed ROM. However, it wouldn't install the ROM. It failed at the point where it tries to verify the device. I changed the recovery to the Cyanogenmod recovery and tried again, but that didn't work either. After a bit of reading, I thought that perhaps I needed to update the bootloader and that a RUU update might do the trick. I got the most recent one from HTC and ran it. It stalled where it says "sending" at 0%. I put the ROM.zip on the SD card to try it that way. That also failed. I relocked the bootloader and tried the RUU again with the same result.
I've wondered if I need to update the firmware per this thread http://forum.xda-developers.com/one-m9/development/firmware-t3068243 but I'm still new to the HTC world and not sure if that's it or if I'm just guessing. The firmware files I found there are much smaller than I expected, so I'm not sure what exactly they will update or if they'll fix the problem or just make it worse.
Can anyone tell me where to go from here, or at least point me in the right direction?
You can't flash offical firmwares unless your phone is stock. I think you should be ok flashing unsigned zips though. I couldn't tell you if htc do incremental or if you can just flash the latest. Flippy's thread might shine a light on something.. Your Cid is supercid.
Beamed in by telepathy.
So, are you saying that if I go back to the stock recovery that I should be able to use the RUU to update everything? There are a bunch of stock recoveries here, but none of them match my phone. The oldest ones there are several versions newer than mine and none match my CID. Can I still use one of them or do I need to find one that matches my phone exactly?
When I got the phone there was an SD card in it with a 0PJAIMG.zip file and a text file with a very long name with the software version (1.14.531.1) in it. Fortunately I saved them. I put those files back on and tried flashing that 0PJAIMG file and this time it worked. It seems to have removed the recovery I put on it and now it looks completely stock, with a locked bootloader and everything. Updating with the latest RUU still doesn't seem to work, however. It's still stalled at "sending" and 0%.
I would like to try a different RUU that's a smaller jump, but I haven't had any luck finding one yet.
OTA updates are incremental. A RUU on the other hand contains the whole firmware that has been distributed for its SKU until the point that RUU got released. Besides it contains the whole system. That's why RUUs are so big.
Sneakyghost's files lack some parts of the official firmware packs since they're not meant to get flashed if you want to get back to stock. They're meant to get flashed if you want to update your phone's firmware without reverting it's system back to stock since this way is less time consuming if you want to flash a new custom rom afterwards. That's why they're so much smaller than a RUU. Besides, they're unsigned and you won't be able to use them without S-OFF.
I personally don't like the *.exe versions of RUUs since they use fastboot and many users aren't able to set up their adb/fastboot environment correctly. Therefore, I neither support flashing RUU.exe files nor fastboot flashing of RUU.zip files. However if you extract the RUU.zip from the latest x.xx.531.x RUU.exe you could flash it via a SD card. I don't have a direct link to a guide for the extraction at the moment but there should be several here on xda which you should be able to find via google. It doesn't matter if they're written for an older HTC phone since the steps you need to do are always the same. Instructions for flashing a RUU via SD card can be found in my google sheet (which is linked in my signature).
And one last thing: The SCID prevents the M9 from installing OTAs. Therefore, you should revert it back to its original CID if you want to install any OTA.
Personal opinion: Since you can't use RUUs with a different MID than the one of your phone although you use the SCID (that was possible on older HTC phones) and you aren't able to install OTAs if you use it (that was possible on older phones, too) I personally don't think that there is any benefit left in using it.
Edit: I forgot to mention that there is a dedicated forum for the T-Mobile US M9 here on xda which can be found with the xda search function. You might find the files you need over there. Due to that other forum the T-Mobile US variant of the M9 isn't that much supported here in the forum for the international variant.
Sent from my HTC One S using XDA Labs
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
drfarmkid said:
Thanks for the info on the T mobile forum. I wasn't aware of that and thought this was the only forum for the M9 here. I'll look for it.
I've already tried using the SD card method and that also failed.
I haven't changed the CID. It was the superCID when I got it. I don't think the previous owner changed it either because the phone seems unused. It still has the barcode sticker on the back and it's clearly be barely handled at all. The phone was originally a test unit or something because it has a serial number engraved on the front and it runs some HTC reporting software. It's rooted out of the box. I'm trying to replace the ROM to get rid of that extra software. I just mention that to explain why it's already rooted, s-off and superCID.
Click to expand...
Click to collapse
I would say the phone is modified. As far as I know, test units don't need S-OFF or the SCID since they simply use different firmware versions than normal units. You can change every version of the M9 into a test unit by applying for HTCs beta program.
What was the error that got shown when the SD card method failed? Did you try to flash the correct RUU.zip for your phone? As mentioned before your MID needs to match even if the phone has the SCID. Therefore, you can only use x.xx.531.x RUUs.
Edit: I forgot to mention that every S-OFFed device runs that reporting software you mentioned if that device is running the stock rom. That Software gets triggered by the S-OFF flag.
Sent from my HTC One S using XDA Labs
Well, I managed to find the 1.32.531.33 RUU in the forum for the T-mobile variant (thanks flippy498 for bringing it to my attention) and that ran just fine. Once that was done I tried running the RUU I downloaded earlier from HTC (3.39.531.31) and it worked fine. It seems the problem was indeed that I just needed something that was a smaller jump. I've seen no mention of any software version earlier than 1.32 anywhere in this forum, so I wonder if my phone was an early test unit or something that the version 1.14 mine had was an earlier pre-release version or something and that is why I had the problems I did.
Thanks for the info regarding the reporting software running on all s-off phones. I saw something about red text in other threads and wondered if that's what it referred to. Now I know.
Hi, everybody, This is my first thread in this wonderfull comunity.
I own a HTC one m9 Hima UHL
-Android 5.0.2
-Sense 7.0
-Soft. version: 1.10.709.2
-MID: 0PJA11000 (the original was 2PRG10000)
-CID: 11111111 (the original was HTC__621)
-What is really great is that I GOT S-OFF AND BOOTLOADER UNLOOKED (also rooted by KINGO app)
As the title says I can boot into android and use my phone normally, but due to a several tries to update my phone to android Nougat, I surelly did something wrong
-RUU.EXE NOT WORKING (I just tried with RUU1.36.709.3.exe)
Not because of the version, is bause I can not enter in download mode, afeter running the wizard it just reboot the device.
-I DO CAN ENTER TO BOOTLOADER MODE
But anithing to do from here, if I go to to recovery (latest TWRP installed when download mode still working) or download mode, It goes to the same place "nowere", just appear a message bellow about flashing unoficial Rom, and legal stuffs, etc......
PLEASE ANY HELP (about something not tried yet) WILL BE TOTALLY APPRECIATE
I JUST WANT TO TAKE MY PHONE TO STOCK AGAIN (keeping the s-off and boatloader)
PS:
I read that once getting s-off and bootloader unlocked, it would be normal to "Cross-Flash firmware", so what I was trying to do before messing all up was to install a different firmware (different SKU or region, e.g. 3.x.617.x), and once there apply the recent released 4.19.617.1. (If somebody can correct me about this as well it would be great, but my priority now is to reset my phone to factory, no problem about personal data loss)
jhon222 said:
Hi, everybody, This is my first thread in this wonderfull comunity.
I own a HTC one m9 Hima UHL
-Android 5.0.2
-Sense 7.0
-Soft. version: 1.10.709.2
-MID: 0PJA11000 (the original was 2PRG1000)
-CID: 11111111 (the original was HTC__621)
-What is really great is that I GOT S-OFF AND BOOTLOADER UNLOOKED (also rooted by KINGO app)
As the title says I can boot into android and use my phone normally, but due to a several tries to update my phone to android Nougat, I surelly did something wrong
-RUU.EXE NOT WORKING (I just tried with RUU1.36.709.3.exe)
Not because of the version, is bause I can not enter in download mode, afeter running the wizard it just reboot the device.
-I DO CAN ENTER TO BOOTLOADER MODE
But anithing to do from here, if I go to to recovery or download mode, It goes to the same place "nowere", just appear a message bellow about flashing unoficial Rom, and legal stuffs, etc......
PLEASE ANY HELP (about something not tried yet) WILL BE TOTALLY APPRECIATE
I JUST WANT TO TAKE MY PHONE TO STOCK AGAIN (keeping the s-off and boatloader)
PS:
I read that once getting s-off and bootloader unlocked, it would be normal to "Cross-Flash firmware", so what I was trying to do before messing all up was to install a different firmware (different SKU or region, e.g. 3.x.617.x), and once there apply the recent released 4.19.617.1. (If somebody can correct me about this as well it would be great, but my priority now is to reset my phone to factory, no problem about personal data loss)
Click to expand...
Click to collapse
First of all: Please reduce the size of the text in your post. It's hard to read.
You can flash RUUs for different regions with S-OFF but you don't own a M9. The M9 has 0PJA***** model IDs. Your phone's original model ID is 2PRG1000. It's probably a M9+ or a M9+ Prime Camera edition or something like that. These devices are completely different than the M9. Therefore you shoudn't flash any M9 files on your phone unless you want a fancy new paperweight.
I recommend you reverting your MID and your CID back to their original values and try to flash a RUU for your device. (I don't know whether there is one you could use. I don't own your device and therefore have no knowledge about the file that are available for it.) If you can't find a suitable RUU you'll need to contact Llabtoofer's RUU Service.
Flippy498 said:
First of all: Please reduce the size of the text in your post. It's hard to read.
You can flash RUUs for different regions with S-OFF but you don't own a M9. The M9 has 0PJA***** model IDs. Your phone's original model ID is 2PRG1000. It's probably a M9+ or a M9+ Prime Camera edition or something like that. These devices are completely different than the M9. Therefore you shoudn't flash any M9 files on your phone unless you want a fancy new paperweight.
I recommend you reverting your MID and your CID back to their original values and try to flash a RUU for your device. (I don't know whether there is one you could use. I don't own your device and therefore have no knowledge about the file that are available for it.)
Click to expand...
Click to collapse
Dear sir, @Flippy498
Im really greatful for your answer, I can not understand why I did not see what is obvious, It is not the model I thought...
Besides de MID, the product is not Hima, but HIMARUHL, the ram 2gb and Camera 13mp... (yeahh Im very silly)
I searched over Internet and badly there is not too much information about this especific MID number (2PRG10000), wich I think now belonges to a "HTC ONE M9E". Beyond the fact that there is a RUU available or not, I think I can not install one, because once an ruu.exe is runned this one tried to enter to download mode, wich is unavailable, then reboot and throw the error "USB communication failed", Before messing up the phone, the RUU.exe throwed the "signature error" WICH I UNDERSTAND NOW, because I was trying tu run the wrong one; so I appreciate if you suggest me another way different to ruu.exe installing.
Thanks for your great attendance.
jhon222 said:
Dear sir, @Flippy498
Im really greatful for your answer, I can not understand why I did not see what is obvious, It is not the model I thought...
Besides de MID, the product is not Hima, but HIMARUHL, the ram 2gb and Camera 13mp... (yeahh Im very silly)
I searched over Internet and badly there is not too much information about this especific MID number (2PRG10000), wich I think now belonges to a "HTC ONE M9E". Beyond the fact that there is a RUU available or not, I think I can not install one, because once an ruu.exe is runned this one tried to enter to download mode, wich is unavailable, then reboot and throw the error "USB communication failed", Before messing up the phone, the RUU.exe throwed the "signature error" WICH I UNDERSTAND NOW, because I was trying tu run the wrong one; so I appreciate if you suggest me another way different to ruu.exe installing.
Thanks for your great attendance.
Click to expand...
Click to collapse
Your phone seems to have a mediatek processor. Those devices need to get handled a bit different than snapdragon devices. However, I absolutely have no experiences with mediatek devices. If I were you I'd contact the service I linked in my earlier post...
Dear XDA developers, professionals and programmers:
Recently I came across a good deal (HTC M8 in mint condition) and bought it. It was running Android 4.4.4 and I was happy with it till I read that it could be updated to Marshmallow. I followed a few links and after some time discovered that it was originally bought from the USA and locked to AT&T even though the installed rom was WWE. Stupidly I downloaded Marshmallow update for AT&T (RUU) from the HTC website and ran the installer. The installer completed successfully and the phone now runs Marshmallow with Sense7.
Since the rom was filled to brim with useless AT&T crap that does not work outside AT&T network I decided to switch to developer WWE rom but the RUU refused to install on the phone (I have S-Off)
After doing a bit more reading I discovered it was because my new rom has a software number 6.20.502.5 while the RUU I would like to install has a software number of 6.12.1540.4
I googled and googled and searched and searched but could not find a single tutorial to explain how I can replace my current rom with the WWE version which has less bloatware and takes it easy on the RAM.
Can someone kindly explain (or redirect me to a link) of how to downgrade HTC M8 from image version 6.20.502.5 to image version 6.12.1540.4 or in layman's terms how to replace AT&T rom with Developer rom? BTW both roms are Marshmallow. I do not wish to install TWRP or CM so if there is a way besides this I'd be grateful. If not then I don't see any other options and I'd still be grateful
Awaiting your generous replies
What you want is not really a "downgrade" per se. While the AT&T version number is "larger" than the Dev Ed (6.20 versus 6.12), that is mostly just because it came later due to AT&T's slowness in approving the software. I don't think there is much (if anything) that is actually "newer" or "updated" in the AT&T stock ROM (versus Dev Ed). It just has (as you know) all the AT&T branding and bloatware crap.
What is keeping you from flashing the Dev Ed RUU 6.12.1540 is that your carrier ID (CID) needs to match the RUU (even with s-off). Therefore, you need to change your CID to that of the Dev Edition (or alternately SuperCID), which is easy since you already have s-off. You will however need root to do this, so either flash TWRP and SuperSU/Magisk to root, or you can run adb shell with run while booted to TWRP. Either way, you will need to install TWRP: https://forum.xda-developers.com/htc-one-m8/general/change-wwe-m8-to-dev-edition-ota-t2826567
No need to change the Model ID (MID) since the AT&T version and Dev Edition have the same MID.
After that, you should be able to run the Dev Ed RUU.
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Simply reboot to bootloader/fastboot then run command
To Dev Ed CID
fastboot oem writecid BS_US001
To SuperCID
fastboot oem writecid 11111111
Can't remember if this only can be done on unlocked bootloader. If can't, try this command first
fastboot oem rebootRUU
the follow by the above.
If still can't then need a unlocked bootloader to proceed.
ckpv5 said:
Sorry .. correction. No need root/twrp to change CID, only change MID need these.
Click to expand...
Click to collapse
Ah yes, obviously I was mixing up my methods to change CID versus MID.
Thanks for clarifying, yet again.
Thank you
Many thanks to you gentlemen for your generous assistance and helpful instructions. I really appreciate it. All the best
Update
Good day all:
Sorry to bother again but it failed again! I downloaded fastboot adb and followed the procedure, put the phone in fastboot mode and the CID was already 11111111 and still it refused to accept the RUU. Please find attached a photo of my fastboot screen, hope it can help determine where the problem is on my phone. [ The following errors occurred with your submission:
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!] Site refused to allow me to attach the photo link so I'll just write everything here
*****Software Status - Official******
******LOCKED******** (Even though I can use a non AT&T sim normally)
MS_UL_CA PVT SHIP S-OFF
CID~11111111
HBOOT - 3.19.0.0000
Radio - [email protected](long number)
OPENDSP - v56.2.2. (loooooooong number)
OS-6.20.502.5
eMMC Boot - 2048MB
*end of pic*
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Can any of you good gentlemen help me out a bit more? I'm willing to answer any questions to further clear the picture of my predicament.
Thank you again
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
ckpv5 said:
Bootloader is fine, still ATT.
Explain more on the error that you have when you tried installing RUU.
Do note - to run RUU you need PC with USB 2.0;
Latest htc usb drivers which you'll get when you installed latesr htc sync manager (uninstall sync manager but leave all drivers to proceed RUU installation)
Click to expand...
Click to collapse
Thank you for your reply:
the RUU I'm trying to install is the developer RUU that I downloaded off the HTC official website. It is the same website I downloaded the AT&T RUU from which installed fine, upgrading the phone's OS from Android 4.4.4 to Android 6.0.
I have several laptops each running a different OS (Windows 7 which I use mostly and have been using for this process) Windows 10, Linux and Solaris.
I did download and install HTC Sync but disabled it's auto run when I noticed every time I plug my phone in it pops up. So that's disabled not uninstalled, but it didn't interfere in the RUU installation of the ATT update and it doesn't pop up when I try to install the developer update.
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Sir Lucifer said:
On the official HTC site in the support section where they post the RUUs it states the following.
"Before you proceed, please confirm that this software upgrade to 6.12.1540.4 is a newer version than what is currently loaded on your device. If it is the same version, there is no need to reload the software. Navigate to the Home screen then tap All apps > Settings > About and locate the Software information . If your Software number is less than 6.12.1540.4 , you should proceed with the upgrade." end of quote
This paragraph is what let me to believe it is the software version that is stopping me from changing RUUs and why I called this post a downgrade (even though I know it's not)
Click to expand...
Click to collapse
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
Sir Lucifer said:
The Error get is as follows:
Upon running the RUU it does all the necessary checks and then asks me if I would like to install the update, I click on "I Agree" and next, then it puts the phone in boot mode (black screen with HTC written in grey) and after it begins the process by popping up a screen that says: Current info about your Android phone: Image Version: 6.20.502.5 select one below and the update button. After I click on it another screen pops up: Verify that you want to update the Rom version from image version 6.20.502.5 to image version 6.12.1540.4 Clicking on Next another windows shows explaining what happens when I click on Next. When I click next it puts the phone in boot mode and begins by Reading header, sending............................................. then it pops another screen that says update failed and I have to click on recovery and press the power button on my phone for 10 seconds to turn it off
Click to expand...
Click to collapse
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Have tried it 5 times already, results are the same. I'm downloading the RUU again, maybe my download was corrupt. Will get back to you later with any results. Thank you for your patience and time. Much appreciated
redpoint73 said:
You can't really take the "official" HTC info literally, anymore. By having s-off and SuperCID, you are so far off the "official" path, that most of the rules no longer apply.
S-off bypasses version check (flashing older RUUs is allowed). In fact, you can RUU all the way back to Kitkat if you wanted with s-off (not recommended - just making a point).
---------- Post added at 09:56 AM ---------- Previous post was at 09:52 AM ----------
The RUU stalling out while "sending" is a common bug. Did you simply try running the RUU again? A lot of times, it will work on subsequent attempts.
The fact it got that far, means to me that it passed (or bypassed) any version or CID checks. Otherwise, it never would have gotten to the point of "sending". Instead, it would have told you something like "Error 140" with a description of what the problem was, and aborted the install before ever "sending".
Click to expand...
Click to collapse
Maybe my downloaded RUU is corrupt, I'll download another time and if it gives me the same problem I'll look for another source. I will keep you posted, thank you very much good man.
RUU Broken on HTC's website
Dear all:
After downloading the developer RUU for the second time and trying to install it again (Marshmallow for those of you who have just joined us) off the HTC support site I failed miserably at changing my firmware using that RUU. After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Sorry for wasting all your time gentlemen. I am very grateful (and very lucky) having assistance from good people like yourselves who have taken from their time to help a complete stranger. Much obliged gentlemen. And thank you all again
Cannot be the RUU is broken.
Another way to do this :
1. Install Dev Edition firmware. You can get the fw_6.12.1540.4.zip from - https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
2. Instead of using RUU exe, you can use RUU zip (rom.zip) to install RUU. I remember long time ago someone had same problem like you. Asked him to use zip format RUU and it was successful.
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
You can get your own RUU.zip which is actually rom.zip yourself. Just run RUU.exe (no need to connect phone). Once it opens the agreement page, go to %temp% thru your search/run windows menu.
It's better to clear your temp directory first so easy to find 2 newly created folder when you run RUU.exe
The rom.zip is inside one of the folder. Copy that to your desktop.
Then follow this on how to install - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
There are 3 methods but I prefer the htc_fastboot because easily can see any error if any.
So step 1 firmware & step 2 RUU (rom.zip)
Sir Lucifer said:
Dear all:
After a series of searches on the internet and darknet I came across a post on reddit dot com titled M8 marshmallow RUU from HTC is broken and the article was dated last year. Searching further I found a similar post on a Chinese website that stated the same thing. So in conclusion the developer RUU on HTC's site is damaged as confirmed by a few users/developers on both reddit and the Chinese website.
Click to expand...
Click to collapse
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Downloaded Again
redpoint73 said:
Did those threads specifically mention RUU 6.12.1540.4? If not, then you realize this device has dozens of RUUs for the M8? Most of which have been confirmed many times over to work properly.
My experience, is that 95% of the time, the problem with RUU running is with the PC. Try re-installing HTC drivers, different USB port, turn off USB 3.0. Also try a different USB cable, or if possible another PC.
Downloading the RUU again (as you tried) is not a bad idea. They do sometimes get corrupted while downloading. But if you download another time, and it still fails, the problem is probably not the RUU.
You should also verify your PC has Visual C++ installed, as the RUU exe requires it. The error your are encountering doesn't sound like the C++ problem. But it won't hurt to verify, anyway. Link here, but confirm it's the right install for your Windows version: https://forum.xda-developers.com/showpost.php?p=60021580&postcount=4
Or of course, you can use the RUU.zip method stated by ckpv5, which avoids all the of the above possible pitfalls. You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
ckpv5 said:
I believe there is RUU.zip somewhere on XDA. Can't search now as I'm on mobile.
Click to expand...
Click to collapse
redpoint73 said:
You'll need to search for the 6.12.1540.4 zip, as I don't know where it is off hand, either.
Click to expand...
Click to collapse
Sir Lucifer said:
I did download the developer RUU again, I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
I am an electronics engineer so yes my laptops are always up to date on flash, oracle, C++, Perl, Java, etc
Click to expand...
Click to collapse
I have the RUU.zip
You can download it from here :good:
Sir Lucifer said:
I also downloaded the Metro PCS RUU which has a software number of 6.20.531.5 and it installed just fine but refused to see the sim card so I reinstalled AT&T
Click to expand...
Click to collapse
That is the T-Mobile RUU. MetroPCS merged with T-Mobile, so it's a bit one and the same. But most everyone will call that RUU/version T-Mobile. It will change band support (as flashing any other RUU will). So if it was working before on the AT&T RUU(or Dev ED will support the same bands) I would not mess with random RUUs, unless we suggest them specifically.
hello guy's, i'm a real noob with htc or "rooting" etc and i'm facing a problem. I just bought a htc one m9 with android 6. I think its refurbished because it look like new but the left speaker is louder than the right, and are not loud at all. So I thought I would update it for maybe solve the problem, but I have the update notification and when i click on it, it say the sytem is not stock so can't update. The phone isn't root so i don't know why i'm facing this, so after a long research i did many things like try to install RUU..exe or with RUU;zip and no one want to install. At one moment i change the CID and the OTA begin the update by itself (don't show the "not stock system" message anymore" but stop at 25% and reboot. I'm really confused and don't understand anythings, last thing i did is unlock the bootloader but doesn't change anythings. Is it possible to reinstall a pure stock version ? and after update it ? I am not interested by rooting the phone, i just want pure stock version and be able to update the phone, is it possible to get help? Thanks !
What's the current CID of the phone? Which firmware version is currently installed? Which model name is engraved on the backside of the phone? Is the phone S-ON or S-OFF?
Please read the ReadMe thread in the general section if you don't know how to answer any of the questions.
Flippy498 said:
What's the current CID of the phone? Which firmware version is currently installed? Which model name is engraved on the backside of the phone? Is the phone S-ON or S-OFF?
Please read the ReadMe thread in the general section if you don't know how to answer any of the questions.
Click to expand...
Click to collapse
current cid : htc 001 (don't remember what it was before i change it, something like 1111111)
firmware : 3.35.401.12
model : nothing on the backside (just htc) but on download mode i see "product: htc_himauhl"
S-OFF
Ok. The SuperCID (11111111) was the culprit of your initial problem. On older HTC phones it was a way to unlock kind of a region free mode. On the M9 however, that CID prevents official updates from being installed.
Is your current CID really htc 001? Or is it HTC__001? Only the latter one is written in the legit format. The former one won't work.
HTC__001 is one of the CIDs that would match your current SKU (401).
The model name in download mode can be changed via RUUs. As long as no one changed the backplate, only the engraving on the backside of the phone shows the true model name. The engraving is quite small on the downer part of the backplate. Can you please take another look and see if you can find it? The ReadMe contains some commonly asked questions. There should be one that covers the engraving.
We should only proceed with flashing RUUs if we know the model name of your phone. It's not wise to flash GSM RUUs on a CDMA phone or vice versa.
Flippy498 said:
Ok. The SuperCID (11111111) was the culprit of your initial problem. On older HTC phones it was a way to unlock kind of a region free mode. On the M9 however, that CID prevents official updates from being installed.
Is your current CID really htc 001? Or is it HTC__001? Only the latter one is written in the legit format. The former one won't work.
HTC__001 is one of the CIDs that would match your current SKU (401).
The model name in download mode can be changed via RUUs. As long as no one changed the backplate, only the engraving on the backside of the phone shows the true model name. The engraving is quite small on the downer part of the backplate. Can you please take another look and see if you can find it? The ReadMe contains some commonly asked questions. There should be one that covers the engraving.
We should only proceed with flashing RUUs if we know the model name of your phone. It's not wise to flash GSM RUUs on a CDMA phone or vice versa.
Click to expand...
Click to collapse
real cid is : HTC__001 (from getvar all)
I search everywhere with camera and there is nothing about the model, the person I bought it from told me it was refurbished, maybe thats a false case ? am I stuck ?
It's up to you to decide whether you want to try flashing the 3.35.401.12 RUU or not. All clues imply that you have a 0PJA10000. However, we don't know for sure.
In case you want to proceed: Check the MD5 sum of the file that you can find in the ReadMe thread. Flash it with the instructions for the SD card method.
Afterwards the phone should be working normally, again. Unless it's not a CDMA variant. In the latter case you would at least get problems with network reception.
Edit with another thougt that comes to my mind: What's the fastboot getvar result for your MID. Since the refurbisher used the SCID they most likely didn't know that the M9 behaves differently than older HTC phones and probably didn't change the original MID.
the getvar mid is : 0PJA10000 but i change it too and don't know the initial.
I will try the process, i don't understand what you mean by "check the MD5"
is this file is good ? : https://androidfilehost.com/?fid=23991606952597788
Is it possible to flash it with the pc instead of sd card ? if it's mandatory the sd card I will buy one
Well, if you manually changed the MID, didn't write down the original MID and there's no engraving on the backside of the phone then there's no way to know for sure which variant you own.
C.f. https://en.m.wikipedia.org/wiki/MD5
Tl;dr: Check whether the file didn't get broken during download (e.g. due to connectivity issues). The ReadMe thread suggests useful programs for that purpose.
Flashing broken files might lead to unrecoverable bricks; especially on S-OFF phones. "Good" file hosts like AndroidFileHost will always mention the reference MD5 value for their downloads.
The SD card method is the most fail safe method for flashing RUUs on a M9. That's why I recommend to use it, always. You'll want to get a card that has not more than 32 gb due to the needed format. Those cards should cost less than 10 €.
Edit: You can't use the RUU that you linked. Please read the ReadMe thread, thoroughly. That RUU uses a different encryption key. Everything you need can be found in the ReadMe thread. Trying to flash just any random RUU is quite dangerous on a S-OFF device due to the security checks being turned off. You might risk a brick.