Where can I find a firmware update for hima and how do I update it??? Trying to upgrade to nougat.
Donnie267 said:
Where can I find a firmware update for hima and how do I update it??? Trying to upgrade to nougat.
Click to expand...
Click to collapse
Hi, all the needed information and related download links you can find it here going to Post #6 and then at RUU Section.
Marko Indaco said:
Hi, all the needed information and related download links you can find it here going to Post #6 and then at RUU Section.
Click to expand...
Click to collapse
I've tried using ruu. Keep getting error 132. Tried it in bootloader, download and recovery.
Please search for the key word "encryption key" in that post or read the post with the common RUU errors.
Sent from my HTC One M9 using XDA Labs
Thanks guys. Any chance y'all know if the firmware can be flashed with TWRP?
RUUs can't get flashed via TWRP. However, there are several flashing methods explained in the RUU section.
Sent from my HTC One M9 using XDA Labs
What about firmware? Those can be flashed with twrp, right?
Not really. TWRP doesn't have access to the partitions that would be needed to be overwritten. TWRP only has access to the system, the recovery partition and the boot partition. You might want to read the article that is linked as "the difference between rom and firmware" in the further reading section.
Once I have the firmware extracted, could I use adb to flash the firmware?
No, since ADB only works if the phone is booted to modes in which it won't accept the firmware files (the system or the recovery mode).
Why don't you keep things simple and use an OTA?
Sent from my HTC One M9 using XDA Labs
Ota keeps giving me an error saying my phone has been modified and ruu keeps giving me error 132 in both download and bootloader modes.
As written before, that error 132 occurs due to the new encryption keys.
You need to flash the RUU for your current firmware or to restore an "untouched" TWRP backup of that version and then you can take the OTA.
Sent from my HTC One M9 using XDA Labs
How am I supposed to ruu when it keeps giving me errors?
The newer 4.x RUU uses different encryption keys than your phone. You need to flash the RUU for your current firmware.
Sent from my HTC One M9 using XDA Labs
I know that. I keep asking for the ruu for my firmware but jeep getting the runaround instead of what I'm asking for.
That's what I'm running. Which ruu do I need?
Donnie267 said:
I know that. I keep asking for the ruu for my firmware but jeep getting the runaround
Click to expand...
Click to collapse
Really? Then, maybe you have to read rules FIRST instead of getting the runaround. And then read as well the ReadMe Thread (as already warned you).
Donnie267 said:
instead of what I'm asking for
Click to expand...
Click to collapse
Did I understand wrong or this seems like an order?
I've read the Readme a dozen times. Replied to the Readme asking questions. Nobody can give me a straight answer. How hard is it to tell me which file I need so I don't have to download every single file in the forum soft bricking my phone over and over again? All I'm asking is which file I need given my firmware. Which I've posted screenshots of.
help!
Okay,before any of you start. Yes I've read the forum Readme. Yes, I've read the rules. I've asked this question at least a dozen times on multiple threads and absolutely nobody can give me a straight answer telling me to read the readme/rules. And it's really getting frustrating. So here's my question one more time. How do I update my phone to nougat? Yes I've tried ruu in both download mode AND in bootloader mode AND in recovery mode in all 3 modes, I get error 132. Yes, I tried Ota update through phone settings and keep getting an error saying the my phone has been modified. Here are screenshots of my software info.
Donnie267 said:
I keep asking for the ruu for my firmware[...]
Click to expand...
Click to collapse
And in which of your posts did you mention your current firmware? You didn't even mention which version of the phone you own before 01:03 (MET), today. The fact that you get errors while trying to install OTAs gets mentioned the first time at 23:06 (MET), yesterday. We don't own crystal balls. How are we suposed to know these things?
Donnie267 said:
I've read the Readme a dozen times. Replied to the Readme asking questions.
Click to expand...
Click to collapse
You obviously didn't read a single guide in the RUU section. They all start with the same step:
Boot to download mode and look at the line with "OS" at the beginning for finding out your current firmware version.
The "firmware version" in "settings>about>software information>more" is only the base of the (custom) rom you are running and might therefore differ from the real one in the download mode.
Remember that you can always flash newer RUUs as long as they use the same encryption key as your current firmware. (c.f. the important notes in this post)
Click to expand...
Click to collapse
And a little bit further below in the same post:
Download Links:
Click to expand...
Click to collapse
Donnie267 said:
Nobody can give me a straight answer. How hard is it to tell me which file I need so I don't have to download every single file in the forum soft bricking my phone over and over again?
Click to expand...
Click to collapse
I already explained at the beginning of this post why you didn't get straighter answers. How hard is it to read what got written on the first pages of the ReadMe thread? (And it's not the first time that you completely ignore opening posts of a thread.)
Related
I have an M9 with Eragon rom flashed, which is android 5, if I try to flash ANY other rom, it never boots, I figured it was something about the firmware, but I have absolutely no idea what I'm looking for, I'm using the mexican M9, unlocked, S-ON (i don't really know what any of this means), I have access to TWRP but for the life of me I can't figure out what I need to download or flash, it's really frustrating (and yes, I've used the search funcion but like I said, I don't even know what I'm looking for.
Radamenenthil said:
I have an M9 with Eragon rom flashed, which is android 5, if I try to flash ANY other rom, it never boots, I figured it was something about the firmware, but I have absolutely no idea what I'm looking for, I'm using the mexican M9, unlocked, S-ON (i don't really know what any of this means), I have access to TWRP but for the life of me I can't figure out what I need to download or flash, it's really frustrating (and yes, I've used the search funcion but like I said, I don't even know what I'm looking for.
Click to expand...
Click to collapse
Read through the readme thread at the top of this forum. It has everything you need.
computerslayer said:
Read through the readme thread at the top of this forum. It has everything you need.
Click to expand...
Click to collapse
I did, but what am I looking for? I tried the SD thing and it failed
Radamenenthil said:
I did, but what am I looking for? I tried the SD thing and it failed
Click to expand...
Click to collapse
The rom version MUST MATCH THE FIRMWARE VERSION. If you need to flash stock then you need to get it back to stock condition by following the thread that flippy spent ages on, it is in the general section stickies.
Beamed in by telepathy.
But how do I know which rom version and firmware version I have? and do I have to go back to stock? I don't understand anything about the RUU stuff (i tried downloading one and using the SD method thing to flash it, but it gave me an error)
Radamenenthil said:
But how do I know which rom version and firmware version I have? and do I have to go back to stock? I don't understand anything about the RUU stuff (i tried downloading one and using the SD method thing to flash it, but it gave me an error)
Click to expand...
Click to collapse
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
computerslayer said:
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
Click to expand...
Click to collapse
I found the SKU, it's 600, should I just download that and try to flash it with the SD method thing?
computerslayer said:
The readme thread, particularly the section on RUUs is what you need.
You need to look up your OS version, identify the SKU and match that to the RUUs that are available. Then you can download and apply the correct software to your phone.
The readme thread explains this, step by step. Check it out and post any questions you have from there in this thread.
Click to expand...
Click to collapse
Radamenenthil said:
I found the SKU, it's 600, should I just download that and try to flash it with the SD method thing?
Click to expand...
Click to collapse
I just tried the SD method thing, with the correct SKU RUU, didn't work...
I get
"Failed: -2, 19: fail to flash via downloadzip"
three times, please i'm at a total loss of what to do
Radamenenthil said:
I just tried the SD method thing, with the correct SKU RUU, didn't work...
I get
"Failed: -2, 19: fail to flash via downloadzip"
three times, please i'm at a total loss of what to do
Click to expand...
Click to collapse
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
computerslayer said:
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
Click to expand...
Click to collapse
Also, we're not talking about a phone error - you've got a perfectly working device. The problem is that your firmware is outdated and current ROMs require Marshmallow or Nougat firmware. From the looks of it, your SKU doesn't have any updates available.
Assuming you have correctly identified your SKU as 600, your best bet is to achieve S-OFF and change your phone SKU to the developer SKU so that you can update to the latest firmware for the M9. Keep in mind that you will lose any carrier specific features that may be included in the 600 SKU firmware (such as VoLTE, wifi calling).
Before taking that step, be sure that you've properly identified your SKU - if you turn out to have a CDMA phone/SKU, attempting to apply other firmware will almost certainly brick it.
computerslayer said:
I don't know how to interpret the error code, but perhaps we can rule out the obvious. What is your current OS version?
---------- Post added at 09:42 AM ---------- Previous post was at 09:37 AM ----------
Also, we're not talking about a phone error - you've got a perfectly working device. The problem is that your firmware is outdated and current ROMs require Marshmallow or Nougat firmware. From the looks of it, your SKU doesn't have any updates available.
Assuming you have correctly identified your SKU as 600, your best bet is to achieve S-OFF and change your phone SKU to the developer SKU so that you can update to the latest firmware for the M9. Keep in mind that you will lose any carrier specific features that may be included in the 600 SKU firmware (such as VoLTE, wifi calling).
Before taking that step, be sure that you've properly identified your SKU - if you turn out to have a CDMA phone/SKU, attempting to apply other firmware will almost certainly brick it.
Click to expand...
Click to collapse
I got desperate and I tried another SKU, 599, which had the same CID as mine (but apparently a higher version) and it actually worked, it started flashing and all, i'm on the "Android is starting... Optimizing apps" screen right now, somewhat relieved, I hope it works, I've been at this for like 3 days
and I can't pay for S-OFF, I'm totally broke (and I feel kinda salty because I already paid for that app once lol)
Radamenenthil said:
I got desperate and I tried another SKU, 599, which had the same CID as mine (but apparently a higher version) and it actually worked, it started flashing and all, i'm on the "Android is starting... Optimizing apps" screen right now, somewhat relieved, I hope it works, I've been at this for like 3 days
and I can't pay for S-OFF, I'm totally broke (and I feel kinda salty because I already paid for that app once lol)
Click to expand...
Click to collapse
Interesting and weird. I can't explain why a RUU of another SKU would work on your phone - unless your phone is actually SKU 599 and not 600. I am glad it worked, however!
My guess is that the reason for that being possible is the fact that those two SKUs share the same CID and MID. I don't even know the difference between the two SKUs (assuming that there actually is one). :silly:
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
My guess is that the reason for that being possible is the fact that those two SKUs share the same CID and MID. I don't even know the difference between the two SKUs (assuming that there actually is one). :silly:
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Apparently one is specifically from Mexico (Telcel) and the other one (that worked) was Latinamerica in general...
So now that I'm in stock android 6, how would I go about getting Nougat on it? or rooting? (I don't know if I should make a new thread for this)
Radamenenthil said:
Apparently one is specifically from Mexico (Telcel) and the other one (that worked) was Latinamerica in general...
Click to expand...
Click to collapse
Well, that info is taken from the naming of the RUUs. What I meant was the content. Why would HTC decide to use the same MID and CID for two SKUs. As far as I know this situation is unique. Have you been able to notice any differences of the two RUUs software.
The telcel one didn't work because it was probably too old for your phone. With S-ON downgrades are only possible in some rare cases.
Radamenenthil said:
So now that I'm in stock android 6, how would I go about getting Nougat on it? or rooting? (I don't know if I should make a new thread for this)
Click to expand...
Click to collapse
Not every SKU already received the Android N update. You may need to wait a bit longer.
If your bootloader is still unlocked you can flash TWRP and SuperSU. The correct versions for each firmware version of the M9 are stated in the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Well, that info is taken from the naming of the RUUs. What I meant was the content. Why would HTC decide to use the same MID and CID for two SKUs. As far as I know this situation is unique. Have you been able to notice any differences of the two RUUs software.
The telcel one didn't work because it was probably too old for your phone. With S-ON downgrades are only possible in some rare cases.
Not every SKU already received the Android N update. You may need to wait a bit longer.
If your bootloader is still unlocked you can flash TWRP and SuperSU. The correct versions for each firmware version of the M9 are stated in the ReadMe thread.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
thank you, after that, I should be ok flashing MM roms and stuff?
To sum up i wanted to wipe the date and i "accidentaly"(how can be accidentantaly?well i am an idiot) delete the os of my htc m9. I was stucked in the starting logo for ages.I have acess to download and recovery mode.I tried to flash a custom rom i found in the forums using the twrp all went good it flashed the rom.When it reached the part where it says android application updating 0-189 it did everything.After that it kept showing me the htc logo i could restart shutdown lock and power up and down the volume but nothing else and the logo kept in front.Any idea?can it be fixxed?s-on.Thanks for your time
You need to flash a stock firmware. The same firmware as what was on it before it borked.
Beamed in by telepathy.
shivadow said:
You need to flash a stock firmware. The same firmware as what was on it before it borked.
Beamed in by telepathy.
Click to expand...
Click to collapse
i ve been trying all day.now i flashed a rom the phone will open but it has no signal.cant i just install the stock rom with odin?and be like it was?thanks
So i am in a loop here.I flashed a rom which is not working.Twrp is not working so i cant flash a new rom.Also my pc wont "see" my phone when i am plugging in my phone it does that connect disconnect sound all the time like crazy so i cant install twrp again.Please help me
anon_1993_ said:
So i am in a loop here.I flashed a rom which is not working.Twrp is not working so i cant flash a new rom.Also my pc wont "see" my phone when i am plugging in my phone it does that connect disconnect sound all the time like crazy so i cant install twrp again.Please help me
Click to expand...
Click to collapse
Have you read through the readme thread? One of your previous posts referenced ODIN, which is a Samsung tool. If you've read through the readme thread we will have a common foundation of understanding - and you may discover the solution to your problem there.
It sounds like you need to flash a RUU to your phone. The pre-requisites and guide to doing so are laid out in the readme thread. If you have any questions after reading through it, please post them here and we'll help out as best we can.
i am sorry for asking so much.But in order to flash a RUU it says that you need a rooted device.How i am gonna root my device since i cant connect it to my pc?
anon_1993_ said:
i am sorry for asking so much.But in order to flash a RUU it says that you need a rooted device.How i am gonna root my device since i cant connect it to my pc?
Click to expand...
Click to collapse
Where does my ReadMe thread say what I highlighted in the quote?
Flippy498 said:
Where does my ReadMe thread say what I highlighted in the quote?
Click to expand...
Click to collapse
so i downloaded thr ruu many times but i am keep receiving 22 RU_HEADER_ERROR. what i am doing wrong?
anon_1993_ said:
so i downloaded thr ruu many times but i am keep receiving 22 RU_HEADER_ERROR. what i am doing wrong?
Click to expand...
Click to collapse
Which RUU are you exactly trying to flash (link it please)? What's your current firmware version? Have you checked the MD5 checksum of the downloaded file? What's the size of the SD card you're using? What's its format?
Flippy498 said:
Which RUU are you exactly trying to flash (link it please)? What's your current firmware version? Have you checked the MD5 checksum of the downloaded file? What's the size of the SD card you're using? What's its format?
Click to expand...
Click to collapse
i followed the guide its 32 giga exfat. My firmware is 3.35.401.12 and i am trying to install this one https://pa1.androidfilehost.com/dl/...1_U11440792_97.00.51203G_F_release_signed.zip
That RUU got successfully flashed by S-ON users in the past and it's the correct one for your current firmware. So either the file got corrupted during the download (you didn't mention whether the MD5 checksum matched) or your SD card is broken.
Sent from my HTC One M9 using XDA Labs
sorry for not responding.today i had my day off and tried once again to fix the phone and Ruu is working.It was the cable i went and bought a new genuine one.Atm the phone is blank from Os when ill turn it on it will automatically take me to the bootloader.I tried to run a ruu.exe but i got a 155 error saying i am using the wrong ruu.I locked the bootloader using oem lock to try if that was the problem but aparrently it wassnt. the phone was from Europe and was working with differents sims in greece and uk so i assume its unlocked.Cant i just install a the stock rom with twrp?
I actually won't answer in this thread, anymore. You already got told to read the ReadMe thread and to follow its instructions. That thread clearly explains how to find the correct RUU and how to flash it. Besides, it tells you not to (re-)lock the bootloader and why you shouldn't do so.
If you ignore all these information and prefer to try out wrong RUUs and to relock your bootloader then there's nothing I can do for you.
Flippy498 said:
I actually won't answer in this thread, anymore. You already got told to read the ReadMe thread and to follow its instructions. That thread clearly explains how to find the correct RUU and how to flash it. Besides, it tells you not to (re-)lock the bootloader and why you shouldn't do so.
If you ignore all these information and prefer to try out wrong RUUs and to relock your bootloader then there's nothing I can do for you.
Click to expand...
Click to collapse
thank you and i am sorry for the stupid questions and actions.
Hello,
I wanted to install the newest nightly update. But when I tap "Install" it says "Unable to restart to recovery". Ive got a few questions here:
What causes this and why doesnt the errormessage explain itself?
Can I apply the update myself somehow (Where is it located and how can I apply it)?
Greetings,
Ravior
Honestly, if you don't know how to get to recovery then I highly suggest you stay away from modding android phones.
Beamed in by telepathy.
shivadow said:
Honestly, if you don't know how to get to recovery then I highly suggest you stay away from modding android phones.
Beamed in by telepathy.
Click to expand...
Click to collapse
Did I say anything about that? You assumed that and simply insulted me.
Of course I know how to get there. I did that several times for installing and trying out stuff. But how should I know that I can simply go there and apply the update by selecting it and chosing install. I asked for that information and you didnt gave it to me, instead you where insultive. Had a bad day or what?
can you boot in Recovery via adb (adb reboot recovery)
Have same issue. The other day I tried to go from viperone 3.5, s off, unlocked/rooted, twrp installed 3.0.
After the installation attempt using clean install, got stuck in a bootloop. Finally was able to install a stock rom 5.0 using ruu. S off, unlocked
Now I cannot log into recovery.. I get that splsh screen with red waning text below but the top section in red says cannot load recovery. I tried a few reasons over the last few days, trying fastboot/adb but can not load twrp. Tried everything from 2.8xxx to 3.xxx.
cid is 11111111.
Also tried some other ruu's but says its not for my device, but it is. Unlocked, m9, hima
scratching my head here, I must be missing something
RaviorMetal said:
Did I say anything about that? You assumed that and simply insulted me.
Of course I know how to get there. I did that several times for installing and trying out stuff. But how should I know that I can simply go there and apply the update by selecting it and chosing install. I asked for that information and you didnt gave it to me, instead you where insultive. Had a bad day or what?
Click to expand...
Click to collapse
If had read anything to do with installing ANY rom it will have detailed instructions on how to install it, usually it will tell you how to get to recovery too. Even if it doesn't tell you how to get to recovery it is a google search away.
Spoon feeding is a no-no. You must try to solve issues yourself before asking and refer to the forum for "obtuse" issues.
As for the detailed output of why it failed, usually you get some sort of error code or phrase as to why. If not then you have to start looking into logcat. You will notice that it failed to boot to recovery so manually doing it will resolve that, then you just follow whatever guide you were using after that step..
I understand that things can get overwhelming when flashing devices but it is all part of the learning curve and knowing how to navigate your device is essential before even considering changing anything.
Further more, I didn't insult you. I didn't intend to. It was an honest opinion because if you don't do the basics you WILL "become a cropper", you'll probably brick your device.
Back to basics is my advice before you proceed to mess with ANY device.
bigjailerman said:
Have same issue. The other day I tried to go from viperone 3.5, s off, unlocked/rooted, twrp installed 3.0.
After the installation attempt using clean install, got stuck in a bootloop. Finally was able to install a stock rom 5.0 using ruu. S off, unlocked
Now I cannot log into recovery.. I get that splsh screen with red waning text below but the top section in red says cannot load recovery. I tried a few reasons over the last few days, trying fastboot/adb but can not load twrp. Tried everything from 2.8xxx to 3.xxx.
cid is 11111111.
Also tried some other ruu's but says its not for my device, but it is. Unlocked, m9, hima
scratching my head here, I must be missing something
Click to expand...
Click to collapse
Yup, missing the cid is supercid. No longer valid. Cid and mid must match the firmware you're trying to install.
The bigger issue is not being able to get to recovery at all... Will it go to download mode?.
Obviously you've read flippy's thread and sneakyghosts thread?
Beamed in by telepathy.
Yes those threads brought me back from a soft brick....
I remember back when I first rooted and installed viper there has to be a way to change the cid, isnt there?
Thanks btw
bigjailerman said:
Yes those threads brought me back from a soft brick....
I remember back when I first rooted and installed viper there has to be a way to change the cid, isnt there?
Thanks btw
Click to expand...
Click to collapse
Yes there is, it's done via a command in fastboot but I can't remember if you can do it with just root or if you need s-off too..
Beamed in by telepathy.
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Aint nobody got time fo dat!. It's confusing for idiots like me.. My attention span is... Oo ice cream!..
Beamed in by telepathy.
Flippy498 said:
So, obviously you both didn't read my thread since it contains a guide for changing your CID/MID...
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
No honestly, I re read everything and t is right there, no question and it is appreciated. I was just concentrating on how to get back to a version of TWRP. Finally I was able to do that and still unlocked, S Off and have a TWRP 2.7 but every time I try to go higher I get the cannot boot recovery in the red letters. My bottom line was to install a 7.1.x rom. That is what caused all my original issue, tried to update into 7.1.1 RR Rom and everything crashed. I used a RUU you have in that thread (THANK YOU) and was able to get out of bootloop on RR bootanimation. I am running on stock 5.x, rooted as well.
Is there anyway to still move forward? Do I need to change the CID to match the firmware I choose within the device choices?
Thanks for all your earlier posts and it has become invaluable and thanks for any advice going forward.: good:
TWRP versions above 3.x require your M9 to be at least using firmware 3.x. The same applies to android 6/7 based roms. Either restore the correct CID for your SKU, flash the latest available 3.x RUU for that SKU and then install all missing updates via the software update function of the stock rom or restore the correct CID and look for a full-wipe firmware pack in Sneakyghost's firmware thread (located in the development section). Be aware that his packs don't contain a rom but that shouldn't be a problem at all if you want to install RR, anyway.
i was triying to update mi at&t m9 to the nougat official rom using the Ruu fromj htc web page, first i updated to 3.38.502.41 as the at&t update page says, and then i tried the nougat Ruu, but i keep getting the "error 132: signature error". any idea why this happens?
PS: my device its S-on, carrier unlocked(cant download OTA) and not rooted.
XsaucerX said:
i was triying to update mi at&t m9 to the nougat official rom using the Ruu fromj htc web page, first i updated to 3.38.502.41 as the at&t update page says, and then i tried the nougat Ruu, but i keep getting the "error 132: signature error". any idea why this happens?
PS: my device its S-on, carrier unlocked(cant download OTA) and not rooted.
Click to expand...
Click to collapse
Read this topic - https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
And post #5!
Golv said:
Read this topic - https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
And post #5!
Click to expand...
Click to collapse
Does that means that i can't flash the nougat Ruu? Im s-on and i cant get OTA updates. Maybe using the SD card method.
PS: thanks for the reply.
Sent from my HTC One (M9) using XDA Labs
XsaucerX said:
Does that means that i can't flash the nougat Ruu? Im s-on and i cant get OTA updates. Maybe using the SD card method.
PS: thanks for the reply.
Sent from my HTC One (M9) using XDA Labs
Click to expand...
Click to collapse
You can flash Nougat RUU but you need flash FULL stock signed Nougat firmware for your CID before (all data will be deleted). Then you can flash Nougat RUU for your CID using the SD card method.
Golv said:
You can flash Nougat RUU but you need flash FULL stock Nougat firmware for your CID before (all data will be deleted). Then you can flash Nougat RUU for your CID using the SD card method.
Click to expand...
Click to collapse
Thats the problem i cant flash the stock nougat Ruu
Sent from my HTC One (M9) using XDA Labs
XsaucerX said:
Thats the problem i cant flash the stock nougat Ruu
Sent from my HTC One (M9) using XDA Labs
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=64299817&postcount=5
It seems like HTC changed its encryption keys between firmware 3.x and 4.x. Therefore, you cant flash 4.x RUUs if your phone is currently using a 3.x firmware. You either need to flash a NoWipe/Full-Wipe Firmware Pack beforehand (only possible with S-OFF) or you need to use a 3.x RUU for the same SKU and install the 4.x OTA, afterwards.
Already installed the 3.38.502.41(the prerequisite to get the nougat OTA) but i cant get the OTA, my phone its the at&t m9 but carrier unlocked and s-on
Sent from my HTC One (M9) using XDA Labs
XsaucerX said:
Already installed the 3.38.502.41(the prerequisite to get the nougat OTA) but i cant get the OTA, my phone its the at&t m9 but carrier unlocked and s-on
Sent from my HTC One (M9) using XDA Labs
Click to expand...
Click to collapse
Ever find a solution to this? I have a similar situation.
tiger1999 said:
Ever find a solution to this? I have a similar situation.
Click to expand...
Click to collapse
I'm still waiting for the OTA update to come, asked about this in the readme thread and one of the mods told me that i don't need an at&t service to get the update, just wait.
Ps: you can't update using the Ruu because of the new encryption, have to use the OTA.
Sent from my HTC One (M9) using XDA Labs
Please don't forget that mods are just humans and therefore not all knowing. We make mistakes, too.
I made a further research and it looks like I was wrong. AT&T actually seems to request users to have one of their sim cards inserted if you want their OTAs. Sorry for the bad news. This was the first time that I read about that. (And I thought European carriers would be an annoyance...)
Theoretically, you should be able to install the OTA manually if someone uploads it somewhere or posts HTC's download link. However, it looks like no one uploaded the file or published the official link, yet.
Flippy498 said:
Please don't forget that mods are just humans and therefore not all knowing. We make mistakes, too.
I made a further research and it looks like I was wrong. AT&T actually seems to request users to have one of their sim cards inserted if you want their OTAs. Sorry for the bad news. This was the first time that I read about that. (And I thought European carriers would be an annoyance...)
Theoretically, you should be able to install the OTA manually if someone uploads it somewhere or posts HTC's download link. However, it looks like no one uploaded the file or published the official link, yet.
Click to expand...
Click to collapse
Dont worry about it man, thanks for trying to help! I'll just wait 1-2 weeks and get a go phone sim card from amazon, its just like 2-5 bucks anyways.
Does anyone have OTA backup?
Please could someone upload OTA update? (3.38.502.41 to 4.27.502.7)
XsaucerX said:
I'll just wait 1-2 weeks and get a go phone sim card from amazon, its just like 2-5 bucks anyways.
Click to expand...
Click to collapse
Hi! So did it work for you? You received this OTA with att sim card?
Hi guys.
I'm having the same error (132) signature error.
My device:
UNLOCKED
htc_himaulatt PVT S-OFF
CID: 11111111
LK-1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G_F
OpnDSP-15.6.1.00522.8994_1026
os-3.35.617.31
NO OTA Updates.
Now running 3.35.617.31 trying to update with RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6.exe or any other 4.XX.XXX.X
RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe was applied with no problem but when trying to apply the 4.14.617.6 error (132) shows.
I have downloaded all updates and try to apply:
4.14.617.6
4.23.617.1
4.30.617.2
4.30.617.12
None of the RUUs works, shows error (132)
All RUUs was downloaded from htc / us / support / rom-downloads
Can someone give me some hints on how solve this issue???
Thanks in advance.
mollon said:
Hi guys.
I'm having the same error (132) signature error.
My device:
UNLOCKED
htc_himaulatt PVT S-OFF
CID: 11111111
LK-1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G_F
OpnDSP-15.6.1.00522.8994_1026
os-3.35.617.31
NO OTA Updates.
Now running 3.35.617.31 trying to update with RUU_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.14.617.6.exe or any other 4.XX.XXX.X
RUU_HIMA_UL_M60_SENSE70_ATT_MR_NA_Gen_Unlock_3.35.617.31.exe was applied with no problem but when trying to apply the 4.14.617.6 error (132) shows.
I have downloaded all updates and try to apply:
4.14.617.6
4.23.617.1
4.30.617.2
4.30.617.12
None of the RUUs works, shows error (132)
All RUUs was downloaded from htc / us / support / rom-downloads
Can someone give me some hints on how solve this issue???
Thanks in advance.
Click to expand...
Click to collapse
What is your M.I.D number?
S-OFF users should be aware that the phone's CID and MID need to correspond to the SKU of the RUU you want to flash. The SCID (11111111) won't make your phone ignore mismatches between those ID numbers as it did on older HTC devices
Pfaffinator said:
What is your M.I.D number?
S-OFF users should be aware that the phone's CID and MID need to correspond to the SKU of the RUU you want to flash. The SCID (11111111) won't make your phone ignore mismatches between those ID numbers as it did on older HTC devices
Click to expand...
Click to collapse
Thanks Pfaffinator.
Actually I was able to solve the issue changing the CID to BS_US001 and then applying the OTA update using stock recovery, after that I was able to use the latest RUU.exe with latest HTC SW release.
Thanks for your kind support!!!
Pfaffinator said:
S-OFF users should be aware that the phone's CID and MID need to correspond to the SKU of the RUU you want to flash. The SCID (11111111) won't make your phone ignore mismatches between those ID numbers as it did on older HTC devices
Click to expand...
Click to collapse
The MID is irrelevant in this situation. As already explained in this thread (c.f. the first page) and my ReadMe thread you can't flash 4.x RUUs while your phone is using firmware 3.x or lower. The encryption keys got changed.
And the SCID not only "lost" the ability to make the phone ignore MID mismatches it additionally prevents the M9 from being able to receive OTAs.
A general request to everyone who needs help with his/her M9: Please read the ReadMe thread. There's a reason why it's pinned above the normal threads in the General and the Q&A section. 99% of all questions are already answered there. Reading the first two pages of that thread takes less time than creating a new thread and waiting for someone to respond.
?
Flippy498 said:
The MID is irrelevant in this situation. As already explained in this thread (c.f. the first page) and my ReadMe thread you can't flash 4.x RUUs while your phone is using firmware 3.x or lower. The encryption keys got changed.
And the SCID not only "lost" the ability to make the phone ignore MID mismatches it additionally prevents the M9 from being able to receive OTAs.
A general request to everyone who needs help with his/her M9: Please read the ReadMe thread. There's a reason why it's pinned above the normal threads in the General and the Q&A section. 99% of all questions are already answered there. Reading the first two pages of that thread takes less time than creating a new thread and waiting for someone to respond.
Click to expand...
Click to collapse
That paragraph is from your thread.
Yeah, I know. Nonetheless, the MID isn't the problem in this case. It's the SCID preventing the OTA download (as explained in the OTA section of the ReadMe thread) and the encryption keys of the RUUs being different between firmware 3.x and 4.x (resulting in error 132 as described on page 1 in this thread, the RUU and the RUU error section in the ReadMe thread).
Sent from my HTC One M9 using XDA Labs
Hi,
I'm looking for a stock recovery.img for my HTC One M9. I'm trying to update to Android 7.0 Nougat, but TWRP is preventing me from completing the OTA install. I'm on stock 3.41.651.41 ROM with an unlocked bootloader, TWRP.
Basically I want the whole phone back to stock and able to take the Android 7.0 OTA update has released. I just bought this phone and it has TWRP recovery installed and running stock 3.41.651.41
I tried to update using the RUU exe downloaded from the HTC link above, but i got the error 132 (signature error).
Whenever i try to install the available OTA update it just boots into TWRP and nothing happens. I want the stock recovery image so that i could flash it in TWRP (or any other way) so that i would be able to install the OTA.
at
Info:
Sotware status Official
UNLOCKED
S-OFF
HTC DOWNLOAD MODE
UNLOCKED
(bootloader) product: htc_himaulatt PVT S-OFF
CID: 11111111
LK-1.0.0.0000
RADIO-3 00.C1144084060114
OPENDSP 15-6.1.00522.8994.1026
OS : 3.41.651.41
Nov 2 2016
Please take a look at the ReadMe thread (especially the RUU, the stock recovery and the OTA section). You'll find all needed information and files there.
Sent from my HTC One M9 using XDA Labs
Hello
Thanks for your reply , Please can you help to get the direct link for the tutorial to get a stock recovery on my HTC One m9 and to get the OTA Update.
Thanks
It's not that hard to find. ? I'm sure you'll directly see it if you either visit the General or the Q&A section.
Sent from my HTC One M9 using XDA Labs
Hi
I have tried many Roms updates without any results , Please if you can help me directly i will be soo reconized .
Thanks
Discliamer: Don't get the following message wrong. It neither means that I'm annoyed nor pissed. This is an honest question since I really don't understand it and you're by far not the only person that makes me ask myself the following:
Why does nobody read the ReadMe thread? It's pinned above all normal threads in the General and the Q&A section. In other words it's not hidden at all. Is it due to its naming? If so how do I need to rename it so that people actually read it? Or is it due to the length of its guides? Well, it's not possible to shorten them without deleting important information.
If people would read the ReadMe thread at least 90% of the questions in this section wouldn't get posted since the answers are already covered there*.
* E.g. the RUU section tells you exactly which RUU to use and why RUUs with firmware 4.x (like the ones on HTC's website) can't be used on phones with older firmware versions (version 3.x and below). If people read it they didn't need to "try many roms/RUUS" without success like you did. Then, the OTA section explains that the SuperCID shouldn't be used if you want install OTAs. In addition, the OTA and Stock Recovery sections both explain that simply unrooting and flashing the Stock Recovery isn't enough for being able to install OTAs. And with the explanation of the SKU that can be found above all downloads and with the MID/CID/SKU list in the further reading section you can find out which kind of firmware you're using (branded/unbranded and/or the country/continent that it belongs to). Btw, it's Sprint in your case so be careful with what you're trying to flash on that phone since it's a CDMA device (c.f. the warnings that can be found all over the ReadMe thread).
Hello Back ;
im following this guide :
rename firmware to 0PJAIMG.zip
-copy 0PJAIMG.zip to ext_sd card
-boot into bootloader or download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
When i press volume up and confirm update i get this error message
HTC ONE M9 fail 22 RU HEADER ERROR
Please help me to solve this issue.
Did you read the post with the most common RUU errors in the ReadMe thread?
Flippy498 said:
Did you read the post with the most common RUU errors in the ReadMe thread?
Click to expand...
Click to collapse
Yes , i have found this guide and i get theses errors
Flippy498 said:
Please take a look at the ReadMe thread (especially the RUU, the stock recovery and the OTA section). You'll find all needed information and files there.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
But aren't the links to all the T-Mobile stock files linked to from the HTC One M9 ReadMe thread are dead, and have been for well over a year (since I got my HTC One M9)?
[Edit: Nevermind, I might be stupid.]
48roses said:
But aren't the links to all the T-Mobile stock files linked to from the HTC One M9 ReadMe thread are dead, and have been for well over a year (since I got my HTC One M9)?
[Edit: Nevermind, I might be stupid.]
Click to expand...
Click to collapse
Are you sure that you're talking about the ReadMe thread? When I checked it the last time all links were working...
Sent from my HTC One M9 using XDA Labs