Basically on one slot my phone is rooted but on the other it is not. I play a game that somehow knows that I am rooted even with magisk hide enabled. So they nerf some features insisting I am exploiting the game. I am not. So I have been using non-rooted slot for now.
If I switch to guest mode while on the rooted slot, will guest mode show as rooted or will it be stock?
Thanks
Edit: Looks like root also goes to guest mode.
Related
First my phone's details:
Rooted
Model: Samsung-SGH-I337 (AT&T)
Android Version: 4.2.2
Build: JDQ39.I337UCUAAMDL
Here's the situation...
I'm an IT guy (low on totem) and we're in the Pilot phase for Android using MobileIron. I have a rooted AT&T 32GB S4 and I'm trying to fool MobileIron into believing my phone is compliant. I have done lots of reading on this subject, and nothing has helped, to this point. I have access to the MobileIron server, so I can register, and de-register, my device as often as I want. I plan on reporting this back to the people who get paid more than I do to let them know how secure this is.
Here's what I've tried:
1. I have installed Xposed Framework, and installed RootCloak, but it has zero effect on MobileIron. I couldn't even get to the point in MobileIron setup where I could download our 'secure apps'. (I am aware that RootCloak moved to Cydia, but I read it wasn't as good)
2. I tried using 'Hide My Root' from Play, and that also had zero effect on MobileIron; I got no further than I did with RootCloak.
3. I tried using 'Hide Rooting Lite' from Play, and I was able to download our 'secure apps', and MI required that I create a password/pattern to unlock my phone. In my opinion, this got past the first level of authentication that MI requires, which is a step in the right direction. I have recently learned that MI also scans your list of installed APPs for any APP that requires root.
Do any of you think that changing the names of some of my apps (Titanium Backup, Root Explorer, etc.) would help fool MobileIron? What about trying to DualBoot ROMS? If the secondary ROM that I setup is not rooted, and I have MI installed on it, would it be able to detect root from my primary ROM?
Any help, or ideas that I have not thought of yet, that you geniuses can provide would be greatly appreciated!!
GatorRuss said:
First my phone's details:
Rooted
Model: Samsung-SGH-I337 (AT&T)
Android Version: 4.2.2
Build: JDQ39.I337UCUAAMDL
Here's the situation...
I'm an IT guy (low on totem) and we're in the Pilot phase for Android using MobileIron. I have a rooted AT&T 32GB S4 and I'm trying to fool MobileIron into believing my phone is compliant. I have done lots of reading on this subject, and nothing has helped, to this point. I have access to the MobileIron server, so I can register, and de-register, my device as often as I want. I plan on reporting this back to the people who get paid more than I do to let them know how secure this is.
Here's what I've tried:
1. I have installed Xposed Framework, and installed RootCloak, but it has zero effect on MobileIron. I couldn't even get to the point in MobileIron setup where I could download our 'secure apps'. (I am aware that RootCloak moved to Cydia, but I read it wasn't as good)
2. I tried using 'Hide My Root' from Play, and that also had zero effect on MobileIron; I got no further than I did with RootCloak.
3. I tried using 'Hide Rooting Lite' from Play, and I was able to download our 'secure apps', and MI required that I create a password/pattern to unlock my phone. In my opinion, this got past the first level of authentication that MI requires, which is a step in the right direction. I have recently learned that MI also scans your list of installed APPs for any APP that requires root.
Do any of you think that changing the names of some of my apps (Titanium Backup, Root Explorer, etc.) would help fool MobileIron? What about trying to DualBoot ROMS? If the secondary ROM that I setup is not rooted, and I have MI installed on it, would it be able to detect root from my primary ROM?
Any help, or ideas that I have not thought of yet, that you geniuses can provide would be greatly appreciated!!
Click to expand...
Click to collapse
Hi! Any luck with beating mobile iron?
MobileIron is kicking my ass. I have a Nexus 5 that's never been rooted and I can't get MI to install on this device. Is it because the bootloader is unlocked? I'm in IT as well, and our MobileIron administrators have NO IDEA what to do.
Broadscope said:
MobileIron is kicking my ass. I have a Nexus 5 that's never been rooted and I can't get MI to install on this device. Is it because the bootloader is unlocked? I'm in IT as well, and our MobileIron administrators have NO IDEA what to do.
Click to expand...
Click to collapse
I had a similar issue in my non-rooted M8. MI started working after I did a factory reset .
Hi all,
I use my personal phone (specifically a phone that I own) for both home use and work use and I am considering rooting my phone so I can make some changes to the system UI file. I know that one of the checks that the "Device Policy" app checks for is to see if the phone is rooted so I was wondering if anyone has rooted their phone and successfully been able to pass the device policy check? Specifically I am looking to find out if:
1. would something like root cloak work?
2. if root cloak will not work, has anyone rooted the phone, made the changes, and then disable root leaving the phone running un-rooted so that the device policy check still succeeds? (I ask as I do not need permanent root, just access to fix some of the annoyances that come with stock android).
Thanks,
dave
Device is a SM-N916S from Samsung (Galaxy Note 4 S-LTE Exynos 5433 ver.) for anyone that's wondering. It's current state : Completely stock with no root. USB debugging disabled. No Samsung Account linked to device. Can't change password through ADM. No more guesses left for the password anymore, any more will reset the phone.
So yeah. For the past few days I've been trying to bypass Android Device Manager's remote "Lock" feature that's meant to keep your data safe from thieves. As for why? Long story short : I tried to pull a prank on my brother by remotely locking his device through ADM. I have since forgotten the password (it was a random combination of letters and numbers that I thought I could remember, but obviously not.) and trying to set a new password through Android Device Manager just gives me the infamous "Since Google has verified that a screen lock is already set, the password you entered won't be needed." error message.
Now, if this was a phone that belonged to me, I would just install a custom recovery and remove the password with a password disable zip, but unfortunately, that is not an option here. I probably forgot to mention that I CANNOT void the warranty (as in trip the KNOX counter) under ANY circumstances and would very much like to avoid a factory reset. Am I out of luck here? Or is anyone here aware of a method that can be used to bypass the ADM lock / or a way to backup data with usb debugging disabled. Thanks.
use smart switch to go back to stock firmware
SrikarPrayaga said:
use smart switch to go back to stock firmware
Click to expand...
Click to collapse
Hi, could you explain what you mean by this? Does smart switch work even when the phone is locked? And what would going back to stock firmware do? Thanks.
So I've searched the forums for a while now, and being the noob I am, I do not know what i am looking for. I was trying to root my daughters tablets (Samsung Galaxy Tab 4 8''). I used the CF auto root. Everything list on his download page matched perfectly with what the tablet said in the about device tab (I'm talking about the model number and all the version number were exact. So i use Odin and everything went perfectly. The tablet went through its steps and Odin said PASS in big green letters. But it got stuck in the screen that says "Samsung". So I let it sit there for a while and finally i held the power button and it rebooted. It booted up fully but it kept popping up that all the apps were stopping. Touchwiz and all the storage "has stopped" along with tons of other apps. So i can't go home to get to the apps. I can go into settings and do stuff, but I cant get anything else to work. Is there anything i can go to get Touchwiz to work so that I can navigate? I can provide more info if anyone is willing to help me. Please this my daughters favorite toy in the world. I'll donate $15 to anyone who can help me get the tablet back functional. Thanks! I am such an idiot. I have no idea what I am doing and no clue why I decided to root her tablet.
Duster1d said:
So I've searched the forums for a while now, and being the noob I am, I do not know what i am looking for. I was trying to root my daughters tablets (Samsung Galaxy Tab 4 8''). I used the CF auto root. Everything list on his download page matched perfectly with what the tablet said in the about device tab (I'm talking about the model number and all the version number were exact. So i use Odin and everything went perfectly. The tablet went through its steps and Odin said PASS in big green letters. But it got stuck in the screen that says "Samsung". So I let it sit there for a while and finally i held the power button and it rebooted. It booted up fully but it kept popping up that all the apps were stopping. Touchwiz and all the storage "has stopped" along with tons of other apps. So i can't go home to get to the apps. I can go into settings and do stuff, but I can't get anything else to work. Is there anything i can go to get Touchwiz to work so that I can navigate? I can provide more info if anyone is willing to help me. Please this my daughter's favorite toy in the world. I'll donate $15 to anyone who can help me get the tablet back functional. Thanks! I am such an idiot. I have no idea what I am doing and no clue why I decided to root her tablet.
Click to expand...
Click to collapse
*UPDATE*
I was able to do a factory reset and start over. Although still have the custom kernel warning when it reboots. Is there a way to get rid of that? Thanks!
Do not use CF Auto Root for now, use chainfire's latest Systemless Root, in this time of writing, i can't find the link to his latest systemless root zip, flash it using a custom recovery.
About that kernel warning, it means that you modified something OR rather the CF Auto Root you flashed in the kernel, this happens also when you flash a custom firmware. You can't remove it. But beware if this warning comes out whenever you restart or power on the device, you might have triggered the KNOX status to 0x1 and that means your warranty is now borked and sammy can use it whenever you want a repair from them to deny your request.
Hello experts!
First off I do admit I have cross posted some information here. Perhaps I should have just asked here first. As a lot of research I have been doing lead me here. I am also aware of the XY problem. So I am giving what information I have on my problem and what I have done to resolve it. In a nutshell I need to recover app data from internal storage.
So here is yet another story of a dropped Samsung Galaxy BSOD. The broken screen of death! :-o
So I dropped my phone and the screen broke, fixed it then put on a screen protector that fractured the new screen in my pocket, of all things. Through that it spiraled out and it needed a new LCD as well as screen which failed to repair as LCD remains blank now. I suspect the display controller has somehow fried. Decided to give up and buy a new phone.
My broken phone is a Core Prime G360G. The digitizer doesn't respond. The LCD is blank. The side buttons, volume, power and home, work fine.
The good news. It turns on and technically still works. It has no screen lock. I can plug it in to computer via USB and it mounts over MTP. I can also install apps remotely (so to speak) from another computer from the Play site. I've installed Samsung Switch this way. Switch does work and I managed to back up files from the Windows program which is good but in my case it isn't smart enough as it doesn't back up app data which I need. I also have AirDroid installed and can reach it that way I but didn't enable mirroring before the incident. Trying to use that to download an app (~10MB in my case) just results in the browser stalling.
The bad news. It is not rooted. It has stock standard firmware. USB debugging is not enabled. Last time I tested OTG wasn't supported. At least not for OTG USB sticks.
So in effect it's rooted without being rooted! Yes, i know, I know, Android rule of thumb; before you accidentally drop your phone, even without planning it, and not being a seer, enable USB debugging for no apparent reason! It all makes sense now.
I've spent the last two weeks reading forums all over the place, blogs and watching videos about how to recover data with a broken screen. And in almost all cases they tell you to enable USB debugging. Well that's nice advice and about as useful as advising someone with a broken toilet to sit down, do their business and then flush it! And is met with equally crappy commentary pointing the conundrum out.
My computer has Windows (Vista) and Linux (Mint 64). I read all about ADB and installed this on both Windows and Linux. And tried to talk to it that way with adb and fastboot which failed. I then read of Samsung devices being different, with a download mode, and using this Odin or Heimdall program. So I could "see" the process I tested with my new phone (a J5 Prime as it happens) and learned I needed to use download mode and how to enter it on boot. Recovery mode didn't work as expected. Heimdall was the only program that would work. I managed to view the PIT on my J5. Odin did see my phone but I found the interface harder to work with at first.
I tried on my Core. Blindly got it into download mode. Heimdall could see it. But the transport was buggy as I kept getting USB errors. I ended up removing it then compiling Heimdall v1.4.2 from source. This worked better, even though it was giving empty bulk transfer warnings, but it managed to download the PIT file. So at this point I can blindly get my Core into download mode and am able to communicate with it using Heimdall.
This is where I am at. I would prefer it if a screen mirroring app could be installed that would load up and activate remotely when a client run on my computer is loaded up. I don't care if it is VNC or how it connects. But it would need to load itself up on the phone and work without needing intervention on the phone and without USB debugging. If there is an emergency mirroring app on the Play store or even an APK that can be installed remotely, using AirDroid or any other means, I would be happy to test it. I'd write one myself if knew how to write an app! LOL.
If USB debugging could be enabled by any remote means then I am welcome to hear how. It opens a window to possibility. But a window that is hard to open if it's locked.
So I would prefer to keep this at the app level if possible. Since apps can help. But if need be as long as it doesn't destroy data I am willing to install a custom recovery image. It looks like I will need to do this as I have exhausted all other possibilities. At least, when I read of the latest broken screen mirroring app, there is always a catch of it needing debugging or activating on the phone.
Although there is support for other Core Prime variants, support for my specific G360G model seems to be lacking. The information I read looks vague at best. I read about CWM and TWRP. But on the TWRP site, although there is Core Prime images, nothing is listed for exactly a G360G. There is no point to me flashing TWRP recover image only to find it doesn't work and I have bricked recovery mode. I'd look like a right twerp!
So guys, after all the info I have given you, what's the next step? Thanks.
Okay so just an update here. I have some good news and bad news on my part. I've been hacking around with customising recovery and modifying compatible recovery images in order to get debugging activated.
The good news is I got USB debugging enabled. The bad news is my computer is unauthorised.
I'm stuck at this point. I updated the adb_keys file with what was on my computer and it won't budge. I finally get somewhere and now I've once again hit a wall. This is just so annoying. :-x
The final countdown. After months of cracking and hacking I've broken in! I modded my hack to create the needed folder just to be sure and updated my RSA key. Applied the firmware patch and let it reboot. Even while booting I knew something was different. The digitizer started responding to my touch and making water noises. Which was strange as I never noticed it doing that before.
I issued an adb command and it was accepted. I could then browse around the system. I already had screen mirroring software installed and all it needed was USB debugging working and suddenly it worked. This was a blessing as I found that trying to do other things like going into a root shell or do an adb backup caused a requester to come up on screen. Had I not been able to satisfy that on a virtual screen I would have run into the same trap of circles I had just climbed out of. Having a rooted phone with no root access.
I was then able to install a backup app and extract the data out. Hooray! I had actually installed it from Google Play site remotely but found there was no space for it and it had failed. But the account said it was installed. With a view to a mobile I could then remove another app and install it from Play on the phone itself. Given how well this worked once I learned what was needed to be done I suppose I should make up a guide. An automated script to create an ADB patch wouldn't go far astray.