yashsingh1/xdaforums huggingface dataset:
[One (M9) Original Android Development] casey00:
C:\>fastboot flash unlocktoken C:\Unlock_code.bin

target reported max download size of 800000000 bytes

sending 'unlocktoken' (0 KB)...

OKAY [ 0.018s]

writing 'unlocktoken'...

(bootloader) flash unlocktoken

(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp

(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock

FAILED (remote: UnlockToken Verify Fail!!)

finished. total time: 0.109s

this also happens

---------- Post added at 08:11 PM ---------- Previous post was at 08:07 PM ----------

still

C:\>fastboot flash unlocktoken C:\Unlock_code.bin

target reported max download size of 800000000 bytes

sending 'unlocktoken' (0 KB)...

OKAY [ 0.018s]

writing 'unlocktoken'...

(bootloader) flash unlocktoken

(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp

(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock

FAILED (remote: UnlockToken Verify Fail!!)

finished. total time: 0.109s

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

i do have the unlock bin file from htc but no unlock am i forgetting a step
[One (M9) Original Android Development] Boostjunky:
Have you checked the option in developer settings to allow OEM unlocking?
[One (M9) Original Android Development] casey00:
Yes it's checked and still no luck

---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------

Is it because of the latest HTC update

Because if I can't root the dam thing I'm just gonna return the ****ty phone and get a basic phone because the battery life fing sucks ........my m8 I gave my dad works fine and I was able to root and unlock it but why not this phone it beats the hell out of me.
[One (M9) Original Android Development] nkk71:
very off topic, but anyway, now that you have OEM unlocking enabled, get a new token from HTCdev, and flash it. (^^ green is good, red is not good)
[One (M9) Original Android Development] irocevo:
I'm getting an error when trying to make a backup of CM12.1 I compiled. I have recovery TWRP 2.8.7.1_CPTB-B1 installed

Backing up System...

E: Error Opening '/system/addon.d' - error: Not a directory

E: Error in Generate_TarList!

I:InfoManager saving '/data/media/0/TWRP/BACKUPS/HTxxxxxxx/2015-10-3-cm_himawhl_userdebug_5.1.1_LVY48F_5afdeff79/system.info'

E:createTarFork() process ended with ERROR=255

Backup Failed

Help please :)
[One (M9) Original Android Development] Captain_Throwback:
That's not a full log.
[One (M9) Original Android Development] Captain_Throwback:
Not sure what that error is about. I know only AOSP ROMs have that folder, but I'm not sure why it would be making the backup fail. Only thing I can suggest is to try repairing the system partition. If that doesn't work then I have no idea. Maybe someone else that's running CM can see if they have the same issue. If so, it can be added as an issue on the TeamWin github. Otherwise, there's something specific to your setup that's causing an issue.
[One (M9) Original Android Development] irocevo:
Thank you for looking into this. I read somewhere that I could try flashing back to sense rom and doing a factory reset and wiping out all data. I made a CM backup yesterday no problem but deleted :(

Update: I wiped dalvik cache, cache, system, data, and internal storage. Flashed my updated CM12.1 build and just did a backup and it works again :)
[One (M9) Original Android Development] Krsmqn:
Hello, TWRP reboots when I try to install a zip. I know the zip is less then 2 gb because it's just an apk. When I swipe to flash, the text starts to move and then within a half second, my phone reboots. I have looked everywhere for a solution. I've tried going back to stock everything. I've unchecked zip verification. At a loss here. Everything else seems to work fine. I can backup and restore fine.
[One (M9) Original Android Development] teddy0209:
If its just an apk, can't you install it normally? What exactly are you trying to flash?
[One (M9) Original Android Development] Krsmqn:
I tried to extract the apk and install it but it didn't work. I'm installing Team Blackout apps. Some can be installed just as an apk, and others have to be flashed. Idk why. Thank you for the reply though. I really appreciate any help. :D
[One (M9) Original Android Development] teddy0209:
Oh... Sorry, I don't use that... Maybe the updater script needs to be updated...
[One (M9) Original Android Development] Captain_Throwback:
That usually happens when you have a bad zip. Better re-download it.
[One (M9) Original Android Development] Krsmqn:
Yes I tried that. Thanks for the reply.:)
[One (M9) Original Android Development] efrant:
[MENTION=1162986]Captain_Throwback[/MENTION] Slightly OT, but have you or anyone else figured out if there is a byte we can flip within aboot or whichever partition to allow the "fastboot boot" command to work.
[One (M9) Original Android Development] Captain_Throwback:
Nope. Not currently possible. [MENTION=2376614]jcase[/MENTION] can confirm though, as I'm sure he knows all about this.
[One (M9) Original Android Development] jcase:
i cant say for sure, but based on their new setup i would say unlikely
[One (M9) Original Android Development] nkk71:
can't say either, but doesnt work for me,

on M7 used to work on firmware 1.xx.xxx.x (includes hboot 1.44), after that it got "borked", i remember someone analysing it, and found something about memcpy was wrong in hboot 1.54 and above

(intentional or not, I can't say, don't even have a link to it)

on M8 works fine, as far as I know

on M9, it never worked
[One (M9) Original Android Development] p3ric0:
Has anyone figured out how to create a usable ext4 partition on the external SD after flashing TWRP as detailed in this thread? When I go to partition my SD, TWRP will spit out this error "E:Unable to locate device to partition"

I can see the contents of my SD just fine through the file explorer and I experience no read/write issues on it while using the phone itself. I did have to edit the platfrom.xml to allow TitaniumBackup write access to the SD, but that was simple enough. I'd like to be able to move entire apps to the SD card but for now seem to be stuck until I can correctly partition it.

Any help is appreciated! :)
[One (M9) Original Android Development] chukis13:
I flashed twrp 2.8.7.0 and when I try to get to recovery I just get a black screen with a picture of a phone with a red triangle with a ! in the middle. Underneath it says "Update in progress. Don't turn off your phone." Then it reboots. So I try to go back to recovery again and get the same thing. Any ideas?
[One (M9) Original Android Development] jollywhitefoot:
Sounds like you didn't flash twrp. That's stock recovery. Post your terminal output so we can see what you're doing wrong.
[One (M9) Original Android Development] chukis13:
Okay, this is embarrassing, it was just a noob mistake. Battery low so it finish properly. For some reason I thought it did because they phone shows complete but terminal shows failed. Sorry lol
[One (M9) Original Android Development] jdjohn:
It seems that the backup size with this version are much bigger than I remember with my M7. I had Lollipop running on that phone, but I think the TWRP backups were less than 2GB. With this version on my new M9, my first backup from rooted stock was over 7GB. Does that seem right?
[One (M9) Original Android Development] Adromir:
I have two Issues with this recovery ( i am on 2.8.7.1_CPTB-B1)

1. Decryptrion of a encrypted partition doesnt work

2. if i try to format cache or data in f2fs causes TWRP to bootloop

any chance of that getting fixed?
[One (M9) Original Android Development] Captain_Throwback:
1. Read the OP.

2. Read the OP.
[One (M9) Original Android Development] Adromir:
Right Sorry.

and sorry for not mentioning, i am running an CM 12.1 based rom on it (AICP). I will provide a TWRP log later
[One (M9) Original Android Development] Captain_Throwback:
TWRP for M9 doesn't include any files to decrypt hardware keymaster, so it's no surprise that decryption doesn't work. The only way it'll ever work is if someone (not me) figures out what files are necessary for decryption, and submits those changes to the TWRP gerrit.

Otherwise you're stuck either not using encryption, or not being able to decrypt in TWRP.
[One (M9) Original Android Development] Adromir:
Ah okay thanks. No problem then, thanks for your time
[One (M9) Original Android Development] Ryche666:
If you are running 12.1 aicp from my downloads. It has early printk enabled so you can do a log to find out why f2fs borks twrp. I asked the same thing and got the same reply. I just haven't figured out how to do a log...... To busy working on o3, strict, hotplugs, and governors to get better test scores and better life than my wifes m8
[One (M9) Original Android Development] LLegion:
hi guys! is there is any more updated version than "Current Beta Version: 2.8.7.1_CPTB-B1" like 2.8.7.2 or something? [MENTION=1162986]Captain_Throwback[/MENTION] thanks in advanced for the answer =D
[One (M9) Original Android Development] Captain_Throwback:
It's the "current" version. That means it's the latest.
[One (M9) Original Android Development] LLegion:
iknew it, but anyways wanted to be 100% sure, i do apologize for the inconvinience, have a nice weekend! =D
[One (M9) Original Android Development] Sierra35:
Hi everyone,

is there any chance that twrp for this device will be updated for Marshmallow? (sorry, if that is a noob, dumb, or even silly question)
[One (M9) Original Android Development] liam_davenport:
Works just fine with MM
[One (M9) Original Android Development] kokinator02:
Current version works just fine, Beta Supersu 2.52 doesn't though. It soft bricked my phone. Fortunately it was able to still go into download mode and into RUU mode letting me flash an RUU back.

Cheers

Nexus 9
[One (M9) Original Android Development] Gandalforce:
Try any BETA SuperSU
[One (M9) Original Android Development] JourNo:
I'm in 2.8.7.0 version, i can't wipe data or cache... It announces " E:\.... can't mount". Anyone help me,please!
[One (M9) Original Android Development] gregsarg:
Use the beta....

It's the only working version...

Instructions are found not only in post 1....but in 2-3 also...

Read carefully....g

http://xdaforums.com/devdb/project/dl/?id=13383
[One (M9) Original Android Development] JourNo:
Thanks guy!
[One (M9) Original Android Development] migascalp:
Hello,

Small question about the version 2.8.7.1_CPTB-B1.

there is a particular reason to format the SD-Ext partition during a Factory Reset?
[One (M9) Original Android Development] donmarkoni:
Yes. SD-Ext is not ext_SD. SD-Ext is secondary data partition used to extend application storage on low storage devices. There's no use for it on M9.
[One (M9) Original Android Development] Captain_Throwback:
Except for MultiROM . . . there's always a use for everything ;).
[One (M9) Original Android Development] migascalp:
Exactly. :)

Possible to have an answer to my question?
[One (M9) Original Android Development] Captain_Throwback:
In the case that [MENTION=2977387]donmarkoni[/MENTION] specified, which is the original purpose of SD-Ext, it makes sense, since this is was essentially wiping ROM data, which was an extension of /data.
[One (M9) Original Android Development] migascalp:
For my personal work I switch between classic version and MultiROM.

With the normal version at a Factory reset I lose Roms on the partition SD-Ext.

I want to disable the wipe of SD-Ext on classic version.

recovery.fstab:

/sd-ext	ext4	/dev/block/mmcblk1p2	flags=display="SD-Ext";removable

So I wanted to know if this could cause problems.
[One (M9) Original Android Development] Captain_Throwback:
Just change "/sd-ext" to "/sd_ext" and that'll take care of it.

Why didn't you just ask that in the first place?
[One (M9) Original Android Development] migascalp:
My English is very bad. So I go to the shortest.

it's not happening all the time. sorry
[One (M9) Original Android Development] Locklear308:
Does anyone know why flashing anything crashes twrp and reboots the phone?
[One (M9) Original Android Development] miggsr:
You may have corrupt partitions. I had similar situation with my m8 I ran ruu and flashed twrp to fix my issue. Repartitioning thru recovery didn't help me.
[One (M9) Original Android Development] Locklear308:
Thanks for the reply, now pardon my ignorance... I've not had an HTC device for many years... lol. I thought RUU stuff was only useable with S-Off? Which I don't have yet because I can't root, because I cannot flash lol.
[One (M9) Original Android Development] miggsr:
Having s-off only allows you to flash modified firmware zips or splash screens and a few other things. In your situation... meaning you are s-on this means you need to lock your bootloader to run ruu. You don't need s-off to be able to root an HTC device.
[One (M9) Original Android Development] jollywhitefoot:
Ruu works when s-on, but is region/carrier/cid specific. So, if there's an ruu for your particular situation, then you're good to go.

---------- Post added at 02:27 PM ---------- Previous post was at 02:26 PM ----------

Could be a bad download, too. I've had this happen.
[One (M9) Original Android Development] miggsr:
That is also correct about a possible bad download.
[One (M9) Original Android Development] Locklear308:
Can't ne that, I redownloaded everything and reflashed TWRP 3 times. I tried an older build and the latest beta. :0 , I will research this RUU and see if that can nix my issue.
[One (M9) Original Android Development] Captain_Throwback:
Not TWRP - whatever zip you were trying to flash. It is possible to have multiple bad downloads, btw.
[One (M9) Original Android Development] Locklear308:
3 different versions of Supersu. I am open to any ideas though... lol. It starts fine, but like 3/4's of the way through the phone just reboots to normal mode.
[One (M9) Original Android Development] Captain_Throwback:
Easiest way to know if you have a good zip (in the case of a signed zip like SuperSU) is to enable zip signature verification. If the zip is good, it'll flash - otherwise it'll immediately fail. Try that and let us know what happens. That'll confirm for sure whether the zip is good or not.
[One (M9) Original Android Development] Locklear308:
Ok, I did that. And...when it gets to "restoring files" it instantly reboots. I don't get enough time to really see everything O.O

I don't think it is failing.. I mean I've used TWRP for years and I've never had it crash.

Is there perhaps a special old build for android 5.0 on the m9?
[One (M9) Original Android Development] Captain_Throwback:
Can you pull the recovery log from /cache/recovery/last_log?
[One (M9) Original Android Development] Locklear308:
There are no logs/files in there. Just to be sure, the location would be , Root - /cahce/recovery correct? If that is right, then yes there are no files. I honestly wonder if I should swap this out for another one or not... X.X

I feel like a derp, I've rooted dozens of phones without issues (other than the first 2 learning experiences lol) and suddenly it's like I don't know what I'm doing.

Thanks for helping so far though!
[One (M9) Original Android Development] Captain_Throwback:
I think the RUU is a good idea. Start fresh.
[One (M9) Original Android Development] Locklear308:
RUU it is then, I presume that should make make it super factory clean haha. Thanks for your help man.
[One (M9) Original Android Development] hallstevenson:
Can you still update TWRP by using TWRP itself ? I know you can toggle between *.zip and *.img files for flashing. Just want to make sure and not do some serious "damage" to the file system.
[One (M9) Original Android Development] Locklear308:
I was under the impression that it was never a good idea to do so that way.
[One (M9) Original Android Development] Captain_Throwback:
If it wasn't a "good idea" then it wouldn't be an option.
[One (M9) Original Android Development] pittvandewitt:
Hello,

I'm having a hard time flashing a functional stock recovery for 2.10.401.1 (european version)

I have found and flashed some, but my firmware stays modified. My unmodified system image is succesfully restored.

I have my ota.zip, but i cannot extract the firmware.zip in it which should contain a usable recovery.

Right now I am unable to take an ota. Can someone point me in the right direction?
[One (M9) Original Android Development] Captain_Throwback:
Are you using 7-Zip to extract the firmware?
[One (M9) Original Android Development] pittvandewitt:
yes I am

Edit: I have uploaded the Ota.zip. I wasn't lucky extracting the recovery_signed.img. Maybe you are?

https://www.dropbox.com/s/93kbd165j...10.401.180-2.10.401.1_release_464143.zip?dl=0
[One (M9) Original Android Development] Captain_Throwback:
Not sure why you're having an issue, then - I've never had issues extracting firmware from an OTA zip. Maybe you can upload it for someone to try extracting for you?

However - you should do that in your own thread, as it's really not related to TWRP.
[One (M9) Original Android Development] Captain_Throwback:
Not in this thread . . .

EDIT: It only took a few seconds to extract, so here's a link. Not sure why you had so much trouble with it. You might need to update your 7-Zip. Are you using the latest version? Next time please create your own thread for this or post in a relevant one. This is the TWRP thread, not the flash stock recovery for an OTA thread ;).
[One (M9) Original Android Development] Locklear308:
Well like dirty flashing is considered not the best idea, but it's an option haha. That's just what I had heard so perhaps it's all been improved since then :)
[One (M9) Original Android Development] pittvandewitt:
Thank you a lot. I'm still having a headache because on my phone i can't extract it either. But you are right, I was going off topic. Excuse me for that.
[One (M9) Original Android Development] Mutasek24:
[MENTION=1162986]Captain_Throwback[/MENTION]

whether it is possible to create a system image (unmodified) before taking root at 6.0 (unbranded) using 2.8.7.1? thanks

EDIT:

after the backup (system image) gets so here's the message:

View attachment 3624378

my log:

http://pastebin.com/eg7TbcTu
[One (M9) Original Android Development] PrizmaticSmoke:
The log shows the file was too large:

[dd: writing '/external_sd/TWRP/BACKUPS/FA53AYJ07782/2016-01-27--08-09-53_MRA58K_release-keys//system_image.emmc.win': File too large]

Is your SD card in FAT32 format? If so you are limited to 4GB when writing a file. Try backing up to internal memory, or use a different SD card (or reformat that one if you are so inclined).
[One (M9) Original Android Development] Mutasek24:
Thanks mate :) completely forgot about that my card is formatted to FAT32

EDIT:

backup (system Image) in the internal memory passed without a problem
[One (M9) Original Android Development] Captain_Throwback:
The good news is, I believe the updated aboot in Marshmallow for the M9 supports reading exFAT-formatted cards, so a FAT32-formatted card (and the limitations that come with it) should no longer be a requirement.
[One (M9) Original Android Development] mick_soul:
Yes, it does :D Thanks for mentioning.

I was wondering why I suddenly got the message 0PJAIMG.zip not found every time I entered Download Mode with MM Firmware.

I saw that message once on Lollipop with an Fat32 sdcard for flashing the 0PJAIMG.zip
[One (M9) Original Android Development] Captain_Throwback:
It's also *possible* that fastboot boot has been enabled while in bootloader mode. Someone will have to test that theory, though.
[One (M9) Original Android Development] efrant:
Confirmed. The "fastboot boot" command is re-enabled in bootloader mode, at least on my firmware (3.38.631.2).
[One (M9) Original Android Development] Captain_Throwback:
And that makes it possible to backup stock recovery without flashing TWRP - that should make it much easier to get the backups people so desperately desire :).
[One (M9) Original Android Development] donmarkoni:
Yeah, working on all 3.xx.401.xx(x) FWs so far.
[One (M9) Original Android Development] Captain_Throwback:
FAQ updated with the good news about fastboot boot. So now all options are at your disposal, with the ability to use exFAT-formatted cards and fastboot boot TWRP.

Combined with systemless root, you might not even need to make a backup at all ;)
[One (M9) Original Android Development] Captain_Throwback:
[MENTION=506238]OMJ[/MENTION]

I don't have a lot of time, but new on the Downloads Tab is a TWRP I just built (we'll call it 2.9.0.0) from the latest source. Consider it a preview of the new version soon to be released.
[One (M9) Original Android Development] OMJ:
Thx bro!
[One (M9) Original Android Development] hallstevenson:
Thanks for not building in "bad" things ;)

---------- Post added at 10:05 PM ---------- Previous post was at 10:01 PM ----------

I'm not an expert by any shot but have been rooting my phones since 2010 (HTC Eris) and have never considered dirty flashing to be a problem. Well, there's certainly no danger in doing. Flashing recovery images has the potential to be bad, on the other hand.
[One (M9) Original Android Development] blocka:
Hi all

I'm having issues doing a TWRP backup using twrp-2.8.7.1_CPTB-B1-hima.img. I'm getting ERROR=255 when backing up system. I've rooted my system, running Marshmallow HTC One M9.

I really want to take a NAND backup before I install Xposed.
[One (M9) Original Android Development] xlx890121:
Can't boot TWRP 2.9.0.0 preview ? The screen still show a black screen.

I'm on Android 5.1 with 2.11 firmware. TWRP 2.8.7.1 is OK.
[One (M9) Original Android Development] blocka:
Same
[One (M9) Original Android Development] donmarkoni:
I was thinking it could be due to old FW, but I'm on new FW and same thing happens to me. [MENTION=1162986]Captain_Throwback[/MENTION], if you need some debugging assistance, I'm around.
[One (M9) Original Android Development] migascalp:
this seems to be a display issue.

because automatic screen off and adb (adb reboot) work.

last_log
[One (M9) Original Android Development] computerslayer:
That's unexpected and very welcome news. Thank you.
[One (M9) Original Android Development] Warcliffe:
Same problem here but i have the last firmware 3.35 !
[One (M9) Original Android Development] Captain_Throwback:
Sorry guys, I have to rebuild. Left some old build flags in there that are messing things up. I'll try and get to it today.
[One (M9) Original Android Development] fajo:
Hello, Thanks very much :D

Sent from HTC One M9
[One (M9) Original Android Development] 2WildFirE:
Thanks we wait for the new build. Take your time Captain

Powered by SkyDragon ROM
[One (M9) Original Android Development] Captain_Throwback:
Try 2.9.0.1
[One (M9) Original Android Development] blocka:
Thanks this one boot/loads. When I try to do a backup I'm still getting the error createtarfork() process ended with with ERROR: 255 when backing up System.

From the recovery_log

Backing up System...

Error opening: '/system/app/AntHalService/oat' (Not a directory)

I:Error in Generate_TarList!

Error creating backup.

I:InfoManager saving '/data/media/0/TWRP/BACKUPS/FA54CYJ11099/2016-01-30--15-23-17_MRA58K_release-keys/system.info'

createTarFork() process ended with ERROR: 255

Backup Failed. Cleaning Backup Folder.
[One (M9) Original Android Development] Captain_Throwback:
What do you mean, "still"?

Do you have enough space on your device for a full backup?

Always provide the FULL log, please.
[One (M9) Original Android Development] blocka:
Yeah I've been getting the ERROR: 255 on versions. Log attached.

twrp-2.9.0.1-hima.img

twrp-2.8.7.1_CPTB-B1-hima.img

twrp-2.8.7.0-hima.img
[One (M9) Original Android Development] Captain_Throwback:
Anyone else with this problem?
[One (M9) Original Android Development] 2WildFirE:
i had this problem in the past, imho rom problem.

here was my problem with err 255 http://xdaforums.com/showpost.php?p=61465976&postcount=474
[One (M9) Original Android Development] Aldo101t:
I just did a back up of my current rom(viperone) and it seemed to backup ok, no errors.

that was to internal, i'll try one to sd card and see what happens

Progress bar doesn't fill as it progresses, it flashes across, but no fill

Backed up to Ext_sd OK too