yashsingh1/xdaforums huggingface dataset:
[One (M9) General] Tirofog:
I'm s-on, trying to get back to stock for the Nougat ota. So I check the mount system read-only box and try to restore my unzipped stock backup (3.35.401.32) but get as far as 'Cannot restore system - mounted read only'. I tried renaming the three system files in the backup to 'system_image.ext4.win000' etc. after reading something in the TWRP thread, but then I get the message 'Partition system image cannot be wiped'. The only way to restore the backup is to uncheck the system read-only box, but then of course the ota fails.. appreciate some help with this before I go nuts..
[One (M9) General] Jooneed:
[MENTION=4373016]Tirofog[/MENTION], as far as I know, and the more knowledgeable people here can correct me, you check "mount system read-only" ONLY when doing the stock recovery/system backup prior to flashing twrp/rooting. When going back to stock, you just go to twrp, and restore the twrp images... Check post#10 of this thread...
[One (M9) General] Flippy498:
Are you sure that you backed up the correct files while creating your backup? The system image consists of one file not three. Sounds like you backed up the system instead. (The latter is only needed by devs who want to create custom roms based on the stock rom.)

The easiest solution would be downloading a backup with the correct files or a RUU from page 1.
[One (M9) General] Tirofog:
The backup I'm using is from page 110, it contains the files as in the pic, which are the same as in the 3.35.401.12 backup from page one..

Edit: tried the 3.35.401.12 backup but same thing, Cannot restore system - mounted read only..
[One (M9) General] Flippy498:
That's a backed up system partition not a system image. You can't use that backup with the guide in this thread.
[One (M9) General] Tirofog:
Well the 3.35.401.12 backup from your post on page 1 gives the same result so I'm lost..
[One (M9) General] Flippy498:
Please post the direct download links you're using. I've just been reading page 110. There's no 3.35.401.12 backup on that page. And the link on page 1 is from my own AFH account. I haven't posted any direct links in this thread in any other location than page 1 since the thread ownership got handed over to me.

Edit: Oh well, it looks like a handful of mistakes happened at once. I missed that the fact that you're on the 32 version in your first post. Then it looks like that backup for 3.35.401.32 on page 110 is a system dump. In other words it's for devs that want to build a custom rom based on the stock rom not for users who want to get back to stock. I haven't expected someone to post a system dump here that's why I didn't check contributions of other user in the past. And in addition it looks like I copied that link to the wrong firmware version on page 1.

Sorry for the confusion. I'll remove that link from page 1 since it's useless for most of you guys.

Nonetheless, your situation is still solvable. It's mentioned in the RUU section.
[One (M9) General] Tirofog:
My firmware is 3.35.401.32 which is why I tried this backup from [MENTION=4445238]Golv[/MENTION] on page 110: https://docs.google.com/uc?id=0B4oyO3CwWup3eWZRY1lRTFZkc3c&export=download

The 3.35.401.12 backup is from page 1: https://www.androidfilehost.com/?fid=24421527759888529 but no go with that either.
[One (M9) General] exocetdj:
Announcement, Chuck me ur firmwares! Lolol. I'll sort that tonight

Anyone else think this is a good idea?

FIRMWARE COLLECTION TO FOLLOW TONITE.

any ideas for the 6th and final post lemme know
[One (M9) General] clsA:
CID For the Developer edition is BS_US001 or BS_US002

fastboot oem writecid BS_US001

For MID
[One (M9) General] Sameh mohamed:
Thanks a lot for help i used 1.32.401.17 R1 executable RUU and finally it worked (though the status is still modified :eek:) i received the OTA and it was installed seamlessly
[One (M9) General] :
Thanks a lot for the stock recovery! :good::laugh:

I can confirm the stock recovery for

works (boot-able) for HTC_044 on rom 1.40.708.9. Though I haven't performed an OTA through it to see whether it is fully functioning.
[One (M9) General] Nima78600:
Glad to see succeed?. Running executable RUU doesn't give you "official" status. You should use sdcard method to have it.
[One (M9) General] RolandCruise:
Downgraded from 1.32.401.17 to .15 while S-ON through microsd method

I'd like to thank you becuase thanks to your experience I was able to have a successful evidence before trying to go back from .17 to .15 to receive the 1.40.401.8 OTA.

Without your post, maybe I wouldn't have found the courage to do this until the very final confirmation that I had to stay on 1.32.401.17 indefinitely because I flashed it via RUU.exe sinning impatience... :victory:
[One (M9) General] mattlovell90:
Glad I could help! I accept donations in the form of beer or cider :cool:
[One (M9) General] exocetdj:
Pmsl!

That's one way of getting donations I suppose :laugh:

Anyway u guys probably noticed the new firmware section the magic fairies set up last night!?

No? My apologies, I have just escaped from the 24 hours of le man's after watching about 15 odd hours of what was the most epic race I have ever seen.

Hopefully get a firmware slot thrown together later. Apologies if world war three started because I didn't do it hahaha have a good Sunday chaps, keep the fun flowing and if anyone's got any links for me, post away. ;)
[One (M9) General] tango280581:
My apologies in advance, I'm a bit special. I've downloaded the rar file for my firmware, extracted the folder inside to the twrp back up folder. Go into twrp then backup but it doesn't show the folder. Can anyone tell me what I'm doing wrong please? Thanks in advance.
[One (M9) General] jamieunit:
What are you trying to do? Update firmware or just flash a backup
[One (M9) General] blocka:
Flash Stock Recovery Failed

Hi all,

I've received OTA 1.140.8.1.

I tried to restore the stock recovery.

I've got myself a bit of a problem flashing the stock recovery back. I'm getting the error below....

I'm rooted, with TWRP Recovery.

Question, do I need to restore the stock NANDROID / RUU backup prior to reflashing stock recovery so I can take the OTA?

I'm downloading ATM the nandroid backup for my model CID.

Where are the RUUs' available?

Thanks guys/gals.

Error Message

c:\Temp>fastboot flash recovery HIMA_UHL_Stock_Recovery_1.32.401.15.img

target reported max download size of 536870912 bytes

sending 'recovery' (32848 KB)...

OKAY [ 1.326s]

writing 'recovery'...

FAILED (remote: cannot flash this partition in s-on state)

finished. total time: 1.420s
[One (M9) General] Nima78600:
Yes you need to restore a nand backup of your rom and stock recovery or flash stock rom (0PJAIMG.zip or RUU) compatible with your model and cid from the link below.

http://androidruu.com/?developer=M9
[One (M9) General] tango280581:
Flash a back up mate
[One (M9) General] blocka:
Thanks.

I've grabbed a copy of http://androidruu.com/getdownload.php?file=M9/0PJAIMG_HIMA_UHL_L50_SENSE70_HTC_Europe_1.32.401.15_R1_Radio_01.01_U11440261_56.02.50306G_2_F_release_426891_signed.zip and https://www.androidfilehost.com/?fid=95916177934553346

Ideally I'd like an RUU (exe)

I checked the TWRP (NAND) I downloaded and noticed there are significantly less files in the backup and comparing it to a TWRP I've done I was expecting to see more files.

These are the files in the TWRP that I download.

boot.emmc.win

boot.emmc.win.md5

system.emmc.win

system.emmc.win.md5

How much data will I lose when I restore the TWRP?

High level...

I need to extract the NAND and copy into my TWRP location (ex-SD) boot into recovery, restore the recovery, flash stock recovery, download the OTA, apply OTA, install TWRP, take a stock NAND then go ahead with rooting and restoring from TB? I read somewhere that you need to rename one of the files adding an underscore ' _ ' but I can't recall if that was for this process or something else?

Thanks for ya help
[One (M9) General] Nima78600:
Actually I didn't test this method. But if you need to keep your data and want to restore from nand backup just read question 8 in post 3 from this link.

http://xdaforums.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720

But if you don't care about your data it's easier to flash stock rom either sdcard method or Ruu.
[One (M9) General] jamieunit:
Did you stick it in your external SD or internal and that twrp is looking in the right place,
[One (M9) General] exocetdj:
Inside twrp there's a folder called backups in backups there's a folder with a string of random letters and numbers the unzipped backup folder goes in there
[One (M9) General] tango280581:
Thanks a lot
[One (M9) General] SoLdieR9312:
The "string of random letters and numbers" is the device serial number =)
[One (M9) General] JohnCorleone:
OK guys, I finally got everything in place and I am about to get started but I have one quick question.... I am on T-Mobile. I unlock the bootloader, flash the TWRP, then make a backup of the stock setup BEFORE rooting, then go back and root. Is this correct in case I need to get back to stock and flash the stock T-Mobile recovery.img that is hopefully available? Do I have everything right? Thanks in advance!

Edit..also I am on the updated software 1.32.531.33 so if I can be of any help as far as providing a stock recovery, just give me a quick tutorial on how to pull it...unless its the same as the T-Mobile .15 version
[One (M9) General] Flippy498:
Please take a look at the edit of my last post. That was (partially) a mistake on my side. Of course you can't use a backup for 3.35.401.12 while being on 3.35.401.32.
[One (M9) General] Tirofog:
Thanks for the clarification.. so in the absence of a 3.35.401.32 RUU or backup I guess I'll need to use the 3.35.401.12 RUU and that should work, yes?
[One (M9) General] Flippy498:
As written in the RUU section:
[One (M9) General] Flippy498:
And did you read this thread further than the opening post? (I'm continueing this discussion in the ReadMe thread since it has nothing to do with the Viper rom.)
[One (M9) General] irshaad86:
My mistake, I've went through to the T-mobile section without reading the readme thread completely as I thought it will have the relevant info.
[One (M9) General] :
I flashed latest nougat RUU and then installed Lineage OS . Now i want to go back to complete official Lollipop firmware . Do i have to download the RUU or does this TWRP backup also do the same work as RUU ???
[One (M9) General] Flippy498:
First of all, you need S-OFF if you want to downgrade (and don't want to rely on a very risky method - I don't support the risky method here. You will need to search for it on your own.).

TWRP Backups only contain the system/rom. That's why they can't be used for up- or downgrading. The mismatch between firmware and system version results in bugs/lags (if you're lucky and the phone boots) or a bootloop. C.f. the article that is called "the difference between rom and firmware" in the further reading section if you want a more detailed explanation.

If you have S-OFF you need to flash a 3.x firmware pack from Sneakyghost's firmware thread. Firmware 4.x uses a different encryption key so that you can't use older RUUs without flashing the old firmware, beforehand. Fortunately, Sneakyghost's packs aren't encrypted since they're custom made (the firmware inside is official, though).
[One (M9) General] krGemini:
[MENTION=5872674]Flippy498[/MENTION], looking for a little help

my little nephew has bought a one m9 which states opja100 as model on casing, but when i executed getvar it states MID as OPJA20000 and CID as 11111111. I am confused whether it's CDMA or GSM version.

the bootloader shows following:

htc_himawhl XC S-OFF

CID-11111111

LK-1.0.0.0000

RADIO-3.00.C1144084@60114

OpenDSP-15.6.1.00522.8994_1026

OS-3.41.651.4

From this, it seems that it's a sprint unlocked model and from a bit searching i came to know that this model supports both gsm and cdma

does this imply that the MID of the device is changed as the phone also carry a sim card slot and work on gsm networks.
[One (M9) General] Flippy498:
So, let's begin with the difference between the models. Hima_ul and Hima_uhl are both GSM variants whereas hima_wl and hima_whl are CDMA phones. Those are different network technologies that are not compatible with each other. The partition layout of the CDMA variants differ from the GSM versions. Flashing CDMA files on GSM or vice versa will most likely result in unrecoverable hardware damages. Not even the different CDMA variants share the same partition layout so that flashing Sprint files on Verizon phones or vice versa isn't possible, either. The partition layout of the two GSM version on the other hand is one and the same. That's why you can convert GSM phones without any risks.

Now, let's come to your nephew's phone. The CID has nothing to say in this case. As soon as you have S-OFF you can change the CID to whatever you want. No matter which variant you own. (You should get rid of the SCID, nonetheless, since it prevents the M9 from being able to receive OTAs.) Unfortunately, more and more people replace the housing of their phone since the original one got damaged at some point. The problem is that those people don't seem to care whether the replacement housing they use corresponds to the actual version of the phone they own. This leads to frankenphones (the term originates from Frankenstein's monster) that consist of parts that originally belonged to different variants.

Newer CDMA phones (the M9 belongs to this category) support some (not all!) GSM frequencies. The reason behind that is that LTE is a GSM-only technology. Therefore, CDMA phones need be able to support GSM frequencies if they want to be able to support LTE. That's why newer CDMA phones have a sim card, as well.

If the phone was converted from GSM to CDMA or vice versa you wouldn't be able to get any reception, no matter which sim card you use. Therefore, I assume that it's a Sprint frankenphone in a housing of the Hima_uhl variant.

Further reading:

GSM vs. CDMA

The RUU Section of this thread

The OTA Section of this thread

The FAQ of this thread (c.f. Q11 & Q13)
[One (M9) General] krGemini:
Thanks for the detailed reply, that have cleared many of the confusions already. Just another little query, currently the phone has supercid and twrp so if he want to get OTA he just have to change the CID and flash the RUU that correspond to his SKU ?
[One (M9) General] Flippy498:
Correct.
[One (M9) General] milos.kn:
Hey guys,

I need RUU for this:

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) version-main: 3.35.401.12

(bootloader) boot-mode: download

(bootloader) version-baseband: 01.01_U11440792_97.00.51203G_F

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: CID__058
[One (M9) General] Flippy498:
The needed RUU can be found on page 1. Read the RUU section. It contains the info that you need for finding the correct file.
[One (M9) General] milos.kn:
I couldn't match CID. Phone is S-ON. It needs to be CID__058
[One (M9) General] Flippy498:
Oh, I missed the CID since I only looked at the firmware version.

That CID doesn't exist on the M9. In other words, that phone was S-OFF at some point and someone tinkered with the CID. You'll need to re-S-OFF the phone if you want to be able to fix it.
[One (M9) General] milos.kn:
Oh... Okay, thanks a lot!
[One (M9) General] Tetragrammazoid:
I cant quite get it Please can you guys advise me (HTC One M9)

Hi Guys,

Could someone please assist me? :confused:

I'm a bit overwhelmed.

I unlocked the bootloader via HTCdev on my HTC One M9 (running Nougat 7.0 from Vodafone) it reset to factory settings after reboot. (Which was expected).

I then installed TWRP (version: twrp-3.1.1.0-him.img) via fastboot and after that I flashed SuperSU (version: SR4-SuperSU-v2.78-SR4-20161115184928.zip).

Now the HTC One M9 hima_uhl Vodafone UK CID VODAP001 (previously unlocked from carrier and working) will not recognise SIM cards and the IMEI number is missing along with this other information:

IMEI : UNKNOWN

IMEI SV: UNKNOWN

IMSI: UNAVAILABLE

BLUETOOTH ADDRESS: UNAVAILABLE

---------

The software version is:

SOFTWARE VERSION: 4.17.161.11

Build number: 4.17.161.11 CL859282 release-keys

I've read through the forums and the net, I downloaded a file which looks correct but I'm unsure how to proceed exactly or whether I've really got the right file.

I downloaded this file from Android file host which was linked in this thread:

0PJAIMG_HIMA_UHL_N70_SENSE80_MR_Vodafone_UK_4.17.161.11_Radio_01.01_U114401031_124.01.70203G_F_release_500907_combined_signed_2_4

I've also found these downloads from the same source:

http://androidfilehost.com/?a=show&w=files&flid=178206

which I noticed includes a

"Full_Stock_firmware_4.17.161.11_(with_wipe).zip"

and a,

"Full_Stock_firmware_4.17.161.11_(with_wipe)_signed.zip"

these last two are 220 MBs in size compared to the 2GB Vodafone one I mentioned I've already downloaded.

I can confirm TWRP is installed in my phones recovery and phone root access was granted after flashing the SuperSU.

I've included a Systems Provisions text file in this post which I got from using an App from the playstore.

(I used Wi-Fi to download it).

Could someone please, please tell me how to proceed, I'm terrified of bricking the phone.

Thank you so much for any help.
[One (M9) General] Flippy498:
Why did you flash that version? As explained in this thread, in Captain Throwback's TWRP thread and several threads in the Q&A section not every SuperSU version is compatible with the M9. This group of incompatible versions includes the one that you flashed (c.f. the FAQ of this thread).

That's actually a bit unexpected. From my previous experiences a non-compatible SuperSU version should lead to a bootloop and not to the issues that you're facing. What you describe sounds similar to the issue in Q1 of the FAQ but that would mean that you flashed more than just TWRP and SuperSU.

How about following the instructions directly above the download links?

The smaller packages are custom made firmware packs like the ones that can be found in Sneakyghost's thread. You need S-OFF if you want to be able to flash them.
[One (M9) General] dying4004:
guys, can you please guide me to find the below? cheers

C:\Fastboot>fastboot getvar all

(bootloader) kernel: lk

(bootloader) product: htc_himauhl

(bootloader) version: 1.0

(bootloader) current-slot:

(bootloader) version-main: 4.30.841.1

(bootloader) boot-mode: download

(bootloader) version-baseband: 01.01_U114401011_117.00.61117G_2_F

(bootloader) version-bootloader: 1.0.0.0000

(bootloader) mid: 0PJA10000

(bootloader) cid: TELST001

all:

finished. total time: 0.000s
[One (M9) General] Flippy498:
So far, no one has contributed files that you could use. You'll need to either use the RUU service that is linked in the useful links section or to search on websites like ir-file or easy-firmware.
[One (M9) General] Tetragrammazoid:
I'll buy you a coffee if you can please guide me Flippy

Hi, Thanks so much for trying to advise me with this. I'll buy you a coffee to show my appreciation if would please guide me in a 1, 2, 3 type list of what I should do. The reason I installed SR4-SuperSU-v2.78-SR4-20161115184928 was because I was following this article:

http://joyofandroid.com/how-to-root-the-htc-one-m9/

The link he gave in the article took me to to that SuperSU file:

http://download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip

( I was trying to look through the XDA Noob Friendly guide originally, but some of the links from it weren't functioning. So that's why I followed that other guide).

I can't figure how to quote again, so I'll use quotation marks:

"That's actually a bit unexpected. From my previous experiences a non-compatible SuperSU version should lead to a bootloop and not to the issues that you're facing. What you describe sounds similar to the issue in Q1 of the FAQ but that would mean that you flashed more than just TWRP and SuperSU."

Really I swear I didn't flash anything else,, I just unlocked with HTC dev and followed that guide above, only thing different was I used latest TWRP 3.1.1-0

"How about following the instructions directly above the download links?"

I'm unsure of what went wrong exactly and worried I will get it wrong.

"The smaller packages are custom made firmware packs like the ones that can be found in Sneakyghost's thread. You need S-OFF if you want to be able to flash them."

Would you please tell me what to do exactly? Like: 1, 2, 3.

I will buy you a coffee! :)

Extra info: The IMEI is showing via System Info in the volume down and power button screen but not in the actual phone when it's turned on. :/
[One (M9) General] Flippy498:
You better thank god that you didn't follow the second part of that guide. Kingroot installs malware on your phone and/or your PC (depending on which version of it you use). Let me be honest, that website is cr@p. Instead of linking chainfire's website so that users are able to get the latest SuperSU version they link a specific version and that one isn't even compatible with this phone.

The "noob friendly" guide is completely outdated and didn't get updated in ages. However, you can find all guides you might ever need in this thread. That's why it's stickied on top of the General and the Q&A Section and why it's called "ReadMe".

Did you already take a look at the guides in this thread? It doesn't sound like you did. If you did you wouldn't make such a request. ?

That's normal for the issue in Q1 of the FAQ. The problem of that Q is caused by a boot.img that's not compatible with your current firmware. However, for creating that issue you would need to restore a TWRP backup that isn't meant to be used on your phone or to flash a custom rom that's not compatible. SuperSU doesn't exchange the boot.img. It keeps the original one and introduces changes to the it but those don't result in that problem.
[One (M9) General] Tetragrammazoid:
Help please

Well yes it does appear something has gone badly wrong. I certainly won't be using that site again, nor recommending them, and I shall write to him to tell him his guide could be causing issues for many people.

Yes I've tried my best to understand it but I'd like to double check with someone more experienced as I've already encountered this issue I have now by following guides on my own, I don't want to do it risk it unnecessarily if at all possible.

Yes as I've said, I don't feel comfortable steaming in on my own, I don't think there's any shame in asking for help. I think its better to check with a Pro. I'm a noob.

That's odd because I didn't flash any boot image at all. I didnt even have another ROM, the ROM is the one that was already on it, it just reset to factory condition after unlocking the bootloader from HTCdev, then fastbooting TWRP to recovery and rebooting the phone. (no new ROM was introduced from outside at all) the Vodafone Nougat 7.0 Software rebooted clean after unlocking the bootloader but the radio and other info, IMEI etc was gone, and the sound too I've just discovered.

The software checks out for the serial numbers of the phone etc, software matches last release from Vodafone UK but not HTC.

Perhaps Vodaphone flash the software on top of HTC firmware that already includes the radio info etc?

Its a second hand phone, I've only had it a week, I just wanted to root to use Greenify but now all this and I tried asking HTCdev but I just keep getting 504 timed out responses from their online form. I've spent many hours trying to find exact instructions from someone that knows what they're talking about, just to be sure I'm doing the right thing. I can't afford another phone. :(

If you can help, I'll buy you a coffee! Or anyone reading if you know and can give me clear instructions, a coffee and a great amount of appreciation is yours! Please help. _/\_ :)