Related
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
Hi guys,
Yesterday i have rooted a friend's phone with a laptop using the RootGenius application and all worked perfectly and the root is working good.
EDIT: I've tested other root apps on my friend's phone and it's the same problem. So that app didn't rooted correctly.
After that, i rooted my phone wich is a Samsung Galaxy S4 Black Edition (i9505) and...well, something went wrong there. After the root, all the programs were stopping working. The installed programs were not available and i couldn't open almost any app. I did a factory reset and now it's working fine, but...the root acces it's a little bit f****d up.
If i check the root with Root Checker, it says that i have root access. The superuser app is called KingUser and i never heard of this app.
Now, here comes the problem: if i want to use a root-needed app like GameCIH, for example, i grant the root access, but i can't use the app, it says that i don't have a rooted phone...
I can use the XMODGAMES app wich is also a root-needed app, but i want to use all the root apps, 'cause why not?
I tried to install SuperSU. When i open it, it says that i need to update SU binaries. I press normal, because i don't have a custom recovery and then i grant root acces and then it says: Failed, reboot the phone and try again. I rebooted it a few times and no succes, the same thing.
So what should i do?
Should i unroot it and then re-root it?
If yes, how?
Thanks.
Have a nice day.
Why not just use CF auto-root for flashing. Easiest method and never fails.
Unroot and reroot using CF-Autoroot. Search for the CF-Autoroot thread to learn how it's done.
Be aware however that this will trip the Knox flag.
Strephon Alkhalikoi said:
Unroot and reroot using CF-Autoroot. Search for the CF-Autoroot thread to learn how it's done.
Be aware however that this will trip the Knox flag.
Click to expand...
Click to collapse
Thanks, I will try to do that. But what means that it will trip Knox flag?
We have an entire thread on Samsung's Knox software on the forum, but in short the flag is a means for Samsung to tell the phone's firmware has been tampered with.
Strephon Alkhalikoi said:
We have an entire thread on Samsung's Knox software on the forum, but in short the flag is a means for Samsung to tell the phone's firmware has been tampered with.
Click to expand...
Click to collapse
And so it's bad if i use cf-root?
Cubix202 said:
And so it's bad if i use cf-root?
Click to expand...
Click to collapse
No, it's not.
Lennyz1988 said:
No, it's not.
Click to expand...
Click to collapse
Ok thank you. I have one more question.
So i didn't find anything on how to unroot with cf-auto-root for android 5.0.1....
Can i root it over the root that it has right now?
I mean just root it again by following this post: http://forum.xda-developers.com/showthread.php?t=2219803
Stay away from Kingroot,nothing but trouble,on some devices whitch are difficult to root it can be a sollution ,on Samsung it's Chainfire auto root. And i strongly advice to remove the Kinguser app !!!
ludoke said:
Stay away from Kingroot,nothing but trouble,on some devices whitch are difficult to root it can be a sollution ,on Samsung it's Chainfire auto root. And i strongly advice to remove the Kinguser app !!!
Click to expand...
Click to collapse
This situation is beyond me
How can I remove the KingUser app?
Now i was trying to install CWM Recovery someway to be able to update su binaries trhu it with SuperSu.
Can i add you on Facebook or Steam or Skype or whatever to help me faster?
Or can you send me a detailed step-by-step thing to help me faster..?
Thanks
You can remove King user by clicking on the icon,hold it en move it to the left upper corner ,where it'saing delete app or something like that in Dutch it's "installatie ongedaan maken"
At first root whith Chainfire ,don't use CWM but TWRP 2.6.0.0? Search for it,and dont use TWRP 2.8.5.0.
ludoke said:
You can remove King user by clicking on the icon,hold it en move it to the left upper corner ,where it'saing delete app or something like that in Dutch it's "installatie ongedaan maken"
At first root whith Chainfire ,don't use CWM but TWRP 2.6.0.0? Search for it,and dont use TWRP 2.8.5.0.
Click to expand...
Click to collapse
Damn, i just installed CWM recovery with succes....
I can't uninstall KingRoot or KingUser or KingMaster, whatever is called, it's installed as a system app.
And...i think i just ****ed up my recovery. I can't boot into recovery mode.
Cubix202 said:
Damn, i just installed CWM recovery with succes....
I can't uninstall KingRoot or KingUser or KingMaster, whatever is called, it's installed as a system app.
Click to expand...
Click to collapse
That's why i said it's trouble, the only sollution to remove it is factory reset,root again and custom recovery,use this time TWRP much easier ,just touch and spare the volume rockers
Sorry,didn't know it's removable that way...says enough i think...
The factory reset dont unroot, i factory reseted and the phone is still in that trouble.
And with the recovery? Can i install TWRP now?
Ok so i figured out what i've done: I have installed Philz Recovery which is a CWM recovery 6 with touch version and it works via an app that boots into recovery (root app that fortunattely worked as root). So what do i need to do now?
If i open SuperSu it says that it needs to update the su binary. When i tap normal it fails and then i tap cwm/twrp, it dosen't do anything, even if i boot into recovery mode. Do i need to install a zip SU-BB? I did it and it didn't work. Any other ideas?
ludoke said:
You can remove King user by clicking on the icon,hold it en move it to the left upper corner ,where it'saing delete app or something like that in Dutch it's "installatie ongedaan maken"
At first root whith Chainfire ,don't use CWM but TWRP 2.6.0.0? Search for it,and dont use TWRP 2.8.5.0.
Click to expand...
Click to collapse
Your information is outdated. TWRP is already on 2.8.7.0 and it's the only one that should be used. Do not use old version because it will give you conflicts with Lollipop.
Cubix202 said:
Ok so i figured out what i've done: I have installed Philz Recovery which is a CWM recovery 6 with touch version and it works via an app that boots into recovery (root app that fortunattely worked as root). So what do i need to do now?
If i open SuperSu it says that it needs to update the su binary. When i tap normal it fails and then i tap cwm/twrp, it dosen't do anything, even if i boot into recovery mode. Do i need to install a zip SU-BB? I did it and it didn't work. Any other ideas?
Click to expand...
Click to collapse
What you need to do:
- If you are on the latest Philz just perform a full wipe. Reflash the rom. And do what I told you.
Lennyz1988 said:
Your information is outdated. TWRP is already on 2.8.7.0 and it's the only one that should be used. Do not use old version because it will give you conflicts with Lollipop.
What you need to do:
- If you are on the latest Philz just perform a full wipe. Reflash the rom. And do what I told you.
Click to expand...
Click to collapse
I've bricked my phone.
Cubix202 said:
I've bricked my phone.
Click to expand...
Click to collapse
No you have not.
Lennyz1988 said:
No you have not.
Click to expand...
Click to collapse
Yes i have.
It is stuck at bootlogo SAMSUNG.
[GUIDE] [OSPREY] [MM] 【6.0/6.0.1】Install TWRP, Root and Xposed successfully on 6.0
1) Unlock your bootloader . for complete unlocking process go here.
https://m.youtube.com/watch?v=sw675ipX-ds&feature=youtu.be
IT WILL RESET ALL YOUR DATA.
2) Turn on USB debugging on
3) Boot your device into bootloader mode
4) flash TWRP recovery v2.8.7 r5. http://forum.xda-developers.com/devdb/project/?id=11051#downloads
5) Boot into TWRP recovery
6) Flash supersu zip v2.62-3. http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
7) After succsesfull flashing wipe cache/dalvik cache . reboot system. If it asks to install Root. DO NOT INSTALL ROOT AT THIS STAGE.
8) wait till Boot finishes.
9) If you want to install Xposed Boot into TWRP recovery.
10) Flash Xposed installer xposed-v79-sdk23-arm.zip. http://forum.xda-developers.com/showthread.php?t=3034811.
Thanks for contributors of TWRP, Supersu and Xposed.
I am G-Root...ed
Thanks man!, being trying a lot with no succes... till now... Excelent Work :good:
abhijeetc9762 said:
1) Turn on USB ) .
Click to expand...
Click to collapse
do we have twrp for moto g turbo?
The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?
abhijeetc9762 said:
3) flash TWRP recovery v2.8.7 r5.
Click to expand...
Click to collapse
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
You don't have chance anyway after rooting. You have to have Flash the firmware again to receive OTA
Sent from my MotoG3 using XDA Premium 4 mobile app
soumyajit_nayak said:
Will this work without flashing TWRP? Can I just boot TWRP using fastboot, then flash SuperSU 2.62-3 and reboot? In that way, after reboot it will be system recovery and as SuperSU 2.62-3 is a systemless root, there won't be any modification in /system. Thus, I can receive OTA updates in future directly.
Did anybody try this with XT1550?
Click to expand...
Click to collapse
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.
Tel864 said:
Yes, you can do it that way, I've done it several times. Like someone said though, it's simpler to just flash TWRP and be done with it rather than wait for OTA's that you probably can't flash anyway.
Click to expand...
Click to collapse
In an earlier post you indicated that you can simply do a full unroot with SuperSU and receive OTA updates. Did that only apply to 5.1.1 and not 6.0?
Tel864 said:
I was able to d/l the update, but had to unroot to install the update. If you're using SuperSU to root, it's a simple matter to use the SuperSU app and do a full unroot, then just root again after the update.
Click to expand...
Click to collapse
Kakaroth89 said:
The phone has to have the bootloader unlocked?
The whole thing will completely reset the device?
Click to expand...
Click to collapse
Same question. Coming from a Nexus 4 phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
EDIT (01-20-2016): Thanks for adding the missing unlock bootloader step to the instructions. I just ordered a Moto G yesterday.
pjc123 said:
Same question. Coming from a Nexus phone, it was necessary to unlock the bootloader first. According to the instructions here, that is unnecessary?
Click to expand...
Click to collapse
To root you will need an unlocked bootloader.
Any one?
Rooted xt1550 with supersu 2.62 and then deleted moto bloatware, now phone stuck on black screen after rebooting. Any help abt deleting bloatware?
Seems fine..but
just done this and boot up looks normal but seems forever to boot up. It has not boot up yet, what is the estimated time to wait?
Does it matter if TWRP is configured as "Read Only" or not?
Tel864 said:
To root you will need an unlocked bootloader.
Click to expand...
Click to collapse
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader
Kakaroth89 said:
And this procedure will do a factory reset?
I mean all the procedure, not just unlocking the bootloader
Click to expand...
Click to collapse
No, all your data and apps will still be there.
Tel864 said:
No, all your data and apps will still be there.
Click to expand...
Click to collapse
I lost all apps and data when I unlocked bootloader.. I did not unlock until after the 6.0 upgrade.
MrTooPhone said:
Does it matter if TWRP is configured as "Read Only" or not?
Click to expand...
Click to collapse
Do no tick as read only.
Sent from my MotoG3 using XDA Premium 4 mobile app
OP updated for bootloader unlocking procedure
Sent from my MotoG3 using XDA Premium 4 mobile app
abhijeetc9762 said:
5) Boot into TWRP recovery
Click to expand...
Click to collapse
@abhijeetc Excellent instructions. One recommendation is to address the issue with the "read only" TWRP option. I am sometimes presented with this option during TWRP boot (not sure why this option is not presented every time since I never check "don't show again"). I am not sure if "read only" makes a difference or not. But I can confirm I was soft bricked after enabling read only and flashing 2.66. I did not wipe Dalvik/Cache either. I was successful with 2.62-3 but was not presented "read only" option either. Also, you may want to recommend a Nandroid back up prior to any attempt flashing root. Just a recommendation.
I notice under developer settings (tap Build Number a bunch of times in the "About Phone" section to access developer mode) it has the option "OEM unlocking - Allow bootloader to be unlocked" as an option. Does that make this process any easier or is it necessary? I bought my phone straight from motomaker.
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
tl;dr: fastboot boot to stock boot.img, log in to snapchat, reboot.
Hello All,
I was trying to log in to Snapchat and I discovered that it won't let you log in if you're rooted. I searched the forums and I found a lot of different solutions, but they required me to install Xposed or fully unroot, which seemed like a hassle. So, I decided to make a guide for the best way to do this on a stock rooted ROM.
1. Download the full system image for your device + build (https://developers.google.com/android/images)
This worked on my Pixel, it should work for other Nexus/Pixel/Pixel XL devices as well though.
2. Unzip the file
3. Unzip the image-sailfish-XXXXXX.zip inside the new folder
4. Connect your device to your computer with ADB and reboot to bootloader
5. fastboot boot path/to/boot.img (inside the folder from step 3.)
NOTE: Please make sure to fastboot BOOT, NOT fastboot FLASH.
6. Once booted, log in to Snapchat. It should work.
7. Reboot.
8. Backup Snapchat in Titanium Backup so you don't have to do this again.
You should now be logged in to Snapchat! Since you only booted to the stock unrooted image, you should still be rooted after you reboot in step 7.
Doesn't work babe
I just use magisk yes it's limited but it does what it need it for
avenator14 said:
tl;dr: fastboot boot to stock boot.img, log in to snapchat, reboot.
Hello All,
I was trying to log in to Snapchat and I discovered that it won't let you log in if you're rooted. I searched the forums and I found a lot of different solutions, but they required me to install Xposed or fully unroot, which seemed like a hassle. So, I decided to make a guide for the best way to do this on a stock rooted ROM.
1. Download the full system image for your device + build (https://developers.google.com/android/images)
This worked on my Pixel, it should work for other Nexus/Pixel/Pixel XL devices as well though.
2. Unzip the file
3. Unzip the image-sailfish-XXXXXX.zip inside the new folder
4. Connect your device to your computer with ADB and reboot to bootloader
5. fastboot boot path/to/boot.img (inside the folder from step 3.)
NOTE: Please make sure to fastboot BOOT, NOT fastboot FLASH.
6. Once booted, log in to Snapchat. It should work.
7. Reboot.
8. Backup Snapchat in Titanium Backup so you don't have to do this again.
You should now be logged in to Snapchat! Since you only booted to the stock unrooted image, you should still be rooted after you reboot in step 7.
Click to expand...
Click to collapse
This method wont work with the stock kernel. You would need to use a kernel that includes the safetynet patch since Snapchat checks against this. Magisk does work though. Just select Snapchat from the Magisk Hide settings menu once you get it installed properly.
uodii said:
This method wont work with the stock kernel. You would need to use a kernel that includes the safetynet patch since Snapchat checks against this. Magisk does work though. Just select Snapchat from the Magisk Hide settings menu once you get it installed properly.
Click to expand...
Click to collapse
I got this to work on my own stock rooted Pixel with the stock kernel. You are booting into an unrooted image using my method, so the SU binary will not be present. This was sufficient to allow me to log in to Snapchat, even though my bootloader was still unlocked. This works because the Pixel uses a systemless root.
real_stacky said:
Doesn't work babe
Click to expand...
Click to collapse
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.
avenator14 said:
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.
Click to expand...
Click to collapse
SafetyNet checks for an unlocked bootloader. That's why I said a patched kernel is required...Unless they changed something again, but this was definitely required a few months back.
uodii said:
SafetyNet checks for an unlocked bootloader. That's why I said a patched kernel is required...Unless they changed something again, but this was definitely required a few months back.
Click to expand...
Click to collapse
Hm yeah I can't really speak to the inner workings of SafetyNet, however I did have an unlocked bootloader at the time of performing this, so from my own anecdotal experience I can say that this method allows Snapchat to log in with an unlocked bootloader (I haven't tried it with other apps) on build NHG47K.
avenator14 said:
Hm yeah I can't really speak to the inner workings of SafetyNet, however I did have an unlocked bootloader at the time of performing this, so from my own anecdotal experience I can say that this method allows Snapchat to log in with an unlocked bootloader (I haven't tried it with other apps) on build NHG47K.
Click to expand...
Click to collapse
If that's the case, then it's good info. Maybe it only does a SU check instead of SafetyNet. Good info.
avenator14 said:
Are you using the right image? Make sure you are downloading the factory image, not the OTA image. This will only work if you are on stock firmware, and make sure to download the right factory image for your device and version.
Click to expand...
Click to collapse
Nvm i found an app on the play store that does the trick called Hide Rooting Lite. (Can't link it soz)
thanx this actually worked flawlessly. latest build twrp rc1 and rooted. I follow your instruction and it worked. now TB backup. thanx and rep for u.
Edit: after doing this I actually did a TB backup. deleted snapchat app and restore app+data using TB. having root and it still works.
Failed to boot boot.img ..... "dtb not found"....?
+1 mate
Titanium backup is also good for me cause I use the app kik and when you sign out you lose all your messages so I make backups and when restoring all my messages are back!!
Going be using that app more often now!!
https://www.youtube.com/watch?v=a-PtwtQFBWg
I made a video on how to increase your snap score. Hope you enjoy it!
cgrimm9 said:
I just use magisk yes it's limited but it does what it need it for
Click to expand...
Click to collapse
What do you mean it's limited? More features than SuperSU
---------- Post added at 11:29 AM ---------- Previous post was at 11:14 AM ----------
eduardmc said:
thanx this actually worked flawlessly. latest build twrp rc1 and rooted. I follow your instruction and it worked. now TB backup. thanx and rep for u.
Edit: after doing this I actually did a TB backup. deleted snapchat app and restore app+data using TB. having root and it still works.
Click to expand...
Click to collapse
Just use Magisk m8