Develop Bugs

Original Firmware without fully losing root?

There are a couple of apps I want to use which require the fire tv to be unrooted. Is there a way I can run clean firmware without losing the future option to root the device again? I'm currently running one of the latest pre-rooted firmwares, so I've installed clockworkmod recovery.
I'm assuming I can install one of the old firmware versions that is still rootable? Not sure what functionality I'd lose?

What apps require you to be unrooted? Isn't there an Xposed module that will hide root from the app?

Sky Go and Virgin Anywhere. Wasn't aware of a module?

Checked the module and it doesn't work with those apps.

tonton82 said:
Checked the module and it doesn't work with those apps.
Click to expand...
Click to collapse
Did you try it, or just read about it? Rootcloak?

On the devs page it tells you it doesn't work with them.

tonton82 said:
On the devs page it tells you it doesn't work with them.
Click to expand...
Click to collapse
Again, did you actually try it in case it does? It's not going to bootloop. And was it rootcloak?

Yes, root cloak. It specifically says on the page that it doesn't work, so is it really worth trying? Sky are notoriously strict with iOS and Android platforms.

tonton82 said:
Yes, root cloak. It specifically says on the page that it doesn't work, so is it really worth trying? Sky are notoriously strict with iOS and Android platforms.
Click to expand...
Click to collapse
Fine, I'm done begging you to do it. You're on your own, good luck...

ldeveraux said:
Fine, I'm done begging you to do it. You're on your own, good luck...
Click to expand...
Click to collapse
Are you always so stroppy? I've explained that the dev says it doesn't work. The thread on xda also says it doesn't work. I'm not going to waste my time checking something that everyone says doesn't work.
Could anyone help with my original question please?

Systemless Root & Android Pay

So I'd like to know how I can use Chainfire's new systemless root to then still use Android Pay. I downloaded the Android binaries from Google for the 5X and proceeded like so:
(I was already rooted with the normal method that modifies the /system parition)
1. Run flash-all.bat to flash all partitions and go back to stock.
2. Install the modified boot.img from Chainfire
3. Install the latest TWRP 2.8.7.2
4. Reboot into TWRP
5. Install using adb sideload from TWRP the beta SuperSU
6. Reboot into phone and set it up... restore Titanium Backups...
The problem is that Android Pay still won't let me add a card to it....
Did I do something wrong in this process here?
Would love it if someone who has done this could help me out here..
Thanks!

chickentech said:
So I'd like to know how I can use Chainfire's new systemless root to then still use Android Pay. I downloaded the Android binaries from Google for the 5X and proceeded like so:
(I was already rooted with the normal method that modifies the /system parition)
1. Run flash-all.bat to flash all partitions and go back to stock.
2. Install the modified boot.img from Chainfire
3. Install the latest TWRP 2.8.7.2
4. Reboot into TWRP
5. Install using adb sideload from TWRP the beta SuperSU
6. Reboot into phone and set it up... restore Titanium Backups...
The problem is that Android Pay still won't let me add a card to it....
Did I do something wrong in this process here?
Would love it if someone who has done this could help me out here..
Thanks!
Click to expand...
Click to collapse
Did you hide/disable/uninstall supersu and reboot before opening the Android pay app?
If not, do that, and clear app data for Android pay. Then try to set it up.

Android pay and root don't work. If you want Android Pay to work, you need to disable root anytime you want to use it and even then it may not work.

buru898 said:
Did you hide/disable/uninstall supersu and reboot before opening the Android pay app?
If not, do that, and clear app data for Android pay. Then try to set it up.
Click to expand...
Click to collapse
metpage said:
Android pay and root don't work. If you want Android Pay to work, you need to disable root anytime you want to use it and even then it may not work.
Click to expand...
Click to collapse
Systemless root does work with Android Pay when root is on. At the very least, you should be able to add cards. Which means you should be able to use pay in general. Safetynet checks in Pay are not that strict.
Did you flash TWRP and boot into recovery or did you boot it from fastboot USB?
Have you tried simply putting the zip on the device and flashing it from there?
Did you let TWRP install SU/Root in the prompt before rebooting? (The answer should be no)

formula91 said:
Systemless root does work with Android Pay when root is on. At the very least, you should be able to add cards. Which means you should be able to use pay in general. Safetynet checks in Pay are not that strict.
Did you flash TWRP and boot into recovery or did you boot it from fastboot USB?
Have you tried simply putting the zip on the device and flashing it from there?
Did you let TWRP install SU/Root in the prompt before rebooting? (The answer should be no)
Click to expand...
Click to collapse
To answer,
You can read exactly what I did above. I did not let TWRP install SU for me, and rebooted using the power button I believe after installing the Beta SU from TWRP's ADB sideload..
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Thanks.

chickentech said:
To answer,
You can read exactly what I did above. I did not let TWRP install SU for me, and rebooted using the power button I believe after installing the Beta SU from TWRP's ADB sideload..
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Thanks.
Click to expand...
Click to collapse
Have you tried doing Android Pay before restoring stuff from Titanium Backups? There is a slim possibility that it may be altering something from system, making it fail the safetynet checks.
I would try flashing the zip from TWRP instead of sideloading as well. Just in case.

chickentech said:
...
I'll try again tonight as I KNOW Android Pay DOES work with the new Systemless Root, I just haven't gotten it right on my first try here.
Click to expand...
Click to collapse
Uh... how exactly can you know something "DOES" work if your one and only attempt at making it work was a complete failure and no one else has been able to get it to work?
Not saying Android Pay can't work with systemless route in one form or another. But to make a statement as if something is of fact when you've proven nothing to support that fact is a bit idiotic.
But hey, people said Einstein and Tesla had idiotic ideas. So here's to hoping.

sn0warmy said:
Uh... how exactly can you know something "DOES" work if your one and only attempt at making it work was a complete failure and no one else has been able to get it to work?
Not saying Android Pay can't work with systemless route in one form or another. But to make a statement as if something is of fact when you've proven nothing to support that fact is a bit idiotic.
But hey, people said Einstein and Tesla had idiotic ideas. So here's to hoping.
Click to expand...
Click to collapse
The same could be said for not doing your own research. This is a section for helping others
Right at the bottom: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Update: Reddit user MajorNoodles has informed that Android Pay works on his Nexus 5. Chainfire, on his Google+ post, does mention that the working of Android Pay is by accident and not by design. He expects Android Pay to be updated in the future to counteract this.
Click to expand...
Click to collapse
Unless that hole has been patched already, it should still work, but we won't know for how long.
@chickentech I'm not in much of a position to help, given my location, but this might help you debug whether it is Pay being weird or if SafetyNet is tripped: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground

nvm

PhoenixTank said:
The same could be said for not doing your own research. This is a section for helping others
Right at the bottom: http://www.xda-developers.com/chainfire-releases-root-for-android-6-0-without-modifying-system/
Unless that hole has been patched already, it should still work, but we won't know for how long.
@chickentech I'm not in much of a position to help, given my location, but this might help you debug whether it is Pay being weird or if SafetyNet is tripped: https://play.google.com/store/apps/details?id=com.cigital.safetynetplayground
Click to expand...
Click to collapse
Thanks...
I said I knew because I actually READ.. As you have.
Probably something to do with the order I'm doing things in.. Or as mentioned, the Titanium backup could definitely do it..
You know, I wouldn't even Root if there was a good way to block ads without - but most of what I've seen isn't quite there for me.
Again, thank you @PhoenixTank

chickentech said:
Thanks...
I said I knew because I actually READ.. As you have.
Probably something to do with the order I'm doing things in.. Or as mentioned, the Titanium backup could definitely do it..
You know, I wouldn't even Root if there was a good way to block ads without - but most of what I've seen isn't quite there for me.
Again, thank you @PhoenixTank
Click to expand...
Click to collapse
If you're rooting to modify the hosts file to block ads.... that changes system, and will trip Android Pay's SafetyNet checks. The best adblocking I can get without changing System is Adblock Plus for Android. (Root on ABP seems to only allow some sort of localhost proxy network rerouting instead)
FYI Safetynet Playground trips for me, but Android Pay works just fine.
UPDATE: Weird, now I pass, must be because I recently re-encrypted my phone.
So now it's confirmed, I can use Android Pay and not trip SafetyNet API. Neato.

Thanks! That hosts file was it.. A fresh install and I'm gold with Safetynet Many thanks all around!

You're very welcome!
Right now I'm using adblock plus + a "patcher" that's pretty "lucky" heh.

Hi there everyone !!
I gone a long way till now...
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
http://forum.xda-developers.com/nexus-5x/help/how-to-enable-oem-unlocking-bricked-t3249003
And now I'm trying to get full Stock phone with Encryption, Locked oem and systemless Root without No warnings. = S E L R N
As far as I went was S R N when i tried to encrypt it got stucked on colorful bubbles screen.
Anyone got idea how to reach this ?
Did somone checked is AdAway after changing location of host file and symlinking it, stops Google Pay/Makes additional warning while booting ?

Play Protect Certified: Device is not certified

Not sure if it has anything to do with unlocking bootloader, but it seems that I can't install Netflix because my device is not certified in the Play Store. Anyone else come across this issue?

It is caused by the unlocked bootloader. It has been that way with Pixels since the originals. The solutions are to root with Magisk (do not know if Magisk works with the Pixel 3 or not) or use a custom kernel when one becomes available provided the P3 works like the P and P2.

Sideload it, done.

krabman said:
Sideload it, done.
Click to expand...
Click to collapse
what level is your widevine since you have unlocked your bootloader, did it change?

Actually I need to backtrack here, Netflix wont install on a rooted device and while some say it works I've never had it work with Magisk either. On the other hand you can just sideload and it will work fine rooted. I don't actually know what happens if the device is unlocked but not rooted because I've never done that. lol My bad. I would try sideloading though, it's got a good shot at working and nothing lost if it doesn't.

Just download apk file from apk mirror
Works fine
https://www.apkmirror.com/apk/netfl...flix-6-13-0-build-29940-android-apk-download/

Figured, it's been this way for a fair while now and thats been the fix from the start.

Just open play store in settings\apps, clear data. Reopen the play store and see if it still says it. Might have to do it more than once. I unlocked my bootloader, and I saw that. I had to clear data twice. Now mine shows as certified.

gettinwicked said:
Just open play store in settings\apps, clear data. Reopen the play store and see if it still says it. Might have to do it more than once. I unlocked my bootloader, and I saw that. I had to clear data twice. Now mine shows as certified.
Click to expand...
Click to collapse
No dice for me Google Pay won't work either... strange

virtyx said:
what level is your widevine since you have unlocked your bootloader, did it change?
Click to expand...
Click to collapse
How do I check widevine?

JeromeLeung said:
No dice for me Google Pay won't work either... strange
Click to expand...
Click to collapse
Weird, mine went back to not certified. I did the clear data again and it's good, again. Hrmm

gettinwicked said:
Weird, mine went back to not certified. I did the clear data again and it's good, again. Hrmm
Click to expand...
Click to collapse
Will Google Pay allow you to add a card?

JeromeLeung said:
Will Google Pay allow you to add a card?
Click to expand...
Click to collapse
Nope. Says it cannot complete setup because the device has been rooted or modified. And play store keeps jumping back to uncertified. Guess it won't stick. Have to wait for root. No biggie, I haven't fully jumped on the GPay train yet.

gettinwicked said:
Nope. Says it cannot complete setup because the device has been rooted or modified. And play store keeps jumping back to uncertified. Guess it won't stick. Have to wait for root. No biggie, I haven't fully jumped on the GPay train yet.
Click to expand...
Click to collapse
Okay, I thought something was wrong with my device. Good to know we're all in the same boat

I'm kiinda wondering if the much talked about Titan chip is going to make it harder to hide root. Some of the stuff out there is making that claim. Something related is that I followed a link to a google blog about it and the said that one of it's (Titian's) features is the ability to block unlocking. Not that it did block it, that it had that ability, so presumably it will depend on the OEM whether or not that feature is active. Was wondering where that will put the Verizon guys... Not trying to scare anyone because I haven't run into anything specific that comes from google and says exactly what it does but I know it's got my attention.

JeromeLeung said:
How do I check widevine?
Click to expand...
Click to collapse
you can download an app to check, just search widevine

virtyx said:
you can download an app to check, just search widevine
Click to expand...
Click to collapse
Widevine Security Level: L1

JeromeLeung said:
Widevine Security Level: L1
Click to expand...
Click to collapse
with unlocked bootloader?

Hi
It happens to me on samsung s8 device not certified. I have tried some things( saw in youtube and foruns) and nothing.
So try this...
Open setting/apps/ and look if any app of google is disabled( chrome/gmail/play movies...) activate all from google and voila
My s8 is now certified

virtyx said:
with unlocked bootloader?
Click to expand...
Click to collapse
That's correct

Amazon Fire TV 2 (sloane) - Fix SuperSU crashing issue

Note: Systemless root is not an option on this box due to locked bootloader, do not tell me that root is not an option, because I am rooted right now.
I rooted my Fire TV 2 (FireOS 5.2.7.1) with the hardware method using SuperSU in system mode, although whenever I open SuperSU it immediately crashes. It still comes up with root prompts and I can still accept them, but I can't actually open the app and change settings because it just instantly crashes. Is there a fix for this?
If there isn't a fix for this issue, are there any other SYSTEM MODE superusers that do the same thing as SuperSU.
(Magisk is systemless root, so it doesn't meet the criteria above.)

It's just what amaz. does with apps they don't like^^
But you can edit the supersu config file if you like, in order to access all supersu settings...
The fix is to flash the amonet zip with twrp (aka. unlock the BL), then use magisk... but I guess you know that already, isn't it!?

Sus_i said:
It's just what amaz. does with apps they don't like^^
But you can edit the supersu config file if you like, in order to access all supersu settings...
Click to expand...
Click to collapse
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Sus_i said:
The fix is to flash the amonet zip with twrp (aka. unlock the BL), then use magisk... but I guess you know that already, isn't it!?
Click to expand...
Click to collapse
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.

Toothless_NEO said:
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Click to expand...
Click to collapse
No, it isn't the package name. Most likely it's because an incompatible app theme (missing theme on all fireTV OS versions). If you want to know details, somewhere on xda is a guide, on how to use root/xposed together with xposed modules, as a workarround in order to open up the supersu app on fireTVs. A working theme was material dark, if I remember correct.
Idk why you state magisk isn't an option on 'this' box, since the BL unlock is out and really easy.
Anyway, have fun.

Toothless_NEO said:
So an Amazon service force closes the package name eu.chainfire.supersu in an attempt to make root Unusable? If that's the case Couldn't I just edit the package name to something else, like what I did with FireStarter Launcher?
Well unless Magisk Devs release a System mode Root that can't happen, for reasons I stated above:
"Systemless root is not an option on this box due to locked bootloader"
Having TWRP doesn't mean it's an unlocked bootloader, I know because I recently tried Magisk out of desperation, the result was that It ended up being stuck on the Amazon Logo and I had to do the unbrick process again.
Click to expand...
Click to collapse
He never said or implied having twrp means you have a unlocked bl.
He (as well as I) are wondering why you haven't simply flashed Rortiz2 amonet zip (the unlock) from within your current locked twrp.
This will ultimately unlock the bl of your Sloane.
And solve your issue in minutes + enable you to flash magisk etc.
Regards

Bertonumber1 said:
He never said or implied having twrp means you have a unlocked bl.
He (as well as I) are wondering why you haven't simply flashed Rortiz2 amonet zip (the unlock) from within your current locked twrp.
This will ultimately unlock the bl of your Sloane.
And solve your issue in minutes + enable you to flash magisk etc.
Regards
Click to expand...
Click to collapse
WAIT....
I can unlock the bootloader of my AFTV 2 box- sloane?
Last year i did hardware method to get root/twrp because i was under the impression that one CAN NOT unlock bootloader on this device....
If you can now unlock bootloader on sloane box, when did this happen?
When was this "Rortiz2 amonet" released?
Lastly, since im already rooted and twrp, what do i further need to do to unlock the bootloader?
Thanks many

dovedescent7 said:
WAIT....
I can unlock the bootloader of my AFTV 2 box- sloane?
Last year i did hardware method to get root/twrp because i was under the impression that one CAN NOT unlock bootloader on this device....
If you can now unlock bootloader on sloane box, when did this happen?
When was this "Rortiz2 amonet" released?
Lastly, since im already rooted and twrp, what do i further need to do to unlock the bootloader?
Thanks many
Click to expand...
Click to collapse
I'll answer your pm and your post here...
Yes you can, the boys have presented the full unlock of the Sloane Firetv 2 and Rortiz2 has headlined the thread in "Original Android TV development" section within the Amazon Firetv forum.
All you need to do is follow the OP there, download and flash the zip in current twrp.
If you need any assistance just ask.
Good hearing from you again
Regards

Bertonumber1 said:
I'll answer your pm and your post here...
Yes you can, the boys have presented the full unlock of the Sloane Firetv 2 and Rortiz2 has headlined the thread in "Original Android TV development" section within the Amazon Firetv forum.
All you need to do is follow the OP there, download and flash the zip in current twrp.
If you need any assistance just ask.
Good hearing from you again
Regards
Click to expand...
Click to collapse
I was told that you have to update to the latest version of FireOS and those versions are extremely broken. I can't use that unlock method unless someone finds a way to do it without updating to the latest firmware.

Sus_i said:
No, it isn't the package name. Most likely it's because an incompatible app theme (missing theme on all fireTV OS versions). If you want to know details, somewhere on xda is a guide, on how to use root/xposed together with xposed modules, as a workarround in order to open up the supersu app on fireTVs. A working theme was material dark, if I remember correct.
Idk why you state magisk isn't an option on 'this' box, since the BL unlock is out and really easy.
Anyway, have fun.
Click to expand...
Click to collapse
It's not an option because the unlock requires an update to the latest firmware (stock firmware) or so I was told.
If it's just the theme that is the issue could I just use Preferences editor to change it to a working theme?

Toothless_NEO said:
If it's just the theme that is the issue could I just use Preferences editor to change it to a working theme?
Click to expand...
Click to collapse
Probably not.
This is the old guide, mentioned above:
[PROTIP] How to get SuperSu, Xposed App Settings and other apps that dont open to run
Some apps like supersu or xposed app settings dont open on firetv. Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes. To fix those apps and make em run, you need...
forum.xda-developers.com

Sus_i said:
Probably not.
This is the old guide, mentioned above:
[PROTIP] How to get SuperSu, Xposed App Settings and other apps that dont open to run
Some apps like supersu or xposed app settings dont open on firetv. Apparently this is caused by the app theme which the firetv is missing. So its unable to open those apps with incompatible themes. To fix those apps and make em run, you need...
forum.xda-developers.com
Click to expand...
Click to collapse
Interesting, Why does It work to change the theme in Xposed and not through preferences and/or modding the app?

What features stop working when you unlock the bootloader?

From what I have found, SafetyNet and Netflix still work as they would with an unlocked bootloader (at least on LineageOS). Is there any camera or audio functionality missing? Can you still download and watch Netflix/Disney+ content?
I'm sure some of these questions were answered before I just want to be sure before I do something to my phone that I might not be able to change back

Nothing happens. you can use your phone as usual

itsfaiez said:
Nothing happens. you can use your phone as usual
Click to expand...
Click to collapse
Really? So you can still use banking apps and streaming services?

ivao said:
Really? So you can still use banking apps and streaming services?
Click to expand...
Click to collapse
Streaming services no problem. I don't know about banking apps.

itsfaiez said:
Streaming services no problem. I don't know about banking apps.
Click to expand...
Click to collapse
Are you using a custom rom or stock? This might be too much to ask but can you install a safetynet testing app (try https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample) and send a screenshot of the results? You can uninstall it after

I went ahead and unlocked the bootloader anyway and Widevine L1 and safetynet basic integrity remain. I forgot to copy the screenshots to my computer before installing LineageOS (oops).
On LineageOS Widevine L1 is still there and Netflix/Disney+ work perfect when downloaded from Aurora Store. I haven't bothered checking safetynet because I'm using MicroG meaning it won't pass anyway.