No Google Play . Missing Acrobat - Remix OS for PC

Hi,
Google Play does not work for me on the latest Remix_OS_for_PC_Android_M_64bit_B2016082301.iso.
Having done the Play Activation update + Play Activation + Reboot, both Play and new Account protest about not being able to contact Google Servers, even though: 1.Internet connectivity is definitely present and 2. In Apps for Google Play and Google Play Services there is no cache to empty (a suggested remedy in other threads.)
The system is below (minus the touchscreen which was unplugged at the time of running the report).
Incidentally I am running remix via a grub entry:
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/install.img
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x$
initrd /remix/initrd.img
Remix works beautifully apart from this Play and Acrobat hiccup.
Best wishes
System: Host: localhost.localdomain Kernel: 4.6.2-1-MANJARO x86_64 (64 bit gcc: 6.1.1)
Desktop: Xfce 4.12.3 (Gtk 2.24.30) info: xfce4-panel dm: lightdm
Distro: Manjaro Linux
Machine: Mobo: ASRock model: Z87 Extreme4
Bios: American Megatrends v: P3.40 date: 04/12/2016
CPU: Dual core Intel Core i3-4130 (-HT-MCP-) cache: 3072 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 13604
clock speeds: min/max: 800/3400 MHz 1: 3400 MHz 2: 3399 MHz
3: 3401 MHz 4: 3399 MHz
Memory: Using dmidecode: you must be root to run dmidecode
Graphics: Card: Advanced Micro Devices [AMD/ATI] Turks XT [Radeon HD 6670/7670]
bus-ID: 01:00.0 chip-ID: 1002:6758
Display Server: X.Org 1.17.4 driver: fglrx
Resolution: [email protected]
GLX Renderer: AMD Radeon HD 6670
GLX Version: 4.5.13399 - CPC 15.201.1151 Direct Rendering: Yes
Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:8c20
Card-2 Advanced Micro Devices [AMD/ATI] Turks/Whistler HDMI Audio [Radeon HD 6000 Series]
driver: snd_hda_intel bus-ID: 01:00.1 chip-ID: 1002:aa90
Sound: Advanced Linux Sound Architecture v: k4.6.2-1-MANJARO
Network: Card: Intel Ethernet Connection I217-V
driver: e1000e v: 3.2.6-k port: f040
bus-ID: 00:19.0 chip-ID: 8086:153b
IF: enp0s25 state: up speed: 1000 Mbps duplex: full
mac: bc:5f:f4:c7:97:ee
WAN IP: 202.67.36.243
IF: enp0s25 ip-v4: 192.168.1.100 ip-v6: fe80::97f8:3170:7a5a:8f77
Drives: HDD Total Size: 3120.6GB (90.1% used)
ID-1: /dev/sda model: Corsair_Force_GT size: 120.0GB serial: 12147901000015020820
ID-2: /dev/sdb model: WDC_WD30EZRX size: 3000.6GB serial: WD-WMC1T2484449
Optical: /dev/sr0 model: TSST CDDVDW SH-224DB
rev: SB00 dev-links: cdrom
Features: speed: 48x multisession: yes
audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition: ID-1: / size: 39G used: 36G (95%) fs: ext4 dev: /dev/sda3
label: ROOT uuid: c550c05c-bfa9-4d19-ba16-0f6459eb7e93
ID-2: /boot size: 190M used: 42M (23%) fs: ext2 dev: /dev/sda1
label: BOOT uuid: 84060996-08ed-41da-be5c-e0c15a12544e
ID-3: /home size: 71G used: 63G (94%) fs: ext4 dev: /dev/sda4
label: HOME uuid: 56ca1278-38ec-43a7-a83e-7a247242efa7
ID-4: /media/esata/MEDIA size: 1.8T used: 1.7T (96%) fs: ext4 dev: /dev/sdb2
label: MEDIA uuid: f6232cfa-6daa-4d48-a378-9dde17c525f9
ID-5: /media/esata/SYSTEM size: 917G used: 863G (100%) fs: ext4 dev: /dev/sdb1
label: SYSTEM uuid: be0b8822-6339-4051-bbcf-021beb1cf6ff
ID-6: swap-1 size: 1.05GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
label: N/A uuid: cba5f6b8-ebd1-4350-85ae-6c2c844b2538
RAID: No RAID data: /proc/mdstat missing-is md_mod kernel module loaded?
Unmounted: No unmounted partitions detected
Sensors: System Temperatures: cpu: 44.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Weather: Conditions: F ( C) Wind: Calm
Pressure: in ( mb) Location: Altitude: ft
Time: August 27, 3:07 PM Observation Time: ,
Info: Processes: 287 Uptime: 1:30 Memory: 3230.4/7918.3MB
Init: systemd v: 231 Gcc sys: 6.1.1
Client: Shell (bash 4.3.421 running in xfce4-terminal) inxi: 2.3.0

Add a SERIAL=random to your grub.

HypoTurtle said:
Add a SERIAL=random to your grub.
Click to expand...
Click to collapse
Thanks.
I added that to the end of the kernel line. It seemed to have an effect in that when booting up because the optimize app process was displayed. I can't remember seeing that before.
However there was no change to the "can't contact google servers" when trying to create a gmail account.
I did another Activate Google Play and rebooted but still no change.
The Acrobat problem has gone away so I'll edit that out.
Two more problems were noticed.
1. When trying to print as PDF there was a "SAVE as PDF Jide" error.
2.Inability to access EXT4 drives.

Hi,
The "SERIAL=random" needs to be behind "quiet"
*after edit hit "enter" then "b" to boot
If done correctly /setting/tabled/status/serial
Will show a serial number...
About pdf... just try a different app
Goodluck

Hi, this is the modified grub entry:
Code:
menuentry 'Remix OS' --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/install.img
linux /remix/kernel quiet SERIAL=random root=/dev/ram0 androidboot.hardware=remix_x86_64 androidboot.selinux=permissive CMDLINE
initrd /remix/initrd.img
}
I reinstalled RemixOS, went through the activation and reboot, and still Play "can't contact Google servers".

Related

Android on Beagleboard-Xm

Hi all. I have compiled 0xdroid Gingerbread for beagleboard-xm following the official wiki.
the system stops during kernel boot
Here is my output:
Code:
reading boot.scr
462 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage
3502776 bytes read
reading uInitrd
173707 bytes read
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-2.6.38.6-g3298421-dirty
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3502712 Bytes = 3.3 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
Image Name: Android Ramdisk Image
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 173643 Bytes = 169.6 KiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
<5>Linux version 2.6.38.6-g3298421-dirty (sarasini-64bit)
(gcc version 4.5.4 20110505 (prerelease) (Linaro GCC 4.5-2011.05-0) )
#6 Mon Jan 2 21:02:10 CET 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: OMAP3 Beagle Board
<6>Reserving 33554432 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
<5>Truncating RAM at a0000000-bfffffff to -afffffff (vmalloc region
overlap).
<6>OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
<6>SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
No more output. all leds on the board are turned on. Any help?
thanks
Francesco
Repo Sync , Sync'd all projects for over 8 hrs on my 2mbps plan
This is the guide i took for reference and changed the repositories address to the one for beagleboard , using this command
Code:
repo init -u https://bitbucket.org/sola/android_manifest
Yet all 239 odd projects got downloaded , how to only download the beagleboard source files and not all aosp project on the main android source code git
Please clarify this (i know how to use -b option in repo sync to take only branches of a project from the manifest i point it to)
repo should only download files from bitbucket.org and not all android sources files correct?

[Q] partition errors - CyberNav tablet

I'm looking for some experienced eyes to scan through the partition info of a CyberNav tablet that I've mucked up by being very stupid. The CyberNav is a cheap Chinese GPS/Android tablet. It works great, or rather worked great until I very stupidly left it attached to my computer after downloading a track of my latest dirtbiking exploits. Later that evening I decided to make another Ubuntu USB startup disk... well, you can guess the rest.
At this point, the tablet will not mount the internal "sdcard" memory. It still boots, everything works, not bricked yet. When connected to USB, it will share out this external storage just fine. It just won't mount it within Android. It reports "Preparing memory device, checking for errors." Never gets past that point. I do have a backup of the original internal sdcard contents (made that when I first got the device) and anything that was important to me. Yes, I make backups, been burned too many times. I've also managed to find a factory ROM for it and I've successfully flashed that to the device. It made no difference with the problem. I've also got a root prompt via ADB shell using psneuter.
I have a copy of parted and gdisk, though I've not tried to run them yet. In other words, it's time to start figuring out what to fix in the partition tables.
I think the problem is here:
# busybox fdisk -l /dev/block/mmcblk2p6
... Device Boot Start End Blocks Id System
/dev/block/mmcblk2p6p1 1 1017 3436381 5 Extended <<<<< HERE
/dev/block/mmcblk2p6p5 1 1017 3436379 b Win95 FAT32
Does that seem right? Am I in any danger of bricking this device if I blow away the mmcblk2p6p1 partition and/or the entire mmcblk2p6? How bad do things generally have to get in these partitions before the device bricks?
What is the best/safest way to remove this partition and if I have to blow the whole mmcblk2p6 partition away will I have to manually recreate it before rebooting?
Any advice appreciated,
David...
P.S. Here is all the hopefully relevant information I've so far managed to locate:
Cybernav Mini: CPU: IMAPX200 ARM11 800MHz, also known as YFPi08, now flashed to Android 2.2-104.
# cat /proc/partitions
Code:
major minor #blocks name
179 16 3878912 mmcblk2
179 17 4096 mmcblk2p1
179 18 8192 mmcblk2p2
179 19 153600 mmcblk2p3
179 20 1 mmcblk2p4
179 21 277760 mmcblk2p5
179 22 3435072 mmcblk2p6
# busybox fdisk -l /dev/block/mmcblk2
Code:
Disk /dev/block/mmcblk2: 3972 MB, 3972005888 bytes
1 heads, 16 sectors/track, 484864 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk2p1 9 520 4096 30 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk2p2 521 1544 8192 31 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk2p3 1545 20744 153600 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk2p4 20745 484864 3712960 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk2p5 20753 55472 277760 83 Linux
/dev/block/mmcblk2p6 55481 484864 3435072 b Win95 FAT32
# busybox fdisk -l /dev/block/mmcblk2p6
Code:
Disk /dev/block/mmcblk2p6: 3517 MB, 3517513728 bytes
109 heads, 62 sectors/track, 1016 cylinders
Units = cylinders of 6758 * 512 = 3460096 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk2p6p1 1 1017 3436381 5 Extended
/dev/block/mmcblk2p6p5 1 1017 3436379 b Win95 FAT32
# cat /proc/kmsg
Code:
...
<3>[ 2.295000] imapx200_iic imapx200_iic.0: iic thread TX_ABORT occur
<3>[ 2.295000] imapx200_iic imapx200_iic.0: source is 1
<3>[ 2.295000] imapx200_iic imapx200_iic.0: slave address is 1a
<4>[ 2.300000] mmc_request bus 2 cmd 5 error -110
<4>[ 2.300000] mmc_request bus 2 cmd 5 error -110
<4>[ 2.300000] set info,open device error -939392608
<4>[ 2.305000] mmc_request bus 2 cmd 5 error -110
<3>[ 2.305000] imapx200_iic imapx200_iic.0: iic thread TX_ABORT occur
<3>[ 2.305000] imapx200_iic imapx200_iic.0: source is 1
<3>[ 2.305000] imapx200_iic imapx200_iic.0: slave address is 1a
<4>[ 2.305000] mmc_request bus 2 cmd 5 error -110
<6>[ 2.330000] mmc2: new high speed SDHC card at address 0002
<6>[ 2.330000] mmcblk2: mmc2:0002 3.69 GiB
<6>[ 2.335000] mmcblk2: p1 p2 p3 p4 < p5 p6 >
<4>[ 2.400000] custom info start sector 8182
<4>[ 2.430000] i2c-imapx200 transfer timeout
...
<6>[ 4.095000] EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode
<6>[ 4.635000] EXT4-fs (mmcblk2p5): recovery complete
<6>[ 4.645000] EXT4-fs (mmcblk2p5): mounted filesystem with ordered data mode
...
<3>[ 26.285000] FAT: invalid media value (0xa5)
<6>[ 26.285000] VFS: Can't find a valid FAT filesystem on dev mmcblk2p6.
... x3 above spaced to end of log.
dmesg:
Code:
...
<6>[ 0.295000] Imap Framebuffer Driver Initialization OK!
<4>[ 0.340000] set info,open device error -939392608
<4>[ 0.440000] set info,open device error -939392608
<4>[ 0.540000] set info,open device error -939392608
<4>[ 0.640000] set info,open device error -939392608
<4>[ 0.740000] set info,open device error -939392608
<4>[ 0.845000] set info,open device error -939392608
<6>[ 0.925000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
...
<3>[ 96.180000] FAT: invalid media value (0xa5)
<6>[ 96.180000] VFS: Can't find a valid FAT filesystem on dev mmcblk2p6.
... x2 above
adding a little info
# /data/local/tmp/parted /dev/block/mmcblk2
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk2
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: SD (sd/mmc)
Disk /dev/block/mmcblk2: 3972MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 65.5kB 4260kB 4194kB primary
2 4260kB 12.6MB 8389kB primary
3 12.6MB 170MB 157MB primary ext4
4 170MB 3972MB 3802MB extended
5 170MB 454MB 284MB logical ext4
6 454MB 3972MB 3518MB logical
But,
# /data/local/tmp/parted /dev/block/mmcblk2p6
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk2p6
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Error: Can't have a partition outside the disk!
(parted)
Every command I try just reports: "Error: Can't have a partition outside the disk!"
Okay, Okay, I get it. No how do I get rid of said partition?
Back at: # /data/local/tmp/parted /dev/block/mmcblk2
(parted) check 6
check 6
Error: Could not detect file system.
(parted)
dare I go: rm 6
If I just reboot at that point, what are the odds of the bootloader just recreating this partition for me? Should I recreate the partition via parted first? Something like: mkpart logical fat32 454 3972 and then format it by Windows Computer via USB mode, or (man for parted says this is discouraged) mkpartfs logical fat32 454 3972 to let it format right away?
I guess what I'm really asking is: what are the odds of bricking it if I blow this partition away? Seem low, what with it not working properly now, but I figure I should at least make an attempt at asking before I suck it up and hit the button.
Anyone?
David...
fixed:
rm 6 and mkpartfs logical fat32 454 3972 then a reboot did the trick. I've copied all the data back and set the tablet back to where it was. All done
Only took 2 weeks of head-banging, trying to figure out the Android way. Not an easy thing, what with all the fragmentation, and it pushed my Linux skills to their limit as well. By the hour, this $100 tablet is now worth an order of magnitude more but those skills should be worth it, even if the tablet isn't.
David...

[Q] how to directly edit a ubifs system image

Hi,
I have searched the forums and still haven't found any useful information.
I've been trying to edit a ubifs image (system.img) for a generic mediatek tablet.
These are the many things I have tried:
1) Edit the boot.img so that ro.secure=0 etc to see if I can get root. Unfortunately selinux is enabled and I don't even have busybox on the system (something called toolbox)
2) Work out what nand flash is being used (in my case its - SanDisk SDTNRGAMA 64G 3.3V 8-bit). And emulate the nand by using nandsim on a linux computer, but it causes a segmentation fault:
Code:
sudo modprobe nanDsim id_bytes=0x45,0xde,0x94,0x93,0x76,0x50 cache_file=./test.img
Note - I have included a spelling mistake (nanDsim should be nandsim) because I dont' want anyone to just cut and paste this command - it causes a segmentation fault on Ubuntu and Debian and I have found that if you are running on an ssd system it will hard lock your pc! (You have been warned).
3) Use ubireader (github.com/jrspruitt/ubi_reader).
Code:
$ ubireader_display_info ./system.img
UBI File
---------------------
Min I/O: 16384
LEB Size: 4161536
PEB Size: 4194304
Total Block Count: 122
Data Block Count: 120
Layout Block Count: 2
Internal Volume Block Count: 0
Unknown Block Count: 0
First UBI PEB Number: 0
Image: 1101756791
---------------------
Image Sequence Num: 1101756791
Volume Name:system
PEB Range: 0 - 121
Volume: system
---------------------
Vol ID: 0
Name: system
Block Count: 120
Volume Record
---------------------
alignment: 1
crc: 3336263623
data_pad: 0
errors:
flags: autoresize
name: system
name_len: 6
padding:
rec_index: 0
reserved_pebs: 248
upd_marker: 0
vol_type: dynamic
but when I run 'ubireader_extract_files' I get all the files, but they are all corrupted.
I'm currently trying to use the information in the ubireader_display_info to create a blank ubifs image and using 'linux dd' to try and read the image that I have.
Has anyone got any tips on how to progress, your help and advice would be appreciated.

HHD/Ubuntu - Remix OS Stuck on Pulsing Logo

I have an old Inspiron 11z EEPC and i want to make it a kids friendly PC
The system is:
Processor: Intel® Celeron(R) CPU 743 @ 1.30GHz
Memory: 2GB
Graphics: Mobile Intel® GM45 Express Chipset x86/MMX/SSE2
HDD: 150GB
OS: Ubuntu 16.10 - 32bit
Following some online tutorials i downloaded the 32Bit installer (release_Remix_OS_for_PC_Android_M_32bit_B2016112201) and extracted some of the files in a root create folder on HDD.
In detail a created a “remix” and a “remix/data” in / folder.
Then extracted some files from the ISO and copied in “remix” folder (the files are initrd.img, kernel, ramdisk.img, system.img).
Then i modified grub using this entry:
Code:
menuentry "Remix OS" --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/kernel
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x86_32 androidboot.selinux=permissive DATA=/remix/data SRC=/remix
initrd /remix/initrd.img
}
Using grub I try to run Remix OS but it stall on pulsating logo
Any ideas?? i think it’s something related with the Grub script (i’m not an expert ubuntu user…. )
Thanks
Mars Spider said:
I have an old Inspiron 11z EEPC and i want to make it a kids friendly PC
The system is:
Processor: Intel® Celeron(R) CPU 743 @ 1.30GHz
Memory: 2GB
Graphics: Mobile Intel® GM45 Express Chipset x86/MMX/SSE2
HDD: 150GB
OS: Ubuntu 16.10 - 32bit
Following some online tutorials i downloaded the 32Bit installer (release_Remix_OS_for_PC_Android_M_32bit_B2016112201) and extracted some of the files in a root create folder on HDD.
In detail a created a “remix” and a “remix/data” in / folder.
Then extracted some files from the ISO and copied in “remix” folder (the files are initrd.img, kernel, ramdisk.img, system.img).
Then i modified grub using this entry:
Code:
menuentry "Remix OS" --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /remix/kernel
linux /remix/kernel root=/dev/ram0 androidboot.hardware=remix_x86_32 androidboot.selinux=permissive DATA=/remix/data SRC=/remix
initrd /remix/initrd.img
}
Using grub I try to run Remix OS but it stall on pulsating logo
Any ideas?? i think it’s something related with the Grub script (i’m not an expert ubuntu user…. )
Thanks
Click to expand...
Click to collapse
Try
Code:
[b]androidboot.hardware=remix_x86[/b][strike]_32[/strike]

Question couldn't host Android Automotive OS 11 in Raspberry Pi 4 Model B

Hi, I downloaded the img file from the provided link(https://images.snappautomotive.com/rpi/snapp_automotive_rpi4_32gb_20211119.img.zip), but after successfully flashing the image file to an SD card, the raspberry pi4 model b didn't boot up. It shows (attached are the images of shown error) :
Raspberry Pi 4 Model B - 8GB bootloader: 6efe41bd 2022/01/25
board: 003115 6485fcf2 e4:5f:01:ad:58:05 boot: mode SD 1 order f41 retry 0/1 restart 18/-1
SD: card detected 00035344534431323885fa236632a165 part: mbr [0x0c:00000800 0x83:00040800 0x83:00440800 0x83:00480800]
fw: start4.elf fixup4.dat
net: down ip: 0.0.0.0 sn: 0.0.0.0 gw: 0.0.0.0
tftp: 0.0.0.0 00:00:00:00:00:00
Trying partition: 6
type: 16 lba: 2048 oem: 'mkfs. fat' volume:
rsc 4 fat-sectors 256 c-count 65399 c-size 4
root dir cluster 1 sectors 32 entries 512 Read config.txt bytes 206 hnd 0x00000000
Read start4.elf bytes 2214880 hnd 0x00000000 Read fixup4.dat bytes 5433 hnd 0x00000000
Firmware: 4b4aff21f72c5b9ba39d83c7b0f8fa910a6ef99b Dec 15 2020 14:48:29
0x00d03115 0x00000000 0x0000003f
start4.elf: is not compatible This board requires newer software
Get the latest software from https://www.raspberrypi.com/software/
Help me solve the issue. What should I follow?
just add the polestar and volvo images for emulator in android auto

Categories

Resources