Android Enthusiasts
Q&A for enthusiasts and power users of the Android operating system
Latest Questions
1
votes
0
answers
166
views
How to install GApps/Magisk any addon through the TWRP recovery to the Android Virtual Device based on Android 5.1.1 and the Nexus 10
I'm trying to install GApps/Magisk etc any addon through the TWRP recovery to the Android Virtual Device based on Android 5.1.1 and the Nexus 10. The first step that I have accomplished has been to boot the TWRP thanks to an hint found here : https://github.com/TeamWin/android_device_emulator_twrp/i...
I'm trying to install GApps/Magisk etc any addon through the TWRP recovery to the Android Virtual Device based on Android 5.1.1 and the Nexus 10. The first step that I have accomplished has been to boot the TWRP thanks to an hint found here :
https://github.com/TeamWin/android_device_emulator_twrp/issues/2
He suggested to use an older version of SDK Tools(24.4.1). With it I have booted TWRP 2.8.0.1 in android 5.1.1 armeabi-v7a for the tablet Nexus 10 :
$ /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator -verbose -avd Nexus_10_API_22 -
ramdisk /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/twrp-2.8.0.1-twrp.img -kernel /home/ziomario/
Scrivania/FILES/watch?v=LL4lLoMCvMY/goldfish_3.4_kernel -show-kernel -gpu off
emulator:Found AVD name 'Nexus_10_API_22'
emulator:Found AVD target architecture: arm
emulator:Looking for emulator-arm to emulate 'arm' CPU
emulator:Probing program: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm
emulator:return result: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm
emulator:Found target-specific emulator binary: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm
emulator:GPU emulation is disabled
emulator: Running :/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm
emulator: qemu backend: argv = "/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm"
emulator: qemu backend: argv = "-verbose"
emulator: qemu backend: argv = "-avd"
emulator: qemu backend: argv = "Nexus_10_API_22"
emulator: qemu backend: argv = "-ramdisk"
emulator: qemu backend: argv = "/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/twrp-2.8.0.1-twrp.img"
emulator: qemu backend: argv = "-kernel"
emulator: qemu backend: argv = "/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/goldfish_3.4_kernel"
emulator: qemu backend: argv = "-show-kernel"
emulator: qemu backend: argv = "-gpu"
emulator: qemu backend: argv = "off"
emulator: Concatenated backend parameters:
/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm -verbose -avd Nexus_10_API_22 -ramdisk /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/twrp-2.8.0.1-twrp.img -kernel /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/goldfish_3.4_kernel -show-kernel -gpu off
emulator: found ANDROID_SDK_ROOT: /home/ziomario/Android/Sdk/
emulator: Android virtual device file at: /home/ziomario/.android/avd/Nexus_10_API_22.ini
emulator: virtual device content at /home/ziomario/.android/avd/Nexus_10_API_22.avd
emulator: virtual device config file: /home/ziomario/.android/avd/Nexus_10_API_22.avd/config.ini
emulator: using core hw config path: /home/ziomario/.android/avd/Nexus_10_API_22.avd/hardware-qemu.ini
emulator: Found AVD target API level: 22
emulator: Read property file at /home/ziomario/Android/Sdk//system-images/android-22/google_apis/armeabi-v7a//build.prop
emulator: No boot.prop property file found.
emulator: found skin 'nexus_10' in directory: /home/ziomario/Android/Sdk/skins
emulator: autoconfig: -skin nexus_10
emulator: autoconfig: -skindir /home/ziomario/Android/Sdk/skins
emulator: keyset loaded from: /home/ziomario/.android/default.keyset
emulator: trying to load skin file '/home/ziomario/Android/Sdk/skins/nexus_10/layout'
emulator: Auto-detect: Kernel image requires legacy device naming scheme.
emulator: Auto-detect: Kernel does not support YAFFS2 partitions.
emulator: Using initial system image: /home/ziomario/Android/Sdk//system-images/android-22/google_apis/armeabi-v7a//system.img
emulator: autoconfig: -data /home/ziomario/.android/avd/Nexus_10_API_22.avd/userdata-qemu.img
emulator: autoconfig: -initdata /home/ziomario/.android/avd/Nexus_10_API_22.avd/userdata.img
emulator: autoconfig: -cache /home/ziomario/.android/avd/Nexus_10_API_22.avd/cache.img
emulator: autoconfig: -sdcard /home/ziomario/.android/avd/Nexus_10_API_22.avd/sdcard.img
emulator: Physical RAM size: 1907MB
emulator: GPU emulation is disabled
emulator: WARNING: CPU acceleration only works with x86/x86_64 system images.
Content of hardware configuration file:
hw.cpu.arch = arm
hw.cpu.model = cortex-a8
hw.ramSize = 1907
hw.screen = touch
hw.mainKeys = no
hw.trackBall = no
hw.keyboard = yes
hw.keyboard.lid = no
hw.keyboard.charmap = qwerty2
hw.dPad = no
hw.gsmModem = yes
hw.gps = yes
hw.battery = yes
hw.accelerometer = yes
hw.audioInput = yes
hw.audioOutput = yes
hw.sdCard = yes
hw.sdCard.path = /home/ziomario/.android/avd/Nexus_10_API_22.avd/sdcard.img
disk.cachePartition = yes
disk.cachePartition.path = /home/ziomario/.android/avd/Nexus_10_API_22.avd/cache.img
disk.cachePartition.size = 66m
hw.lcd.width = 1600
hw.lcd.height = 2560
hw.lcd.depth = 16
hw.lcd.density = 320
hw.lcd.backlight = yes
hw.gpu.enabled = no
hw.initialOrientation = landscape
hw.camera.back = none
hw.camera.front = none
vm.heapSize = 192
hw.sensors.proximity = no
hw.sensors.magnetic_field = yes
hw.sensors.orientation = yes
hw.sensors.temperature = yes
hw.useext4 = yes
kernel.path = /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/goldfish_3.4_kernel
kernel.parameters = androidboot.hardware=goldfish android.checkjni=1
kernel.newDeviceNaming = no
kernel.supportsYaffs2 = no
disk.ramdisk.path = /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/twrp-2.8.0.1-twrp.img
disk.systemPartition.initPath = /home/ziomario/Android/Sdk//system-images/android-22/google_apis/armeabi-v7a//system.img
disk.systemPartition.size = 1500m
disk.dataPartition.path = /home/ziomario/.android/avd/Nexus_10_API_22.avd/userdata-qemu.img
disk.dataPartition.size = 2g
avd.name = Nexus_10_API_22
.
QEMU options list:
emulator: argv = "/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm"
emulator: argv = "-show-kernel"
emulator: argv = "-android-hw"
emulator: argv = "/home/ziomario/.android/avd/Nexus_10_API_22.avd/hardware-qemu.ini"
Concatenated QEMU options:
/home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/./emulator64-arm -show-kernel -android-hw /home/ziomario/.android/avd/Nexus_10_API_22.avd/hardware-qemu.ini
failed to load image file '/home/ziomario/Android/Sdk/skins/nexus_10//port_back.webp'
emulator: ## WARNING: can't load part '' from skin
failed to load image file '/home/ziomario/Android/Sdk/skins/nexus_10//land_back.webp'
emulator: ## WARNING: can't load part '' from skin
emulator: ### WARNING: ignoring part location with unknown name 'portrait'
emulator: ### WARNING: ignoring part location with unknown name 'landscape'
emulator: Starting QEMU main loop
emulator: trying to find: /home/ziomario/Scrivania/FILES/watch?v=LL4lLoMCvMY/tools_r24.4.1/lib/ca-bundle.pem
emulator: registered 'boot-properties' qemud service
emulator: Using kernel serial device prefix: ttyS
emulator: Ramdisk image contains fstab.goldfish file
emulator: Found format of system partition: 'ext4'
emulator: Found format of userdata partition: 'ext4'
emulator: Found format of cache partition: 'ext4'
emulator: system partition format: ext4
emulator: Mapping 'system' partition image to /tmp/android-ziomario/emulator-s31jL5
emulator: nand_add_dev: system,size=0x5dc00000,file=/tmp/android-ziomario/emulator-s31jL5,initfile=/home/ziomario/Android/Sdk//system-images/android-22/google_apis/armeabi-v7a//system.img,pagesize=512,extrasize=0
emulator: userdata partition format: ext4
emulator: nand_add_dev: userdata,size=0x80000000,file=/home/ziomario/.android/avd/Nexus_10_API_22.avd/userdata-qemu.img,pagesize=512,extrasize=0
emulator: cache partition format: ext4
emulator: nand_add_dev: cache,size=0x4200000,file=/home/ziomario/.android/avd/Nexus_10_API_22.avd/cache.img,pagesize=512,extrasize=0
emulator: registered 'boot-properties' qemud service
emulator: Adding boot property: 'dalvik.vm.heapsize' = '192m'
emulator: Adding boot property: 'qemu.sf.lcd_density' = '320'
emulator: Adding boot property: 'qemu.hw.mainkeys' = '0'
emulator: Adding boot property: 'qemu.sf.fake_camera' = 'none'
emulator: Kernel parameters: qemu.gles=0 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish android.checkjni=1 ndns=1
emulator: autoconfig: -scale 0.471507
serial0 console
emulator: Forcing ro.adb.qemud to "0".
emulator: control console listening on port 5554, ADB on port 5555
emulator: sent '0012host:emulator:5555' to ADB server
emulator: android_hw_fingerprint_init: fingerprint qemud listen service initialized
emulator: Failed to parse .AndroidStudio preferences file usage.statistics.xml
emulator: Defaulting user crash-report opt-in to false
emulator: Skipping metrics reporting: No user opt-in.
emulator: UpdateChecker: skipped version check
Uncompressing Linux... done, booting the kernel.
goldfish_fb_get_pixel_format:170: display surface,pixel format:
bits/pixel: 16
bytes/pixel: 2
depth: 16
red: bits=5 mask=0xf800 shift=11 max=0x1f
green: bits=6 mask=0x7e0 shift=5 max=0x3f
blue: bits=5 mask=0x1f shift=0 max=0x1f
alpha: bits=0 mask=0x0 shift=0 max=0x0
Booting Linux on physical CPU 0
Initializing cgroup subsys cpu
Linux version 3.4.67-gd3ffcc7 (dees_troy@XPS12-Ubuntu) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #2 PREEMPT Thu Aug 14 16:20:36 CDT 2014
CPU: ARMv7 Processor [410fc080] revision 0 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Goldfish
Truncating RAM at 00000000-772fffff to -2f7fffff (vmalloc region overlap).
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 193040
Kernel command line: qemu.gles=0 qemu=1 console=ttyS0 android.qemud=ttyS1 androidboot.hardware=goldfish android.checkjni=1 ndns=1
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 760MB = 760MB total
Memory: 745824k/745824k available, 32416k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
.text : 0xc0008000 - 0xc0454578 (4402 kB)
.init : 0xc0455000 - 0xc047a000 ( 148 kB)
.data : 0xc047a000 - 0xc04b3808 ( 231 kB)
.bss : 0xc04b382c - 0xc05fdaf0 (1321 kB)
NR_IRQS:256
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
Console: colour dummy device 80x30
Calibrating delay loop... 1047.75 BogoMIPS (lpj=5238784)
pid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux: Initializing.
Mount-cache hash table entries: 512
Initializing cgroup subsys debug
Initializing cgroup subsys cpuacct
Initializing cgroup subsys freezer
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x368698 - 0x3686f0
NET: Registered protocol family 16
bio: create slab at 0
Switching to clocksource goldfish_timer
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP: reno registered
UDP hash table entries: 512 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 2976K
goldfish_new_pdev goldfish_interrupt_controller at ff000000 irq -1
goldfish_new_pdev goldfish_device_bus at ff001000 irq 1
goldfish_new_pdev goldfish_timer at ff003000 irq 3
goldfish_new_pdev goldfish_rtc at ff010000 irq 10
goldfish_new_pdev goldfish_tty at ff002000 irq 4
goldfish_new_pdev goldfish_tty at ff011000 irq 11
goldfish_new_pdev goldfish_tty at ff012000 irq 12
goldfish_new_pdev smc91x at ff013000 irq 13
goldfish_new_pdev goldfish_fb at ff014000 irq 14
goldfish_new_pdev goldfish_audio at ff004000 irq 15
goldfish_new_pdev goldfish_mmc at ff005000 irq 16
goldfish_new_pdev goldfish-battery at ff015000 irq 17
goldfish_new_pdev goldfish_events at ff016000 irq 18
goldfish_new_pdev goldfish_nand at ff017000 irq -1
goldfish_new_pdev qemu_pipe at ff018000 irq 19
goldfish_pdev_worker registered goldfish_interrupt_controller
goldfish_pdev_worker registered goldfish_device_bus
goldfish_pdev_worker registered goldfish_timer
goldfish_pdev_worker registered goldfish_rtc
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered goldfish_tty
goldfish_pdev_worker registered smc91x
goldfish_pdev_worker registered goldfish_fb
goldfish_pdev_worker registered goldfish_audio
goldfish_pdev_worker registered goldfish_mmc
goldfish_pdev_worker registered goldfish-battery
goldfish_pdev_worker registered goldfish_events
goldfish_pdev_worker registered goldfish_nand
goldfish_pdev_worker registered qemu_pipe
audit: initializing netlink socket (disabled)
type=2000 audit(0.350:1): initialized
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
fuse init (API version 7.18)
msgmni has been set to 1462
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
console [ttyS0] enabled
brd: module loaded
loop: module loaded
nbd: registered device at major 43
goldfish_audio_probe
goldfish nand dev0: size 5dc00000, page 512, extra 0, erase 0
goldfish nand dev1: size 80000000, page 512, extra 0, erase 0
goldfish nand dev2: size 4200000, page 512, extra 0, erase 0
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre
eth0: SMC91C11xFD (rev 1) at fe013000 IRQ 13 [nowait]
eth0: Ethernet addr: 52:54:00:12:34:56
mousedev: PS/2 mouse device common for all mice
*** events probe ***
events_probe() addr=0xfe016000 irq=18
events_probe() keymap=qwerty2
input: qwerty2 as /devices/virtual/input/input0
goldfish_rtc goldfish_rtc: rtc core: registered goldfish_rtc as rtc0
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-devel@redhat.com
ashmem: initialized
logger: created 256K log 'log_main'
logger: created 256K log 'log_events'
logger: created 256K log 'log_radio'
logger: created 256K log 'log_system'
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (11700 buckets, 46800 max)
ctnetlink v0.93: registering with nfnetlink.
NF_TPROXY: Transparent proxy support initialized, version 4.1.0
NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
xt_time: kernel timezone is -0000
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
TCP: cubic registered
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
8021q: 802.1Q VLAN Support v1.8
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 0
goldfish_rtc goldfish_rtc: setting system clock to 2024-08-21 19:34:03 UTC (1724268843)
Freeing init memory: 148K
mmc0: new SD card at address e118
mmcblk0: mmc0:e118 SU02G 512 MiB
mmcblk0:
type=1403 audit(1724268843.570:2): policy loaded auid=4294967295 ses=4294967295
SELinux: Loaded policy from /sepolicy
type=1404 audit(1724268843.580:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
init: /dev/hw_random not found
init: cannot open '/initlogo.rle'
eth0: link up
init: /dev/hw_random not found
init: Unable to open persistent property directory /data/property errno: 2
init: using deprecated syntax for specifying property 'ro.serialno', use ${name} instead
init: property 'ro.serialno' doesn't exist while expanding '$ro.serialno'
init: cannot expand '$ro.serialno' while writing to '/sys/class/android_usb/android0/iSerial'
EXT4-fs (mtdblock1): recovery complete
EXT4-fs (mtdblock1): mounted filesystem with ordered data mode. Opts:
EXT4-fs (mtdblock0): mounted filesystem with ordered data mode. Opts:
Now,let's say I want to install Magisk using the TWRP to the emulator, what should I do ? I imagine that I should save the Magisk file (or any other zipped adddon) inside the sd card...or ? How can I do this ?

mister_smith
(21 rep)
Aug 21, 2024, 09:03 PM
1
votes
1
answers
3238
views
Running MX Player on a Nexus 10 to access an ext4 USB Flash drive
How would I play an MP4 on a USB Flash drive connected to the Nexus 10? The drive was formatted with Ubuntu with `ext4` format. I have the MX Player but it does not see the USB Flash drive.
How would I play an MP4 on a USB Flash drive connected to the Nexus 10? The drive was formatted with Ubuntu with
ext4
format. I have the MX Player but it does not see the USB Flash drive.
H2ONaCl
(109 rep)
Aug 1, 2013, 10:30 AM
• Last activity: May 5, 2024, 09:07 AM
1
votes
1
answers
1450
views
How do I mount an external disk drive formatted in ext4 via USB Host?
I plugged a 2.5 inch 1Tb drive into a Nexus 10 and I cannot see it anywhere really. Something pops up in ES File Explorer, but I cannot access the drive. Do I have to root my device, or is there some other way? Would formatting it to a different filesystem help in any way (to access it for r/w)?
I plugged a 2.5 inch 1Tb drive into a Nexus 10 and I cannot see it anywhere really. Something pops up in ES File Explorer, but I cannot access the drive.
Do I have to root my device, or is there some other way? Would formatting it to a different filesystem help in any way (to access it for r/w)?
Fred
(11 rep)
Oct 16, 2014, 10:21 PM
• Last activity: Mar 31, 2022, 12:06 PM
4
votes
2
answers
2093
views
Blurry images in gallery
Had a nexus 10 for nearly a year now. Before 5.0 came out w/e version I was on, the extra large images that I had imported from my computer to my nexus would properly resolve and keep their quality when I zoomed in. Now Post-5.0 my large images are just a giant blurry mess. Any idea on how to fix th...
Had a nexus 10 for nearly a year now. Before 5.0 came out w/e version I was on, the extra large images that I had imported from my computer to my nexus would properly resolve and keep their quality when I zoomed in. Now Post-5.0 my large images are just a giant blurry mess.
Any idea on how to fix this?
Sneaky Devil
(41 rep)
Dec 26, 2014, 02:08 AM
• Last activity: Mar 3, 2022, 10:03 AM
0
votes
1
answers
1940
views
fastboot flash recovery img never completes
My Nexus 10 stopped booting. It shows an open padlock on startup and the Google text in the middle. So I figured my son unlocked the bootloader somehow after creatively following instructions he found on youtube. I then tried to proceed to installing a fresh rom. Saw that CM has the "Manta" roms. I...
My Nexus 10 stopped booting. It shows an open padlock on startup and the Google text in the middle. So I figured my son unlocked the bootloader somehow after creatively following instructions he found on youtube.
I then tried to proceed to installing a fresh rom. Saw that CM has the "Manta" roms.
I have handy the main rom: cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J6-manta.zip.
I found two recovery roms: twrp-2.8.7.0-manta.img and cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J6-manta-recovery.img.
I'm able to get fastboot to see my device, after doing the vol up+down / power thing. But then the command fastboot -w flash recovery cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J6-manta-recovery.img never completes.
Creating filesystem with parameters:
Size: 29783752704
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7271424
Block groups: 222
Reserved block group size: 1024
Created filesystem with 11/1818624 inodes and 158176/7271424 blocks
Creating filesystem with parameters:
Size: 553648128
Block size: 4096
Blocks per group: 32768
Inodes per group: 6768
Inode size: 256
Journal blocks: 2112
Label:
Blocks: 135168
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/33840 inodes and 4363/135168 blocks
sending 'recovery' (7860 KB)...
OKAY [ 0.932s]
writing 'recovery'...
That never finishes. The tablet shows, aside from the laying down Android picture and the info, a blue line: "FASTBOOT STATUS - flash:recovery". It never gets past this.
I tried this with both the recovery img files I found.
Anyone have any idea why my Nexus 10 can't seem to complete this fastboot recovery installation? I'm doing this using Xubuntu 15.04 btw, and I don't have Windows handy. I seriously hope it isn't a Linux limitation thing. adb has always worked great. Fastboot sees and interacts with the device, so, that part should be good I hope.
Mike
(139 rep)
Aug 29, 2016, 07:26 PM
• Last activity: Dec 26, 2021, 06:08 PM
0
votes
2
answers
1458
views
Nexus 10 - Android 5.0.1 OTA upgrade, "no command" and suggested steps failed
I was trying to install the OTA upgrade on my Nexus 10 running Lollipop 5.0.1. Got the "no command" problem. I tried the steps below from [this link](https://support.google.com/nexus/forum/AAAANseOu18WF6iOz7-XQY). > I suggest you try the following: > > Press and hold Power button until your device p...
I was trying to install the OTA upgrade on my Nexus 10 running Lollipop 5.0.1. Got the "no command" problem. I tried the steps below from [this link](https://support.google.com/nexus/forum/AAAANseOu18WF6iOz7-XQY) .
> I suggest you try the following:
>
> Press and hold Power button until your device powers off (it could take 30 seconds).
>
> 1. Press and hold Power and Volume Down buttons simultaneously until you see something other than Google on the screen.
> 2. You should see a large arrow at the top of the screen.
> 3. Tap Volume Down repeatedly until you see Recovery in the arrow. Then tap the Power button
> 4. You should see an android on his back, chest open with a red triangle and exclamation mark.
> 5. While holding Power button tap Volume Up once then release Power.
> 6. You should now see a list of items at top of screen.
> 7. Tap Power Down until the item to erase or wipe the cache partition is highlighted. Then tap Power button to initiate.
> 8. Status messages will appear at ths bottom of the screen. Be patient - it can take 10-15 minutes to complete. When done restart the Nexus.
>
> Wiping the cache partition does not impact any of your data, but it may take a while before your apps repopulate their cache values. During this time some may appear a bit slower than previously.
* I can't get past step 1, as when I do that, it keeps saying, "download in progress. do not close target ( or similar)".
* I tried the Power + Volume up + Volume down buttons, and get the menu, but don't see as below.
* I also tried Nexus Root Toolkit flash + restock, and that also shows "finished", but reboot goes back to "no command".
What to do?
OldProgrammer
(111 rep)
Aug 3, 2015, 05:09 PM
• Last activity: Dec 24, 2021, 07:01 PM
1
votes
0
answers
124
views
Accidentally wiped internal storage on Nexus 10 via TWRP now I can't turn on my tablet
I wanted to use TWRP to install an Android image but when I was deleting the already existing Android image files, I accidentally pressed "Internal Storage" and now when I try to operate my tablet, it does not turn on and when I put it on charge, it only gives me the battery charging icon. I also ca...
I wanted to use TWRP to install an Android image but when I was deleting the already existing Android image files, I accidentally pressed "Internal Storage" and now when I try to operate my tablet, it does not turn on and when I put it on charge, it only gives me the battery charging icon. I also can't access bootloader.
user334424
Dec 13, 2020, 01:18 AM
0
votes
1
answers
820
views
Error with rotation in Google Now Launcher
I have a Google Nexus 10, 16GB, with Android KitKat, v4.4.2. Yesterday I installed Google Now Launcher and when the launcher is rotated the wallpaper does not fit the screen properly in portrait mode. Here's the home screen when on landscape: [![Landscape][1]][2] Click image for larger version And h...
I have a Google Nexus 10, 16GB, with Android KitKat, v4.4.2. Yesterday I installed Google Now Launcher and when the launcher is rotated the wallpaper does not fit the screen properly in portrait mode.
Here's the home screen when on landscape:
Click image for larger version
And here's the home screen when on portrait mode:
Click image for larger version
I have tried setting the wallpaper while in portrait, but it still looks the same.
What could be the problem with this?
Thank you in advance.


Neko250
(1 rep)
Mar 26, 2014, 10:30 AM
• Last activity: Dec 8, 2020, 01:00 AM
2
votes
1
answers
1995
views
Adjust magnetic auto-lock sensitivity
I just bought a case for my Nexus 10 tablet ([EasyAcc Smart Cover][1]), but it seems the magnetic auto-lock sometimes thinks the cover is closed when the cover is flipped to the back side, behind the device. This especially happens when holding the tablet open in my hand, and it's easy to accidental...
I just bought a case for my Nexus 10 tablet (EasyAcc Smart Cover ), but it seems the magnetic auto-lock sometimes thinks the cover is closed when the cover is flipped to the back side, behind the device. This especially happens when holding the tablet open in my hand, and it's easy to accidentally adjust the position of the cover on the back.
Since this false positive condition doesn't always happen, I'm guessing a simple sensitivity change might be enough to make the auto-lock feature of the cover work proprely. Another possible fix could be to have some sort of delay, os that when the system detects the lid as "closed", it'd wait for a few secs to see if it stays in closed state, and only then put the device to sleep.
**Is there a way to adjust the magnetic auto-lock sensitivity?**
*(Nexus 10 tablet, running Android 4.2.2)*
Ilari Kajaste
(2226 rep)
Jun 3, 2013, 09:51 AM
• Last activity: Jun 1, 2020, 05:01 AM
1
votes
1
answers
2620
views
Nexus 10. The device cannot start. Code 10.
I had some problem with my Nexus 10. Died on me and then came back from the dead. Since then it refuses to connect to my PC. In the Device Manager I get "The device cannot start. Code 10." I have uninstalled/reinstalled the USB and ADB drivers to no avail. Even did a factory-reset to the tablet (was...
I had some problem with my Nexus 10. Died on me and then came back from the dead.
Since then it refuses to connect to my PC.
In the Device Manager I get "The device cannot start. Code 10."
I have uninstalled/reinstalled the USB and ADB drivers to no avail.
Even did a factory-reset to the tablet (was nothing real important on it).
I am totally stuck. I need to use it for development and it is totally useless to me like this.
theblitz
(161 rep)
Jun 2, 2015, 09:43 PM
• Last activity: May 24, 2020, 05:08 PM
2
votes
1
answers
1557
views
Nexus 10 cannot sign into Google Accounts
I have a brand new Nexus 10. It worked for a few minutes of web browsing and then I am not sure what I did but somehow it got to the point where I was asked to sign into a Google Account. Since I use `gmail`, the required answer to the question: `do you use Google Accounts?` is yes. So I touched 'ye...
I have a brand new Nexus 10. It worked for a few minutes of web browsing and then I am not sure what I did but somehow it got to the point where I was asked to sign into a Google Account. Since I use
gmail
, the required answer to the question: do you use Google Accounts?
is yes. So I touched 'yes'.
I put in my gmail address and password. Now it shows Couldn't sign in, Can't establish a reliable connection to the server.
There is the suggestion that it is a temporary problem but retries have failed over several days.
I then wiped all user data using instructions I found on the internet. However, it still ends up stuck on the screen that shows Couldn't sign in, Can't establish a reliable connection to the server.
I even logged out of gmail
on my laptop, but it doesn't help the situation on the Nexus 10. The Nexus 10 is a brick so now I am shopping for a few hundred thousand of these and some mortar.
Additional info: I use 2-step verification on the laptop for my gmail
.
H2ONaCl
(109 rep)
Jun 20, 2013, 09:57 AM
• Last activity: Apr 17, 2020, 09:43 AM
1
votes
2
answers
548
views
How to root a Nexus 10 without wipe?
I would like to root my Nexus 10 without wiping its data so I can later [install Ubuntu Touch][1] on it. How should I do this? [1]: https://wiki.ubuntu.com/Touch/DualBootInstallation
I would like to root my Nexus 10 without wiping its data so I can later install Ubuntu Touch on it. How should I do this?
Jules Bertholet
(111 rep)
May 10, 2015, 10:35 PM
• Last activity: Dec 20, 2016, 11:19 AM
0
votes
0
answers
24
views
AOSP nexus 10 android 7 nougat options?
I'm currently running an early AOSP build of android 6 on nexus 10. What are the aosp options for android 7? I'm not talking about a custom ROM like cyanogenmod. I mean one as close to AOSP as possible.
I'm currently running an early AOSP build of android 6 on nexus 10. What are the aosp options for android 7? I'm not talking about a custom ROM like cyanogenmod. I mean one as close to AOSP as possible.
Jan S
(111 rep)
Sep 20, 2016, 09:49 PM
• Last activity: Sep 21, 2016, 05:18 AM
0
votes
1
answers
145
views
Nexus 10 - Android 5.0.1 OTA upgrade, “no command” and suggested steps failed
I did rooting with Kingo root, and also i did factory reset. but i still can't use OTG When I press power+voldown, boot menu starts and immediately shows "Downloading... Do not turn of target!" then i tried Hold Power + Volume Up + Volume Down, and then i can see recovery mode, but it still not work...
I did rooting with Kingo root, and also i did factory reset. but i still can't use OTG
When I press power+voldown, boot menu starts and immediately shows "Downloading... Do not turn of target!"
then i tried Hold Power + Volume Up + Volume Down, and then i can see recovery mode, but it still not working - no command ...
I still see "System update download" , still failed.
what can i try more?
John Han
(1 rep)
Dec 31, 2015, 09:18 AM
• Last activity: Sep 20, 2016, 08:33 AM
0
votes
1
answers
131
views
I need to reinstall (OS? and gapps) after a part-wipe of internal memory of Manta, 5.1
After a failed change to CM13 ROM, my Nexus 10 booted to show only its screen still alive but with lots of green Androids (its name is..?) and unconnected icons. Inside are only 5 apps, no keyboard, no file manager, but there is 'Settings', 'Terminal IDE' and TWRP (2.3.3.0). I do have a usable USB k...
After a failed change to CM13 ROM, my Nexus 10 booted to show only its screen still alive but with lots of green Androids (its name is..?) and unconnected icons.
Inside are only 5 apps, no keyboard, no file manager, but there is 'Settings', 'Terminal IDE' and TWRP (2.3.3.0). I do have a usable USB keyboard, I'm pleased to say.
I can run TWRP in Recovery and can see into the device with Android File Transfer running on my iMac. TWRP shows 'cm-13.0......zip' and '...open_gapps...aroma...zip'. AFT shows 'twrp...img'. I can put a replacement stock Manta 5.1 .tgz on it via AFT, 'tho I can't remember if I need to 'un-tgz" it first.
In order to avoid a bricking, what is the safest option?
- Can I just install and run Aroma to replace the lost bits of the
Gapps?
- Should/Can I transfer the Android stock to the nexus and install
that?
- Be brave and install the Cyanogenmod 13 and Gapps?
Your help will be appreciated!
user138779
(21 rep)
Jul 2, 2016, 11:23 PM
• Last activity: Sep 19, 2016, 01:46 PM
0
votes
1
answers
654
views
Nexus 10 not booting, showing Google and lock icon when turned on
This is odd. My Nexus 10 has been working great a quite a while now, but now, suddenly, when I turn it on, its quickly shows a Google title in the middle, and a lock icon at the bottom (in landscape mode only). The lock looks like a padlock and it looks open (not fully closed). Nothing happens when...
This is odd. My Nexus 10 has been working great a quite a while now, but now, suddenly, when I turn it on, its quickly shows a Google title in the middle, and a lock icon at the bottom (in landscape mode only). The lock looks like a padlock and it looks open (not fully closed). Nothing happens when I wait. I can turn the tablet off by holding the power button for about 5 seconds. The tablet then stays off, until I press the power button for about 1 second. "Google" and the open padlock icon then reappears.
I've image-googled for anything about not booting and lock icons and whatnot, but I can't find anything that resembles this.
I've had an ipod touch years back and after my toddler tried to log in a few times, I lost access to it, and lost all my data. This made me not wanting to try Apple again. I seriously hope I'm not dealing with something like this here now again...
Mike
(139 rep)
Aug 22, 2016, 10:49 PM
• Last activity: Aug 23, 2016, 07:34 AM
1
votes
0
answers
100
views
Nexus 10 does not show stacktraces anymore
I have an Nexus 10 with Android 4.4.4 (Stock, no root). Today I noticed a strange behaviour: When an App crashes, the device doesn't show the Stacktrace in Logcat. I purposely implemented a Bug in an App (parseInt("A)") without any try/catch. If I execute this on Nexus 10 the App just freezes and sh...
I have an Nexus 10 with Android 4.4.4 (Stock, no root).
Today I noticed a strange behaviour: When an App crashes, the device doesn't show the Stacktrace in Logcat.
I purposely implemented a Bug in an App (parseInt("A)") without any try/catch. If I execute this on Nexus 10 the App just freezes and shows the "App isn't responding" Dialog
In Logcat it shows only one line:
Does anyone know how I can get my Stacktraces back?
I purposely implemented a Bug in an App (parseInt("A)") without any try/catch. If I execute this on Nexus 10 the App just freezes and shows the "App isn't responding" Dialog
In Logcat it shows only one line:
threadid=1: thread exiting with uncaught exception
.Does anyone know how I can get my Stacktraces back?
Thommy
(111 rep)
Aug 15, 2014, 01:17 PM
• Last activity: Jul 19, 2016, 08:02 PM
0
votes
1
answers
970
views
why wont my nexus 10 hold a charge?
I've had my Nexus 10 for a while and it's been great until recently and the battery now won't hold a charge. Whenever I unplug the charger it just turns off right away and when I plug in the charger that goes from 0 percent to a hundred percent in like 5 seconds
I've had my Nexus 10 for a while and it's been great until recently and the battery now won't hold a charge. Whenever I unplug the charger it just turns off right away and when I plug in the charger that goes from 0 percent to a hundred percent in like 5 seconds
daniel briscoe
(1 rep)
Nov 15, 2014, 05:32 PM
• Last activity: Apr 15, 2016, 08:33 AM
7
votes
5
answers
17135
views
Why is ART not available on Nexus 7 (2012) or Nexus 10 running Android 4.4?
I just updated my Nexus 7 to Android 4.4 KitKat and was looking forward to testing out ART, but that option isn't available. I got word that the Nexus 10 also lack this option, but I can't find any info as to why that is. Anybody have anything to share? Of course, they would need an AOT compiler for...
I just updated my Nexus 7 to Android 4.4 KitKat and was looking forward to testing out ART, but that option isn't available. I got word that the Nexus 10 also lack this option, but I can't find any info as to why that is.
Anybody have anything to share? Of course, they would need an AOT compiler for that platform, but how big of a difference is there between Nexus 7 and Nexus 4? They are both ARMv7, although Nexus 4 is A5-based and Nexus 7 is A9-based (according to my research). Why would that make a difference?
jishi
(171 rep)
Nov 14, 2013, 10:41 AM
• Last activity: Mar 2, 2016, 06:14 AM
0
votes
1
answers
49
views
Problems with drivers for Nexus 10 when building Android 4.3 from source
I followed the steps in the [Android Source][1] web page to download **android-4.3_r1** and build it for Nexus 10. **What is the problem?** - When I download and install the drivers for Nexus 10 for Android 4.3 (JWR66Y) form the [drivers web page][2], the device stucks at the Google logo. [1]: https...
I followed the steps in the Android Source web page to download **android-4.3_r1** and build it for Nexus 10.
**What is the problem?**
- When I download and install the drivers for Nexus 10 for Android 4.3 (JWR66Y) form the drivers web page , the device stucks at the Google logo.
User
(1 rep)
Jan 22, 2016, 11:37 PM
• Last activity: Jan 24, 2016, 08:06 PM
Showing page 1 of 20 total questions