Related
Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
KingRoot appears to work on other 4th gen Amazon devices as well!
http://forum.xda-developers.com/kindle-fire-hdx/general/to-root-4th-gen-amazon-device-t3104853
One caveat:
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Hopefully someone more knowledgeable can resolve this, but until then
I've opted to install the Xposed Framework and LightningWall module in order to block KingUser's network activity.
najoor has found a way to replace KingUser via adb:
najoor said:
Instructions for replacing Kinguser with SuperSU are posted in the general forum:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
Click to expand...
Click to collapse
Also, hydromän pointed out that HDXPosed is working to enable widgets and block potential updates. Awesome!
hydromän said:
How to Block now Amazon Updates?
Fixed. Using xposed with hdxmodules. Now working all Launchers with Widgets and Updates Are disabled
http://forum.xda-developers.com/showthread.php?t=2618158
Click to expand...
Click to collapse
Granted! Root working!
z64 said:
Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
Everything seems to be working, however, I am not sure how safe KingRoot is actually.
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Maybe someone more experienced than myself could take a look at it.
Other than that, seems great.
Hope this bit of news helps!
Click to expand...
Click to collapse
Thanks z64 for the information about a working root for 4.6.1 (US Unlocked GSM) Fire Phone.
I would like to know if KingRoot 4.0 is really safe to use, and if will make a FULL or a PARTIAL root to the Amazon Fire Phone?
I also would like to know if after rooting, you will be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?
z64 said:
Greetings!
I was successfully able to root my US unlocked Fire Phone (on 4.6.1) by installing and running KingRoot 4.0!
Everything seems to be working, however, I am not sure how safe KingRoot is actually.
KingRoot installs KingUser as its superuser app, and KingUser appears to prevent the su binary from being overwritten.
Because of this, I have not yet been able to replace KingUser with SuperSU or similar.
Maybe someone more experienced than myself could take a look at it.
Other than that, seems great.
Hope this bit of news helps!
Click to expand...
Click to collapse
Is KingRoot a PC based program or a APK file? I'm Google searching now, just wondering which you used.
http://androidxda.com/download-kingroot-application
Choose 4.0
does this survive a reboot? that would be great news =)
After rebooting root checker report" ROOT" but you are right superSU is not working actualy it got installed but the SU binary upgrade failed
Can I go backward and UnRoot later the FirePhone to Default/Normal Original State??
Please, can someone that has already Rooted their Fire-Phone, if after rooting would be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?
ulises.rodriguez said:
Thanks z64 for the information about a working root for 4.6.1 (US Unlocked GSM) Fire Phone.
I would like to know if KingRoot 4.0 is really safe to use, and if will make a FULL or a PARTIAL root to the Amazon Fire Phone?
I also would like to know if after rooting, you will be able to go backward and UnRoot later the Fire Phone, to the default and normal original state?
Click to expand...
Click to collapse
I'm not sure what qualifies as a full or partial root; the bootloader is still locked, so no custom recovery or custom roms.
It is possible to unroot using the included KingUser app.
You have to uncheck "Backup Root permission" first to completely unroot it.
(Still haven't figured out how to replace KingUser with SuperSU while it's rooted.)
Viperise152 said:
Is KingRoot a PC based program or a APK file? I'm Google searching now, just wondering which you used.
Click to expand...
Click to collapse
I used the latest KingRoot 4 apk from kingroot.net/down
"KingRoot-4.0.0.233-release-201505071219_105001.apk"
drdoomgod said:
does this survive a reboot? that would be great news =)
Click to expand...
Click to collapse
It does survive reboot!
I just installed the Xposed Framework with LightningWall to control net access.
How to Block now Amazon Updates?
Fixed. Using xposed with hdxmodules. Now working all Launchers with Widgets and Updates Are disabled
http://forum.xda-developers.com/showthread.php?t=2618158
works !
Failed for me. Wouldn't install.
EDIT: Got it working!!
Sent from my SD4930UR using XDA Free mobile app
The question is what can we do with it now? Can we get rid of the lock screen and install a new settings apk??
TheDynamo said:
The question is what can we do with it now? Can we get rid of the lock screen and install a new settings apk??
Click to expand...
Click to collapse
Xposed framework is the first thing I did
Hi, i have the xposed framwork installed but not sure what to do with it lol
Instructions for replacing Kinguser with SuperSU are posted in the general forum:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546
Not sure why - but after following instruction (after rooting etc) tried to follow the guide for making phone look like normal android and thats when all hell broke loose on my phone. Unresponsive bottom button, wiget's not loading, super su showing nothing then refreshing a while later showing apps in there etc.
Kinda killed my phone so going to factory reset and start again.
This is great! I got the now launcher to work, although I'm not exactly sure how. I tried the supersu replacement and only made it to steps 6 and 7 mostly because I couldn't understand what exactly I was supposed to do, so step 8 didn't work and I'm still using the kingsu. I then d/l the now launcher and the google (search) apps, tried to run it a couple of times with no luck. Then force stopped the home app, restarted, and I was given the choice to use the now launcher.
Its easy. If u have root, convert Google Now Launcher and Google Search with Titanium Backup to a System App... And you can Choose Google Now Launcher.
This is great. I was able to fix my play store/services issues by changing my build.prop to nexus 5 after rooting. Awesome!
So this thread will be about the general state of Xposed on our shield TV's. If you have any questions or need help related to Xposed on the Shield TV, feel free to ask.
First Things First, Xposed does work on the 2.1 firmware. (If someone on the Vulcan preview could chime in about 3.0 that would be great.)
Steps to install Xposed on 2.1 (Assuming you already have a working recovery)
1) Download xposed-vXX-sdk22-arm64.zip and XposedInstaller_3.0_alpha4.apk from this thread.
either adb push it to /sdcard/ or use a thumb drive etc etc.
2) ADB reboot recovery
3) Preform a full backup IMPORTANT (I did 2 backups, one to internal storage, and another to external usb, better safe than sorry!)
4) Flash xposed-vXX-sdk22-arm64.zip (Wiping cache after is optional)
4) Reboot to system, Booting will take longer than usual, it took about 5 minutes on my 16gb, but could take longer.
5) Install XposedInstaller_3.0_alpha4.apk (ES file explorer works great for this, you can download it from playstore)
6) Open up Xposed installer once installed, select framework, and it should show Xposed framework version 80 is active. If not, repeat steps 1-4, If you're still having problems, ask here. From the installer you can install modules, just make sure to activate them and reboot!
Steps to install Xposed on 3.0 MM (with a working recovery)
1) Download xposed-vXX-sdk23-arm64.zip and XposedInstaller_3.0_alpha4.apk from this thread.
either adb push it to /sdcard/ or use a thumb drive etc etc.
2) ADB reboot recovery
3) Preform a full backup IMPORTANT (I did 2 backups, one to internal storage, and another to external usb, better safe than sorry!)
4) Flash xposed-vXX-sdk23-arm64.zip (Wiping cache after is optional)
4) Reboot to system, Booting will take longer than usual, it took about 5 minutes on my 16gb, but could take longer.
5) Install XposedInstaller_3.0_alpha4.apk (ES file explorer works great for this, you can download it from playstore)
6) Open up Xposed installer once installed, select framework, and it should show Xposed framework version 80 is active. If not, repeat steps 1-4, If you're still having problems, ask here. From the installer you can install modules, just make sure to activate them and reboot!
I've only tried 2 modules so far, one works, one doesn't. If You have tried a module and it does or doesn't work, please comment with the version and I'll add it to this list.
WORKING
NoSafeVolumeWarning V1.7 Stable (http://forum.xda-developers.com/xposed/modules/module-nosafevolumewarning-t2718933/)
App Settings (http://repo.xposed.info/module/de.robv.android.xposed.mods.appsettings) (Thanks Andy4Shurr)
Xprivacy http://forum.xda-developers.com/xposed/modules/xprivacy-ultimate-android-privacy-app-t2320783 (thanks Bradwatson and banderos101)
NOT WORKING
Youtube Adaway V3.1.1 (http://forum.xda-developers.com/xposed/modules/app-t2547316)
Reservado
happydish said:
Reservado
Click to expand...
Click to collapse
Also Reserved, just in case.
Hi,
Have you tried with shield 3.0? Does it works with systemless root?
Change in install procedure?
Thank you for your feedback
olivier.bossaer said:
Hi,
Have you tried with shield 3.0? Does it works with systemless root?
Change in install procedure?
Thank you for your feedback
Click to expand...
Click to collapse
Haven't tried it yet, been super busy with school, currently running 3.0 stock (not even rooted). If you try it, let me know if it works! I don't see why it shouldn't
olivier.bossaer said:
Hi,
Have you tried with shield 3.0? Does it works with systemless root?
Change in install procedure?
Thank you for your feedback
Click to expand...
Click to collapse
Nope, did not work for me
after flashing the zip it keeps booting forever
Arf!
I haven't time to test now.
But seems unfortunate...
Hope there will be a workaround!
Envoyé de mon Nexus 6 en utilisant Tapatalk
I installed Xposed on the 3.0 update. Had no issues. Also installed Xprivacy. Hoping to bypass mlb blackouts with mlb.TV.
I went through the standard process for installing it. Basically the exact steps of the OP but the newest version of the framework.
Sent from my XT1575 using Tapatalk
App Settings module works perfectly.
Xposed and root are working fine for me on 3.0 update, I'll write another guide maybe later today, but the steps are the same, just with the updated zip (SDK 23 for MM).
Brad, is Xprivacy working for you? Any problems?
happydish said:
Xposed and root are working fine for me on 3.0 update, I'll write another guide maybe later today, but the steps are the same, just with the updated zip (SDK 23 for MM).
Brad, is Xprivacy working for you? Any problems?
Click to expand...
Click to collapse
I can also confirm sucess with the sdk23 MM latest version and shield marshmellow
Xprivacy seems to be working well, except ondemand doesnt seem to pop up for any, or at least some, of the storage restrictions..........im not sure if xprivacy has been updated for marshmellow, so im not sure if storage restriction is working, i will pay attention next time i install an app from scratch........
Andy4Shurr said:
App Settings module works perfectly.
Click to expand...
Click to collapse
Andy can u help me.I have installed xposed and it says it is active.Than i instaled App Settings and when i try to change Dpi or other app setting nothing happens.(i have stock 6.0 ...3.0 rooted)
Installed root and xposed on 3.0 no problems, just needed to use pen stick because adaptive storage. Cannot seem to access the bootloader via hardware method (wait 3 secs then hold power button). I Tried many variations of it to no avail... Also I have to reflash the boot loader every time to access it. If I choose kernel recovery from bootloader it just shows the android with a warning / error.
Using Xposed mod Unbeloved Hosts and Lucky Patcher. Between the two I can filter 99% of all ads.
keep getting a error when tryin to flash with twrp on my nvidia shield tv whats is the corret zip for my device? Thanks all.
K I got Xposed installed MM 3.0 But when I use KODI if I have a stream playing it stops a few mins in, If I stop all of the modules in xposed and restart KODI Starts to work again, no probleems streaming. So it has to be Xposed or one of the modules I was using. Luck Patcher, App settings, Xprivecy, yourtube, MinGaurd (Not sure full name der) , YouTube AdAway.
Just installed the latest version of Xposed following the steps on the guide. I'm on 3.3 update, rooted. No problems so far. Will test some modules and report back.
joelcool69 said:
Just installed the latest version of Xposed following the steps on the guide. I'm on 3.3 update, rooted. No problems so far. Will test some modules and report back.
Click to expand...
Click to collapse
I finally unlocked my bootloader and rooted my Shield after using it for about a year. I use Xposed regularly on my Nexus 6P but wanted to know if anyone has information about Youtube Adaway Module working (or alternative). So far seems like it doesn't work everywhere.
Are there any other modules worth getting on Xposed for Android TV? Perhaps something for Xbox 360 Controllers?
Also would be very interested in Youtube HDR if anyone has a workaround seeing that it's supported officially by Youtube but their Youtube for Android TV app literally hasn't been updated since April so I take it we'll have to wait a few months. Not fun considering my 4K HDR tv has been waiting a year for this.
Thanks in Advance.
copticwalad said:
I finally unlocked my bootloader and rooted my Shield after using it for about a year. I use Xposed regularly on my Nexus 6P but wanted to know if anyone has information about Youtube Adaway Module working (or alternative). So far seems like it doesn't work everywhere.
Are there any other modules worth getting on Xposed for Android TV? Perhaps something for Xbox 360 Controllers?
Also would be very interested in Youtube HDR if anyone has a workaround seeing that it's supported officially by Youtube but their Youtube for Android TV app literally hasn't been updated since April so I take it we'll have to wait a few months. Not fun considering my 4K HDR tv has been waiting a year for this.
Thanks in Advance.
Click to expand...
Click to collapse
Well, Youtube Adaway Module it's working for me. About 1 hr of continuous playback and no one single ad. Xprivacy and Marshmallow SD Fix working too.
Now that Nougat has been out for months and Xposed not working on it, has anyone figured out a way to block Youtube ads? I know arter97 has patched youtube apks but nothing yet for the Shield.
Does Adguard work on Android TV?
Hey, just wondering if anyone can help, for the past week I've been trying to fix a problem with my Fire tv and have tried various methods to fix this issue. Basically I use Sloane 5.0.5 r4 ROM on my aftv 2, it comes with super su and the root does work as superuser requests pop up to allow or deny. However super su doesn't appear in apps (the GUI management tool) when installed (tried various versions of supersu from 2.4 to 2.7) and I try to launch it, it just takes me back to the home screen. From googling I can see a few others have a similar problem, some people suggesting kingroot(not keen to use that as it doesn't give me the same options as super su) some suggesting rbox will make an update to sort the problem. Although not something I know is definite. The super su works and it's binaries as suggested earlier but the gui tool is nowhere to be seen. Even tried changing sloanes rom and replacing it with another supersu version but this hasn't worked. Just to add more details im running TWRP recovery also!
Thanks.
Aaron-Marcus said:
Hey, just wondering if anyone can help, for the past week I've been trying to fix a problem with my Fire tv and have tried various methods to fix this issue. Basically I use Sloane 5.0.5 r4 ROM on my aftv 2, it comes with super su and the root does work as superuser requests pop up to allow or deny. However super su doesn't appear in apps (the GUI management tool) when installed (tried various versions of supersu from 2.4 to 2.7) and I try to launch it, it just takes me back to the home screen. From googling I can see a few others have a similar problem, some people suggesting kingroot(not keen to use that as it doesn't give me the same options as super su) some suggesting rbox will make an update to sort the problem. Although not something I know is definite. The super su works and it's binaries as suggested earlier but the gui tool is nowhere to be seen. Even tried changing sloanes rom and replacing it with another supersu version but this hasn't worked. Just to add more details im running TWRP recovery also!
Thanks.
Click to expand...
Click to collapse
It's something Amazon does to Android and SuperSU being a system app. I noticed the same problem with the Play Store. You might be able to launch it while in an alternative launcher and/or using adb shell.
Run a adb shell and fire up this one
pm path eu.chainfire.supersu
Just to check the installation path
Hey rbox! Many thanks for your reply, and well done on your effort with this rom, can't fault it except for this minor issue. Been tearing my hair out trying to figure out exactly why it all looks fine and well but won't launch. I was thinking of trying to install play store using xposed, was looking at a guide online and wondered if it would open through play store. Didn't realise I could use another launcher with your rom though. Do you know if there's others you know that understands amazon devices to come up with a fix, update etc? seems like you're the only one to make a rom so far for the aftv so I'm guessing it'll take time until everyone fully understands amazon devices and apply similar Android based roms. Thanks for your advice.
Here's what the path came back as, I did notice there's two different locations for supersu though.
correct me if i'm wrong but as far as i know the supersu (the one that you just found) is the su binary but the GUI (which is responsible for the grant notification) is here: /system/app/Superuser.apk
I'm not 100% sure about it, so maybe someone could light up the dark
once sloane-5.0.5-rooted_r4 is flasheed can we update SU from play store?
Sure but you don't have to. Just take that one http://apps.evozi.com/apk-downloader/?id=eu.chainfire.supersu
Sent from my Nexus 6 using XDA-Developers mobile app
Cool thks but i purchased the pro and thought i could update without breaking anything on the fire
ok i updateed to pro since it was allready purchased, all went well but dont know what it does more since i cant open the app loll, but it works, thats what counts
Habs69M said:
ok i updateed to pro since it was allready purchased, all went well but dont know what it does more since i cant open the app loll, but it works, thats what counts
Click to expand...
Click to collapse
My experience is with Firestick.
1) On main Amazon screen, go to the App line and look accros there.
2) Connect Wukong Remote https://play.google.com/store/apps/details?id=com.wukongtv.wkremote.client.en and you'll see the Apps selection at bottom.
I like to go into Supersu settings and the default to "Grant" and I like to turn off notifications.
king200 said:
My experience is with Firestick.
1) On main Amazon screen, go to the App line and look accros there.
2) Connect Wukong Remote https://play.google.com/store/apps/details?id=com.wukongtv.wkremote.client.en and you'll see the Apps selection at bottom.
I like to go into Supersu settings and the default to "Grant" and I like to turn off notifications.
Click to expand...
Click to collapse
thks cool app but i still cant open super su , dont know after reading some that you even can
Arghhhh. Think I've soft bricked my fire tv or worse! I was re flashing the rom and was cleaning the data before hand, I must of wiped the system and now I'm only seeing the amazon white logo when i turn it on... Tried to install recovery again since I can't even get into recovery but when going through preloader it eventually says error can't find target file. Tried to use fast boot but fire tv isn't connecting to try and install recovery etc that way! You guys got any ideas or have I totally broken the device? ???
Keep calm buddy, als long as the preloader is still working everything is possible. Did you try to Flash TWRP again?
http://forum.xda-developers.com/fire-tv/development/firetv-2-unbrick-image-t3313349
Thank you so much! It saved the day! never will i ever be such a n00b and delete the entire system again. Also big thankyou RBOX for your guide and files to unbrick, they worked a dream. Everything is installed now, hopefully in near future someone manages to get SuperSu opening in the GUI lol im just happy I can actually use my fire tv again though!
Update: Thanks to spotmark's discovery, DirecTV Now is working with root.
spotmark said:
Hide My Root Apk works. :good:
Click to expand...
Click to collapse
spotmark said:
Just installed and hid SU. I'm rooted on 5.0.5. Did you clear cache and data on Now after you installed Hide My Root?
Click to expand...
Click to collapse
There's a write-up and link to the apk for this on aftvnews: http://www.aftvnews.com/how-to-use-directv-now-on-a-rooted-amazon-fire-tv-or-fire-tv-stick/
If your rooted FireTV can't see the DirecTV Now app, use this link: https://www.amazon.com/AT-T-Services-Inc-DIRECTV/dp/B01J62Q632 and sign in to your Amazon account. On the right side, select your rooted device and click "Deliver".
----
Original post:
I signed up today for DirecTV Now only to be greeted on my FireTV with the following error:
Code:
This video failed to load. Restart the app and launch your content again. Or search for Error 40 in the Help Center. (QP1005)
Hrmm.. that's weird. So I looked up Error 40, and it says there's a network problem. I tried it on my non-rooted Nexus 6P and it worked flawlessly. So I jumped in to logcat and found some interesting messages:
Code:
I/drm_oal ( 4862): IsDeviceRooted: 0x0000000000000002
and
Code:
D/NewRelicGateway(14071): ERROR event was recorded. Error description = Failed preparing the player because device security check failed due to: (FileSystem)(com.quickplay.vstb.core:1005)
So I installed xposed and RootCloak 2 hoping it would help. I added it to the list of apps and it still had the same problem.
Next thing I did was pull the apk from my Fire TV. After some digging, I found that lib/armeabi/libdrmagent_downloadable_jni.so had some interesting strings in it, including a check for Cyanogen:
Code:
ro.build.product
ro.build.tags,release-keys,OnePlus3#%?OnePlus2#%?OnePlus#%?Z26CL#%?STUDIO_C,ro.build.type,user,#%?
ro.build.display.id,cm_,#%?,ro.build.display.id,cyanogen,#%?,ro.build.type,debug,#%?,ro.build.type,userdebug,#%?,ro.build.host,cyanogenmod,A0001#%?
and a list of strings for paths it might check:
Code:
/system/bin/su,#%?,/system/xbin/su,#%?,/sbin/su,#%?,/system/su,#%?,/system/bin/.ext/.su,#%?,/system/usr/we-need-root/su-backup,#%?,/system/xbin/mu,#%?
su,#%?,busybox,#%?
type %s
test -u `whence -p %s`
/data,#%?,/system,#%?,/system/bin,#%?,/system/sbin,#%?,/system/xbin,#%?,/vendor/bin,#%?,/sys,#%?,/sbin,#%?,/etc,#%?,/proc,#%?,/dev,#%?
/isdrmXXXXXX
Why do they even care if you're rooted?? So lame...
Since they appear to be checking for root in a C/C++ .so file, is Xposed useless here?
jkchr1s said:
I signed up today for DirecTV Now only to be greeted on my FireTV with the following error:
Code:
This video failed to load. Restart the app and launch your content again. Or search for Error 40 in the Help Center. (QP1005)
Hrmm.. that's weird. So I looked up Error 40, and it says there's a network problem. I tried it on my non-rooted Nexus 6P and it worked flawlessly. So I jumped in to logcat and found some interesting messages:
Code:
I/drm_oal ( 4862): IsDeviceRooted: 0x0000000000000002
and
Code:
D/NewRelicGateway(14071): ERROR event was recorded. Error description = Failed preparing the player because device security check failed due to: (FileSystem)(com.quickplay.vstb.core:1005)
So I installed xposed and RootCloak 2 hoping it would help. I added it to the list of apps and it still had the same problem.
Next thing I did was pull the apk from my Fire TV. After some digging, I found that lib/armeabi/libdrmagent_downloadable_jni.so had some interesting strings in it, including a check for Cyanogen:
Code:
ro.build.product
ro.build.tags,release-keys,OnePlus3#%?OnePlus2#%?OnePlus#%?Z26CL#%?STUDIO_C,ro.build.type,user,#%?
ro.build.display.id,cm_,#%?,ro.build.display.id,cyanogen,#%?,ro.build.type,debug,#%?,ro.build.type,userdebug,#%?,ro.build.host,cyanogenmod,A0001#%?
and a list of strings for paths it might check:
Code:
/system/bin/su,#%?,/system/xbin/su,#%?,/sbin/su,#%?,/system/su,#%?,/system/bin/.ext/.su,#%?,/system/usr/we-need-root/su-backup,#%?,/system/xbin/mu,#%?
su,#%?,busybox,#%?
type %s
test -u `whence -p %s`
/data,#%?,/system,#%?,/system/bin,#%?,/system/sbin,#%?,/system/xbin,#%?,/vendor/bin,#%?,/sys,#%?,/sbin,#%?,/etc,#%?,/proc,#%?,/dev,#%?
/isdrmXXXXXX
Why do they even care if you're rooted?? So lame...
Since they appear to be checking for root in a C/C++ .so file, is Xposed useless here?
Click to expand...
Click to collapse
I've read other posts from fellow rooted ftv users reporting the same thing. It would seem as if directv is following suit with PSVue in blocking rooted firetvs. It could be possible that it just won't run on any fireos older than 5.2.2.0
.
Same issue here. I hope someone figures out a workaround soon. I may just have to wait for my Apple TV to arrive.
d3adpool said:
I've read other posts from fellow rooted ftv users reporting the same thing. It would seem as if directv is following suit with PSVue in blocking rooted firetvs. It could be possible that it just won't run on any fireos older than 5.2.2.0
.
Click to expand...
Click to collapse
I was able to get the PSVue up and running using RootCloak but ended up cancelling it due to them ditching Viacom.
Hide My Root Apk works. :good:
spotmark said:
Hide My Root Apk works. :good:
Click to expand...
Click to collapse
Ahh nice! I will try it out tonight when I get home. Thanks!:highfive:
spotmark said:
Hide My Root Apk works. :good:
Click to expand...
Click to collapse
What did you do to get it to work? I installed Hide My Root 4.0 and hid the su binary but it still doesn't work.
ryknow27 said:
What did you do to get it to work? I installed Hide My Root 4.0 and hid the su binary but it still doesn't work.
Click to expand...
Click to collapse
Just installed and hid SU. I'm rooted on 5.0.5. Did you clear cache and data on Now after you installed Hide My Root?
spotmark said:
Just installed and hid SU. I'm rooted on 5.0.5. Did you clear cache and data on Now after you installed Hide My Root?
Click to expand...
Click to collapse
That did it. Thanks!
I tried Hide My Root 4.0 on a nexus 6 with android 7.0 and the app i guess doesn't work on on 7.0. Which makes sense since it hasn't been updated since 2013. It can't find my root at all.
I ended up just unrooting to try directtv now since I am currently not using the root for anything specific, but obviously I am going to want to root my phone again. Hopefully there is something found to bypass this on android 7.0.
Not even sure why they want to stop root users. I paid just like everyone else. Why crap on us? I am definitely less likely to recommend the service in the future.
eureca said:
I tried Hide My Root 4.0 on a nexus 6 with android 7.0 and the app i guess doesn't work on on 7.0. Which makes sense since it hasn't been updated since 2013. It can't find my root at all.
I ended up just unrooting to try directtv now since I am currently not using the root for anything specific, but obviously I am going to want to root my phone again. Hopefully there is something found to bypass this on android 7.0.
Not even sure why they want to stop root users. I paid just like everyone else. Why crap on us? I am definitely less likely to recommend the service in the future.
Click to expand...
Click to collapse
I believe I saw someone post that Sony does it as well with Vue.
spotmark said:
Just installed and hid SU. I'm rooted on 5.0.5. Did you clear cache and data on Now after you installed Hide My Root?
Click to expand...
Click to collapse
This didn't work for me for some reason. I have a 6P that's still on 6.0 due to Xposed. I was able to get around ps vue with root cloak though.
I unrooted my phone just so I could test it out, but it still doesn't work for me because I'm on CM13.1 and I think there is a check on Cyanogen too? That really sucks, I hope someone figures a way around it.
I've tried using RootCloak with the keyword 'cyanogen' added to the blacklist as well as the string 'com.att.tv' added to the list of apps to block, alas without any success.
I also tried suhide with a fresh install of Marshmallow and systemless root, but it didn't work.
I am currently running 6.0.1, rooted 2.76, with Xposed installed.
loloudoudara said:
I've tried using RootCloak with the keyword 'cyanogen' added to the blacklist as well as the string 'com.att.tv' added to the list of apps to block, alas without any success.
Click to expand...
Click to collapse
In the nexus 6p section someone found out that changing build prop got it to work.
http://forum.xda-developers.com/showpost.php?p=69885082&postcount=2
venelar said:
In the nexus 6p section someone found out that changing build prop got it to work.
http://forum.xda-developers.com/showpost.php?p=69885082&postcount=2
Click to expand...
Click to collapse
This didn't work for me.
The build prop edit didn't work for me either
venelar said:
In the nexus 6p section someone found out that changing build prop got it to work.
http://forum.xda-developers.com/showpost.php?p=69885082&postcount=2
Click to expand...
Click to collapse
I have a Nexus 6P and use Magisk Hide to get the app to stream. After flashing Magisk v9 and enabling Magisk Hide, I rebooted the phone and added the Directv NOW app. Works perfectly.
Sent from my Nexus 6P using Tapatalk
xstahsie said:
I have a Nexus 6P and use Magisk Hide to get the app to stream. After flashing Magisk v9 and enabling Magisk Hide, I rebooted the phone and added the Directv NOW app. Works perfectly.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I tried this on my Nexus Player and still didn't work
montajd said:
I tried this on my Nexus Player and still didn't work
Click to expand...
Click to collapse
Could you outline the steps that you took?
xstahsie said:
Could you outline the steps that you took?
Click to expand...
Click to collapse
Installed Magisk v9 manager, and flashed Magisk zip in TWRP. Still get the error 40 qp1005 error. Oh yeah, and enabled Magisk Hide and selected Directv Now. Now I will mention that I also have superSU and Xposed installed if that makes a difference
Filmstruck app on FTV1 rooted with 5.2.4.1r2 rom - 573210720
Menu selections starts at top (Filmstruck) goes down to browse, then settings. Going back up, it goes to browse, then to Criterion Channel. So can not access Watchlist or Search, and can only access Filmstruck after first opening the app. If you have already gone down a menu selection, you can't go back up to it. I don't remember which version this issue started with but I tried going back a couple rom versions with the same results.
Can anyone else confirm this on theirs or have any idea how to fix it? I have 2 FTV1 boxes and an FTV Stick 1, all rooted. I'd hate to have to go back to stock for one app but since I'm paying for the service (Filmstruck) I may have to.
Video of how it is not working https://youtu.be/uz_JEjfbv18
For what it's worth I did try older versions of the app as well as side loading the app from my kindle fire HD 8 tablet (rooted) where it works just fine. Also works fine on my phone running android nougat and PC. The side loaded app would just start to open and then close.
New versions for Amazon and Google Play - no fix
So there was an update to the Filmstruck app 3.1.1 on Amazon Appstore and 3.1.0 on the Google Play Store. Same results exactly. Both versions work fine on the tablet. Both versions have same exact menu navigation issues on the FTV 1. I'm about to throw in the towel and just give up being rooted and go back to stock. I'd really like to confirm that would be the solution before I go that route though. Can anyone else confirm they do or don't have this issue on their rooted FTV1 or if it works fine on unrooted? Right now all I can do is play it on my tablet and cast to the TV which is pretty frustrating. Thanks in advance for any thoughts on this.
Works fine on new unrooted FTV STick 2
OK, the suspense was killing me so I went and bought a Fire TV Stick 2 for testing. Opened up network so it would take updates if it needed them, set it up, installed the Filmstruck app, and everything worked perfectly. (Except I couldn't adjust the video scaling, but that's just because I have an old TV)
So I guess this confirms there is an issue with the Filmstruck app and the latest prerooted rom versions for the FTV1 and FTV1 Stick.
Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.
drewb0y said:
Finally decided to pull the trigger on unrooting and going back to stock on the FTV Stick 1 that I had. Now the Filmstruck app works perfectly as it should. Hopefully someone can figure this out before I just give up and toss root out the window on my other two FTV 1 boxes.
Click to expand...
Click to collapse
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.
Y314K said:
One option is to keep TWRP & root access but remove the SU folder from the PreRooted ROM before flashing. This will have u running unRooted (no SU manager) with the option to flash SU or root access in the future. Just make sure you are still blocking updates probably thru Method 2.
Click to expand...
Click to collapse
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.
drewb0y said:
I will try that out while I'm in the process of unbricking one of my other FTV 1 boxes. Didn't realize it would be as simple as removing the su folder. I'll report back with my findings. I'm surprised no one else had this issue reported yet. There's an awesome library of movies available with that app.
Click to expand...
Click to collapse
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.
Y314K said:
Will have to try that App out. Thanks for the heads up. RBox mentioned that was possible even before the PreRooted FireOS 5 Rom's started to come out. And a few folks have mention success. As long as the updates are blocked. You should be able to keep updating the ROM as long as you remove the SU folder. Best of both worlds.
Click to expand...
Click to collapse
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!
drewb0y said:
Well it took some major convolutions on my part but that was mostly because the box I was working with was on old CWM with the boot menu and stuck in a reboot loop. After finally getting the zip without su pushed over, TWRP would say the file was corrupt. I originally used the windows built in zip manager. After redoing it with WinRAR it all loaded perfectly. On reboot I had to reregister, reinstall the app, and guess what? It works perfectly now. So I'm on the latest ROM 5.2.4.1r2 minus the su folder. Thanks a ton!
Click to expand...
Click to collapse
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...
Fixed
Y314K said:
Did u used a MD5 file for verification of the modded zip? That never worked for me last time I tried. Guess something was hard coded.
Make sure you verify you got at least the Method 2 of update blocking working. TWRP should also block updates. But at least one extra Method is good for piece of mind.
And don't forget to share the knowledge...
Click to expand...
Click to collapse
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!
I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.
drewb0y said:
No MD5 file as it would not match with the SU folder removed. It would be a different size. I do have the update domains blocked through the router as well as through my Pi-Hole network wide ad blocker. So two layers there. That and there may not be any updates for FTV1 any time soon. Thanks again!
Click to expand...
Click to collapse
drewb0y said:
I could create an MD5 file and post that as well as the zip with the SU folder removed if you want to try it out.
Click to expand...
Click to collapse
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.
Y314K said:
No problem. I tried to create a new MD5 file before to match the modded ROM. But there seem be something hard coded. Since it would still fail in TWRP. That is why I asked.
Click to expand...
Click to collapse
Gotcha. It seemed to load just fine without the MD5.
Well it worked for a few weeks and then back to the same behavior as before. Going to try unrooting again.