Researching the Kindle Fire's 'no Amazon Video with root' lock - Kindle Fire Android Development

So it's a bit rubbish that you can't use Amazon Video on your Kindle Fire if it's rooted. I don't want to steal movies, crack DRM or anything else, I just want to have a rooted device to use with my Amazon Prime VOD feature. Bit harsh imho. Sooooo.... I thought i'd have a poke around and see what I could find out.
What I found was a very complex web of protection on a scale above anything i've seen an Android app before. Not only does the application check for root in more that one location (in the application itself and in the native library), it also performs tamper detection on the APK. Not only that but it also checks that the signature on the APK to check that no code has changed (if you change the code in classes.dex and drop it in, this is usually OK on a /system/app file, but not in this case). The code itself doesn't have a single, uniform tamper / root check function, it does it all over the place. Finally, just to make things even more difficult, key parts of the code are pretty heavily obfuscated to make the code hard to analyse / modify.
Despite this, I thought i'd see what I could achieve by patching it piece by piece with the goal of allowing video with root.
The first step was to work out how to get around the signature check. Without sorting this out, the app would immediately flag up as being tampered if I made ANY change to the code. The answer to this was to re-sign the Amazon Video APK, ATVAndroidClient.apk. Of course we don't have the Amazon certificates, so we can sign them with our own, or with SDK certificates. Since Amazon Video uses a shared user id, other APKs need to be signed too. The full list is ATVAndroidClient.apk, KindleForOtter.apk, OtterTutorial.apk, AmazonVenezia.apk, Launcher.apk, Windowshop.apk, CSApp-unsigned.apk, MyAccount-unsigned.apk, amazonmp3-unsigned.apk, Cloud9-unsigned.apk, OOBE-unsigned.apk, com.amazon.dcp.apk, Cloud9SystemBrowserProvider-unsigned.apk, OTASilentInstall.apk, Facebook.apk and OtterAppManager.apk.
After doing this, the next step is to patch out the tamper checks. This can really only be achieved by tracing where the app goes and how it works and by carefully analysing logcat to get clues as to where the errors are happening. Since i'm in the UK I also had to use a DNS proxy with a static IP... I used unblock-us which works a treat. Eventually I got to a stage where I got the application to ignore any tamper detections, thereby enabling the various 'Watch' buttons.
In the next step I could see what something was triggering another problem, and it turned out to be detection of root. This was happening in one of the more obfuscated bits of code, but again with careful tracing I managed to find this and patch it out.
At this point the application was loading, passing tamper checks, giving me the watch buttons, requesting the stream from Amazon and giving me the loading progress bar etc... BUT... the licence request to Amazon continually failed. This is the point where I came to something of a brick wall. It appears that there is some additional root checking going on in the native library, and unfortunately, reverse engineering this is beyond both my abilities and more important the time I have available, so we don't have a fully working solution.
The positive things though are that we now have a patchable Amazon Video APK, which means we can implement the functionality of the 'root keepers' within the app itself. We can effectively make the Amazon Video APK hide the su binary from itself on launch and put it back after it's run it's checks. Not ideal, but might be the best way to go. Note that the root check doesn't care about the Superuser APK, it only checks for 'su'. It checks in all the locations in the PATH variable, so moving it to, say. /system/root and adding that to the path won't help. Unfortunately.
For now, I have to put this on the back burner, but i'm posting my patched APK below so that if anyone wants to pick up the work of reversing the native binary they can do so, simply by using this APK and re-signing it and the other APKs mentioned above.
Any questions, feel free to ask them here. Obviously I have no interest in saving streams, downloading movies or any stupid stuff like that, so don't even ask.
P
DOWNLOAD - MD5: f6044dbeffa4eb3f8361c71a96683150

send to kindle - passage through amazon servers
Apologies if this seems off off topic but I believe it may tied to your explanation of the security at Amazon --
http://forum.xda-developers.com/showthread.php?p=21366426#post21366426
As proof of concept Ive been messing around with the SendtoKindle.exe from the desktop explorer -- and have failed to get anything worthwhile past the amazon servers.... to see if I can use the Send to Kindle to get say, a rom file or binary kernel or apk or something of that sort -- and have not been able to get anything past.
The fact that everything is failing is only making me want to keep trying different things -- which Ill just keep on trying.. so i will try different things -
Ive sent 40 different documents of all kinds to see what goes through and what doesnt... and the only things that are going through are basically legitimate items.
If this is entirely irrelevant to your quest, then my apologies -- but regardless I shall enjoy observing how you shall achieve your success Paul!

Solved. Its hacky, but I've confirmed it working. http://rootzwiki.com/topic/15134-how-to-get-amazon-prime-video-working-with-rooted-stock/

infinitybiff said:
Solved. Its hacky, but I've confirmed it working. http://rootzwiki.com/topic/15134-how-to-get-amazon-prime-video-working-with-rooted-stock/
Click to expand...
Click to collapse
No offense but this has been around for awhile and is known as a workaround. This thread is about finding a solution instead of having to use a workaround I suppose.
Here is an example of a thread posted in November with this information.
http://forum.xda-developers.com/showpost.php?p=19718688&postcount=6
And another thread in December.
http://forum.xda-developers.com/showthread.php?t=1414235

G1ForFun said:
No offense but this has been around for awhile and is known as a workaround. This thread is about finding a solution instead of having to use a workaround I suppose.
Here is an example of a thread posted in November with this information.
http://forum.xda-developers.com/showpost.php?p=19718688&postcount=6
And another thread in December.
http://forum.xda-developers.com/showthread.php?t=1414235
Click to expand...
Click to collapse
Late to the party i suppose
Sent from my SGH-I897 using XDA App

What ROM were you testing on? Even if you temp unroot with RootKeeper on CM7, Amazon Video will not work (in my experience). The Watch button is always greyed out.

Takenover83 said:
What ROM were you testing on? Even if you temp unroot with RootKeeper on CM7, Amazon Video will not work (in my experience). The Watch button is always greyed out.
Click to expand...
Click to collapse
Have you tried force closing the video app and restarting it while unrooted?
Also does video work on CM7? I have not installed it to try.
Sent from my E4GT using xda premium

mkuehn10 said:
Have you tried force closing the video app and restarting it while unrooted?
Also does video work on CM7? I have not installed it to try.
Sent from my E4GT using xda premium
Click to expand...
Click to collapse
Yep, sure did. Something about CM7 that amazon does not like

Takenover83 said:
Yep, sure did. Something about CM7 that amazon does not like
Click to expand...
Click to collapse
I'm sure it's more than just the Amazon video app you will need to get this working...what apps are installed and are they on the system partition. Can you keep us posted on your progress?

B3L13V3 said:
I'm sure it's more than just the Amazon video app you will need to get this working...what apps are installed and are they on the system partition. Can you keep us posted on your progress?
Click to expand...
Click to collapse
There was 3 or 4 apks I had to install. Cant remember all the names off the top of my head. I know some account apk just to sign into amazon, video. I wish I could be more helpful but do not have my Pc in front of me right now (out and about). But the app its self was runing just fine. I Just was being blocked (even though I unrooted.)

Related

[Guide] Activate Windows 8 Permanently

UPDATE: Personalization does NOT work in METRO. Everything works flawlessly and I tend to stay in desktop mode so I didn't realize this. DESKTOP MODE CAN BE PERSONALIZED. This still gives you enables everything I wanted so I don't see the problem. My metro background doesn't matter to me. I can also just install a win7 start menu, but again I have no issues and this works flawlessly.
A tool called "Windows 8 Activator For Build 9200 (Sep 2012)" (Google it, LINK BELOW) will permanently activate Windows 8. Specifically the latest build. Just run it and follow the simple instructions.
MOD EDIT: WAREZ LINK REMOVED
atrix4g18 said:
Let me know if we can't post this guide even though it is just providing information and no links to anything.
A tool called "Windows 8 Activator For Build 9200 (Sep 2012)" (Google it, LINK BELOW) will permanently activate Windows 8. Specifically the latest build. Just run it and follow the simple instructions.
If this doesn't comply with forum rules let me know. There is another thread describing how to remove activation watermark and notification, this does the same thing but actually removes it instead of hiding it.
Click to expand...
Click to collapse
The comments seem to be all over the place, I don't see definite proof it will work.
Isn't this classed as warez and is completely banned by xda, why would you want to steal windows 8 anyway? The upgrades only like £20 & I've tried the rtm on a friends pc, its awesome!
Sent from my HTC Desire HD using xda app-developers app
eZaCx said:
The comments seem to be all over the place, I don't see definite proof it will work.
Click to expand...
Click to collapse
idk what to say. I'm no expert tell me a way to show you that my windows 8 copy is fully activated and I'll show you. It worked perfect you dont't need anything complicated. It opens command prompt and works.
scaryshark said:
Isn't this classed as warez and is completely banned by xda, why would you want to steal windows 8 anyway? The upgrades only like £20 & I've tried the rtm on a friends pc, its awesome!
Sent from my HTC Desire HD using xda app-developers app
Click to expand...
Click to collapse
Understood. However for people who want to use all the features so they download the newest build (9200) but they run into activation watermarks and notifications. When Windows 8 comes out (October 26th) aka a long time from know, I will most likely buy a licence if not a Surface.
For now however this works. This gives you Windows 8 as it will be on October 26th. working perfectly. I have it on my Acer Aspire One 722 netbook and it works flawlessly AMD has a consumer driver preview for Windows 8 and everything runs smooth.
Apparently this still won't let you personalize. OP pm me plz.
Sent from my HTC One XL using xda premium
ptesmoke said:
Apparently this still won't let you personalize. OP pm me plz.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
What do people mean "won't let your personalize."? Is there something I am missing?
Also OP, how do you know it was permanently installed, and not 90/180 days?
>Isn't this classed as warez
No, it's classified as malware, as in "let's infect all the dumb pirates desperate for keys". Kiddies need to learn about social engineering at some point, and this is a good time as any.
ptesmoke said:
Apparently this still won't let you personalize. OP pm me plz.
Click to expand...
Click to collapse
Same problem here, please contact me if you found a solution.
it doesn't let you personalize because Win8 isn't really activated, even though the messages tell you it is. The system files have been tempered with. Read more on MDL about this. It has been shown many times that it fakes activation.
http://forums.mydigitallife.info/th...if-any/page466?p=630762&viewfull=1#post630762
if you do a sfc /scannow and reboot you will see that your system is not activated. If you feel comfortable with it you can keep the files, however you need to realize that you are in fact not activated.
(to find out whether personalization works or not, got to the metro screen, move mouse bottom right corner to open settings in the charm bar, at the bottom you see Change PC settings, try to personalize Lock screen, start screen, account picture - if you are activated you have no problems here, if you are not it's likely greyed out)
best solution to get activated at the moment is to wait for a KMS server or wait until Oct26 to purchase it. You can try to register a PC you may purchase or already purchased here and hope that you only have to pay $15 when it comes out (for a PC you haven't actually purchased). It may or may not work. Many believe that MS won't be able to check that many registered PCs to see if these have actually been recently purchased. We will see.
good luck
eZaCx said:
What do people mean "won't let your personalize."? Is there something I am missing?
Also OP, how do you know it was permanently installed, and not 90/180 days?
Click to expand...
Click to collapse
Windows, not the program confirmed it was permanently activated. This is not kms... this is all done locally.
e.mote said:
>Isn't this classed as warez
No, it's classified as malware, as in "let's infect all the dumb pirates desperate for keys". Kiddies need to learn about social engineering at some point, and this is a good time as any.
Click to expand...
Click to collapse
484 thanks? And you are that ignorant? Please grow up. This requires build 9200. Not the consumer version and it works flawlessly.
9200 build, is it a final version ?
Sent from my GT-I9100 using Tapatalk 2
derausgewanderte said:
it doesn't let you personalize because Win8 isn't really activated, even though the messages tell you it is. The system files have been tempered with. Read more on MDL about this. It has been shown many times that it fakes activation.
http://forums.mydigitallife.info/th...if-any/page466?p=630762&viewfull=1#post630762
if you do a sfc /scannow and reboot you will see that your system is not activated. If you feel comfortable with it you can keep the files, however you need to realize that you are in fact not activated.
(to find out whether personalization works or not, got to the metro screen, move mouse bottom right corner to open settings in the charm bar, at the bottom you see Change PC settings, try to personalize Lock screen, start screen, account picture - if you are activated you have no problems here, if you are not it's likely greyed out)
best solution to get activated at the moment is to wait for a KMS server or wait until Oct26 to purchase it. You can try to register a PC you may purchase or already purchased here and hope that you only have to pay $15 when it comes out (for a PC you haven't actually purchased). It may or may not work. Many believe that MS won't be able to check that many registered PCs to see if these have actually been recently purchased. We will see.
good luck
Click to expand...
Click to collapse
Interesting. I am not losing any functionality however so can you explain more? I don't see that personalization menu but I can personalize themes and stuff exactly like windows 8. Games work, net framework is functioning so I don't see what I'm missing out on...
UPDATE: Personalization does NOT work in METRO. Everything works flawlessly and I tend to stay in desktop mode so I didn't realize this. DESKTOP MODE CAN BE PERSONALIZED. This still gives you enables everything I wanted so I don't see the problem. My metro background doesn't matter to me. I can also just install a win7 start menu, but again I have no issues and this works flawlessly.
atrix4g18 said:
UPDATE: Personalization does NOT work in METRO. Everything works flawlessly and I tend to stay in desktop mode so I didn't realize this. DESKTOP MODE CAN BE PERSONALIZED. This still gives you enables everything I wanted so I don't see the problem. My metro background doesn't matter to me. I can also just install a win7 start menu, but again I have no issues and this works flawlessly.
Click to expand...
Click to collapse
the more important point is that you are not activated. System files have been replaced and sooner than later with a Windows Update these files will be fixed. Just letting you know and that you are aware of it. The system "fakes" activation - period. It spoofs some strings and flips some "switches" to make things appear that you are activated when in fact you are not.
You can do everything else without Win8 activation as well and use the system forever. You have the watermark and a reminder to activate. You can remove the watermark and activation reminder with the remover somebody made . However, that patch will not report that you are activated, it will only remove watermark and bypass activation message. Your OP reports on a nasty (not only my opinion) patch that replaces some system files that actually fake activation. You should at least change the statement that it will permanently activate Windows8, this is not true and has been proven to be fake (see MDL posts).
I personally don't like patches that replace system files that I am not aware of and that claim to give you activation when in fact it replaces text within dll's that fool you. If you want to be informed on how to activate Win8 I suggest reading the MDL forum about Win8 activation.
atrix4g18 said:
484 thanks? And you are that ignorant? Please grow up. This requires build 9200. Not the consumer version and it works flawlessly.
Click to expand...
Click to collapse
as much as I don't like his attitude, he is correct that it is malware.
It is not ACTIVATED! I downloaded to try and downloaded Microsoft something. I forget what its called but it checks for stuff on your computer that is not activated and Windows 8 was on there and said Windows 8 is not genuine. SO there you go.
I did manage to activate it permanently though by getting a serial number off a youtube vid and activate via UK Microsoft number and worked WITH personalize working!!!!
THIS IS ILLEGAL. DO NOT POST CRACKS FOR ACTIVATING WINDOWS.

Ignore/hide app update

I have an app (calorie counter) that keeps showing a notification there is an update. I don't want to update it because the new permissions seem intrusive (allowing hardware controls - take picture and video).
Does anyone know how I can disable getting a notification about the update?
Cheers,
Open Google play, go to settings and uncheck " notifications" option.
Sent from my Galaxy Nexus using xda premium
That will turn off notifications for all apps though, which I'd rather not do.
Sent from my Galaxy Nexus using Tapatalk 2
Gucci.Nexus said:
That will turn off notifications for all apps though, which I'd rather not do.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You could use titanium backup to disassociate the app with the Google Play store. I've personally never done it myself, but I think this is the solution you're looking for
Sent from my HTC One XL using xda premium
Gucci.Nexus said:
That will turn off notifications for all apps though, which I'd rather not do.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You can also specify it on a per app basis. Just open the app in Google play and uncheck the checkbox.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
You can also specify it on a per app basis. Just open the app in Google play and uncheck the checkbox.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No, you can't
The only check box is for Automatic Updates, not update notifications.
Go to settings, apps, select the app, uncheck notifications.
Solution by using ZipSigner 2
I just came across a solution (android.stackexchange.com/a/25527)
If you've got root access and have the original apk of the version you want to keep at hand (via Titanium backup or copied out of your \data\app folder), you can use ZipSigner 2 to give that apk a different key (auto-testkey).
When you install the apk with its new key, the Play Store will not recognize the installed app and will therefore not try to search or push any updates. :good:
ZipSigner 2 is available for free in the Play Store: play.google.com/store/apps/details?id=kellinwood.zipsigner2
If you have root, you can simply use ti backup to detach an app from the market.
It was assumed op doesn't have root though.
Sent from my Galaxy Nexus using Tapatalk 2
Petrovski80 said:
If you have root, you can simply use ti backup to detach an app from the market.
Click to expand...
Click to collapse
It was my understanding that detaching an app in Titanium does not work anymore since an update from Google Play has more checks on the server side.
http://www.titaniumtrack.com/changelog/titanium-backup/4-8-4-1
Djezpur said:
I just came across a solution (android.stackexchange.com/a/25527)
If you've got root access and have the original apk of the version you want to keep at hand (via Titanium backup or copied out of your \data\app folder), you can use ZipSigner 2 to give that apk a different key (auto-testkey).
When you install the apk with its new key, the Play Store will not recognize the installed app and will therefore not try to search or push any updates. :good:
ZipSigner 2 is available for free in the Play Store: play.google.com/store/apps/details?id=kellinwood.zipsigner2
Click to expand...
Click to collapse
Thanks for this. What a quick and easy solution. Now I can keep the old Foursquare without getting it automatically updated to that new version.
Please note: ZipSigner 2 does not require root!
The solution probably still works. Thanks for the hint!
Now I did test it.
1. Use App Backup and Restore to save the apk
2. Use Zipsigner to give the apk a different autokey
3. Uninstall original app
4. Install the apk modified by Zipsigner, you may need some file manager like TotalCommander for this
It is all possible without root and works well
Gucci.Nexus said:
I have an app (calorie counter) that keeps showing a notification there is an update. I don't want to update it because the new permissions seem intrusive (allowing hardware controls - take picture and video).
Does anyone know how I can disable getting a notification about the update?
Cheers,
Click to expand...
Click to collapse
I know this is an old thread. And I understand that Ti Backup used to work for detaching an app from Play Store. But I also understand that this works no longer. For those who are interested, I have created an app that does a pretty good job of this. It is called Hide Updates In Play Store. There is a video showing the app at work. It does require a rooted device. Thanks
Let me summarize:
- it costs money
- it needs root
- it needs an additional app
- the solution may not persist if you uninstall the controlling app
All these disadvantages can be avoided by reading just one posting higher ...
tag68 said:
Let me summarize:
- it costs money
- it needs root
- it needs an additional app
- the solution may not persist if you uninstall the controlling app
All these disadvantages can be avoided by reading just one posting higher ...
Click to expand...
Click to collapse
You are, of course, correct in the disadvantages. But the above method has its own limitations:
1) I wonder how/if it will work with system apps unless you have root. For instance, I actually wanted to get rid of updates to Google Search since later versions hose-up Utter.
2) It is something of a pain to "undo" since you will loose any settings or data (unless you are VERY CAREFUL) related to the app when you uninstall the "fake-signed" app and re-install the "real" app. Of course, this would also happen during the install of the "fake-signed" app in the first place. In some cases, this may be trivial but in others, it may not. And App Backup/Restore - which I use - fine app - only processes the .apk file.
3) It requires a minimum 2 apps be installed.
4) It isn't terribly easy to do. Developers would likely be able/willing to handle this - or even know what signing is or what to do. But how about others? The first one would be hardest for sure.
Like my solution, it also seems not likely to work with paid apps or apps having in-app purchases. I am not 100% sure, but would guess that the re-signing will mess up most Play Store license checking. Indeed, App Backup/Restore handles these differently and with far less functionality.
Still, for someone who is willing to do it and for those lacking root, the solution suggested above seems like it will work and those who are rooted can certainly save that $1 which can be used to make a one-time purchase of maybe 1/2 cup of coffee at the nearest Starbucks
Cheers!
David, if you would have mentioned the possibility of resigning in the description of your app, maybe even give the manual how to do without your app, I'd much more be willing to believe and support you.
Without that hint it has a little smell of betraying for me, not showing people who do not know better or do not have root that there are cost-free alternatives. But probably I have just to admit that you seem to be good at selling. I usually don't like people who are good at selling.
tag68 said:
David, if you would have mentioned the possibility of resigning in the description of your app, maybe even give the manual how to do without your app, I'd much more be willing to believe and support you.
Without that hint it has a little smell of betraying for me, not showing people who do not know better or do not have root that there are cost-free alternatives. But probably I have just to admit that you seem to be good at selling. I usually don't like people who are good at selling.
Click to expand...
Click to collapse
First, I developed and posted my app on Play Store before I even saw this forum thread with its reference to resigning apps. So I was not aware at the time.
Second, I still have not even tried to confirm that the re-signing approach will work (although I can see that it might). I will take the word of the person who posted this technique that it does indeed work. But I now have a solution that I like and use. So I have no real need to find and test other solutions.
Third, there are often many possible solutions to a given problem. In fact, my original approach to this particular problem was done via Tasker and shell scripts. It worked but was not particularly user friendly. I tried to remedy that in my app. It seems you are saying that a person (me) choosing to implement one possible solution must also run down, verify, and advertise all other approaches. If so, I think that is a bit ridiculous and would appreciate a list of examples of app authors who are doing this who you do "believe and support." I do not think it is very common.
Fourth, I found this thread via a google search. I think it is fair to believe others will as well if they are seeking alternative approaches. So they too can learn about the resigning approach and decide for themselves how to proceed. I never claimed (here on in my app) that mine is the only approach. I never say it is the "best" approach. I do not denigrate proponents of other approaches. I only implemented one approach that seemed reasonable to me. I posted here so others who suffer from this weakness in Play Store can, if they wish, can check it out for themselves. Play Store gives buyers 2 hours or so to test the solution and decide if it works for them. If not, they are free to return the app and cancel the sale and charge.
Fifth, if you check my list of apps on Play Store, you will see that they are all very small apps and all are either free or very low cost. All of these apps were the result of my trying to resolve situations that I found personally irritating. I then thought that maybe others would find them useful as well. If you look at the number of installs for all of my apps combined, I think you will find that I am NOT at all good at "selling". Indeed, if the net proceeds from all of my paid apps combined exceeded much more than $300 total it would be a miracle. With programming, testing, and support time this likely works out to be maybe $0.10 per hour. I figure the market for this app will be no larger than my previous apps and at $1 per sale, it will be a while before I can use the proceeds to buy even a six pack of beer (especially after Google takes their cut). So I can hardly be considered a successful salesman. If only that were true! I do sell some of my apps. But truth be told I really do this, not for the money, but so I can show some revenue to the tax authorities so they permit me to write off some computer-related expenses.
I am sorry you feel "betrayed" by me somehow. And I am sorry that you have somehow decided that you don't like me for the rather limited reasons you have managed to list here. I really do not think I have given you or anyone else cause to reach such conclusions. It really makes me kind of sad. But you are entitled to your opinions and I will leave it at that as I walk away in wonder.
You admit that you googled where you could post ads for your app, did not even have a look what was last written in the thread and then sent your ad? In my opinion that IS Spam, nothing else ...
So thank you for the offer, and for staying away from this thread in future. For everyone who needs a good working solution free of cost and less use of resources but with a bit more manual handling of apk-files, have a look at posting #13 of this thread.
Djezpur said:
I just came across a solution (android.stackexchange.com/a/25527)
If you've got root access and have the original apk of the version you want to keep at hand (via Titanium backup or copied out of your \data\app folder), you can use ZipSigner 2 to give that apk a different key (auto-testkey).
When you install the apk with its new key, the Play Store will not recognize the installed app and will therefore not try to search or push any updates. :good:
ZipSigner 2 is available for free in the Play Store: play.google.com/store/apps/details?id=kellinwood.zipsigner2
Click to expand...
Click to collapse
Thank-you! That worked like charm!!

"Continue to Amazon Appstore" external market issue

Hi folks,
I've got a Fire Phone, with default Fire OS 4.6.1
I am not quite ready to get into rooting it and adding a new OS, as I don't have the time.
So in the interim I have the Google Play Store installed, along with a launcher that's more to my liking.
I have the issue that when I click on links in apps which, I assume, are intended to launch the Google Play Store, I get a message from Fire OS saying,
Continue to Amazon Appstore?
This app is trying to open a link with an external market that is not available on your device. Would you like to open this link with the Amazon Appstore instead?
[CANCEL] [CONTINUE]
Click to expand...
Click to collapse
If I click cancel, then the link does not open. If I click continue it goes to the Amazon Appstore and can't find what the link relates to (obviously).
I saw someone else posting something about this, and they were advised to edit some settings in the Manage Applications settings, and also External Market settings. Since updating to 4.6.1 I don't seem to be able to find any Manage Applications settings, no External Market settings (not even sure if those existed on the pre-4.6.1 OS that was on here when I received it).
Is there a way to set this thing to allow Google Play to launch when Play links are clicked?
Cheers,
J
On an unrooted device:
- Go to "settings" and look for "manage applications", select "all", to see every app installed...
- Disable the "Appstore"
As long as the Amazon appstore is disabled, Play Store will intercept the links.
It's not very comfortable, I know. On a rooted device, I used a shortcut to dis-/enable the Amazon Appstore to get the job done faster.
As of now, there is no official way to set the "Play Store" as your default store (of course not, why would Amazon be interested in that option ^^).
Bingo Bronson said:
On an unrooted device:
- Go to "settings" and look for "manage applications", select "all", to see every app installed...
- Disable the "Appstore"
As long as the Amazon appstore is disabled, Play Store will intercept the links.
It's not very comfortable, I know. On a rooted device, I used a shortcut to dis-/enable the Amazon Appstore to get the job done faster.
As of now, there is no official way to set the "Play Store" as your default store (of course not, why would Amazon be interested in that option ^^).
Click to expand...
Click to collapse
Hi Bingo,
Thanks for the help.
The thing is, since it updated to 4.6.1 (and I see that last night it updated itself to 4.6.3 on its own accord) the "Manage Applications" option that was there previously has gone. There is now just an "Applications" option. And that
Okay... at last I've figured out where "Manage Applications" went since 4.6.1 update. There is now just an "Applications" menu. Touching that expands it to show various options. One of those options is "Force quite or clear data for applications". This is now the way to access the "Manage Applications" screen. The first option on that expanded "Applications" menu is "Manage the settings for individual Amazon applications on your phone". The wording of this had me thinking that this had somehow replaced the Manage Applications option.
Cool. I've now disabled Amazon AppStore.
Thanks.
This Fixed My Issue
I fixed my issue by going to the Applications menu under Settings (little gear in dropdown menu) then going to Manage Applications, then selecting All Applications from the dropdown there. I found the Appstore, clicked on it, selected Force Stop and Clear Cache. That seemed to do the trick. I also have Allow 3rd Party Apps selected, which can also be found under Applications in settings.
I've been searching everywhere for this solution. Youtube and google, and yes finally someone who just needed google play apps to not be redirected to kindle appstore. It worked by disabling the appstore. <3 The ES File Explorer helped me to uninstall the updated version and now apps can be directed to google play. Thanks for saving me from having to root. I like the launcher option from google play. Don't have enough patience to root and then it possibly doesn't work. TOT! Ty for solution!
My 4.6.3 new phone seems to work well in this regard without any setting being made. Just disabled Amazon store auto update. At first I had that redirect to Amazon problem, but then some other Google store link just redirected to Google play app.
For me, clicking on Disable App Store doesn't seem to be doing anything. Unable to disable and blocking of external market link continues
Can someone please help, nothing in here worked.
I tried going to settings -> apps and games -> manage all applications -> All -> Appstore and pressed "clear cache", "clear data", and "force stop", and it didn't help.
I also tried going to settings -> Apps and Games -> Amazon Application Settings -> Appstore -> External Market Links -> Don't Open and now it says "External Market Links Disabled You can choose to open external market links with the bracketbracketAppstore_long_namebracketbracket. Update this option in the External Market Links section of the Appstore settings." (I had to type bracket instead of using [ because it said I was using BBcode and couldn't post)
I'm using a 5th generation fire running Fire OS 5.3.6.4
Fixed it
I just figured it out.
Settings, Applications & Parental Controls, Configure Amazon application settings, Appstore, External Market Links, Don’t Open
This will prevent the Appstore from trying to open links for external app markets. It doesn’t prevent the links from opening with the correct market, just makes that message stop popping up and click-jacking you into oblivion. So now when you click on a link, a little box will open with apps to choose from to open the link, like your browser or Google Play Store, for example.
I want to keep using this phone, because it’s potentially a good privacy phone, without all the tracking stuff installed. Sorry, that would mean no Google Apps...but I use some apps that apparently won’t get notifications unless GAPPS are installed. I heard MicroG can fix that but it doesn’t seem to work. Anyway if I could fix that and maybe upgrade the camera module to a better quality camera, it would be a better phone...almost perfect actually.
thanks for your helpful post
Ninja000 said:
I just figured it out.
......
Click to expand...
Click to collapse
Thanks so much for posting today!! So happy to see people still using this nice phone. I too want a simple "relatively" private phone, plus I actually preferred the Fire OS UI (which is much better version of Fire OS than we have on Fire tablets).
But I came here because I was fearful that Amazon has bricked my device. It suddenly became "de-registered" and the menus for registering to my Amazon account do not work -- I'm not able to register. And I'm not able to use ANY app that I got from the Amazon app store, and I lost ALL of my nice customizations (organizing my apps into folders, etc -- a huge amount of work because I have a ton of apps).
Probably I should start a new thread on this issue but I wanted to post here in gratitude that people still discuss this phone, plus it is an app store (and bigger...) issue, so it is not entirely unrelated. I will try some of the above advice because perhaps it allow me to launch apps without the Amazon App Store demanding log in.
dini77 said:
Thanks so much for posting today!! So happy to see people still using this nice phone. I too want a simple "relatively" private phone, plus I actually preferred the Fire OS UI (which is much better version of Fire OS than we have on Fire tablets).
But I came here because I was fearful that Amazon has bricked my device. It suddenly became "de-registered" and the menus for registering to my Amazon account do not work -- I'm not able to register. And I'm not able to use ANY app that I got from the Amazon app store, and I lost ALL of my nice customizations (organizing my apps into folders, etc -- a huge amount of work because I have a ton of apps).
Probably I should start a new thread on this issue but I wanted to post here in gratitude that people still discuss this phone, plus it is an app store (and bigger...) issue, so it is not entirely unrelated. I will try some of the above advice because perhaps it allow me to launch apps without the Amazon App Store demanding log in.
Click to expand...
Click to collapse
No problem! "Sharing is caring" :laugh:
Yeah I like it too! I wish it was still supported by Amazon, but the bad press killed it.
As for not being able to use your account...you might try a factory reset, BUT...
FIRST: backup your APKs and saved files via USB to PC (can use file browser in Windows)
or MAC (will need this --->android.com/filetransfer/<---), and make sure under Battery and Storage, USB Connection Type is listed as File Transfer.
This is important because once you regeister, it might restore your last cloud backup, which I assume is probably pretty old after reading your reply.
Next:
Perform the Factory Reset OR...
To reregister your phone go to Settings, My Accounts, either "Register your phone" if that is an option (mine says "Deregister"), or maybe Manage your Amazon account.
The later will probably redirect you to the Amazon website, because the Amazon Shopping App is no longer supported on this older OS.
*I haven't found a newer version of the Amazon Shopping App that works on the Android 4.4 based Fire OS 4.6.6.1.
The other thing is you might be able to do it via the Amazon website, you probably have it listed under your account still, just need to find it.
I'd contact Amazon help to learn about how to do it that way. They might not know off hand, since the phone is no longer technically supported,
but they will definitely still try to help you.
I would really love it if someone on this forum could pull the launcher and everything from this version of Fire OS to work on the newer Android Roms like Cyanogen Mod,
because then we could just replace the old unsupported apps with the new versions. That would be awesome! I realize 2gb Ram would be a little low for the latest Android,
but just having a little newer OS version that is still supported by Amazon would be great. I really enjoy the Kindle App on this, because it has text to speech and
that is really convenient.
BTW, do you have the Google APPS installed on yours? I have them installed on mine, and it drains the batter like crazy,
granted, it's the original battery from 2014, but still.
Side note: If anyone has an extra screw(s) for the bottom they're willing to part with, I'd be willing to buy one (or a handful).
Lost one in the carpet (I know *rolls eyes) when I had to replace the camera module due to some (I guess) scratches or something actually on the sensor itself.
Thanks for all of your advice!! Very much appreciated. I tried one of them right away, which is to check My Devices on the Amazon site, but the phone is no longer listed (it used to be). So that only lists registered devices. Once it is de-registered, it is not considered to be my device. But, you are correct that Amazon customer service may possibly help, because if you buy a device from Amazon, it usually automatically gets registered to you (unless you say it is a gift), and that automatic registration is probably done via some code on the device box probably its serial # (that is, they don't register it by messing with the actual device, I'm guessing). But to be honest I'm not too hopeful about this. But something to try.
Before you replied, I started a new thread on this, mostly to warn people not to de-register their devices, because I think it may not be possible to register again. And this could be a very recent development. Amazon usually sends an email warning when an older device will no longer work, but maybe this was not intentional. I never realized that so much of the function depended on the registration, as if it were an Echo device!
I do have a collection of APKs saved so at least I won't need to re-download, but because I have so many apps, it would still be a lot of work to set things up from scratch, especially since I don't think it will work. I don't think my system is corrupted. Just de-registered. A soft reset (long-press of power button) did not help. Again this just happened by itself -- I had not added anything new or did any updates. So it is not likely that my install got messed up.
I'm always confused when people mention "Google Apps" -- if that means the Play Store and its dependencies, then yes, I have that. But I did not install GMail or Docs or Drive, etc. I minimize using Google things on this phone.
About the screws, eBay may have them. eBay has almost everything.
Ninja000 said:
No problem! "Sharing is caring" :laugh:
Yeah I like it too! I wish it was still supported by Amazon, but the bad press killed it.
.
Click to expand...
Click to collapse
I think it is just extremely difficult for "alternative" phone systems to survive, which is soooo sad, because I like interesting variety. I also love Meego, and Windows 10 Mobile. Meego had just one model (it was from Nokia, not released in the U.S.; it was planned to be the Nokia successor for their older Symbian OS). Well, maybe FireOS is not truly "variety" because it is after all essentially Android, but much less messy or annoying, in my opinion. I really like how the Settings are organized. And I like the Carousel, especialy how nicely it works with the built-in apps like weather and email. Being basically Android, it actually had the best chance of survival out of the "Alternatives." It could use most of the same apps as a "real" Android.
The reason for quick death are probably multi-faceted but my guess is the problems with the earliest version of the OS were the most serious thing. And that led to the bad press, so you are correct, that is what did it. I got mine after the "fire sale" and by then the system was much nicer, with the most annoying or serious issues all fixed, so I only read about the early issues. I feel terrible for the (former) Amazon employees who put a huge amount of effort into this thing. (Like Meego, too!) And the hardware is still very nice, better than my Fire Tablet that is much newer. I really thought it would last me for years, for the sorts of things I used it for. (Another thing I liked to do is control my Squeezbox music streaming devices. And listen to podcasts. Things like that.) There are so many uses for an older device. And I enjoyed this one.
Since at the very minimum this device is a Kindle book reader and Amazon music player, Amazon loses by not providing some bare-minimum support for it. My first Kindle e-Reader from 2011 still works great. But my guess is, the number of people still using this phone is super low. Which is why I was happy to see your post!
dini77 said:
Thanks for all of your advice!! Very much appreciated. I tried one of them right away, which is to check My Devices on the Amazon site, but the phone is no longer listed (it used to be). So that only lists registered devices. Once it is de-registered, it is not considered to be my device. But, you are correct that Amazon customer service may possibly help, because if you buy a device from Amazon, it usually automatically gets registered to you (unless you say it is a gift), and that automatic registration is probably done via some code on the device box probably its serial # (that is, they don't register it by messing with the actual device, I'm guessing). But to be honest I'm not too hopeful about this. But something to try.
Before you replied, I started a new thread on this, mostly to warn people not to de-register their devices, because I think it may not be possible to register again. And this could be a very recent development. Amazon usually sends an email warning when an older device will no longer work, but maybe this was not intentional. I never realized that so much of the function depended on the registration, as if it were an Echo device!
I do have a collection of APKs saved so at least I won't need to re-download, but because I have so many apps, it would still be a lot of work to set things up from scratch, especially since I don't think it will work. I don't think my system is corrupted. Just de-registered. A soft reset (long-press of power button) did not help. Again this just happened by itself -- I had not added anything new or did any updates. So it is not likely that my install got messed up.
I'm always confused when people mention "Google Apps" -- if that means the Play Store and its dependencies, then yes, I have that. But I did not install GMail or Docs or Drive, etc. I minimize using Google things on this phone.
About the screws, eBay may have them. eBay has almost everything.
I think it is just extremely difficult for "alternative" phone systems to survive, which is soooo sad, because I like interesting variety. I also love Meego, and Windows 10 Mobile. Meego had just one model (it was from Nokia, not released in the U.S.; it was planned to be the Nokia successor for their older Symbian OS). Well, maybe FireOS is not truly "variety" because it is after all essentially Android, but much less messy or annoying, in my opinion. I really like how the Settings are organized. And I like the Carousel, especialy how nicely it works with the built-in apps like weather and email. Being basically Android, it actually had the best chance of survival out of the "Alternatives." It could use most of the same apps as a "real" Android.
The reason for quick death are probably multi-faceted but my guess is the problems with the earliest version of the OS were the most serious thing. And that led to the bad press, so you are correct, that is what did it. I got mine after the "fire sale" and by then the system was much nicer, with the most annoying or serious issues all fixed, so I only read about the early issues. I feel terrible for the (former) Amazon employees who put a huge amount of effort into this thing. (Like Meego, too!) And the hardware is still very nice, better than my Fire Tablet that is much newer. I really thought it would last me for years, for the sorts of things I used it for. (Another thing I liked to do is control my Squeezbox music streaming devices. And listen to podcasts. Things like that.) There are so many uses for an older device. And I enjoyed this one.
Since at the very minimum this device is a Kindle book reader and Amazon music player, Amazon loses by not providing some bare-minimum support for it. My first Kindle e-Reader from 2011 still works great. But my guess is, the number of people still using this phone is super low. Which is why I was happy to see your post!
Click to expand...
Click to collapse
Yeah I completely agree. I got mine for $199 and a year of Amazon Prime included made the phone basically $99. ? I happened to think of one more possibility. Maybe there is an Amazon Fire ?services app (like Google services) or account manager app that got automatically updated by your Google Play store, or even replaced by a version off the Play store that led to this issue, because like I mentioned mine is actually still working aside from the Amazon Shopping app, and some apps that require a newer google services to get notifications.
I actually had flashed several different Roms on this phone and yeah the stock (but updated) Fire OS 4.6.6.1 is definitely the best. --Amazon account registration is part of the initial setup BTW, so factory reset might work.
I made the jump over to iOS after experiencing the Android 7&8 difficulties on a few other devices and battery gate with Samsung phones. Now I am experiencing a crapy battery life issue with my iPhones. My Fire Phone is from 2014, original battery and still has better battery life than even my iPhone XS Max. Wow ? So yeah, there is something to Fire OS being so light that makes it probably just about the best OS for a phone. The last time I flashed back to stock I used a ROM from this website, but I don’t remember what thread that’s on. I think it’s in the Cyanogen 11 Rom thread for this device. Maybe try flashing that. And you could actually (if you don’t mind losing the storage space) create a backup Rom from your current one, then make a new slot in twrp or whatever it’s called and have the other Rom installed on there. Then check to see if it’s possible to register on that version. If it doesn’t work, no big deal you will still have your backup rom with all your data. If it does work, then you could transfer your stuff over via usb. That would save you quite a bit of time incase it decides not to work. You can do a root and install the other rom right from your fire phone these days. That’s a bonus.
What happens when you open Amazon Instant Video? Does it ask you for a loggin? That would be awesome. BTW My Kindle Fire HX 7 is still working great too, just starting to slow down a bit. I also have a 6" Fire HD. I really agree Fire OS is super clean and alot of modern OS's are not that great and way too heavy for what most people need, especially on mobile devices.
Thanks again for your advice, especially since I will almost certainly end up flashing this thing. I have done a lot of "phone hacking" in the past -- even back in flip phone days -- but it is very time consuming and I'm super busy now. But it is kind of fun. So, maybe later.
I did not have Google Play (or any app store, on any of my devices) to be set to automatically update apps. Tho I think the store itself and its dependencies may still update, even if my apps don't, and I can't control that. And sometimes my setting to not automatically update is "reset" when a google component is updated. So it is conceivable that something got automatically updated and that caused my issue. I did have to reset the "do not update" setting.
I'm curious to see if anyone else has this issue, because if no, then you are right, I should just re-flash. I downloaded the latest Fire OS a while ago -- I collect stuff like that because you never know when it will be no longer readily available. So the phone is definitely not dead -- and it is nice that I have options for how to set it up. I'm glad to have the community contributions for that -- I did read thru those hacking posts.
I bought a spare battery a little while ago because I was worried they would be hard to get once I need one. But my currently installed battery, the original, is very satisfactory. So definitely I'll keep using this nice phone for a while.
dini77 said:
Thanks again for your advice, especially since I will almost certainly end up flashing this thing. I have done a lot of "phone hacking" in the past -- even back in flip phone days -- but it is very time consuming and I'm super busy now. But it is kind of fun. So, maybe later.
I did not have Google Play (or any app store, on any of my devices) to be set to automatically update apps. Tho I think the store itself and its dependencies may still update, even if my apps don't, and I can't control that. And sometimes my setting to not automatically update is "reset" when a google component is updated. So it is conceivable that something got automatically updated and that caused my issue. I did have to reset the "do not update" setting.
I'm curious to see if anyone else has this issue, because if no, then you are right, I should just re-flash. I downloaded the latest Fire OS a while ago -- I collect stuff like that because you never know when it will be no longer readily available. So the phone is definitely not dead -- and it is nice that I have options for how to set it up. I'm glad to have the community contributions for that -- I did read thru those hacking posts.
I bought a spare battery a little while ago because I was worried they would be hard to get once I need one. But my currently installed battery, the original, is very satisfactory. So definitely I'll keep using this nice phone for a while.
Click to expand...
Click to collapse
Was just thinking of going back to this phone as my primary phone. My problem is trying to get Micro G or something to work, for spoofing google services, because I want to use some apps that require google services, else they won't receive notifications. I also found on app I use, it's Korean, Kakaotalk is not receiving notifications when closed anymore. I haven't figured out why yet. Saw another thread about notifications on 3rd party apps not working, but didn't see a solution. I would also like to see a camera upgrade (4k video) and maybe a speaker upgrade and storage would be nice, but obviously that would require some soldering that I'm not willing to do, but maybe if I had a few doner phones would try it.:laugh: happy thanksgiving by the way!
I just went back to a Nokia N9 as my primary, at least for voice and weather and such basics (MeeGo OS, and battery lasts for days, good quality voice, nice small size, does not crash, etc). But I have my iPad and iPhone SE (the older model) always turned on so that covers all my needs. So, it is perfectly fine to use an old phone as primary so long as you have another device to supplement what the primary lacks. The Fire Phone would also make a primary. Tho in my experience it is not as stable. The "mishap" in this thread was not my first serious hiccup. See also the thread on all apps crashing if they require the address book (including the phone). That one is serious and reoccurs. (I think it is caused by having a very large number of apps on the phone. Usually fixed when I delete one of the larger apps.) So in other words at least with the original OS, stability is an issue. Maybe the custom firmware on this board is more stable.
Have a great thanksgiving!

Anyway to make superuser auto allow on fire tv 2nd gen?

I have a rooted box and on certain programs that require root access it removes the allow screen too fast for me to click allow and therefore cannot use the addon. Is there a way to make it simply auto allow everything? On the 1st get I was able to do this but not on the second gen. And when clicking on supersu you cannot launch it to edit any options so basically I am stuck.
Have you tried editing /data/data/eu.chainfire.su/files/supersu.cfg? In particular, change "access=2" to "access=1" as the default.
retyre said:
Have you tried editing /data/data/eu.chainfire.su/files/supersu.cfg? In particular, change "access=2" to "access=1" as the default.
Click to expand...
Click to collapse
No I have not. Not exactly sure what that means. Is that an adb command?
danknasty said:
No I have not. Not exactly sure what that means. Is that an adb command?
Click to expand...
Click to collapse
Open the file in any text editor (e.g., ES File Explorer has a Note Editor) and make the change to the default. If you can't, do an adb pull of the file, edit on another device, and put it back to its original location. Make sure you set permissions back to 600.
retyre said:
Open the file in any text editor (e.g., ES File Explorer has a Note Editor) and make the change to the default. If you can't, do an adb pull of the file, edit on another device, and put it back to its original location. Make sure you set permissions back to 600.
Click to expand...
Click to collapse
I was going to try this but remembered that rooting on fire tv uses the a to a usb cable method and all the files are transferred automatically. I do not have a super user file... would I install another one and overwrite it on the box?
sure you do. How would you have root without su? Just look for the file mentioned above and edit it as per retyre's post above.
danknasty said:
I was going to try this but remembered that rooting on fire tv uses the a to a usb cable method and all the files are transferred automatically. I do not have a super user file... would I install another one and overwrite it on the box?
Click to expand...
Click to collapse
Regardless of the method used to root, rooting involves the install of su and something like SuperSU to make it easier to work with. The fact that you're being prompted to allow su access is proof enough.
Install a root file explorer (I use ES File Explorer), allow it su access, go to the root of the device ("/") and look for the file in the location mentioned above.
retyre said:
Regardless of the method used to root, rooting involves the install of su and something like SuperSU to make it easier to work with. The fact that you're being prompted to allow su access is proof enough.
Install a root file explorer (I use ES File Explorer), allow it su access, go to the root of the device ("/") and look for the file in the location mentioned above.
Click to expand...
Click to collapse
I wasn't saying I didn't have supersu just that the method I use doesn't allow me access before I transfer but I see what you mean I can do this from the box itself. Was hoping I could do it to the supersu file on the computer so that when I root another box I wouldn't have to change the text file again. But I'll try this out later and see how it goes.
retyre said:
Regardless of the method used to root, rooting involves the install of su and something like SuperSU to make it easier to work with. The fact that you're being prompted to allow su access is proof enough.
Install a root file explorer (I use ES File Explorer), allow it su access, go to the root of the device ("/") and look for the file in the location mentioned above.
Click to expand...
Click to collapse
I tried accessing supersu in two root browsers and it gives me a bunch of greyed out permissions... I am not sure how to even open it with notepad on es file explorer. This is a little different than the first gen as everything must be installed through tw recovery. Before Supersu would just ask me if i wanted to approve everything I clicked ok and never had to check it again. Is there any way I can edit any of the text that is being injected into the box when installing the firetv recovery via the usb cable method.. I believe this is where supersu is being transfered.
update: ok I found supersu inside the prerooted rom... I opened it as a text file and its pages and pages of random symbols etc.
harlekinade said:
Comedy gold.
I suggest you swipe left.
Or start reading what other people actually posted in here before. Or this: https://en.wikipedia.org/wiki/Compiler or what a filepath is, or why you shouldnt try to resell Fire TVs - just in case...
Here is why - I havent encountered any case where the allow root access prompt would be on screen for less than 15 seconds during which you have to press down/right/enter to grant it permissions - and it only pops on when you are actively launching anything that tries to pull root rights - so you already have the remote in your hands.
Automating root prompt behavior to grant root by default is a really bad idea in general and you asking not only how to automate it, but also automate further installations of such a setup, suggests that maybe you are battling with user behavior of folks that don't know what a superuser prompt is and that go with default settings in most cases. Ethically it is hard to support any of this.
Click to expand...
Click to collapse
Wow that was really presumptuous and didn't at all relate to anything or help me.... excellent work. I suggest before attempting to troll a post you read the entire post so you can at least have a firm grasp on your ridiculous comments. 9 posts in you're doing great. Lol "ethically it is hard to support any of this." At least you made me laugh. I guess it's unethical in your opinion for me to paint my car red also since it comes from the dealership blue. Btw it never occurred to me to push down right then enter with the remote thanks problem solved.....
danknasty said:
I tried accessing supersu in two root browsers and it gives me a bunch of greyed out permissions... I am not sure how to even open it with notepad on es file explorer. This is a little different than the first gen as everything must be installed through tw recovery. Before Supersu would just ask me if i wanted to approve everything I clicked ok and never had to check it again. Is there any way I can edit any of the text that is being injected into the box when installing the firetv recovery via the usb cable method.. I believe this is where supersu is being transfered.
update: ok I found supersu inside the prerooted rom... I opened it as a text file and its pages and pages of random symbols etc.
Click to expand...
Click to collapse
Why are you trying to edit SuperSU (the app)? You should edit supersu.cfg, which is the text config file for SuperSU. Look for supersu.cfg in the location mentioned earlier.
retyre said:
Why are you trying to edit SuperSU (the app)? You should edit supersu.cfg, which is the text config file for SuperSU. Look for supersu.cfg in the location mentioned earlier.
Click to expand...
Click to collapse
The only supersu I was able to find using es explorer was the supersu file in the system folder... data showed up as black. I was finally able to find it using a different root browser I changed the setting for the app it self to 1 and it works. The only program that this gives me this issue with is teamviewer and I am wondering if it has to do with using a launcher version of kodi as it always kicks me out of the allow root selection screen, automatically disallows root and jumps to the kodi screen. But doing what you recommended worked. Thanks
harlekinade said:
Thank you for explaining your issue a little bit further. Changing the default of a superuser prompt to "yes" is something that shouldnt be considered an "easy fix" you could integrate into an image an then roll out on several devices.
Even if you LOL at the ethics of this, as you so eloquently put it - its still not something you should consider doing, generally speaking.
Just like you - trying to edit the Superuser binary in a texteditor - people can ruin their devices beyond repair, the default on "no" is a behavioral crutch to make it less likely that they find themselves in that situation.
Not sure if it would work for you - but I posted a teamviewer alternative in the general section (Exposed modules and root apps thread), that you might want to take a look at, as it doesnt require the app to be launched every time you want to access the Fire TV via VNC - as it runs as a service in the background.
I'm not exactly sure what you try to accomplish with teamviewer and why you want to roll out this configuration on multiple devices - so I'm not sure if it fits your purpose, but it might.
Click to expand...
Click to collapse
My issue was explained in the first post but i think you're really thanking me for telling you that I don't intend to sell rooted fire tv's with super user permissions on yes by default for malicious purposes... as you so eloquently put it.. I was actually laughing at the fact that you are on a forum that is primarily devoted to rooting and customizing devices but you draw the line at me wanting to default the supersu permissions on my devices because of ethical reasons. Anyways I'll check out that alternative to teamviewer you spoke of. I intend to use teamviewer for the purpose it was created which is to remotely access devices from my computer.
I actually did confirm that it was the launcher version of kodi that was kicking me out of the supersu prompt for anyone that was interested.. I turned off the xposed module to confirm.
harlekinade said:
You wanted support, you did get what you asked for, and then you almost ruined your device, because you din't see the file you were told to edit, and decided to open a different one. Then you blamed it on your root explorer app.
In the opening posting you stated that you wanted to change the default, but not why - and when I criticized this as being not needed in general, risky - and if you'd planned to roll it out to several installations, other people might use - as your postings intended, even unethical.
Unethical because of two concepts -
- You usually don't think about automation for mass deployment - if you don't plan an reselling devices, and we have a big problem with resellers in this community, not taking the responsibility "clause" seriously. Because of a principle you could describe as "sell and vanish". Which almost ruined the Kodi community, and arguably has impacted this one as well.
There is this distinct sense of "wasteland" after a general interest crowd was allowed to promote their interests (ad hoc, personal problem solving assistance) for a few months, by moderators that have no stake in this specific scene at all. I can only repeat that.
- It is ethically problematic to tell users like you how to change an important default and not what comes with it. The entire filesystem model and security in operating system depends on escalating user account rights. With root - you always grant access to everything.
Yes XDA (or what this community stood for in the past) is all for root (the rights to do whatever you want in an OS) - but ostensibly not for handing those permissions over to every user, or making sure that root level rights are granted by just pressing the big OK button on a TV remote, whenerver a popup comes up. The prompt is there for a reason. So is the default to no. If you want to change that because of a very specific personal problem, thats fine - you can (thats the "self empowerment" part), its the "mass rollout" of this configuration you hinted at - that rang some alarmbells - so to speak. Just from a "you might cause more problems than you solve" in the longterm - standpoint.
Click to expand...
Click to collapse
Well just to clarify not at one point did I ever almost ruin my device that's just pure imagination on your part furthermore I did not blame any program for my own actions I stated my experience. Secondly I can do whatever I want with a device I purchase, are you attempting to police the entire community with our own personal "ethical" standards on what should and should not be done with their property? I can tell you're biased because people sell these and it makes you upset. I've identified as not part of that community and honestly I don't owe you any explanation on what I want to do with my devices period. The quantity is also irrelevant can one not own more than two tvs? But again the issue was solved mainly by the aid of the others contributing to this post thanks for your ethical input though. Lol.
harlekinade said:
Then a simple question.
Did you plan, at any point, to sell rooted AFTVs with Teamviewer on them and Superuser modified in a way that defaults to granting root rights to any process that asks for them?
Because thats a major issue. Not only because we saw in here over the past few months what happens if some peaple sell other people "free and easy" and then arent able to assist them if something breaks. The influx of technically illiterate users - having been sold on "free" and then not getting what they paid for in the end, looking for "support" everywhere they could think of, has scared the enthusiasts community in this sector for years to come.
And amazons moves surrounding it (explained away by product bloggers as "easier for most people" and "necessary") ended up establishing blacklists on consumer android devices for the first time in history (?), and almost killed Kodi as an afterthought (there was money to be made, if you faltered and bowed to amazons restrictions).
Resellers were and still are misusing this community by playing out entities that at no point had a self concept of becoming "product support helplines" and destroying the open source ethos by funneling a mainstream clientel through small community channels, that werent created to handle them.
If you look around you - in this forum, on reddit - even on aftvnews - this is what is left at this point, and some of us have no interest in rekindling the hype.
Part of demanding questions from an open source community is also, that you reflect, contrast, rethink and tinker with ideas in the open. XDA becoming a place for the masses to get personal support services - actually destroys communities like this. People demanding that you attend to their personal needs first, and always are respectful, charming and considerate can become problematic also.
When you had opened the Superuser binary in the texteditor, complaining that it only shows you "cryptic symbols" you were exactly one or two steps away from ruining Superuser on your device. Namely - changing ANY of those cryptic symbols and then saving the file you had already opened with the intent to edit.
Click to expand...
Click to collapse
You're still on about me reselling devices I don't know what to tell you I'm not gonna respond to it anymore. I was never close to bricking my device but I love how you decided to map out a scenario where I could have. You seem to be dead set on policing this forum (this post) and I find it odd you're talking about the history of this community after just 10 posts. I never demanded anything, this is a forum as you stated. I made an inquiry you can either help or you can ignore (I thanked those who helped). Or you can force your own moral agenda down everyone's throat that would be option c, the one you chose. Anyway there's really nothing left to be said my issue was resolved with the help of those interested in the actual question. I know people sell these things so does everyone else, this is not relevant to this post however.
harlekinade said:
I have a history in here beyond those 10 postings - but thats a story for another day..
My intent may have been to rattle some notions - but not to "police" by mentioning the concept of ethics once. I'm merely a peasant at this point in time, with a handful of soil in his hand, muttering "what have you done to this place"..
If I had any real power left to wield in here, arguing over concepts would be higher rated than providing "easy solutions". It isn't.
Also, sorry that I have borrowed your thread - and thank you for the conversation. I enjoyed it.
Click to expand...
Click to collapse
I figured there was more to your ten post history. Perhaps maybe you were not so ethical at one point to have lost those powers??? [emoji50] But hey like I said you made me laugh so no complaints here. Continue to enjoy the forum as will I.

Medical app not compatible - is it potentially achievable for me to get it to work?

Hi,
I use continuous glucose monitoring to monitor my blood sugar, as I am a type 1 diabetic. The CGM I use uses Bluetooth to sync with an app (Medtronic's Guardian Connect app) and gives blood sugar data, safety alerts etc., but this app is only compatible with selected Android phones, which doesn't include any Oneplus phones. I really like the Oneplus 7t so I would rather not sell it if possible, so I was thinking of trying to make it compatible with the Oneplus and removing the phone model block. This has been done before with a different medical manufacturer's CGM app ( https://forum.xda-developers.com/oneplus-7t/help/medical-app-compatibility-t4015519 ), so I think it should be possible. Given my lack of programming ability, I was wondering if there are resources anywhere that might help with learning how to do this? Obviously they're not going to tell me "This is how you make this specific app work", but I'm just hoping to find some general resources on this type of coding. I have searched around with no success as I am not sure where to look. I gather it would take more than simply changing the buildprop file to trick the app into thinking it's a compatible phone.
Thanks.
Would help to know the app and what issues you're having. Is it not showing up in the play store? Does it give an error?
ziddey said:
Would help to know the app and what issues you're having. Is it not showing up in the play store? Does it give an error?
Click to expand...
Click to collapse
Sorry, not sure how I managed to omit all those details. The app is Guardian Connect (https://play.google.com/store/apps/details?id=com.medtronic.diabetes.guardianconnect&hl=en). I am able to download it, but when I open it it says "incompatible with your device", as it's only officially compatible with a limited subsection of Android phones (https://guardianconnect.medtronic-diabetes-mena.com/en_gb/app-compatibility). However, the Dexcom app that I linked in the first post also has limited compatibility, yet people have managed to get it to work with other android phones, so I'm cautiously optimistic that it will be possible for me to do the same.
I can't link URLs properly yet as I'm a new user, so I had to add those spaces in the links.
{Mod edit: Links inserted}
Riveon said:
Sorry, not sure how I managed to omit all those details. The app is Guardian Connect (https://play.google.com/store/apps/details?id=com.medtronic.diabetes.guardianconnect&hl=en). I am able to download it, but when I open it it says "incompatible with your device", as it's only officially compatible with a limited subsection of Android phones (https://guardianconnect.medtronic-diabetes-mena.com/en_gb/app-compatibility). However, the Dexcom app that I linked in the first post also has limited compatibility, yet people have managed to get it to work with other android phones, so I'm cautiously optimistic that it will be possible for me to do the same.
I can't link URLs properly yet as I'm a new user, so I had to add those spaces in the links.
{Mod edit: Links inserted}
Click to expand...
Click to collapse
Hello. Just wanted to inform you that I inserted the working links on your behalf (at least I assumed so).
I hope you'll find a solution for the issue soon.
Oswald Boelcke said:
Hello. Just wanted to inform you that I inserted the working links on your behalf (at least I assumed so).
I hope you'll find a solution for the issue soon.
Click to expand...
Click to collapse
Thanks for that
I have diabetes and want to use this app for checking my blood glucose level continiously on my oneplus 8pro phone but the app says its not compatible with the device. I don't know how to solve this problem.
Is there anybody who can help us with this?
Have you you guys tried to email the developer of the app to fix this?
I have diabetes and want to use this app for checking my blood glucose level continiously on my oneplus 8pro phone but the app says its not compatible with the device. I don't know how to solve this problem.
Is there anybody who can help us with this?
v.konvict said:
Have you you guys tried to email the developer of the app to fix this?
Click to expand...
Click to collapse
Yep, they weren't helpful at all though, unfortunately - they just gave a generic "keep an eye on the compatible device list" response. In the end I gave up and sold a Oneplus and got a Samsung.
Hi!
I just had contact with medtronic Belgium and they said; the more people call us the more 'problem cases' go to the IT'ers in America. So they mean how faster the problem will be solved so just give them a call
Greetings
https://m.apkpure.com/guardian-connect-us/com.medtronic.diabetes.guardianconnect.us/download?from=details
Needs stock, unrooted, bootloader locked, oos10
How can we fake the phone ID for an app?
HueyT said:
https://m.apkpure.com/guardian-connect-us/com.medtronic.diabetes.guardianconnect.us/download?from=details
Needs stock, unrooted, bootloader locked, oos10
Click to expand...
Click to collapse
Can this unlocking of phone be done for two other apps from Medtronic as listed below please?
CareLink™ Connect - Apps on Google Play
Diabetes data sharing
play.google.com
MiniMed™ Mobile - Apps on Google Play
Insulin pump display
play.google.com
Same error message as original post...
I am using an Asus ROG 5s Pro
Thanks in advance to anyone who can help
Can't use unlocked bootloader or rooted phones for medical apps as less secure
volkslove said:
Can this unlocking of phone be done for two other apps from Medtronic as listed below please?
CareLink™ Connect - Apps on Google Play
Diabetes data sharing
play.google.com
MiniMed™ Mobile - Apps on Google Play
Insulin pump display
play.google.com
Same error message as original post...
I am using an Asus ROG 5s Pro
Thanks in advance to anyone who can help
Click to expand...
Click to collapse
https://apkpure.com/developer/Medtronic%2C%20Inc.
Here is the list of all Medtronic's apps. Download the APK, then select the file from your Downloads folder in the Files app.
You may be prompted about the app being from an unknown source or risk to your device. Ignore the warning, tap OK, yes, or allow if prompted.
Hope this helps and as the post above already said I would consider calling Medtronic customer service and asking them to make the app available to all phones.
KemikalElite said:
https://apkpure.com/developer/Medtronic%2C%20Inc.
Here is the list of all Medtronic's apps. Download the APK, then select the file from your Downloads folder in the Files app.
You may be prompted about the app being from an unknown source or risk to your device. Ignore the warning, tap OK, yes, or allow if prompted.
Hope this helps and as the post above already said I would consider calling Medtronic customer service and asking them to make the app available to all phones.
Click to expand...
Click to collapse
Was actually hoping for a work around to use on phones that are not on the compatible list, i.e. for the app to not check for phone compatibility before starting.
volkslove said:
Can this unlocking of phone be done for two other apps from Medtronic as listed below please?
CareLink™ Connect - Apps on Google Play
Diabetes data sharing
play.google.com
MiniMed™ Mobile - Apps on Google Play
Insulin pump display
play.google.com
Same error message as original post...
I am using an Asus ROG 5s Pro
Thanks in advance to anyone who can help
Click to expand...
Click to collapse
I second this; rooted OnePlus 8 Pro running an A12 custom ROM
Personally I've actually come pretty close and was able to hide both Root and Developer Options from being detected using XPrivacyLua, but was unable to get MagiskProps working properly to get around the final "Your Phone is Incompatible" by spoofing as a Google Pixel (one of the primary "approved" devices) message, even after trying multiple older APKs combined with clearing data/cache
Zilch163 said:
I second this; rooted OnePlus 8 Pro running an A12 custom ROM
Personally I've actually come pretty close and was able to hide both Root and Developer Options from being detected using XPrivacyLua, but was unable to get MagiskProps working properly to get around the final "Your Phone is Incompatible" by spoofing as a Google Pixel (one of the primary "approved" devices) message, even after trying multiple older APKs combined with clearing data/cache
Click to expand...
Click to collapse
Thanks.
Actually the logic behind limiting the compatible devices boggles my mind because, other than replicating the screen of the insulin pump and sending data downloaded from the pump to health care providers, the app does not allow pump to accept commands from external devices. So I do not see what the concern is with allowing more devices to use the app...
volkslove said:
Thanks.
Actually the logic behind limiting the compatible devices boggles my mind because, other than replicating the screen of the insulin pump and sending data downloaded from the pump to health care providers, the app does not allow pump to accept commands from external devices. So I do not see what the concern is with allowing more devices to use the app...
Click to expand...
Click to collapse
There is no logic, just retarded medical industry bureaucracy BS.
I've contacted customer support multiple times and asked them the same question, only to get the same useless response of pretending to "pass on my feedback".
It's actually one of the reasons I wanna find out how to work around the problem even more; like who needs them to take proper control of a medical device that I own.
Would also be amazing to get a Wear OS app that displays the same or similar information to the app, but I don't see that being made by Medtronic for at least a decade.
Zilch163 said:
I second this; rooted OnePlus 8 Pro running an A12 custom ROM
Personally I've actually come pretty close and was able to hide both Root and Developer Options from being detected using XPrivacyLua, but was unable to get MagiskProps working properly to get around the final "Your Phone is Incompatible" by spoofing as a Google Pixel (one of the primary "approved" devices) message, even after trying multiple older APKs combined with clearing data/cache
Click to expand...
Click to collapse
Hi! Im struggling with getting this app working on my rooted xiaomi. Do you remember how exactly did you bypass those checks with xprivacylua?

Categories

Resources