• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Nexus Player Root][LMY47D][5.1.0] root-boot - 03|26|2015

Search This thread

bunchies

Senior Member
Dec 30, 2012
2,014
1,942
Land of Ooo
I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!
Requires unlocked bootloader!
Based on SuperSU - v4.46 (the binary updates from within the app later on)


I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM


For current firmware:

For past firmware:

For past firmware:


crappy video but simple demonstration :good:​
How to install:
Download the zip depending on your Nexus Player's firmware than extract & run root-boot.bat (Other operating system support coming soon for the installer script) Made on windows 7

Follow and read the on screen instruction carefully

SU app and binarys gets installed to /system/* directory's, The insecure boot.img gets installed to be able to access root adb shell and install those binarys

The root-boot boot.img is temporarily booted once during this process on the first boot of installation, it does not flash the boot.img
The previous boot.img before the installation is restored after SU is installed

Thanks @Chainfire for Superuser

 
Last edited:

bunchies

Senior Member
Dec 30, 2012
2,014
1,942
Land of Ooo
Troubleshooting:
  • Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers


  • This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device


  • After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue


  • Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults
    (If you were to run the factory zip as an update than it would format everything)

  • I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
 
Last edited:

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,142
Ottawa/Gatineau, Canada
I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM



For current firmware:

Working well, Thank you, after semi-manually adapting for working from Linux Mint. :)

I don't have permission to do "adb logcat" or "adb shell logcat" anymore though, unless I restart adbd as root.
 
  • Like
Reactions: bunchies

ggrammer

Senior Member
Jan 24, 2010
151
25
Since running the script everything seems all good except for using voice search. Anybody else having issues where voice search just closes?

Update: Erased and manually flashed the V firmware as I was on M and now it appears to be working correctly, not sure if this is going to be a problem with people stuck on M for now but you may want to think of upgrading your fimware.
 
Last edited:

bunchies

Senior Member
Dec 30, 2012
2,014
1,942
Land of Ooo
  • Like
Reactions: eko3484

prstorero

Senior Member
Sep 12, 2011
2,321
1,051
Dallas
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.



________________________________________________________
root-boot: By Bunchies @xda
________________________________________________________

________________________________________________________
Power off/unplug the device, hold the power button while
plugging in the device until you see the google logo and
than let go to enter fastboot mode
________________________________________________________

________________________________________________________
Plugin the device to a PC using a usb cable
________________________________________________________










Press any key to continue . . .

















waiting for ADB
target reported max download size of 536870912 bytes
sending 'boot' (5424 KB)...
OKAY [ 1.357s]
writing 'boot'...
OKAY [ 1.515s]
finished. total time: 2.876s














rebooting...

finished. total time: 0.602s





When boot completes
and you see the launcher
Press any key to continue . . .


















* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
rm: /system/bin/install-recovery.sh: Read-only file system

mkdir failed for /system/app/SuperSU, Read-only file system
mkdir failed for /system/bin/.ext, Read-only file system
failed to copy 'SuperSU/SuperSU.apk' to '/system/app/SuperSU/': Is a directory
failed to copy 'x86/su' to '/system/xbin/su': Read-only file system
failed to copy 'x86/supolicy' to '/system/xbin/supolicy': Read-only file system
failed to copy 'x86/libsupol.so' to '/system/lib/libsupol.so': Read-only file sy
stem
failed to copy 'x86/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Re
ad-only file system
failed to copy 'x86/install-recovery.sh' to '/system/etc/install-recovery.sh': R
ead-only file system
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: system/xbin/su: No such file or directory
cp: /system/xbin/sugote-mksh: Read-only file system
ln: /system/bin/su: Read-only file system
ln: /system/bin/install-recovery.sh: File exists
rm: /system/bin/app_process: Read-only file system
ln: /system/bin/app_process: File exists
mv: rename /system/bin/app_process32 to /system/bin/app_process32_original: Read
-only file system
ln: /system/bin/app_process32: File exists
cp: /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/app/SuperSU: No such file or directory
Unable to chmod /system/app/SuperSU/SuperSU.apk: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/lib/libsupol.so: No such file or directory
Unable to chmod /system/bin/.ext: No such file or directory
Unable to chmod /system/bin/.ext/.su: No such file or directory
Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
Unable to chmod /system/xbin/daemonsu: No such file or directory
Unable to chmod /system/xbin/sugote: No such file or directory
Unable to chmod /system/xbin/sugote-mksh: No such file or directory
Unable to chmod /system/etc/install-recovery.sh: No such file or directory
Unable to chmod /system/xbin/supolicy: No such file or directory
Unable to chmod /system/bin/app_process32_original: No such file or directory
Unable to chmod /system/bin/app_process_init: No such file or directory
chcon: Could not label /system/xbin/su with u:eek:bject_r:system_file:s0: No such
file or directory
chcon: Could not label /system/bin/.ext/.su with u:eek:bject_r:system_file:s0: No
such file or directory
chcon: Could not label /system/lib/libsupol.so with u:eek:bject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/etc/init.d/99SuperSUDaemon with u:eek:bject_r:syste
m_file:s0: No such file or directory
chcon: Could not label /system/bin/sh with u:eek:bject_r:system_file:s0: Read-onl
y file system
chcon: Could not label /system/xbin/sugote with u:eek:bject_r:zygote_exec:s0: No
such file or directory
chcon: Could not label /system/xbin/supolicy with u:eek:bject_r:system_file:s0: N
o such file or directory
chcon: Could not label /system/xbin/sugote-mksh with u:eek:bject_r:system_file:s0:
No such file or directory
chcon: Could not label /system/bin/app_process32_original with u:eek:bject_r:zygot
e_exec:s0: No such file or directory
chcon: Could not label /system/bin/app_process_init with u:eek:bject_r:system_file
:s0: No such file or directory




















Finished, you can now exit the installer
Press any key to continue . . .


Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.
 
Last edited:
  • Like
Reactions: iamtek7 and toe451

bunchies

Senior Member
Dec 30, 2012
2,014
1,942
Land of Ooo
Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.

Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.

Glad to hear that!
 

prstorero

Senior Member
Sep 12, 2011
2,321
1,051
Dallas

The first time around I got into the bootloop so I had to start over. Second time and it worked :) now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.

Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently :p
 
Last edited:

bunchies

Senior Member
Dec 30, 2012
2,014
1,942
Land of Ooo
The first time around I got into the bootloop so I had to start over. Second time and it worked :) now it seems that I can't get apps to install through the adb install command. I'm mainly trying to get es file explorer and stick mount so I can use an external flash drive. Is it possible that the root method somehow nuked this functionality? I've already restarted the adb server numerous times, rebooted the player, turned debugging off and back on, etc. Even after all that it just sits after displaying the transfer rate and never finishes.

Edit: Nevermind. Looks like this issue also goes back to having to do adb root and adb remount. Gotta do it for everything apparently :p

Weird, windows 8?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 22
    I am not responsible for whatever may happen to you or your device when using this, Run this at your own risk!!
    Requires unlocked bootloader!
    Based on SuperSU - v4.46 (the binary updates from within the app later on)


    I put together root installer script that comes with SU-binary/App with a insecure boot.img, everything is done over adb shell since we don't have a recovery right now but i will be working on it and already booted CWM


    For current firmware:

    For past firmware:

    For past firmware:


    crappy video but simple demonstration :good:​
    How to install:
    Download the zip depending on your Nexus Player's firmware than extract & run root-boot.bat (Other operating system support coming soon for the installer script) Made on windows 7

    Follow and read the on screen instruction carefully

    SU app and binarys gets installed to /system/* directory's, The insecure boot.img gets installed to be able to access root adb shell and install those binarys

    The root-boot boot.img is temporarily booted once during this process on the first boot of installation, it does not flash the boot.img
    The previous boot.img before the installation is restored after SU is installed

    Thanks @Chainfire for Superuser

    4
    At risk of this being a silly question, why not just use the CF-Auto-Root for the Nexus Player, if you're just installing SuperSU...

    (That is not a criticism on your work, I saw this featured on the portal, as if the NP was just rooted... mine has always been rooted just fine?)
    4
    At risk of this being a silly question, why not just use the CF-Auto-Root for the Nexus Player, if you're just installing SuperSU...

    (That is not a criticism on your work, I saw this featured on the portal, as if the NP was just rooted... mine has always been rooted just fine?)

    Idk, I released this method when no development threads were available

    Not long after other methods started to appear. I'm basically keeping this updated because its here but if there was a root method before this one I wouldn't have posted this

    If that way is better than great
    2
    Troubleshooting:
    • Check to make sure your device gets picked up in adb before running the script - - - ADB Drivers


    • This tool uses an unlocked bootloader and i have not unlocked mine yet, does unlocking the bootloader wipe the device? - - - Yes unlocking the bootloader will wipe the device


    • After fastboot flashed the boot.img than rebooted to the home screen i continued the the script like the installation steps said but it returned "device not found" - - - As long as it shows transferring files a few seconds after than its fine, adb restarts at that moment which will than return "device not found" than it reconnects and transfers. if fastboot flashed than rebooted fine than adb shouldn't have an issue


    • Help! Something went wrong and im bootlooping but i dont want to loose all my saved data - - - Everything is fine, Download the factory zip from here for your android version than extract the zip and retrieve the system.img and copy it into a folder that contains adb/fastboot and boot your device into fastboot mode and do "fastboot flash system system.img" doing it this way wont wipe your "/data" partition leaving everything intact but will restore the system back to its defaults
      (If you were to run the factory zip as an update than it would format everything)

    • I installed SU with this method but cant use adb commands on my device - - - Go into "Settings>About" and click on "Build" 7 times very fast and it will enable "Developer options" in the settings menu, Go back to the settings menu and open developer options (You may need to reboot if it doesnt show up immediately) and enable the "USB debugging" option
    2
    Alright so I just got around to running the script, and none of the commands work after booting back up. There's a failure for every rmdir and mkdir command that's used, so the device doesn't get rooted. I tried doing a adb remount, but the device isn't allowing that.



    ________________________________________________________
    root-boot: By Bunchies @xda
    ________________________________________________________

    ________________________________________________________
    Power off/unplug the device, hold the power button while
    plugging in the device until you see the google logo and
    than let go to enter fastboot mode
    ________________________________________________________

    ________________________________________________________
    Plugin the device to a PC using a usb cable
    ________________________________________________________










    Press any key to continue . . .

















    waiting for ADB
    target reported max download size of 536870912 bytes
    sending 'boot' (5424 KB)...
    OKAY [ 1.357s]
    writing 'boot'...
    OKAY [ 1.515s]
    finished. total time: 2.876s














    rebooting...

    finished. total time: 0.602s





    When boot completes
    and you see the launcher
    Press any key to continue . . .


















    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    error: device not found

    error: device not found
    error: device not found
    error: device not found
    error: device not found
    error: device not found
    error: device not found
    rm: /system/bin/install-recovery.sh: Read-only file system

    mkdir failed for /system/app/SuperSU, Read-only file system
    mkdir failed for /system/bin/.ext, Read-only file system
    failed to copy 'SuperSU/SuperSU.apk' to '/system/app/SuperSU/': Is a directory
    failed to copy 'x86/su' to '/system/xbin/su': Read-only file system
    failed to copy 'x86/supolicy' to '/system/xbin/supolicy': Read-only file system
    failed to copy 'x86/libsupol.so' to '/system/lib/libsupol.so': Read-only file sy
    stem
    failed to copy 'x86/99SuperSUDaemon' to '/system/etc/init.d/99SuperSUDaemon': Re
    ad-only file system
    failed to copy 'x86/install-recovery.sh' to '/system/etc/install-recovery.sh': R
    ead-only file system
    cp: system/xbin/su: No such file or directory
    cp: system/xbin/su: No such file or directory
    cp: system/xbin/su: No such file or directory
    cp: /system/xbin/sugote-mksh: Read-only file system
    ln: /system/bin/su: Read-only file system
    ln: /system/bin/install-recovery.sh: File exists
    rm: /system/bin/app_process: Read-only file system
    ln: /system/bin/app_process: File exists
    mv: rename /system/bin/app_process32 to /system/bin/app_process32_original: Read
    -only file system
    ln: /system/bin/app_process32: File exists
    cp: /system/bin/app_process32_original: No such file or directory
    Unable to chmod /system/app/SuperSU: No such file or directory
    Unable to chmod /system/app/SuperSU/SuperSU.apk: No such file or directory
    Unable to chmod /system/xbin/su: No such file or directory
    Unable to chmod /system/lib/libsupol.so: No such file or directory
    Unable to chmod /system/bin/.ext: No such file or directory
    Unable to chmod /system/bin/.ext/.su: No such file or directory
    Unable to chmod /system/etc/init.d/99SuperSUDaemon: No such file or directory
    Unable to chmod /system/xbin/daemonsu: No such file or directory
    Unable to chmod /system/xbin/sugote: No such file or directory
    Unable to chmod /system/xbin/sugote-mksh: No such file or directory
    Unable to chmod /system/etc/install-recovery.sh: No such file or directory
    Unable to chmod /system/xbin/supolicy: No such file or directory
    Unable to chmod /system/bin/app_process32_original: No such file or directory
    Unable to chmod /system/bin/app_process_init: No such file or directory
    chcon: Could not label /system/xbin/su with u:eek:bject_r:system_file:s0: No such
    file or directory
    chcon: Could not label /system/bin/.ext/.su with u:eek:bject_r:system_file:s0: No
    such file or directory
    chcon: Could not label /system/lib/libsupol.so with u:eek:bject_r:system_file:s0:
    No such file or directory
    chcon: Could not label /system/etc/init.d/99SuperSUDaemon with u:eek:bject_r:syste
    m_file:s0: No such file or directory
    chcon: Could not label /system/bin/sh with u:eek:bject_r:system_file:s0: Read-onl
    y file system
    chcon: Could not label /system/xbin/sugote with u:eek:bject_r:zygote_exec:s0: No
    such file or directory
    chcon: Could not label /system/xbin/supolicy with u:eek:bject_r:system_file:s0: N
    o such file or directory
    chcon: Could not label /system/xbin/sugote-mksh with u:eek:bject_r:system_file:s0:
    No such file or directory
    chcon: Could not label /system/bin/app_process32_original with u:eek:bject_r:zygot
    e_exec:s0: No such file or directory
    chcon: Could not label /system/bin/app_process_init with u:eek:bject_r:system_file
    :s0: No such file or directory




















    Finished, you can now exit the installer
    Press any key to continue . . .


    Edit: Fixed it! I had to manually do "adb root" then "adb remount" and remount succeeded that time and I was able to run the rest of the script and saw all the file transfers.