Related
I had some issues with the ADB commands for preparing my rooted Nook Color for on-device app install (primarily due to microcrap's 64-bit Vista) so I found a very easy method.
In the Market, there's an app called "Sqlite Editor" from the folks who make "Root Explorer" - it's about $3.07 US$ but I bought it anyway.
With this [AFTER A BACKUP!] I was able to directly edit the settings.db (sub category SECURE) and change the following:
'install_non_market_apps' from the default value of 0 to 1 and following a SAVE and REBOOT I can now install directly from my SD Card.
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
I also posted this in Mobileread's excellent Nook Color Forum and I was thinking that may we should also acknowledge them as a great forum for our beloved Nooks!
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Dare I do this???
Click to expand...
Click to collapse
LOL...If only it were this easy.
I had no issue with installing apps from the sd card after rooting/installing mkt and gapps.
Depends on How You Rooted..
I'm not certain but some rooting methods have market/gapps built-in, some don't. I used Autonooter (after upgrading to 1.01) and market & Gmail just appeared - I never had to install anything else.
If you used Autonooter then you wouldn't have to do anything to be able to install non market apps. Maybe just toggle the setting in Nook Tools if anything.
docfreed said:
While I was doing this, I find a large number of additional entries including (are you ready for this???) bluetooth_on!
Click to expand...
Click to collapse
Its NOT that simple, its been turned on in the kernel & custom ones built for it with nothing.
If you see the "salting nook" posts so much as been done trying to get it to work, most expect something ground breaking to come from actually looking at the pins on the chip it self an connection through the MoBo.
Amd sold faulty quad cores as triples so it could be that the chip/Mobo cant do it. Could be a easy hardware mod but TBH so much deep thought an attempts have been seen in IRC i dont see a "virtual fix" anytime soon.
But that said im an idiot so could be 475% wrong
Yeah, I tried toggling Nook Color Tools per the instructions - never seemed to work for me. Anyway, it appears to be just a one-shot adjustment any way it's done (at least till we get FroYo) so I'm happy.
Merry XMAS everyone
docfreed
sqlite not working for me
Purchased Sqlite, when trying to install, exits without loading apps. Any suggestions? Rooted with older booker and then re-rooted with pre 1.01 autonooker. Thanks. -
I have a kernel and u-boot that enables the bluetooth portion of the module and sets up an rfkill device. hciattach will detect it as a TI Bluetooth module and will load one of the TI bluetooth firmware scripts, but then complains about a missing socket or something. It sounds like a software error more than anything that might be wrong with the hardware.
What this means is that the Bluetooth part of the WiFi module isn't just left disconnected and the link to the CPU is working. But we don't know if the antenna is set up to share between wifi and Bluetooth or if the hardware is otherwise missing something that would keep it from working.
If you have experience with getting TI WiLink Bluetooth working in Android or Linux, or know someone who does, PM me or join us on Freenode channel #nookie. We're really close!
Hi All-
Trying to get the Audible app working from the android market. It downloads and installs seemingly correctly. I can even browse the audible catalog using it.
What isn't working correctly for me is entering my account information to authorize the device & start playing items from my audible library. I seem to end up in an endless loop of asking for my credentials, saying they're good, followed by asking for them again. (I have another thread open where I am experiencing the exact same problem with the android market -- I can't seem to buy paid apps but free apps download and install fine & dandy)
Hopefully this issue with audible & my android market issue are caused by the same problem & both will start working once solved. In the mean time, can anyone confirm they have audible working on their device??
Thanks,
Mark
Have Exactly Same Issue
I called Audible and spoke with tech service - they even reset my password but to no avail. Audible is basically clueless (owned by Amazon so maybe it's a conspiracy
docfreed said:
I called Audible and spoke with tech service - they even reset my password but to no avail. Audible is basically clueless (owned by Amazon so maybe it's a conspiracy
Click to expand...
Click to collapse
I really dont think audible tech support can be faulted for not being able to help you get their app working on a rooted ereader.
Audible and Rooted Nook Color
I have this same issue with the Audible app. I had an email thread with someone from the app team and here is what I got from them.
"The problem is that we are not getting a consistant device id for use in authentication. I'm guessing from the device that you're using that you're making your own framework builds; if so, if you can force the DeviceID field to always give the same value, then your activation problems should stop.
I've deactivated all the activations on your account. Just to be explicit, we check TelephonyManager.getDeviceId(), and if your phone type is TelephonyManager.PHONE_TYPE_NONE we'll check android.provider.Settings.Secure.ANDROID_ID. If for whatever reason you can't get these working correctly, then you can use the .audiblePrefs file from a device where this does work; we cache the device id there in case TelephonyManager.getDeviceId() returns null but your phone type isn't PHONE_TYPE_NONE."
So it looks like someone will need to figure out how to ensure that the Device id remains the same during all the transactions with Audible.
Sean
Thanks for finding that, Sean.
I have an android phone I can look at rooting to get to the mentioned prefs file. Perhaps that would be a way to generate a stop-gap while one of the devs looks into the device id issue.
Mark
Doesn't Market Use the Device ID
It seems that I remember that the Android Market also uses the phone device ID - in fact that is why certain cheap Android tablets cannot have the Market installed. Since we can get Market on a rooted Nook Color with no issue, I don't understand how the device ID would keep changing in case of Audible.
Keeping an eye on this thread. I would love to have my Audible app working
Sent from my nook color using XDA App
Same problem here; also following it like K8108; thanks for any help you guys can come up with!
I havent tried to install audible yet but wanted to listen to my huge library of books on my old mytouch before they had an app and found a solution. You can buy SoundTaxi and rip the downloaded Audible books from your PC to whatever format you want and put on memory card on the Nook and listen. its not as bad as you think.
The odd thing of it is that under 0.2 and side-loading the app seemed to work for me. Moving to the latest autonooter however is causing the authentication problem that everyone is having.
Audible support was very kind, but basically said we do not support tablets only phones. My NC was trying to connect to audible.co.uk thus causing the conflict. As a Californian this isn't going to work for me obviously. The app seems to be able to download but not play the .aa files. Is there anyway to check the server without sending an in-app email, as that is the only way I know how to check?
Subscribed to the thread with hope that someone smarter than me can figure this out.
Update: Forgot to state that using adb of Audible does not work. Does this have anything to do with the new .jar file from Barnes and Noble, or something in the Autonooter itself. 0.2 was working very nice, but that was also under 1.0.0.
So doesn't anyone have any android device with working Audible on it... that can examine .audiblePrefs
RpDn said:
So doesn't anyone have any android device with working Audible on it... that can examine .audiblePrefs
Click to expand...
Click to collapse
I have audible working on my android rooted HD2 - and have put several builds on there, but don't know a lot of techie stuff. If you will explain to me where to look, I could have a try.
It's been suggested to copy a working .audiblePrefs file over, but I don't have another android device to set up. I might borrow one, though, for a temporary setup, to get a working .audiblePrefs file (or an Id anyway), if I knew it was the way to get around this glitch. Was hoping someone with a NC and another android device would have tried it by now.
I have a Samsung Fascinate with Audible. I copied .audiblePrefs from my SF to my NC, rebooted my NC, and I am still in the loop of entering my username and password.
I am don't know much about the technical side of this, but I am very good at following directions. If there is anything you want me to try, just let me know. I am very anxious to try this.
I don't mind posting my .audiblePrefs file, but I don't know if there is personal information in there that I should be careful about posting.
I think you should keep your prefs file to yourself... it may be specific enough to include subscriber Id. Also, you may have exceeded your activation limit if you've tried too many times before copying your prefs... an email to Audible can reset the limit.
I find it interesting that the activation loop includes a quick flash of "Activation successful" on the screen. Audible sent me a reply in response to question... that they reset my activations... didn't solve prob, of course. Also interesting that I -can- play recent 'free' excerpts dnld'd from them via Audible app on the NC.
Just need a modder to look into this Id storage/reading. I'm a comptech but just a newbie on Android/NC.
I call all the time to have Audible reset my activations. That is no big deal for me. I am rooting phones all the time or switching computers and I never deactivate devices the way you are supposed to. I do wish Audible would wise up and give their users a way to reset activations online. But at least they never hassle me about resetting them when I call them.
Any new updates on getting Audible to work? Just did the autonooter and have hit the same problem.
Thanks,
Tim
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
k8108 said:
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
Click to expand...
Click to collapse
I went from a stock 1.1.0 and then applied autonooter for the first time. Audible does not allow the authentication to occur just as the original poster noted.
k8108 said:
I did the autonooter thing to update to 1.1. Uninstalled and re -installed Audible. Error message came up about having to many devices. Called Audible. They reset my acct. Uninstalled and reinstalled again. This time the activation took. I using Audible with no problems.
Click to expand...
Click to collapse
I did same thing (except I requested only my Android activations be reset, so as not to affect my PC or WinMo phone)...and have been using Audible on my NC successfully for a week.
So here is a short Huawei Mate 10 Pro guide. It might work for other Huawei's as well. If so pls let me know.
How to kill ads on Huawei Mate 10 Pro without Rooting the phone
What does the good people of XDA think is the way to go to kill ads without rooting?
NB: These tips and tricks are not my brain work. It is a collection of problems, issues and solutions to things I've experienced with the Mate 10 Pro, and the solutions are the great work of this forum and various contributors. My only contribution is to try to gather them all here in post one so people don't need to read the whole thread. In particular i would like to thank Pretoriano80 for his contributions in this thread. He made my life easier. Thank you.
-------------------------------------------------------------------------------------------------------------------------------------------------------
Recap:
Remove Ads from browsers:
This solution worked well for removing ads from browsers, so I bought it from playstore to show my support. Thx to Pretoriano80 for resolving most of my ad problems.
This solution also takes care of the in-apps ads!
Pretoriano80 said:
Hi mate, i also hate aggressive ads, so after many trials and errors, i finally found the best (and also free and no Root) solution.
I'm using an app called "Virtual Hosts" which is blocking ADS by creating a local VPN and loading a host file.
The app is open source and you can get the apk for free, downloading it from here - > https://github.com/x-falcon/Virtual-Hosts/releases < - or from Playstore by paying it (both versions are identical).
Once installed, you can downloaded and use the "host" file from here - >
http://adblock.mahakala.is/ <- or use another one of your choice (i got the file from this thread - >
https://forum.xda-developers.com/showthread.php?t=1916098 )
Click to expand...
Click to collapse
Youtube without ads:
A youtube version that is slightly altered to filter out ads. Works on non rooted devices and can be installed alongside the original youtube. Notice the modified MicroG apk on the second quote for using this modified youtube with your google account.
Pretoriano80 said:
Yes, you can try the latest x64 version from here - > https://androidfilehost.com/?w=files&flid=236411 - > it doesn't need root and can be installed alongside YouTube, as a secondary YouTube. [emoji6]
Click to expand...
Click to collapse
Pretoriano80 said:
Yeah, in-app ads are also gone. [emoji16]
BTW, if you want to use your Google account with the modified YT app, then you will also need a modified MicroG apk, which is specifically designed for it.
Click to expand...
Click to collapse
How to root Huawei Mate 10 Pro:
Some of you looking into this thread might wanna have full control over your Mate 10 Pro by rooting. There are various ways but the MAGISK seems really nice, and you can choose which apps shall see root or not. Read more here; https://forum.xda-developers.com/apps/magisk
A short video of Magisk; https://www.youtube.com/watch?v=iFJVoIjKZJw
Pretoriano80 said:
Rooting with Magisk is possible on Mate 10 pro, so you can use banking app or any other app that requires a "stock" device. As long as you pass SafetyNET verification and you hide root from the eyes of those apps, than you can use them with Root.
Click to expand...
Click to collapse
Huawei Mate 10 Pro apps loosing 4G and Wifi connection
When I first started to use the Huawei Mate 10 Pro I noticed that every once on a while an app would not work when I tried to restart the app. Suddenly I got an error saying their was no data connection, meaning no 4G or wifi. It was faulty error because I could use data in other apps. For me typically the problem was related to Spotify and Audible. The only fix I could find right away was a full reboot. It always took care of the problem and apps would work properly. Reboots are not welcome in a busy day. So I've looked around and found that I could manually control the power saving management for each app in >setting>battery>Launch. By taking back the control apps worked flawless once again.
A few weeks ago we had a yet another firmware update. And behold, once again the problem started. Only this time even in manual mode in >Launch the apps would still loose their 4G connection randomly, or even wifi if at home. It seemed like a reboot was the only choice to get things working. Until I by pure luck tried to enable the Ultra Battery Saver from the pull down menu. Enable it, then exiting it somehow resolves any power saving issues. Apps they work fine, they get their data connection, both 4G and wifi. The quick fix takes only seconds to complete, and there is no need to do a full reboot in order to have apps fully working.
I'm using adguard. To avoid some popup that coming from browser. And in the same time, if the apps have ads and i use the app continuesly, I'll purchased it, as im supporting the developer.
joppy said:
So I got a new phone, after years with a LG G3 it finally tanked. Today the replacement came. Huawei Mate 10 Pro.
And what a strange experience it was to fire up the unrooted phone. So much ads. Everywhere. Overwhelming.
I've been on a custom ROM rooted G3 for the past 4 years or so. I forgot about the ads.
The plan was to keep this phone stock, no root. In order to comply with all the crazy folks that try to force us to not use rooted devices. But as many of you have seen too, there are so many services that we use daily that will not work with rooted phones. I've worked around that before and have been happy.
But for now I am not ready to use a custom Rom or to root.
how can I kill ads? Ad guard, DNS66 or maybe block-this?
Maybe I am getting old, have a touch of paranoia or are just not brave anymore. But adding APK from sources I don't know much about feels well not good. There are so many scams and ****ware floating around. I would hate to end up with crapware for trying to get some peaceful surf time without ads. Apps are for the most part OK, because I pay for almost all those apps I use, and by paying I support and avoid ads. But even using a browser to read news I get littered in ads. Man ads really take the fun out of internet. I would easily pay good money as yearly fee to avoid ads. IS there anything out there that will work as a paid app?
What does the good people of XDA think is the way to go to kill ads without rooting?
Click to expand...
Click to collapse
Hi mate, i also hate aggressive ads, so after many trials and errors, i finally found the best (and also free and no Root) solution.
I'm using an app called "Virtual Hosts" which is blocking ADS by creating a local VPN and loading a host file.
The app is open source and you can get the apk for free, downloading it from here - > https://github.com/x-falcon/Virtual-Hosts/releases < - or from Playstore by paying it (both versions are identical).
Once installed, you can downloaded and use the "host" file from here - >
http://adblock.mahakala.is/ <- or use another one of your choice (i got the file from this thread - >
https://forum.xda-developers.com/showthread.php?t=1916098 )
P. S : Let me know how it works for you. Here is working perfectly and with almost no battery drain.
In regards to browsers. I used to use Dolphin browser, which has a good ad blocker, but, ever since Oreo, it crashes when I enable the ad blocker. Anyone have luck using Dolphin? Firefox also has a pretty good ad blocker but I find it slow.
A while back I had to send the much beloved Lg G3 to change screen, and the week it took before it was returned I had a loaner phone, a G5. Phone was not rooted so I added a adblock by DNS can't remember the name of it, but that thing ate battery as well as cpu. One could feel phone starting to bog down while surfing. That being said, I didn't put any time and effort into the loaner phone so I didn't try to tweak anything so the sluggish result could be my mistake also.
As soon as I have made a complete backup I will start trying these, and the virtual host one by one and put a small review here in this thread. I just learned that twrp should now also work for unrooted devices. That makes me very happy as it is familiar to use. Got to check out to see if maybe even Titanium now will work for unrooted phones as well. That would be really sweet.
Forgot how much work it is to get a new phone. Nothing is the same, and every brand UI got their own take on small bits and pieces just so we get our heart rate going
If others have other suggestions for anti-ad apps I will make time to try those as well. Thx you all for your input. Much obliged.
I'm using adclear. Helps a lot.
joppy said:
A while back I had to send the much beloved Lg G3 to change screen, and the week it took before it was returned I had a loaner phone, a G5. Phone was not rooted so I added a adblock by DNS can't remember the name of it, but that thing ate battery as well as cpu. One could feel phone starting to bog down while surfing. That being said, I didn't put any time and effort into the loaner phone so I didn't try to tweak anything so the sluggish result could be my mistake also.
As soon as I have made a complete backup I will start trying these, and the virtual host one by one and put a small review here in this thread. I just learned that twrp should now also work for unrooted devices. That makes me very happy as it is familiar to use. Got to check out to see if maybe even Titanium now will work for unrooted phones as well. That would be really sweet.
Forgot how much work it is to get a new phone. Nothing is the same, and every brand UI got their own take on small bits and pieces just so we get our heart rate going
If others have other suggestions for anti-ad apps I will make time to try those as well. Thx you all for your input. Much obliged.
Click to expand...
Click to collapse
Root was never required for TWRP to work, only unlocked bootloader. Anyway, there's no TWRP available yet for Mate 10 Pro.
Titanium Backup will never work without root cause is the only way it can write on the /data partition.
Oh ok I thought that no-root-needed was a new feature for twrp. I guess as Titanium will not work with un rooted phones neither will any other apps similar to Titanium?
Is there any apps similar to twrp that will work with Huawei Mate 10 Pro?
No matter what I guess I just have to start testing adblockers this weekend. Because I can't take all the ads I struggle with now. Too bad I didn't start out with the new phone by testing, before I sat up the phone they way it is now, with all apps, settings etc. Cos now if I would like a fresh start after testing various adblockers I will need to do the whole process of installing and tweaking all over again unless I find something like twrp for the Mate Pro 10.
Btw the xda app named my device BLA-L29, is that a name that is widely used for the Mate 10 Pro? Never seen this name before.
joppy said:
Oh ok I thought that no-root-needed was a new feature for twrp. I guess as Titanium will not work with un rooted phones neither will any other apps similar to Titanium?
Is there any apps similar to twrp that will work with Huawei Mate 10 Pro?
No matter what I guess I just have to start testing adblockers this weekend. Because I can't take all the ads I struggle with now. Too bad I didn't start out with the new phone by testing, before I sat up the phone they way it is now, with all apps, settings etc. Cos now if I would like a fresh start after testing various adblockers I will need to do the whole process of installing and tweaking all over again unless I find something like twrp for the Mate Pro 10.
Btw the xda app named my device BLA-L29, is that a name that is widely used for the Mate 10 Pro? Never seen this name before.
Click to expand...
Click to collapse
Installing the app i recommended has no risk, you don't need to backup anything. If it works and you like it, then you keep it, if not, just uninstall the app simple as that.
That app is open source, so no bloatware or any hidden stuff, it doesn't use DNS to circumvent ads and doesn't track anything, all it does is pointing Internet traffic to your "host" file, it's nothing like AdGuard and similar apps that also sell your data to third parties.
It only takes 5 minutes to test and decide, without any harm. [emoji6]
@Pretoriano80 thx a lot. That worked great, so great I had to support by buying the app.
Next step is to make youtube clutter free.
joppy said:
@Pretoriano80 thx a lot. That worked great, so great I had to support by buying the app.
Next step is to make youtube clutter free.
Click to expand...
Click to collapse
No problem, i knew it would work perfectly. Battery drain is also low and it doesn't throttle net performance.
I think that for YouTube the only alternative with no root is to use a modified version (look here on XDA if interested).
@Pretoriano80 Not sure I follow you, modified youtube? Search came up blank.
Is that an app/apk to replace the default youtube app? Because when I try to uninstall youtube from phone I get an error msg saying "system app can not be uninstalled". Should I just overwrite?
joppy said:
@Pretoriano80 Not sure I follow you, modified youtube? Search came up blank.
Is that an app/apk to replace the default youtube app? Because when I try to uninstall youtube from phone I get an error msg saying "system app can not be uninstalled". Should I just overwrite?
Click to expand...
Click to collapse
You should be able to deactivate the app and install the modded apk.
Ok, will retry. Seems that iYTBP - injected YouTube Background Playback might be a solution worth trying?
https://forum.xda-developers.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900
If you have tried other ones that works well for you feel free to share and recommend.
joppy said:
Ok, will retry. Seems that iYTBP - injected YouTube Background Playback might be a solution worth trying?
https://forum.xda-developers.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900
If you have tried other ones that works well for you feel free to share and recommend.
Click to expand...
Click to collapse
Yes, you can try the latest x64 version from here - > https://androidfilehost.com/?w=files&flid=236411 - > it doesn't need root and can be installed alongside YouTube, as a secondary YouTube. [emoji6]
joppy said:
Ok, will retry. Seems that iYTBP - injected YouTube Background Playback might be a solution worth trying?
https://forum.xda-developers.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900
If you have tried other ones that works well for you feel free to share and recommend.
Click to expand...
Click to collapse
You Can use newpipe. You Can download it for free on f droid open source market. Works very well
Thx again @Pretoriano80. Now I got a phone that is very usable and responsive and it is still not rooted. I will quote your ad free youtube solution in the first post so others find what they need easily.
Now lets hope all them crazy people out there stops with the root discriminating behavior, so that people in the future damn well self decide to root or not without being locked out from using services, apps or whatever.
joppy said:
Thx again @Pretoriano80. Now I got a phone that is very usable and responsive and it is still not rooted. I will quote your ad free youtube solution in the first post so others find what they need easily.
Now lets hope all them crazy people out there stops with the root discriminating behavior, so that people in the future damn well self decide to root or not without being locked out from using services, apps or whatever.
Click to expand...
Click to collapse
Yeah, in-app ads are also gone. [emoji16]
BTW, if you want to use your Google account with the modified YT app, then you will also need a modified MicroG apk, which is specifically designed for it.
One more thing to get sorted, and that is a backup. I would prefer to find a custom recovery image that works with Huawei Mate 10 Pro, and that will also work well for non-rooted devices.
I have only used twrp myself, but twrp will not work with Mate 10 Pro. I also know about cwm recovery, have not tried it yet but that one will only work for rooted devices. So neither twrp or cwm will work for the BLA-L29/Mate 10 Pro.
Any suggestions?
joppy said:
One more thing to get sorted, and that is a backup. I would prefer to find a custom recovery image that works with Huawei Mate 10 Pro, and that will also work well for non-rooted devices.
I have only used twrp myself, but twrp will not work with Mate 10 Pro. I also know about cwm recovery, have not tried it yet but that one will only work for rooted devices. So neither twrp or cwm will work for the BLA-L29/Mate 10 Pro.
Any suggestions?
Click to expand...
Click to collapse
For backup use Huawei Backup on your phone, or HiSuite on PC... works just fine.
Thank you for all you hard work, I have been a user for many releases prior and love that your software has always been "there and working well". So why only speak up when I have a problem, so for that I apologize.
I have managed to obtain a version of Xposed (Systemless) ported for Magisk installed on my phone (SDK 23) and while Magisk lists Xposed in its installed module list with a check box saying it is active, the Xposed menu shows the green notification area that says it is working, when I install XprivacyLua, and while after the installation of XprivacyLUa, in the Modules section of Xposed there is a check box showing that XprivacyLua is installed and active, the problem is that the Xprivacy app thinks it is not loaded. I sent trace logs captured via adb to the Xprivacy developer and he says that Xposed believes the XprivacyLua app is not installed (even though all indications are that it is active).
Someone who knows more about this than me stated my problem was likely with Toybox being on the phone and something about symlinks where he gave another suggestion about loading Busybox and then following with loading a BusyBox binary zip package via TWRP. All this does is render me not able to access MagiskManager any longer.
Do you know anything about such an issue and how I might get around it? I am saddened that using this valuable tool is being made so difficult from all the new hardware changes. I normally stick with age old phones, but accidents happen, the old one's cracked and my new one won't seem to work with Xposed.
Thanks!
BLU STUDIO XL 2 16/2G
MT6737
ARMv7 Processor rev4 (V71)
armv71
Is there anyone who can help me with my issue? I have poor eyesight and need a larger phone like the BLU, plus as often as I drop phones I cannot afford to buy the fancy, expensive and popular gaming models that everyone seems to purchase.
I am willing to do what ever it takes to resolve the issue, including running traces, submitting file structure maps or anything the developer needs to address the issue with Toybox or whatever the problem that is causing XprivacyLua not to be enabled by Xposed.
Thank you again.
Donphillipe said:
Is there anyone who can help me with my issue? I have poor eyesight and need a larger phone like the BLU, plus as often as I drop phones I cannot afford to buy the fancy, expensive and popular gaming models that everyone seems to purchase.
I am willing to do what ever it takes to resolve the issue, including running traces, submitting file structure maps or anything the developer needs to address the issue with Toybox or whatever the problem that is causing XprivacyLua not to be enabled by Xposed.
Thank you again.
Click to expand...
Click to collapse
What about making system run in permissive mode?
have you tried?
I have not "jumped" from superSU to majisk so my method is to use superSU.
I have a recovery install package that sets file in place to make permissive and force superSU to install systemless.
you can give a try.
the updater-script prints out a message it was made for "blu tank xtreme pro" but it is fine for other phones too. I made it for/ with other dev who wanted to have one step to make root and permissive.
I do not know how will respond to majisk, so better off to try ununstall that first, and start fresh.
H! So I am actually unsure where to post this..
Here's hoping you can figure something out and not be mad at me if this is the wrong place to post this.
Initially, i was going to post this as a Bug report on Github. However, I figured this was not correct.
Technically speaking this also isn't really an issue with magisk itself, more that adobe might have found a way to circumvent magisk anti detection methods.
In short: The App "Adobe Account Access" (com.adobe.ims.accountaccess on the play store: https://play.google.com/store/apps/details?id=com.adobe.ims.accountaccess) seems to have found a way to detect magisk and/or root, even though root detection is hidden in magisk.
The App just displays a prompt, saying "Device not supported. Sorry, your phone is not supported for Adobe Account Access.", even though the device used should be supported.
I checked with adobe community support on whether my Phone is supported or not and according to them, it should indeed be supported: https://community.adobe.com/t5/acco...-access-app-device-not-supported/m-p/11696613
I suspect they have found a way to get around all magisk anti detection methods and i would be grateful if someone would be kind enough to check if there is a workaround or if magisk's detection prevention needs an update.
Unfortunately, i don't have much more to say other than that..
There aren't any magisk log entries that would indicate something went wrong (only entries mentioning the app are"i" loglevel, one coming from hide_list_add and one coming from proc_monitor).
I could not find anything out of the ordinary in the logcat, although i suppose i could be more thorough with my search.
My technical/general info would be:
Magisk Version used: 22.0 (22000) (18)
SafetyNet integrity: Both basicIntegrity AND ctsProfile = pass; evalType = BASIC
ROM used: OxygenOS 10.0.11.GM21BA
Android version: 10
Device name: OnePlus 7 Pro
"Adobe Account Access" App version: 1.6
+++ Please feel free to ask for any additional info in case I missed it +++
Thanks in advance for any productive suggestion!
When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list, and with the Magisk app unhidden.
Didgeridoohan said:
When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list.
Click to expand...
Click to collapse
Oh? That is peculiar.. Damn, that implies an issue somewhere else i reckon ://
It displays it immediately after launching the app. The very first screen..
What phone and which OS (/ROM) are you using? Might just be that my phone is genuinely not supported and the folks over at the adobe community forum lied when saying my phone should be compatible..
Also, which android version are you on if you don't mind me asking?
You don't have any modules installed? No edxposed or lsposed, or magisk modules?
Have you tried root detection apps like Root Beer Fresh to see if indeed the app is unable to detect root? If you try any such app, remember to add it to the Magisk Hide list beforehand, otherwise the app will clearly detect root.
It's a OnePlus 3T with Android 9 ArrowOS. As stated above, it could very well be a module, like EdXposed. Or a root app, or a file or folder on your device, or something completely different.
It's not detecting Magisk at least, that's for sure...
General root hiding tips:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
@Barrel Titor
Samsung Galaxy S7 Custom 9.0 Pie, Magisk 22 root with random name, application without hiding works fine.
Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.
Barrel Titor said:
Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.
Click to expand...
Click to collapse
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.
mario0318 said:
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.
Click to expand...
Click to collapse
I cannot find any results using this search term on google other than my own post on the adobe community forums.. This one: https://community.adobe.com/t5/acco...access-app-device-not-supported/td-p/11695914
@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?
Barrel Titor said:
@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?
Click to expand...
Click to collapse
Well, the well known magisk module MHPC or Magisk Hide Props Config comes to mind. You can change device fingerprints and maybe also give the Device Simulation feature a go, or custom edit any range of configurable props.
You could do so without the module editing the build.props yourself. Or if you stick with edxposed and deal with not having magisk manager's hide enabled, perhaps any of the device spoofers on the xposed repo could fool the app. Or Sudohide if you set Adobe app to hide from any and all apps that are root relevant. May also consider removing directories in your internal and removable storage for things like TWRP or PBRP, Titanium Backup, xposes, etc, you know, things that a simple media scan looking for any sign of root apps might pick up.
But for now, I'd give MHPC a try and change device fingerprint and maybe enable device simulation if simple fingerprint change doesn't work.
I'm having the same issue on a rooted OnePlus 8T
Same for me on op7 pro. Hiding with somiko but Adobe still not working. Nor could I bypass square, it notes root when it pairs Bluetooth