So I have run into a problem with my Nexus 7 2013 (2nd gen). Some apps have not been able to find my OTG storage (such as Spotify) that is attached to my device, but it is been able to find it on my Nexus 7 2012 (1st gen) and OnePlus 3. I have narrowed down the problem to this: In those images, you can see that the OnePlus 3 and the Nexus 7 2012(1st gen) have the OTG storage device showing up under /Storage/usbdisk and /Storage/18FA-B433 folders where as the Nexus 7 2013 (2nd gen) shows up as /Storage/0193-1CFF. But the problem there is that the first 2 show up as folders where the Nexus 7 2013 (2nd gen) only shows up as a file in 3rd party file explorers. (I can still browse the files in the built-in file explorer in Android) Does anyone here know what the problem could be causing it to show as a file instead of a folder and how I fix it? The device is rooted and running 6.0.1

I followed [this guide](https://wiki.lineageos.org/devices/taimen/install) until fastboot flash boot boot.img included and OK Then reboot in recovery mode Then *"Now tap Factory Reset, then Format data / factory reset"* included and OK **/!\\** BUT since then, _adb_ can't see my Nexus phone (Pixel 2XL - "taimen"), neither is it visible with lsusb when in recovery mode. I tried *"Apply from ADB"* or *"Enable ADB"* via lineageOS recovery mode gui, but adb devices returns an empty list :-| When in fastboot mode, I can see the phone via lsusb :

[stan@stan-xps139305 ~]$ lsusb
...
Bus 003 Device 012: ID 18d1:4ee0 Google Inc. Nexus/Pixel Device (fastboot)
...

Is there a way to get my phone recognized by _adb_, or to flash it via _fastboot_ directly... ? Also can _udev rules_ help... ? N.B. : SECURE BOOT is ON (don't know if it can be blocking...) [EDIT] >>> I also tried several USB cables/ports already :-| I'll try on another computer too ASAP I just fear the phone USB mode is kinda stuck while in recovery mode. This page shows the possible modes for pixel phone (mine is PIXEL 2 XL): [https://devicehunt.com/view/type/usb/vendor/18D1](https://devicehunt.com/view/type/usb/vendor/18D1) 4ee2 instead of 4ee0 is what I expect, but hell no. How is it that I can see the phone with lsusb while in fastboot mode, but cannot see it at all while in recovery ? >> these are the _udev_ rules I've set:

#GOogle Inc. 
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee1", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0666", GROUP="plugdev"
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d001", MODE="0666", GROUP="plugdev"

<<<

I have an old 2012 Asus Nexus 7. How can I get it to connect to wifi again? My goal is to use it as a digital photo frame, where the software for showing the slideshow of photos is a React app (website) that I've built. So all I need this tablet to be able to do is browse a website hosted on my LAN. (Ideally the browser ideally will support localStorage and IndexedDB.) Currently, I can't get the Nexus 7 to connect to my wifi. It has some custom limited version of Android 7.1.2 that I barely remember installing. Sometimes it can see my wifi networks and lets me enter its password, but then never lets me browse the internet. Sometimes the wifi is "Off", and when I try to turn it "On", it just hangs. My WiFi router is a NOKIA BGW320-505 (AT&T fiber) with WPA-2, WPA-3, and B/G/N/AX. NOKIA BGW320-505 gives me 3 options in the dropdown for WPA Version: "WPA-1 and WPA-2", "WPA-2", "WPA-2 and WPA-3". It has been on "WPA-2 and WPA-3", and I'd love to keep it there. I temporarily changed it to WPA-2, and even then the Nexus won't connect. I've already tried a factory reset of the Nexus. What are my options for solving this? I'd be up for installing a new OS on the Nexus if there is a high chance of achieving my goal.

I am trying run xgoldmon utility with my old Samsung Galaxy Nexus. I follow instructions provided in README file. > The Galaxy Nexus has to be rooted first to activate diag mode! Then: > - In the adb shell, as root, enter: echo MODEM > /sys/devices/tuna_otg/usb_sel > - Connect to the first of the serial devices (e.g. /dev/ttyACM0) with a terminal emulator and enter AT+TRACE=1 I tryied with several factory images for Samsung Galaxy Nexus ("yakju" for Galaxy Nexus "maguro" (GSM/HSPA+)) from the Google site . I flashed Android 4.0.4 (IMM76I), rooted phone via TWRP installng SuperSU , connected to the phone via running adb shell and run echo MODEM > /sys/devices/tuna_otg/usb_sel Phone became disconnected and I did not see ttyACM* devices in /dev directory to enter AT commands. Also I could not connect with the adb tool. When I did echo NONE > /sys/devices/tuna_otg/usb_sel I could connect to my phone with adb tool. I tried the same things with 4.3 (JWR66Y) and got the same result. There are several hardware versions of Samsung Galaxy Nexus, I suppose, but not sure, that I have a version that did not allow to work with modem diagnostic mode. Can somebody say what I am doing wrong? And is there any solution to my problem?

I'm trying to extract the source audio from a podcast so I don't constantly have to go to the website and find the exact point I was at. It is directly from a web player which is embedded on a webpage that I visit. As far as I'm aware it's not possible with any extensions because they are not compatible with the chrome browser on android (which I am using on my Nexus 5X). Has anyone been successful in downloading an MP3 file from a webpage using their Android phone? If any clarification is needed please let me know in the comments. Thanks!

I have an **Iodine** (DNS Tunneling) server running on my VPS and have tested and confirmed DNS Tunneling is working by connecting using the Iodine client from my local Linux machine. When using the **Andiodine** app (https://f-droid.org/packages/org.xapek.andiodine/) on Android however, it connects but i have no internet connectivity. I've done extensive searching and am unable to work out what the issue is.
My Android device is a Nexus 5 running Android version 6.0.1.
Has anyone else experienced this issue? Any remediations or other things to try?

My sister's Nexus 5X won't turn on. It is charged. When you try to power on, it makes it to the Google animation but freezes and goes back to black. You can make it to the debug menu go through the options, but when you choose Start it does the same thing. We've tried the Google Support suggestions, and nothing is working.

Update: I don't know what I did differently apart from factory resetting it a lot of times, but it finally went through and unlocked. --- I'm trying to unlock the bootloader on my Nexus 7 2013 WiFi 32GB (flo). I turned it off, pressed power button + volume down, which soon greeted me with "the bootloader". I then ran fastboot oem unlock which prompted the tablet to ask me whether I really want to unlock the bootloader, and I subsequently navigated to yes using the volume keys and confirmed with the power button. Following that, this was printed to my computer's terminal: (bootloader) Unlocking bootloader... (bootloader) erasing userdata... (bootloader) erasing userdata done FAILED () Finished. Total time: 17.372s As you can see, it only says FAILED (). No error code. Looking at photos of others unlocking the bootloader, it seems that the next step should be erasing cache, however it evidently does not progress there. I can still boot into Android though. First boot initially greeted me with an "erasing" screen which had an Android on it, and all user data was erased (as expected). I did try repeating the procedure once more after letting it boot Android again but the result was the same. Other things I have tried are manually formating the userdata and cache partitions via the recovery menu and factory-resetting from within Android, however neither of these were fruitful. I have tried 2 different computers and 2 different USB cables but they yielded the same results. How might I go about resolving this so that I can unlock the bootloader?

I was trying to do [flash factory image](https://developers.google.com/android/images#instructions) on [angler](https://developers.google.com/android/images#angler) on my Nexus 6P. There is some No space left on device error: ./flash-all.sh # added set -x to script + fastboot flash bootloader bootloader-angler-angler-03.68.img target reported max download size of 494927872 bytes sending 'bootloader' (3544 KB)... OKAY [ 0.127s] writing 'bootloader'... OKAY [ 0.208s] finished. total time: 0.335s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.073s + sleep 5 + fastboot flash radio radio-angler-angler-03.81.img target reported max download size of 494927872 bytes sending 'radio' (48728 KB)... OKAY [ 1.283s] writing 'radio'... OKAY [ 2.174s] finished. total time: 3.457s + fastboot reboot-bootloader rebooting into bootloader... OKAY [ 0.022s] finished. total time: 0.072s + sleep 5 + fastboot -w update image-angler-n2g48c.zip extracting android-info.txt (0 MB)... extracting boot.img (12 MB)... target reported max download size of 494927872 bytes archive does not contain 'boot.sig' archive does not contain 'dtbo.img' archive does not contain 'dt.img' extracting recovery.img (17 MB)... archive does not contain 'recovery.sig' extracting system.img (2727 MB)... W/ziparchive(66399): Zip: unable to allocate 2860210996 bytes at offset 0 : \ No space left on device failed to extract 'system.img': I/O error (space inserted by myself for better readability) I suppose this is lacking space on the phone. shell@angler: $ df -h Filesystem Size Used Available Use% Mounted on tmpfs 1.4G 484.0K 1.4G 0% /dev tmpfs 1.4G 0 1.4G 0% /mnt /dev/block/dm-0 3.0G 1.8G 1.1G 62% /system /dev/block/dm-1 196.6M 184.7M 8.0M 96% /vendor /dev/block/platform/soc.0/f9824900.sdhci/by-name/cache 92.9M 1.8M 88.0M 2% /cache /dev/block/platform/soc.0/f9824900.sdhci/by-name/persist 3.9M 740.0K 3.0M 20% /persist /dev/block/platform/soc.0/f9824900.sdhci/by-name/modem 80.0M 47.5M 32.4M 59% /firmware tmpfs 1.4G 0 1.4G 0% /storage /dev/block/dm-2 53.5G 132.9M 52.9G 0% /data df: /mnt/runtime/default/emulated: Permission denied /data/media 53.5G 132.9M 52.9G 0% /storage/emulated Using fastboot version 1:8.1.0+r23-5 from Debian, Android is angler:8.1.0. Any idea what could be the problem? Searching in the sources, it fails in static void* unzip_file(ZipArchiveHandle zip, const char* entry_name, int64_t* sz) int error = ExtractToMemory(zip, &zip_entry, data, zip_entry.uncompressed_length); if (error != 0) { fprintf(stderr, "failed to extract '%s': %s\n", entry_name, ErrorCodeString(error)); free(data); return 0; } https://android.googlesource.com/platform/system/core/+/android-8.1.0_r73/fastboot/fastboot.cpp#505 or in static int unzip_to_file(ZipArchiveHandle zip, const char* entry_name) int error = ExtractEntryToFile(zip, &zip_entry, fd); if (error != 0) { fprintf(stderr, "failed to extract '%s': %s\n", entry_name, ErrorCodeString(error)); return -1; } https://android.googlesource.com/platform/system/core/+/android-8.1.0_r73/fastboot/fastboot.cpp#628 **UPDATE**: it looks like it's really lack of space on the laptop. Previously I had about 8GB, which I considered enough. After clear to have 17GB and trying to update different image image-angler-nmf26f.zip I got different error (probably related /tmp being tmpfs): strace -o strace.log fastboot -w update image-angler-nmf26f.zip extracting android-info.txt (0 MB)... extracting boot.img (12 MB)... target reported max download size of 494927872 bytes archive does not contain 'boot.sig' archive does not contain 'dtbo.img' archive does not contain 'dt.img' extracting recovery.img (17 MB)... archive does not contain 'recovery.sig' extracting system.img (2691 MB)... archive does not contain 'system.sig' archive does not contain 'vbmeta.img' extracting vendor.img (194 MB)... W/ziparchive(109113): Zip: unable to allocate 204079852 bytes at offset 0 : No space left on device failed to extract 'vendor.img': I/O error wiping userdata... Couldn't parse erase-block-size '0x'. Couldn't parse logical-block-size '0x'. mke2fs 1.45.5 (07-Jan-2020) /tmp/TemporaryFile-xaoMGH: Unimplemented ext2 library function while setting up superblock /usr/lib/android-sdk/platform-tools/mke2fs failed with status 1 mke2fs failed: 1 error: Cannot generate image for userdata

I have the 10gb hotspot plan for tmobile but I also have unlimited data when I'm on my phone. Is there a way to bypass the hotspot limit by using the unlimited data from my phone instead? I have the nexus 6 on android version 6.

Few days ago I started my Nexus 9 and it didn't manage to load. It started looping. The loop goes like this: The four colored dots circling around and then loops again - 5-6 times then it shuts down. I haven't done anything with it - it's unrooted, original firmware, used it normally since the day I bought it (have it for about 5 years). I tried anything I knew: -factory settings, -wiped cache, -flashed original (newest firmware), -flashed earlier versions, -flashed original HTC firmware, -sideloaded newest firmware, -sideloaded an earlier version. Every procedure ended with a success, but the result was always the same - four colored dots circling around and then loop again ... Any suggestions (besides "get a new tablet")?

My Nexus 5 running on Marshmallow and it has Last ota security update provided by Google at the time of end of support. I’ve a perfectly working SIM card. Using this sim card to make calls from nexus 5, but before the call gets placed the mobile signal drops to zero. When the call is disconnected the signal resumes back to normal. I tried soft reset, hard reset and airplane mode on/off. But nothing works. Any help would be appreciated.

I have a Google Nexus 6P with Copperhead OS installed on it. I forgot the pattern to unlock the screen. Is there any way I can recover (a part) of the data on my phone? I am pretty sure that the answer is going to be "no way", but I just want to ask to make sure, before I wipe the phone. I DO have a fingerprint in the phone, which works. Unfortunately - for some security reason - it wants the pattern as well. Maybe I can add, that I *kind of* remember the swipe pattern. I am sure about a middle part, but not about the beginning and the end. Unfortutely I have tried so many combinations by now (even keeping a book), that I have to wait 240 seconds now until I am allowed to enter the next try. (First I had to wait 20, then 30, 60, 120 seconds, now 240.) I had about 55 tries by now.

I have a nexus 5X phone, which needs a factory reset to fix it's infinite boot loop. The problem is that the bootloader says DEVICE STATE - locked. Is it possible to fix this?

I have a Nexus 5x that has an unresponsive and broken display (screen displays colored lines and doesn't respond to any touches) that I am trying to get files off of. I can't seem to get my computer to recognize it, presumably because you need the phone to be unlocked, but i cant get through the lock screen without touching the display. Is there any way to unlock my screen through recovery mode or something without wiping it? Thanks!

What I've tried: uninstall the app (Black Pocket) and restart. Also tried: Google. All search results tell me how to hide the status bar, which is not what I want. Obviously like most users I want to see all the battery and connectivity icons when I press the power button, then the Home button. Using Nova and System UI on Android 8.1.0 on a Nexus 6P - as if this would have anything to do with it, when I saw the status bar go transparent and auto-hide upon install of the app...

I was on my Nexus 5. I hadn't updated google apps for a long time. Then one day, i thought "why not update hangouts" so I tried to get it through google play. Google Play updated itself. Then updating the rest was a bad mistake. It froze and now won't boot. I used these instructions: https://gist.github.com/deloz/6a9663ca7052fc4acf9c but for hammerhead m4b30z and could back to stock. But everytime I try to update google apps through wifi, it dies and won't work. I thought I could just live with un-updated google apps, but now, every few days, my phone just freezes up. Any suggestions would be helpful?

> In recovery, perform a full factory reset, wipe cache, dalvik cache > and wipe data/factory reset. (source: https://www.naldotech.com/how-to-install-custom-roms-on-nexus-6p-with-custom-recovery/) But in my Android Recovery I can only see following options: - Apply update from ADB (or SD card) - Wipe data/factory reset - Wipe cache partition - Mount /system - View recovery logs - Run graphics test No such thing as full factory reset, wipe cache, dalvik cache. There is also no "install" option. My Recovery screen says: Android Recovery, google/angler/angler, 8.1.0/OPM6. ...(long version), user/release-keys Prior to that I have installed custom recovery (TWRP) from Play Store. Perhaps TWRP should be installed differently?

I had deleted several files like from my Nexus 6P, I want to permanently erase all deleted files, how to do it? where are the deleted files stored?

I have a Nexus 9 running Android 7.1.1, and the home button, recent button, *all* notifications, and the top pull-down menu all stopped working. The home and recent buttons respond to being tapped in that the animation that indicates I tapped them runs (the gray circle expands out from the button), but nothing happens. I can open the top pull-down menu, but it always says that there are no notifications, and I can't pull the menu down further to expand the icons. I have about 15 GB out of about 30 GB available, and memory usage is listed at 1.6 GB out of 1.8 GB. I've tried restarting the device multiple times. If I remember correctly, I accidentally drained the battery before this happened, but I can't recall if the device was simply powered off. When I powered up the device, the PIN prompt buttons caused the device to vibrate, even though I had had previously had that setting turned off. I restarted the device, and that setting turned back off. Double-tapping to wake up the device doesn't work consistently. Any ideas?