Related
I have to install citrix mobile connect to connect to the Exchange server at work, and citrix will not run on a rooted device
is there a way to overcome this or perhaps install a different app to receive exchange sync?
(for example will "hide root" work here)?
You can try voodoo rootkeeper that can perform a temporary unroot.
I will start with this thread and see if blocks the exchange sync, http://forum.xda-developers.com/showthread.php?t=1957273
I hope rooting doenst erase my data, as I am already working for a week with the device.
Anyway, I will run titnium backup before I start
ofird said:
I will start with this thread and see if blocks the exchange sync, http://forum.xda-developers.com/showthread.php?t=1957273
I hope rooting doenst erase my data, as I am already working for a week with the device.
Anyway, I will run titnium backup before I start
Click to expand...
Click to collapse
titanium backup needs root
just found that out
So - any other ROM back up program out there that doesnt neet root?
or perhaps i dont have to worry about losing data with CFAuto root?
ofird said:
just found that out
So - any other ROM back up program out there that doesnt neet root?
or perhaps i dont have to worry about losing data with CFAuto root?
Click to expand...
Click to collapse
rooting does not delete data, whereas you never can be sure 100% that it will go as planned. Nevertheless there is not app that can backup 100% of your rom without root.
so i will take my chances :0)
Ke sera sera
done, went smooth
although I am running "root checker" and it says system running slow and doenst return results
is there a specific app i should install now ? "super SU" or something?
ofird said:
done, went smooth
although I am running "root checker" and it says system running slow and doenst return results
is there a specific app i should install now ? "super SU" or something?
Click to expand...
Click to collapse
If you rooted it correctly SuperSU or SuperUser should already be installed. Did you have any progress getting Citrix to work while rooted? Im in the same situation and I've only been able to get it to work briefly with Touchwiz based ROMs with SuperSU. All others give me a " cannot connect due to a security policy" error - even after disabling root and trying to re-enroll. Its a beast...
Yes I have
I used hide my root throughout all the process.
I check with root checker to validate it's indeed hidden.
And I keep running hide my root at all times
ofird said:
Yes I have
I used hide my root throughout all the process.
I check with root checker to validate it's indeed hidden.
And I keep running hide my root at all times
Click to expand...
Click to collapse
Nice! I'm gonna give that a go then. Thanks
tscalia2 said:
Nice! I'm gonna give that a go then. Thanks
Click to expand...
Click to collapse
I have had to do the same...and all seems to work. But I had to also install two more apps enforced by policy; Lookout, and Touchdown.
Any ideas on what these do?
Touchdown is a great app for synching all your mails, notes and Exchange data.
I use it
I don't know what lookout is for
I used Towelroot and KindleFree to root my HDX and install Google apps. I did not disable OTA in KindleFee.
Now when I check for updates, it says "Last updated failed", when I try to set off an alarms off Amazon's site it fails and it doesn't locate the HDX.
I suspect that either Towelroot or KindleFree disabled something, but just to make sure, do they disable something by default that prevents those three things from working? Wanna make sure something else isn't wrong with my device.
well
herzzreh said:
I used Towelroot and KindleFree to root my HDX and install Google apps. I did not disable OTA in KindleFee.
Now when I check for updates, it says "Last updated failed", when I try to set off an alarms off Amazon's site it fails and it doesn't locate the HDX.
I suspect that either Towelroot or KindleFree disabled something, but just to make sure, do they disable something by default that prevents those three things from working? Wanna make sure something else isn't wrong with my device.
Click to expand...
Click to collapse
Well I am guessing if you say you have gapps working that you had to install hdxposed module and framework... If you had read OP of the modification that you installed you would know already that the 1.3 version blocks ota, and probably as a side effect blocks a couple of other Amazon exclusive services .
jimyv said:
Well I am guessing if you say you have gapps working that you had to install hdxposed module and framework... If you had read OP of the modification that you installed you would know already that the 1.3 version blocks ota, and probably as a side effect blocks a couple of other Amazon exclusive services .
Click to expand...
Click to collapse
Yes, I totally forgot that I installed that as well! It's what's doing it. I posted in that thread, but any idea what it does to disable OTA? I tried completely removing it modules, Xposed and ran the script to enable OTA, but it still doesn't work.
herzzreh said:
Yes, I totally forgot that I installed that as well! It's what's doing it. I posted in that thread, but any idea what it does to disable OTA? I tried completely removing it modules, Xposed and ran the script to enable OTA, but it still doesn't work.
Click to expand...
Click to collapse
What is your current system ?
So on my kindle i had everything installed to have the play store working and i got the play store to work and i got the youtube app to work. And so what happened was i deleted the youtube app and installed the newest version and when i opened youtube it gave me the google play services error, but the play store itself still worked.
So what i did was i uninstalled all the google account manager, google services frame work, etc.
And tried to fix the youtube issue by reinstalling all of those things. I started by installing google account manager, and then i rebooted it to install the next thing. Only, when it started up i could unlock the device, but none of the apps would load. So i did a stupid thing and factory reset it, which i think got rid of the root.
I have no idea what to do. I couldn't find any thread about this.
The notificaton bar works and the navigaton buttons show up on the side. So i can get to settings, but the carousel and home screen won't load after i unlock it
here are some pics:
i can't post links because i'm a new member so type it in without spaces
http :// imgur . com / a/ uuB6f
What version of firmware do you use?
ONYXis said:
What version of firmware do you use?
Click to expand...
Click to collapse
13.3.2.6
Sorry, I missed that you did hard reset. without root I think i can do nothing.
Only way is update to 13.4.1..1 http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813 (if you can go to settings) and lose root. Of course if your devices HDX 7.
ONYXis said:
Easiest way , i think, is install safestrap and flash stock firmware by SafeStrap (without wiping anything!)
after that gapps need to install again.
Adb working?
Click to expand...
Click to collapse
How am i going to install safestrap when i can't open any apps?
android2204 said:
How am i going to install safestrap when i can't open any apps?
Click to expand...
Click to collapse
Sorry, I missed that you did hard reset. without root I think you can do nothing.
Only way is update to 13.4.1..1 http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813 (if you can go to settings) and lose root possibility.
What do you mean by loose root possibility?
android2204 said:
Do you mean by loose root possibility?
Click to expand...
Click to collapse
Sorry. English isn't my native language so I don't understand your question.
I wrote that if you upgrade to 13.4.1.1 you will not be able to obtain root.
How do i update?
http://www.amazon.com/gp/help/customer/display.html?nodeId=201390340
link to update file https://kindle-fire-updates.s3.amazonaws.com/update-kindle-13.4.1.1_user_411009920.bin
Yes. but how would i install it?
you wrote ""So i can get to settings, ", what difficulties after that?
Can you get into Settings - Device - System Updates?
nevermind. so i followed the instructions and put the update into the internal storage folder but when i went into system updates on my kindle the box said "check now" instead of "update" so when i tap check now it says "last update failed".
android2204 said:
kindle the box said "check now" instead of "update" so when i tap check now it says "last update failed".
Click to expand...
Click to collapse
Try to turn off wifi and reboot.
You should see that your device has found update, no more variants.
I'll try it again after school. What would I do next if I get the error again?
I have no idea. This is one variant. if tablet do not found update - this says about broken symlinks for example or something else that anyway do not fix without root.
btw check your root status:
adb shell
su
ONYXis said:
I have no idea. This is one variant. if tablet do not found update - this says about broken symlinks for example or something else that anyway do not fix without root.
btw check your root status:
adb shell
su
Click to expand...
Click to collapse
I didn't really understand any of that. What is a broken symlink? And I don't think I'm rooted because I factory reset it.
Also, how could I check root status and what would be the purpose?
Okey. You not rooted now, so do not pay attention.
Your one method to get working device is update firmware.
In way that I described.
If you do not see "update" button after pulling file - sorry. no other idea.
So basically, if this doesn't work I'm screwed?
Anyone else got any ideas?
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
njaustin123 said:
My observations:
MyProfiles Pro not able to turn data ON/OFF with ROOT permissions even if the root permission is there for the app.
One Power Guard battery app works, but cannot tweak the profiles, it says root needed. I seriously doubt if it really is working.
Click to expand...
Click to collapse
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
dimm0k said:
I'm currently rooted and restoring my apps, however it seems like with each new version of Android the external SD gets trickier and trickier. A lot of apps these days use the round about method of having you choose the card to write to via the file manager, unfortunately not all apps do this and one of them looks to be the ever popular Tasker. am I missing the option or am I screwed and have to rewrite all my tasks to write to the internal storage?
another issue is with Secure Settings mainly used in conjunction with Tasker... when I start it up it fails to recognize su and never prompts me via SuperSU for permissions to grant. anyone have any workarounds or fix for this?
lastly, is BusyBox still usable under Marshmallow? i loaded it up and everything seemed fine, but after a reboot Google Play Services, Amazon, Youtube and some others kept crashing.
Click to expand...
Click to collapse
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
Whenever you do a clean fresh flash Rom at the setup most rooms let you restore all your previous apps from google, no need to go to the play store it does it automatic. If you made a backup just restore the data.
Sent from my LG-H901 using XDA-Developers mobile app
dimm0k said:
what I've realized is that SuperSU is running in systemless mode, which is causing some issues for outdated apps that were hardcoded to find 'su' in /system. some workarounds are putting a dummy file named su in /system or getting SuperSU to run in /system.
Click to expand...
Click to collapse
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
chernabog88008 said:
I learned this the hard way in updating from LP to MM; do NOT restore your apps from a backup under LP. I did that, and was having nothing but issue after issue. Best bet, backup everything not an app, go back to the google play store, and reinstall everything from there. Any apk's you had you installed, install them fresh. I was literally to the point of shipping the phone back to T-Mobile and going to an S7 it was such a pain in the neck. After I learned after the 4th factory reset from LG Bridge, I've never had any issues since.
Click to expand...
Click to collapse
I have witnessed this, mainly with Google apps. after restoring the app with data the app would randomly crash... removing the app and installing it from Google fixes it, but I have not experienced this with non-Google apps. I'll keep this in mind the next go around when restoring my stuff.
njaustin123 said:
Thanks. But can you give me little bit more details on that. How can I get SuperSU to run in /system? I checked settings of SuperSU app, but could not find.
Also I tried to create a new file called su in /system with Root Browser of ROM Toolbox, but it says 'failed'
Click to expand...
Click to collapse
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
after doing some research and from my understanding, the bad news is that it looks like it's up to devs to add the feature of writing to the external SD via the Storage Access Framework (SAF). unfortunately it doesn't look like an easy task, as the developer of Tasker mentioned that he won't be implementing this since the number of external SD users are far and few =( and would revisit it if that number changes.
the good news for those of us smart and brave enough to root our devices, this is solvable via editing packages.xml and adding in one line for each app you want to "fix". this is documented here
justice26 said:
I am having issues with the camera in manual mode it keeps force closing
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
works fine for me here... are you using stock ROM?
dimm0k said:
you won't be able to change SuperSU to be in systemless mode within SuperSU... look here for the non-systemless root method that you'll need to flash in TWRP. realize that if you do this flash that it most likely will break Android Pay. not sure if you need to mount /system as rw in Root Browser before you can create files there or if Root Browser does it for you automatically?
Click to expand...
Click to collapse
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
njaustin123 said:
I don't want to break stuff like Android Pay though I am not using it right now.
And about putting the file, in ROM Toolbox it says rwxr-xr-x for /system. Doesn't that mean write is there?
Click to expand...
Click to collapse
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
dimm0k said:
I believe non-systemless root only breaks Android Pay because of the way Android Pay is designed, as I believe it needs /system to be "pure". just want you to know that I have not done anything and have left everything as is, systemless root. seems like the only app I had that needed root was Secure Settings, which doesn't look like it will ever be updated anytime soon so I'm trying to ween myself away from that and do everything via Tasker without that plugin. as for you, if you're lucky, write to the apps you're having issues with and have them update it for systemless root. the issue is that their apps were looking for root specifically in /system, but with systemless root the su binary is now in /su/bin. as for putting a dummy su file in /system, I'm not entirely sure that would make your apps work and if it would break Android Pay if you did so. regardless, it doesn't hurt to try as you can simply remove the dummy su file to revert back to systemless. I believe those permissions you've listed for /system does does mean it can be written to, however it has to also be mounted as rw. check that via a terminal by issuing "mount | grep /system". you will probably see a ro in parenthesis or simply try to put a file in there.
Click to expand...
Click to collapse
OK, so here is it: I was able to mount /system as rw with the terminal emulator in ROM toolbox and then create a dummy file named su. Rebooted the phone, both the apps still fail. I will write to the developers. For the time being, I am OK turning data on/off manually along with using MyProfiles for other things. And for the One Power Guard, I believe freezing many of the T-Mobile and LG junk using Titanium and having SetCPU with a little bit under-clocking have already made the battery better. So I can wait. Am also evaluating Craig's Root Battery App instead of OPG. Thank you anyways.
I have a rooted Samsung SG10Exynos/OS9 that bypasses SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2 (meets BASIC INTERGITY) that I have been using the Starling Bank app 2.92.1.79025 without an issue. I stupidly upgraded to the latest version and got the attached screenshot saying that I had 14 days to restore the device to factory settings (I was still able to use the app after pressing ok). I even more stupidly thought that I could revert back to the previous version that I was using, using Titanium Backup which failed (the app would just flash continuous on launch) and then Swift backup (where it would just repeatedly crash even even before being launched requiring a force stop)
If I wipe data/uninstall/restart phone and install fresh from google play, I now get the attached screenshot saying again to restore to factory, but the button says close app. So being a digital bank, I'm now locked out of my account.
I've tried to install previous versions from APKMirror mirror after wiping data/uninstall/restarting phone, and then just restoring my data with my Titanium/Swift backups but still no joy.
Does anyone know how to downgrade/install not the latest version of Starling Bank, which doesn't have the increased STRONG INTERGITY check?
nukescript said:
I have a rooted Samsung SG10Exynos/OS9 that bypasses SafetyNet with the help of Magisk 26.0 & safetynet-fix-v2.4.0-MOD_1.2 (meets BASIC INTERGITY) that I have been using the Starling Bank app 2.92.1.79025 without an issue. I stupidly upgraded to the latest version and got the attached screenshot saying that I had 14 days to restore the device to factory settings (I was still able to use the app after pressing ok). I even more stupidly thought that I could revert back to the previous version that I was using, using Titanium Backup which failed (the app would just flash continuous on launch) and then Swift backup (where it would just repeatedly crash even even before being launched requiring a force stop)
If I wipe data/uninstall/restart phone and install fresh from google play, I now get the attached screenshot saying again to restore to factory, but the button says close app. So being a digital bank, I'm now locked out of my account.
I've tried to install previous versions from APKMirror mirror after wiping data/uninstall/restarting phone, and then just restoring my data with my Titanium/Swift backups but still no joy.
Does anyone know how to downgrade/install not the latest version of Starling Bank, which doesn't have the increased STRONG INTERGITY check?
Click to expand...
Click to collapse
It will force you to use the latest app.
Block firebaseremoteconfig.googleapis.com
theoneofgod said:
It will force you to use the latest app.
Block firebaseremoteconfig.googleapis.com
Click to expand...
Click to collapse
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Undeadwolfy said:
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Click to expand...
Click to collapse
You could try Magisk Delta as it now acts as whitelist so you add only what you want with root. This won't bypass Starling security though. You need to also block address above.
Undeadwolfy said:
Also having the same issue. Is this something I should be blocking in Zygiskhide? I can't see it there. Googling the above isn't helping me.
Click to expand...
Click to collapse
Blocking this address (firebaseremoteconfig.googleapis.com) through AdAway has fixed it for me! That is along with all the things that were needed to run it previously.
theoneofgod said:
You could try Magisk Delta as it now acts as whitelist so you add only what you want with root. This won't bypass Starling security though. You need to also block address above.
Click to expand...
Click to collapse
I think the part where I'm stuck is, what would you suggest to block that address? I can't do that in HMA or in Denylist because it doesn't exist.
I've tried blocking in AdAway and manually adding and still getting Starling recognising root.
I've blocked anything Google Play Services, Play Protect, Wallet too. Starling is my main bank. Has only been an issue in the last couple weeks.
A13 P6 Pro running the April security update 13 (TQ2A.230405.003.E1), Magisk 26101, USNF 2.4.0 Mod 1.2, passing Safetynet Basic+ CTS.
Will look at Magisk Delta next.
marian42 said:
Blocking this address (firebaseremoteconfig.googleapis.com) through AdAway has fixed it for me! That is along with all the things that were needed to run it previously.
Click to expand...
Click to collapse
This isn't working for me :/. Can you share what other modules you're running/how you've set up Magisk?
I followed the directions in this video.
I didn't do the final step where he renames the Magisk app, seems that it isn't necesary.
The YASNAC app shows that the device passes "Basic integrity" and "CTS profile match".
Also remember that blocking firebaseremoteconfig.googleapis.com might break other apps that use this domain (I've found one so far).
Undeadwolfy said:
I think the part where I'm stuck is, what would you suggest to block that address? I can't do that in HMA or in Denylist because it doesn't exist.
I've tried blocking in AdAway and manually adding and still getting Starling recognising root.
I've blocked anything Google Play Services, Play Protect, Wallet too. Starling is my main bank. Has only been an issue in the last couple weeks.
A13 P6 Pro running the April security update 13 (TQ2A.230405.003.E1), Magisk 26101, USNF 2.4.0 Mod 1.2, passing Safetynet Basic+ CTS.
Will look at Magisk Delta next.
Click to expand...
Click to collapse
It's a recent update that broke it.
Try Magisk 26.1, enable Zygisk and enforce deny list. Add systemless hosts. Add only Starling to the deny list.
Install safetynet fix 2.4.0 mod 1.2 by displax.
Add the domain I posted to adaway blocklist. Make sure its enabled and in root mode.
theoneofgod said:
It's a recent update that broke it.
Try Magisk 26.1, enable Zygisk and enforce deny list. Add systemless hosts. Add only Starling to the deny list.
Install safetynet fix 2.4.0 mod 1.2 by displax.
Add the domain I posted to adaway blocklist. Make sure its enabled and in root mode.
Click to expand...
Click to collapse
That's exactly how I have it running now. No change.
Undeadwolfy said:
That's exactly how I have it running now. No change.
Click to expand...
Click to collapse
It's the domain that did it for me. Working fine as of now.
theoneofgod said:
It's the domain that did it for me. Working fine as of now.
Click to expand...
Click to collapse
Thanks for updating. I have both of these in my AdAway too
Code:
firebaseinstallations.googleapis.com
firebaseremoteconfig.googleapis.com
Nothing doing
Undeadwolfy said:
Thanks for updating. I have both of these in my AdAway too
Code:
firebaseinstallations.googleapis.com
firebaseremoteconfig.googleapis.com
Nothing doing
Click to expand...
Click to collapse
Clean install for Starling? I'm trying to think if I did something else.
Oh. Have you "hidden" Magisk?
Just to weigh in here, I can confirm blocking:
firebaseremoteconfig.googleapis.com
Does indeed allow the Starling app to work. Yes blocking Firebase is going to stop some applications working, but you could always pause AdAway until you are done using the problematic app then resume AdAway when you want to use Starling.
Many thanks @theoneofgod
Not working
Reverting the Starling app back to version 2.95.1.79953 fixes things - just don't forget to re-add it to the Deny List.
I'll probably stay on this version until a new fix is found for the current version 2.96.0.80202.
darsh said:
Reverting the Starling app back to version 2.95.1.79953 fixes things - just don't forget to re-add it to the Deny List.
I'll probably stay on this version until a new fix is found for the current version 2.96.0.80202.
Click to expand...
Click to collapse
Wild, even this didn't work for me. No idea why I'm having issues.
Hi All
Quick update - Can confirm that rolling back to 2.95.1.79953 does fix things for now
This is using adaway to block the Firebase URLs in a custom host file and using enforce denylist. It doesnt work beyond that for now.
I swapped over to Magisk Alpha for now but i dont know what Starling are doing in the background to see that you have root at this point. Its very annoying
- Edit 2
They seem to be detecting the Enforce Denylist in Magisk (In any form)
Disabling it on version 2.95.1 shows the app can see root. Enabling it allows the app to proceed as if you are not rooted.
Give KernelSU a try if you can. No modules or any workarounds required.
theoneofgod said:
Give KernelSU a try if you can. No modules or any workarounds required.
Click to expand...
Click to collapse
Isnt that the same as the setting in magisk that hides root from everything not on the su list. Which also doesnt work.