yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] bpdamas:
Wow. Worked like a charm. I am unlocked. I have done that method before through a computer so I took a calculated risk to not backup data (it didn't wipe through the computer). It didn't wipe my data. Thanks so much for this. That was awesome. I am rooted now. Fantastic.
[One (M9) Original Android Development] fesustamus:
It's on the Mount menu

---------- Post added at 08:24 AM ---------- Previous post was at 08:17 AM ----------

I realize this is an old thread and there may be an answer in one of the many posts... but on the TWRP "Mount" page, there's a subtle checkbox near the bottom of the screen that says "Only mount system read-only". It appears to affect restorations as well as file manager browsing. I had the same issue of not being able to restore the system partition on a different device until I went to the Mount page and unchecked the system read-only box. Worked fine after that.
[One (M9) Original Android Development] migascalp:
You have see this?
[One (M9) Original Android Development] Nemeth27:
OK, I'm sure I'm missing something. So I installed the beta version of twrp, confirmed that system wasn't mountable so it was read only. And I did tbe backup. Now I received an OTA and when it boots it goes into twrp.

So I'm gathering I need to fasboot flash the original recovery right? Where can I get that? For Dev Edition. I've been doing this since M7 don't know why I feel.lost.
[One (M9) Original Android Development] HolyAngel:
I'm working on it myself right now. I was able to unpack the 401.8 euro recovery with androidimagekitchen and change the default.prop to match dev edition build.prop, then repacked and flashed it in fastboot mode that allowed it to work with the dev ota's, now i'm fastboot flashing stock system.img from my nand and hopefully if all goes well i'll be set.
[One (M9) Original Android Development] Captain_Throwback:
You shouldn't have to change the build fingerprint in the OTA stock recovery. If you look at the updater-script it will usually accept the previous stock recovery, or the version included with the current OTA.

EDIT: Of course that only applies if your updating to the correct version. I see now you're talking about going from Euro to dev. That should work - all it confirms from stock recovery is the build fingerprint. But when it gets to the firmware portion, that'll have to match your device otherwise it'll fail.
[One (M9) Original Android Development] HolyAngel:
yeah pretty much, I don't have dev edition stock recovery, could only get the euro 401.8 recovery and when I first tried to flash the ota it said the device id was wrong, was euro and not dev, so yeah the unpacking and editing default.prop fixed that part. then had to do the fastboot system and it seems to be working, thanks for all the effort figuring this out ;)

edit: aaaaand halfway through the install it now says my system has unexpected contents when I pretty much guarantee its %100 stock from my nand, just renamed emmc.win to img and fastboot flashed it :crying:

Anyone have dev nand?
[One (M9) Original Android Development] Nemeth27:
HolyAngel, based on what I did above would my backup be stock?

Also, I haven't rooted, so if I just flash a stock recovery I should be able to take the OTA, right? Would you be willing to share the recovery to came up with?

Thanks!
[One (M9) Original Android Development] HolyAngel:
idk, sounded like it. I know mine is/was but its still not working. I got the ota at this point though and have removed the sha checking so will try again, won't hurt for you to try.. it'll either work or it won't.

edit: if it does, send me you're system.emmc.win and md5 please lol
[One (M9) Original Android Development] Nemeth27:
I don't have the stock recovery..only the nand I created when I flashed the beta twrp as read only. Do you have the stock recovery you created?
[One (M9) Original Android Development] HolyAngel:
https://www.androidfilehost.com/?fid=95916177934550560

anything else pm me, i don't wanna clutter captain's thread here
[One (M9) Original Android Development] il Duce:
I have the Dev edition, haven't done anything yet with the phone. I might have time this weekend to mess with it. PM me?
[One (M9) Original Android Development] fearomoon:
I have backup of stock System but restore does not work....stuck on boot Screen...

EDIT: Damned.....System is not backed up :((((
[One (M9) Original Android Development] Nemeth27:
Captain, sorry the OT in your thread..
[One (M9) Original Android Development] lukemo:
Sorry but I installed TWRP 2.8.6.0 after unlocking but now I'm not able to flash anything (neither Ruu) cause I got the error:

target reported max download size of 800000000 bytes

Invalid sparse file format at header magi

what can I do now?

Thanks a lot
[One (M9) Original Android Development] DroidShift79:
First of all you should read the first and tge second post carefully...

And then you should try again.
[One (M9) Original Android Development] Captain_Throwback:
Okay I revamped post 2 a bit to hopefully make the situation clearer for people that are new to the device. If people actually read the post, it should answer their questions. Please direct people to this thread if they don't understand what's going on with TWRP on this device. Thanks.
[One (M9) Original Android Development] guidogsbn:
Thanks again for the beta which was a perfect solution just after a day. Big Master as usual. Good for us flashing noobs to have you at our side!.

So not only words: 9MD96342VX976983P :cool:
[One (M9) Original Android Development] Captain_Throwback:
Much appreciated!

This really is new territory for everyone that's used HTC devices in the past, so it'll take some getting used to. If anyone has time to help update some of the TWRP code to better handle the unique situation we're in (and the other devices that use block-based OTAs and could use a similar fix), please submit your code changes to gerrit. It's open source for a reason! All help is welcome.
[One (M9) Original Android Development] WorldIRC:
So if I use TWRP 2.8.6.0 to make my system backup (brand new device, never had TWRP on it before), then flash a custom ROM, and then at some point restore my system backup, OTA will work? Even with TWRP installed?
[One (M9) Original Android Development] Captain_Throwback:
You can NEVER install an OTA with TWRP. That's what stock recovery is for.
[One (M9) Original Android Development] WorldIRC:
Thanks -- so then I would restore the backup, then restore stock recovery, then do the OTA?
[One (M9) Original Android Development] vizzy:
Right. I read this thread this morning but due to dodgy naming of my files i ended up flashing the wrong TWRP so heres what i did:

1. unlocked bootloader

2. installed TWRP 2.8.6.3 (the latest beta posted)

3. did a system back up - it was like 6gb

4. rebotted and copied across lee rom onto internal memory

5. system wiped and installed it, but i got errors and it said no OS installed

6. installed Lee-hima recovery , installed successfully but just sits on black screen

7. .....no idea what to do from here. I have read the thread but it seems i am missing something or doing something wrong. any help?

EDIT: I have it working now :).......sorry to of been an annoyance!
[One (M9) Original Android Development] n3xam:
while trying to root

I get Fail message and a 255 entry in the download mode when i give the fastboot flash recovery command with the last 3 different versions of twrp.

Htc one m9. android 6.0 build nr. 3.36.709.3. Bootloader unlocked and s-on.

I just waited and tried again and it worked. thanks. resolved my problem.
[One (M9) Original Android Development] Johnny424:
[MENTION=1162986]Captain_Throwback[/MENTION] tried google and came across some info regarding my issue. Every time I try to start a backup I get error 255. I pulled the recovery log and found the point it goes south but it doesn't make sense to me. Could you have a look at this screen shot and see what you think I should do?

Att 6.0 HTC m9. Tried backing up to SD card.
[One (M9) Original Android Development] Captain_Throwback:
Log?
[One (M9) Original Android Development] Johnny424:
Thanks for responding .. let me upload the entire log now

---------- Post added at 08:24 PM ---------- Previous post was at 08:19 PM ----------

https://drive.google.com/file/d/0BwoxfVvLyFuyS19ZTVFYTkFfbEU/view?usp=drivesdk
[One (M9) Original Android Development] Captain_Throwback:
First off, have you tried updating your TWRP to the latest version? I won't even bother looking at the log until you do that.
[One (M9) Original Android Development] Johnny424:
I'll look into that. Wasn't aware there was a newer version sense I just flashed mm last week and pulled and flashed what I thought was the newest twrp img from the site
[One (M9) Original Android Development] Captain_Throwback:
The newest one is always at the top, and it's been there for a while. Looks like you just downloaded or flashed the wrong one.
[One (M9) Original Android Development] Johnny424:
OK so I am definitely using 3.0.2-0 now. Running a backup results in the error at the same time right at backing up system
[One (M9) Original Android Development] Johnny424:
https://drive.google.com/file/d/0BwoxfVvLyFuyaEtTVzlnSUFxQ3M/view?usp=drivesdk

[MENTION=1162986]Captain_Throwback[/MENTION]
[One (M9) Original Android Development] Captain_Throwback:
Can you mount System and run this command from adb shell while in TWRP and post the output please?

ls -l /system/app/DriveActivator/lib
[One (M9) Original Android Development] Johnny424:
I most certainly can. As soon as I get home from work this eve. I'll post out put back here

---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------

Unless I can gather info from terminal for you while mobile somehow
[One (M9) Original Android Development] Captain_Throwback:
You can do it from the TWRP Terminal too.

EDIT: In which case, you'll probably want to direct the output to a file to make it easy to upload, so:

ls -l /system/app/DriveActivator/lib > /sdcard/ls_system.txt

And then you can upload ls_system.txt to the thread.
[One (M9) Original Android Development] Johnny424:
OK will do
[One (M9) Original Android Development] Johnny424:


---------- Post added at 06:04 PM ---------- Previous post was at 06:04 PM ----------

This is what I keep getting [MENTION=1162986]Captain_Throwback[/MENTION]
[One (M9) Original Android Development] Captain_Throwback:
That's because you didn't type it exactly as I wrote it. You have to follow my instructions for it to work.
[One (M9) Original Android Development] StephanSch:
It is case sensitive. DriveActivator

The second ls command was better.

Gesendet von meinem HTC One M9 mit Tapatalk
[One (M9) Original Android Development] Binary Assault:
Any update on decryption? I encrypted while on 5.0 using the Viper rom. Updated to the latest TWRP and my rom to 6.0, but still cannot decrypt via TWRP. Sucks because I can't do a nandroid backup.
[One (M9) Original Android Development] Captain_Throwback:
From the OP:

NOTE: TWRP CANNOT decrypt HTC Sense ROMs!!
[One (M9) Original Android Development] computerslayer:
One of my biggest frustrations with HTC is their proprietary encryption scheme - its even affecting current AOSP/CyanogenMod builds (see the CandySix thread). The result is that no custom recovery can decrypt the phone.
[One (M9) Original Android Development] StuPot01:
Is the m9 sense rom encrypted by default? I haven't selected to ever encrypt it so does that mean it should install twrp OK?

I'm on the latest international sense firmware.

The bootloader is unlocked but when I try install the latest twrp via adb it outputs some random text that seems to be command suggestions.. loads of them.

Does adb do that when it doesn't recognise the command?

This is what I've tried:

Adb devices <-- works fine, it recognises the phone.

Adb reboot download / bootloader <-- works fine, reboots to either.

Adb fastboot flash recovery c:\file path.twrp.img <-- out puts loads of input suggestions. No errors or info related to the command I wrote.

I've tried various other flash commands like replacing "fastboot" with "download".

I've read this thread and many other sources for the last few days but I can't get it to work.

It's odd that some adb commands are working but not when I try to flash the file.

The twrp file is in the same folder as fastboot, adb and related files, it is the latest and renamed to twrp.img (even tried TWRP.img), drivers are up-to date, so is adb and fastboot.

I also have this error on the phone screen when in download mode:

"FILE /mnt/media_re/ext_sd//OPJAIMG.zip file not found"

Is that why twrp won't flash?
[One (M9) Original Android Development] StuPot01:
Well I'm a little stuck here..

I've rooted many phones but this has got me a little stumped. I've read and re-read this thread and I've no idea why it won't flash.

I've gone through the HTC dev site and re down loaded drivers, twrp fast boot and adb but it still won't flash.. just getting a load of command suggestions like it doesn't know what the command I've typed is.

I'll try again in a couple of days when the frustration has passed :D

I think the only thing that the problem could be is corrupt downloads because I've followed all steps to a tea. Adb isn't even throwing any errors.. just command suggestions when I do what I mentioned in the post above this one. I'm certainly not a dumb twat but this has me a bit stumped.
[One (M9) Original Android Development] Black-FR:
You can't flash anything in download mode, via adb.

There you need to use fastboot.

The command, to flash the recovery would be:

fastboot flash recovery Name_of_recovery.img

Gesendet von meinem HTC 10
[One (M9) Original Android Development] StuPot01:
Thanks a lot for your reply, much appreciated.

OK, I'll have another go in a couple of days on my next days off work,

I've used HTC as my main phone for quite a long time but I've always put off of rooting them up until now because I aren't exactly savvy with adb and fast boot. I'll do more research to make myself a little more familiar with the two over the next couple of days.

Again, thanks for the help.
[One (M9) Original Android Development] StuPot01:
Thanks a lot for that buddy, it made me realise i need to read up on adb and fastboot and now the phone has twrp, supersu, custom rom installed so i feel like a kid with a new toy again haha
[One (M9) Original Android Development] kemoli:
i have a problem with root, i am s-off, bootloader open, i have twrp as recovery, but everytime i want to install su.zip , the cellphone just got stuck in the htc one white screen or in bootloop...i have a image recover so, i just keep trying that one....any ideas what i can do for getting root? i don´t know what i am doing wrong.

thanks in advance for helping me
[One (M9) Original Android Development] Captain_Throwback:
Use the stable SuperSU version 2.65. Newer (Beta) versions don't work on the M9.

P.S. That's the version that's linked in the FAQ on the first page. I know you read that, right?
[One (M9) Original Android Development] kemoli:
yes and use a stable one, that´s the reason why i don´t know is not working, i flash a few cellphone and tablets that i own. so i don´t why is not working, i flash the 2.46 version.
[One (M9) Original Android Development] Captain_Throwback:
The LATEST Stable version. Not an old version. Did you even follow the link in the OP?
[One (M9) Original Android Development] kemoli:
ythank you very much!!! not it works!! yes i follow it, but i confuse files in the download section!! thanks!!
[One (M9) Original Android Development] Adromir:
Apparently it depends on the rom. I am on aicp and the SuperSu 2.74 Beta works fine for me
[One (M9) Original Android Development] kemoli:
just for the record, i use stock rom android version 6.0.
[One (M9) Original Android Development] teddy0209:
Coming from 2.65, 2.74 does not work... But it works with clean start, (from restored system.img and no apps on /data)
[One (M9) Original Android Development] sanju_barc:
I am on lollypop 5.01 and upgraded twrp from 2.8.7 to 3.0.2 Now I am getting message " Failed to boot to recovery Mode".

Please suggest possible fix.

I desperately need to boot to recovery to flash Marshmallow

Thanks
[One (M9) Original Android Development] Black-FR:
You need to update your firmware first.

The newer twrp version, needs also the marshmallow firmware.

Gesendet von meinem HTC 10
[One (M9) Original Android Development] sanju_barc:
Finally problem could be fixed by flashing TWRP 2.8.7.1 via add booting phone in download mode.

Thanks for the reply
[One (M9) Original Android Development] RoxelloX:
Get in Mount and uncheck " only mount system read-only !!! :D
[One (M9) Original Android Development] DxMo:
In the windows command i have to write:

fastboot flash recovery twrp-3.0.2-0-m8

or am i missing something?

Thank you!
[One (M9) Original Android Development] teddy0209:
The file extension, .img
[One (M9) Original Android Development] DxMo:
And could i just rename the file? For example like this? :

Twrp-3.0.2-0-m8.img to TWRP.img and just wirte in windows command: fastboot flash recovery twrp.img

Tnak you!
[One (M9) Original Android Development] teddy0209:
Yes[emoji6]
[One (M9) Original Android Development] DxMo:
This shows when i tried to install TWRP in windows command: Failed(remote cannot flash this partition in S-on state)

What is this? I cant get acces root without S-off?:cyclops::cyclops:
[One (M9) Original Android Development] teddy0209:
I am s-on... what mode did you try? Download mode or in bootloader? Try the other, then it should work...
[One (M9) Original Android Development] DxMo:
I wrote in commands windows: abd reboot bootloader and then fastboot flash recovery twrp.img

Is something wrong?
[One (M9) Original Android Development] teddy0209:
Use download mode instead, one with black background if I'm not mistaken...
[One (M9) Original Android Development] DxMo:
Yes it charged on the blackscreen now i got this: C:\Users\XXX\Desktop\ADB and Fastboot files>fastboot flash recovery twrp.img

target reported max download size of 800000000 bytes

sending 'recovery' (20046 KB)...

OKAY [ 1.970s]

writing 'recovery'...

(bootloader) HOSD CL#671447

(bootloader) start@1

(bootloader) recovery@100%

(bootloader) Update partition OK

(bootloader) end@Done

OKAY [ 2.408s]

finished. total time: 4.379s

C:\Users\Jose\Desktop\ADB and Fastboot files>

But now, where is the option to acces TWRP to flash SuperSU? and in what folder i have to save SuperSU Zip to flash it?

Thank you!

---------- Post added at 12:54 PM ---------- Previous post was at 12:41 PM ----------

I installed the 2.8 TWRP and it finnaly worked but in the moment to Install SuperSU 2.64 the TWRP says: This operation may install incomaptible software and render your device unusuable. Shloud i continue? :confused::confused::confused::confused::confused::confused:

I dont know what supersu i have to install 2.64 or latest? I found conflicting information

[MENTION=3615867]teddy0209[/MENTION]
[One (M9) Original Android Development] teddy0209:
Use the latest 2.76.... You're still using Lollipop?(android 5.0)...
[One (M9) Original Android Development] DxMo:
I'm on marshmallow and i got root flashing 2.64. Should i update SuperSU from PlayStore or just keep the 2.64 v?

Thanks
[One (M9) Original Android Development] teddy0209:
If you're on MM, you can use twrp302... It's best to flash the latest 2.76.... Clean start maybe required though...
[One (M9) Original Android Development] DxMo:
Clean start is just repeat the fastboot flash recovery *twrp name* in commands windows and then flash SuperSu zip no? dont i lose my archives?; Or i have to Reset Factory Data and then re-install all?
[One (M9) Original Android Development] teddy0209:
Clean start, I mean nothing is installed yet (if flashing supersu2.76 over 2.64 doesn't work)... You can update twrp to 302 by booting to twrp recovery and flashing the twrp302recovery.img

Edit: flashing supersu might cause bootloop, so make a backup in twrp prior to flashing...
[One (M9) Original Android Development] DxMo:
So the steps are:Backup, Factory reset, Flash twrp 3.0.2 and then flash lastest supersu, no?

Sorry for too many questions, im new and so lost on HTC, and thank you.
[One (M9) Original Android Development] DxMo:
I just did a complete backup of my phone with Titanium but mu question is, if i flash twrp 3.0.x and then i flash last supersu? will i lose any archives?
[One (M9) Original Android Development] teddy0209:
[MENTION=7469987]DxMo[/MENTION]

Backup in twrp not using titanium... You won't lose anything... The backup is just for emergency.... Since you're new to HTC, read everything in the OP, the faq's...
[One (M9) Original Android Development] DxMo:
Ok thank you teddy, i will try it tomorrow and if i have some doubts i will ask you here :p

Thanks for the answers :)
[One (M9) Original Android Development] brockyneo:
hi guys just got my m9 and i have unlocked my bootloader and trying to gain root so i can soff but here is my message

target reported max download size of 536870912 bytes

sending 'recovery' (19912 KB)...

OKAY [ 0.531s]

writing 'recovery'...

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

finished. total time: 0.562s

any ideas please
[One (M9) Original Android Development] teddy0209:
Flash in Download Mode
[One (M9) Original Android Development] brockyneo:
thanks all done now ;)

now time to see if the m9 is going to replace my z3 lol :laugh:
[One (M9) Original Android Development] BigShowSavas:
I might be missing something, but i just cant get my M9 to accept the recovery. I reboot to download mode, while connected to PC (debugging is On), try the flash and this is what happens in command prompt:

C:\adb>fastboot flash recovery twrp.img

sending 'recovery' (19912 KB)...

FAILED (data transfer failure (Unknown error))

finished. total time: 1.003s

C:\adb>

On the phone the screen changes to:

Download 0%

Start Downloading (highlited but nothing i press will do anything)

forgot: Bootloader unlocked via HTC Dev, Android 6.0, Sense 7.0, Firmware 3.35.401.12

edit 2: seems it was a problem with the pc, probably the xfast usb. tried on my old laptop and it worked.
[One (M9) Original Android Development] makavellys:
Htc one m9 (sprint)

Ok guys, i have a HTC One M9 (Sprint / Android 6 (RUU_HIMA_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_3.41.651.4)). I installed last version of TWRP (3.0.2.0) after that i installed SuperSU (V. 2.76). But after these manipulation my phone doesn't boot (stuck on the HTC ONE screen)...

P.S. - Bootloader is unlocked / S-ON
[One (M9) Original Android Development] teddy0209:
Restore your boot.img... start clean or wipe /data prior to flashing supersu...
[One (M9) Original Android Development] makavellys:
I restored boot.img but anyway is stuck on HTC ONE screen..:(
[One (M9) Original Android Development] Captain_Throwback:
Find SuperSU v2.65 and flash that. That's the last known working version on the M9.

EDIT: I just added a link to it in the FAQ.
[One (M9) Original Android Development] sanju_barc:
@ makavellys, exactly same happened to me too. Finally relocked the bootloader and flashed ruu again. Now on stock MM. But eager to root again if issue resolve.
[One (M9) Original Android Development] computerslayer:
^^^This. I had the same problem when flashing the latest version of SuperSU (currently 2.76).

Once you've flashed version 2.65, you can update to 2.76 via the SuperSU app within Android. For whatever reason, flashing it always results in a bootloop.
[One (M9) Original Android Development] stingerbs:
So I was an idiot and wiped my stock recovery file on TWRP AND wiped my phone clean as well. I want to go back to stock unrooted so I can update my M9 running 5.1 (2.11.502.18). to 6.0. What would be the fastest way to achieve this now that everything is wiped on my phone?