Related
Hi all,
Not even sure I'm in the right place, still I'd like to share my own experience after upgrading to Oreo last few days. So moderators, if you guys find this irrelevant, or it is in the wrong place, please help me move it accordingly.
I am using XZ F8332. Last few days I decided to say hello to Oreo after some time being patient with the pretty annoying "Upgrade your system" notification. I finally managed to have a fully working Oreo + DRMfix + Magisk + SafetyNet passed and root. Unfortunately good things usually come with bad things too...
At first, I was trying to patch my boot image using ta_poc method. Believe me ta_poc seems to be working on Oreo too, I got all the DRM functionalities working thanks to munjeni & serajr. However, it doesn't seem to be working with both Magisk and SuperSU. I tried all recent versions of those two e.g. Magisk v14, Magisk v14.5 beta, SuperSU v2.79 SR3, SuperSU v2.82 SR5, etc... ALL cause bootloops! I had to come to a conclusion that any methods that patch your modified (with ta_poc) boot image will cause bootloops. There's one thing I didn't try: SuperSU system mode which installs to /system. What's the point of system-less then? But it's up to you to try this.
The above means you are most likely gonna lose root if you go with ta_poc on Oreo. So I had to give ta_poc up and go with DRMfix instead. I got into a few troubles then.
I was initially trying to keep my userdata intact, so I didn't do a full wipe, I actually wiped everything except only my userdata (including data in sdcard). DRMfix didn't fix at all. All I got was only "FIDO_KEYS: Provisioned", the rest was "general error!" and of course DRM functionalities didn't work. I did some search, followed some guides saying about removing these directories: /data/credmgr, /data/drm and /data/mediadrm. There's even a script named "SafetyNet-Cleaning-Tools" also does exactly the same. Perhaps I wasn't that lucky enough. It just didn't work. Until I had to pull all of my data out, do a FULL WIPE including userdata, DRMfix worked then.
Next thing is to get Magisk (or SuperSU) working to have root. I knew recent update of SuperSU causes Xperia devices into bootloops. I also used Magisk on Nougat too. Why not now? So I flashed Magisk v14. Uh oh... I met my old dear friend again, Mr. Bootloops. So Magisk v14 doesn't work on Oreo. But v14.5 beta does. That's how I got it fully working.
Then I pushed my data back to sdcard (including a nandroid of course), did a restore DATA ONLY in TWRP and manually delete the folders mentioned above. After phone started, everything went back. I smiled.
Some existing Magisk modules started to work without any problems. But some other they need busybox. Without any thoughts, I immediately installed osm0sis' busybox installer, the one on Magisk repo. Weirdly it said "Magisk is not activated". I tried other modules, same issue. So only existing modules work, I couldn't install any new modules using Magisk Manager. "Use TWRP then" I thought. I went to TWRP and flashed the busybox installer. My old dear friend came and said "Hi! Bootloops!!" to me again. This time I used Magisk uninstaller to clear magisk files and re-flashed it again. I was able to get back in. I tried YashdSaraf's busybox universal installer. Same issue. Maybe I haven't tested well enough or maybe I went completely wrong way, but looks like busybox isn't working on Oreo? Also, I'm not sure this is the right way to do it, or we have to "clean install" Magisk too? Like uninstall everything first and re-install module by module all over again?
Also, after some Magisk uninstalls and reflashs, suddenly my DRMfix was no longer working. It displayed "general error!" in Service tests -> Security. I tried to fastboot the modified boot image again. Not working. There's no way to get it back except a FULL WIPE. I didn't get it. System-less approach is supposed to have nothing to do with our files. Somehow it does leave some traces, which we need a FULL WIPE to get rid of it? Maybe it isn't just the 3 folders mentioned above, there's maybe more?
Additionally, on Oreo I got some other bad stuffs:
- Adaptive brightness keeps adjusting, going darker and brighter very very quickly. It's no doubt an Oreo's bug.
- Cannot open Titanium Backup. It crashes right after you open it. I tried v8.0 and v8.1. Same issue. Maybe it's because busybox isn't installed?
- I have a feeling battery drains issue comes back. Looks like its consuming more battery than latest Nougat I'm not sure. Haven't got time to do some stats yet.
Last but not least. When I was pulling / pushing data to / from, I noticed that the storage space somehow changed! My phone is 64gb but the second time I got it fully working, it said "storage is 80% full..." and when I opened Settings -> Storage it showed only 21gb! What I did to get it fixed was to run fastboot format userdata. Then I let the phone start normally (without old data), after finishing setup, I turned off and went to TWRP to restore DATA ONLY. Problem solved. I got my storage back. But I have never figured out why. Maybe something wrong with adb pull / push in recovery?
If you've read down this far, I hope my experience could somehow help you avoid encountering the problems that I did.
Me personally I think I will go back to Nougat and stay low for a while. You understand why. Another reason is I also wanna try the "official" xposed for nougat for a little more. rovo89 is freaking awesome. man, he's a legend.
References:
I used this tool to patch my boot image (kernel). This tool origins by tobias.waldvogel but I used the "unofficial" one here and here modified by serajr for the ta_poc method. Thank you guys for this amazing tool.
Magisk latest versions here
SuperSU v2.82 SR5, v2.79 SR3
SuperSU System Mode v2.82 SR5 here
osm0sis' Busybox installer here
YashdSaraf's Busybox universal installer here
Special thanks to serajr, juanpirulo, munjeni, rovo89 and tobias.waldvogel for your amazing works & supports. I dont tag you guys here coz I dont wanna bother you guys
Been there... I feel like that phone don't want to work with poc and Magisk...
FakeMobile said:
Been there... I feel like that phone don't want to work with poc and Magisk...
Click to expand...
Click to collapse
ta poc needs to be rebuild, but munjeni probably dont wanna work in his tool anymore. But serajr´s tool works well so you can root xz oreo with magisk. cheers
Yeah it what I have atm, but I still can't mirror cast to my tv because it not real drm keys
Hi guys, just some hours ago i got into a problem (at least for me).
I switched today from LineageOs 14.1 to AospExtended Oreo and since i can't use LineageOs root and i don't trust SuperSu anymore (because CodingCode), the only root available for me is Magisk.
Now i have flashed Magisk and set up some modules and the root itself is working, but i cannot delete system apps and modify /system in general. I haven't faced this problem in LineageOs (also with magisk).
And yes, i have tried "reboot disemmcwp" and it didn't work.
I am on A2017G, TWRP 3.2.1.7 (Nfound's build).
Thanks in advance for the answers.
EDIT: I FOUND A SOLUTION (KIND OF)
The situation, however turned out a bit different. At first i thought it was magisk messing with zte's system write protection, but it turned out that the culprit was actually SdMaid. Yep. It has a bug, so when you install a module that REPLACES a system app, like Vanced Youtube, it cannot recognize all the links and tricks that Magisk does and screws up everything, showing /system as read only and if you try to uninstall any system app with its inbuilt app manager, it makes Android crash.
There are 2 possible causes:
1. Magisk
2. You're on the B35 bootstack
I had your issue with Magisk before. Personally, I still think SuperSU can be trusted. But if you're willing to try it again, you should know that it will cause a bootloop with Oreo. It's because of the dtb patching. But I figured out how to make it work anyway. Download the SuperSU 2.72 SR5 zip. Unzip the file into a folder. Then open /meta-inf/com/google/android/update-binary in a text editor. Search for all instances of dtb, and change true to false. Save the file, and create a new zip. Then get the Aroma SuperSU Config zip. In TWRP, flash the config zip first. Select sbin mode on the first page, on 2nd and 3rd pages just use default options or whatever you want. Then flash your modded SuperSU zip. You should be able to boot. All works fine for me.
The 2nd possibility is that you are using the B35 bootstack. There is an issue with it where root appears to work but system partition can't be changed no matter what you do. You need to find a B32 bootstack zip and flash that instead.
I personally am using AOSP Extended Oreo, with B32 bootstack and SuperSU, all is fine so far. I can modify system partition too. If you need more clarification then just ask.
Good luck!
I've used the "disemmcwp" option in nfounds twrp options and it worked for me.
AnonVendetta said:
There are 2 possible causes:
1. Magisk
2. You're on the B35 bootstack
Click to expand...
Click to collapse
Wow, thanks for the fast answer!
I am currently using the B32 bootstack (also from Nfound), so the culprit must be Magisk (unfortunately).
I think i will try your method in the next days, meanwhile i will post this in the Magisk thread, maybe they have some clues about this.
Sent from my ZTE Axon 7 using XDA Labs
Modded SuperSU zip is attached.....
Modded B32 bootstack:
https://forum.xda-developers.com/attachment.php?attachmentid=4427264&d=1519249436
Aroma SuperSU config:
http://download.chainfire.eu/1121/SuperSU/AROMA-SuperSUConfig-v1.00.zip
Magisk uninstaller:
http://tiny.cc/latestuninstaller
Flash Magisk uninstaller, B32 bootstack, Aroma SuperSU config, then modded SuperSU, in that order. Go to /system/xbin and delete the su file, it will interfere with SuperSU. Wipe cache/dalvik cache and reboot. And run the "reboot disemmcwp" (as root, or with ADB), for good measure. You should be able to modify /system now.
Thanks, really.
Sent from my ZTE Axon 7 using XDA Labs
Ok, i did exactly what you said, but i ended up with a bootloop :/
But after dirty flashing my rom and Magisk and reboot disemmcwp in twrp, guess what? I got complete access to /system. That's wizardry my friend.
wannaskoo said:
Ok, i did exactly what you said, but i ended up with a bootloop :/
But after dirty flashing my rom and Magisk and reboot disemmcwp in twrp, guess what? I got complete access to /system.
Click to expand...
Click to collapse
Just for the sake of knowledge i should report that, after many tries, i discovered something interesting (at least for me). Magisk IS actually messing with system write protection, but only if you have any modules enabled. I have Ainur Sauron, Deep_buffer remover, Dolby Atmos for Oreo, AudioModLib, Youtube Vanced and Syspatch as Magisk modules, and i can't touch system in any way after booting into AEX, but if i enable Magisk Core mode and reboot i get complete access to /system.
I hope this thread will be useful for someone having problems with Magisk, because it is a great tool for modding and rooting, but i do really care to have /system access, that's the point of custom roms (for me).
Sent from my ZTE Axon 7 using XDA Labs
wannaskoo said:
Just for the sake of knowledge i should report that, after many tries, i discovered something interesting (at least for me). Magisk IS actually messing with system write protection, but only if you have any modules enabled. I have Ainur Sauron, Deep_buffer remover, Dolby Atmos for Oreo, AudioModLib, Youtube Vanced and Syspatch as Magisk modules, and i can't touch system in any way after booting into AEX, but if i enable Magisk Core mode and reboot i get complete access to /system.
I hope this thread will be useful for someone having problems with Magisk, because it is a great tool for modding and rooting, but i do really care to have /system access, that's the point of custom roms (for me).
Sent from my ZTE Axon 7 using XDA Labs
Click to expand...
Click to collapse
Thanks. I would recommend you report this on the Magisk Thread
Yep, i will do that.
Sent from my ZTE Axon 7 using XDA Labs
I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
INSTALLATION
1.back up your system, data and boot partition. If the process fails restoring those will revert the changes.
2.Download and flash Magisk 15.3 (later versions didn't work for me, phone wouldn't boot at all) through twrp.
3.Flash the latest f2fs loop back work around.
4. Flash magisk manager for recovery (mm-2018.8.1.zip attached below)
5.Boot your phone
UPDATING TO MAGISK 16.0
Once the phone has booted:
1.install magisk manager 5.8.3 (attached below)
2.Open magisk manager
3.if any update is available for magisk manager, install it.
4.click on the button that tells you to update magisk to latest version.
IMPORTANT:
5. Select the direct installation method. Flashing the update through recovery will render the phone unable to boot again.
That's it, thanks.
=======
Downloads:
Magisk 15.3
f2fs-loopback-bug-workaround-2018.8.1.zip
mm-2018.8.1.zip
Magisk Manager v5.8.3.apk
freeZbies said:
I followed many guides out there and none worked, phone would always bootloop or freeze at Motorola's logo.
Now I've found a way to do it.
You can use the files attached below.
....snip
Click to expand...
Click to collapse
Interesting.
For what is the magisk manager for recovery needed?
Wolfcity said:
Interesting.
For what is the magisk manager for recovery needed?
Click to expand...
Click to collapse
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
EDIT: Mm for recovery is actually a module that allows you to list and Uninstall modules from Twrp in case your phone no longer boots after flashing a module.
and you're correct, magisk 15.3 does include magisk manager and will install it. the problem I had is that I flashed magisk 15.3 over a system where either the boot.img was already patched, and I experienced that magisk manager sometimes wont be installed in these cases
Sent from my Moto G (5) using Tapatalk
freeZbies said:
Magisk 15.3 doesn't come with magisk manager, so you either have to flash it from recovery or install the provided apk directly.
Click to expand...
Click to collapse
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.
nicolap8 said:
This is not true. The (original) Magisk 15.3 has inside the MM and will install it.
Click to expand...
Click to collapse
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.
freeZbies said:
Well, I may be not well informed then, but upon flashing magisk 15.3, magisk manager did not show up in my device.
Click to expand...
Click to collapse
At least it's inside the official 15.3. But I remember that MM was often not installed in earlier builds.
Sent from my Moto G5 Plus using XDA Labs
I Got Another Method Also
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy
Sonisudhanshu said:
1. I Flashed oreo soak.
2. booted it up and set my moto g5 .
3. went to boot loader and flashed (64bit) TWRP .... (i know that this is a 32 bit rom)
4. Backed up EFS.
5. Didnt boot it and went to bootloader again
6. flashed 32 bit recovery .
7. Flashed No-verify-opt-6.0
8. Booted . ( it was working.)
9. installed latest magics manager.
10. downloaded latest magicx.zip
11 booted to twrp
12 flashed magics16(1600)
13. Booted and it started working like charm. (Had some problems with safetynetcheck)
14. Pls Dont Point Your Fingers At Me If Your Device Stops Booting.
15 . Most important ...... Enjoy
Click to expand...
Click to collapse
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Sent from my Moto G (5) using Tapatalk
freeZbies said:
As far as I know official twrp doesn't backup any of those. I'm on 3.2.3.0 official and it doesnt offer an option to backup neither efs nor persist.
Click to expand...
Click to collapse
I'm on 3.2.2.0 and it offers the ability to backup EFS, 3.2.1.0 also.
As said, for persist there are several unofficial builds but you can back it up with those commands in TWRP terminal:
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
for backup and
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
for restore.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
One question, why do you flash a 64bit recovery in-between? You can backup efs with official TWRP too, just persist needs a special unofficial build (or you can do it by dd command).
Are you sure that no-verity.zip is needed?
That job should be done by magisk.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
1. Because I didn't have any option to backup efs in twrp.32.bit
2. I was not sure but I just flashed it so that no problem occurs like booting issue..
Hope this helps
Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming..... If this helped , i would be gladed
Do the magisk modules work ?
llucas_br said:
Do the magisk modules work ?
Click to expand...
Click to collapse
Which magisk module?
Sent from my Moto G5 Plus using XDA Labs
TWRP flashable Oreo 8.1 OTA updates
Sonisudhanshu said:
Guys pls keep one thing in mind.
Rooting causes some issue.
If you are installing soak 8.1 , then this post is for you.
First of all , there is no fully independent rom for soak test , i mean that its an ota , so rooting this rom will prevent you from upgrading via ota, so you will have to go to 7.0 then 8.1 then any further ota, which is time comsuming.....
Click to expand...
Click to collapse
There are already TWRP flashable Oreo 8.1 OTA updates available.
https://forum.xda-developers.com/g5/development/twrp-flashable-soak-test-oreo-t3827913
thanks
Chekm8Qc said:
I just installed magisk 17.1 and it worked right away. Even safety net passes.
Click to expand...
Click to collapse
Chekm8Qc confirmed here https://forum.xda-developers.com/showpost.php?p=77906610&postcount=56 that he could directly install the latest Magisk version (currently 17.1) on Oreo 8.1 OPP28.85-16 eliminating the need to install an older version first as recommended in this thread.
I can also confirm, installed straight away 17.1 and worked flawlessly, no bootloop and safety net passed.
Please Update!
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080
G5-User7080 said:
Using the currently newest version which is Magisk18.0.zip (flashed in twrp64bit) Magisk Manager showed up in my device app list, then installed the currently newest apk, which is MagiskManager-v6.1. After that i had root. I only flashed f2fs after magisk, no mm_for_recovery.
Quick question: what exactly is that f2fs bug which that file should fix? Because after i installed twrp i had to factory reset or format data that i was able to flash things (there were red lines while trying to flash, telling me that data is encrypted or so and i have to forma data). But even though i did and tried then your versions & mm_for_recovery (which didnt work at all, no root) when i wanted to restore the boot & system image i made earlier as you said there was that text again, telling me i need to format data,.. did that, restored, flashed new versions and it worked, but im afraid that i need to format dat now everytime i want to flash something ?!
Greetings 7080
Click to expand...
Click to collapse
in oreo stock you dont need f2fs bug module, because is working without it
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.
HT10 Stock ROM with Majisk, Xposed, and Busybox
ROM Version: HT10 6.0-V01-20170622
The System, Boot, Recovery, and assorted app files for the working setup are zipped as a Titanium backup and needs to be installed from recovery within the Titanium app; available as freeware on the Play Store. The file is packaged as a zip for upload, but will need to be unzipped and placed in the root of your Internal SD directory so that Tianium Backup can recognise it and restore to your device. I have included the individual files that were involved, in case anyone feels like starting from scratch. They include the Homtom HT10 ROM, The MediaTek SP_Flash_Tool_v5.1552_Win (whith which to flash your ROM, TitaniumBackup.zip (which you will simply flash to a non-rooted Stock HT10 ROM from the app on the running device), the Systemless Magisk v. 19.0, Magisk Manager v7.1.1 and the Xposed_Framework_(SDK_23)-89.3_(Systemless) by topjohnwu and his intrepid team of devs, and the TWRP 3.0.3 recovery by Mebhius which has proved so very useful.
Stock ROM installed with Majisk. The ROM is rooted, the root is systemless (Thanks to Majisk),additional modules within Majisk include a systemless Xposed Module. Gravitybox added within Xposed. Busybox added as an additional Majisck module. I have included screenshots of the Majisk status screen, Pokemon Go working on an unsigned and otherwise rooted ROM, and of course, the settings About Phone page. My contribution is by no means revolutionary in anyway, but the results are tested and working. Hopefully, until more work can be done in Lineage, this ROM will allow you to have more freedom and flexibility with the stock ROM.
Long and sort of it: I flashed a clean ROM (making sure to flash the TWRP recovery instead of stock, reboot to System, reboot, then, to recovery. Flash Majisk 9.0, Reboot back into recovery flash the systemless Xposed framework, reboot to system, verify install, flash selected downloads, Install the Xposed Installer apk and the Magisk Manager.apk, reboot. Once root is established, it is verified to be systemless, a root exploerer needs to be installed so you can locate the installed bits of TWRP, Mgisk, and Xposed in System/Bin and Xbin, as well as the Internal SD and either rename or move them discretely away from the prying eyes of apps that will try to verify your root and block you. Then test, test, test, and test some more.
I have found that once verything is installed, verified, and cleaned, you can simply Magisk Hide Magisk for Play Services, Play Store, Google Services Framework, and the desired (Play Store app) like PokemonGo. Then, set Magisk to Core Only Mode in settings, Make sure that Magisk hide is selected, Systemless Hosts are selected, Clear the repo cache, clear data for the deired app, in this case PokemonGo, reboot and have at it. Expect some hung boots in the process. Pull the battery and keep at it. Dont be afraid to master reset or reflash and start from scratch. And dear Lord, dont start importing personal data in bulk until you feel youve reached a stable system build and made the appropriate backups.
Or you can simply restore the files I've provided, reboot, and start your testing there. The choice is yours.
I have made similar inroads with the Lineage 13 ROM for HT10, ported by Nukeer9578 with limited success. There is still much work to be done. I would say, however, that Nukeer9578 got me started with working on the HT10 and I'm grateful for the challenge.
If you are new to this sort of thing, I would advise consulting XDA developers, Google web, and Youtube for further instructions; it is all spelled out if you have the time and patience.
※Please make a backup of your device before installing or updating ROM
XDA:DevDB Information
HT10 Stock ROM with Majisk, Xposed, and Busybox, Tool/Utility for all devices (see above for details)
Contributors
mven45
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-03-30
Created 2019-04-02
Last Updated 2019-04-19
Thread closed https://forum.xda-developers.com/android/software/homtom-ht10-stock-rom-mod-root-root-hide-t3917395