yes, stock is a ROM. based on a few past handsets, the customized / debloated stock ROM is the way to go. i'm by no means an expert, but not finding a thread for it, decided to make one. if you found your way here, you're welcome to discuss issues you're facing, whether it be magisk, xposed, debloat, whatnot. needless to say i'm just a punter, not the dev.
mine is NPP25.137-15 cedric, but i assume most of the issues arising are the same across the stock builds.
NPP25.137-33 is downloadable here.
https://mega.nz/#!jcp0UCiS!1EXQUYdNftgRrHsdBvmsmn4e_IZy3GtytOaoET9Kjm0
disclaimer: anything you do is between you and your gadget.
XDA:DevDB Information
[ROM][semiOFFICIAL][7.0] rooted stock [magisk], ROM for the Moto G5
Contributors
zdoe
ROM OS Version: 7.x Nougat
Based On: stock
Version Information
Status: Stable
Stable Release Date: 2017-01-01
Created 2017-12-18
Last Updated 2017-12-19
anyone got xposed working on this?
for me, xposed-v88.2-sdk24-arm.zip installs ok, but the modules don't see it. what i need most is the appopsxposed module.
Download link? Features?...
Fedray said:
Download link? Features?...
Click to expand...
Click to collapse
The link Is there
It's only a stock ROM without junk apps and pre-rooted
this thread is not a true DEV-thread - but one to disuss issues in using stock ROM
peter9811 said:
The link Is there.
It's only a stock ROM without junk apps and pre-rooted
Click to expand...
Click to collapse
this thread is not a true DEV-thread - but one to discuss issues in using stock ROM. there's a download link to one version of it. haven't tried to install it though, but there's guides on the net if you want/need to do so.
however, the link's ROM is from motorola, it's not debloated, and rooting is a separate matter - guides are again foundable for that.
thanks for this, but we already have a thread with stock rom, how to install it and root is there...so the firmware from your link is the stock firmware, not rooted or something. I think this thread is useless
look here
Can i flash it with TWRP?
Cricamju said:
Can i flash it with TWRP?
Click to expand...
Click to collapse
i believe you can't flash with TWRP - but using ADB and a handful of different command lines.
this thread may give you pointers.
i don't think anyone has made a flashable zip (yet).
good
@showlyshah, could we have a conversation here about upgrading magisk to latest. i'd sent you a PM, but the msg thread would help others as well...
How to install this ROM?
I'm noob.
Thx
zdoe said:
@showlyshah, could we have a conversation here about upgrading magisk to latest. i'd sent you a PM, but the msg thread would help others as well...
Click to expand...
Click to collapse
ok - i bit the bullet and upgraded magisk to 15.2 and the latest magisk manager.
root is ok, but various applications say that busybox is not installed - and stericsson's doesn't install. however, it seems that apps requiring busybox are still working. @showlyshah is your busybox ok?
lcosta2 said:
How to install this ROM?
I'm noob.
Thx
Click to expand...
Click to collapse
RTFF for a link to installation instructions. but likely you already have stock - that's what you got when you bought your phone.
zdoe said:
ok - i bit the bullet and upgraded magisk to 15.2 and the latest magisk manager.
root is ok, but various applications say that busybox is not installed - and stericsson's doesn't install. however, it seems that apps requiring busybox are still working. @showlyshah is your busybox ok?
Click to expand...
Click to collapse
No.. since magisk module for busy box wont install.. i did install it via busybox installer.
---------- Post added at 08:03 PM ---------- Previous post was at 08:02 PM ----------
showlyshah said:
No.. since magisk module for busy box wont install.. i did install it via busybox installer.
Click to expand...
Click to collapse
And i got working busy box. If you find problems with magisk installer app.. install with twrp installer. Btw. It didn't trip safety net..
showlyshah said:
No.. since magisk module for busy box wont install.. i did install it via busybox installer.
And i got working busy box. If you find problems with magisk installer app, install with twrp installer. Btw. It didn't trip safety net..
Click to expand...
Click to collapse
i'm now on 15.3 magisk & 5.5.5 magisk manager. for me, it installs seemingly OK using the magisk-busybox installer script, both from the magisk manager & from recovery. stericsson busybox installer fails to install.
but the end result is the same, terminal reports "busybox: not found" and TWRP manager that it's not installed.
but there's a busybox folder at /sbin/.core/busybox - and apps needing it seem to work.
zdoe said:
i'm now on 15.3 magisk & 5.5.5 magisk manager. for me, it installs seemingly OK using the magisk-busybox installer script, both from the magisk manager & from recovery. stericsson busybox installer fails to install.
but the end result is the same, terminal reports "busybox: not found" and TWRP manager that it's not installed.
but there's a busybox folder at /sbin/.core/busybox - and apps needing it seem to work.
Click to expand...
Click to collapse
If apps cant find it.. it is not symlinked.. busybox is a swis army knife.. that means.. it is capable of doing most of the fuctions of various modules by its own.. normally.. apps need to use these modules ( binaries ) for doing things.. for example.. if there is a zip application.. it uses the "zip " binary to work out.. dns.. etc are some another modules..
In case of busy box.. most of these binaries are coded into that single busybox binary.. and its much less heavy on system.. and thats why some developers use it for different functions rather than using several individual binaries to accomplish the same..
The benifit is.. you only need to load a single binary .. but if individual binaries are called. Then all of these binaries will have to load and unload.
So... In a busybox installer.. there is a script that points to busy box binary.. from its normal individual binary. Its called symlink. I mean.. if you properly symlink a busybox .. and then if an app calles for a binary.. eg.. zip binary.. the system will point that call to busybox binary and not zip binary.
Also busy box binary is more reliable as it gets upadtes more frequently than normal binaries.. its bit more stable and low on hardware resources usage.
So.. what i am saying is.. even if busybox binary is installed on system.. but if it is not properly symlinked.. the apps cant find it out..
That is the problem.. thats why i said.. find the latest twrp flashable busybox.. busybox installer cant install busybox in magisk installed system. Simply because magisk use its own binary folder and not normal xbin or bin folder.
In twrp.. the installer just install busybox into xbin and symlink it properly.. so its the only working way for f2fs error phones like moto g5 and others ( where magisk module wont work)
showlyshah said:
If apps cant find it.. it is not symlinked.. busybox is a swis army knife.. that means.. it is capable of doing most of the fuctions of various modules by its own.. normally.. apps need to use these modules ( binaries ) for doing things.. for example.. if there is a zip application.. it uses the "zip " binary to work out.. dns.. etc are some another modules. ... In twrp.. the installer just install busybox into xbin and symlink it properly.. so its the only working way for f2fs error phones like moto g5 and others ( where magisk module wont work)
Click to expand...
Click to collapse
thanks for the busybox explanation, illuminating, even if i kinda knew - have seen/used it on various linux-based boxes before (mostly routers). but yes, i'm still a noob.
as i stated at https://forum.xda-developers.com/apps/magisk/module-magic-folder-binder-t3621814/page85#post75191777
, the @VR25 magic fmount now installed for me (the f2fs-loopback-bug-workaround-2018.1.1-NOMOUNT version). as did the magisk module busybox installer. so i assume i'm now good, and wonder why your situation is different.
i'm kinda psyched - if magic fmount works, the ROM is finally ready for prime time / actual use. thanks google for making it this hard.
zdoe said:
thanks for the busybox explanation, illuminating, even if i kinda knew - have seen/used it on various linux-based boxes before (mostly routers). but yes, i'm still a noob.
as i stated at https://forum.xda-developers.com/apps/magisk/module-magic-folder-binder-t3621814/page85#post75191777
, the @VR25 magic fmount now installed for me (the f2fs-loopback-bug-workaround-2018.1.1-NOMOUNT version). as did the magisk module busybox installer. so i assume i'm now good, and wonder why your situation is different.
i'm kinda psyched - if magic fmount works, the ROM is finally ready for prime time / actual use. thanks google for making it this hard.
Click to expand...
Click to collapse
Oh.. hahah.. its not actually google.. its moto.. they choose f2fs ( that too with out full permissions for third party apps) when i dig into it.. i found that the stock kernel wont allow magisk to mount image.
So only ways are..
1) use a third party kernel with proper f2fs patches
2) patch stock kernel with f2fs patches
3) use a different mount partion for magisk. ( Thats what done with the f2fs fix magisk module)
I tried it. Unfortunately. It wont stick after reboot on my stock os.
Btw.. u said u play with routers.. can you tell me a way to access ( with root permissions) on huawei e5577 pocket modem.. mine was locked to some carrier, unlock will never work, so i mixmatched firmware files.. and now its working .. but i have a problem with wifi .. the modem wont connect two devices in 2.4 ghz band.. but it works perfectly on 5ghz band... So i like to dig into its firmware. And check more
showlyshah said:
Oh.. hahah.. its not actually google.. its moto.. they choose f2fs ( that too with out full permissions for third party apps) when i dig into it.. i found that the stock kernel wont allow magisk to mount image.
So only ways are:
1) use a third party kernel with proper f2fs patches
2) patch stock kernel with f2fs patches
3) use a different mount partion for magisk. ( Thats what done with the f2fs fix magisk module)
I tried it. Unfortunately. It wont stick after reboot on my stock os.
Btw.. u said u play with routers.. can you tell me a way to access ( with root permissions) on huawei e5577 pocket modem.. mine was locked to some carrier, unlock will never work, so i mixmatched firmware files.
Click to expand...
Click to collapse
well, moto f'd up on f2fs, but google made the fundamental user-hostile decision to write data onto a hard-to-access partition, not give the user the choice. there could be a per-app menu like for notifications: store data on extSD / intSD.
good rundown on the f2fs bug. but my phone seems to have accepted the @VR25 workaround. (still testing magic fbind). at least the module(s) survive boots. go figure.
routers - don't know enough to help you. much like android - each box has a different set of problems based on hardware / firmware combo. i only buy routers that are known to behave well with opensource firmware.
debloating - anyone? what can we remove from stock ROM?
here is a list that i got from some other moto ROM's thread, assume ours would be (about) the same:
/system/app/3c_main
/system/app/Bug2GoStub
/system/app/com.motorola.android.nativedropboxagent
/system/app/MotGeoFenceSvc
/system/app/MotoSignatureApp
/system/etc/bug2go
/system/framework/com.motorola.android.dropboxhelper.jar
/system/priv-app/3c_checkin
/system/priv-app/3c_devicemanagement
/system/priv-app/3c_notification
/system/priv-app/3c_ota
/system/priv-app/IncrementalUpdates
but i'm sure you can take out more... anyone play with this?
there's a debloater as one of the magisk-modules:
https://forum.xda-developers.com/apps/magisk/module-terminal-debloater-debloat-t3584163
but it doesn't run at least for me - first some permission issue, then "module not found." besides, it only provides an UI for removing apps, it doesn't have any opinion on what to take out.
EDIT: version 8 of the debloater does work. 8.2 doesn't.
Related
I was wondering if anyone has installed Viper4Android on this device. I had it on my previous phone and it worked flawlessly; all my music sounded amazing.
But ever since we achieved root, I couldn't successfully install it. It keeps telling me Busybox is broken or not installed, and therefore won't let me install the audio drivers.
Can anyone try installing it, if they can? My favorite band just released a new album and I'd love to hear it with a good equalizer.
Sent from my MT2L03 using XDA Free mobile app
I have just installed it successfully and it works perfectly on MT2-L05 4.4.2
I have busybox ( stericson ) installed on my phone. Maybe you can delete whatever version of busybox that you have installed and try to install stericson Busybox from playstore?
Good Luck !
4L0M said:
I have just installed it successfully and it works perfectly on MT2-L05 4.4.2
I have busybox ( stericson ) installed on my phone. Maybe you can delete whatever version of busybox that you have installed and try to install stericson Busybox from playstore?
Good Luck !
Click to expand...
Click to collapse
I've tried many Busybox versions, including stericson and it still won't work. Maybe the OS has something to do with it, if it works on KitKat and not Jelly Bean?
I failed to as well. I even tried the zip install.
Sent from my MT2L03 using Tapatalk
I tried everything today: manual Viper installation, different Busybox versions, etc., still doesn't work.
Maybe the KitKat update will make it possible. That is, if we ever get a KitKat update... I may not use a Huawei phone again if we don't get updates. There's already been so many issues (for me at least) with Emotion being so extensively modified from regular Android. And we don't have any developers at all. I'll probably go Nexus next time.
ScoobSTi said:
I was wondering if anyone has installed Viper4Android on this device. I had it on my previous phone and it worked flawlessly; all my music sounded amazing.
But ever since we achieved root, I couldn't successfully install it. It keeps telling me Busybox is broken or not installed, and therefore won't let me install the audio drivers.
Can anyone try installing it, if they can? My favorite band just released a new album and I'd love to hear it with a good equalizer.
Sent from my MT2L03 using XDA Free mobile app
Click to expand...
Click to collapse
I am using it now flawlessly. The driver cannot be installed automatically but you can manage to use the flashable zip file to install it manually.
First uninstall the app and backup your build.prop.
Download the flashable zip file here.
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796
Reboot to your TWRP and flash the zip file and reboot. The zip file would install the apk file in /system/priv-app which is actually not recognized by the Huawei system. So please manually move the apk file to /system/app or /data/app , or just install it and remove whatever file left in /system/priv-app
And then start the app you should be able to install the driver. Actually the driver has been installed after you flashed the zip file.
Since it will modify your build.prop, so please make a backup. And in my case it broke my build.prop so I had to modify the file manually. There is an example in the link above. Please append the followings at the end of your build.prop.
Code:
##Viper4android
lpa.decode=false
tunnel.decode=false
lpa.use-stagefright=false
lpa.releaselock=false
OK. Reboot and you are all set.
Again, if you encounter soft brick and the system ui fails to appear, high chances that V4a broke or deleted your build.prop. Make sure you make a back up of that file first.
dbmj said:
I am using it now flawlessly. The driver cannot be installed automatically but you can try to use the flashable zip file to install it manually...
[snip]
Click to expand...
Click to collapse
Do you have this working on the US version MT2L03? And can V4A be used to boost the handset (earpiece) volume?
Thanks,
arcadesdude said:
Do you have this working on the US version MT2L03? And can V4A be used to boost the handset (earpiece) volume?
Thanks,
Click to expand...
Click to collapse
Yes and yes. I am using the US version MT2L03 and it can be used to boost my earbud volume.
Sweet, I thought you had the non-US version at first. I'll install TWRP soon, try this and report back!
I managed to install it...but I dont know which settings will let me do this.
I want to increase the volume of the phone when using it as a phone held up to my ear without affecting battery drain. There are too many options. The FAQ links to a site to explain the settings but that site is down. Help?
Update: never mind I uninstalled viper4android (reverted to backup actually). It barely increased the volume but it would crash my phone when connecting to Bluetooth despite it being disabled for bluetooth.
Works great but shuts down when the screen sleeps. No option in the apps list to keep it running.
MikeyLee said:
Works great but shuts down when the screen sleeps. No option in the apps list to keep it running.
Click to expand...
Click to collapse
There was the option to mark it as a protected app for me but that's because i installed it to /data/app by copying it there. Did you install it to /system/app maybe?
I found it too buggy to keep though so I dont use it now.
Sent from my MT2L03 using Tapatalk
arcadesdude said:
There was the option to mark it as a protected app for me but that's because i installed it to /data/app by copying it there. Did you install it to /system/app maybe?
I found it too buggy to keep though so I dont use it now.
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
No I pushed it to data/app. No protect option for me
Aw, I forgot to install TWRP and try Viper over the weekend. I don't want to risk messing up my phone during the week, leaving me phone-less!
MikeyLee said:
Works great but shuts down when the screen sleeps. No option in the apps list to keep it running.
Click to expand...
Click to collapse
In the Viper settings, you can set "Show notification", so the system won't kill the app when the screen is off. If that's not enough, what I did on my previous phone was use this app to protect Viper. Install that, go to "Tasks", tap on Viper, and select "Exclude" on the bottom left.
Root the device (search how to root the device Huwei Mate 2)
Change to permissive mode with “SELinux Mode Changer” apk from xda or search.
Enable developer options (tapping the Settings->Builld Number several times will enable the developer options, by default it is hidden from the user) and uncheck Use Nuplayer option.
Install the viper4android (get the latest untouched viper4android from original viper4android thread).
optional making viper4andriod as system app(refer how to make system app, if you want to make viper4andorid as system app)
set following values on the “build.prop” using the (Build Prop Editor, search for apk)
##Viper4android
lpa.decode=false
tunnel.decode=false
lpa.use-stagefright=false
lpa.releaselock=false
Run following commands with “Terminal Emulator” apk (search playstore or internet)
>>su
>>/system/xbin/supolicy --live "allow mediaserver mediaserver_tmpfs:file { read write execute };"
Open the viper4android and install the drivers.
Reboot the device
After reboot Launch the viper4android and check the driver status then you will see driver status normal.
feel free to play with compatible mode option or other options to suit your needs.
Thanks, guy with one post who revived a year old thread. If anyone tries this let us know how you made out, I guess.
kimtyson said:
Thanks, guy with one post who revived a year old thread. If anyone tries this let us know how you made out, I guess.
Click to expand...
Click to collapse
I've been using V4A on stock ROMS and on CM ROMS with no issues at all.
It tries to load the framework and then it says Gravitybox has stopped working, it will close now.
The same problem as here:
http://forum.xda-developers.com/showthread.php?t=2529641
That fix didn't work for me.
Doesn't work on stock ROM
Sent from my Pixel C using Tapatalk
xposed and gravitybox also work sin stock rom.
use xposed v 82 sdk 32
and before you flash it use selinuxmodechanger.
you also can read it on the xposed thread.
xposed needs permissive selinux mode
and our kernel has enforcing mode. thats why it dont work
I have Xposed already installed.
skeleton1911 said:
xposed and gravitybox also work sin stock rom.
use xposed v 82 sdk 32
and before you flash it use selinuxmodechanger.
you also can read it on the xposed thread.
xposed needs permissive selinux mode
and our kernel has enforcing mode. thats why it dont work
Click to expand...
Click to collapse
Hi
Rooted stock rom.
From the official xposed xda page, I installed xposed installer, then flashed framework sdk23 (marshmallow), arm64 v84.
Xposed says 'not compatible with sdk version 23 or your processor architecture (arm64-v8a)'.
Is it the selinuxmodechanger that i haven't installed (yet) or will v84 not work anyway?
arlrb said:
Hi
Rooted stock rom.
From the official xposed xda page, I installed xposed installer, then flashed framework sdk23 (marshmallow), arm64 v84.
Xposed says 'not compatible with sdk version 23 or your processor architecture (arm64-v8a)'.
Is it the selinuxmodechanger that i haven't installed (yet) or will v84 not work anyway?
Click to expand...
Click to collapse
You're using the wrong version of xposed installer, you need v3.0-beta4.
Jonny said:
You're using the wrong version of xposed installer, you need v3.0-beta4.
Click to expand...
Click to collapse
Thank you, Jonny.
In case anyone else runs into this problem, it's the material design version by DVDandroid.
If you have any other version already installed, uninstall it first.
arlrb said:
Thank you, Jonny.
In case anyone else runs into this problem, it's the material design version by DVDandroid.
If you have any other version already installed, uninstall it first.
Click to expand...
Click to collapse
So, you downloaded the app and clicked on INSTALL/UPDATE with framework "xposed-v84-sdk23-amd64" and that's it?
xposed Qs
llucax said:
So, you downloaded the app and clicked on INSTALL/UPDATE with framework "xposed-v84-sdk23-arm64" and that's it?
Click to expand...
Click to collapse
Yes, that was it. It will auto-shutdown & auto-flash in TWRP, then restart & it should be done.
However, xposed installer says, in green, that sdk23 arm64 is active, yet, i'm not sure if a couple of modules i've tried are working properly/at all.
Minminguard module (ad blocker) for instance says that xposed is not enabled, & sure enough ads are still popping up in apps & in chrome.
So i'm wondering if certain modules won't work seeing as i'm using the latest installer & sdk/64? ie do the module developers need to keep up?
Can someone shed some light on how it works in that respect?
Should i try the 32bit sdk? (all 32bit sdks will work on a 64bit cpu, won't they?)
Or should i try a different version - 82?
Is there a version that is most reliable for most modules?
Same results in here, I guess we have to change the SELinux mode somehow for it to work according to what I've read somewhere else...
llucax said:
Same results in here, I guess we have to change the SELinux mode somehow for it to work according to what I've read somewhere else...
Click to expand...
Click to collapse
As skeleton1911 wrote "and before you flash it use selinuxmodechanger". That fixed most of my problems, I also use xposed V84, haven't tried V85 though
there is a solution for xposed by skeleton1911
---------- Post added at 02:25 PM ---------- Previous post was at 02:22 PM ----------
skeleton1911 said:
Guys
there is a solution for xposed:
1. with mixplorer go to system/etc/init.d/ 07permissive and open it with editor (just tap on it)
2. remove the sleep 60 line. save and reboot to recovery
3. flash xposed framework , reboot and install xposed app and your modules. enable them in xposed app and reboot (normal xposed procedure)
4. open your apps like gravitybox etc.. ( they will connect to the xposed framework now)
5. open 07permissive again in system/etc/init.d and add sleep 60 into it again
6. save and reboot
Done!
in short words:
the cause is permissive and enforcing. Xposed only run in permissive mode on boot , but permissive mode forces some apps to close , but it is needed for viper v4a so i did this init.d script, system boots in enforcing and after 60 sec it will switch to permissive.
this is a dirty but working method. there is no other way at the moment because elephone didnt released the kernel source to modify it..
1. remove sleep 60 in 07permissive , save and reboot
2.perform the xposed stuff and after reboot open all xposed apps so they can connect to the xposed framework
3. add sleep 60 back into 07permissive and reboot
All works now!
cheers!
p.s: I will make a flashable zip for that soon
Click to expand...
Click to collapse
Do it anybody probe it? Maybe Do it working?
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Aha, thanks, I didn't know what is the difference
Jtig said:
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Click to expand...
Click to collapse
Mmm, OK, maybe is the soft reboot what I missed, because I used selinuxmodechanger and it didn't work with a full reboot. I am using stock but with RodriguezMod, but I think I will try the Eragon ROM. I'll report back. Thanks!
I'm finally trying the Eragon ROM, and following the steps from skeleton1911 finally seem to be working! At least Amplify for the first time is not complaining about not having Xposed. So I wiped, flashed the ROM, updated the SuperSU binary, rebooted, remove the sleep from the init.d script, went to the Xposed installer Material beta, updated from v82 to v85 using the installer, and after that flash, Amplify started to recognize Xposed!
Jtig said:
That's for his custom rom. For the stock rom you need selinuxmodechanger, set it to permissive and soft reboot via xposed. It will work fine then!
Click to expand...
Click to collapse
That fixed it, thanks.
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
AP756 said:
To whom it may concern: Asus software engineers were busy and they released Oreo: https://www.asus.com/de/Phone/ZenFone-4-ZE554KL/HelpDesk_Download/
For me I'll wait for some answers about compatibility of TWRP and the possibility to root. At present I run rooted Nougat Version WW_14.1064.1711.96 (TWRP 3.1.1 with Magisk V15.2, XPosed V89 and Gravity Box [N.] V 7.0.6). Never change a running system if you don't feel the urgent need
Click to expand...
Click to collapse
Excellent. You use XDA guide to Root and install TWRP? You don't have brick?
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3.
The main problem: ROOT doesn't work. Root check says phone's rooted, and apps request and get root permissions, but in fact there's no one. For example, root uninstaller can't remove any system app. Tried lesser TWRP (3.1.1), tried SuperSU instead of Magisk. SuperSU doesn't even work, says "SU binnary occupied".
Also one problem: WW-15.0405.1712.83 doesn't want install through TWRP, says "no file contexts". But you can install it through stock recovery, it just bypasses this check.
To get stock recovery, you can do the trick: install SuperSU, boot system, open the app and pick "Unroot" option (it will offer you to clear recovery and boot). Now you get stock recovery and can install firmware.
UPD: Was wrong. Root works, but neither Magisk nor SuperSU gives RW permission on system folder. That's the main problem now. Tried updating permissions on system folders manually through file managers (Root Explorer, etc.). Tried updating through terminal: from adb shell and from recovery. Nothing works. Folders are marked RW now, permissions are right, but apps like Root Uninstaller still can't do anything.
Click to expand...
Click to collapse
Thanks to shared. You have sucess to make root?
PedroArmindo said:
Thanks to shared. You have sucess to make root?
Click to expand...
Click to collapse
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Vikindor said:
Well, yes. As said at the end of the last message, phone in fact appears to be rooted. I have access to /root folder and apps now ask for super-user permissions.
But some apps, like Root Uninstaller, doesn't work... However you can manually delete unwanted .apk from /system folder, it's possible.
Click to expand...
Click to collapse
Could you test if the Titanium Backup app works?
grinna said:
Could you test if the Titanium Backup app works?
Click to expand...
Click to collapse
Checked. Yep, it works.
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Vikindor said:
After couple nights of pain, finally installed 8.0.0. I have TWRP 3.2.1-0 and Magisk 15.3. ...
Click to expand...
Click to collapse
lunger said:
I'm sorry if this is a noob question, but where can I get TWRP 3.2.1-0?
Click to expand...
Click to collapse
Hi. Sorry, haven't seen this message.
TWRP: https://twrp.me/
Magisk can be found here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (or in app stores).
Hi,
Can anyone help me with my phone ZE554kL on how to root this or link me to a guide? Thanks in advance.
"Continue reading only if interested what happen."
I've never done this before and I just want to do root because my internal storage was wiped out when I was backing up all my files to PC. Windows explorer stops responding while transferring files then after the not responding issue, my internal storage is empty and when I checked my phone all the files is gone (photos, videos, PDFs).
I tried different android recovery software in windows and everytime i do a scan, i always ending up being asked by the software to root my phone so it can scan through to my internal storage.
Since my files was lost, i never touch my phone since then so nothing will be written on internal storage that could take away the chance of recovering my files.
Hello guys!
If you update to the latest Magisk version (v16.4), you will notice that it will now pass SafetyNet check.
Check attached screenshots!
rzarectha said:
Hello guys!
If you update to the latest Magisk version (v16.4), you will notice that it will now pass SafetyNet check.
Check attached screenshots!
Click to expand...
Click to collapse
Thats nice to know. I mean i havent used magisk yet (on previous phone it didnt work at all). Currently still on supersu. But its good to know that it works again, so i might switch in the future.
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
GodOfPsychos said:
Thats nice to know. I mean i havent used magisk yet (on previous phone it didnt work at all). Currently still on supersu. But its good to know that it works again, so i might switch in the future.
Sent from my ZTE A2017G running V1.2.0B08 using XDA Labs
Click to expand...
Click to collapse
I think it's just as good as SuperSU in handling root apps. The way Magisk stands out though is the modules. I would recommend that you install only the magisk manager (it does not mess with anything in your phone if you just install it), and browse through the list of modules it has. It's very similar to the way modules in xposed look like. Maybe you can find some interesting functionality in there.
I am using the greenify module (works much like boost mode on xposed), busybox, adblocker, systemiser (turns user apps in sys apps), debloater (completely uninstall user apps). There's a ton of mods though, I don't even understand what most actually do.
Keep in mind that having xposed installed will break safetynet no matter what. Magisk can't hide it.
rzarectha said:
I think it's just as good as SuperSU in handling root apps. The way Magisk stands out though is the modules. I would recommend that you install only the magisk manager (it does not mess with anything in your phone if you just install it), and browse through the list of modules it has. It's very similar to the way modules in xposed look like. Maybe you can find some interesting functionality in there.
I am using the greenify module (works much like boost mode on xposed), busybox, adblocker, systemiser (turns user apps in sys apps), debloater (completely uninstall user apps). There's a ton of mods though, I don't even understand what most actually do.
Keep in mind that having xposed installed will break safetynet no matter what. Magisk can't hide it.
Click to expand...
Click to collapse
Edit: i moved this issue to the Q&A and help section since more issues keep coming
https://forum.xda-developers.com/axon-7/help/finally-decided-to-switch-supersu-to-t3787201
just switched to latest stock rom (1.2.0 B10) and installed magisk (16.4). it works and safetynet passes. the problem i got now is that the greenify module fails to install in magisk (see screenshot)
do i gotta flash the module through TWRP maybe? still a newbie to magisk since the axon 7 is the first phone to have it working
EDIT: for some reason magisk doesn't remember which apps have requested root after a reboot. everytime i reboot i get a prompt to allow root access to all my root apps (like greenify). idk why this is happening. i mean, root itself is working as it should. i already uninstalled bloatware and disabled/freezed things like the powermanagement
I'm interested in knowing where Magisk is at
As the title says, is it possible.and how to successfully install Viper4Android to Renoir, running MIUI 12.5+, A11 - assuming that the phone is already rooted by Magisk
Or at least, how to successfully install JanesDSP
If you have already Magisk and rooted your phone, you can install the module of Viper with it.
Thoiareg said:
If you have already Magisk and rooted your phone, you can install the module of Viper with it.
Click to expand...
Click to collapse
Did you try and does it really work for you?
I've posted to Viper4Android thread with more details - Viper4Android apk can never find drivers:
- It asks to install drivers and to reboot
- After rebooting and reopening, Viper4Android apk again does not find drivers and asks to install and to reboot
- It can go endlessly
I tried with AML, by debloating' MusixFM, no avail
---
Similarly, I tried but cannot properly install JamesDSP
It's app always crashes, with exception saying that it cannot find drivers
Reported also to JamesDSP thread
---
In both threads there are several other users with the new A11 phones who report the same problems (cannot install Viper4Android, neither JamesDSP)
Frankly, I don't have Renoir - I have Lisa (Xiaomi 11 Lite 5G NE), with MIUI 12.5.8, A11.
Still, I wanted to ask if somebody with the similar Renoir (Mi 11 Lite 5G) succeeded to install V4A or JamesDSP?
zgfg said:
Did you try and does it really work for you?
I've posted to Viper4Android thread with more details - Viper4Android apk can never find drivers:
- It asks to install drivers and to reboot
- After rebooting and reopening, Viper4Android apk again does not find drivers and asks to install and to reboot
- It can go endlessly
(...)
Click to expand...
Click to collapse
The magisk module is not a apk. It't a zip file.
Best Magisk modules
Looking for some of the best Magisk modules for modding? We’ve got all the information you need to get started right here. Read on!
www.xda-developers.com
Thoiareg said:
The magisk module is not a apk. It't a zip file.
Best Magisk modules
Looking for some of the best Magisk modules for modding? We’ve got all the information you need to get started right here. Read on!
www.xda-developers.com
Click to expand...
Click to collapse
Sorry, I'm 5 years user of V4A, used successfully on 5 phones so far - I perfectly know what is Magisk, Magisk modules, V4A module, how it installs, etc
I'm talking about the Viper4Android application that installs with the module and serves for managing presets, kernels, etc
If you have practical advice how to install to the new MIUI release.(that you can prove that it works), fine - otherwise please let's stop wasting the time
Good night
zgfg said:
Sorry, I'm 5 years user of V4A, used successfully on 5 phones so far - I perfectly know what is Magisk, Magisk modules, V4A module, how it installs, etc
I'm talking about the Viper4Android application that installs with the module and serves for managing presets, kernels, etc
If you have practical advice how to install to the new MIUI release.(that you can prove that it works), fine - otherwise please let's stop wasting the time
Good night
Click to expand...
Click to collapse
Sorry, but I don't know you.
So, I answer according to the information you give in your message.
You have a problem installing Viper, I suggest you install it via Magisk. And you answer by talking about an apk file. So your answers don't make sense.
Now be nicer to people who respond to you and try to help you.
Good luck in your problem.
Solved by temporarily disabling USNF 2.2.1 - then JamesDSP installed correctly.
Later I re-enabled USNF and now both modules work correctly
Still I wasn't able to make V4A working
Anyway, closing the thread
THREAD LOCKED
Requested by OP.
Regards,
shadowstep
Forum Moderator