all thanks goes to ...https://redfern.me/bypassing-root-detection-in-three-intouch/
http://d-h.st/ZVg
I always use the app called "RootCloak" for those kind of apps.
Works perfectly everytime!
joeyzbg said:
I always use the app called "RootCloak" for those kind of apps.
Works perfectly everytime!
Click to expand...
Click to collapse
Same as what I use. Fails for Halifax banking app though
i never had root or unlocked boot loader but still got the error as it is cyanogen and i didn't want to root to root cloak to get three in touch
It says that my carrier is unsupported, any way to bypass that?
joeyzbg said:
I always use the app called "RootCloak" for those kind of apps.
Works perfectly everytime!
Click to expand...
Click to collapse
Used this myself, but it doesn't work with ART unfortunately
ricebus said:
It says that my carrier is unsupported, any way to bypass that?
Click to expand...
Click to collapse
Are you with Three?
bobthecooldad said:
all thanks goes to ...https://redfern.me/bypassing-root-detection-in-three-intouch/
http://d-h.st/ZVg
Click to expand...
Click to collapse
this hides root and cyanogen mod without needing to root and void warranty so it will run on our phones
any tips,? I can't install it.
The install button doesn't respond to my press
ah no problem sussed it, had to install it using adb.
app updated.
An update has been released by 3uk today.
Can anyone provide the new .apk with the root check removed again.
Thanks
More importantly.. anyone worked out how to use it on tablet?
Well I've tried to install big apps like Fifa 15. Well this error keeps popping up.
Eror 905 Could not install application.
Is there a fix for this?
I've read that its related to the Memory Leak in lollipop?
Could someone please tell me how to resolve this.
sagar846 said:
Well I've tried to install big apps like Fifa 15. Well this error keeps popping up.
Eror 905 Could not install application.
Is there a fix for this?
I've read that its related to the Memory Leak in lollipop?
Could someone please tell me how to resolve this.
Click to expand...
Click to collapse
Try this and remember:Google is your friend.
http://wikitechsolutions.com/9958/how-to-fix-error-905-android
Sent from somewhere
Wolfcity said:
Try this and remember:Google is your friend.
http://wikitechsolutions.com/9958/how-to-fix-error-905-android
Sent from somewhere
Click to expand...
Click to collapse
Yeah I know about this solution (My friend Google..), But I dont get the option of disable updates. The only things are Force Stop and Disable.
sagar846 said:
Yeah I know about this solution (My friend Google..), But I dont get the option of disable updates. The only things are Force Stop and Disable.
Click to expand...
Click to collapse
Are you rooted? You can try to uninstall and reinstall it. Maybe someone has a flashable zip or you can do it with the help of Aroma gapps.
Sent with somewhat
Shoud I install Aroma Gapps? (Cause I use Nano)
Yes I am rooted but don't want to do that.
sagar846 said:
Shoud I install Aroma Gapps? (Cause I use Nano)
Yes I am rooted but don't want to do that.
Click to expand...
Click to collapse
If you don't want to install/reinstall playstore (for it's a system app) you can try aroma gapps because there you can decide what you want to flash. Uncheck everything you don't need and just flash playstore. Just an idea.
You can also uninstall playstore with titanium and move the new playstore apk to system with a file manager like root explorer.
Sent with somewhat
So I purchased the samsu g unlocked but when. I choose to install the theme it s
Does not work.. It says installing and than it sends me to install a package.. What am I doing wrong?..
egren58 said:
So I purchased the samsu g unlocked but when. I choose to install the theme it s
Does not work.. It says installing and than it sends me to install a package.. What am I doing wrong?..
Click to expand...
Click to collapse
That's what it does. Each overlay is a separate install. It threw me off the first time, too.
Sokudoningyou said:
That's what it does. Each overlay is a separate install. It threw me off the first time, too.
Click to expand...
Click to collapse
So I manually have to install all of them?
egren58 said:
So I manually have to install all of them?
Click to expand...
Click to collapse
Yep.
I have a problem with my Galaxy S10. I have rooted the phone with magisk. If I open any app that requires the camera, the whole phone crashes.
I wanted to ask why that may be
RoyalPriis said:
I have a problem with my Galaxy S10. I have rooted the phone with magisk. If I open any app that requires the camera, the whole phone crashes.
I wanted to ask why that may be
Click to expand...
Click to collapse
Weird, that doesn't happened to me. Does it ask you permissions to access your camera, or does it crash immediatly without asking anything ?
KuraKira37 said:
Weird, that doesn't happened to me. Does it ask you permissions to access your camera, or does it crash immediatly without asking anything ?
Click to expand...
Click to collapse
It crashes immediatly even when I open the normal camera app
RoyalPriis said:
It crashes immediatly even when I open the normal camera app
Click to expand...
Click to collapse
Are you sure you booted on the right partition ?
Check with "root checker" if magisk hide work properly, if not, you may be on the wrong partition.
If you're on the right partition, maybe reflash a stock rom and start from scratch. It could be that something went wrong in the process.
KuraKira37 said:
Are you sure you booted on the right partition ?
Check with "root checker" if magisk hide work properly, if not, you may be on the wrong partition.
If you're on the right partition, maybe reflash a stock rom and start from scratch. It could be that something went wrong in the process.
Click to expand...
Click to collapse
yes I am on the right partition
RoyalPriis said:
yes I am on the right partition
Click to expand...
Click to collapse
Okay, so apart from reflashing everything from scrath to see if that resolves the issue, i don't have any idea on how to solve your problem...
But as you have a rooted device, maybe you could help me by answering mine here
KuraKira37 said:
Okay, so apart from reflashing everything from scrath to see if that resolves the issue, i don't have any idea on how to solve your problem...
But as you have a rooted device, maybe you could help me by answering mine here
Click to expand...
Click to collapse
I tried and exactly the same problem
RoyalPriis said:
I have a problem with my Galaxy S10. I have rooted the phone with magisk. If I open any app that requires the camera, the whole phone crashes.
I wanted to ask why that may be
Click to expand...
Click to collapse
If you have TWRP recovery installed, update it to a newer version.
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
Did you remove all modules prior to rooting March update?
Tulsadiver said:
Did you remove all modules prior to rooting March update?
Click to expand...
Click to collapse
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
dimm0k said:
@Tulsadiver no, I neglected to do that since I was able to do so previously without ever having to... any idea how to do so at this point? do I need to wait for an updated image from your thread of https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557 ?
Click to expand...
Click to collapse
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Tulsadiver said:
The old one might work but I'm making a new one for you now...
Edit: here it is
https://www.androidfilehost.com/?fid=4349826312261736126
Click to expand...
Click to collapse
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Tulsadiver said:
Did you put the whole folder from the zip file?
ramdisk/overlay.d
Click to expand...
Click to collapse
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
dimm0k said:
any suggestions on how to fix this? updated to the Mar 2020, extracted the boot image, patched in Magisk, flashed, and rebooted like I have done with the previous updates, however once the device is booted up all I get is a black screen! device is still responsive as pressing the power button brings up a menu allowing me to shutdown or reset. flashing a non-modded boot allows me to use the device normally again. help!
Click to expand...
Click to collapse
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
dimm0k said:
I don't have the link handy, but there's a gpay module fix that should fix that for you. I'm definitely able to use Google Pay now!
Click to expand...
Click to collapse
Is it the MagiskHide Props Config module the one you're talking about?
So, I can't get Magisk to patch the boot image. It crashes every time I click let's go. I was on canary, went to the stable channel, rebooted, pushed the boot file over a few times, still nothing. Any ideas?
dimm0k said:
woohoo! this worked... now I need to figure out which module is fscking me... while you were making this, I followed the steps in your thread to attempt to create a boot image with core only, but mine didn't work. any idea why? regardless, thank you!!
Click to expand...
Click to collapse
Did you figure out which module? I have the same problem.
EVR_PR said:
I was able to update and root, but latest Magisk stable is showing ctsprofile as false. Any ideas on how to fix this?
Click to expand...
Click to collapse
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
dimm0k said:
hah! I'm in idiot running around with my head cut off. I just checked, I dumped that folder into the root and not into ramdisk! anyway, turns out the culprit of my issue was your mod to increase the notifications to 7! hopefully you can make an updated mod for this update when you get some time
Click to expand...
Click to collapse
I had some stuff running. Here you go.
Tulsadiver said:
I had some stuff running. Here you go.
Click to expand...
Click to collapse
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
arh2o said:
Same issue, here's what I'm seeing with the ctsprofile. Magisk might need to be updated to support this feature drop.
Click to expand...
Click to collapse
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
EVR_PR said:
Hey Tulsadiver, does your MagiskManager pass CTSProfile or are you using a module to fix the issue of it failing?
---------- Post added at 06:15 PM ---------- Previous post was at 06:13 PM ----------
I dont have the preserve dm-verity option on nor did I have it on when I patched the boot image. Seems like that doesn't make a difference either?
Click to expand...
Click to collapse
Mine shows it as passing. I'm using beta channel.
Weiii said:
Did you figure out which module? I have the same problem.
Click to expand...
Click to collapse
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
dimm0k said:
for me it was the module provided by Tulsadiver to increase the notifications to 7... I'm guessing any modules that makes changes to system files might likely be the culprit. list your modules, but all I can do is take a guess as to which one it would be
Click to expand...
Click to collapse
For me it was smali patcher, i think. Not 100% sure because I booted from Tulsadrivers once I got stuck at the Google logo, this took me into safe mode inside of magisk. Every time I would reboot (after deleting the magisk cache file) with smali patcher enabled it would get stuck. After I disabled magisk safe mode I re-installed smali patcher(re-creating the zip on my desktop). After that everything booted fine and passed all safetynet checks.
EVR_PR said:
Is it the MagiskHide Props Config module the one you're talking about?
Click to expand...
Click to collapse
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
1dopewrx05 said:
No, not magisk props config. I linked the module he was referring to. Make sure during installation you hit the volume up key when it prompts you to at the end because you need to let it clear the gpay data.
Click to expand...
Click to collapse
I went ahead and installed the Magisk Props config module before I read your message and that fixed the problem. Apparently Google forgot to certify this specific build for ATT (the one ending 004.A1). Thank you for your help though.