Just wanted to post a thanks for your work. It's wonderful to have some interest in this box early on by some competent people. Have a great one!
[Nexus Player Root][LMY47D][5.1.0] root-boot - 03|26|2015
- Thread starter bunchies
- Start date
So, rooting it for what as of now? What about future updates? Is the NP going to force us to update OTAs?
Sent from my OnePlus One via Tapatalk
Sent from my OnePlus One via Tapatalk
Until recovery yes, I'll update this as new OTAs come along
Gotcha. I guess I should have asked before. Will rooting erase everything? I'm reluctant to having to set it up every time a new update comes out and breaks root.
Sent from my OnePlus One via Tapatalk
Sent from my OnePlus One via Tapatalk
Rooting won't wipe everything
Updates would just remove it since the update would write over the /system partition
In case of any bootloops our downgrades you can refer to post #2
If something were to happen you can always extract than flash boot.img and system.img in fastboot manually from an OTA zip to fix anything, all user data and configuration is held in /data and untouched if you do it manually
Last edited:
:good: Could not get this method working without the notice of "manually do "adb root" then "adb remount" and remount" then it continued flawlessly!
Thanks for the info/update!
Thanks for the info/update!
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.
If we get LRX22C or anything after related to the 5.0.1 release than I'll look through the script again since I'll have to make another zip
root-boot.img
Hey I'm trying to root manually and I wanted to know if the root-boot.img file downloaded for LRX21V is the root.img needed for fastboot root. Thanks!
fandas
Hey I'm trying to root manually and I wanted to know if the root-boot.img file downloaded for LRX21V is the root.img needed for fastboot root. Thanks!
fandas
You use the .img to obtain insecure adb (root) to be able to push the su files to the device
It is flashed through fastboot
I tried booting the the root-boot.img file with fastboot boot root-boot.img, the hit adb shell and then su, and it said su: command not found. I assume that means that the root was unsuccessful? Is the file not correct? Using the LRX21V root-boot.img file on my OEM unlocked Nexus player.
root-boot.IMG give insecure adb so you would use the adb root command. The rest of the script pushes the SU binarys over adb shell after that giving you SU commands and superuser app
Out of interest will rooting prevent OTA updates from installing in the future? Or as mentioned earlier will it just remove root and still OTA Update successfully?
It would remove root since it would rewrite the entire /system directory so all su binarys would be removed and the OTA would go through just fine
The only way to stop an OTA is custom recovery
Thanks for the info - I used your bat script and it worked perfectly after future updates I guess I should head back here to install new boot image.
Using Ubuntu after a lot of crap got adb to work. (Sudo kill-server, sudo start-server) but now fastboot does nothing. With or without the sudo command. Fastboot devices just gives me a new line and any fastboot command leaves me waiting for device. Any help?
Hello,
I have not given my Nexus Player any love in a long time so I have not been active in the threads... I hear there is a 5.1 update rolling out and need clarity. Do those of us who did this original rooting method need to do anything in order to be prompted for the update? I would think since the root-boot method does not modify recovery that we would still see the update. Am I correct in my thought process?
cheers
I have not given my Nexus Player any love in a long time so I have not been active in the threads... I hear there is a 5.1 update rolling out and need clarity. Do those of us who did this original rooting method need to do anything in order to be prompted for the update? I would think since the root-boot method does not modify recovery that we would still see the update. Am I correct in my thought process?
cheers
Correct, 5.1 is rolled out and I'll end up pushing out an update to this thread for it and might convert this method into a program instead of a .bat file
This method puts SU binarys into the /system/* location and installs the superuser app
You will continue to be notified for updates and if you do take the update it will remove SU access because an update will wipe /system and reflash it with a new system.img from the update zip
I haven't yet seen the OTA update file for the Nexus Player, but if it is similar to the 5.1 OTA update files for the Nexus 5, 6 and 9, then even if you are prompted for the update, you will not be able to install it. The 5.0.1+ updates no longer verify file-by-file for the existing system image, they verify the entire partition. In other words, prior to 5.0.1 updates, you could add files to /system, and you would still be able to apply the OTA update (assuming you didn't modify any of the existing files). Starting with the 5.0.1 update, you cannot apply the OTA update if you have added any files (or otherwise modified anything in /system). And since root adds some files to /system, the OTA will fail.
The easiest way to update to 5.1 if you have anything modified is to reboot into the bootloader, and flash the 5.1 boot and system images (from the Google-provided factory image here) using fastboot. You will then need to get root again.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone