Related
this may have been asked, but i'm new to the nexus 7. i rooted it right away, and put TWRP on. probably shouldn't have but i like doing nandroids. i was excited for the OTA and want to just install it since my tab got it, but it won't obviously since i've got a custom recovery (duh i should've thought of that..) and i don't want to go flashing roms yet (i like keeping everything stock right away, it's so smooth)
so my question is, is there a way to go back and flash the stock recovery somehow so i can OTA, then put TWRP back on? i can't find the stock file to fastboot flash or anything
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
kangy said:
You can either download the OTA update manually and flash via TWRP. or do a full 4.2 stock ROM
http://forum.xda-developers.com/showthread.php?t=1989158
Warning: there have been mixed results from the early adopters on the OTA patch. I was running 4.1.2, TWRP, and SuperSU. I lost both SuperSU and TWRP when I upgraded and a handfull of apps are not working right with the new multi user file structure.
The way I did it was
1) Download the OTA zip from the thread I posted above
2) Moved that to SD Card (I moved via Google Drive, you can use USB if you want) I did the whole thing while waiting for a flight without a computer handy
3) Reboot to TWRP Recovery
4) Flash OTA Zip
To get Root and TWRP back I did the following (note, I have SuperSU pro and the survival mode was checked)
1) disabled SuperSU and reenabled which prompted to update Binaries
2) flashed TWRP via ROM Toolbox
Click to expand...
Click to collapse
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Alright try this.
Go to SuperSU settings and and click on Reinstall under Cleanup, it will give you a prompt and tell you it will self close and to re-install from the market. (Mine never fully uninstalled which I assume is due to it being flashed to ROM, I checked under the App manager and it only had a downgrade option so) Anywho. If it did uninstall go ahead and redownload it from the market, if it didn't check the market anyway, the Dev published and update for it to help with 4.2 multi users.
Once you get it reinstalled and/or updated from the market go back to the settings and Toggle off Enable Superuser, close the app, re-open and then re-enable superuser. You probably will want to give it a reboot at this point. (Ive restarted my device a hundred times since going to 4.2 from trying to work through the bugs. Once you restart test a root app. I used Adaway for the test. Important, if the app fails or gives an error about not having root, try again. After I went through all of those motions SuperSU was pretty slow for a while with giving root access, usually the second request from the app wakes it up. Since then though it is back to being snappy with zero lag.
Yes, the reason you can't flash TWRP through ROM Toolbox is that requires root. Once you get your SuperSU working try flashing the latest TWRP again, it should only take a few seconds to flash. Let me know how it goes, I'm subscribed to the thread. I may not be the smartest guy on XDA but you are in the same exact boat I was last night!
jayochs said:
thanks kangy! i also lost both when i flashed.
the reason it didn't work was that i frogot i played with my build.prop and had apps frozen on titanium.
so i disabled and reenabled SuperSU, but no prompt to update.
i'm using rom toolbox now to install but it keeps telling me install failed...basically because it doesn't have root i presume. any ideas?
Click to expand...
Click to collapse
First, determine if you have root or not. Open TiBackup, if it opens correctly and you can see all your apps listed, you have root. Otherwise it will say "Failed to obtain root," and quit.
If you have root, then great. If not, you can flash the SuperSU zip in TWRP/CWM: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
I haven't tried flashing superSU, I've always flashed Superuser zip [google "superuser zip"], and then installed superSU from Play store.
Once you have root..
Go to Settings > Security and check allow installation from non-market apps, and uncheck the security feature that checks all apps for being malicious.
Then try it. If you still cannot restore apps, you might have to install them with adb.
I just updated someone's N7 to 4.2, and as usual I backed up everything in TiBackup.
Then I backed up the TitaniumBackup directory [because I had to do a full factory reset].
I then extracted all the .apk.gz files with gunzip. [in linux OR adb: $ gunzip *.apk.gz -- for windows, I suppose you would have to use 7-Zip].
Then I tried to install with pm:
Code:
for i in *.apk; do pm install $i; done
But every one was giving me an error, INSTALL_FAILED_INVALID_URI, I couldn't figure it out. Found a thread said to chmod 755 /data/local, but that did not fix it.
So what I had to do, was on my linux PC:
Code:
for i in *.apk;
do adb install "$i"
done
So I finally was able to batch install my apk files.
after that I restored all apps data.
Nandroid back ups not possible after 4.2 update
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Yordan5 said:
After updating my rooted N7 to 4.2 OTA I re-rooted using Wug's Nexus Root Toolkit 1.5.5 and realized that Nandroid back ups are failing.
I had no problem creating such back ups while on 4.1.2 and using his Toolkit 1.5.3. I guess the reason may be that the 1.5.5 Toolkit does not have the latest build incorporated.
Click to expand...
Click to collapse
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
mvmacd said:
why are you even using a toolkit? it's a nexus!...
Root by flashing Superuser zip or superSU zip in CWM/TWRP.
Make nandroid backups in CWM/TWRP, and you should have no problem.
Click to expand...
Click to collapse
NRTK 1.5.5 would not flash the 4.2 custom rom I fed it either. Just kept stalling out with errors that it could not find the zip file.
So I booted into TWRP and flashed it with no problem at all.
I also did backup in TWRP and checked everything but saw no mention that is was a Nandroid backup. How can I be sure?
i'm trying to nandroid back to a 4.1.2 nandroid i have, problem is, twrp has different directories for nandroids in 4.2 than 4.1.2...so it can't find the old nandroids and i can't find the 4.2 dir where twrp stores them now. ugh. such a damn headache for an update that it turns out i didn't want lol
Read my post below, I was having the same problem but got back on 4.1.2. You have to use the twrp explorer and relocate the twrp files since 4.2 moved them.
http://forum.xda-developers.com/showthread.php?t=1992552
Nandroid Downgrade from 4.2 to 4.1.2
Sent from my Nexus 7 using Tapatalk 2
There are a few threads that deal with upgrading lollipop to marshmallow, but they seem to raise as many questions as they answer - mainly since they were usually written before rooted images were distributed.
Basically, I am on an unlocked, rooted stock XT1575 with TWRP 2.8.7.0. It sounds like it's less efficient and has lots of potential problems to go back to stock, unroot, install OTA, do new system root, and re-add TWRP.
Instead, it sounds like the simplest method to get to stock rooted MM, with least steps and potential problems, should be this:
Update TWRP to 2.8.7.1 using IMG file here from within TWRP Recovery (TWRP Manager did not install it when I tried via Android proper - I was still at 2.8.7.0)
Do a full TWRP backup of my current Lollipop stock rooted installation (I assume this means I can restore without problems if the MM install goes awry)
*Optional: Use Titanium Backup to backup settings of important apps, and text messages/MMS.
In TWRP, Wipe->Swipe to Factory Reset
Transfer to phone and Flash via TWRP the stock rooted odexed ROM from this thread (not sure if there is a good argument for deodexed? I've never gotten a clear answer why one should be better, but would stick with odexed just because I believe it is "stock" so maybe less problems?)
Install SuperSU 2.62 from this thread by simply flashing it as normal in TWRP 2.8.7.1.
Reinstall all programs on initial setup. [*Optional: Reinstall via Titanium backup]
I assume if I do this I will: have marshmallow; have root; have working TWRP.
Does anyone see any obvious problems with this method? Thanks, I really appreciate any comments.
EDIT: Yes, I tried this method. It all worked, except I've added SuperSU installation steps that worked for me, since the "Stock Rooted" ROM is NOT actually rooted when I flash it. Also, used Titanium Backup successfully for some programs, so added that as an option.
Sorry to bump, but any response from someone with experience would be very helpful. I just want to make sure I don't have to go through the whole unroot/OTA/reinstall TWRP/reinstall root procedure that every thread says seems to cause problems...
Answered my own question - edited the main post to show the method used successfully.
Thank you for this answer thread. I was looking for the simplest answer for upgrading to MM without having to unroot and reflash everything. Looks like this is the easiest for now (I have having to reinstall everything, since some games I play to NOT react nicely to data being restored via titanium).
Have a brand new XT1575 with 5.1.1, Does the MM Update break root ability. I primarily want it for xposed, adaway. No ROMing
Should I update and then root? or root and then update?
I personally have found that following this method breaks root possibilities. MM is rooted, but when I got to the point of installing SuperSU via these steps, it broke EVERYTHING (settings stopped working, Motorola Services stopped working, etc).
I have to start from scratch again now.
I recently got a Galaxy S5 (SM-G900T with LMY47X.G900TUVS1FOJ4).
I grabbed chainfire autoroot and flashed it with the Odin 3.10.6 that came with the CF file. It successfully rooted the phone. I installed Titanium Backup and restored all the stuff I wanted from my old device.
I've been using the device for 1-2 days now and lost root. I opened TB and it says I'm no longer rooted. I confirmed this by downloading a root checker and it also says I'm not rooted.
According to TB, I had BusyBox for root. There was no application icon nor was it in my list of installed applications. When I used chainfire's autoroot on my S4, it installed a super user program that I could open from my app list.
I would really like to continue using Titanium Backup. Does anyone know how I can gain root access again? I already messed it up once by reflashing the autoroot. This caused an infinite bootloop and I eventually got out of it by doing a factory reset. I've returned my S4 to T-Mobile and don't want to soft brick my phone again.
Thanks.
Anyone have any suggestions of how I can reroot my phone?
If you successfully used cf autoroot then that's not the issue.....My money is on a deleted or disabled or un-updated super user app.... this is what will give you (or prevent you from having) root access to your device.
http://i.imgur.com/rVnFwJM.jpg
Using supersu v2.65 works well for me
whynoteel said:
Anyone have any suggestions of how I can reroot my phone?
Click to expand...
Click to collapse
Some days ago I get same problem ( lost root ) because i use supersu v2.67 on cm13 for sg s5 : g900f
therefore, after installed cfroot you can use twrp 3.0.0.0 as custom recovery
Then , Download. & update supersu to v2.65 by using twrp recovery ZIP version
Thanks i'm waiting for a reply
Hi Guys.
As the title suggests root access suddenly disappeared from my nexus 6p yesterday.
DigitalHigh rom 7.0 was flashed through the latest twrp (3.0.2-2) and everything was running fine. I got the notification that the SU binary is out of date from PHH's SuperUser. Opened it but nothing really happened. So I downloaded superSU and suddenly it prompted me that the device isn't rooted. Being unfamiliar with PHH's SU I decided to flash the latest SuperSu through TWRP but the phone wouldn't boot.
Right now it has been restored to a backup taken just before flashing SuperSU which means everything is running fine and even android pay works however there's no root access. Is there something specific that might have caused this?
Are there any ways to re-gain root?
Haven't gone through the process of a clean flash yet as the phone is needed for work however even if all of that is done the SU binary will still need to be updated. Is there a different method for updating PHH's root?
So far I have tried clearing cache etc. but noting worked.
apostol96t said:
Are there any ways to re-gain root?
Click to expand...
Click to collapse
Phhusson's superuser and SuperSU don't mix. If you're back to booted, but not rooted with Phh, you'll need to either flash one of the Nougat boot images from the nexus/angler folder or the latest superuser.zip (I think the latest is r229) from http://superuser.phh.me
I just bought a Moto g5 plus and rooted it, evidently successfully. Every time an app tried to access the system folder, root access was lost. I could not access the system folder myself to fix the problem without losing root.
Magisk did nothing. Every time I tapped it, it showed nothing but ads.
So I switched to Resurrection Remix 5.8.4 2017-09-17. The versions with Oreo did not work on my phone so I got the latest one with Nougat.
The phone app crashes repeatedly. I wiped/reflashed this time leaving the Google dialer out in the GApps install, I cleared cache after cache, turned off battery optimization for Phone and SIM toolkit, nothing helps
The latest problem I've had is that no apps will download files directly to the SD card. I can access it and move files over, but the whole point of purchasing a large SD card is in case something goes wrong (like installing a faulty rom or breaking the phone on a dryer), my files are safe and accessible once the problem is fixed. It also prevents the phone's internal storage filling up.
The phone this replaced is a Moto g4 play, on that phone I ran a stock room, root stuck like gum on a shoe, and the SD card worked properly.
I have already googled fixes for my issues, nothing in the first page of any search worked.
What I need is a way to make keepvid, Firefox, ACR, and any other program that downloads stuff save it to the SD card AND a working dialer on Resurrection Remix, or instructions on how to make root stick on the stock room, or a *reliable* custom ROM recommendation.
shadow460 said:
.....Magisk did nothing. Every time I tapped it, it showed nothing but ads.....
.
Click to expand...
Click to collapse
This sentence makes me attentively.
I use magisk a long time now and I NEVER saw any ads in it because there aren't any. Where did you download the file?
Also I never heard of losing root when accessing system. How do you realize that an app tries to access system? It seems your device isn't properly rooted, maybe because of a wrong magisk installation. Btw, instead of opening a new thread I would post the problem in the Magisk thread:
https://forum.xda-developers.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382/page2721
The only place to download magisk.zip and Magisk Manager is here:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Sent from my Moto G5 Plus using XDA Labs
https://forum.xda-developers.com/showpost.php?p=75114774&postcount=236
This is the guide I used to root the phone. All the files I needed came from the links there. I went through step by step and, once I finished I ran Root Checker to verify root. Next I flashed super su and went about installing apps until I realized root access had been lost. I found out by trying to run Root Explorer. At the time Super SU was handling all root access requests normally.
The next day I wiped and tried again. I tried several ways to retain root access, with and without Super SU. When I clicked Magisk, it prompted me to update it and sent me to the Play Store for something called Magisk Manager. That appears to be the only update available for whatever's in that guide. I installed it, but it's straight up adware.
Root Explorer, ES File Explorer, and any app that attempt to access the phone's root (system?) folders will cause root access to disappear when they try.
So I gave up on the stock ROM, backed up that install to my SD card, wiped the phone's memory, and flashed Resurrection Remix with Oreo. It was the first thing that came up by searching "best custom rooms for Moto g5 plus". The SD card access in that rom is completely broken, making it useless to me. I wiped that one too and installed the ROM listed above. I ran that without really setting up any of my apps... I downloaded them and left them on their stock settings. I installed the Google dialer with the Aroma GApps, and was later shown this would cause the phone app to crash, which it did.
Wipe and reflash AGAIN, this time sans Google dialer. Turn off battery optimization for phone and SIM toolkit. Wipe cache and data for both. Boot to TWRP and wipe cache/dalvik. NO CHANGE, phone app *still* reports it has crashed but will allow a conversation.
I decide I can live with that and start customizing apps. That's when I find out the *only* apps with write access to my SD card are the camera, the stock file browser, and ES File Explorer. Another app, FX explorer, shows write access is enabled on the SD card. Firefox, AdBlock Browser, and keepvid all need access to it. I grabbed Firefox hoping the issue was just that the others were simply too outdated to work with Nougat, but evidently that's not the case.
The camera and ES went through some kind of weird dialog telling me to select the root directory of the SD card before they would write to it. It's almost as if ES is functioning as a skin for the stock file browser and those other programs have no permission for that.
BTW, the forum chucked me an error about my IP address already being used once today when I tried to reply to this the first time. I was steamed already and about to Chuck the phone out in the freeway.
Basically what I need is advice on a custom ROM that, as Microsoft puts it, just works.
In case it matters, the SD card is a 200GB SanDisk model, A1 / V10 rated (the phone can't transfer data to it that fast anyway) and there's a ~2500 mAh Newdery battery case attached. There is no USB OTG in the battery case... just a cheap Chinese battery.
shadow460 said:
https://forum.xda-developers.com/showpost.php?p=75114774&postcount=236
This is the guide I used to root the phone. All the files I needed came from the links there. I went through step by step and, once I finished I ran Root Checker to verify root. Next I flashed super su and went about installing apps until I realized root access had been lost. I found out by trying to run Root Explorer. At the time Super SU was handling all root access requests normally.
The next day I wiped and tried again. I tried several ways to retain root access, with and without Super SU. When I clicked Magisk, it prompted me to update it and sent me to the Play Store for something called Magisk Manager. That appears to be the only update available for whatever's in that guide. I installed it, but it's straight up adware.
Root Explorer, ES File Explorer, and any app that attempt to access the phone's root (system?) folders will cause root access to disappear when they try.
So I gave up on the stock ROM, backed up that install to my SD card, wiped the phone's memory, and flashed Resurrection Remix with Oreo. It was the first thing that came up by searching "best custom rooms for Moto g5 plus". The SD card access in that rom is completely broken, making it useless to me. I wiped that one too and installed the ROM listed above. I ran that without really setting up any of my apps... I downloaded them and left them on their stock settings. I installed the Google dialer with the Aroma GApps, and was later shown this would cause the phone app to crash, which it did.
Wipe and reflash AGAIN, this time sans Google dialer. Turn off battery optimization for phone and SIM toolkit. Wipe cache and data for both. Boot to TWRP and wipe cache/dalvik. NO CHANGE, phone app *still* reports it has crashed but will allow a conversation.
I decide I can live with that and start customizing apps. That's when I find out the *only* apps with write access to my SD card are the camera, the stock file browser, and ES File Explorer. Another app, FX explorer, shows write access is enabled on the SD card. Firefox, AdBlock Browser, and keepvid all need access to it. I grabbed Firefox hoping the issue was just that the others were simply too outdated to work with Nougat, but evidently that's not the case.
The camera and ES went through some kind of weird dialog telling me to select the root directory of the SD card before they would write to it. It's almost as if ES is functioning as a skin for the stock file browser and those other programs have no permission for that.
BTW, the forum chucked me an error about my IP address already being used once today when I tried to reply to this the first time. I was steamed already and about to Chuck the phone out in the freeway.
Basically what I need is advice on a custom ROM that, as Microsoft puts it, just works.
In case it matters, the SD card is a 200GB SanDisk model, A1 / V10 rated (the phone can't transfer data to it that fast anyway) and there's a ~2500 mAh Newdery battery case attached. There is no USB OTG in the battery case... just a cheap Chinese battery.
Click to expand...
Click to collapse
In the rooting thread you mentioned it says "Chose your preferred rooting app, superSU OR magisk".
Never use both.
I recommend to use this guide:
https://forum.xda-developers.com/g5-plus/how-to/how-to-root-moto-g5-plus-t3579659/post74673573
As superSU is abandoned and not supported anymore I recommend magisk.
If you say "when I tap magisk" than it's the magisk manager you're using. Magisk consists of two parts: The magisk.zip for flashing through TWRP and the Magisk Manager which is the interface.
Nor magisk neither Magisk Manager is in the playstore! Only use the files from the thread I mentioned above. The Magisk Manager apk is inside the zip and also downloadable in the magisk thread. Normally the manager is present when you have flashed the magisk.zip. Sometimes it is not, than install it just like any other apk. But don't use any other sources than
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page5
So my advice is flash your actual stock ROM (the one you were on) via fastboot.
Hopefully you made a backup in TWRP because if you don't have a backup of EFS and persist you have a big chance of losing your IMEI/4g/voLTE if you switch from an Oreo custom ROM back to stock.
If you have a backup of EFS save it for your life!
If your IMEI and/or 4g is gone after flashing stock restore EFS and if you have it persist when you have TWRP after the next step.
Flash latest TWRP 3.2.3.1.
Boot into TWRP and flash magisk 16 (it's the most stable one at the moment).
If the Magisk Manager is there don't update it if it prompts you to. If it's not there install the apk found in the magisk 16.zip.
This is it in short form, the rooting guide I posted is more detailed.
I think most of your problems result from the not complete rooting solution.
And one hint: Forget ES, it's a data thief.
Use Solid Explorer, Total Commander or imho the best: MIXplorer. This one is not in the playstore, you find it on XDA:
https://forum.xda-developers.com/showthread.php?t=1523691
Sent from my Moto G5 Plus using XDA Labs
I have two backups: one with the stock rom that was losing root and one with the custom ROM above that I took an hour ago. The phone has had Oreo on it and gone back to Nougat, I think with the stock rom.
I took the first backup when I thought I had everything running stable on the stock rom. Is there a way to unroot it and try again?
Not sure what version TWRP is, whatever was linked to in the root guide.
I'm not sure what EFS refers to and I don't yet know how to flash a room via fastboot. I assume it's similar to installing TWRP.
Ok. TWRP is version 3.2.3-1.
I went into the thread above and downloaded Magisk 17.1, which is claimed to be the most stable release. I downloaded the Magisk uninstaller. Next I booted into recovery mode to restore the stock ROM I had used at first (with my apps loaded on it) and uninstall Magisk 16.7.
The uninstaller refused to "install".
Magisk 16.7 refused to install. (Error 1, failed to install from zip)
Magisk 17.1 refused to install. (Same error)
Super SU installed perfectly, though I didn't load into the OS to play with it.
Now is it sinking in that Magisk is CRAP??
I found the stock ROM over at androidfilehost, matched it to the version I have, and attempted to flash that with TWRP. Another error... this one said invalid zip file format.
I'm back on Resurrection Remix, wondering exactly what else I will find broken in it.
The solution here isn't going to be the stock rom, and I will NEVER attempt Magisk again. It's going to be answering three questions:
1. How do I set global permissions for *every* app on this phone to write to the SD card?
2. How do I keep com.android.phone from crashing?
3. Is there a custom ROM that has these issues addressed?
shadow460 said:
Ok. TWRP is version 3.2.3-1.
I went into the thread above and downloaded Magisk 17.1, which is claimed to be the most stable release. I downloaded the Magisk uninstaller. Next I booted into recovery mode to restore the stock ROM I had used at first (with my apps loaded on it) and uninstall Magisk 16.7.
The uninstaller refused to "install".
Magisk 16.7 refused to install. (Error 1, failed to install from zip)
Magisk 17.1 refused to install. (Same error)
Super SU installed perfectly, though I didn't load into the OS to play with it.
Now is it sinking in that Magisk is CRAP??
I found the stock ROM over at androidfilehost, matched it to the version I have, and attempted to flash that with TWRP. Another error... this one said invalid zip file format.
I'm back on Resurrection Remix, wondering exactly what else I will find broken in it.
The solution here isn't going to be the stock rom, and I will NEVER attempt Magisk again. It's going to be answering three questions:
1. How do I set global permissions for *every* app on this phone to write to the SD card?
2. How do I keep com.android.phone from crashing?
3. Is there a custom ROM that has these issues addressed?
Click to expand...
Click to collapse
Stock ROM has to be unzipped in your Fastboot folder on PC and flashed from there. That's why you've got an invalid zip error message.
If you think magisk is crap you will have problems in the future as superSU is dead.
You should read the instructions for installing magisk and how to use the uninstaller.
You have such a lot of problems that I recommend to do a full wipe and install any Oreo custom ROM you want, they all are stable. AOSP Extended or Pixel Experience are good choices. If you want to root them try superSU 2.82 SR5 (the latest stable) or use magisk 16 (I said before that it's the most stable, not 17.1). Do a full unroot if you change from one rooting method to the other. There's a script called unsu.zip from Osmosis which deletes all traces of every rooting method:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067
If you know what you're doing it's an easy job and magisk is a very cool piece of software if you use it correctly.
Sent from my Moto G5 Plus using XDA Labs
Will look into those when I get home. I patched up the g4 play that got crushed by a clothes dryer (oops) and will run it a few days while I work out the g5 plus.
For full unroot do I need to return to stock recovery or can I keep TWRP?
Does Pixel experience have anything to do with the Pixel launcher?
Last question... if I flash the stock room do I still need to unroot?
I actually patched up the g4 play that got crushed when I was moving a clothes dryer and am running it, so I have some time now to work out any issues with the g5 plus. I'll probably go ahead and try one of those custom rooms with SuperSU. I don't use any apps that require non-root and by the time I need to root something again there will probably be a new Superuser type app out there. If I go with the stock rom, I don't see much of a choice, but I'm not thrilled about Magisk.
Let me get on the download for one of those custom rooms you listed...
I hear bad things about 17.1 for Magisk. Find the Magisk 16.0 and you will be fine. But follow the instructions first.
Also there's a thread somewhere for flashing actual stock Nougat zips according to your version (may it be RETUS or RETEU) if anything has gone horribly wrong as it sounds you have at least a working TWRP. Once you got that going, then reboot into recovery, back it all up.
Then format system, cache, data and dalvik (MUST always be done on clean flash). Then flash desired Oreo rom. Then flash Gapps. Then flash Magisk. Then boot it.
I found the thread on TWRP flashable stock roms and am downloading one now. I also found my credit card statement, which reminded me how much I spent on that electronic curse... and I ought to actually put some software on it and use it. Been running the g4 play (harpia) for a bit as I got a semi decent quality screen to replace the broken ones. Parts are getting harder to find... which is the same reason I retired my last Galaxy. (actually I think that one is just missing the ROM...)
Anyway, I backed up the EFS on the G5 plus using TWRP. I plan to try to TWRP flashable stock rom and give Magisk another shot since I have a working phone I can use while I set the G5 up (I have all the time I need).
I think I understand how to recover the imei if it gets deleted.
Update: TWRP flashable stock room appears to be working. Gonna make a nandroid backup of it, grab the Magisk 16 download on *this* phone and then head off to bed. Will attempt root again later this week.
Thanks ya'll!
Next step was getting Magisk 16 on there with the TWRP flashable stock ROM. That was a simple process. I put Joey krim's Root Checker and Root Explorer on also and ran them both to try and remember create the loss of root problem. Root stuck like duct tape... for now.
I looked through Magisk 16's settings using it's manager. I'm not 100% sure what all of that does so I left them alone.
There were some tweaks in RR I liked such as the battery var and swipe the status bar for brightness. If there's a way to run that kind of thing, I'm all ears.
Going for round 2 with the Moto G5 plus. I haven't had any trouble since September 20 aside from needing a screen replacement (I dropped it).
Wife broker HER screen on a Galaxy J3, so she's getting a G5 plus. It's backing up its stock ROM now. I made a backup of the install on my phone with what I consider essential apps. I'll flash that in but put her efs on it from the new to us G5 plus not mine from my phone.
From there everything should be the same save for the phone number, esn, and SD card, plus whatever she puts on it.
Should be a lot faster than her in rootable AT&T J3.