Database Users

[Q] Error installing Android 4.3

So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:

Same problem here. I haven't fixed it yet either.
Why is the right door always locked?

hasbrobot said:
Same problem here. I haven't fixed it yet either.
Why is the right door always locked?
Click to expand...
Click to collapse
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium

Ben Ling said:
I got this problem...
I download this OTA...Then it say reboot to install but it enter TWRP.
Then I put the zip to internal storage and flash but I got error.
Sent from my Sony Xperia™ sola using XDA Premium
Click to expand...
Click to collapse
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.

jazzespresso said:
looks like your SystemUI.apk has been modified not in original. I would recommend to get copy of systemUI.apk from stock 4.2.2 and copy it to your tablet and using file explorer, replace it. and give a try.
Click to expand...
Click to collapse
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App

Ashenphoenix said:
So I got the OTA update, but after downloading it, the install failed (dead android says: error), then the Nexus 7 reboots to 4.2.2.
I already did a factory reset, but it didn't help either...
Anyone with the same issue?
Video:
Click to expand...
Click to collapse
my OTA failed too, different error. this usually always the case if /system/ folder integrity check failure (error 7), means files in /system/ folder are not original or modified. Yours does not give any details, but I bet it is. to see what error, try to flash it thru CWM or any other custom recovery you use.
http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/

Ben Ling said:
yeah i have modified my SystemUI before.and also framework-res...
but i didn't save my old SystemUI,can you upload?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)

jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
okay...will my data be erase when installing?
Sent from my Google Nexus 7 using XDA Premium App
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
jazzespresso said:
here you go...but remember it may get another error for another file, so it is better to find stock 4.2.2 ROM (check here N7 forum, someone probably posted the link)
Click to expand...
Click to collapse
Tried your SystemUI,don't work...keep on stopped...so I replace back...
Sent from my Sony Xperia™ sola using XDA Premium

I guess I'll download the Nexus Toolkit, click on the flash stock + unroot button, so it flashes the stock 4.2.2 and then I'll try to OTA update again.
I already unrooted, but I think it's not a problem.

Seems like it is not fixable!
I used fast boot to push my missing file.
I used es file explorer.
I used titanium back up to make the app, system...
No way, nothing. Not the slightest luck.
(My missing app is xt9ime.apk)
I haaaaaate this situation.
the worst thing is that xt9ime.apk is asus keyboard, and it is disabled by google on nexus 7.
why should not having an app that they don't want to use be a problem. X(
Sent from my Nexus 7 using XDA Premium HD app

Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.

jaysus145 said:
Are you guys with errors using SuperSU? If so what version?
It seems like that the last couple versions touch a file used by OTAs. The Dev recommends using the "Full Unroot" option in the SuperSU app prior to accepting the OTA.
Click to expand...
Click to collapse
I did full unroot, and I also did a factory reset, but it still fails to install.
Using Wug's Toolkit to flash stock 4.2.2 is a good idea?
Then try to OTA update 4.3 again?

Same problem
Hi,
I think I have the same problem:
What to do?

You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2

chrisinsocalif said:
You cannot install the full image from Google using fastboot? Just back up your data(if you can) then try a fresh install.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
What is Fastboot?

Theuntje said:
What is Fastboot?
Click to expand...
Click to collapse
Sadness.
Fastboot is a utility used to control the base fastboot firmware on many Android devices. It lets you do low-level actions such as flashing a custom recovery, ROM, or kernel. Toolkits run fastboot behind the scene, but automate the commands for newer users.

I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
I downloaded the system file here: https://developers.google.com/android/nexus/images#occamjwr66v
Then, in the Nexus Root Kit, launch " flash stock + unroot" and select the downloaded system file.
The flash lasts 5 minutes, and the system will reboot.
Then you need to reactivate the usb debugging .
The next action is to relock the Nexus, with the "OEM Lock" in Nexus Root Toolkit.
The system will reboot after flash.
Then, the 4.3 update will be available automaticaly but this time the installation won't crash.
I hope this could help.

el chibro said:
I had exactly the same problem and after trying a few things, I just found a working solution for my Nexus 7.
I used the same tool I used to unlock and root a few months ago: Nexus Root Toolkit 1.6.3.
I made a backup of my files first, my idea being to reflash the 4.2.2 rom
...
I hope this could help.
Click to expand...
Click to collapse
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.

RocketOptics said:
Thanks for the idea. I used a similar approach with different steps and got 4.3 and root back.
I had stock 4.2.2, stock recovery, rooted (SuperSU).
Backup data.
From the Toolkit at http://forum.xda-developers.com/showthread.php?t=1809195
- "9. Download, Extract + Flash Google Factory Stock Rom"
- Download Stock Image
- "15. Android 4.2.2 (Build JDQ39)
... followed directions to download and flash WITHOUT wiping USERDATA
I did NOT do the "relock the Nexus, with the OEM Lock".
After flashing, did the OTA update to 4.3
After OTA and rebooting, got SuperSU update and put it on my N7
SuperSU thread: http://forum.xda-developers.com/showthread.php?t=1538053
CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu
I went back in to the Toolkit:
- "10. Boot to Custom/Stock Recovery without Permanently Flashing it"
In CWM, I flashed the installable SuperSU ZIP, rebooted, and got rooted.
Click to expand...
Click to collapse
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Hmm, why didn't you flash directly the 4.3 factory image and the SuperSU.zip on top of it ...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I wanted to save my data and wasn't sure if going directly to 4.3 would be safe. Was just being cautious and letting the OTA do the update.

superSU cant update binary

stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app

minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.

shimp208 said:
I would recommend flashing or temporarily booting a custom recovery and then flash the latest version of SuperSu which can be found here in recovery. This should give fix the binary need's to update error your encountering. Let me know if you still have questions.
Click to expand...
Click to collapse
how to boot a custom recovery? any link?

minjiet said:
stock recovery, just unlocked and rooted.
superSU said binary need to update, i choose 'normal', then it keep showing the screen as i attached.
remain the same even after reboot.
pls help
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mine did the same. Then I chose the other option not normal and it installed it automatically through recovery. Before that it might be needed to download twrp recovery from here
http://www.teamw.in/project/twrp2/128. Use Android App Install Method.

I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5

awyeahh1 said:
I got my nexus 10 yesterday...
did the regular stuff:
fastboot oem unlock followed by fastboot flash recovery ... then i applied SuperSU.1.65 but its not workin > pic below.. any idea folks?
http://tinypic.com/r/2ziocra/5
Click to expand...
Click to collapse
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.

shimp208 said:
I would recommend flashing SuperSU again in recovery and if that still doesn't work take a look at CF-Auto root which will allow you to gain root access.
Click to expand...
Click to collapse
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?

awyeahh1 said:
thanks for the answer.. I flashed 10x times.. same story... doesn't CF-Auto root flash an old version of supersu which is not compatible with android 4.3 ?
Click to expand...
Click to collapse
People have reported that CF-Auto Root works fine with Android 4.3 on the Nexus 10. You can also always update the SuperSU app and binary after successfully rooting with CF-Auto Root.

Thx my prob was solved by appying latest recovery and latest supersu 1.65
Beamed from my Htc kickass Sensation using tapatalk 4.

Same problem here
On starting SuperSU, here’s what I get:
>The SU binary needs to be updated. Continue?
[selected: Continue]
>If you have a custom recovery like TWRP or CWM, that can be used to (try to) install the SU binary. This is recommended for HTC devices. How would you like to install the SU binary? (Normal / TWRP/CWN)
[selected: Normal]
>Installing, please wait
>Installation failed!
As far as I can tell, I can’t install TRWP/CWN because the SuperSU binary is not updated, and I can’t update the the SuperSU binary unless TRWP/CWN is installed. This looks like a vicious circle, can anyone recommend a way out of it please?
Further background:
Device: Evolveo Xtraphone 4.5 Q4, rooted by SRSroot which recognised it as an HTC device.
Also attempted: updating from SD card with UPDATE-SuperSU-v1.86.zip, by running Superuser.apk from the zip folder. This takes me back to square one: “The SU binary needs to be updated. Continue?” etc.
Any recommendations enormously appreciated, thanks!

[4.4.4][TWRP][Modified system] OTA update zip file

So I have pulled and uploaded the update zip file to drive just in case anyone needs it.
And modified to get it working on twrp with Modified system but important core apps like systemui.apk need to be untouched though, no need to flash stock again, just normal flash via TWRP, worked on mine.
And some people were asking if it flashes default recovery or not, so the Answer is TWRP/CWM will stick.
And you will not lose root Access too
Download Links:
TWRP/CWM flashable
Default OTA zip
Explanation of how solve if still having problems as posted by @[email protected]
[email protected] said:
As OP said,
U only have to edit the updater-script file present under condor_4.4.4_TWRP_flashable.zip\META-INF\com\google\android in order to get the zip file working.
1. Copy the condor_4.4.4_TWRP_flashable.zip file that OP shared to your PC.
2. Now open this file using any zip handler like 7zip/winzip/winrar/windows explorer(if running windows8+), browse to the above location to find updater-script file, now extract /copy this on your PC.
3. Now select an option to edit this file using Notepad++ (step 4 on how/what to edit/change)
4. As per the TWRP error log, remove all the lines from the updater-script in particular to that error.
For Ex. if the error says:
/system/app/LiveWallpapersPicker.apk\" has unexpected contents.
then u need to remove the following line from the updater-script
apply_patch_check("/system/app/LiveWallpapersPicker.apk", "f4b9dc41f0d4691a2f9b71be06036c1de91c43ea", "d57f5cbc092e3e6cab286793da70ee7ffc4f440e") || abort("\"/system/app/LiveWallpapersPicker.apk\" has unexpected contents.");
assert(apply_patch("/system/app/LiveWallpapersPicker.apk", "-",
f4b9dc41f0d4691a2f9b71be06036c1de91c43ea, 160480,
d57f5cbc092e3e6cab286793da70ee7ffc4f440e, package_extract_file("patch/system/app/LiveWallpapersPicker.apk.p")));
5. Once u are done with all such, simply save the updater-script and copy this back to its location and select replace if asked.
6. Now save the condor_4.4.4_TWRP_flashable.zip and copy it back to Phone and try flashing now using TWRP.
hope it helps
Click to expand...
Click to collapse
Only for XT1022

Gogeta said:
So I have pulled and uploaded the update zip file to drive just in case anyone needs it.
https://docs.google.com/file/d/0B72C6RSL0mQmVlVwZ1VBTWwzaVE/edit?usp=docslist_api
Click to expand...
Click to collapse
Can i use it on XT1022?

Anyone knows when the update comes out for the Europe retail?

mrpkarthik said:
Can i use it on XT1022?
Click to expand...
Click to collapse
It's for xt1022.

i have updated my phone though setting now after updating,, it works fine for 1 min, then it gets boot back into twrp(recovery)... any solution guys

sunnyx12x21x said:
i have updated my phone though setting now after updating,, it works fine for 1 min, then it gets boot back into twrp(recovery)... any solution guys
Click to expand...
Click to collapse
I also had the same problem...and flashed STOCK Recovery and Updates works great...

How to flash stock recovery...
Sent from my XT1022 using XDA Premium 4 mobile app

Nandha005 said:
How to flash stock recovery...
Sent from my XT1022 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flash the attached recovery.img (after unzipping the archive) using fastboot or mfastboot.
This one is only for XT1022.

Okay, so tried to modify the updater script to get it working with TWRP but it won't work if you modified any system file by yourself because it verifies all the system files and then patches them, (I had modified many apks, so it didn't work.), tried to skip verification but then it failed during patch.
So you can try But it won't work for modified system. and must create a nandroid backup.
Use the attached updater script for TWRP.
Even Stock recovery won't work on modified system.

update works on rooted devices but there should be stock recovery
Rooted users can update their moto e but must have stock recovery. If you are facing problem with trwp recovery while updating it, then flash the stock recovery annd then try. It works
Hit thanx if helped

If I flash Stock recovery data is wipe or not...
Sent from my XT1022 using XDA Premium 4 mobile app

Nandha005 said:
If I flash Stock recovery data is wipe or not...
Sent from my XT1022 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no

I have flashed stock recovery and downloaded update file using settings but now when it start installs it shows installation unsuccessful and whenever I boot into stock recovery it shows no command with dead android
Sent from my XT1022 using XDA Free mobile app

@Gogeta I downloaded the update and choose install later. How to pull the downloaded update file ? I am rooted with TWRP.

gtsfreak said:
I have flashed stock recovery and downloaded update file using settings but now when it start installs it shows installation unsuccessful and whenever I boot into stock recovery it shows no command with dead android
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
As i said, it verifies all system files before update, you must have modified or deleted something.
raj.amalw said:
@Gogeta I downloaded the update and choose install later. How to pull the downloaded update file ? I am rooted with TWRP.
Click to expand...
Click to collapse
/cache
but only if you are rooted

Nope I have only deleted stock apps that's all
Sent from my XT1022 using XDA Free mobile app

gtsfreak said:
Nope I have only deleted stock apps that's all
Sent from my XT1022 using XDA Free mobile app
Click to expand...
Click to collapse
Gogeta said:
As i said, it verifies all system files before update, you must have modified or deleted something.
Click to expand...
Click to collapse
Thats what i said

So what should I do now I don't wanna loose any data please help?
Sent from my Z10 using XDA Free mobile app

[HELP]
How To Manually Flash The OTA.Zip On Stock Unrooted Device ?

ADB sideload
salkollizz said:
How To Manually Flash The OTA.Zip On Stock Unrooted Device ?
Click to expand...
Click to collapse
guys u can use adb sideload on TWRP 2 flash d update package

[ROOT][RECOVERY][ALL IN ONE] Cf-Autoroot-twrp-T700/705/800/805/Tab S- UPDATE 23/4/15

Updated CF-autoroot with latest Supersu binaries and combined TWRP recovery for SM-T800/SM-T805/T700/T705 Exynos only, Lollipop and Kitkat
I've noticed that quite a number of people seeking to root their device also flash TWRP afterwards, seeing as it's unnecessary to do both steps I have made an all in one package to root and install TWRP recovery.
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version (ADB root shell and Download mode fixes).
UPDATE - I have updated all versions with new builds. TWRP is now v2.8.6.2 and now includes the fixes recently pushed to their repo for encrypted backups. I have also addressed the slow wipe issue, cache, system, etc., which some have experienced and should now be much quicker.
Each device now has it's own build, this is to ensure that TWRP recovery build properties reflect the device it's installed on. ROMs such as CM12 should now install without issue.
Feedback is welcome.
Simply flash with ODIN. Odin 10.6
cf-autoroot-twrp-t700
cf-autoroot-twrp-t705
cf-autoroot-twrp-t800
cf-autoroot-twrp-t805
Check root status with ROOT VALIDATOR
Guide how to flash, credit to Usama m.
http://techbeasts.com/2015/05/01/root-twrp-recovery-galaxy-tab-s-84-running-lollipop-502/
UPDATED TWRP:
http://forum.xda-developers.com/showthread.php?t=3074633
NOTE: It is important to boot to recovery after flashing or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
Credits to chainfire for his great work.
FEEDBACK PLEASE
AND DONT FORGET THAT THANKS BUTTON :good: HIT AND RUN IS NOT NICE
.

Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks

d3xtr0 said:
Testing..
EDIT:
Root is working great, at least terminal got root permissions and recovery does work too !
Thanks
Click to expand...
Click to collapse
Good stuff. :good:

Just picked up a T800 as a birthday present to my mom.. Its going to be hard to give this thing to her..lol
Anyways.. just used this to root and it worked perfect.. Had already took ota to LP..
Thanks !!

delete post !

tids2k said:
delete post !
Click to expand...
Click to collapse
What?

ashyx said:
What?
Click to expand...
Click to collapse
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.

snapper.fishes said:
I guess he made an unnecessary post and wanted an admin to delete his post, and not yours.
Click to expand...
Click to collapse
Why the forum doesn't allow users to delete their own posts is beyond me?

In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx

lloydb9382 said:
In the Odin section, the Tar. File , i just want to double check , i have to put it on the AP box correct ?, thanx
Click to expand...
Click to collapse
Correct.

thanx so much it worked great ,

T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app

almony8 said:
T807A, is that a model this could possibly work on? I just got this tablet and just starting to look for root. It's an AT&T tab s 10.5
Sent from my SM-N900P using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately AT&T lock the bootloader, so atm you're stuck with a device that cannot be modified in any way.
Sent from my SM-T805 using XDA Free mobile app

After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.

cyaclone said:
After using the app with odin, root checker indicates that "Root access not properly configured or granted".
Root question comes up but can not check the box to allow.
Had an issue like this on a different device and it was corrected when I changed to ART, but do not know where it is in 5.0.2?
Just tried TWRP, and it is allowed.
Click to expand...
Click to collapse
Use Root Validator and post the output. Root checker doesn't give enough information.

ashyx said:
Use Root Validator and post the output. Root checker doesn't give enough information.
Click to expand...
Click to collapse
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive

cyaclone said:
Root Denied
Superuser app found
Superuser Binary
Multiple busybox's
SELinux is permissive
Click to expand...
Click to collapse
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.

ashyx said:
Looks like you are rooted but are not granting root permission when asked.
Is the post below any solution to your problem?
http://forum.xda-developers.com/showthread.php?t=3076796
If you still have problems you could open the Super su app and change in settings to 'Grant' root access by default.
Click to expand...
Click to collapse
BINGO!, it was Lux. I did an uninstall and rebooted and had ROOT.........WOW, strange that this would be the answer, but it worked for me at this moment.
Thanks

Not sure if it matters but what version of twrp is being installed?

AKfortyseven said:
Not sure if it matters but what version of twrp is being installed?
Click to expand...
Click to collapse
Cf-autoroot has been updated with the latest Supersu binaries and TWRP has been updated with my fixed version.
Click to expand...
Click to collapse
= 2.8.6.1

Android 7 root?

Anyone get root to stick? I flash supersu via TWRP and on reboot, no root. Anyone get root working properly on the nexus player with android 7?
Thanks

dfl said:
Anyone get root to stick? I flash supersu via TWRP and on reboot, no root. Anyone get root working properly on the nexus player with android 7?
Thanks
Click to expand...
Click to collapse
I rooted using BETA-SuperSU-v2.71-20160331103524.zip the latest super su doesn't seem to work

Do yourself a favor and don't screw with binary roots (you never know what they're really doing).
https://github.com/seSuperuser/AOSP-SU-PATCH
And I even keep prebuilt binaries in /bin path.
Just write the fugu boot.img and install the apk.

How do I use the Beta SU
Anjustice1 said:
I rooted using BETA-SuperSU-v2.71-20160331103524.zip the latest super su doesn't seem to work
Click to expand...
Click to collapse
I downloaded the Beta SU how do I use it?

feennleydy said:
I downloaded the Beta SU how do I use it?
Click to expand...
Click to collapse
Bootloader unlocked ??
TWRP installed ??
If both are yes flash in recovery (TWRP)
If no than you should read more. So you don't screw up your device.
Good luck.

Anjustice1 said:
I rooted using BETA-SuperSU-v2.71-20160331103524.zip the latest super su doesn't seem to work
Click to expand...
Click to collapse
hi.
did you just flashed the superSU zip file by using twrp with a unlocked bootloader?
i had 6.0.1 stock rooted nexus player rom (unlocked bootloader and twrp installed) by using the tips of xda.
Then the nexus player updated itself to 7.0 (i didnt update it manually), then i lose root and twrp. i only have unlocked bootloader ("secure boot= enabled" and "lock state = unlocked")

Bruno_Tec said:
hi.
did you just flashed the superSU zip file by using twrp with a unlocked bootloader?
i had 6.0.1 stock rooted nexus player rom (unlocked bootloader and twrp installed) by using the tips of xda.
Then the nexus player updated itself to 7.0 (i didnt update it manually), then i lose root and twrp. i only have unlocked bootloader ("secure boot= enabled" and "lock state = unlocked")
Click to expand...
Click to collapse
That's exactly what I did, good to go. Only thing I notice now is that every so often when I go to use the nexus player in the morning it sometimes boots itself into twrp :/
Sent from my SGH-I337M using XDA-Developers mobile app

Anjustice1 said:
Bootloader unlocked ??
TWRP installed ??
If both are yes flash in recovery (TWRP)
If no than you should read more. So you don't screw up your device.
Good luck.
Click to expand...
Click to collapse
Yes bootloader unlocked and yes TWRP Manager installed. don't know how to flash in recovery

feennleydy said:
Yes bootloader unlocked and yes TWRP Manager installed. don't know how to flash in recovery
Click to expand...
Click to collapse
Do you just have twrp manager or do you also have twrp installed as your recovery? If you have twrp as recovery, boot into recovery, than install from zip and select the SuperSU.zip file you downloaded
Sent from my SGH-I337M using XDA-Developers mobile app

raptor170 said:
[...] Only thing I notice now is that every so often when I go to use the nexus player in the morning it sometimes boots itself into twrp :/
Click to expand...
Click to collapse
Same here! Why is this happening, anybody knows?

digitaligor said:
Same here! Why is this happening, anybody knows?
Click to expand...
Click to collapse
The Nexus player is trying to update via OTA and failed due to keep being the recovery.
Sent from my Nexus 6 using Tapatalk

payazo915 said:
The Nexus player is trying to update via OTA and failed due to keep being the recovery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Ok, is there maybe a way to avoid this?

payazo915 said:
The Nexus player is trying to update via OTA and failed due to keep being the recovery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I can confirm this also, it tried to do it while I was watching YouTube and it booted into recovery :/
Sent from my SGH-I337M using XDA-Developers mobile app

raptor170 said:
I can confirm this also, it tried to do it while I was watching YouTube and it booted into recovery :/
Sent from my SGH-I337M using XDA-Developers mobile app
Click to expand...
Click to collapse
The usual cause of this issue is that the NP is rooted and has a Custom Recovery such as TWRP installed. The NP fails to update automatically whenever there's a new official OTA image available.
To stop this from happening you can use an apps like DisableService or My Android Tools and UNCHECK (disable) the following:
Disable Service or My Android Tools -> System -> Search -> Google Play Services and "Uncheck" SystemUpdateService.
If it still boots into recovery also disable it in the Services Framework
Disable Service -> System -> Search -> Google Services Framework ->. disable SystemUpdateService.

Anjustice1 said:
I rooted using BETA-SuperSU-v2.71-20160331103524.zip the latest super su doesn't seem to work
Click to expand...
Click to collapse
I too had to do this as well. I tried all the rootkits and different methods and versions of SuperSu and none worked.
BETA-SuperSU-v2.71-20160331103524.zip on the other hand worked flawless on Android 7 Nougat.
I too had lost root due the device updating itself to Android 7.
To accomplish this I did the following:
My device was already unlocked previously
Flashed TWRP via ADB
Booted into TWRP
Once booted into TWRP I could see the file contents of my NP on my Windows PC
I copied BETA-SuperSU-v2.71-20160331103524.zip to the root of the internal memory of my NP
Disconnected the USB cable from my computer to my Nexus Player and connected my OTG cable with the Wireless Mouse and Keyboard dongle
Once I had mouse connectivity, from TWRP I chose install Zip
I browsed over to where I had copied BETA-SuperSU-v2.71-20160331103524.zip and selected and flashed it
Once the flashing was completed I chose Reboot to System
I tested SuperSu for root = "Success!"
I installed SideLauncher
I installed BusyBox
To prevent the device from updating itself and the reboots:
I followed the instructions on post #24 from this thread by GabbyWC:
http://forum.xda-developers.com/nex...ess-playing-videos-marshmallow-t3220531/page3
Here is a copy and paste of it
Sideload the "My Android Tools" app which is available at https://play.google.com/store/apps/d...oidtools&hl=en. After it's installed on your Nexus Player, open and configure it as shown here by using a mouse but you will need root access for this to work.
Service >> System >> Search >> Google Play Services >> Disable SystemUpdateService.
Service >> System >> Search >> Google Services Framework >> Disable SystemUpdateService.
The drawback is your applications will be prevented from updating unless you restart the services back up or side load the latest version of your app.
Hope this helps someone. I was already frustrated that nothing else was working.
One final note:
I was able to find everything I needed by doing a search

Guys on Nougat, if you use the newest Android tv Remote app on your phone. Can you adjust the volume of your nexus player by pressing the phone's volume up/down hardware buttons while the remote app is open?
If you have a different remote with volume can you adjust the volume up or down?
Reason I ask is because the shield can and now the new Xiaomi Mi box AndroidTV can as well. If the nexus player still can't I will remain on my current custom rom.

Tested it, no volume up/down. Struggling to restore pure nexus 6.0.1
Sent from my Redmi Note 2 using Tapatalk

Nothing roots. i always get a failure when it comes to systemless

fontong said:
Tested it, no volume up/down. Struggling to restore pure nexus 6.0.1
Sent from my Redmi Note 2 using Tapatalk
Click to expand...
Click to collapse
Try using the Nexus Rootkit. I can downgrade to any previous version with it. Just make sure you freeze the update processes otherwise it will upgrade right back to Nougat
Sent from my HTC 10 using Tapatalk

vicvega said:
Try using the Nexus Rootkit. I can downgrade to any previous version with it. Just make sure you freeze the update processes otherwise it will upgrade right back to Nougat
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
Thx bud, i wasn't thinking. Got it restored
Sent from my Redmi Note 2 using Tapatalk