The only part in this that will wipe data is unlocking the bootloader, so if it's still locked than yes it will wipe when you unlock it
[Nexus Player Root][LMY47D][5.1.0] root-boot - 03|26|2015
- Thread starter bunchies
- Start date
Good stuff I'm unlocked rooted and running unleashed kernel. I imagine the kernel will no longer exist and will be incompatible until updated.
Sent from my Nexus 6
---------- Post added at 01:13 AM ---------- Previous post was at 01:12 AM ----------
So technically I could use flashify to flash the 5.1 boot.img?
Sent from my Nexus 6
Hi Bunchies,
Do you have plans to update the root-boot option using the new LMY47D?
Cheers
Do you have plans to update the root-boot option using the new LMY47D?
Cheers
Yeup, I've been gone for 2 weeks and I get home tomorrow
I'll consider converting everything to an executable instead of a script but we will see how that idea goes since it would take more time to do
Flashify is fine to flash kernels, But if you are unlocked and decide to root with this method the boot image included is temporarily booted for one boot to add the su binarys than restores the old boot on the 2nd boot
So your custom kernel should stick through the root process
Hello,
The current process is easy enough plus you would have to change up the instructions?. Would you suggest all to flash the entire image posted on Google, probably some needed firmware bits? I see many are just flashing each partition and not the entire update. I realize in hopes of saving data but is this the best option? Unlocking the bootloader wipes it anyway correct? In the old days it wasn't always necessary to update the bootloader but now it seems more important.
Your thoughts?
Sent from my HTC6525LVW using Tapatalk
5.1.0 root-boot out :good: using the latest binarys/app also
I did not make an executable for this release like i wanted to but u may in the future so we remain .bat for now, we will see though.
Updated OP's
I did not make an executable for this release like i wanted to but u may in the future so we remain .bat for now, we will see though.
Updated OP's
Last edited:
Ok lets say your bootloader is unlocked and you have already rooted using this method and you want to update from 5.0.x to 5.1.0
All you need to do is download the firmware zip from nexus images page https://developers.google.com/android/nexus/images
extract the entire thing, even the zip inside the main archive.
get the images into a folder that contains adb which are:
boot.img
recovery.img
system.img
bootloader-fugu-fugu-xx.xx.img (replace the "x"s with the new version numbers)
than open adb in that folder and do the following commands in bootloader mode:
fastboot flash bootloader bootloader-fugu-fugu-xx.xx.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
than run the latest version of this root method after
this will flash the new images without erasing the /data partition which is where all you configurations and app data stays
the /data wipe of normally running the firmware zip is either the script or triggered from running the archive as a whole telling the bootloader to wipe it
Well I´m unable to root my Nexus Player running 5.1 (LMY47D)
Any idea? (Using Windows 8)
Any idea? (Using Windows 8)
Hello,Well I´m unable to root my Nexus Player running 5.1 (LMY47D)
Any idea? (Using Windows 8)
I just rant the bat file myself and there is something going on... Does not seem to remount and push the su binaries so root is not active. I did notice that USB debug was not active on first boot so you do need to go in and turn it back on. This does allow for the unit to be recognized for both fastboot and adb. You also have to allow your PC again. I ran the bat file a second time and same outcome, not finding device after first boot. Is this perhaps happening since we already have SU installed causing an issue with the script? Should we uninstall SU, it gives the "There is no SU binary installed" message. I assume since the player is not mounting on the second boot it is not being pushed?
Cheers
So are you saying the issue is its not completing install of su or afterwards are you having issues with root stuff
I'll do a test tonight by reverting firmware and update again
The thing is if you update to 5.0 to 5.1 it flashes a new system.img which will always wipe /system
Both the su binarys and su app is in /system so everything being applied by the .bat is wiped on update
There is a possibility I missed something but I'll go over it again, if you want you can provide info on the steps you took for updating ect..
Hello,
I will try to be more clear and yes this was LRX21V to LMY47D. I extracted and flashed the factory images keeping data. Rebooted back into fastboot and ran the bat file and the script executed the first portion. This first step runs and completes causing the reboot. The on screen advises to wait until the launcher appears then continue. When you start the second portion the fugu acts as if it is no longer mounted. I understand that it does spit out some commands showing "the can't find" messages but I do not see that it is pushing anything. I realized that flashing the new images probably reset USB debug. I checked that and had to turn it back on before the fugu was seen within Windows7. Once I did that I could see the fugu for both adb and fastboot. I then re-ran the bat file but the SU app is showing "no binaries" installed and will not let you in to the app to update. Is it ok to just manually fastboot boot your root-boot.img file like Chain's? Thanks for your continued work.
Cheers
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?)
(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
Can't seem to find this anywhere. I used it the first time for 5.0.
NVM, invisible to google for some reason though: http://forum.xda-developers.com/nexus-player/orig-development/root-t2948565
Hey Guys,
Assuming there is an insecure boot for the ADT-1 floating around, How hard would this script be to modify to work with LRX22G 5.0.2
I can see I would need to grab the ARM binaries, SU etc
Cheers Rob.
Assuming there is an insecure boot for the ADT-1 floating around, How hard would this script be to modify to work with LRX22G 5.0.2
I can see I would need to grab the ARM binaries, SU etc
Cheers Rob.
https://www.google.ca/search?q=what+are+the+benefits+of+rooting&oq=what+are+the+benefits+of+rooting
There are a few.. Titanium Backup will allow restoring an app with its data. Works great on the NP. That's my primary use. SU access in ADB Shell is another which will allow you to make changes to /system (ie. build.prop, delete/add APKs, etc.)
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