yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Astrobrewer:
I have had some issues with my phone since unlocking with sunshine. See separate thread http://xdaforums.com/droid-turbo/help/help-bricked-xt1254-unlocking-to-t3279581 for description. I have a theory about this now and would like some opinions from folks with more experience.

I used device encryption on my Turbo before the OTA update to Lollipop. After encrypting the phone I would be prompted to enter my PIN to decrypt the data partition before the phone would boot, and then I'd have to enter the PIN again after boot to unlock it. After the OTA I no longer had to enter my PIN when booting the phone, but I would still have to enter it after boot to unlock. After the OTA the phone still reported that it was encrypted in the system security settings even though it didn't need a PIN to decrypt at boot time. That makes sense from what little I know because encrypting the device re-writes the data partition, and the OTA didn't touch the data partition and could not un-encrypt it. I was baffled by this, but I didn't want to factory reset and wipe the data partition to let me re-encrypt the phone.

So after the OTA, the data partition of my phone was still encrypted, but magically the phone was able to decrypt data and boot without my PIN. I don't know why. But one clue is that after unlocking and installing TWRP I looked at TWRP log and saw a log message saying something about decrypting with default PIN. Anyway, I never wiped data, but my phone somehow manages to boot. Re-flashing system and recovery caused problems at first, but now it seems to be back to the way it was. I haven't flashed a new ROM yet, but I expect that when I do I'll have to wipe data and that will get everything back to normal.

My question is has anyone else experimented with device encryption and is this behavior expected?

Thanks.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] meskes:
Not having to enter a PIN with the factory image was a bug I initially discovered, and reported, during the *initial* Android L SOAK test. Needless to say, they never fixed the bug (plus one of the Stagefright CVEs) during the second SOAK rollout. I reported it then, too. They did nothing. That second SOAK was the straw that broke the camel's back, for me. I will never participate in another.

As far as this bug goes, what I would do, is an FDR, and re-encrypt your device to wipe the key store and start over.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Astrobrewer:
I got notifications that the SU4TL-49 OTA was ready to install on my phone, and I had read that if you try to install it with anything but stock recovery that you get into a boot loop. I figured it was a matter of time before I ended up accidentally installing the OTA upgrade and so decided to wipe my phone and go back to stock, and I would use that opportunity to re-encrypt the phone. It took me a couple of tries before I discovered that factory reset isn't enough to remove the encryption, and that I had to reformat the data partition. This took a few hours of going back and forth between reverting to stock, upgrading, rooting, configuring and starting over before I finally got it right, but eventually the phone said that it wasn't encrypted and gave me the option to encrypt. What a pain. After setting up all my apps for the third or fourth time I thought I was done. Whenever I rebooted I was prompted for my PIN before android booted. I even had to enter my PIN to run TWRP.

At least that's the way it was for a few hours. Now when I reboot it just starts up android with no password again. All the effort to un-encrypt and re-encrypt seems to have been a waste. Oh well, at least I avoided getting into boot loop hell.

Hopefully this unencrypting without requiring password/PIN thing gets fixed when (if) they come out with M for the turbo.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Astrobrewer:
This just keeps getting better and better. I decided to flash the Unofficial CM13 ROM this afternoon just for fun. I got it all set up when I found that the GPS receiver wasn't working. Searching the thread I found a link to a flash-able radio image to fix that, and when I rebooted to TWRP it prompted me for a password to decrypt the data partition! Unfortunately it didn't like my PIN no matter how many times I entered it. I don't know if there's something about entering a numerical PIN on the qwerty keyboard, but it had worked earlier in the day before it stopped prompting for passwords. After a bunch of tries and reboots I gave up and downloaded a fastboot flashable version of the same. I've spent most of the day screwing around with this phone already and I'm not going to reformat the data partition again today for sure! Maybe it just needs a good night's sleep.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Encryption is totally broken on CM13. The issue is that our version of TWRP cannot decrypt it. I contacted the maintainer of TWRP for our device about this issue and he said that he tried to fix the issue, but he failed.

Also, official CM13 has been out for a while now for the Turbo. No need to go with the unofficial version.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Astrobrewer:
Thanks for the info [MENTION=5901115]TheSt33v[/MENTION], but I'm not sure that it's totally broken.

The strange thing is that I was using TWRP 3.0.2 just fine after encrypting phone while on stock ROM, and it worked for a while even after flashing CM13. Then it just stopped liking my PIN. But CM13 takes my PIN and decrypts data just fine. So my phone is usable for now, and the problem of it decrypting without asking for a PIN is solved for now. I just went to cyanogenmod and see that there's a CM13 recovery. Based on your post I'm guessing that's what is broken, so no point in flashing that. Oh well, at least my phone is secure.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Just FYI, our TWRP maintainer has fixed decryption. You can get the latest version here: https://www.androidfilehost.com/?w=files&flid=39562 (version 3.0.2-0 mod 02 as of this writing). I still had trouble decrypting a partition that was previously formatted using the stock recovery menu, but once I formatted the data partition using this version of TWRP and re-encrypted, it decrypted fine.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Astrobrewer:
Yes they have fixed it! I found TWRP Mod 2 over the weekend and saw from the change log that decryption was fixed. I flashed it and it works great. :D No problems decrypting my previously encrypted data partition since I flashed mod 2. The funny thing about it is that basic TWRP 3.0.2 (no mod) worked well enough for long enough for me to flash CM13, and it even seemed to work for a little while after that. But then it decided that it didn't know how to decrypt my phone anymore and I was stuck until Mod 2. I can't explain why it worked for a while and then stopped, but I'm very happy that mod 2 fixed it.

Thanks for your help and support. Sometimes I feel like I'm the only user who encrypts his phone. There don't seem to be a lot of threads about encryption/decryption issues.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Most people don't seem to think it's worth the impact that it has on performance.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Astrobrewer:
I was worried about the performance hit too before I tried it. But I don't notice any real difference in performance. Of there is a hit it's too small for me to tell.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] oldidaho:
This is a very interesting thread. I would like to encrypt so I can setup my work exchange email as its a requirement. Just to clarify what is the order to do this in? Currently I am running RR 6.01 but have run CF's 1.3.6 ROM most of the time as its awesome.

Can I encrypt using RR or do I need to switch back to CFs ROM or to stock Lollipop after installing the upgraded TWRP in place of the standard version I am running now?

thanks for the help and information.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
You can encrypt on RR. Just make sure you're running TWRP version 3.0.2-0 mod 2: https://www.androidfilehost.com/?w=files&flid=39562

If encryption fails, you'll need to format your data partition (aka do a factory reset) using this version of TWRP. Then it will work.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] oldidaho:
thanks so much for the clarification! Being encrypted, how does that affect installing future updates or restores? Can I still flash ROMS and other ZIPS from TWRP the same as now?
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
The only difference is that you'll have to enter your password/pin every time you boot twrp. Don't try to use a pattern lock. Everything else will be the same.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] oldidaho:
thank you for the help! I was able to encrypt my RR MM install without having to wipe the data partition. It now prompts me to put my PIN in when booting up and when going into the modded version of TWRP. It then is able to decrypt the partition in TWRP so as you said just like before. Only difference is a little longer boot up time. Performance seems the same to me.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] oldidaho:
Guess I spoke too soon. phone was working fine for a day. Yesterday at work I'm looking at my phone as it reboots on its own (just sitting there). I then get cant decrypt partition message. Cant do anything and it wont boot up into the OS WO giving this error. In TWRP still cant do anything because it cant decript the partition. So I formatted the data partition and started over. I had saved a recent backup to my PC so I was able to get back to that. Now running CFs latest instead of RR. I need my phone, cant take a chance on this happening again as I was instantly dead in the water. Just wont encrypt.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] ChazzMatt:
Well, just as you used CM13 Marshmallow and RR Marshmallow just fine without encryption, not sure why you went to CF Lollipop instead of RR just because encryption didn't work. It just seems you were implying it's CM13 or RR at fault when you used them just fine before, and even now on CF you are NOT using encryption.

But it's your phone, so you can run what you want.

I do commend you for having a recent backup on your PC.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] oldidaho:
I should have clarified, I dont think RR had anything to do with my issue. I actually really liked RR, it has some great features, great performance and good battery life too. I just missed the Moto features in the stock and CFs ROMs.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] TheSt33v:
Strange. I've been using RR M encrypted for several weeks now with no issues. Oh well. If you're happy with modified stock, that's all that matters. You can encrypt that too if you like. I'm a big fan of the Moto features as well, and RR M has basically all of them built in besides Voice (chop chop flashlight was removed for a while, but it has been added back). Although I've never understood what Voice offers that Google Now does not.
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] Astrobrewer:
Mystery solved!

I have been running the CM13 ROM for the past few months and it's been great, but now that Verizon came out with official Marshmallow I decided to go back to a stock-based ROM again because I've been missing VOLTE. So I flashed ComputerFreak274_MM. After flashing and rooting I was back in the stupid state of the phone saying that it was encrypted but booting without a PIN. It seemed unreal that Moto/Verizon would have left this bug in MM too. So I reformatted data, re-flashed and rooted the ROM and tried encrypting. Then I discovered that it won't encrypt if it's rooted. So back to wiping, re-formatting and flashing again, but this time I am able to successfully encrypt before rooting. Success! Now root and start setting up the phone. Now I have to enter my PIN before it will boot into the system or into TWRP. Yay! By now it's 1:00am and I have to be at work early, so I let it sit overnight while my apps download. In the morning I flash SuperSU and notice that I wasn't prompted for a password to decrypt when I booted into TWRP and I wasn't prompted for password when booting system after flashing SuperSU. WTF!!! More time wasted. It seemed that stock ROMs just don't like encryption. :crying:

Anyway, after stewing about it all day I randomly chanced into the solution. In the Security settings menu there's an option under Encryption called "Secure start-up" which only becomes available when phone is encrypted. The Secure start-up options says:

"You can further protect this device by requiring your PIN before it starts up. Until the device starts up, it can't receive calls, messages, or notifications, including alarms. This helps protect data on lost or stolen devices."​

Secure start-up defaults to disabled for some reason, and when it's disabled the phone automatically decrypts itself when it boots without requiring PIN entry. So you can encrypt your phone and still be totally unprotected. What a dumb-ass default! :mad:

But when I enable Secure start-up then encryption works the way it should -- with phone prompting for PIN before booting. :D Maybe I just didn't notice it, but I didn't see anything when I encrypted the phone saying to enable Secure start-up to actually protect the phone. I'm guessing that this option was there in Lollipop too; but who knew???
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Kallu609:
I need some help with the Flashtool. Did I build the .ftf right if I choose everything but the .ta files (following this guide)? Also, which things should I wipe when selecting firmware? There's APPS_LOG, DIAG, SSD and USERDATA.

Does this seem like a good output when starting?

31/044/2015 16:44:53 - INFO - Flashtool Version 0.9.19.8 built on 24-09-2015 22:00:00
31/044/2015 16:44:53 - INFO - Executing search strategies to find proxy selector
31/044/2015 16:44:54 - INFO - No proxy found for IE. Trying next one
31/044/2015 16:44:54 - INFO - No proxy found for firefox. Trying next one
31/044/2015 16:44:54 - INFO - No proxy found for java. Trying next one
31/044/2015 16:44:55 - INFO - Syncing devices from github
31/044/2015 16:44:57 - INFO - Scanning devices folder for changes.
31/045/2015 16:45:17 - INFO - Pulling changes from github.
31/045/2015 16:45:19 - INFO - Devices sync finished.
31/045/2015 16:45:27 - INFO - Device connected with USB debugging off
31/045/2015 16:45:27 - INFO - For 2011 devices line, be sure you are not in MTP mode
31/046/2015 16:46:57 - INFO - Device connected with USB debugging on
31/046/2015 16:46:57 - ERROR - Cannot identify your device.
31/046/2015 16:46:57 - INFO - Selecting from user input
31/047/2015 16:47:08 - INFO - Connected device : E58XX
31/047/2015 16:47:08 - INFO - Installed version of busybox : N/A
31/047/2015 16:47:08 - INFO - Android version : 5.1.1 / kernel version : 3.10.49-perf-g83fc9bc / Build number : 32.0.A.6.152

My device I think is in MTP mode currently, does it affect the flashing?

I'd really appreciate the help, I'm very beginner in flashing roms and don't want to brick my phone.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mxpcc:
Few minutes ago I have the same problem. Finally I select only APPSLOG and USERDATA and it clean phone from carrier bloatware and apps that I've installed. Now it's like simfree from open market, not any carrier.

USB debugging off and in mtp mode but what was problematic for me because I couldn't find anywhere how long I should keep VOL down press. So when I start flashtool and try to connect with z5c and start pressing VOL down I keep it press all the time, when appear info about restart device still keeping it pressed till second connection starts and the green line in bottom shows, then I release button and it passed.

Wysłane z mojego SM-G920F przy użyciu Tapatalka
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Kallu609:
Thanks for the reply! The only thing I'm really wondering now is that what those two sections mean, DIAG and SSD. Is it needed/okay to wipe them?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] mxpcc:
I'm still waiting for answer what they means but I didn't tick them. As I sad I only tick APPSLOG and USERDATA nothing more and now I have clean soft.

Wysłane z mojego SM-G920F przy użyciu Tapatalka
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Kallu609:
Ahh.. Of course, I'll try flashing today and see how it goes. I'll be reporting back.

E: Flashing went just fine. Didn't wipe anything, had USB-debugging and MTP on. Didn't bundle the .ta files when making the .ftf, but I don't think that really even matters.

Thanks for all the help! :)
[Android Q&A, Help & Troubleshooting] janalam92@yahoo.com:
I changed 3 galaxy s6 and s6 edge after flash hang in samsung logo and then Odin flash fail pls guide any soltution why this problem

Allah Bless You All
[Android Q&A, Help & Troubleshooting] amw2320:
Hi,

I'm trying to figure out how to root the new ZTE ZMAX 2. My hope to start is to figure out if it is vulnerable Justin's ZTE backdoor which keeps root for ADB. However I have been unable to get temproot using anything I can find so far, and most I have tried besides the one-click-apps are pretty old scripts (android-run-root-shell). Are there any scripts out there that are known to work on 5.1? VTS shows I am vulnerable to CVS-2015-6616 and 6608, but I haven't seen anywhere that these are public exploits. Any direction would be helpful. Thanks.
[Android Q&A, Help & Troubleshooting] Skorpion96:
I've the same problem with zte a5 2019 which is vulnerable to cve-2015-1474 and there is no exploits available.
[Nexus 5 Q&A, Help & Troubleshooting] phantom146:
Hi!

This is just a quick question and a voting poll on which you will prefer and most of you have on their device right now (possibly after voting please explain why you choose the other one from the latter)

This is to help me to determine whether I'm gonna flash a CM based rom or an AOSP stocking based Rom(Which I have been using since MM was released)

What all our goals and possible feuds you can discuss below are:

1.) Which one has bettery battery life in idle?

2.) Which one has faster performance?

3.) Which one has the most buttery smooth effect on your hands?

Features differ from every rom and we couldn't care less about it because we flash whichever has the feature we need
​
[Nexus 5 Q&A, Help & Troubleshooting] phantom146:
Any reasons anyone?

So far aosp stock based is a favorite

I would pretty much want to hear your opinion/take on this
[Upgrading, Modifying and Unlocking] PDAaddictz:
Can someone help me? Is there a installer or instructions to do it? Thanks in advance.
[Upgrading, Modifying and Unlocking] Rudegar:
if you cant use cab installs or install using activesync

your device maybe cid locked you can prob find info about uncid locking it in wiki or in elf forum
[Upgrading, Modifying and Unlocking] PDAaddictz:
I'm having problem with the cab file. Thanks for your help.
[Upgrading, Modifying and Unlocking] levenum:
Lets have a little more info please:

What precisely do you do to install a cab file?

Do you copy it to your device and click on it in file explorer?

What error message are you getting?

Does this happen with all kinds of different cab files or some specific ones?

If it is certain cabs tell us where you got it from and what it is for.

Also if you purchased your Touch from a cell-co it may be application locked.

You should check the Touch forum and the WiKi for unlocking procedure.

P.S. This is not CID lock. That would be irrelevant to 3rd party software only to changing ROM.
[Upgrading, Modifying and Unlocking] PDAaddictz:
I'm new to this phone. How can I install it into my Touch? I'm lost on the installation.

B the way, If it's locked, how can I unlock it? Unlock SIM?

Thanks in advance.
[Upgrading, Modifying and Unlocking] Rudegar:
http://wiki.xda-developers.com/index.php?pagename=HTC_Elf

read it

http://xdaforums.com/forumdisplay.php?f=374

read it too
[Upgrading, Modifying and Unlocking] qcampbell123:
umm i need help say i wanted to download a app, like a game or any random app for my htc fuze, how do i install it? I ive tried just draging the file and droping them in the program file but i just dont kno how to do it at all.

HOW DO I INSTALL APPS TO MY FUZE OR A WINDOWS MOBILE PHONE?

thanks...
[Upgrading, Modifying and Unlocking] orb3000:
Put them on your memory card and run them from there

is very similar to a process in a PC
[Nexus 6P Q&A, Help & Troubleshooting] xddawg:
hi there, i am a new owner of the 6p and have a few questions regarding tmobile.

does wifi calling/VoLTE work with the 6p out of the box? and how do i check that it is working?

and also, how do i check if i am on band 12? thank you
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
Under cellular networks its a setting called enhanced 4g lte. That is what enables volte. *#*#4636#*#* will take you to a menu to check bands and other stuff.
[Nexus 6P Q&A, Help & Troubleshooting] Pilz:
WiFi calling and VoLTE both work out of the box on T-Mobile. You can download the LTE Discovery app which will tell you what band you're connected to
[Nexus 6P Q&A, Help & Troubleshooting] SpookyTunes:
Enhanced 4G LTE Mode (VoLTE / HD Calling) works!

[IMG="Enhanced 4G LTE Mode"]https://dl.dropboxusercontent.com/u/1451579/2016-01-01%2014.24.55.png[/IMG]

Wi-Fi calling works!

[IMG="Wi-Fi calling"]https://dl.dropboxusercontent.com/u/1451579/2016-01-01%2014.25.16.png[/IMG]

Visual Voicemail works!

[IMG="Visual Voicemail"]https://dl.dropboxusercontent.com/u/1451579/2016-01-01%2014.26.35.png[/IMG]

Band 12 on T-Mobile after 6.0.1 update works!

[IMG="Band 12 LTE"]https://dl.dropboxusercontent.com/u/1451579/2015-12-31%2019.59.07.png[/IMG]
[Nexus 6P Q&A, Help & Troubleshooting] xddawg:
Another quick question. My LTE becomes a H when making phone calls. Is this normal? And what apn are you guys using. Thanks
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
Woops hit the thanks instead of quote.

What network?
[Nexus 6P Q&A, Help & Troubleshooting] xddawg:
Tmobile
[Nexus 6P Q&A, Help & Troubleshooting] XxMORPHEOUSxX:
Sry. Didn't actually read. I just saw a new post and did not connect that you are the OP. Lol

Its an issue. http://xdaforums.com/showthread.php?p=64227798
[Nexus 6P Q&A, Help & Troubleshooting] Barsky:
I am on fi now, but the first day I had the phone I put my tmo prepaid sim in. Noticed in the APN, the setting APN type was : default,supl

On my previous t-mobile branded phones the setting has been:

APN type: default,mms,supl

Not sure if it matters or resoved any problems, but I edited mine to match.
[Nexus 6P Q&A, Help & Troubleshooting] SpookyTunes:
If I am on LTE with VoLTE, I stay on LTE. If I am on HSPA+, I drop to Edge while on a call.

Not all LTE towers support VoLTE yet. Find someone else on T-Mobile with a VoLTE and see if you get HD calling. You can really hear the difference. It sounds like a Skype to Skype call.

My APN settings are the defaults for T-Mobile. You can reset them to defaults when in the APN menu from the three dots drop down.

The first one if for data and Assisted GPS (default,supl).

The second one is Wi-Fi calling (ims). Not sure if it is used by VoLTE.

The third is for MMS (mms).
[G4 Q&A, Help & Troubleshooting] Fma15:
I know there is an unlocked bootloader for the h815, but I'm just wondering if one is being developed for any other models. Either way, anyone who is involved with developing roots and anything like that keep up the great work! Sorry if this has been asked. If it has can you please give me the link?
[G4 Q&A, Help & Troubleshooting] Leeum:
Yes there is one on the way hopefully. I have the H815K (Australian Model) G4 and can't unlock the bootloader sadly. All i would like to do is Install CM13 :(
[G4 Q&A, Help & Troubleshooting] HIshan Pavidu:
Y you dont try another way luke flashfire flash cm with flashfire maybe it will be worked with bootloader locked devices i flashed xposed with flashfire and it work greatly