yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] weinberk:
The idea is to have the device wipe itself before it can be brute forced. "Hey, the phone is encrypted says the person who found it." It gets sold to someone in the underground and they go mining. Sure, passwords could be reset before that and the sim deactivated, but there's still potentially valuable data on the device.

I'd think that ADB or other tools would make it possible to do an image of an encrypted device, then just brute force away. With the ability to truly remote wipe, it would add piece of mind, giving it the best shot to protect the data that's on the phone. I don't know if it's easy to remove the wipe flag, or if that's even relevant.

And I know that remote wiping it reduces the chances of a lost phone being returned, but someone can still return it using the sticker with my contact information that's on the back. Real world, a lost phone in a city cab isn't coming back anyway.

Thanks for asking for reasoning. Hope this explains it.
[One (M9) Original Android Development] Captain_Throwback:
Unless Android Device Manager sends a different, special command to reset/wipe the device, there's no way to differentiate that from a standard factory reset, unfortunately. I don't think things possible, but toucan open an issue in Github for it and see what the TWRP devs come back and say. I'd include your complete explanation here as well.
[One (M9) Original Android Development] weinberk:
Before I post over at github, why would we need/want to differentiate from a standard factory reset?
[One (M9) Original Android Development] Captain_Throwback:
Because some people accidentally trigger a factory reset when playing around with custom stuff, and there is some expectation that having TWRP on the device would prevent them from losing all of their data. It's essentially the opposite side of the argument - that TWRP shouldn't respect the factory reset command because otherwise what's the point of a custom recovery? However, if there's a way to differentiate between the remote wipe command and the standard factory reset, we may be able to make everyone happy.
[One (M9) Original Android Development] weinberk:
That's a REALLY good and important point! Hadn't considered that.

(easy solution, have TWRP use the front camera to see who is using the device. If it's the user, then don't wipe, if it isn't the user, then wipe. I'll be sure to let the devs know that this was your idea :D )
[One (M9) Original Android Development] Captain_Throwback:
This one is for you: https://gerrit.omnirom.org/22389

We'll see what kind of response it gets...:eek:
[One (M9) Original Android Development] weinberk:
grateful
[One (M9) Original Android Development] drakeNas:
Is the fastboot boot recovery command working again?
[One (M9) Original Android Development] Captain_Throwback:
Read the FAQ.
[One (M9) Original Android Development] drakeNas:
***delete***
[One (M9) Original Android Development] Boskoel03:
Cap one thing i noticed using last official recovery,3.1.0,is that now phone when flashing rom does get really hot,recovery says 50c,and that was not the case earlier,not sure it is recovery related,but that is only thing i changed,rom's are the same,earlier never pass 45c... Just mentioning not sure there is something that can be done about it....
[One (M9) Original Android Development] Nimir:
Hi,

Today morning my m9 unexpectly reboot and stuck in bootloop.

I tried to boot into TWRP and recovery said "unmodified system partition" and ask to keep it read only or allow modifications.

I allow modifications and tried to wipe but

Recovery said:

"couldn't mount /data and unable to find crypto footer.

failed to mount /cache

failed to mount /system.....

"

I'm on 3.35.401.12 firmware and twrp 3.0.2

I tried update TWRP

but after restart it is still 3.0.2 and problems with mounting /data

Could you help me?
[One (M9) Original Android Development] Captain_Throwback:
Can't help until you read the OP under "Bug Reporting" and provide what's asked for...it sounds like TWRP isn't your problem, though.
[One (M9) Original Android Development] Nimir:
Hi,

Of course I forgot.

So please find file.. and if you can help me.
[One (M9) Original Android Development] Captain_Throwback:
Looks like your device is broken and you need to RUU. That should fix you up.
[One (M9) Original Android Development] Ainz_Ooal_Gown:
Okay so i just unlocked my bootloader (I'm on 5.0.1 Lollipop Sprint Variant) i want to flash TWRP in order to flash the Latest Viper Rom and it recommends the latest TWRP, but on here it says the latest one won't boot on Lollipop so do i just take an OTA or what?
[One (M9) Original Android Development] Afeef.mlk:
Lock back your bootloader. Take OTA and update your phone to latest nougat sprint firmware. Then unlock bootloader and flash twrp 3.1.0.0
[One (M9) Original Android Development] Ainz_Ooal_Gown:
bruh :V lol well thank you now to do more work lol
[One (M9) Original Android Development] nkk71:
Don't relock your bootloader, it's not needed for OTAs.
[One (M9) Original Android Development] Ainz_Ooal_Gown:
the **** .-.
[One (M9) Original Android Development] nkk71:
:confused:

I just wrote a quick reply, so you avoid a potentially huge headache.

Locked/Relocked bootloader is not necessary for OTA, it never was.

It

used to be

necessary for RUUing older devices, like the M8 or M7.

This is no longer the case for the M9 or 10.

And it was never necessary for an OTA.

The above remarks would be completely irrelavant if you are S-OFF, in which case nothing matters, and you can just flash an unsigned firmware package (a full one is preferred, not an incremental one).

And be sure to stay S-OFF.

M9 is an FRP enabled device, so relocking bootloader, may result in "the **** [just happened] .-." statements, and headaches. Which is why I made a quick post, so you avoid problems.
[One (M9) Original Android Development] Afeef.mlk:
Oops i didn't knew about unlocking bootloader. But I guess it won't be any problem if you have locked it back. You can unlock again anytime. Am i right ?
[One (M9) Original Android Development] Ainz_Ooal_Gown:
Thanks guys

---------- Post added at 11:17 AM ---------- Previous post was at 11:07 AM ----------

Pro tip: In the latest versions of Windows 10 Command Prompt was replaced with Powershell in the shift right click menu....You have to manually open the OG Command prompt from the start menu then manually navigate to the folder where ADB and Fastboot are located via command lines. Only because Powershell doesn't seem to like ADB or Fastboot.
[One (M9) Original Android Development] Flippy498:
Taken from the ReadMe thread:
[One (M9) Original Android Development] Ainz_Ooal_Gown:
Lucky after I updated to Nougat I turned on OEM unlock and I'm on ViperOne now :)
[One (M9) Original Android Development] Ainz_Ooal_Gown:
hmmm....it says to format sd card to something other then Fat 32 cause 4GB+ back ups would fail...but mine is formatted to vfat and fails so should ijust format it to exfat??
[One (M9) Original Android Development] FuXiN:
Twrp 3.1 is overheating in backup. Other versions did not have this problem

HTC One M9 cihazımdan Tapatalk kullanılarak gönderildi
[One (M9) Original Android Development] Ainz_Ooal_Gown:
Are you backing up the system.img? i haven't felt any overheating myself.....maybe it's because I'm using an Otter Box case .-.
[One (M9) Original Android Development] FuXiN:
Yes, I do. Temperatures up to 50 degreesView attachment 4120468

HTC One M9 cihazımdan Tapatalk kullanılarak gönderildi
[One (M9) Original Android Development] Boskoel03:
Same here....
[One (M9) Original Android Development] FuXiN:
I think there is a problem

HTC One M9 cihazımdan Tapatalk kullanılarak gönderildi
[One (M9) Original Android Development] Tirofog:
And here..
[One (M9) Original Android Development] Presto2601:
I put my phone in the fridge while backing up to keep temp down.
[One (M9) Original Android Development] FuXiN:
[emoji16] [emoji23] [emoji106]

HTC One M9 cihazımdan Tapatalk kullanılarak gönderildi
[One (M9) Original Android Development] bigjailerman:
I was able to screw up my wifes recorey on her HTC m9. tried to update 3.1 twrp over 2.7x using twrp. It didnt install paerly and now I cant log into recovery at all. I tried adb but keep running into issues.. cant load twrp etc etc

Id appreciate any assistance. Phone is s off, rooted still and boot properly. I tried to use Flashify but nothing downloads...

Thanks in advance
[One (M9) Original Android Development] idontkn1:
You should update your recovery with fastboot while in download mode. If you can't do it through fastboot tie probably best of doing an app backup with titanium and using the appropriate ruu and redoing everything.
[One (M9) Original Android Development] bigjailerman:
Thanks

Well I was able to install updated to 3.1 twrp, I installed the rr rom and am stuck in bootloop animation. Can get into recovery etc..

Haha it seems to never end. Thoughts?
[One (M9) Original Android Development] bigjailerman:
Also where are the ruu repository?

Thanks
[One (M9) Original Android Development] nkk71:
In the don't bother looking section, there's a don't bother reading thread, you may want to read after all.
[One (M9) Original Android Development] bigjailerman:
This is fantastic... Great info here. Many thanks on those one ??
[One (M9) Original Android Development] chikuji:
Will this twrp work on the m9+?
[One (M9) Original Android Development] Adromir:
I encountered a strange Bug in 3.1 , the size of my data partition was calculated as 240GB and TWRP even tried to back up around 62GB somehow. Log is attached, i removed the files that were added from log, because otherwise the log would have exceeded file size
[One (M9) Original Android Development] Flippy498:
No, the M9+ is a completely different device. Look in the M9+ forum for files you can flash on your phone.
[One (M9) Original Android Development] mikeataol:
Hi

I have installed 3.1.0 from twrp.me

I've tried using adb backup to pc, which appears to have gone fine with 2 backups....

However , trying "adb restore " does not work....

gives these errors:

E: Unable to find file system (first period).

E: Unknown restore method for '/system'

E: ADB Restore failed.

some threads point to this being fixed in some versions of TWRP 3.1.0

is there any chance for these backups?

Thanks
[One (M9) Original Android Development] jpwhre:
Try flashfire in play store.
[One (M9) Original Android Development] mikeataol:
Thanks for the reply...

at this point I've done a full wipe... I suppose I "could" reload to get a working OS and try it, but

I can wait and see if there is a fix to TWRP and flash recovery only to get the backup back.

none of it urgent BTW, I have a working phone and was just trying various things to see what's going to happen if VZW ever gets off their *ss and gets Nougat out for the M9
[One (M9) Original Android Development] Captain_Throwback:
Wait for TWRP 3.1.1.
[One (M9) Original Android Development] Golv:
Thanks! :good:

Updated TWRP 3.1.1-0

What's new in 3.1.0-0:

vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)

adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)

tweak MTP startup routines (mdmower)

support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)

support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)

better indicate to users that internal storage is not backed up (Dees_Troy)

improve automatic determination of TW_THEME (mdmower)

minimal getcap and setcap support (_that)

try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)

shut off backlight with power key (mdmower)

timeout during FDE decrypt (Dees_Troy and nkk71)

support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)

boot slot support (Dees_Troy)

TWRP app install prompt during reboot (Dees_Troy)

support for AB OTA zips (Dees_Troy)

support new Android 7.x log command (Dees_Troy)

update recovery sources to AOSP 7.1 (Dees_Troy)

numerous bugfixes and improvements by too many people to mention

Download: twrp-3.1.1-0-hima.img
[One (M9) Original Android Development] amiraras:
Hi,

First of all thank you for all of your contributions.

Second I have HTC One M9 that I'm trying to convert it from AT&T to developer and still be able to get updates over the air or OTAs, which post on XDA would I follow and what are the procedures I have to do?

Enthusiastically,

Amir.
[One (M9) Original Android Development] nkk71:
Not sure what this has to do with TWRP :eek:

But if it was me, I'd start by looking at the HTC One (M9) ReadMe Thread which is extremely well maintained by Flippy498 :good:
[One (M9) Original Android Development] amiraras:
Okay, thanks.
[One (M9) Original Android Development] One-ti-teuf:
Good evening everyone. I have a backup worry with the data. I just updated twrp, but it does not change anything. Do you have a solution for me? Thank you in advance. View attachment 4186275

Envoyé de mon HTC One M9 en utilisant Tapatalk
[One (M9) Original Android Development] nkk71:
1) Screenshot is not a recovery.log, next time please upload a recovery.log

2) I don't fully understand your question, so I'm going to assume you mean the text about "Internal Storage (pictures, etc)", that has always been the case, TWRP only backs up /data excluding /data/media (your virtual sdcard/Internal Storage). The added text is for informational purposes only, it has always been like that.
[One (M9) Original Android Development] One-ti-teuf:
Ok, so the data backup should work? Sorry my English is very average

Envoyé de mon HTC One M9 en utilisant Tapatalk
[One (M9) Original Android Development] nkk71:
The backup is fine, TWRP backs up /data:

that would mean downloaded applications + settings, and system settings

It will not backup your /sdcard

those would be things like pictures, music, etc. If you connect your phone to the PC, you will see:

View attachment 4187874

View attachment 4187875

^^ Those will

not

get backed up.
[One (M9) Original Android Development] fanfanus:
Hi,

Recovery mode with TWRP doesn't work. I have this message : "this build is for development purposes only do not distribute outside htc with out htc write permission failure to comply my lead to legal action ."

What can I do ?

Thanks
[One (M9) Original Android Development] jpwhre:
Nothing. Your bootloader is unlocked. That is why it says that.

What you are seeing is your splash screen like normal, but with a notice.

You didn't reboot to recovery, you just rebooted.

Hold power/volume up/volume down for ~10 seconds to open bootloader (white page tells you if system status is official, bootloader locked/unlocked, s-on/off)

It will give you option to reboot, reboot recovery, reboot download...... And such.

Select recovery reboot.

A: twrp

B: black screen with layout described for bootloader, no twrp
[One (M9) Original Android Development] fanfanus:
hTC download mode

*** UNLOCKED ***
htc_hiau_ml_tuhl PVT S-OFF
CID-HTC__621
MID-0PK711001
[...]

> system info
> show barcode
> reboot to bootoader
> reboot to download mode
> reboot
> power down
> check smart sd
> factory reset

If I chose "reboot to boot loader" :

>REBOOT TO BOOT-LOADER
>BOOT TO DOWLOAD MODE
>BOOT TO RECOVERY MODE
>DDR TEST
> POWER DOWN

If I chose " boot to recovery mode":

This build is for development purposes only do not distribute outside htc with out htc write permission failure to comply my lead to legal action .

And the screen is frozen.

So I have not the options you tell me. :(
[One (M9) Original Android Development] nkk71:
That's

not

an M9 (hima), it's an M9+ (as can me seen by the code name and MID) check here
[One (M9) Original Android Development] calikevin:
For some reason my TWRP backups aren't restoring properly.. During the System Image part of the restore process, the phone randomly reboots and sticks at the first reboot screen. I was able to restore the Data Image successfully so I know it's not that. Any ideas?
[One (M9) Original Android Development] nkk71:
What are you trying to restore, "System Image" or "System", in the latter case is your system partition mounted read/write? (TWRP->Mount-> the box at the lower left corner)

and you could run the following command (before starting the restore) on your PC:

adb shell tail -s 0 -f /tmp/recovery.log

This will continuously read the recovery log to your command prompt, so you can see what's going on.
[One (M9) Original Android Development] calikevin:
I'm trying to take a full backup and restore my LeeDrOiD ROM, but when it gets to the System part of the restore it reboots. Not System Image, my mistake.
[One (M9) Original Android Development] nkk71:
Is your system partition mounted r/w?

If so you can run the command above to see what's going on.
[One (M9) Original Android Development] calikevin:
Okay I did the log and I watched the restore until it crashed. It completes the System restore just fine, crashes and reboots during the System Image restore.

I:Restore filename is: /external_sd/TWRP/BACKUPS/serial/2017-07-24-LeeDrOiDMM/system_image.emmc.win
I:Restore file system is: 'emmc'.
I:Restore file system is: 'emmc'.
Restoring System Image...
I:Reading '/external_sd/TWRP/BACKUPS/serial/2017-07-24-LeeDrOiDMM/system_image.emmc.win', writing '/dev/block/mmcblk0p66'
Truncating string cache entries.

It ends there then reboots.

And as far as I can tell System is mounted as r/w... The box in the lower corner that you mentioned says "Select to mount system as read only" and is unchecked.
[One (M9) Original Android Development] nkk71:
So after all these posts, you:

1- Haven't answered whether you're system partition is mounted r/w or not

2- You are in fact restoring a System_Image (according to your 4 lines above), whereas you said you're restoring System not the Image

In regards to (2) are you restoring both?

EDIT: oh you did edit your answer to include (1).

Still are you restoring both System and System_Image? You shouldn't be doing that, it's either or, not both
[One (M9) Original Android Development] calikevin:
My mistake, initially I thought the rebooting was occurring during the System restore because it was usually the last thing I saw during the reboot, but the log showed me that the System restore completed just fine.

I just assumed that since both were checked by default I had to restore both System and System Image, that's where I was going wrong, thank you. What is the point of having both if you don't use both, is one more efficient or something? Sorry for the confusion but I've never ran into this problem before, maybe it doesn't usually take both backups.
[One (M9) Original Android Development] Captain_Throwback:
You could read the FAQ...
[One (M9) Original Android Development] calikevin:
I could, but it doesn't mention anything about the issue I'm having nor anything I'm dealing with. There seems to be a Q for what I'm asking but not an A.
[One (M9) Original Android Development] Captain_Throwback:
That's not what the FAQ says...you must be using XDA Labs. Open that post in a browser and read the actual answer...
[One (M9) Original Android Development] :
i directly flashed the latest version 3.1.1.0 twrp through flashify but the recovery did not work .

Do i have to flash any older twrp version before ???

.

Bootloader Unlocked .

S-OFF

HTC M9 (Hima)(AT&T)
[One (M9) Original Android Development] Flippy498:
Did you read the FAQ on the first page? You're not using the correct TWRP version for your firmware version.
[One (M9) Original Android Development] jpwhre:
If you have android info text for your carrier and device name you can make installer yourself.

I have Sprint and my device is 0PJAIMG.
[One (M9) Original Android Development] :
Lols , i am not so expert that i make an installer myself .

And yes i have that red coloured text on boot which says this build is for development purpose .

.

.

TWRP 2.8.7.0 Is Working Fine For Me :)
[One (M9) Original Android Development] jpwhre:
ONLY WORKS FOR S-OFF USERS

yes you do

find in settings of your device the firmware version, then look through the threads for your carrier and find the zip flash-able file of just your firmware and download it

extract the file and you will find 2 files inside (could be more depending on who made it) one will be the firmware package and the other will be android info text with info matching your firmware version.

i'm on sprint, and my info text shows

modelid: 0PJA20000
cidnum: SPCS_001
mainver: 4.27.651.4
btype:1
aareport:1
hbootpreupdate: 3
nohardreset: 1
resparseoption: -S800M
erasepartition: cache
eraseonflash: system
eraseonflash: userdata
eraseonflash: aboot
eraseonflash: adsp
eraseonflash: boot
eraseonflash: cpe
eraseonflash: hosd
eraseonflash: hyp
eraseonflash: radio
eraseonflash: recovery
eraseonflash: rpm
eraseonflash: pmic
eraseonflash: sbl1
eraseonflash: sdi
eraseonflash: tz
eraseonflash: rfg_1
eraseonflash: sp1
eraseonsoff: frp
eraseonflash: cota
erasepartition: ddr
eraseonsoff: carrier

make a new folder on your desktop and name it whatever you want, or dont and leave it as "new folder"

put the android info text file in it leaving it named

android-info.txt

and put twrp in that file and make sure it is named

recovery.img

then highlight both files by clicking and then dragging over both

you will need 7zip installed for this, but just right click and select compress with 7zip

you need to name the compressed file to

0PJAIMG

first character is a number (zero) not a letter

put that file in the root of your sd card and put device in download mode and press volume up

it will install for you
[One (M9) Original Android Development] mikeataol:
I'm guessing you mean create "New Folder"
[One (M9) Original Android Development] jpwhre:
My bad, yes, and thank you. Making change
[One (M9) Original Android Development] :
I did not know it is that easy to learn . But i have now upgraded to marshmallow , so the latest version works for me now . I forgot reading FAQs at first :D
[One (M9) Original Android Development] green-gf:
deleted
[One (M9) Original Android Development] Captain_Throwback:
<ignoring this post as the poster obviously didn't read the OP>
[One (M9) Original Android Development] Einheit-101:
...Whats up with the download link. TWRP site is 404.

€DIT:: Someone should Update OP....

Its

https://twrp.me/htc/htconem9.html

"https://twrp.me/devices/htconem9.html" is wrong
[One (M9) Original Android Development] Kisakuku:
TWRP 3.2.0.0

Download

Changelog
[One (M9) Original Android Development] BiOMeX:
TWRP 3.2.0.0 contains some bug: if /system is read-only - backup restoring process may hang on progress bar screen until full battery drain. There is no warning about it (partition /system state) as was done in version 3.1.1.0.
[One (M9) Original Android Development] bigbiff:
Hi, can you post the recovery.log for this issue so I can trace the code?
[One (M9) Original Android Development] BiOMeX:
Нере уоu go. Hope it helps.
[One (M9) Original Android Development] bigbiff:
Unfortunately that looks like the default recovery.log with no operations performed.
[One (M9) Original Android Development] BiOMeX:
Everything stops at this point (see attachment) with running progress bar until full battery drain. Pressing VolUp + Power is the only way to switch off the phone.

OS 3.35.401.32
[One (M9) Original Android Development] nkk71:
Screenshot is not the same as a recovery.log, so while it's *sitting* there, connect it to your PC and get the logs:

adb pull /tmp/recovery.log
adb pull /tmp/adb.log

and finally reboot to recovery:

adb reboot recovery

or just reboot:

adb reboot

I'm actually restoring a system_image backup as I type this, and it's restoring fine.

Can you check the filesize of your backup, how big is it?
[One (M9) Original Android Development] BiOMeX:
Why should i do the logs again? So, okay, here they are.

Filesize of backup is 7.48Gb (data (excl. storage)/system/boot)