yashsingh1/xdaforums huggingface dataset:
[One (M8) Original Android Development] Captain_Throwback:
File system doesn't matter. There were some MTP fixes pushed recently that should help with MTP in the next release. The problem seems to exist for people with a lot of files to index and Windows times out loading the driver because of it. The updates handle that differently/better (at least that's my understanding). Once that update comes out, you'll know for sure or you can sync and build it from source now and see how it works for you.
[One (M8) Original Android Development] teemo:
For OneX these fixes definitely helped. Windows drivers load pretty fast now. Before that, I had to reload the drivers after the timeout, then it worked. Sometimes :D
[One (M8) Original Android Development] Captain_Throwback:
Because I can't help myself, if you'd like to test this ahead of the release, look here (also please post feedback there).
[One (M8) Original Android Development] linezero:
why does every time I do a normal wipe factory rest, my ext-sdcard gets wiped? i'm on twrp 2.8.0.2. It started to happen very recently
[One (M8) Original Android Development] Captain_Throwback:
Because that version is bugged. That's why 2.8.0.3 was released very shortly thereafter. Flash the latest and it'll work properly.
[One (M8) Original Android Development] Muellersirch:
Encryption Issues - CM11 and TWRP

﻿I have encrypted my phone using the Option in Settings>Security>Encrypt Phone in CyanogenMod 11.

Ever since doing so, I have been unable to decrypt my phone from Recovery to perform a nandroid, clear cache/dalvik, or fix permissions. The data partition shows up as 0MB, and I do not get any option to decrypt. I am able to decrypt and use the phone properly when booting into the system. From what I've found online so far, I suspect an issue with the encryption footer. Can anyone point me in the right direction?

I am currently running cm-11-20141010-NIGHTLY-m8.zip. I have had issues with previous nightlies as well, never had Recovery recognize the encryption since I set it up a few months ago.

Recovery is currently TWRP 2.8.0.3, but also had issues with previous versions.

Phone is the Sprint version.

I have cross posted this in the Cyanogenmod Forum.
[One (M8) Original Android Development] Captain_Throwback:
It turns out you have to actually include the option for decryption when building TWRP (I mistakenly assumed it was included automatically), so none of the decryption stuff is included. Oops.

I can build a test build with it included tomorrow, but you'll have to get it from my thread over at theMikMik. I'll ask [MENTION=912474]Dees_Troy[/MENTION] to make sure it gets included when the next official update comes out.
[One (M8) Original Android Development] Captain_Throwback:
#TapatalkFAIL
[One (M8) Original Android Development] noname55804:
Hey,

i cant backup on my 64GB Fat32 formatted sdcard. It alwys sais Unable to create folder (errno=30). Tried it on 2.8.0.3 and .4.

Any idea how to solve this?
[One (M8) Original Android Development] williamfold:
Your sdcard may be corrupt. I was getting that error once, backed up my card, reformatted, error was gone...
[One (M8) Original Android Development] Captain_Throwback:
How much free space do you have on your card? Also, why is your card formatted FAT32 and not exFAT?
[One (M8) Original Android Development] -Duir-:
Shouldn't 64GB be exFat?

That error means your sdcard is being mounted as read-only.
[One (M8) Original Android Development] noname55804:
Thanks, will try that

<cyanogenmod has removed exFat support....

Ah ok and how can i change?
[One (M8) Original Android Development] Captain_Throwback:
[MENTION=3409890]Muellersirch[/MENTION]

http://themikmik.com/showthread.php...ecovery-v2-8-0&p=300598&viewfull=1#post300598

---------- Post added at 11:14 AM ---------- Previous post was at 11:00 AM ----------

I'm not sure where you got this information, but it's incorrect. CM has to work with exFAT cards, as it's how all XC cards are formatted. I've used CM11 on the M8 with my 128GB exFAT-formatted card with no issues.
[One (M8) Original Android Development] noname55804:
see this

https://github.com/CyanogenMod/andr...mmit/43447934d2abca36550a4014985ba73db806d380
[One (M8) Original Android Development] Captain_Throwback:
That's just the exFAT-nofuse support built into the kernel. That was reverted, in favor of the exfat-fuse stuff that's been being used since ICS. I will say it again - exFAT works fine with CM.
[One (M8) Original Android Development] DannySchaukens:
I made a backup, I don't find the files/map. I want to delete it. If I look in restore, it is still there. I check the map twrp...

Thx for helping me out!
[One (M8) Original Android Development] bitwiser:
Did you get a chance to look at the recovery log? any idea why it is failing or how I could restore original image?

Thanks for your time :)
[One (M8) Original Android Development] jmz:
Nothing is out of the ordinary with the backup. I have confirmed though, that I can backup and restore WITHOUT compression enabled. I start having issues with compression enabled though. It seems hit or miss with it enabled
[One (M8) Original Android Development] jonny68:
On the TWRP website I'm following the instructions on how to flash TWRP via terminal on my phone(I don't have a laptop or PC) I'm copying and pasting the commands exactly as described and it's giving me an error, has anyone successfully flashed the latest TWRP HTC M8 via terminal?
[One (M8) Original Android Development] Michealtbh:
Just use the Flashify app
[One (M8) Original Android Development] jonny68:
But you need to be rooted to use that to the best of my knowledge and I'm not rooted yet just unlocked bootloader , I wanna install TWRP then flash supersu zip
[One (M8) Original Android Development] Michealtbh:
You can't flash from terminal without root, you'll have to use fastboot.
[One (M8) Original Android Development] jonny68:
Thanks for telling me as it doesn't actually state that on the TWRP website, but I should have actually remembered myself as I got s-off on the M7 using terminal before, and now I remember someone mentioning this.

Pain for me as I have to keep going to Internet cafes full of loud teenagers playing games, on Facebook , etc.. ah well!
[One (M8) Original Android Development] bitwiser:
OK, is there any way to uncompress them on a PC to try a restore without compression? or check to make sure they are valid backups? Obviously I can't make another backup of my original system now.
[One (M8) Original Android Development] thekalby:
I've heard TWRP was having some problems on the M8. Can someone explain to me what exactly these problems are, and whether or not they have/can be worked out?
[One (M8) Original Android Development] GSLEON3:
The major issue is the "black screen", which really is just the screen timing out. It is a feature with a bug, the device just won't wake after a flash process that exceeds the screen timeout setting. A long hold power reset gets you going again. The best fix for now is to disable screen timeout in TWRP settings.

There have also been reports of nand backups failing to restore, though I believe that issue was rectified with the 2.7.0.2 update.

No biggie.
[One (M8) Original Android Development] maaaxi:
I can confirm that V 2.7.0.2 still have the problem , as I backed up & restored with it and it failed ( 2 backups) , it really ruined a good progress in a game i was playing :(
[One (M8) Original Android Development] Michealtbh:
I believe only compressed backups fail to restore, so disable compression and you'll be fine.
[One (M8) Original Android Development] guyd:
I've seen some people report having problems with Compression turned On and doing backups, or restoring a compressed backup.

I leave compression turned off and have not had a lick of trouble!
[One (M8) Original Android Development] shortyboy:
I can confirm restore issues with latest twrp on SD and on internal memory without compression.
[One (M8) Original Android Development] Michealtbh:
I've made and restored dozens of backups with compression disabled and haven't had a single problem
[One (M8) Original Android Development] Root-Maniac:
No problems restoring here either.
[One (M8) Original Android Development] simondavies315:
I experienced the black screen issue earlier and **** myself thinking I had somehow bricked the device flashing ViperOne
[One (M8) Original Android Development] guyd:
Turn off the screen timeout settings in TWRP and you'll never have that problem ever again!
[One (M8) Original Android Development] Nekromantik:
There are other bugs too, after first booting into twrp if you choose install button then screen goes blank for 2-4 secs and then goes back to twrp menu if you press power.
[One (M8) Original Android Development] Captain_Throwback:
Can you post a recovery log?
[One (M8) Original Android Development] Muellersirch:
The recovery log is not being saved after rebooting due to the save location being encrypted. Export to sdcard seems to send it to /data/media (also an encrypted location). Is there a way to export it if I were to sideload adb from recovery?

The errors I'm seeing in recovery that seem pertinent are:

E:Could not mount /data and unable to find crypto footer.

E:Unable to mount /data.

E:Unable to mount /data/media during GUI startup
[One (M8) Original Android Development] Captain_Throwback:
Do you not have an external card in the device?

EDIT: You can also adb pull /tmp/recovery.log

Also, if you could please post your feedback over in the thread where I posted the recovery, it'll help keep the testing separate. I only like to bring it over to the official thread once it's been tested and confirmed to work, and I can ask TeamWin to merge it to the official.

EDIT 2: http://themikmik.com/showthread.php...ecovery-v2-8-0&p=300601&viewfull=1#post300601
[One (M8) Original Android Development] Johnny424:
Hey Captain...From what I read do sense users need to update to your unnofficial 2805 build or should we stick with the 2803 official build? Do to changes mostly for aosp
[One (M8) Original Android Development] Captain_Throwback:
No one needs to update, unless you're going to help test the AOSP decryption.
[One (M8) Original Android Development] linezero:
delete
[One (M8) Original Android Development] Captain_Throwback:
[MENTION=3409890]Muellersirch[/MENTION] (in case you don't get notified of replies over there)

http://themikmik.com/showthread.php...ecovery-v2-8-0&p=300605&viewfull=1#post300605
[One (M8) Original Android Development] jkolner:
I realy don't get this cos i can't get TWRP 2.8.0.1 or 2.8.0.3 to write Nandroid backups to my external SD card, so i have to copy them manually.

I have reformated the card from the phone and on my pc.

Im on ViperS 2.5.0 and FW 3.28 but has also tried 2.X.

When i go to TWRP Manager it says my External SD Location is /mnt/media_rw/ext_sd.

If i change it to my external SD card and close the app, the /mnt/ location is back.

Any idea what is wrong?
[One (M8) Original Android Development] Captain_Throwback:
It sounds like your issue is with the app, not recovery.
[One (M8) Original Android Development] jkolner:
But how do you set TWRP to archive Backups to the external SD card automatically, so i don't have to copy the backups my self?
[One (M8) Original Android Development] Captain_Throwback:
You need to ask the app devs. This is not an issue with the recovery.
[One (M8) Original Android Development] Vi553r:
You could also bypass the twrp app and go directly to recovery mode. Make a backup from there, you can select where the backup must go, so select your ext SD card.

Sent from HTC One M8 running Viper One
[One (M8) Original Android Development] jkolner:
Dammmmm.... i realy feel like a total mega NOOB now!!!

I have never seen the option when you do a backup, that you can choose Internal storage or Micro SD card.

Thanks a milion - you realy saved me at lot of time.

Note to self: read the text befor you ask stupid question!!!
[One (M8) Original Android Development] Nekromantik:
Has compression been fixed?
[One (M8) Original Android Development] Captain_Throwback:
Since when was it broken?
[One (M8) Original Android Development] jshamlet:
Has the issue with recoveries not booting correctly with the latest OTA been fixed? (As opposed to flashing)
[One (M8) Original Android Development] Nekromantik:
It was broken on 2.8.0.0

If you tried to backup it would freeze.
[One (M8) Original Android Development] Captain_Throwback:
Recovery boots fine.

Haven't had a freeze during a compressed backup.
[One (M8) Original Android Development] garyd9:
Well, I guess you could say that it "boots" fine. You can't see anything on the display, but it does "boot" just fine. ;)

This is for the new 3.28.x.x firmware, and specifically referencing "fastboot boot twrp.img" (as opposed to flashing it and then booting.)

Take care

Gary
[One (M8) Original Android Development] Captain_Throwback:
I didn't realize you were referring to the 3.xx firmware with your question - you just said latest OTA, and most people haven't received an OTA past 2.xx at this point. Booting on 3.xx won't work until updated kernel source is released by HTC.
[One (M8) Original Android Development] garyd9:
I was just clarifying the other person's post. With the updated bootloader, I pretty much expect issues like this.
[One (M8) Original Android Development] donmarkoni:
Which version are you referring to, guys?

I got these booting using fastboot boot some.img :

TWRP_multirom_m8_20141001-02.img

TWRP_Recovery_2.8.0.4_M8_CPTB.img

openrecovery-twrp-2.8.0.3-m8.img

I'm on 3.28.401.6 FW, if you can't see my sig.
[One (M8) Original Android Development] garyd9:
That's interesting... I wonder what the difference is.

I tested with openrecovery-twrp-2.8.0.3-m8.img as downloaded directly from http://techerrata.com/browse/twrp2/m8. (Which is the link provided for the m8 GSM device on the official TWRP website.) The HBOOT version on the phone is 3.19.0.0000. (This is a dev edition device that just got the 3.28.x.x OTA.)

Process tested:

// after the OTA applied and a couple of OTA related reboots

// reboot to fastboot

adb reboot bootloader

// attempt to boot twrp

fastboot boot openrecovery-twrp-2.8.0.3-m8.img

The result is a slightly visible vertical line being drawn upwards on the far right side of the phone screen (perhaps 2 px wide) from about 1/4 from the top of the phone screen up to near the top of the phone screen. The vertical line then disappears and I'm still on the fastboot screen. "adb devices" shows that the device is in recovery, but the recovery display doesn't show.
[One (M8) Original Android Development] Captain_Throwback:
The behavior will be the same on all of them; they all use the same kernel/dtb.

I need kernel source to update the dtb for it to boot properly.
[One (M8) Original Android Development] donmarkoni:
I don't understand... :confused: Well, I know what are you talking about, but those DO boot properly, at least for me...
[One (M8) Original Android Development] Captain_Throwback:
Hmmm in that case, perhaps the issue is NOT the recoveries? I can also boot recovery on my device, and I'm using HBOOT 3.19.0.0000.

Maybe the person needs an updated version of fastboot?
[One (M8) Original Android Development] garyd9:
I'd ask which version of fastboot you're using, but it doesn't seem to be versioned. I'll try this: Are you using a fastboot from HTC's site, a fastboot from google's dev toolset, or something else?
[One (M8) Original Android Development] Captain_Throwback:
I'm using whatever the latest version of fastboot is from the Android SDK.
[One (M8) Original Android Development] garyd9:
Strange. I just updated my platform tools (using the ADT "SDK Manager".) SDK tools are at 23.0.5 and platform tools at "20." I see the exact same thing with fastboot boot xxx.img not working. I'd really like to think I'm missing something obvious here...

Let's see.. I'm using Win8/64 at the moment. Can also try Win7/64, but won't be able to try linux until I get home tonight. I'd be really surprised if the version of windows impacted fastboot, though.
[One (M8) Original Android Development] Captain_Throwback:
Yeah it shouldn't make a difference. I am in Ubuntu, though. My platform-tools version is also 20.
[One (M8) Original Android Development] garyd9:
Same problem from win7/64. Will try from Linux when I get home tonight.

This is just weird!

Sent from my HTC One_M8
[One (M8) Original Android Development] garyd9:
No luck with the latest adb/fastoot in linux either. Very odd. Perhaps it's something particular to the dev edition (1540) firmware? [MENTION=1162986]Captain_Throwback[/MENTION], which firmware do you have loaded?
[One (M8) Original Android Development] Captain_Throwback:
I have the WWE firmware loaded. If you point me in the direction of the dev edition firmware, I can try it and see if booting works or not.
[One (M8) Original Android Development] garyd9:
The problem is that it doesn't make any sense. Nothing in the firmware EXCEPT the bootloader should be loaded before fastboot, so nothing else should make any difference!

If it DOES make a difference, then loading *whatever* it is could cause a problem for you (and a simple nandroid backup wouldn't restore whatever it is anyway... you'd need a full RUU or something that re-writes all the various partitions.)

I think, at this point, it might be a good idea to just sit and watch what happens. If there's a pattern of 1540 folks having the same issue, but WWE/401 folks don't, then we can take a reasonably educated guess as to the issue. If, on the other hand, 1540 people (who actually got the 1540 OTA and didn't restore a nandroid with it) are able to "fastboot boot img" properly, then I might have something wacky with my phone.

Gary
[One (M8) Original Android Development] Captain_Throwback:
I'd still like a link to the firmware ;).
[One (M8) Original Android Development] garyd9:
In order to get the complete update, I'd suggest downloading the RUU from here and then applying the OTA (either naturally or via here)

This would set you up with all the partitions (and not just /system)

Edit: Obviously, you'd need to set your CID/MID properly.
[One (M8) Original Android Development] Captain_Throwback:
I know how to update a device, lol.

I'm not even on a GSM variant, so it's definitely not safe for me to run that RUU. If you don't have the firmware, that's fine.
[One (M8) Original Android Development] jshamlet:
This.

However, since I suspect the next update won't come until Android L, I'm just going to leave TWRP installed.

---------- Post added at 02:27 AM ---------- Previous post was at 02:23 AM ----------

Mine actually hung hard while attempting to boot the latest TWRP recovery (as in, I had to hold all three buttons to force a restart). I was able to get Philz to "boot", and I could tell that I was accidentally hitting buttons because of the vibration., but no video - just the fastboot screen. I finally caved and installed TWRP so that I could re-root my phone.
[One (M8) Original Android Development] Captain_Throwback:
Are you on the Dev Edition firmware too? Can you upload it somewhere for me to test?
[One (M8) Original Android Development] jshamlet:
Yes, though it started as an AT&T carrier edition. It's now been fully converted to the developer edition.

What partitions/blocks do you need?
[One (M8) Original Android Development] Captain_Throwback:
I just want the firmware zip from the OTA. You're on the latest version (3.xx) right?
[One (M8) Original Android Development] jshamlet:
Yes, I'm now at 3.28.1540.5.

I wouldn't mind at all, if I can find it. Does the OTA updater keep a copy of the zip somewhere?

As an aside, the built-in shell doesn't seem to support the find command? What kind of "Developer Edition" phone doesn't have a full busybox install?
[One (M8) Original Android Development] tvandegr:
To chime in on this, the 4.4.3 update seemed to cause the same inability for fastboot to boot via a recovery img (no issues installing a recovery) there were several people tbat mentioned it in the updates thread. I had not realized that TWRP had fixed it before the 4.4.4 release.
[One (M8) Original Android Development] Captain_Throwback:
Once it's installed, it gets deleted. Usually someone pulls a copy of the OTA zip, but I guess no one has done that yet.
[One (M8) Original Android Development] jshamlet:
Ah, sorry. I didn't think to postpone and backup the ZIP. Hopefully someone will slow down and get a copy.
[One (M8) Original Android Development] garyd9:
They have, and I gave you a link for it in this post: http://xdaforums.com/showpost.php?p=56052155&postcount=617 .. which would point you to this link to the actual OTA: https://www.dropbox.com/s/oghzza93g...540.4_release_39432124ijo1z75a3kzrca.zip?dl=0
[One (M8) Original Android Development] Captain_Throwback:
Ah thanks, sorry I missed it in your original post. I only saw the RUU link which confused me since I was asking for the firmware and you were talking about applying the OTA, etc.

---------- Post added at 09:50 AM ---------- Previous post was at 09:22 AM ----------

So I installed the Dev edition firmware, and TWRP still fastboot boots for me. I'm not sure why it's not working for everyone, but it definitely works for me and [MENTION=2977387]donmarkoni[/MENTION], so I really don't know what I can do about it.
[One (M8) Original Android Development] garyd9:
Which portions of the 1540 firmware did you install? Nothing in /data, /system or /cache partitions would have any impact on fastboot'ing an image. It would have to be one of the bootloader related partitions (tz, hboot, etc.)

[MENTION=2977387]donmarkoni[/MENTION] appears to be running WWE (401) (based on previous posts.)

I think it would be interesting to get an idea of how many people (if any) are running the full 1540 firmware (including the pre-boot firmware) and able to fastboot boot into TWRP. I also want to test fastboot boot into the stock 1540 recovery (instead of TWRP.) The problem (for me) is finding the time to do any of that stuff.
[One (M8) Original Android Development] Captain_Throwback:
System, Data & Cache aren't part of the firmware.

I installed everything that's relevant from the firmware, obviously including all bootloader-related images. I think the biggest difference is that I have a Sprint variant, which must allow the dtb in the recovery image to load properly, since the image includes the latest dtb for my variant. I still think it goes back to needing updated kernel source, as that was the issue last time. Something in the dtb source must've been updated to load properly with the new HBOOT and sbls for specific variants. Once source is released, this will be easy enough to confirm.

EDIT: I would test fastboot booting the stock 1540 recovery, but there's no way it'll work on my device because I have the Sprint variant, and the dtb isn't compatible.
[One (M8) Original Android Development] Mstaniford:
Can't install zip

I've been trying to get back to stock from Venom (so that I can get OTA for android 4.4.3). I've managed to wipe the system so currently I only have access to bootloader and recovery. I've tried installing a zip of a twrp backup of stock for my device but it always fails (right away, never gets very far in the process). I've read somewhere that I should do this using uncompressed files rather than a zip. Can I move the files to the phone via fastboot flash? If so, what is the correct location? I have a TWRP/BACKUPS/FAXXX/ folder on both external and internal sdcards. Is there a way to create a folder in there to put the files? what if I were to just do fastboot flash to /sdcard/Existing empty folder?

I've also tried going through the Restore menu but I can't get the files to show up.

My device:

HTC One M8, (m8_ul)

Unlocked

S-ON

CID: VODAP001

OS: Not sure as it is blank

TWRP: 2.8.0.3
[One (M8) Original Android Development] thebobmannh:
Why is the title of this thread still 2.8.0.1, not 2.8.0.3?