In preparation for Mario Run, and knowing that Nintendo doesn't work well with Rooted devices I decided it was time to upgrade my ROM while dropping root.
I had been running cm-13.0-20160129-MARSH1.9.7, with a normally flashed SuperSU. Doing a quick look at the options I went with an upgrade to the most recent SlimOS, Slim-bacon-7.1.1.build.0.14-BETA-20170303-0805.
For some reason, apps such as Flipp have been earning me about the safety risks of running rooted; and even though the SuperSU app tells me I'm not rooted once I installed it, I'm getting a close on startup trying to run Mario Run. Do I have to revert to stock to fully get rid of root?
Life101 said:
In preparation for Mario Run, and knowing that Nintendo doesn't work well with Rooted devices I decided it was time to upgrade my ROM while dropping root.
I had been running cm-13.0-20160129-MARSH1.9.7, with a normally flashed SuperSU. Doing a quick look at the options I went with an upgrade to the most recent SlimOS, Slim-bacon-7.1.1.build.0.14-BETA-20170303-0805.
For some reason, apps such as Flipp have been earning me about the safety risks of running rooted; and even though the SuperSU app tells me I'm not rooted once I installed it, I'm getting a close on startup trying to run Mario Run. Do I have to revert to stock to fully get rid of root?
Click to expand...
Click to collapse
Use latest lineage os.
Related
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
filmfanatic09 said:
Hi everyone, new guy here.
I'm rooted and currently running 9.18.79 with Verizon. I'm trying to install the 9.18.94 OTA update, but it fails everytime. After I select "Install Now" it reboots and starts to install, but then I get the Android robot on its back with the red triangle. The phone then reboots again and I get a message that says the software update failed. What's the secret to updating when rooted (while also making sure to still have root access afterward)?
Thanks...
Click to expand...
Click to collapse
You cannot be rooted or you must hide root w/ voodoo or super su. Also you must use stock recovery.
the update will not actually fail if you are rooted, although it may report failing.
if it actually fails, you can obviously see it doesnt go through the process, then there is some other factor causing it to fail.
some things that would cause it to fail all together are: non stock recovery, freezing any bloat, removing any bloat, pretty much any modifications to the stock software other than rooting will cause it to fail.
once you have any system deficiencies fixed, use voodoo from the market to protect root and temp unroot before taking the update.
if you cant figure out what you did to the system to fix it, you may want to re-flash using the proper utility for your current system, re-root, protect and temp unroot through voodoo, then try the update again.
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
filmfanatic09 said:
Thanks for the replies.
The primary reason I rooted in the first place was to remove a ton of unwanted bloatware, so at this point it's not even close to resembling the stock software. What are my options? Do I really have to re-install everything I deleted, or is it possible to flash the whole system back to stock?
Click to expand...
Click to collapse
you can flash the hole system using this http://forum.xda-developers.com/showthread.php?t=2474393 get the 1.33 version to match what you are on or the 1.34 to go right to the version you are trying to upgrade to. either is fine.
I noticed that the pro version of SuperSu has a survival mode option. Should I have this enabled all the time? or should it only be enabled when I am ready to make a OTA update?
Just leave it where it is. I'm not even sure if it'll work with an ota. The nexus 5 is so easy to root that I've never tried it. It had been helpful on some other devices butt it's not needed with the n5
gee2012 makes a good point for cm roms of you want to maintain supersu
Edit out of curiosity I did enable survival mode on 4.4. It does survive update to 4.4.2
Sanvido said:
I noticed that the pro version of SuperSu has a survival mode option. Should I have this enabled all the time? or should it only be enabled when I am ready to make a OTA update?
Click to expand...
Click to collapse
You can turn it on all the time, also when you flash CM superSU will remain the main superuser app.
You leave it on all the time as I assume it has scripts to reinstall SuperSU if certain files are removed. It currently works fine for me with OmniROM OTA updates.
Thanks guys for the answer.
Charlular said:
You leave it on all the time as I assume it has scripts to reinstall SuperSU if certain files are removed. It currently works fine for me with OmniROM OTA updates.
Click to expand...
Click to collapse
^^^
Well, of course you would keep root with OmniROM, since it is a rooted rom.
Why wouldn't it keep root when you're using a ROM that requires root to begin with?
Forgive me for being a compleat (sic) Nitwit... but I thought that Rootkeeper and Survival Mode in SU were supposed to keep root through an OTA update for the stock ROM, like going from 4.3 to 4.4 which I think is impossible because when I tap 'check for updates', the message comes up that (and I'm paraphrasing here'... can't be updated because your system has been modified.
When reading through all the caveats in OTARootkeeper in the Play Store, it seems to say that you can un-root temporarily in order to install a new ROM update, and then re-enable root.
Of course, then the Dev. goes on to say that OTARootkeeper won't work with SuperSU installed because OTARootkeeper has it's own version of SU built in.
Am I right or wrong... and if I'm wrong, I wish that somebody would explain it to me exactly where.
Am I correct in assuming that OTARootkeeper will allow temporarily un-rooting for the purpose of installing let's say, an update to the stock ROM which I happen to be running, and then re-rooting and still keep root status?
I've had OTARootkeeper installed for quite a while, but I read that it no longer works with 4.3 to 4.4 stock ROM updates anyway, so I guess my comments become moot.
So I can successfully install superuser v2.40, but it's not working with one of my apps (puzzle and dragons). I have been told me to downgrade to 2.25, but I have been having issues.
The problem is no matter what, when I flash 2.25 it gets stuck in a bootloop. Flashing it on stock, and even flashing it over 2.40, and flashing it over 2.40 when clicking the replace button in the superuser app. What am I doing wrong? Is 2.25 not compatible with my phone?
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
experience7 said:
Hi First of all, if you have any compatibility issues with apps try upgrading them rather than downgrading. In this case SuperSU v2.46 would be the current version. Anyways, I just googled a bit and that's not the problem at all.
The developers of the game implemented a function which doesn't let the app start on a rooted device. It will check if you have Superuser-rights and automatically close the game at the splash screen if so.
So actually what you need is something that "hides" your root. There are several methods. I heard about Xposed modules like RootCloak for example. I even read on the xda News page that it's Lollipop compatible
Click to expand...
Click to collapse
Thanks for the reply. On the game's forums, I have been told that masking does not work (if you look at xposed rootcloak it says it's not compatible). And some users have been able to get the game to work with certain versions. I am on the latest binaries and it still doesn't work. The only way to get it to work is to unsinstall SuperSU and reflash it every time I want to play.
On some forums I've read that SuperSU has got a function to "hide" or "temporarily disable" it... Take a look at the app. Hopefully this feature hasn't been removed and maybe that's enough for you to get the game working. It's not a perfect solution but at least you don't have to uninstall / reflash every time. Let me know if it worked
Hello all,
I've recently given in to the draconic overlords that demanded no root (i.e. Niantic). I've rolled my phone back to OxyegnOS 2.1.4 (Android 5.1.1). Are there any more recent ROMs, possibly custom ROMs, that do not have root?
Thanks for any help you can offer.
sultans cm13 is specifically unrooted for apps that require no root. theres some xposed modules for things like pokemon go, banking apps, and snapchat if you want to keep root as well.
http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700
You can use Magisk and play your game even if you're rooted. Check this out. You can use it with AutoMagisk, which will automatically unroot on the fly when you open the game!
xymic said:
You can use Magisk and play your game even if you're rooted. Check this out. You can use it with AutoMagisk, which will automatically unroot on the fly when you open the game!
Click to expand...
Click to collapse
Thank you. I was using Magisk on CM13 but that stopped working, PoGo was really intermittent. Then I updated Magisk and phhsuperuser and only after the fact realized that they removed the root toggle feature in the latest version. That's what prompted the move to stock and the question above.
The Jack of Clubs said:
sultans cm13 is specifically unrooted for apps that require no root. theres some xposed modules for things like pokemon go, banking apps, and snapchat if you want to keep root as well.
http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700
Click to expand...
Click to collapse
Thank you for this. I knew there were some around but I just couldn't filter them out from the root-included ROMs.
Need some answers/help...
I was stock, rooted on 8.0....saw a pop-up box yesterday about OTA, didn't think much about since I thought being rooted wouldn't allow the OTA. Have seen the occasional pop-up over maybe the last couple weeks, but I don't normally restart my phone unless it starts to lag or freeze up/run slow. A restart usually fixed that. Was perfectly happy staying on 8.0. I did a shutdown on my phone this evening, and when I restarted it, bam, I'm unrooted on 10 now, specifically, QP1A.190711.020
The phone was bought from Google, unlocked in Oct 2017. I immediately unlocked bootloader and rooted at that time and have been running stock 8.0 since. TWRP and Magisk were used following instructions from the thread here on the forum.
No data was lost after the restart today and 10 seems to be running ok. I did download some data and pictures through my USB-c onto a flashdrive and it did seem to drain my battery FAST while doing it.
What I'd like to know now is how to get root back. I wouldn't mind staying on 10, but if I re-root, will another OTA break my root again? I haven't tried to do a shutdown and a restart again to see what would happen because I'm afraid my phone will brick.
I'm kind of a noob at this, and I don't always understand when you all get technical, but I can follow step-by-step instructions.
First off, how did an OTA actually get through, update and unroot my phone?
And second, can someone point me to step-by-step instructions to re-root my phone on 10, and how do I keep it from happening again?
Thanks for looking and I'd be very appreciative if someone could help me out.
Thank you.
Jim
same here
Same here.
I've got a retail (NON-Verizon) rooted, stock OG Pixel with 8.1 and I've been ignoring the nag to update to 10.
My wife has a retail (NON-Verizon) Pixel 2 that was also stock, rooted 8.1 except she just took the update and asked me about it later.
Both were done with TWRP and Magisk, albeit differing versions.
She's now unrooted at QP1A.191005.007.A1
TWRP v3.2.1-0-walleye is installed.
EDIT: TWRP seems to have been nuked by the OTA upgrade.
I just tried to reboot into TWRP recovery and it's gone.
Magisk Manager app version 5.4.0 (57) + "Latest Magisk Version: v16.0" (I'm pretty sure I rooted via v14.5(1456) though) are present.
"Update Magisk Manager" is nagging about updating /installing MagiskManager-v5.8.2
Root Checker Basic v6.4.6 is also installed.
I'm scared to death to update Magisk or attempt root without some guidance from you fine folks here.
Until then, I'll start having her backup everything she wants to keep in case things go sideways.
I didn't think I was the only one this happened to.
Ok...noticed another issue.
I had Titanium Backup Pro installed. I had several apps frozen before the forced upgrade to 10. Guess what? Those apps are listed as disabled in the app list with no button for re-enabling them. Titanium Backup Pro no longer works because I lost root with the forced update to 10, so I can't unfreeze with Titanium Backup.
Is there any way to unfreeze those apps without re-rooting? Not too sure I even want to attempt to root again.
Also, I haven't shutdown or restarted since the forced update. S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
fjm568 said:
S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
Click to expand...
Click to collapse
Correct.
As for "other issues", none that I, or she, have noticed.
Still breathlessly waiting to hear about how I go about re-rooting without data loss.