[ROM][AOSP][Full Android 6.0.1][v.1.3]

[pisicuta]

Flash boot image for native vpn support in nexus player marshmallow causes boot loops

Before anything thank you for Lollirock and now Marshmallow:good:. May you live long and prosper!

As you know, when using the native vpn in android 6 for nexus player, it attempts to connect but quickly fails showing "unsuccessful". I tried many times what you said in the thread, but only causes endless boot loops for me, after successful flash. Had to go back and restore rom with TWRP, no problem but still no vpn. Any ideas? I have seen that for some colleagues it worked. References:

Try this boot.img https://goo.gl/R1lUCc
it worked for me with built-in Android vpn.
If for you all ok, I will update the firmware in the next days. ( I will change only the boot.img that have inside a new kernel )

to install:
unrar the archive and extract the boot.img

fastboot flash boot boot.img
fastboot reboot
You must re-root with supersu last beta with TWRP recovery if you need root.

 

[zulu99]

Before anything thank you for Lollirock and now Marshmallow:good:. May you live long and prosper!

As you know, when using the native vpn in android 6 for nexus player, it attempts to connect but quickly fails showing "unsuccessful". I tried many times what you said in the thread, but only causes endless boot loops for me, after successful flash. Had to go back and restore rom with TWRP, no problem but still no vpn. Any ideas? I have seen that for some colleagues it worked. References:

Try this boot.img https://goo.gl/R1lUCc
it worked for me with built-in Android vpn.
If for you all ok, I will update the firmware in the next days. ( I will change only the boot.img that have inside a new kernel )

to install:
unrar the archive and extract the boot.img

fastboot flash boot boot.img
fastboot reboot
You must re-root with supersu last beta with TWRP recovery if you need root.

I installed the new boot.img for vpn without problems and also others users tested.
The boot.img for vpn is linked also in second post. There are no problems.

I think that your problem is that you installed supersu in the system partition. In this case you must flash again also system.img if you change the boot.img

In Android 6 we are using the last supersu beta that use system less root. If you have supersu in system partition and use a not patched android 6 boot img is normal that you have boot loop. The boot img must be patched automatically from last supersu beta.
Read about it in ChainFire thread.

To solve install boot for vpn, system and wipe data and install the last supersu beta from twrp as i suggest in first post.

 

[zulu99]

I am not referring to the security patches that were included in MMB29T, but the fix to the critical bug that plagued the nexus player for months described in that issue report. It took Google a long time to acknowledge it, but they finally confirmed a fix in reply 41 of that issue that was said to come out in an OTA early in January due to Google not releasing things over the holidays. Reply 55 confirmed that the latest build resolves the issue as well as this discussion on reddit which links to the exact code change. I can confirm that the latest v1.2 of this rom exhibits this video range issue simply by using google cast and it would greatly benefit from being updated with this change.

You have right thanks. I will update in short time.

 

[pisicuta]

I think that your problem is that you installed supersu in the system partition. In this case you must flash again also system.img if you change the boot.img
In Android 6 we are using the last supersu beta that use system less root. If you have supersu in system partition and use a not patched android 6 boot img is normal that you have boot loop. The boot img must be patched automatically from last supersu beta.
Read about it in ChainFire thread.

I think that you are right since for root I have used and older zip from Chainfire and not the latest beta. I will wait for you to update to the new 1.3 version of this ROM and then do a clean install of all.
You will include the vpn tweak in the new version, no?

 

[zulu99]

I think that you are right since for root I have used and older zip from Chainfire and not the latest beta. I will wait for you to update to the new 1.3 version of this ROM and then do a clean install of all.
You will include the vpn tweak in the new version, no?

yes

 

[shdware]

Can I use TWRP to dirty flash v1.3? My computer has problems with fastboot.

 

[zulu99]

New version 1.3 in first post

V.1.3
Based on Android 6.0.1 MMB29T
fix vpn
fix webcam in hangouts

P.S.
I like the update, better than before.

 

[pointdooly]

New version 1.3 in first post

V.1.3
Based on Android 6.0.1 MMB29T
fix vpn
fix webcam in hangouts

P.S.
I like the update, better than before.

zulu99, I like to ask you a question because you are "THE Pro",

Just wondering...

Is there any way we could load "Remix OS" to Nexus Player like this full android ROM?
They are even plan to release FREE OS package within few days(1/12/2016) for PC(Intel/AMD devices such as PC and Mac)
Related News on XDA : Jide Announce Multi-Window Android For PC and Mac

I love your Full Featured ROM, Android TV OS(overall interface wise, but still yours better for me) specially with this small/compact powerful hardware that I did not expect this much.

Remix OS seems great alternative Android based OS if we can load on Nexus Player for some people
like their Remix Mini Devices.

Again, just wondering and asking since you have the knowledgeable professional!

 

[dabanhfreak]

New version 1.3 in first post

V.1.3
Based on Android 6.0.1 MMB29T
fix vpn
fix webcam in hangouts

P.S.
I like the update, better than before.

thanks, I assume we update through fastboot as normal, without "fastboot -w"?

 

[zulu99]

zulu99, I like to ask you a question because you are "THE Pro",

Just wondering...

Is there any way we could load "Remix OS" to Nexus Player like this full android ROM?
They are even plan to release FREE OS package within few days(1/12/2016) for PC(Intel/AMD devices such as PC and Mac)
Related News on XDA : Jide Announce Multi-Window Android For PC and Mac

I love your Full Featured ROM, Android TV OS(overall interface wise, but still yours better for me) specially with this small/compact powerful hardware that I did not expect this much.

Remix OS seems great alternative Android based OS if we can load on Nexus Player for some people
like their Remix Mini Devices.

Again, just wondering and asking since you have the knowledgeable professional!

If i have to say the true, yesterday, before i made this new update for nexus player, i extracted some stuff from the remix os firmware for nexus 9.
I was playing a little bit...

We must see. I want see how it work on PC, if it have all base components of Android. How is different in the core from Android AOSP and expecially if it have the input part of Android standard. ( if it follow Google guidelines, that is very important for compatibility with apps and games in google play )

http://www.videomap.it/forum/viewtopic.php?f=4&t=1557&p=2969#p2969

I like the UI, but we must see also if all apps can adapt...

So many things, but my mind was already there yesterday.

JideAccount
JideAnalytics
JideFileManager
JideFileStatService
JideMultiWindow
JideNotes
Launcher3

remixos-res.apk

p.s.
Everyone, also now, can have android x86 Marshmallow on every PC, and also installed on a usb key. From vmware you can install in the usb key instead that on hard drive. So you can have a portable OS with everything already installed. And work also relatively well if your usb key is fast. BUt the nexus player firmware is better and you can have Netflix and drm apps that you can't have on not certified devices. The big problem is this. The problem is the Mafia inside Android, not development problems.

For this reason, now , i create firmwares only for certified devices. Otherwise you can't have all apps.

 

[sweets55]

I've flashed a lot of Roms but never flashed a Rom on my Nexus Player. If anyone can help me send me a pm and or if anyone has a video that could help. Thanks

 

[zulu99]

I've flashed a lot of Roms but never flashed a Rom on my Nexus Player. If anyone can help me send me a pm and or if anyone has a video that could help. Thanks

is like all others nexus devices and many others android devices.
adb reboot bootloader
and with fastboot you can do everything

you can go also in bootloader mode if you long press the only hardware button of the nexus player while you power on the device.

to navigate bootloader menu with the hardware button, one press to go down, long press to select. in case you want enter in TWRP recovery directly from bootloader mode..

when you are in TWRP recovery instead you need an usb mouse, so you need and usb otg cable to connect a regular usb mouse or an usb hub

 

[Jhdoubleoseven]

Should the microphone on the Player Remote work? If not, are there any plans to (or definite reasons why we can't) make it work? Thanks!

 

[scottfree1]

I know no one will know this one, but before I undo all my work and rollback to lollipop I thought I'd ask.

One of the things I use the nexus for is to run plex server, since they only make an android version of the client and not the server I use "linux deploy" to run a vm of debian jesse and run plex on that. A little out their but it worked.

So I decide to give marshmellow a try, backup the vm and config file install mm, reinstall linux deploy copy vm over import config, start vm and bam life is good debian running, plex running all is well

That is until I try and mount the network shares that hold my media files, then it all goes south. I've tried moving up (strech, sid version of debian) I've started from scratch with a new vm and no matter I still get VV so anyone know how/why marshmellow would/could f-with cifs in a debain vm?

mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

 

[Jhdoubleoseven]

I know no one will know this one, but before I undo all my work and rollback to lollipop I thought I'd ask.

One of the things I use the nexus for is to run plex server, since they only make an android version of the client and not the server I use "linux deploy" to run a vm of debian jesse and run plex on that. A little out their but it worked.

So I decide to give marshmellow a try, backup the vm and config file install mm, reinstall linux deploy copy vm over import config, start vm and bam life is good debian running, plex running all is well

That is until I try and mount the network shares that hold my media files, then it all goes south. I've tried moving up (strech, sid version of debian) I've started from scratch with a new vm and no matter I still get VV so anyone know how/why marshmellow would/could f-with cifs in a debain vm?

mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
mount error: cifs filesystem not supported by the system
mount error(19): No such device
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

The mount issue is on Debian? In that case I'd think you're missing a package in Debian. Don't ask here, ask around in the Debian communities first and eliminate the VM as the issue first. Good luck!

 

[scottfree1]

The mount issue is on Debian? In that case I'd think you're missing a package in Debian. Don't ask here, ask around in the Debian communities first and eliminate the VM as the issue first. Good luck!

I copied over the virtual machine that was working great in lollipop to the new marshmellow rom and now no cifs. From what I've seen mm has some changes in the security and I wondering if it might be blocking access to the network.

I've rooted/su'd but see some strange behavior there, ie in es file explorer when I turn on root explore su comes up, I grant access es seems to have root then turns it off saying "root check failed" I wonder if linux deploy is not actually getting root also?

(I've tried 3 "root check" utils and they all say rooted)

 

[zulu99]

I copied over the virtual machine that was working great in lollipop to the new marshmellow rom and now no cifs. From what I've seen mm has some changes in the security and I wondering if it might be blocking access to the network.

I've rooted/su'd but see some strange behavior there, ie in es file explorer when I turn on root explore su comes up, I grant access es seems to have root then turns it off saying "root check failed" I wonder if linux deploy is not actually getting root also?

(I've tried 3 "root check" utils and they all say rooted)

not all apps support well supersu system less, the su binary now is in different partition. You can request the update of the app to support this new root, or you can install supersu in system partition to see if this solve your problem. take a look in the Chainfire supersu android 6 thread....

I updated some time ago my server to support also the system less root, i not know if others developer are doing that.

if is a root problem.

p.s.
tested es file explorer pro
no problems with root
no problems mounting windows shared folders.

 

[scottfree1]

not all apps support well supersu system less, the su binary now are in different partition. You can request the update of the app to support this new root, or you can install supersu in system partition to see if this solve your problem. take a look in the Chainfire thread....

I updated my server to support also the system less root, i not know if others developer are doing that.

if is a root problem.

Thanks, I saw that there were multiple root options, I used fugu-mra58k-boot.zip not fugu-mra58k-boot-systemless.zip if that makes a difference?

 

[zulu99]

Thanks, I saw that there were multiple root options, I used fugu-mra58k-boot.zip not fugu-mra58k-boot-systemless.zip if that makes a difference?

sure, you don't have my kernel and ramdisk you have a complete different thing. you can't change the boot image without lose things, vpn, webcam, exfat and others things. you have stock boot image, that have inside stock kernel and stock ramdisk.

install my boot.img and use the last supersu beta to root. as i explain in first post. but i think that you must reinstall everything. boot and system with a wipe of user data

tested es file explorer pro
no problems with root
no problems mounting windows shared folders.

you can install also debian no root, wine and start windows apps this is an x86 device.

 

[scottfree1]

sure, you don't have my kernel and ramdisk you have a complete different thing. you can't change the boot image without lose things, vpn, webcam, exfat and others things.
install my boot.img and use the last supersu beta to root. as i explain in first post.

tested es file explorer pro
no problems with root
no problems mounting windows shared folders.

I had problems when I installed su with your boot image, half hour and ballz still spinning, and thought the correct setup was to use the boot image from the su page (seemed right since that setup booted right away) so my issue is to get your boot.img to work with su, I'll go back to your boot.

My procede was fastboot your boot/system fb -w to clear out system, reboot straight into twrp, install su beta from zip, reboot into system, and it sticks there at the spinning ballz, I am doing something wrong in that?