Related
It wont let me login at all on my rooted XT1575 with TruPureXMM and FranklenClark kernel.
You need to uninstall xposed, login then reflash xposed.
aznflawless said:
You need to uninstall xposed, login then reflash xposed.
Click to expand...
Click to collapse
I tried that with no luck
unnistall xposed via recocery , reboot phone, log in to snapchat then go to recovery and install xposed
Kasyton said:
I tried that with no luck
Click to expand...
Click to collapse
uninstall xposed as in using uninstaller.zip file via recovery. Then log into snapchat, once you login, you can flash xposed again. just be sure to never log out of snapchat, or else you will have to do this process again.
You can install snapchat on a virtual machine or android emulator (like bluestacks, nox), log in, and then use the option for root. Do a backup of the app in Titanium Backup and transfer the backup to your phone. After this, you can uninstall the emulator, but without log off snapchat.
Ugh I just went through this whole process, never have I installed xposed(didn't have a need for it) but when updating to the stock, rooted 6.0.1 ROM I had to use another device for a while, and got kicked off on the pure. It took 2 hours to figure out, even started changing the password. Eventually figured to install xposed via zip, let the app fail a log in, go back into twrp, unistall xposed using zip, reboot and log into snapchat... I could've avoided all of this had I not changed the password and restored data from a backup file but didn't catch onto it in time.
TL;DR: install xposed > try to log in, it'll fail > uninstall xposed using zip > reboot > log into snapchat > make a titanium backup of the snapchat app to keep for the future
Hi guys! I cant log in or make a new acct on Snapchat with my g4 plus rooted on stock N, is there a workaround?
Thanks
You can't make new account with root enabled! Try hide root or Magisk and try creating again
Sent from my Moto G4 Plus using Tapatalk
lexie90 said:
Hi guys! I cant log in or make a new acct on Snapchat with my g4 plus rooted on stock N, is there a workaround?
Thanks
Click to expand...
Click to collapse
Here's a fairly easy way to solve this:
- Unroot your phone
- Install Snapchat and login
- Root
- Install Titanium backup
- Backup Snapchat
- Go to your Internal Storage>Titanium Backup, and copy the gzip files from there to an SDCard or back it up to the cloud.
Now, if you ever flash another custom ROM all you have to do is install Titanium Backup and restore A bit complicated, but it's a 1-time issue and works pretty well.
Oh, and btw, Magisk works fine, so try that instead of SuperSU.
So I can root with magisk instead of super SU? I Tried phh and got stuck on bootlooping!
I Tried unrooting with super SU and didnt work Will try to flash the stock back to do that
1. Flash Magisk from recovery.
2. Install Magisk Manager from the play store.
3. In settings (Magisk Manager), enable Magisk Hide.
4. Go your merry way.
This is what I did. I'm using the likes of Snapchat, Pokémon Go and Mario Run.
And yes, you can log into Snapchat.
baunthiyal said:
1. Flash Magisk from recovery.
2. Install Magisk Manager from the play store.
3. In settings (Magisk Manager), enable Magisk Hide.
4. Go your merry way.
This is what I did. I'm using the likes of Snapchat, Pokémon Go and Mario Run.
And yes, you can log into Snapchat.
Click to expand...
Click to collapse
Didnt work for me, got an error because IM not rooted with magisk SU
negusp said:
Here's a fairly easy way to solve this:
- Unroot your phone
- Install Snapchat and login
- Root
- Install Titanium backup
- Backup Snapchat
- Go to your Internal Storage>Titanium Backup, and copy the gzip files from there to an SDCard or back it up to the cloud.
Now, if you ever flash another custom ROM all you have to do is install Titanium Backup and restore A bit complicated, but it's a 1-time issue and works pretty well.
Oh, and btw, Magisk works fine, so try that instead of SuperSU.
Click to expand...
Click to collapse
thank you! it worked amazingly.
do you have the magisk link throgh? so i can avoid future trouble lol
lexie90 said:
thank you! it worked amazingly.
do you have the magisk link throgh? so i can avoid future trouble lol
Click to expand...
Click to collapse
The latest Magisk zip is here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
You need to flash it in TWRP. I recommend completely unrooting from SuperSU or phh.
Also, stock kernel is incompatible with Magisk. Flash ElementalX or Vegito if you wish to use Magisk.
So, in this order:
-Unroot
-Flash Kernel (EX or Vegito)
-Flash Magisk (will automatically install MagiskSU)
-Wipe ART/dalvik cache
-Boot
-Install Magisk Manager, presto, ur done
Hey everyone,
I`m running LineageOS on my phone and am rooted using SuperSU which seems to work, according to Rootchecker and the feww apps I use, which make use of root privileges.
But I`m not entirely happy with my current situation, since it seems that more and more apps don`t tend to work with my rooted phone. So what are my ways out of this?
Can I easily unroot my phone, while keeping LineageOS?
Is there a working alternative to SuperSU, which would enable me to stay rooted on LineageOS without reflashing the OS and use Banking-Apps?
I`ve heard of Magisk, but I am unsure of how to switch over from my current state and I`am not sure whether or not it would solve my problems
Thanks for any help in advance!!
Magisk
You just have to go to SuperSU, then Full Unroot, then download Magisk 13.3 and flash it from TWRP. After that you should have Magisk Manager, if for some weird reason you don't, install it via apk
Then you just go to the settings, tick MagiskHide, then go back and open the side panel, MagiskHide - select the apps that you want Magisk to hide itself from
So I tried to do what you said.
I did the full unroot in the SuperSu App,
My phone rebooted
I shut it down again and booted into recovery
Tried flashing Magisk
But it failed, apparently due to my Boot image being patched by another program and told me to go with stock image
What do I do now? And will I lose any data by doing so? Thank you so much for any help!
Weird, but you can simply dirty flash LineageOS (the same one that you have now, or an update, doesn't matter) and it should let you install Magisk.
I did what you said and installed a delta update using LineageOS Downloader. Had to manually flash it in TWRP since I had no root permissions anymore. But I was able to install Magisk like a charm! Now I have to questions:
1. How do I update Magisk? Using the app?
2. Do I have to flash it again everytime I'm updating LOS?
Thanks for the great help so far!
And what exactly are those moduls? Should I be messing with them?
If updates come they will appear on the status bar and you can download them, and they'll install with the phone on. after that you have to (not quick) reboot your phone.
and about the modules, seriously? what do you think??
Hey all,
After my rooting experience with marshmallow, I used that with 7.1.1 and have had no issues. MODS: This was my approach to rooting 7.1.1. I apologize in advance for creating this thread if it's not necessary yet since XDA has given me so much help, I'm returning the favor.
NOTE: for those that want to roast me on this thread and/or flame me, don't do it. We are all noobs at one point or another. I have provided no links but have supplied the filename to the best in my capacity.
XDA gang,
After numerous attempts to root nougat, I tried this approach. This was the same approach I took w/ marshmallow.
I used Odin3_v3.12.3
selected 7.1.1 – look for filename j700tuvu3bqi5 NOTE: uncheck auto reboot. I do\did because in my experience, I encountered a boot loop.
after odin processes the flash, I disconnected the usb cable and did a battery pull.
Boot up your phone and let your phone build the recovery. After your phone reboots after the recovery, do a battery pull when the samsung splash screen starts to display itself.
Enter stock recovery and perform a cache, dalvik, and factory reset. Reboot from recovery.
Do a battery pull when the samsung splash screen starts to display itself. Boot back into download mode while holding volume down, home button, and power button. Let go of the buttons when the download mode screen comes up.
Use odin again and click on the AP button – select twrp_3.0.3-1_sm-j700t_23217. I found and downloaded this from XDA. Click start on odin and let odin do it thing. Disconnect the usb cable and do a battery pull.
Enter twrp recovery while holding volume up, home button and power button. Release buttons when twrp comes up.
Here, you will need to flash the latest supersu. I used v2.82-SR5. Also download no-verity-no-encrypt-ashyx.zip (big ups to ashyx for creating this)
Install these 2 files and reboot. NOTE: your phone will reboot twice – no cause for alarm.
After your phone boots up into nougat, go through the setup and reboot your phone.
After doing all of this, I've had zero issues. It may seem arduous but I found it necessary for my goal.
Did you have any issues with unlock screen lag on pin;/pattern?
There are reports and my own experience with this on a 7.0.0 version of otherwise identical process as yours to root. conclusion seems to be the no-verity-no-encrypt patch causes this, and that this patch (or something functionally identical) is integrated into supersu 2.82 versions.
edit - what model phone did you do this one? 7.1.1 not available for the j730g yet, unfortunately.
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
leo31 said:
im on a320y , i got my phone suddenly custom binary blocked by frp lock,
then i reflash 7.0 stock firmware, i forgot how i rooted my device at the first time.
now im done with all the things, already rooted, but now im facing the unlock lag (especially when u are on secure lockscreen ex.pattern, password, etc)
this is very annoying, because there is no problem with unlocking screen when using fingerprint.
Click to expand...
Click to collapse
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
DullPeon said:
caveat emptor, your results may differ drastically from mine, brick device, etc. but I did find a way around this
https://forum.xda-developers.com/apps/supersu/supersu-2-82-nougat-pin-pattern-unlock-t3764305
the issue is removing forced encryption, as far as the pattern unlock lag goes.
i have done this repeatedly on the a520f now and on a j730g/ds as well
Click to expand...
Click to collapse
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
leo31 said:
can i flash the newest su while im still rooted? i mean, i dont want to reflash the whole rom again and again via odin.
and my superuser is from magisk manager. will it crash my system?
Click to expand...
Click to collapse
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
fullofhell said:
U should please educate yourself on what u got going on here..just some advice cuz......
SuperSu is SuperSU, either system wide root or systemless root.
Magisk is magisk, systemless root.
Seems like u rooted your device with SuperSu first, then installed magisk just a heads up SuperSu is obsolete now..and u do not need both. Use one or the other.. No matter, though, I would first make a nandroid backup. Next, I would go into SuperSu and select full system unroot. Next, reboot.go back to your magisk manager,it will say your device is not rooted. download and install through magisk, the magisk16.0 zip. Then it will do it's thing and install magisk and you will be rooted with magisk and have your root manager and magisk module manager. Magisk is like having SuperSu and Xposed all in one. So that's why I say to say goodbye to SuperSu and go all in with magisk. U can learn more that way too.
If u do not want magisk as root, I can't ponder why u wouldn't....just uninstall it. Then download whatever the latest SuperSu zip is. Boot to recovery and flash it. If there is any other updates no that magisk is gone, it will automatically update u with a notification and say yes to update SU binary. That's all.you are prob not getting it cuz magisk is in there too. So, u do not need that mess and remember to always make nandroid backups in twrp before anything where u may screw stuff up. I hope this helps and make sure to find out everything about anything with Android, before u do it.. good luck.
Click to expand...
Click to collapse
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
leo31 said:
this is cool. your answer is helping me a lot. since i forgot how i rooted this device, i think i will remove my magisk manager first.
and i will see if my root is still working or not. if my device still rooted, so i will straightly flash newer SU.
but if it wont work, so i have to flash the newer SU too, right?
Click to expand...
Click to collapse
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
fullofhell said:
Couple things buddy,
If u aren't rooted with magisk, which your magisk manager says rooted with magisk or rooted with SuperSu, uninstall magisk, then flash latest SuperSu zip.make sure to make backups in twrp.that is critical or u will be in bad shape if something goes wrong.and until u are better acquainted with Android , something very well may go wrong. If u are J700T, or J700T1 be sure to always flash the encryption break zip( no verity) which is posted on the ashyx twrp page.after flashing anything.always. there are more instructions under the j700t threads just click on any of our roms.make a nandroid in twrp first, that's a backup.then reboot. if u flashed SuperSu first u are rooted with it . So once uninstall magisk reboot, then u can just see if SuperSu app is functioning properly and shows root access granted on specific apps. Then go to recovery/twrp and flash latest SuperSu then encryption break zip(no verity). If u never did this before, chances are u never formatted after root or installing twrp and have to lose everything. After installing root or twrp u were supposed to go to twrp, wipe, format, "type yes" then flash root and encryption break zip, then reboot and set up phone. U can tell easily if in twrp it doesn't allow u to mount "data" and are unable to make a nandroid. If so don't bother with messing with anything root related till u format your phone, not factory reset, u select format, then type yes. Then flash SuperSu, and the encryption break zip. Once u do that re setup your phone. Then boot back to recovery and make a backup. That will flush magisk manger right out.
Sorry I know that's a lot but please read the j700T T1 threads. First pages of roms explain all this. Figure out if u have made nandroids and can even mount data first. Let me know what that status is. Then I can better help.
If u have done backups and flashed the encryption break zip before then follow above instructions and get rid of magisk or supersu.(this one is easy too, select full unroot) then leave magisk manager alone, go into it and select install magisk, it does it for u. Reboot after each system change. Then u will be rooted with magisk which is the current norm. SuperSu isn't what it once was the Creator retired and it's not anything special. Magisk is the future man. Good luck I hope this helps you.
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
U don't have to flash only SuperSu to have root.magisk also roots your device, way better too
Click to expand...
Click to collapse
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
leo31 said:
i think the lag while unlocking screen is caused by dm-verity.zip file which i flashed straightly after installing twrp.
Click to expand...
Click to collapse
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
fullofhell said:
No, that same dm verity zip has been used since marshmallow and the unlock lag is a nougat bug. All that zip does is disable encryption so u can access data. And thus allow mounting of internal.
Click to expand...
Click to collapse
this is the 2nd time i root my device.
the first time i rooted my a3, i didn't face any lag and never laggy while unlocking screen.
but the problem is i forgot how i rooted it. which files did i flashed. which tutorial did i follow.
but no problem so far , because the fingerprint unlock does not give any lag.
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.