Android x86 7.1-r1 x64 on Dell XPS 12 9Q23

[Serhiy Silvertyuk]

Hello! 

Version  Android 7.1 64 bytes is not started on Dell XPS 12 9Q23. Appears "Detecting Android x86" - then reboot.... (((((  I try start all versions of 7.1 (RC1, RC2, R1) - but no one is not work.....  I try start in Live mode and install to hard drive - no result(((((

Android x86 6.0 64 bytes - working properly )))).  Any idieas?

[Pietro Muscio]

Can you try to run ubuntu live just to find out if the linux kernel start.

[Serhiy Silvertyuk]

Hello !

Before reboot appear message "[     36.203040] SysRq : Emergency  Remout R/O". This message appear only 0.1 second, then reboot. Normaly unable read this message.  I made video  record and  when stop video, I can read the message. What mean this message?

пятница, 9 февраля 2018 г., 15:16:49 UTC+2 пользователь Pietro Muscio написал:

[Quade Masters]

I'd boot a different version of Linux like Ubuntu off a memory stick then FSCK the drive Android is installed onto.  7.1 RC1 and RC2 will fail to boot if the drive is dirty from not being shut down properly.  I've already reported this a couple months ago. 

[Serhiy Silvertyuk]

Hello! Thank you! 

I try do it, but no result (((((( Still reboot (((((

воскресенье, 11 февраля 2018 г., 15:27:39 UTC+2 пользователь Quade Masters написал:

[Nuno Craveiro]

Does it boot in live mode? When you install do to hard drive, in the end of the installation process, when it asks you to reboot or to run Android X86, does it run normally? I hade the same symptom updating 6.0 r2 to 7.1. r1. The solution, in my case was to had parameter "androidboot.selinux=permissive" (with no "" quotation marks) to the GRUB. My system is a dual booting Xubuntu/android x86, and the custom GRUB was created trough Xubuntu.

[Serhiy Silvertyuk]

Hello! Thank you for your time! System has dual boot - Windows 10 and Android 6.0 - x64. I  created additional two partions - first fat 32 for UEFI (GRUB), second EXT4 for Android. Android 6.0 - working properly. 

But Android 7.1 is not booting in live mode. System rebooting, with message "[36.203040] SysRq : Emergency  Remount R/O"

Instalition process to HDD  finish normally, but after reboot , system start load Android, and reboot again with message "[36.203040] SysRq : Emergency  Remount R/O"

I have parameter in GRUB -    linux $kdir/kernel root=/dev/ram0 androidboot.selinux=permissive buildvariant=userdebug $src $@

понедельник, 12 февраля 2018 г., 16:10:08 UTC+2 пользователь Nuno Craveiro написал:

[Nuno Craveiro]

Take a look at this: https://groups.google.com/forum/#!topic/android-x86/ByRiRyX4-8E

I would also try to download a new iso and create a new bootable pen. You should also try the 32 bits iso to see if it boots live mode.

If you can install and run the 6.0 version, try to upgrade that version using the 7.1 r1, choosing your android partitions and not formating it when asked.

The GRUB parameters you refer are from de installer options or the parameters of the actual GRUB? Are you using Grub2Win? Are you sure that "androidboot.selinux=permissive" parameter exists in the GRUB you have installed?

sexta-feira, 9 de Fevereiro de 2018 às 10:51:38 UTC, Serhiy Silvertyuk escreveu:

[Serhiy Silvertyuk]

Hello! Thank yuo for your time!

I try upgrade my version 6.0  to version 7.1 (install and not format partion). I  have installed ExtToFsd in Windows and I can read Ext4 partion in Windows.  As result - now, on partion EXT4 I have two folders :

-android-6.0-r3

-android-7.1-r1

In grub.cfg I write only one entry

set timeout=5

menuentry 'Android-x86_64 7.1' --class android { 

        search --file --no-floppy --set=root /android-7.1-r1//kernel

        linux /android-7.1-r1/kernel root=/dev/ram0 buildvariant=userdebug androidboot.selinux=permissive DATA= quiet 

        initrd /android-7.1-r1/initrd.img 

} 

As result - nothing change.......Whet booting Android 7.1 - my system reebit  with message "[36.203040] SysRq : Emergency  Remount R/O"

понедельник, 12 февраля 2018 г., 18:33:41 UTC+2 пользователь Nuno Craveiro написал:

[Genx]

Btw there is double slash for detection of partition for kernel,may be a mistake while typing here .

[Serhiy Silvertyuk]

Thank you!

I removed slash - but still reboot.

пятница, 16 февраля 2018 г., 12:33:51 UTC+2 пользователь Genx написал:

[Serhiy Silvertyuk]

I try start Android Live in Debug mode. 

Messages before Reboot:

[     52.032395] init Starting sevice'gatekeeperd'.....

[     52.065217] binder : 2617:2617 transaction failed 29189/-22 size 0-0 line 3004

[     52.070130] sysrq: SysRq : Emergency Remount R/O

[     52.004363] Emergency Remount complette

[     52.352579] reboot: Restarting system with command 'recovery'

It's binder's problem. I cannot find avoiding binder issue .......

пʼятниця, 9 лютого 2018 р. 12:51:38 UTC+2 користувач Serhiy Silvertyuk написав:

[Nuno Craveiro]

sexta-feira, 9 de Fevereiro de 2018 às 10:51:38 UTC, Serhiy Silvertyuk escreveu:

Have you tryed de 32 bits iso?

Take a look to this: http://www.hallergard.com/Blog/Android-x86-7.1-rc1.html

Grub seems to have slightly diferent parameters. Perhaps it will welp you.

[Serhiy Silvertyuk]

Hello! 

Yes. I try start 32 bytes version,  but system reboot too. For example - my system reboot, when I try start Android 7.1 from USB Flash - in Live mode. For example, when I use this USB Flash on ASUS machine - Android 7.1 started normally..  As  I wrote upper, before reboot (it's loop reboot) , in DEBUG mode :

Messages before Reboot:

[     52.032395] init Starting sevice'gatekeeperd'.....

[     52.065217] binder : 2617:2617 transaction failed 29189/-22 size 0-0 line 3004

[     52.070130] sysrq: SysRq : Emergency Remount R/O

[     52.004363] Emergency Remount complette

[     52.352579] reboot: Restarting system with command 'recovery'

My system has:

- Intel i7 3517 - 1,9 Ghz

- 8 GB RAM 

- 256 GB SSD

- Video Intel HD Graphics 4000 (1920 X 1080)

пʼятниця, 16 лютого 2018 р. 17:15:33 UTC+2 користувач Nuno Craveiro написав:

[David G]

I found when I tried to install Android 7.1 on a GPT partition it would not boot.  The box did not see a bootable partition and went back to BIOS.

I finally deleted the entire partition table completely and created a DOS partition table and then GRUB created a bootable partition.  Note that deleting a partition table is not the same as deleting a partition.

I am guessing this is an issue with GRUB or the program that creates the GPT partition table.  I am not an expert on either though.  Note that if there is anything valuable on the Harddisk, messing with the partition tables will probably cause it to be lost.

On Friday, February 9, 2018 at 5:51:38 AM UTC-5, Serhiy Silvertyuk wrote:

[Serhiy Silvertyuk]

Hello! Thank you all!

This problem is not a partion, and  is not a GRUB.  For example: I download ISO image and create bootable usb stick (using Win 32 Disk Imager). I try start Android, using this  bootable usb stick, and on my machine (DELL XPS 12) - Android 7.1 is not started in LIVE mode, but using this bootable USB stick on ASUS 5550 - Android start and work properly. On DELL XPS 12 - have BINDER'S error , when I start Android in LIVE DEBUG mode , I can read messages:

[     52.032395] init Starting sevice'gatekeeperd'.....

[     52.065217] binder : 2617:2617 transaction failed 29189/-22 size 0-0 line 3004

[     52.070130] sysrq: SysRq : Emergency Remount R/O

[     52.004363] Emergency Remount complette

[     52.352579] reboot: Restarting system with command 'recovery'

 I cannot find avoiding binder issue ....... How avoiding binder's error? 

пʼятниця, 9 лютого 2018 р. 12:51:38 UTC+2 користувач Serhiy Silvertyuk написав:

Hello! 

[David G]

binder has something to do with the graphics subsystem.

You might want to look at what graphics card you have and if you have another graphics try that.  Perhaps Android doesn't have the right graphics driver.

[Serhiy Silvertyuk]

Thank you all!

Bug report

Android-x86-7.1 and Android-x86_64-7.1 is not booting due to  binder error on DELL XPS 12 9Q23

[     52.032395] init Starting sevice'gatekeeperd'.....

[     52.065217] binder : 2617:2617 transaction failed 29189/-22 size 0-0 line 3004

[     52.070130] sysrq: SysRq : Emergency Remount R/O

[     52.004363] Emergency Remount complette

[     52.352579] reboot: Restarting system with command 'recovery'

CPU     -        Mobile DualCore Intel Core i7-3517U, 2800 MHz (28 x 100)

Chipset -        Intel Panther Point QS77, Intel Ivy Bridge

RAM    -         8071 МБ  (DDR3 SDRAM)

Video -        Intel(R) HD Graphics 4000  (2112 МБ)

HDD-              SAMSUNG SSD PM851 mSATA 256GB  (256 ГБ, SATA-III)

Touchscreen   10 points touch

Keyboard        Integrated PS/2 Keyboard

Mouse        Cypress Trackpad

пʼятниця, 9 лютого 2018 р. 12:51:38 UTC+2 користувач Serhiy Silvertyuk написав:

Hello! 

[Chih-Wei Huang]

2018-02-18 2:51 GMT+08:00 Serhiy Silvertyuk <fencer...@gmail.com>:
> Thank you all!
>
> Bug report
> Android-x86-7.1 and Android-x86_64-7.1 is not booting due to binder error
> on DELL XPS 12 9Q23
>
> [ 52.032395] init Starting sevice'gatekeeperd'.....
> [ 52.065217] binder : 2617:2617 transaction failed 29189/-22 size 0-0
> line 3004
> [ 52.070130] sysrq: SysRq : Emergency Remount R/O
> [ 52.004363] Emergency Remount complette
> [ 52.352579] reboot: Restarting system with command 'recovery'
>
> CPU - Mobile DualCore Intel Core i7-3517U, 2800 MHz (28 x 100)
> Chipset - Intel Panther Point QS77, Intel Ivy Bridge

Please show the result of 'cat /proc/cpuinfo'

[Serhiy Silvertyuk]

Hello! Thank you! Result of cat proc/cpuinfo

u0_a27@x86_64:/ $ cu
/system/bin/sh: cu: not found
127|u0_a27@x86_64:/ $ su
127|root@x86_64:/ # cat proc/cpuinfo

processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz
stepping : 9
microcode : 0x15
cpu MHz : 896.062
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 4789.26
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 1
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz
stepping : 9
microcode : 0x15
cpu MHz : 1031.343
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 1
initial apicid : 1
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 4789.26
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz
stepping : 9
microcode : 0x15
cpu MHz : 1001.718
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 2
initial apicid : 2
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 4789.26
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 58
model name : Intel(R) Core(TM) i7-3517U CPU @ 1.90GHz
stepping : 9
microcode : 0x15
cpu MHz : 891.375
cache size : 4096 KB
physical id : 0
siblings : 4
core id : 1
cpu cores : 2
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt
bugs :
bogomips : 4789.26
clflush size : 64
cache_alignment : 64
address sizes : 36 bits physical, 48 bits virtual
power management:

root@x86_64:/ #