yashsingh1/xdaforums huggingface dataset:
[One (M9) General] Flippy498:
That guide you're linking is completely outdated. Therefore you flashed an incompatible SuperSU version. The recommended versions of TWRP and SuperSU are stated in the FAQ of this thread.

For recovering the bootloop you need to reflash the stock boot.img of your current firmware. Unless you made a backup of your stock system before you started flashing you'll have to flash the 3.35.401.12 RUU and re-install the OTA for 3.35.401.32, afterwards, since no one contributed a backup for your firmware, yet. (This is one of the rare exceptions that allow downgrades via RUU even with S-ON.)
[One (M9) General] sajads1:
so is there any ruu of 3.35.401.12 i can download and flash?
[One (M9) General] Flippy498:
How about reading page 1? :p
[One (M9) General] sajads1:
Found it :) thanks alot

---------- Post added at 05:39 PM ---------- Previous post was at 05:30 PM ----------

and last question do i need to be s-off to install viperonem9 ?
[One (M9) General] Flippy498:
S-OFF is never needed for flashing custom roms. The usage/possible benefits of S-OFF are explained in articles that got linked on page 1.
[One (M9) General] nabeel_bibi:
Help..

Hello, I,m new here and this has been quite helpful. This is my problem... I was trying to change my m9 to the developer edition. Successfully unlocked the bootloader. Flashed twrp 2.8.5.0 recovery. Then everything started to go south. I tried to install a superSU. Got stuck on boot loop. So went back into recovery. Unfortunately, I went and accidentally erased my stock os 3.36.709.3. I found hope in this thread and downloaded the corresponding zip for my software version. Renamed it and used the SD card method. It started but I noticed system 01 and 02 failed. It still finished though. Asked me to use the power button and I did. Restarted and now, for the past 30mins it has been stuck on the htc powered by android screen. Could you kindly help me?
[One (M9) General] Flippy498:
TWRP 2.8.5.0 is probably the oldest and worst version you could use. I don't know which outdated instructions/tutorial you used but you should do yourself a favour and completely forget what you read. Since you used such an old TWRP version you probably used a SuperSU version which way too old, as well, and therefore it's no miracle that your phone didn't boot. It was probably a version of the pre-system-less-root-era. All these versions can't be used with android M. The recommended versions are listed on page 1 of this thread (in the FAQ section).

If the system images failed the RUU only flashed the firmware and your phone is still lacking an OS. I assume you didn't check the MD5 sum of the RUU after you downloaded it, did you? It might be a bad download. I know that the RUU is working since it's already been used by S-ON users without any issues.

Press and hold the power and the volume up button until your phone shuts off. As soon as this happens you need to

immediately

press and hold the volume down button so that the phone reboots to download mode. If you aren't fast enough the phone will try to boot to the non-existend system, again, and you need to repeat the whole procedure. If you reached the download mode you can flash the correct TWRP version and use the 3.36.709.3 backup from page 1 for restoring your system.
[One (M9) General] nabeel_bibi:
Oh... I think I understand now. Just got back online. Will try this and let you know. Thank you! One more thing please. I noticed you mentioned back up sir. So I should use the back up method not the sd card method? Thanks again..
[One (M9) General] Flippy498:
Correct. According to your report, the firmware got flashed just fine via the RUU. Only the system is missing. Therefore, restoring a backup should be sufficient.
[One (M9) General] nabeel_bibi:
Alright. Will try that now. Thank you!!!:D
[One (M9) General] nabeel_bibi:
I tried downloading the corresponding backup twice sir, unfortunately both times the checksums didn't match up. Tried extracting and as expected, there was a corrupted system image. I know you're very busy but please is there a way to confirm if the file isn't damaged or a link to another one perhaps? If not, can I use a lower i.e. 2.x backup to get the phone running again? Thank you

---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------

I tried downloading the corresponding backup twice sir, unfortunately both times the checksums didn't match up. Tried extracting and as expected, there was a corrupted system image. I know you're very busy but please is there a way to confirm if the file isn't damaged or a link to another one perhaps? If not, can I use a lower i.e. 2.x backup to get the phone running again? Thank you
[One (M9) General] Flippy498:
Using a lower version won't work. You need to use the one for your current firmware. I don't have an alternative download. And since I deleted the original from my laptop I can't even re-upload it. Sorry.

You actually have three options at the moment:

1) Re-download the file until the checksum matches.

2) Retry flashing the RUU.

3) Using the RUU Service that is linked on page 1.

I don't know what the actual problem is but I guess AFH has some problems at the moment. Maybe you should wait one or two days if you want to choose option 1 or 2.
[One (M9) General] nabeel_bibi:
Ok. I understand. I think I'll wait a bit. Will let you know how it goes.. Thanks!
[One (M9) General] nabeel_bibi:
Finally!!! One of the downloads wasn't corrupted. Worked like a charm. Thanks for all the help:D:D:D:good::good::good:
[One (M9) General] daniel1005:
M9 T-MOB102 back to Stock

Hello,

i have a big Problem. I have read through the whole collection, but i am very confused now.

I wanted to go back to 100% Stock from Cyanogenmod, i flashed some time ago.

My phone is S-ON with an unlocked bootloader. The problem is, i have a T-Mobile AT branded phone.

Here is the fastboot information:

(bootloader) version-main: 3.35.112.12

(bootloader) boot-mode: download

(bootloader) version-baseband: 01.01_U11440792_93.00.51117G_F

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: T-MOB102

I have tried to recover the phone with the OPJAIMG.zip-Method and used your T-Mobile DE (SKU 111) File.

But in downloadmode the phone tells me there is a "RU_cid_fail cid in android-info mismatch".

As far as i understood it is possible to flash a TWRP-Backup and get stock with this image.

But i could also not find a suitable image for my cid neither my sku, just 111 (TMO DE) again.

So my question is, can i take the TWRP-Backup for 111 to get Stock with my 112 version?

Please help me ... :confused::confused:
[One (M9) General] Flippy498:
Short and simple: No, you can't. You need a backup that exactly matches your current firmware or a RUU for your SKU that has at least the same firmware version as your phone or a newer one.

Unfortunately, no one's contributed any files for your SKU, yet.

Either flash a sense-based custom rom, use sunshine and convert your phone to a version whose RUUs are posted on page 1 or contact the RUU service that got linked on the first page. The costs for both solutions are more or less the same.
[One (M9) General] nleitao:
They work.

I'm waiting for the the developer access on AFH to upload the file Stock_Backup_4.19.617.1.zip

I had a SKU 206, unlocked it, flashed TWRP, SuperSu, S-Off with sunshine, SuperCID, MID 0PJA11000, flashed the RUU 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.19.617.1.zip and tested it now

It's my way to say thank you to your work and help ;)

When it's uploaded I'll drop a line here.
[One (M9) General] doomscooter:
Anyone have ota 4.14.401.7? Or full firmware 4.14.401.7? Tia
[One (M9) General] Golv:
OTA_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7-3.35.401.32_release_490770.zip

Thx [MENTION=7715745]BiOMeX[/MENTION] from 4pda!
[One (M9) General] demian12:
Can I use the OTA file to update from MM ?
[One (M9) General] doomscooter:
Woooghhhh TIA, sir. Yummy...

EDIT : download via IDM but corrupt. I cant extrak zip to get FW.
[One (M9) General] Roobwz:
Is it normal that my bootloader says modified even if I recently RUUd back to stock with the sd card method?
[One (M9) General] Flippy498:
Did you try to extract the firmware with the RUU decryption tool?

Normally it should get reset to "Original". Which RUU did you use? The 3.35.401.12 one?
[One (M9) General] Roobwz:
i used the one that matched my SKU 771.
[One (M9) General] Flippy498:
Ah OK. I thought you were one of the users that are currently flashing a 401 RUU for being able to install the android N update.

Does your download mode state "modified", as well? I'm not sure why the bootloader didn't get reset...
[One (M9) General] Roobwz:
correct me if im wrong... i couldnt find any info about the software situation in the download mode. It just said modified in the bootloader (white background)
[One (M9) General] Captain_Throwback:
OTA firmware isn't encrypted - only signed. The tool isn't necessary to extract it, and besides that, it won't work.
[One (M9) General] doomscooter:
Iam not using RUU descryption tool.

I just using rar aplication to extrak OTA.

But OTA 4.14.401.7 corrupt cant extrak

OTA 4.23.617.1 good to extrak.

I think upload zip 4.14.401.7 corrupt.
[One (M9) General] Flippy498:
I've already used the tool with OTAs. It actually works if you only want to extract the firmware files.

I know that OTAs aren't encrypted but I thought it might be easier to recommend the tool than to explain how to extract the firmware with 7-zip and the #-open method.

Edit [MENTION=5301718]Roobwz[/MENTION]: You're right. Don't know why but I thought the download mode mentions the "modified" or "original", as well.
[One (M9) General] Captain_Throwback:
Interesting, I guess [MENTION=2605798]nkk71[/MENTION] added handling for that when I wasn't looking, lol :eek:.
[One (M9) General] nkk71:
Nope I did not, think last time I tried it was with shadow-projects ;)

The tool is not "by design" needed to do that, we *could* add it, but to be honest, a simple unzip is more than enough.
[One (M9) General] Flippy498:
Ok. Thanks for the clarification. I stumbled across the additional "feature" of the tool by accident when I dragged and dropped the wrong file some days ago.

I didn't have enough time for writing a more detailed post when I recommended the tool for extracting the firmware from the OTA.

From my experiences only unzipping M9 OTAs is "simple" but not unzipping the firmware.zip since you need 7-zip and the "right-click > 7-zip > open (the second one from above) > #" method for the latter. Using this method isn't really difficult but if you don't know what needs to be done you won't be able to open the firmware.zip.
[One (M9) General] Captain_Throwback:
I usually just extract it on my device, which never seems to have any problems. In the past I've had to use ZArchiver or 7zipper, but this most recent OTA I was able to unzip directly in Solid Explorer with no issues, both the OTA zip and the firmware contained within.
[One (M9) General] Flippy498:
Maybe android zipping programms handle the archive in a different way by default than windows programms do? :confused: It doesn't matter which programm you use (the windows explorer or 7-zip) as long as you simply double-click on the firmware.zip you'll get an error. The #-method I mentioned is working fine, though.

I prefer grabbing OTAs with a network monitor instead of extracting them from "/data/data/com.htc.updater/files/". Therefore I never tried to unzip them on an android device.

Edit for being a bit preciser: Windows explorer states "The folder cannot get opened. The zip-compressed folder firmware.zip is invalid." and 7-zip states "The file firmware.zip cannot get opened as an archive.". (These are my own translations from German to English. The exact wording might differ on an actual English system.)
[One (M9) General] nkk71:
I still use WinRAR, unless I don't like the outcome... and you know what comes next "-t " ;)
[One (M9) General] shivadow:
Anyone making a nowipe flashable for 401?.. It's 2017, we shouldn't have to go back to stock..

Beamed in by telepathy.
[One (M9) General] doomscooter:
I already trying stock rom 4.14.401.7 & 4.23.617.1

I think 4.14.401.7 very drain and 4.23.617.1 normally.

But 4.23.617.1 not responsive than 4.14.401.7

When i try flash FW 4.14.401.7 to stock rom 4.23.617.1 that more smooth.
[One (M9) General] Flippy498:
Don't you think asking that question in the thread that provides such flashable *.zip files makes more sense than asking the question here? ;) :p

Besides, Sneakyghsot wrote instructions how to make those files and I've used them in past, as well. The OTAs are already available on page 1 and with the Decryption Tool it's easier than ever to decrypt RUUs. Alternatively you could use the latest NoWipe Pack for your firmware and use that as a base. As you can see you have everything you need for making your own flashable *.zip if you need a newer one that quick.

You should always use the system/rom that corresponds to your current firmware if you want to minimize lags and bugs. I still have no experiences with the new 4.x firmware since I haven't had the time that is needed for updating my phone, yet.
[One (M9) General] blueberry60:
Latest 0PJAIMG zip file for HTC Developer Edition Unlocked Devices flashable from download mode based on Nougat 4.23.617.1 :

0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.23.617.1.zip

md5: c94eab4da47d4dc498460faca8e0d0eb
[One (M9) General] warren.walker:
Do I need to be on stock firmware to flash this?
[One (M9) General] Flippy498:
Did you read page 1?
[One (M9) General] warren.walker:
my apologies, I will re-read
[One (M9) General] Daniyaltahir:
Hi please help i have an international m9 himauhl im currently using viper rom i tried reading your thread it got way over my head so i got confused i have some flashing experience with Samsung phones but i got very confused with when i flashed viper rom so please if you can tell me steps to get my phone to stock nougat. My phone was on stock before its firmware was 3.35.401.12 my bootloader is unlocked and s off
[One (M9) General] Flippy498:
All you need can be found in post #3. You can keep you bootloader unlocked and the phone S-OFF. I highlighted your SKU in red so that it's easier for you to find the correct RUU. For getting back to stock you only need to follow the 11 steps that got explained in the third post of this thread. It's easier than it looks at first sight.
[One (M9) General] barashe:
Ota 3.35.401.32 --> 4.14.401.7

3.35.401.32-->4.14.401.7
[One (M9) General] Flippy498:
We already had this file in our collection. I added that official link, anyway.
[One (M9) General] :
Anyone know where I can download a 3.35.401.32 RUU (zip)?

The official OTA from 3.35.401.32 to 4.14.401.7 failed on a fully Stock M9. Now it won't boot anymore and it still shows the old OS in download mode.

So best option would be a 3.35.401.32 RUU.

Thanks in advance!
[One (M9) General] Flippy498:
As mentioned in the RUU section, you can use the 3.35.401.12 RUU if your firmware version is 3.35.401.32.
[One (M9) General] peyman2514:
when new ruu(4.14.401.3) release?
[One (M9) General] :
Thanks, it worked.

But after using 3.35.401.12 RUU and updating again to Nougat, the phone does not boot anymore.

So this happened twice now and I have to use the RUU again. The Nougat OTA starts and after a restart nothing happens and it still shows the old firmware version. The M9 is not bootable anymore.
[One (M9) General] Flippy498:
I used the RUU myself and had no problems with updating to 4.14.401.7. I don't know what's the problem in your case. Sorry.
[One (M9) General] Daniyaltahir:
please help i have twice downloaded 3.35.401.12 RUU both times when i extract files to check the files it gives corrupt error and even its md5 isn't matching im using idm for download but never had problem before
[One (M9) General] barashe:
I guess I'll have to pay my debt to the community with another file then :)

Here is a 4.14.401.7 TWRP stock backup.
[One (M9) General] dangerguest:
Upgrade with TWRP

I Have the 3.35.401.12 and an rooted phone and with S-ON. Can I use TWRP 3.0.3.0 with the 4.14.401.7 posted on the post 5 in my phone for upgrade?
[One (M9) General] shivadow:
If one could be a gentleman and post the md5 or sha of the file you have at your end?. It may help others to identify a corrupt download?, highly likely on wifi connections!.

Beamed in by telepathy.
[One (M9) General] Flippy498:
No, you can't. Backups don't include the firmware. You need to get back to stock and to install the OTAs that update your phone to Android 7.

I don't know what I should post that isn't already published. :p As written on page one the "good" file hosters mention the correct MD5 checksum on the download page.
[One (M9) General] dangerguest:
Is there any post explaining how do I that?

Thx in Advance ;)
[One (M9) General] Flippy498:
Is that a serious question? You should read at least the first page of a thread before you post in it...
[One (M9) General] dangerguest:
Can I use TWRP 3.0.3.0 to go back to 3.35.401.12 and use 3.35.401.12 and them upgrade the firmware????:confused:
[One (M9) General] Ninec:
Hello guys I have a question about new update. I'm with SKU 401 and still there is no update for adroid 7... people from my country start to receive the new update, but still nothing for me. I try flash with RU from 1st post 3.35.401.12 then update to 3.35.401.32 and again no nougat.
[One (M9) General] Flippy498:
Can you tell us your current CID? Maybe it's the reason for the update not being available.
[One (M9) General] Ninec:
My current CID is HTC__001
[One (M9) General] Flippy498:
Since I know that your phone is S-OFF: Can you try whether changing the current CID to one of the other CIDs that belong to SKU 401 solves your problem? Use the answer to Q10 (located on page one) for changing the CID. I can tell you for sure that the German CID HTC__102 is able to receive and to install the Android N OTA.

Do you know the CID/SKU of your friend's phone?
[One (M9) General] Ninec:
Ok, but where can I find this ABD files ? Also where can i find new MID
[One (M9) General] Flippy498:
The ones I'm currently using should be linked in the TWRP section I. I should add a link to Q10 as soon as I have the time...

As written in the instructions you don't need to change the MID if it already matches the one of the RUU and that's the case. Otherwise you wouldn't have been able to flash the 3.35.401.12 RUU, before.
[One (M9) General] Ninec:
Ok, now I go to step 8 and copy the code it says waiting for device. Where is my mistake ?
[One (M9) General] Flippy498:
Are you using windows 10? If yes, do you have a windows 7 PC you could use? Are you using a USB 3.0 port? If yes, do you have a USB 2.0 port you could use? Are the USB drivers for HTC devices installed? Is the HTC sync manager uninstalled on your PC so that only the USB drivers are left? Do you use the cable that came with your M9?
[One (M9) General] buttie:
If you have stock recovery and SD Card, don't overcomplicate things. Just download OTA straight from HTC servers, copy it to SC Card, reboot to recovery and apply update from there.
[One (M9) General] Ninec:
I use win 10. I have win 7 pc and both USB ports. No drivers and HTC syng manager also I use original cable that came with my phone.
[One (M9) General] Flippy498:
Then install the sync manager and uninstall it afterwards since its known to cause problems. This way you install the USB drivers. Maybe your problems are based on the fact that the drivers are missing.

Edit [MENTION=3618186]buttie[/MENTION]: I personally don't think that it's a good idea to try to manually install an OTA if the phone can't receive it the "normal" way.
[One (M9) General] Ninec:
Ok that works, but when i go to step 11 I must use this fastboot getvar all HTC__102 or ?
[One (M9) General] Flippy498:
Ehm, no. The instructions tell you to use

fastboot oem writecid <enter CID of the RUU you want to flash>

and not

fastboot getvar all

As said before, I know that the CID HTC__102 already received the update. So using that CID should be totally fine. However, if you know the SKU/CID of your friend's phone and that phone's SKU is 401, as well, then using the CID of your friend's phone is a possible alternative.
[One (M9) General] Ninec:
Apologize my bad i mean fastboot oem writecid HTC__102. About my friend he don't know how to check his CID to be honest it's the same with me... We try to go reboot to download to check it, but its not written down like on my phone maybe the reason is because he don't have S-OFF.
[One (M9) General] Flippy498:
He can find it out with the help of fastboot getvar all. And yes, it's not visible due to his phone being S-ON.
[One (M9) General] Ninec:
Ok I change my CID to HTC__102 now i must flash ruu again ?
[One (M9) General] Flippy498:
I think flashing the RUU isn't needed in this case since you don't want to change the SKU. Just try to search for an OTA.
[One (M9) General] Ninec:
Already try manual search for OTA and again nothing...
[One (M9) General] Flippy498:
Then I'm actually at my wits' ends. Sorry. You could try to reflash the RUU but I doubt that this would make any difference...
[One (M9) General] Ninec:
Is there a way to download 4.14.401.7 and install it manual ?
[One (M9) General] Flippy498:
You can download the OTA directly from HTC: http://fotadl.htc.com/OTA_HIMA_UHL_....35.401.32_release_490770qpms6mert5vkt1m3.zip

Put the file onto a SD card, boot to the stock recovery (I always forget which keys need to be pressed for enabling its menu since I never use the stock recovery - you'll have to google the key combination) and use the "apply from sd card" function. I personally don't think that trying to manually install an OTA that the phone can't receive via the software update function is a good idea. But that's only my personal opinion.

There is no publicly available RUU, yet.
[One (M9) General] Ninec:
I try but result is - Installation aborted.

assert failed: check_mid ("full" . "0PJA10000") == "t"

E:Error in /sideload/package.zip

(status 7)
[One (M9) General] Golv:
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7_Radio_01.01_U114401011_117.00.61117G_2_F_release_490768_signed_2_4.zip

Thanks [MENTION=263825]mars[/MENTION]3712

md5 148a8af99ebdc7b26b4b14c09179d6e0

upload date Feb 01, 2017 | 08:27PM​
[One (M9) General] computerslayer:
Oooh! Let's get that in the readme thread - we've had a number of Q&A threads around Nougat OTA install issues for the 401 SKU. Assuming that this is the real deal, it will be very helpful!
[One (M9) General] Flippy498:
I already added the RUU that mutasek24 posted in the nougat update discussion thread, some hours ago. According to the MD5 checksum they're the same file. I'm not sure who of them got the RUU first and whether they have the same source...
[One (M9) General] computerslayer:
Nicely done - I don't know how you keep up with all the threads around here!
[One (M9) General] Flippy498:
To be honest, it's not that hard. There isn't that much activity here in the M9 forum if you compare it with other device forums on XDA. ;)
[One (M9) General] computerslayer:
I'm glad for your sake but a little sad for the M9. Development hasn't been what it could have been what with HTC's moving from the GPE model M8 to the more walled-garden approach with the M9. Still, it's an excellent device and I'm grateful that we have so many well-versed experts still offering support.
[One (M9) General] Ninec:
Guys I can't flash that RUU ... FAIL 12 RU_ZIP_ERROR what is that how can i fix it ?
[One (M9) General] Flippy498:
Please re-read the RUU section. That's the expected behaviour if you're on firmware 3.x.
[One (M9) General] Ninec:
Ok, but how can I do no wipe/full wipe ?
[One (M9) General] Flippy498:
The thread that contains those packs had only been linked in the useful links section. I added some links to the RUU section, as well.
[One (M9) General] Ninec:
Thank you for replay ! I try to follow steps and this is the result
[One (M9) General] doomscooter:
dear OP

whether m9 taiwan region stock rom firmware 709 Nougat already rolling out? tia