Since .apk is a regular executable file, I was more than sure that I will be able to trick mobile Gmail in the same way as I was able to trick PC version of Gmail years ago to force it to send a PC executable (.exe) which it prevented as well. Turned out, I was wrong. Usually changing file extension to .dat or some other or compressing it with password (encrypting file) was enough for PC version of Gmail. However, for mobile version, everything that I have ready at a hand and tried failed as well: - sending as plain file (obviously), - changing .apk extension to .dat or some other, - compressing with ZIP with no password, - compressing with ZIP (ultra compression) and encrypting archive with a password, - compressing with 7ZIP (ultra compression) and encrypting archive with a password, - using an [7 years old idea](https://security.stackexchange.com/questions/35818/are-password-protected-zip-files-secure#comment55859_35818) of double compression: - compress .apk file into .zip file without password, - compress resulting .zip file again into another .zip file with password / encryption. If mobile Gmail is able to detect that I am sending .apk executable file even in 7zip compressed file with password (or it can prevent me from sending such file for any other reasons) do I have any option left? Is there any way to send .apk file over mobile Gmail (attach them to message composed in mobile Gmail)?

I have a Moto Z2 Play device (android 7.1.1) that was rooted with Magisk (v20.1) with Magisk Manager app (v7.4.0). Magisk Manager Hiding feature was also activated. When I deactivated the Magisk Manager Hiding: 1. Magisk Manager v7.4.0 got auto updated to v22.1 and Magisk was shown as not installed 2. Selected direct install option in the app to install Magisk (v22.1) 3. Rebooted the Moto Z2 Play device And the device failed to power up... Is there any way to fix this? I have tried Fastboot boot to TWRP and flashing Magisk-v20.1.zip but to no avail, device still doesn't start up normally when I press the power button. Currently I can still boot into fastboot/recovery mode.

**tl;dr:** _I have my Motorola Moto Z2 Play / A8.0 encrypted and I was forced to provide PIN during very early boot phase of my phone. Since about 1-2 weeks ago -- when my phone had a one-time accident of very long boot -- Android stopped asking for that PIN at boot time. How can my phone be still encrypted and no longer need that PIN to decrypt itself?_ ---- About 2-3 years ago I have encrypted my Motorola Moto Z2 Play (now with Android 8.0). I used the same PIN for the encryption process, so starting from that moment, I had to use PIN three times: - boot (encryption) - startup (SIM card PIN) and - startup (fingerprint unlock). About 1-2 weeks ago my phone hanged badly. After force-restarting, it needed about 20-30 minutes (!) to actually start. From that moment on, I am no longer needed to enter PIN to decrypt phone and start Android. The first time, I now need to provide it, is when unlocking my SIM card. My phone was not reset after that one-time very long boot accident. After it finally got up, I had everything in places: all apps, accounts, settings etc., nothing changed, reset or removed. I have double-checked that my phone is still encrypted: There was no system update (phone stays at Android 8.0.0 from 1+ year and probably forever), no new application installed and no change in system configuration for long months. My phone uses fingerprint + PIN screen lock. PIN in numeric, four digit. From [this answer](https://android.stackexchange.com/a/162451/20449) : > If the phone boots up without asking for a password, it is most likely not protected by encryption in the way you would expect. In theory, it might not be encrypted at all (...). [This answer](https://android.stackexchange.com/a/196467/20449) explains that: > The best way to tell if your Android device is encrypted (and the encryption is actually in use) is to reboot it and see if it asks for a password/PIN with a prompt on a black screen that says: "To start Android, enter your PIN" (...) The lack of prompt means the master key is not encrypted". I don't see such prompt, so I now know that my master key is not encrypted (while the file system itself seems to be encrypted -- above screenshot). But this answer does not explain how / why my master key was encrypted for 2-3 years and stopped being encrypted two weeks ago after a very long boot accident / force-reset. So, why or when my Android 8.0.0 can decide to decrypt my master key and no longer need me to enter startup PIN to decrypt it?

**tl;dr** _Is it possible to root an Android 8.0 phone that is accessible only via USB? Is it then possible to extract encryption .key file out of it in order to decrypt its SD Card that was formatted and encrypted as Adoptable Storage? Can all of this be done with not functioning, broken screen?_ ---- There is a lot of good quality guides here on how to encryption .key file from /data/misc/vold folder and use it to decrypt Adoptable Storage on any Linux-based computer. But all these guides assume that you have: * rooted phone, * access to phone's screen. Your phone must have screen operable to either: * install and use some app on it: [here](https://android.stackexchange.com/a/145446/20449) or * confirm some dialog on it, unlock screen lock, if accessing it via USB: [here](https://nelenkov.blogspot.com/2015/06/decrypting-android-m-adopted-storage.html) or [here](https://android.stackexchange.com/a/135836/20449) . Can the very same process be achieved if my phone have a screen in pieces? Can I: * root a phone and * copy encryption .key file from /data/misc/vold folder after rooting, when I only can access my phone via USB? Assuming that screen cannot be used at all. My Motorola Moto Z2 Play is now in pieces after a car run over it. Screen is in pieces, battery is separated. Mainboard seems in one piece and I think is functioning. Whenever I attach USB it seems to be starting up. Is there **any way** to get encryption key file from it, doing this totally remotely (via USB)? Or attaching a new, functional screen is an absolute must in this case? **EDIT**: _The phone in question is Motorola Moto Z2 Play, which started its history with Android 7.0.0, then went through A7.1 and landed finally with Android 8.0.0, updated about 1+ year ago. All versions of Android on this phone seems very close to stock one, as in most Moto phones._ _Based on [this article](https://support.motorola.com/us/en/products/cell-phones/moto-z-family/moto-z2-play/documents/MS126539) , I believe there's a FDE / full disk data encryption implemented there._

*Google Calendar's event's drag'n'drop functionality* stopped working... again, after nearly exactly [two years since previous report](https://android.stackexchange.com/q/204158/20449) . Tried to restart both Google Calendar and phone itself (Motorola Moto Z2 Play with Android 8.0.0), cleared app cache and then data, without any results. I did very little to my phone before that happened: * no configuration changed, * nothing actually doing with my phone. I have only installed one new up -- FakeStandby -- as suggested [here](https://softwarerecs.stackexchange.com/a/76642/8327) , but since this app has nothing to do with the calendar itself, I would be surprised, if that would be a source of the problem. To clarify problem: _On a day view (not: agenda) long-pressing any event now brings no effect. Previously it caused an event box to be risen up visually above others, and moving finger around screen allowed to move event to some other hour or day. Now, drag'n'drop functionality does not exist / does nothing._ Is there any know report about some bug, bug's regression or is this a generally known problem? Or is this again my stupid phone going wako in exactly the same way during second anniversary of the moment, this problem appeared for the first time? **EDIT**: _From what I have learned, when Calendar becomes "locked" (no event's drag'n'drop) all items in calendar are visually more flat than usual. When functionality "returns" they again become a little bit 3D-like._

After latest update to Wikipedia mobile app for Android (3-4 weeks ago, the one that introduced many changes in user interface), I cannot find "History" functionality or tab. I've checked the usual place (three dot menu on article) and probably all other and... nothing. Is this functionality removed after the latest update of this application? How can I browse articles that I've read recently?

At some point in time (about a week ago) *something* happened to my Motorola Moto Z2 Play / Android 8.0 that caused my base apps to not have access to my media files (i.e. audio, photos etc.). Examples: * all my custom ringtones (i.e. based on my own media files) were reset to default sound: * Contact apps reset custom ringtones for contacts to default one, * Alarms & Clock app reset custom alarm tone to default one, * SMS (Messages) app reset custom message notification tone to default one, * system-wide default notification tone (set by me to custom) was reset as well, * system-wide default ringtone (set by me to custom one) was reset, * [I cannot pick a photo for a contact](https://android.stackexchange.com/q/226466/20449) because my contacts app keeps saying: "No pictures are available on the device". While first situation is resolved. I see my custom ringtone files in the list and I can go through my contacts and assign them again. But second situation is not resolved. I see this error all the time and I cannot change any contact's photo. This is verified as not a bug (tested three different contacts-like applications and all of them shows exactly the same message, when trying to change contact's photo). But still, it seems that problem is limited to contacts-related apps only. Other apps still has read and write access to my custom files. For example: : - (read) I can pick any photo or other custom file and attach it to an e-mail, send it as MMS or share it in any other way or - (read) upload it to OneDrive or Google Drive etc. or - (write) my Camera app is still able to make new photos and store them in "DCIM" or - (write) my sound recorder is able to record sound and write audio files. The only thing that has changed on my phone recently and that I suspect as the cause of above metioned situation was Android 7.1.2 --> Android 8.0.0 update. Is there anything I can do (since replacing contacts app didn't resolve the situation) or check in this case? Or resetting the phone to factory defaults is the only option that I am left with? **EDIT**: _I have cleared cache and data of media app, as suggested in comment. It didn't help._

I am trying to change a contact's photo under my Motorola Moto Z2 Play / Android 8.0.0 (Security Patch July 2019): > Contacts > 🔍 (find a contact) > 🖉 (edit contact) > 📸 (change photo) > Select new photo and I am hit with an error saying: > No pictures are available on the device. I don't understand this situation, because: * I have dozens of photos and pictures on this device, in "DCIM", "Pictures" and others, * I can change widget's icon without any problem (my launcher allows this), * I've been changing contacts' photos many times on this device. * I've managed to change contact's photo on other devices and Android versions (A9 and One), * I don't think this is due to SAF (details: [here](https://android.stackexchange.com/a/226441/20449) and [here](https://android.stackexchange.com/a/225940/20449)) , because I am still on A8, not A10. Since I did this last time a couple of months / maybe a year ago. The only thing that comes to my mind is that I did this last time under old, good Android 7.1.2. And the recent update to Android 8.0.0 maybe messed up something. I have tried putting new photo into every folder that came to my mind: - root, - DCIM, - DCIM/Camera, - Pictures, - Pictures/Contacts (I've been using this one for years). All for nothing. Always seeing this damn message. I even went as far as: - Contacts > 🔍 (find a contact) > 🖉 (edit contact) > 📸 (change photo) > Take new photo, - capture some test image, - use it, - see, where it is stored (turned out that in: DCIM/Camera, as expected), - remove it, - try again using "Select new photo". My phone went as wako as allowing me to change the photo of one of contacts in the first place (i.e. after using "Take new photo"), stored it in DCIM/Camera folder and when I tried to use the very same photo from the very same folder, but using "Select new photo" instead, it again claimed that I have no pictures in this device). Can anyone help me? How to workaround this problem? How to change contact's photo in A8?

I've been using Nova Prime for about 5 years, which includes doing at least 10-20 settings backup-and-restore on various devices. Today I made one another (on my Motorola Moto Z2 Play / Android 8.0 Oreo) and to my extreme surprise I have noticed that all my (restored) contacts widgets have a nasty "main" app (i.e. Contacts) icon overlay over each my contact's photo. Picture worth thousand words -- before (left) sending Z2 to repair and after getting it back (right): Analysis so far: - the problem is only with Contacts; other widgets (Wikipedia and Fancy Widgets in my case) have no "main" app icon overlay, - happens on both widgets restored from Nova Prime's backup and freshly added, - happens on Motorola Moto Z2 only (i.e. does not happen on Motorola One), - happens on Motorola Moto Z2 only this time (starting from this backup restore), since I hadn't this problem for past half year, prior to sending this phone for a repair. Questions: - does anyone else experiences similar problem? - what is its source: is it caused by recent change to Contacts or Nova Prime? - is there any workaround or a way to get rid of this nasty little thing? I am adding a contact-shortcut widget by: - opening Contacts app (default app under 8.0 Oreo?), - finding given contact and tapping it to get to details, - tapping three-dot and selecting _Create shortcut_ from menu. The only difference that I noticed is that prior to this backup restore (prior to sending my Moto Z2 for a repair and getting it back) and on every other device I am getting shortcut created right after above (right after tapping _Create shortcut_). While this time and on this Moto Z2 I see some new, additional _Add to Home screen_ window, where I have to tap _Add_. I assume (given above) that the problem's source is Nova Prime, not Contacts app. I am using Motorola Moto Z2 Play (XT-1710-09) with Nova Prime 6.0 on board Android 8.0 Oreo.

Up until Android 8.0 / Oreo (haven't got chance to test this issue under 9.0 / Pie) there is no Polish layout for physical USB keyboard and writing Polish national letter (i.e. using Right Alt key) is not possible in Android with physical keyboard connected through USB and micro USB OTG cable. Is there anything I can do to resolve this problem? Some option for installing missing layouts? _Supporting, OT and philosophic question_: Is this some kind of political isolation of my country by Google / Android developers or an ostracism? I have carefully checked that there are keyboard layouts for *each and every neighboring country that surrounds Poland* -- i.e. German, Czech, Slovak, Ukrainian, Latvian, Lithuanian and Russian. But there is no for Poland. **EDIT**: _This question is about Motorola Moto Z2 Play, which has an unmodified, stock version of Android 8.0 Oreo and such version doesn't have "Polish" physical keyboard layout. This question does not deal with devices provided by any other manufacturer, with modified Android, where "Polish" physical keyboard layout can be available._

On my Motorola Moto Z2 Play with stock version of Android 7.1.1 currently I have: - 188 photos in DCIM > Camera folder, - 10 pictures in Pictures > Contacts folder, - 5 pictures in Pictures > Icons folder, - 24 pictures in Pictures > Wallpapers folder. Yet, when I am trying to assign a new photo for one of my newly created contacts (Google Account) in Contacts app it claims that I have no images in my device and does not open a file browser / does not allow me to pick any photo for given contact: What am I missing here? How to workaround this weird problem and be able to pick a photo for any contact (other way than using PC for this purpose)?

My Bluetooth headset (SoundBuds Rise) will play its own generic ringtone when it's connected to my phone (Moto Z2 Play). I just went through and gave a bunch of my contacts custom ringtones, so I don't have to pull my phone out to look at who is calling. Is there anyway to force my headset to use my ringtone instead of its?

I would like to have mobile Google Maps' content on my Moto Z2 Play in different language (Polish) than rest of the system (English). Is this possible? If yes, then how to achieve this? Based on my research and previous tries, I managed to: - change language of audio guidance in mobile Google Maps to Polish, - change content in desktop / PC version of Google Maps to Polish (even though my Windows 10 and Google Chrome runs in English). However, I can't / don't know how to change content's language in mobile Google Maps. **Edit**: _[An answer](https://android.stackexchange.com/questions/29124/change-language-for-one-application-google-now-voice-recognition-root-availabl) suggested by Robert is out of option in this particular case, because it requires device to be rooted. I don't have an ability to root the device for which I want Google Maps to run in a different langauge than the rest of the Android system._

Has anyone managed to successfully use Android Auto with any car based in Poland? My Motorola Moto Z2 Play fails completely when I am trying to connect it to my Toyota Aygo 2018+ (tried many good quality USB cables): Android Auto shutdowns itself automatically after about 0.5 second and car's display shows "Unrecognized device". After reading some stuff in the Internet and contacting Motorola and Toyota support it turned out the entire thing doesn't work, because I don't have Android Auto application installed on my phone and I don't have it installed, because it is not available in Poland. Yet, I've heard and read some stories about people here, in Poland, able to use Android Auto without any problems. Does anyone have any idea, how this was accomplished? The only idea that comes to my mind is that these people somehow managed to force-install Android Auto on their phones, somehow omitting Google Play store limitations (i.e. unavailability of this application in Poland).

I have had my Z2 Play for half a year, and soon after I got it I unlocked the bootloader with Motorola's official method, installed TWRP, rooted it with Magisk and installed Xposed Framework. I was on Nougat all the time and used it happily. A few months ago it started repeatedly asking to OTA update, but I just ignored the messages. Then one day, I must have accidentally pressed something, because I think it tried to update. I got a message that the update failed or something like that. The phone gradually got worse after that, randomly rebooting into TWRP. I could somehow get it to boot Android by going to the bootloader and chosing "factory mode" but mostly the modem would not work at all and the phone would not be usable. Trying to solve it, I decided to flash a whole ROM, hoping to remove all of the damage done by the botchered update. Since I already had unlocked my bootloader and TWRP, I decided to just flash a custom ROM, since I did not know if flashing stock would work with TWRP. I found some of the custom ROMs on XDA, and tried to flash them with TWRP. However, flashing would not work. I got some error code 255. I am attaching a screenshot of the error. I tried both flashing via the adb sideload method via my Mac and via USB OTG (flash drive) but I got the same result for both. Having seen this, I decided to try to relock the bootloader and restore stock firmware. I tried following this tutorial . However, that did not seem to work. Here is my fastboot output: Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot devices ZY224BLVMC fastboot Pals-MacBook-Air:platform-tools Fiksdal$ ./fasboot oem lock begin -bash: ./fasboot: No such file or directory Pals-MacBook-Air:platform-tools Fiksdal$ fastboot oem lock begin -bash: fastboot: command not found Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem lock begin (bootloader) WARNING: This command erases all user data. (bootloader) Please re-run this command to continue. OKAY [ 0.003s] Finished. Total time: 0.005s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem lock begin (bootloader) Flash valid Android images now (bootloader) Then re-run this command to lock OKAY [ 0.018s] Finished. Total time: 0.018s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash partition gpt.bin (bootloader) has-slot:partition: not found Sending 'partition' (45 KB) OKAY [ 0.008s] Writing 'partition' (bootloader) Validating 'gpt.default.xml' (bootloader) Security version downgrade (bootloader) Image primary_gpt failed validation (bootloader) Preflash validation failed (bootloader) Cancelling 'gpt.default.xml' FAILED (remote failure) Finished. Total time: 0.264s Pals-MacBook-Air:platform-tools Fiksdal$ sudo fastboot flash partition gpt.bin Password: sudo: fastboot: command not found Pals-MacBook-Air:platform-tools Fiksdal$ sudo ./fastboot flash partition gpt.bin (bootloader) has-slot:partition: not found Sending 'partition' (45 KB) OKAY [ 0.005s] Writing 'partition' (bootloader) Validating 'gpt.default.xml' (bootloader) Security version downgrade (bootloader) Image primary_gpt failed validation (bootloader) Preflash validation failed (bootloader) Cancelling 'gpt.default.xml' FAILED (remote failure) Finished. Total time: 0.259s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash bootloader bootloader.img (bootloader) has-slot:bootloader: not found Sending 'bootloader' (5115 KB) OKAY [ 0.209s] Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml' (bootloader) Committing 'bootloader.default.xml' (bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot' (bootloader) - flashing 'rpm.mbn' to 'rpm' (bootloader) - flashing 'tz.mbn' to 'tz' (bootloader) - flashing 'devcfg.mbn' to 'devcfg' (bootloader) - flashing 'cmnlib.mbn' to 'cmnlib' (bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64' (bootloader) - flashing 'keymaster.mbn' to 'keymaster' (bootloader) - flashing 'prov.mbn' to 'prov' (bootloader) - flashing 'sbl1.mbn' to 'sbl1' OKAY [ 0.548s] Finished. Total time: 0.943s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash logo logo.bin (bootloader) has-slot:logo: not found Sending 'logo' (2192 KB) OKAY [ 0.093s] Writing 'logo' OKAY [ 0.066s] Finished. Total time: 0.344s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash recovery recovery.img (bootloader) has-slot:recovery: not found Sending 'recovery' (20580 KB) OKAY [ 0.838s] Writing 'recovery' (bootloader) Security version downgrade (bootloader) Image recovery failed validation (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 1.234s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash recovery recovery.img (bootloader) has-slot:recovery: not found Sending 'recovery' (20580 KB) OKAY [ 0.729s] Writing 'recovery' (bootloader) Security version downgrade (bootloader) Image recovery failed validation (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 1.125s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash dsp adspso.bin (bootloader) has-slot:dsp: not found Sending 'dsp' (16384 KB) OKAY [ 0.667s] Writing 'dsp' OKAY [ 0.132s] Finished. Total time: 0.984s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash oem oem.img (bootloader) has-slot:oem: not found Sending 'oem' (232923 KB) OKAY [ 10.302s] Writing 'oem' (bootloader) Security version downgrade (bootloader) Image o failed validation (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 10.554s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.0 (bootloader) has-slot:system: not found Sending 'system' (517135 KB) OKAY [ 20.549s] Writing 'system' (bootloader) Security version downgrade (bootloader) Image s failed validation (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.1 (bootloader) has-slot:system: not found Sending 'system' (522979 KB) OKAY [ 20.458s] Writing 'system' (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 20.674s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.2 (bootloader) has-slot:system: not found Sending 'system' (524215 KB) OKAY [ 20.487s] Writing 'system' (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 20.704s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.3 (bootloader) has-slot:system: not found Sending 'system' (521087 KB) OKAY [ 19.126s] Writing 'system' (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 19.330s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.4 (bootloader) has-slot:system: not found Sending 'system' (518083 KB) OKAY [ 19.082s] Writing 'system' (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 19.295s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.5 (bootloader) has-slot:system: not found Sending 'system' (515569 KB) OKAY [ 18.974s] Writing 'system' (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 19.192s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.6 (bootloader) has-slot:system: not found Sending 'system' (250209 KB) OKAY [ 9.380s] Writing 'system' (bootloader) Invalid signed image (bootloader) Preflash validation failed FAILED (remote failure) Finished. Total time: 9.579s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash system system.img_sparsechunk.7 (bootloader) has-slot:system: not found fastboot: error: cannot load 'system.img_sparsechunk.7': No such file or directory Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash modem NON-HLOS.bin (bootloader) has-slot:modem: not found Sending 'modem' (75092 KB) OKAY [ 2.888s] Writing 'modem' OKAY [ 1.878s] Finished. Total time: 4.954s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase modemst1 (bootloader) has-slot:modemst1: not found Erasing 'modemst1' OKAY [ 0.020s] Finished. Total time: 0.210s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase modemst2 (bootloader) has-slot:modemst2: not found Erasing 'modemst2' OKAY [ 0.020s] Finished. Total time: 0.210s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot flash fsg fsg.mbn (bootloader) has-slot:fsg: not found Sending 'fsg' (2932 KB) OKAY [ 0.114s] Writing 'fsg' OKAY [ 0.065s] Finished. Total time: 0.364s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase cache (bootloader) has-slot:cache: not found Erasing 'cache' OKAY [ 0.016s] Finished. Total time: 0.206s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase userdata (bootloader) has-slot:userdata: not found Erasing 'userdata' OKAY [ 2.252s] Finished. Total time: 2.442s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase customize (bootloader) has-slot:customize: not found Erasing 'customize' (bootloader) Permission denied FAILED (remote failure) Finished. Total time: 0.194s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase customize (bootloader) has-slot:customize: not found Erasing 'customize' (bootloader) Permission denied FAILED (remote failure) Finished. Total time: 0.194s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot erase clogo (bootloader) has-slot:clogo: not found Erasing 'clogo' (bootloader) Permission denied FAILED (remote failure) Finished. Total time: 0.192s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem lock (bootloader) Still require signed boot.img OKAY [ 0.003s] Finished. Total time: 0.003s Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot reboot Rebooting Finished. Total time: 0.005s This seemed to do nothing to my device. I wondered if maybe the bootloader was in some sort of locked/unlocked limbo, so I tried to unlock the bootloader again using the key I got from Moto by email. That did not work either. Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot oem unlock THECODEFORMYDEVICE (bootloader) invalid boot state OKAY [ 0.005s] Finished. Total time: 0.008s So I seem to be getting nowhere. There has to be some way to totally wipe everything, to get a fresh start? I do not care if I have to restore stock firmware, stock bootloader, whatever. I just want to be able to at least use my phone somehow. Is my device totally bricked? Is there nothing I can do? I used adb and fastboot on macOS High Sierra. At the request of @acejavelin, I am posting some more information: Pals-MacBook-Air:platform-tools Fiksdal$ ./fastboot getvar all (bootloader) version: 0.5 (bootloader) version-bootloader: moto-msm8953-C0.C7 (bootloader) product: albus (bootloader) board: albus (bootloader) secure: yes (bootloader) hwrev: P4 (bootloader) radio: 3 (bootloader) storage-type: emmc (bootloader) emmc: 64GB SKHYNIX HCG8a4 RV=08 PV=A2 FV=00000000000000A2 (bootloader) ram: 4GB SKHYNIX LP3 DIE=8Gb M5=06 M6=03 M7=00 M8=5F (bootloader) cpu: MSM8953 (bootloader) serialno: ZY224BLVMC (bootloader) cid: 0x0032 (bootloader) channelid: 0x40 (bootloader) uid: B5E66CBA00000000000000000000 (bootloader) securestate: flashing_unlocked (bootloader) verity-state: enforcing (bootloader) iswarrantyvoid: yes (bootloader) max-download-size: 536870912 (bootloader) reason: Last time flashing failed (bootloader) imei: ***************** (bootloader) meid: (bootloader) date: 07-29-2017 (bootloader) sku: XT1710-09 (bootloader) battid: SNN5983B (bootloader) iccid: (bootloader) cust_md5: (bootloader) max-sparse-size: 268435456 (bootloader) current-time: "Sat Jan 3 17:37:25 UTC 1970" (bootloader) ro.build.fingerprint: motorola/albus/albus:7.1.1/NPSS26. (bootloader) ro.build.fingerprint: 118-19-18/24:user/release-keys (bootloader) poweroffalarm: 1 (bootloader) ro.build.version.full: Blur_Version.26.261.24.albus.reta (bootloader) ro.build.version.full: il.en.US (bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0 (bootloader) version-baseband: M8953P_23.33.07.34R ALBUS_EMEADSDS_CUST (bootloader) kernel.version: Linux version 3.18.31-perf-gf3fa6ef (hud (bootloader) kernel.version: soncm@ilclbld83) (gcc version 4.9 201501 (bootloader) kernel.version[2] : 23 (prerelease) (GCC) ) #1 SMP PREEMPT T (bootloader) kernel.version: ue Dec 5 00:03:05 CST 2017 (bootloader) sbl1.git: git=MBM-NG-VC0.C7-0-ge9cd975 (bootloader) rpm.git: git=5578f74 (bootloader) tz.git: git=MBM-NG-VC2.06-0-g82f94af-dirty (bootloader) devcfg.git: git=MBM-NG-VC2.06-0-g82f94af-dirty (bootloader) keymaster.git: git=MBM-NG-VC2.06-0-g82f94af-dirty (bootloader) cmnlib.git: git=MBM-NG-VC2.06-0-g82f94af-dirty (bootloader) cmnlib64.git: git=MBM-NG-VC2.06-0-g82f94af-dirty (bootloader) prov.git: git=MBM-NG-VC2.06-0-g82f94af-dirty (bootloader) aboot.git: git=MBM-NG-VC0.C7-0-gb6d4956 (bootloader) qe: qe 1/1 (bootloader) frp-state: no protection (77) (bootloader) ro.carrier: reteu all: listed above Finished. Total time: 0.034s

Each time when I open the Phone app, I see Favourites tab (first one) as default. This is completely useless for me, because Google uses its weird logic to tell me which contacts are my so called favourites and this logic produces completely wrong results -- i.e. I see "favourite" contacts which aren't truly my favourite ones. This tab is also useless, if your contacts have more than one phone number, because instead of showing a list in this case and letting you pick the number, it always calls the default number. This isn't working in my case, because I have a lot of contacts which I contact both privately (i.e. during weekends and evenings; using private phone number) and on business grounds (using company phone number). So using the default phone number and Favourites tab is pointless in my case. For the above reasons, I am not using Favourites tab at all and I am always forced to switch manually to recent phones / call history tab. Is there any way to make that tab displayed as default each time I open up the Phone app. My stack: - Motorola Moto Z2 Play, - Android 8.0 Oreo. I am using the default, system Phone app. No 3rd party solution.

When you open up the Contacts app second or the following time, it always shows last view (i.e. where I left it), i.e. the most recent contact search. I am using this app purely for searching the contacts, so the need of tapping _Back_ to go back to recent search results list and then tapping _X_ to clear the last query **each time** I want to search for another contact simply kills me. This is as stupid UX approach as it can be. Is there any way to change the default view, in which Contacts app opens by default each time? My stack: - Motorola Moto Z2 Play, - Android 8.0 Oreo. I am using the default, system Contacts app. No 3rd party solution.

From at least [Android 4.0](http://itfuckup.com/2014/09/27/android-and-a-shit-called-mtp/) to at least [Android 8.0](http://itfuckup.com/2018/06/02/the-mtp-protocol-a-catastrophic-failure/) (most likely Pie as well) we are forced by Google-Microsoft trust into using MTP as the only (?) files transportation method between Android-based device and Windows-based computer (if not count as pity, sad and dully methods as attaching files to e-mail messages). For at least **five** years billions of users around the world are forced into using solution that is: - extremely slow (transferring large files collections or huge files takes hours even on USB 3.1), - extremely unreliable (device can stop responding even after sending just a few files), - not working at all most of the time (device that stoped working may not "restart" and may not allow you to copy files even after dozens of unplug cable-plug it again sequences). (I can see above message after _each and every file_ that I copy; I have to unplug and plug the USB cable again after copying _each single file_) Questions: 1. _Supporting, OT and philosophic one_: What am I missing? Why we are forced into using this madness? Why nothing had been done for five years to resolve it? 2. _Main and real one_: Is there **any** other way? Any fast, reliable method of transferring files from Android-based device to Windows-based PC? Described problem was tested on Windows 7 and Android 8.0, so not the newest ones, but still very widely used. And on the quite modern phone -- Motorola Moto Z2 Play -- but of course happnes on dozen other Android-based devices that I own and billions of Android-based devices other uses. And, as stated in links given in first sentence, absolutely nothing had been done into resolving this problem for at least five past years. Is this some kind of sadistic way of understanding market and treating its customers, developed by Microsoft and Google or what?

I am using and very enjoining the fact I can connect my base Android Messages application to its [web counterpart on my PC](https://messages.android.com/) and get much more flexibility in writing and managing all my SMSes. But, I am pretty much irritated that it displays so many notifications about the fact that it is being connected to this or that PC: I think that I see it dozen of times: - daily, each time I start a PC, - each time I restart my browser and - even each time my Messages application / mobile phone looses and regains connection to the Internet and thus Messages application and its browser counterpart reconnects each other. Is there any way to disable this pseudo-security messages? I can't find corresponding configuration option in either Messages application on my Android phone or in its web counter part. And I am afraid to force-block notifications from this mobile application in my Android settings becuase I think that I will loose all the notifications from it, i.e. not just those about being connected, but also notifications about received SMS message. The same goes for notification about using mobile plan, in web counterpart: Is there any way of getting rid of it permanently or do I have to close this nag everyday, every time I restart my browser?

My 4 GB/64 GB/8 core Moto Z2 is incredibly slow when it comes to built in Contacts app. I.e.: - it requires at least 3-4 seconds to open it up, - it needs at least 2-3 seconds to exchange phone numbers with corresponding contacts in dial log. It has nothing to do with the battery charge (happens all the time, on charge level between 10-100%) and has also nothing to do with overall system performance (both system and all other apps are working as fast as possible / expected; Contacts is the only problematic application). I have 95 applications installed. None of them are performance-hungry and many system services (i.e. Google+, Google Assistant, YouTube, Google Drive, Google Play Music / Movies, Photos, etc.) disabled, because I am not using them. Is there anything I can do to fix this problem (except for replacing Contacts with something else)?