yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] Captain_Throwback:
Make sure you provide a log.
[One (M8) Original Android Development] hector2001:
I have flashed this recovery into HTC One M8s (android v5.0.2) using :

fastboot flash boot <recovery_file.img>

instead of : fastboot flash recovery <recovery_file.img>

Now my phone won't start.

Can somebody help ? :(

Thank you..
[One (M8) Original Android Development] amirfida:
Perhaps try go ruu method and restore your phone from there, will it go in ruu mode?
[One (M8) Original Android Development] alex2693836:
Anyone have recoveries themes for 2.8.6.0 ?
[One (M8) Original Android Development] GrandAdmiral:
I am having trouble installing the latest TWRP on my device. I have tried both using TWRP Manager and flashing and I can't get to 2.8.6.0. I've even attempted to downgrade, but remain stuck at 2.8.5.0. Any idea what could be blocking me from making the upgrade?

I'm rooted with an unlocked bootloader and s-off on the stock AT&T ROM.
[One (M8) Original Android Development] mrrocketdog:
thanks to [MENTION=4987085]xunholyx[/MENTION] guinea pigging i was able to install by renaming it to 0P6BIMG and running it in hboot just like an RUU.:good:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[One (M8) Original Android Development] ckvisme:
I follow that ruu thread as well, and i tried it out after you guys did, worked perfect. Thanks for sharing a great idea ?
[One (M8) Original Android Development] ancola66:
I used TWRP 2.8.6.0 and have problem :

I can't restore from backup (backup from InsertCoin 7.1.4) >>> restore system ok but can't restore data >>> get error :( I try to continue reboot >>> Reboot Ok but can't load htc sense home :(

My Devices 16Gb Storage version and 16Gb Extsdcard put in

My rom it's : InsertCoin 7.1.4
[One (M8) Original Android Development] Petert87:
I think you tried flashing boot.img again? And will this recovery works on M8s?
[One (M8) Original Android Development] TangerineTractor:
No, this doesn't work on the new M8s, as I have found to my cost! Unlocked bootloader, tried to flash, now have no recovery! Serves me right for not at least backing up stock recovery first! So I can't even do a factory reset, Good job the phone's rock solid and fast as it is.

We need an M8s recovery so that we can flash SuperSU for root!
[One (M8) Original Android Development] chobungus:
Converting to F2FS

I think I must be doing something wrong, but there is no option to convert my filesystem to F2FS. I'm on TWRP version 2.8.6.0. I've followed the steps by going to TWRP > wipe > advanced wipe > select cache > repair or change filesystem > change file system. I should be able to select F2FS here but the only options are EXT2, EXT3, EXT4, FAT, and exFAT. There is no F2FS. What am I doing wrong?
[One (M8) Original Android Development] Captain_Throwback:
The next official version will support f2fs.

The next official version will support this as well.
[One (M8) Original Android Development] ckvisme:
Have you done a MultiRom version of this?

If not, then no worries I am just curious.

BTW, good to see you in the forums ?
[One (M8) Original Android Development] itsallwright:
I have tested out the decryption and it is working as expected now. Thank you very much for taking the time to build in support for this.
[One (M8) Original Android Development] Captain_Throwback:
FYI - There is an update to the official TWRP (2.8.6.1) which includes the aforementioned updates. There is now no need to use my custom version.
[One (M8) Original Android Development] thelangosta:
Your custom version is probably better looking than stock TWRP. ;)
[One (M8) Original Android Development] donibrasco:
Where could find that version?
[One (M8) Original Android Development] thelangosta:
Here you go.

https://basketbuild.com/devs/Captain_Throwback/One (M8)/ALL/Recovery
[One (M8) Original Android Development] ckvisme:
When you renamed & flashed twrp through hboot (0P6BIMG.zip) ...did you just rename the image file or did you actually zip it...

I thought you had to zip the recovery img file with an android-info.txt file... Then name the zip *0P6BIMG.zip* ...?

I attached some pics of what I mean..
[One (M8) Original Android Development] mrrocketdog:
not the twrp.img , i used twrp.zip so ; was already zipped. but yes , i would imagine you'd have to 'zip' the .img file before renaming.

"all i can really do , is stay out of my own way and let the will of heaven be done"
[One (M8) Original Android Development] NiXiNiX:
How come deleting stuff in recovery via file manager takes almost 2 minutes on 2.8.6.2?

I.e. my old nandroid backup.

It took less than a second on 2.8.4.0...:confused:
[One (M8) Original Android Development] smeejaytee:
Where use 2.8.6.2 please and has captain_throwback made a version thanks in advance.

Sent from my HTC One M8
[One (M8) Original Android Development] Forsaked:
Take a look here!
[One (M8) Original Android Development] mrrocketdog:
does anyone have twrp2860 in a zip that they could share please ? computerless at the moment. thank you.

"all i can really do , is stay out of my own way and let the will of heaven be done"
[One (M8) Original Android Development] geek wana-b:
Have you tried the flashing app?
[One (M8) Original Android Development] mrrocketdog:
tried flashify and it deleted my twrp 2850. so .... now am without recovery , but can flash thru hboot by renaming to 0P6BIMG.zip.

"all i can really do , is stay out of my own way and let the will of heaven be done"
[One (M8) Original Android Development] bacon612:
https://www.dropbox.com/s/pc33atsdkwx7nah/twrp-2.8.6.0-m8.img?dl=0
[One (M8) Original Android Development] ckvisme:
I have one of [MENTION=1162986]Captain_Throwback[/MENTION]s multirom TWRP that I zipped with an android-info.txt file (HBoot flash able).. Also have captains 2.8.6.2 standard TWRP.img ...but not where I can get to PC to zip this last one.

MR.TWRP.2.8.6.-2015-20-5
[One (M8) Original Android Development] mrrocketdog:
thank you both [MENTION=4429707]bacon612[/MENTION] & [MENTION=6402880]ckvisme[/MENTION].:good:

EDIT : 0P6BIMG worked perfectly. back to flashing!:thumbup::cool:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[One (M8) Original Android Development] jkolner:
Just updated to TWRP 2.8.6.1 but when i enter Recovery the action slider bar at the bottom can't be activated cos it's placed way to the left.

Tried TWRP 2.8.6.0 but same problem.

Went back to my previous TWRP but still couldn't activate the slider bar.

I have tried many thems but same problem with all of them.

Deleted the ui.zip in the TWRP folder and with the stock them the slider bare was placed correct.

Anybody has a TWRP theme that works og know what to do?

- - - - E D I T - - - -

Found this theme that works and looks fine.
[One (M8) Original Android Development] _purple_:
I had 2.8.5.0 installed and wipe cache didn't work. I flashed 2.8.6.1 and it still doesn't work. The recovery reports that cache partition has been formatted successfully but when I reboot, all apps' cache is still there. My device is HTC One M8 on stock 5.0.1

Any ideas? I couldn't find this as a reported or confirmed bug.
[One (M8) Original Android Development] bigd4ve:
Data Fails To Restore

I can't restore any of my backups. The one I want to restore won't complete the data restore but can restore system and boot fine.

I've tried with MD5 unchecked and with newer versions of TWRP (2.8.6.1 and 2.8.6.2) with the same result. Is the problem that compressed backups will not restore? Can't say I've had the issue before but don't have to restore backups too often. Tried a mod I don't like and now can't go back.

My current solution is to try and restore data via Titanium Backup or Nandroid Manager or just do a clean install but I would prefer to save the hassle?

Edit: Rolled back to 2.8.5.0 and the restore went perfectly?
[One (M8) Original Android Development] Pete2506:
Same issue here, but the problem starts with 2.8.5.0, thought about the compression, but problem exists on uncompressed backups, too. Always error 255.

Regards Pete
[One (M8) Original Android Development] bigd4ve:
Yes I had the same error but could not see the error message until I removed my theme. I would suggest to remove any theme if you have one, try with MD5 unchecked and then try on different versions of TWRP. Maybe you will have some luck on another version like I did.

If no joy upload your log to here or the Q&A section or use the live support link in the OP. Guys there were very helpful. Looks like my data was failing restoring a facebook file but managed to restore in the end. They will probably ask for a log though if you want advice. Good luck!
[One (M8) Original Android Development] dragontology:
Getting a lot of this after installing 5.1 ROMs; TWRP 2.8.6.0, Verizon HTC One M8: http://i.imgur.com/CRiJdKY.png

The install actually went through, but I've run into this twice now, and while, in my experience, I'm fine in the ROM I'm running (happens to be an AOSP-based ROM called BlissPop), if I try to flash anything else, I get more of these errors and things go badly, and I wind up unable to boot. My solution then is to RUU back to stock, and then I can re-flash TWRP and then go from there. Sense 6 ROMs seem to be safe, it looks like just 5.1 anything at this point.

Asked in IRC first, only an M7 guy in there at the time and he didn't know, but it sounds like someone, somewhere, is encrypting data. I don't believe it actually is, I think TWRP just thinks it is. I can encrypt data in Settings → Security of course, but it says I need to have a full charge and be plugged into a charger. So, it's saying I haven't yet.

Lastly, I had TWRP take a log, but I can't find where it's actually saved. It isn't in the TWRP folders. One on main storage, one on the SD card. The main storage one is empty while the other has my Nandroid backup.
[One (M8) Original Android Development] ckvisme:
I had the same problem.. As well as another guy from DH GPE thread....

*after lots of trouble shooting failure for me.. I just did a standard wipe..(duh.. Facepalm).. Flashed a rom, then it was all good again, I was even able to format internal and ext_sd cards from twrp.
[One (M8) Original Android Development] dragontology:
I might be the other guy from DH's GPE thread, as I posted about it there... unless you're thinking of someone else.

Standard swipe wipe, aka factory reset, formats data and cache. Didn't work for me, just got a bunch of red text and it wouldn't boot. Can't flash anything either, and even the part that writes to system isn't enough to boot to system (Android). I just get dropped into the boot animation forever.

It's funny, because I don't have trouble now. Well, I can't open books in Google Books. Same story in DH's GPE. I suspect the books are stored in \data, maybe. So other problems will probably rear their ugly heads later. Anyway, if I try to flash a ROM, any ROM, I'm gonna soft brick my phone. I know this because I'm exactly where I was Saturday night last weekend, before I tried to restore my Nandroid backup. I'm better prepared now. I'm in the ROM, so I can open my file manager, rename the ROM.zip on my SD card to 0P6BIMG.zip, reboot to bootloader, bada bing bada boom, RUU back to stock rooted, then fastboot flash TWRP and restore. Put like that it's not a huge deal, just extra steps and about 5-10 extra minutes.

I'm almost sure it's a TWRP issue. Not hating. I've just seen my share of red text in TWRP, and it's almost always caused by TWRP not being new enough to handle the ROM, and everyone says to flash the newest one and the problem will go away. Problem is, I'm on the new version, and the new version works for most people. But I know these people are brilliant and it'll get sorted eventually. Especially when 5.1 drops officially and instead of a few of us having the problem, it's a few dozen, including the holdouts who were waiting for an official version. And they'll be like, oh ——, that's what those guys were talking about... hopefully it gets sorted before then. This is what we get for flashing on the bleeding edge. It's called that for a reason. ;)

Edit: Well I took the leap and soft bricked my phone, and RUU'd back to stock, then factory reset in hboot, then RUU'd again because I really hate myself and love looking at loading screens... but really, I skipped the hboot factory reset and the RUU because hey, Sense worked... though the process said if data gets hosed to go ahead and do that. I'm not 100% sure they're related but, you know, measure twice cut once and all that.

And I did it on video. YouTube's got my real name, it's probably too much work to fix, and I don't really care if y'all know my name anyway, so, grab some popcorn, and I apologize in advance for not having a better camera. https://www.youtube.com/watch?v=zh3Xgo2uYxY
[One (M8) Original Android Development] sweetnsour:
I ran into this issue after flashing TWRP on my device (converted to GPE). Trying to boot into the system takes me back into recovery and I could not mount data in recovery, so I went ahead and wiped everything I could in the wipe menu (dalvik cache, cache, system, data, internal storage) as I wasn't in the mood to RUU back to stock; when I say wipe, I mean I used the advanced wipe tab, the format data tab, and the "swipe to factory reset". I figured maybe things will go well if everything is formatted by TWRP. Thankfully I backed up all of my apps and data beforehand so it wasn't too much of a hassle.

I then sideloaded CM and after it flashed, I rebooted back into TWRP to see if this issue was still there, but it seems to be gone. It's not much of an advice, but I guess wiping everything will satisfy TWRP.
[One (M8) Original Android Development] dragontology:
Nope, unfortunately for me, even doing the advanced wipe throws up the error, and it won't flash anything.

I've done this four times now and I'm completely okay with RUU'ing back to stock, fastboot flashing TWRP, and restoring a backup. It's like an hour out of my day, which sounds bad, but I can give up using Android for an hour. But I got a log, and as soon as I get my Nandroid restored, I'll post it here and on github, and hopefully they can get it sorted out.

At this point I'm happy with Sense. Venom does everything I want. I just prefer the AOSP look to the Sense look. It's just an aesthetic thing, but for me as a design kind of guy it gets under my skin. And I'm tired of flashing ROMs all the time. It was fun and exciting, now I just want a phone I can use. I get that with Venom. They don't update much (most Sense ROM developers don't). I'm sure they'll update in August or September when we get 5.1, and that's cool. Sense isn't bad. At least it's not TouchWiz.
[One (M8) Original Android Development] KotTHECat:
Hello there!

Can you pls provide the changelog for twrp-2.8.6.1-m8?
[One (M8) Original Android Development] Captain_Throwback:
http://xdaforums.com/showthread.php?p=60855659#post60855659

(reading the thread is helpful)
[One (M8) Original Android Development] smknutson:
I've found, that rebooting the recovery and trying again often helps when I get those unable to mount red errors.
[One (M8) Original Android Development] imfuzzyyy:
same error on 2.8.6.1 error 255 on restore nandroid back up my phone fcks up and cannot restore nid to fully wipe and reintall rom to boot -.-
[One (M8) Original Android Development] bigd4ve:
I had the same problem and managed to restore using 2.8.5.0. I've since found out it wasn't the version of TWRP that fixed it for me. I had clean installed my ROM first then tried one last time to restore the nandroid and it worked. Messing around yesterday I've found this is the only way I can get a nandroid to restore.

It doesn't seem to matter for me which version of TWRP I'm using, what options I've selected, compressed or uncompressed. I have to clean install the ROM then restore the nandroid and it works. Takes much longer than it should but at least I found a solution that works for me. Can anybody tell me why this is the case or suggest a way to restore a nandroid without doing this first?

I'm running LeeDrOiD 7.4.3. I backed up the clean install and can restore this nandroid without issue but cannot restore my other backup over this one. It will only restore over a clean install. Something corrupt in the data partition? But then why does it restore fine just after a clean install?
[One (M8) Original Android Development] imfuzzyyy:
correct have restored my nandroid backup after flashing a clean install rom, coincedence since Im on same rom as yours, it really takes time to restore the back up super slow... hope my nandroid back up didnt f*ck up my stock rom lol since I didnt test it to restore
[One (M8) Original Android Development] Captain_Throwback:
Did one or both of you post a recovery log? I'm betting you have a bad file on /data that isn't getting cleaned up (possibly a virus) and that's breaking the restore. Only way to permanently fix it is to use the "Format Data" option in TWRP, and get rid of the nandroid that includes the bad file.

If you look in the log of the failed restore and see an error unlinking a file in a folder called "com.facebok.kata" then that's your problem. Definitely not a TWRP issue - in fact TWRP is trying to prevent you from restoring a bad file, so I'd say that's a good thing rather than a bad one.
[One (M8) Original Android Development] bigd4ve:
I posted a recovery log at the top of page 112. I don't know how to interpret them properly but I believe this is the issue. Is there a way to find out what this file is/does so I can prevent it from ruining nandroids? I don't think I have any viruses. I've tried several different backups one of which was a stock ROM from when I first got the phone and that also had the problem.
[One (M8) Original Android Development] Captain_Throwback:
The file appears to be posing as a Facebook database file, but it isn't. That's why I say it's likely something malicious. The reason you can't restore ANY nandroid is because TWRP is unable to delete that file when it tries to wipe prior to the restore. Just because you don't think you have any viruses or malicious code doesn't mean you don't. This specific file prevents TWRP from even accessing it, even with root access while in recovery, so that in itself should raise a red flag. Formatting the data partition is the only way to permanently remove the file. However if you then restore a nandroid that contains the file, you're back in the exact same situation you started with.
[One (M8) Original Android Development] smeejaytee:
[MENTION=1162986]Captain_Throwback[/MENTION] do you by any chance know when we'll get 2.8.7.0 I notice other devices seem to have updated TIA.

Sent from my M8
[One (M8) Original Android Development] Captain_Throwback:
Did you look for it?
[One (M8) Original Android Development] bigd4ve:
Thanks for explaining. This makes much more sense to me now. I wonder where and when I picked up this file? Just to be clear I should format my data partition which will wipe my internal SD card, correct? Also if I back up my internal SD card is there any risk of copying the malicious file back to the device when restoring files?
[One (M8) Original Android Development] Captain_Throwback:
Yes, Formatting Data will wipe internal storage. As long as that's all you back up (i.e. don't backup /data, just backup /sdcard), you *should* be fine.
[One (M8) Original Android Development] smeejaytee:
I did and I checked your site to see if you'd built one as I always use your versions, I prefer them thanks.

Sent from my M8
[One (M8) Original Android Development] Captain_Throwback:
I don't plan on building any versions. So I guess you're stuck with the official. There is no functional difference between mine and the official. If you use a theme, then using mine is simply a waste of time (which is why I'm not building them anymore).
[One (M8) Original Android Development] smeejaytee:
Sad to hear that your versions always seemed a step ahead of the official versions,

Why is it a waste of time if we use a theme ?

Sent from my M8
[One (M8) Original Android Development] Captain_Throwback:
Because the only difference between mine and the official (currently) IS the WIP updated stock theme. If you're using a custom theme, then both the official and mine are the same (which again, is why I'm not building it anymore).

There's no reason for me to build mine, because if an urgent fix is necessary, it can be done via an official, device-specific build.
[One (M8) Original Android Development] joni2012:
Captain need speak you, send pm please

Team SkyDragon loving
[One (M8) Original Android Development] imfuzzyyy:
correct I have that f*cking file on my data com.facebook.kata and I cant seem to delete it no matter what I do in root explorer so how can I get rid of that file? I've encounter it when I change my rom into MIUI I cant install facebook no matter what so thats what I decided to delete the data and I cant seem to delete it no matter what. so the only way is to rename that file so I can install that f*cking facebook
[One (M8) Original Android Development] bacon612:
I'm trying to flash 2.8.7.0 on my vzw m8 with no luck. I have always flashed recoveries in hboot. I have renamed the IMG to 0P6BIMG.ZIP and tried to flash in hboot but it gives me an error message. Do vzw users require a specific twrp build or am I doing something wrong?
[One (M8) Original Android Development] jas88:
Flashify worked for me flashing 2.8.7.0
[One (M8) Original Android Development] Captain_Throwback:
Just flash the new image from TWRP. Install -> Images

I'm not sure why everyone is making it so difficult . . .
[One (M8) Original Android Development] mrrocketdog:
+1 m8 but att.:thumbup:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[One (M8) Original Android Development] bacon612:
Flashify worked for me to flash 2.8.7.0 on my VZW M8.

What makes it difficult is that nowhere in the OP does it suggest that the builds above 2.8.5.0 (which had a vzw specific version) work on all variants. Nor does it suggest to use flashify. I tried using the TWRP manager to flash and it wasn't able to do it for me successfully. If TWRP is now carrier agnostic, the VZW variant should be removed from the list in TWRP manager as it is misleading.
[One (M8) Original Android Development] Captain_Throwback:
TWRP has been unified (or carrier-agnostic, as you called it) since 2.8.0.3. Why would it suggest to use Flashify? As I just said (and you quoted), you can update within TWRP directly.

TWRP Manager isn't a TeamWin app. You'll have to contact the dev if you want that fixed.
[One (M8) Original Android Development] mrrocketdog:
duh , for me. did not realize could update thru twrp directly. thank you for that info [MENTION=1162986]Captain_Throwback[/MENTION]. learning everyday.: good:

"all i can really do , is stay out of my own way and let the will of heaven be done"
[One (M8) Original Android Development] ancola66:
Working on M8 but time backup and restore very long :

With 2.8.6.0 backup time is 238s

and with 2.8.7.0 backup time is 494s
[One (M8) Original Android Development] tuxattack80:
Had a rare occurrence using 2.8.7.0 last night. I was running cm12.1 last latest nightly on the Sprint variant and out of no where it rebooted itself and started optimizing apps all on its own as if I wiped cache. Once it was done optimizing it rebooted once again instead of loading up the OS. When I finally got back into recovery it took forever to load twrp and when I attempted to wipe and reflash it refused to mount any partitions and keep giving me multiple mount and crypto errors. Basically had to ruu back to stock. This was using cm12.1 Sprint variant with no custom kernels or tweaks other than those provided by cm and theme engine.

Nothing was set to encryption that I'm aware of.