yashsingh1/xdaforums huggingface dataset:
[One (M9) General] Azure1203:
Yeah no kidding. If you knew me you'd say messing up and figuring it out is pretty typical. :)

Anyways for people asking what happened and if it helps someone.

When I got phone it already had the 3.38.631.2 firmware on there. I installed TWRP and SuperSU no problem. But then I went into TWRP and did a full wipe which completely removed the OS on there. When I tried to reboot the phone would get stuck at the HTC screen. When I booted into TWRP it said no OS installed.

I actually didn't realize that there was no proper OS on the phone at this point, nor did I understand the importance of flashing a ROM that had the proper firmware(3.38.631.2) so I just went ahead and loaded Android Revolution ROM, which is actually a 3.35 firmware onto phone, installed it via TWRP as instructions indicated. Everything installed perfectly, but when I went to reboot phone it took almost a hour to load, which was my first sign of a problem. I actually didn't let it TRY to completely load and instead went a tried to install a different ROM. That also didn't load properly. Again, all the ROMs I tried to install had the 3.35 firmware, and if you go read the fine print, all the ROM developers say you need proper firmware. Me being me didn't read it properly.

I then went crazy trying to get a RUU on there and lost TWRP because I flashed stock recovery. What I didn't realize is that you can easily get TWRP back on there by just using flashboot. I did that, and then after fooling around with a RUU that didn't install(wrong firmware again) and trying to use the 3.38 nandroid files from the first post that didn't flash because you actually have to first manually do a backup, and then move the proper files into the folder that TWRP created for it to recognize the boot, recovery and system files. Eventually after exhausting all those possibilities I again installed Android Revolution ROM, let it load COMPLETELY, and then created TWRP backup file, moved the 3.38 files into the folder, went into TWRP while on Android Revolution(which loaded but didn't work properly), and flashed backup.

That worked perfectly.

Now my only issue is my LED notification light doesn't work. Is there even one on there? Official site says there should be. I installed root, got Titanium Backup and removed a bunch of HTC apps so I'm guessing I might have disabled the one that makes the notification light work.

Any help there?
[One (M9) General] Azure1203:
Another update. I tried flashing some 3.35 ROMs to my device and they seem to work okay, but the baseband is unknown so I get no network connection. Is there a reason the Rogers firmware is higher? Videotron one is even higher(3.39).

I'm still s-on so can't really do what I want.

No big deal obviously because now I have a TWRP backup that is easy to restore!
[One (M9) General] SaHiLzZ:
There maybe a mismatch with HBOOT and Rom version, causing unknown baseband.

What is a 3.35 ROM? You should cross-check a custom rom's requirement with what you have on the phone.
[One (M9) General] Azure1203:
Most of the ROMs in Android Original Development are based on the 3.35 firmware.

They claim it should work if you have a higher firmware but I still haven't found one that does.
[One (M9) General] ak41:
Sorry if I'm beating a dead horse here, but I have a Rogers One M9 with these details:

Htc_himaulatt PVT S-ON

LK-1.0.0.000

RADIO-01.02_U11440601_77.04.50715G_2_F

OPENDSP-V29.2.6-00492-M8994_0702

OS-2.11.631.2

JUL 23 2015,19:54:48(579410)

I've lost root recently for some reason but still have Twrp recovery.

I'm trying to go back to stock so I can upgrade to Marshmellow and then install Viper Rom. I also have this file:

0PJAIMG_HIMA_UL_L51_SENSE70_ATT_MR_Rogers_WWE_2.11.631.2_Radio_01.02_U11440601_77.04.50715G_2_F_release_449106_combined_signed_2_4_7

Based in the information above, I can flash it with TWRP from my external SD card, BUT, I need to relock my bootloader first? Is this correct? Will I still be able to flash something from TWRP with a locked bootloader?
[One (M9) General] efrant:
There's a link in the first post that has stock Rogers system boot and recovery images for 2.11.631.2. All you have to do is download those onto an (exfat-formated) sdcard in the proper directory structure, and restore using TWRP. Then the OTA update will install properly.

You don't need to relock your bootloader to flash RUU zips, but I'm not sure you can flash that particular one if you are S-ON. (It's a "combined" RUU, and based on what I've read, not signed by HTC.
[One (M9) General] ak41:
I see. So I place the 3 files from the first post (the 2.11.631.2 boot.emmc.win, recovery.emmc.win and system_image) on an exfat-formatted sdcard (not sure what's meant by in the proper directory structure - don't I just place them in the root of the card?), and flash it with TWRP? Do I have that right?

I'm currently on Viper 3.5.0 which I've been very happy with, but I got the "Binary's need to be updated" message out of no where a few days ago, and basically lost root along with the ability to flash SuperSu for some reason. That's pretty much why I'm looking to go back to stock, update and install the latest Viper Rom.
[One (M9) General] efrant:
No, they don't go in the root directory.

When you backup your ROM in TWRP, it saves the files in a specific folder. The easiest way to set up the directory structure is to boot into TWRP and do a backup to your exfat-formated sdcard. (You can just back up boot or recovery to create the folder tree, no need to back up everything.) Once you do that, navigate to that folder and delete all the files there, then copy the 2.11.631.2 boot.emmc.win, recovery.emmc.win and system_image files there. Then restore.
[One (M9) General] ak41:
Oh OK, I understand. Thanks for the explanation. I'll try this method tonight. Just one problem however. Every time I try to download the 4.4gb system_image file, I get a network failure message towards the end of the download (at about 3.7gb). Is anyone else experiencing this? I don't have any connectivity issues.
[One (M9) General] ak41:
Here's an update.

Placed the 3 files on an exfat SD card in the in the TWRP folder as instructed. Restored via TWRP. This allows me to install the 2.11.631.180 software update. Then when I begin the system update, the phone reboots, begins the update process, but then stops at the red triangle with the exclamation mark.

Here's the error log. Can someone tell me what the issue is?

E:missing bitmap oem_unlock_bg

(Code-1)

E:missing bitmap oem_unlock_bg_yes

(Code-1)

E:missing bitmap oem_unlock_bg_no

(Code-1)

E:Find no match PARTITION: for package path @/cache/recover/block.map

Finding update package…

Opening update package…

Verifying update package…

Installing update…

L51QCT.01.103.027

Verifying current system…

/dev/blobk/bootdevice/by-name/system has been remounted R/W

reflash device to reenable OTA updates

E:Error in @/cache/recovery/block.map

(Status 7)

Installation aborted.

OTA failed! Please power off the device to keep it in this

tate and file a bug report!
[One (M9) General] efrant:
In TWRP, there is an option in the mount menu to "keep system read-only". That needs to be enabled BEFORE you restore the backup.
[One (M9) General] ak41:
I'm not seeing it. Not under mount, or anywhere else for that matter. I'm on TWRP 2.8.6.0 if that matters.
[One (M9) General] efrant:
I think that's too old. Try using this one: twrp-2.8.7.1_CPTB-B1-hima.img
[One (M9) General] ak41:
You're right, I flashed 2.8.7.0 and it had that option. And now I've successfully updated to Marshmallow! Thanks for all your help efrant. The only thing left in my way to flash the Viper 4.3.0 rom is get root, but this seems to be another issue I'm having. When TRWP ask if I want to root, I accept, it does it's thing but then I'm stuck in a bootloop. I try manually flashing SuperSU, and still the same problems. Is there a particular version I should try to flash or anything else in my phone I should do?
[One (M9) General] efrant:
Do not use the option in TWRP to root. You need to manually flash a specific version of SuperSU: v2.65
[One (M9) General] ak41:
Yup, that did it. Thanks again. You've been incredibly helpful. I've never had so much trouble modifying a phone before.
[One (M9) General] efrant:
Welcome to HTC... :D
[One (M9) General] samuspr1me:
Hello, i flashed with this backup sucessfully but i got blank screen the phone won't boot.

CID - TELUS001 2015-07-27--21-18-11_LRX22G_release-keys.zip

any help?
[One (M9) General] mozer0:
I keep getting "error: cannot load 0PJAIMG.zip" everytime I try flashing. What am I doing wrong?
[One (M9) General] rythos42:
How did you get past the network error? I'm getting the same thing, both at home and at work.
[One (M9) General] ak41:
I switched to Firefox and the full download went through. For some reason Chrome wasn't getting the full download.
[One (M9) General] efrant:
You're going to have to provide a bit more information if you want users to help you.

What CID is your device? Is your device S-OFF? Where did you get the 0PJAIMG.zip file? If you are trying to go back to stock, why not just restore one of the TWRP backups in the first post?
[One (M9) General] mozer0:
Currently, I have SuperCID 1111111. My device is Unlocked and S-OFF. I tried extracting the TWRP backup '2015-06-04--18-49-33_LRX22G_release-keys.zip' and uploading all of its content into my SD card. I created the TWRP backup file structure, and I can see the backup in TWRP but when I select it, I don't see any boot, system or anything. So I tried swiping to restore, it says no partitions selected. Any ideas? I have been trying to get go back to stock for 6 hours now and no luck yet :(
[One (M9) General] efrant:
I don't know what's in 2015-06-04--18-49-33_LRX22G_release-keys.zip, but I assume there is a recovery image, boot image and system image. They need to be named properly, i.e., recovery.emmc.win, boot.emmc.win, system_image.emmc.win in order for TWRP to restore them.

You should also set your Cid back to what it was if you want to be able to install OTA updates.
[One (M9) General] ShensMobile:
So I ran fastboot getvar all to verify that I have a Telus CID (bought the phone used, unlocked). Downloaded the Telus package on front page. Successfully restored the backup. When I go to boot the phone up, it never gets past the first HTC screen, not even the boot logo, just the one with the red text saying "This system has been modified for development purposes."

I recall there being an issue with restoring a backup while having your bootloader unlocked with other devices (as 5.0 has that toggle to allow OEM unlock IN the OS). Do I just have to run fastboot oem lock to get past this screen? Or did I do something really wrong?
[One (M9) General] efrant:
Doesn't look like you did anything wrong. (That said, I have no idea if the Telus backup in the first post actually works -- maybe the orginal poster can verify?)

Anyway, do you have S-OFF? And what firmware version is user device? If you are S-ON, and your firmware version is 1.32.661.6 or older, you can try using this RUU: http://androidruu.com/getdownload.p...21_59.04.50303G_2_F_release_426163_signed.zip

If you have S-OFF, then you can use whatever RUU you want. I see that you are on Fido, so I would image a Rogers RUU would be the best for you.
[One (M9) General] ShensMobile:
I am S-ON. I'll check which version of firmware I'm on when I get home later and see if I can try that RUU. Thanks for the help!
[One (M9) General] efrant:
I'd also highly recommend getting S-OFF. It makes things much easier.
[One (M9) General] ShensMobile:
So unfortunately, another getvar all reveals that my software version is 2.XX+ so I won't be able to use that RUU.

I have to pay to S-Off right now, right? I'm at a point where I don't want to spend any more money on this phone :(

Is there anything else I can try?

Edit: Some reading says I also need to flash the boot.img that goes along with the recovery backup. Where can I find a stock Telus boot.img?

Double edit: I looked at the other recovery images, this one doesn't have a boot_img.emmc.win or a recovery_img.emmc.win. Is there any way to acquire these files?
[One (M9) General] efrant:
Yes, you need the boot image, the recovery image and an untouched system_image file to go back to stock.

Your only options (that I can think of) are as follows:

1) Try and find a proper Telus 2.xx backup from someone. There must be other Telus users that own M9s that have made a backup;

2) Badger HTC enough and they may give you a newer Telus RUU. (They provided me with a Rogers RUU after some harassment by me :) ...although I never had to use it.)

3) Forget about stock and just use 2.xx based custom ROMs;

4) Get S-OFF and never have to worry about going through this again... :)
[One (M9) General] dumb_ass:
Hey guys,

looking for BM___001 radio's for 1.32.666.30 and 3.38.666.2.

if anyone has them handy thanks.

su

dd if=/storage/sdcard0/radio.img of=/dev/block/mmcblk0p20

or does anybody have success with a particular radio/firmware.

3.35.617.12 dev is crap

thanks
[One (M9) General] Ib31415:
Okay, so I was reluctant for it to come to this but I have come thoroughly lost.

Bell Canada HTC One M9

Software number:

3.38.666.2

cid: BM___001

mid: 0PJA11000

S-ON

Bootloader Unlocked

Today I installed TWRP 3.0.1 (I'm pretty sure it was that one) and I installed SuperSU2.65. I was indeed rooted, but then decided there was nothing in rooting for me nor in the TWRP Bootloader since it doesn't look like CM13 is going to be stable any time soon.

Now i'm trying to go back to stock.

I didn't fully understand every step I think because I never got a image backup before I installed TWRP (I was never clear on where or how). Basically after I flashed TWRP but before I installed SuperSU I used the software to make a backup, but even after using the built in restore button function I did not get back to stock as TWRP is still installed (although SuperSU was gone).

I saw some of the posts earlier in this thread with BriniaSona and Flippy498 (which are relevant because BriniaSona has the same CID and MID as I do, although a very different software number).

And yes in the QA I saw this:

However I'm kind of stuck at this point. I don't have a recovery_signed.img nor do I have an RUU (wouldn't that be wonderful).

I went to htcdev [dot] com/devcenter/downloads and found a ZIP tied to my software number but it doesn't seem useful to me.

I did also download the Stock_Bell_LP_5.0.1_1.32.666.30_TWRP file from earlier, but it predates my software quite a bit and I'm not entirely sure how to use it. I put it in the TWRP\Backups\<SN> folder but I'm a bit afraid of how to proceed at this point.

Can some kind person on this forum hold my hand a bit and explain exactly how to get back to stock? Possibly even using the Stock_Bell_LP_5.0.1_1.32.666.30_TWRP file? Or where I could find a RUU (would contacting HTC work?)

My phone is working, and has some of the apps I need for work on it, so it's not all bad, but I'd really like to get it back where it was, the Bootloader can stay unlocked, but I'd like the System Recovery to be stock so I can just factory reset and start from scratch.
[One (M9) General] Ib31415:
I tried calling HTC Support this morning, but they couldn't provide an RUU since I'm in Canada.
[One (M9) General] efrant:
The advice I gave ShensMobile about his Telus ROM applies to you. You have a few options to return to stock:

1) Try and find a proper Bell 3.38.666.2 backup from someone. There must be other Bell users that own M9s that have made a backup;

2) Badger HTC enough and they may give you a newer Bell RUU. (They provided me with a Rogers RUU after some harassment by me ...although I never had to use it. And by harassment, I mean via email/chat, I kept saying how disappointed/frustrated/upset I was that a company like HTC, which allows users to unlock their bootloaders and flash custom firmware, does not give Canadian users a way to return to stock, while it gives U.S. users that ability. I repeated something similar, over and over and over, and they provided me with an RUU.)

3) Forget about stock and just use what you have or a custom ROM;

4) Get S-OFF. Once you get S-OFF, you can flash one of the older Bell RUUs from this site (or even flash the unbranded developer RUU), and then you'll receive the OTA updates to your current version. And never have to worry about going through this again.

See my point #2 above.
[One (M9) General] dumb_ass:
Here is Bell 3.38.666.2 Radio image.
[One (M9) General] efrant:
Thanks for posting. Do you happen to have the stock recovery, boot and untouched system images as well for Bell 3.38.666.2? I'm sure [MENTION=7385879]Ib31415[/MENTION] would be very happy if you do.
[One (M9) General] dumb_ass:
i'll ask, had to bug buddy to get the radio..

will see what i can do.
[One (M9) General] bsilvino:
Hi I am trying to help a buddy that flashed CM13 GSM on his One M9 from Rogers, I got till the point where none of the Rogers files provided is working for me, and is giving this error (see pic), I have tried to flash the via fastboot and got no luck, any help would be appreciated, I am trying to get it back to stock, since the CM13 does not have the proper radio on it, and the LTE/none network is not working.
[One (M9) General] efrant:
Are you S-OFF or S-ON?

What is the current firmware version on the device?

1) If you are S-ON and you have a firmware version that is higher than the file you are trying to flash, you won't be able to flash it.

2) If you are S-OFF, you could try typing "fastboot oem rebootRUU" before you flash the zip. It may help

3) If you are S-ON or S-OFF, you could always restore the Rogers backups from the first post. Pick the backup that has the same firmware version as what is on your device, and restore them via TWRP. (How to do this has already been covered in this thread.)
[One (M9) General] bsilvino:
See the pics for details of the device, now can you provide the link of the right file I should flash via TWRP? I'd appreciate, I am a bit overwhelmed with all the info that I am reading.. I am working on this phone since yesterday.. and it is pissing me off. I reaally would appreciate if you can. Tkx
[One (M9) General] bsilvino:
So based on the imgs my OS versions is 3.38.631.2 so

Can someone have the kindness to guide how to install/flash/recover these 3 files:

boot.emmc.win

recovery.emmc.win

system_image.emmc.win

thank you!!!
[One (M9) General] bsilvino:
So based on the img my OS versions is 3.38.631.2 so can you/someone have the kindness to guide how to install/flash/recover these 3 files:

boot.emmc.win

recovery.emmc.win

system_image.emmc.win

thank you!!!
[One (M9) General] efrant:
I'm mobile right now, but I will try to help you out. (I won't be able to post links though.)

1) Have an exFAT formated sdcard in your device.

2) Download TWRP and flash it to your device. Make sure it's a version that starts with a 3, since your firmware starts with a 3.

3) Boot into TWRP and make sure that the setting to keep "system" as read-only is enabled. (Look under the mounts menu.)

3) Do a backup of the boot partition in TWRP to your sdcard.

4) Go to the folder where TWRP saved the file and delete all the files in there. (We just need the proper folder structure.)

5) Copy the 3 files you mentioned in your post to the folder that you just emptied.

6) Restore the backup in TWRP. (They should work fine the exact way they are named.)

7) Done. You should now be fully stock.

I'm pretty sure I've detail the same steps in this thread, so read my posts if you get stuck - - there may be more detailed instructions.
[One (M9) General] bsilvino:
:good:Thanks a lot [MENTION=1566190]efrant[/MENTION] !! that would be my last shot, and it was.. but now the phone is restored, the

files for Rogers 3.38.631.2 are working like a charme

.. :cool:
[One (M9) General] schergr:
Android is starting....

So I downloaded the boot, recovery and system images for 2.11.631.2, and did a restore from within TWRP. It restores successfully, and starts booting runs through a "Android is starting..Optiming app x of 121." counting sequence, and then reboots, and starts over again from 121 apps (it was 172 initially).

Has anyone seen this? Any thoughts? Seems to be stuck in a loop.
[One (M9) General] efrant:
Hmm. Bizarre.

Is your device firmware 2.11.631.2?

I would try letting it reboot by itself a few times and see if it sorts itself out. If if doesn't work, you'll likely have to wipe.
[One (M9) General] schergr:
Cycling...

Yup, its on 2.11.631.2 Here are the rest of the details. The bootloader is also unlocked.

htc_himaulatt PVT S-ON

LK-1.0.0.0000

RADIO-01.02_U11440601_77.04.50715G_2_F

OpenDSP-v29.2.6-00492-M8994_0702

OS-2.11.631.2

Jul 23 2015,19:54:48(579410)

I let it reboot a few times and it keeps cycling, so I wiped it, and now it just hangs at the HTC screen..appears to be bricked. Any thouhgts?

Greg
[One (M9) General] schergr:
Sorted...

had to wipe the data partition as well. Found an OTA update, downloaded, starts installing, gets about 1/4 of the way through, but then the Red upside down exclamation appears. Any thoughts?

Greg
[One (M9) General] efrant:
To me, that sounds like you didn't have the setting to "keep system as read-only" enabled when you restored the TWRP backup. That setting needs to be enabled before you restore the backup. So what I would do, is flash TWRP, enable that setting, and restore the backup again.
[One (M9) General] schergr:
read only?

I was using 2.8.7.0 TWRP but when I checked the mount read only option, it wouldn't let me restore the recoveries. Did I do something wrong?

Now, I tried to reinstall TWRP, but it doesn't want to connect. UGH! I'm in worse situation now then I was before LOL
[One (M9) General] efrant:
Use this version of TWRP: twrp-2.8.7.1_CPTB-B1-hima.img
[One (M9) General] schergr:
First of all, let me say thank you for your assistance on this. My thanks doesn't begin to cover my debt. :) If only I have just followed your damn instructions.... Had I just...

"4) Go to the folder where TWRP saved the file and delete all the files in there. (We just need the proper folder structure.)

5) Copy the 3 files you mentioned in your post to the folder that you just emptied."

Things probably would have been fine. But did I? NO!!!!! F!"!"!"! I copied a previous TWRP backup, deleted the boot, recovery and system.win files, and just dropped the new ones on top, but didn't delete all the other extraneous BS. Hence the problem. UGH!!!

Now, I've done things right. Successfully went through the OTA to get to 2.11.631.180. Now going through the OTA update to get to Marshmallow.

BTW...this may not be an issue for everyone, but I found that after I restored this the first time, and had a "stock" ROM, I coudn't use the Android SDK adb / fastboot anylonger (didn't see the device). Oddly, the HTC Sync Manager, which it just so happens I have installed as well, DID work THANK GOD!
[One (M9) General] schergr:
SIM not detected. Baseband Unknown

After bringing things back to stock in order to get the OTA firmware updates, I flashed TWRP and CM 13 nightly. Upon booting, it says SIM not detected, and stays that way, even after waiting a few minutes.

A quick peek at Setup --> About indicates Baseband: Unknown.

Anyone else having this issue? No SIM, baseband Unknown?

After the restore to stock, and the subsequent OTA updates, this is where I am...

htc_himaulatt PVT S-ON

LK-1.0.0.0000

RADIO-01.01_U11440801_96.01.51207G_F

OpenDSP-v15.6.1.00522.8994_1026

OS-3.38.631.2

Dec 22 2015,16:54:24(682500)

Insights appreciated.

Greg
[One (M9) General] SaHiLzZ:
Ideally you would SOFF, and then flash a RUU, unless there is a modem zip file floating around.
[One (M9) General] schergr:
Indeed, though I don't believe sunshine supports HTC One M9 in 6.0, does it? Have you seen a flashable radio anywhere? Things work fine in stock, its when I install CM 13 nightly that I have the issue. Odd?