Hello everyone,
I am trying to (completely) unroot the lineageos version of Android x86. The only thing I need is an old pc can run Android without root since the app I am about to use does not work if the device (android) is modified. I tried several different ways:
DIsable root in settings
Physically remove su binary
Using Gearlock to install custom recovery then able to install Magisk, but could not hide the root (Safetynet) using Magisk
None of them works in order to run the app.
Would some one have experience on this? Thank you in advance.
2. Have your removed all of it?
https://download.lineageos.org/extras
How about using some other build?
https://www.xda-developers.com/tag/android-x86/
CXZa said:
2. Have your removed all of it?
https://download.lineageos.org/extras
How about using some other build?
https://www.xda-developers.com/tag/android-x86/
Click to expand...
Click to collapse
Thanks for your reply. I already tried to flash the su removal addon from lineageos but the thing is, it is unable to have TWRP with android x86 for now (as I know), so the only custom recovery is Gearlock but it is failed to flash su removal via Gealock
Android x86 only has two releases of lineageOS which is 13.0 and 14.1. I tried both and same issue.
Thanks again
lnguy193 said:
Thanks for your reply. I already tried to flash the su removal addon from lineageos but the thing is, it is unable to have TWRP with android x86 for now (as I know), so the only custom recovery is Gearlock but it is failed to flash su removal via Gealock
Android x86 only has two releases of lineageOS which is 13.0 and 14.1. I tried both and same issue.
Thanks again
Click to expand...
Click to collapse
Signed zips can be flashed in stock recovery...
Here are the files that it removes...
/system/system/addon.d/51-addonsu.sh
/system/system/bin/su
/system/system/etc/init/superuser.rc
/system/system/xbin/su
Why it has to be lineage? You could get pie, also bliss has it.
https://www.android-x86.org/changelog.html
CXZa said:
Signed zips can be flashed in stock recovery...
Here are the files that it removes...
/system/system/addon.d/51-addonsu.sh
/system/system/bin/su
/system/system/etc/init/superuser.rc
/system/system/xbin/su
Why it has to be lineage? You could get pie, also bliss has it.
https://www.android-x86.org/changelog.html
Click to expand...
Click to collapse
For some weird reasons the app I will mainly use always work only the lineage version, but crashed on others. I haven't tried pie and bliss yet! I just only removed the 2 su binaries in /bin and /xbin. I will try to reflash or remove the other two files that you recommended. Thanks
lnguy193 said:
For some weird reasons the app I will mainly use always work only the lineage version, but crashed on others. I haven't tried pie and bliss yet! I just only removed the 2 su binaries in /bin and /xbin. I will try to reflash or remove the other two files that you recommended. Thanks
Click to expand...
Click to collapse
Yes same here, I am also looking for an unrooted lineage OS(works well), or any other unrooted Android OS.
Can anyone help finding a stable unrooted OS.
Related
I have uploaded the latest androd 6.0.1 MMB29K.
I have twrp installed - the latest I believe.
super su - 2.46 pro
I installed the ElementX kernel - can't remember witch page I followed to root my nexus 9. but it suggested this.
Now I can't set a pin for my sudoers
tried uninstalling and reinstalling no luck.
I have ex kernel manager and it says there is a new version available, but I need superSU 2.61 - witch means the new beta version.
Looking at the thread http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
looks like I have refrash a stock boot
"
If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
"
how do I do this ?
What does the new kernel give me ?
Any idea on why my supersu doesn't let me use pin codes ?
KeyzerSuze said:
I have uploaded the latest androd 6.0.1 MMB29K.
I have twrp installed - the latest I believe.
looks like I have reflash a stock boot
"
If you are coming from any SuperSU install in /system, you must re-flash the stock system partition contents prior to installing this.
"
how do I do this ?
What does the new kernel give me ?
Any idea on why my supersu doesn't let me use pin codes ?
Click to expand...
Click to collapse
Latest TWRP for Nexus 9 is twrp-2.8.7.1-flounder
Get the latest factory image and unzip the contents a few times then use fastboot to flash both boot.img and system.img.
From TWRP Flash SuperSU-v2.62-3 first and then the latest ElemetalX kernel (if you want it, not needed for root).
Never used pin codes with supersu, so don't know about that.
corkiejp said:
Latest TWRP for Nexus 9 is twrp-2.8.7.1-flounder
Get the latest factory image and unzip the contents a few times then use fastboot to flash both boot.img and system.img.
The latest SuperSU-v2.62-3
From TWRP Flash that first and then the latest ElemetalX kernel (if you want it, not needed for root).
Never used pin codes with supersu, so don't know about that.
Click to expand...
Click to collapse
Flashing vendor.img is a good idea as well, just to make sure everything is synced up.
I'm I going to have to reinstall all my apps again ?
Sent from my Nexus 6P using Tapatalk
KeyzerSuze said:
I'm I going to have to reinstall all my apps again ?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Flashing just boot.img, system.img and vendor.img, will not wipe data.
And leaves data untouched, so won't need to reinstall apps again. Just don't flash the full factory image.
(Note: Flashing the full factory image can also be done without wiping data)
Thanks did it and all good.
Sent from my Nexus 6P using Tapatalk
Just flash the zip in the attachment, and then flash SuperSU. No more messing with Terminal Emulator!
Note: if you installed SuperSU first, and got a bootloop, install the fixer then SuperSU again. All will be good.
Please don't redistribute this, just link to the thread.
Thanks. Phone wouldn't boot after SuperSU install. This worked perfectly.
Note: if you installed SuperSU first, and got a bootloop, install the fixer then supersu again. All will be good.
mx597turbo said:
Thanks. Phone wouldn't boot after SuperSU install. This worked perfectly.
Note: if you installed SuperSU first, and got a bootloop, install the fixer then supersu again. All will be good.
Click to expand...
Click to collapse
I'll add your note to the op
Life saver
Yay! I was in that bootloop, and then I couldn't find an ADB driver that worked, to load this fix. The obvious solution was to put the fix on a Micro-SD card but it didn't come to me for a bit - my other current phone has no external card slot - but once I did this, the fix worked perfectly. Many thanks to whomever came up with this!!!
No need to flash SuperSu for root, phh's SuperUser works perfect
Can I ask what this script exactly does?
Is this only for flashing SuperSU on to stock? or is this something I need to use every time I flash SuperSU on any rom, even on lineageOS?
I just am confused what this script does and when exactly I would need to use it. Thanks!
BigNaes said:
Can I ask what this script exactly does?
Is this only for flashing SuperSU on to stock? or is this something I need to use every time I flash SuperSU on any rom, even on lineageOS?
I just am confused what this script does and when exactly I would need to use it. Thanks!
Click to expand...
Click to collapse
This is for roms on stock and also roms that do not support native root. If you flash LineageOS, all you have to do is flash their SU package in their Extras section on the website. Some of the roms in the development section have native root built in under development settings, and some do not.
fireball0093 said:
This is for roms on stock and also roms that do not support native root. If you flash LineageOS, all you have to do is flash their SU package in their Extras section on the website. Some of the roms in the development section have native root built in under development settings, and some do not.
Click to expand...
Click to collapse
Thank you for your reply. I understand. I prefer to use SuperSu as opposed to the LineageOS SU package.
When I installed LineageOS I flashed this zip first and then SuperSU after and it works perfectly, I am just not sure if I needed this zip first when using Lineage OS.
Also one last question is I believe I found a post which explains what this fix does, can anyone confirm this is the fix being performed? https://forum.xda-developers.com/moto-g4/how-to/how-to-root-g4-fix-bootable-attempted-t3417592
Thanks again for all the help, always learning on XDA :good:
If anybody wants the manual method, type this is Terminal in TWRP Recovery:
echo SYSTEMLESS=true>>/data/.supersu
Ashutosh Sundresh said:
If anybody wants the manual method, type this is Terminal in TWRP Recovery:
echo SYSTEMLESS=true>>/data/.supersu
Click to expand...
Click to collapse
What's that for??
Sanjay parsi said:
What's that for??
Click to expand...
Click to collapse
SuperSU, if you don't type this, your device WILL bootloop
download link isn't working for me.
Edit: everything is fine my brain is the one not working
So... CyanogenMod is dead. LineageOS is taking it's place. The ROM is basically CyanogenMod but with changes to the name.
This is completely 'stock' from their source code and will be prerooted (under Developer options in Settings)
Changelog is available at LineageOS Gerrit
There are no apparent bugs, but any bug reports will be welcome.
Gapps are available at OpenGapps.
These should build almost every night
Installation
Download latest release from here
Install it in TWRP recovery
Install the downloaded opengapps package
XDA:DevDB Information
LineageOS/CyanogenMod 14.1 Nightlies, ROM for the Nexus 7 (2013)
Contributors
hazzer
Source Code: https://github.com/LineageOS/
ROM OS Version: 7.x Nougat
Based On: LineageOS
Version Information
Status: Nightly
Created 2017-01-08
Last Updated 2017-01-08
May you upload some Screenshots? Can I dirty flash? I'm on CyanogenMod 14.1 20161225
Just clean installed, no big difference from Cyanogen,.. Not even the logo.
Everything seams to be working as it did on cyanogen nightly.
Regards,
Me
Thank you
Sent from my Nexus 6 using XDA Free mobile app
Thanks for this, great job.
@hazzer I'd like to grab your image but your website seems down?
Edit: I see it's back up, thanks!
Can you enable your rom to use the built in updater?
Which opengapps do you suggest?
Poslano z mojega ONE E1003 z uporabo Tapatalk
@hazzer there are still two bugs first being hangouts crashes when you try to message someone over unless it's from the notification. This works fine on my other lineage devices. Second is Allo's message sounds use a don't play because it doesn't like the codec. This works in regular Android but seems to be a Lineage specific bug.
@jstsmblaz
pico works fine for me.
Sent from my Nexus 7 using XDA Labs
Edit :
(I use pico for testing. If I need more I use a gapps-config file.)
Lost Root
Root access in Developer Options is greyed out. Only options are Disable and ADB. I am using TWRP 3.0.2. Yes, bootloader is unlocked. I had root with CM 1/25/2016 and when restored to that version, Root returned.
When I installed 1/16/2017, I did not wipe Data.
Am I missing something in Developer Options? Any thoughts?
I stated at the start of this 'project', I am balancing this alongside school work. Unfortunately, it's just become too much to manage alongside time consuming A levels.
This means:
Builds will be less frequent (perhaps once or twice a week)
I'm not going to be available on XDA or IRC very often (if at all)
I apologise I haven't been the best at communicating or fixing issues, but I just didn't envisage having to invest the amount of time I have.
If anyone would like to take over, give me a shout. You can borrow my server for hosting and my blog article if you're willing to learn.
You might see me again sometime around July. Thanks everyone for helping me with an incredible learning process into the depths of Android.
pclewis said:
Root access in Developer Options is greyed out. Only options are Disable and ADB. I am using TWRP 3.0.2. Yes, bootloader is unlocked. I had root with CM 1/25/2016 and when restored to that version, Root returned.
When I installed 1/16/2017, I did not wipe Data.
Am I missing something in Developer Options? Any thoughts?
Click to expand...
Click to collapse
When I first starting doing builds (before Lineage rebrand, and before CM shutdown), I disabled root for personal reasons (passing SafetyNet by default). I achieved this by building the ROM as 'user' instead of 'userdebug', which disables and also doesn't install the su binary to /system.
When the project transitioned to Lineage (after the CM shutdown), I began to build as userdebug (this is the default) again, to be close to official nightlies as possible.
Members of the Lineage team decided to (by default) remove root from Lineage builds (in the last few days), so the ROM will pass SafetyNet by default. This means root is now disabled in my builds (as I haven't explicitly enabled root).
If you would like root in the ROM, (SuperSU) or (Magisk+phh) is the way to go
SuperSU
hazzer said:
When I first starting doing builds (before Lineage rebrand, and before CM shutdown), I disabled root for personal reasons (passing SafetyNet by default). I achieved this by building the ROM as 'user' instead of 'userdebug', which disables and also doesn't install the su binary to /system.
When the project transitioned to Lineage (after the CM shutdown), I began to build as userdebug (this is the default) again, to be close to official nightlies as possible.
Members of the Lineage team decided to (by default) remove root from Lineage builds (in the last few days), so the ROM will pass SafetyNet by default. This means root is now disabled in my builds (as I haven't explicitly enabled root).
If you would like root in the ROM, (SuperSU) or (Magisk+phh) is the way to go
Click to expand...
Click to collapse
SuperSU will not root with TWRP, since root is built into TWRP. It just looks for a missing binary,
@pclewis
That's odd. What version of twrp and SuperSU are you using?
I have been using SuperSU with no problems since the cm-20161231 build.
- I didn't try phh, normally I use phh when SuperSU does not work.
Note :
I initially installed the rom, gapps and SuperSU using twrp. - Completely clean install.
Sent from my Nexus 7 using XDA Labs
ipdev said:
@pclewis
That's odd. What version of twrp and SuperSU are you using?
I have been using SuperSU with no problems since the cm-20161231 build.
- I didn't try phh, normally I use phh when SuperSU does not work.
Note :
I initially installed the rom, gapps and SuperSU using twrp. - Completely clean install.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
I use TWRP 3.0.2 and it has root built in. Works fine with 1/25/2016 but root is lost with the Linage. I tried SuperSU 2.79, but it is looking for binary that does not exist.
The decision to not support root is not consistent with the Linage teams. I have updated two phones to Linage since CW and both maintain root. I think they need to reconsider. Most of us run TWRP and simply want to root with that.
So im on the 1112017 build and was wondering if anyone else is experiencing screen rotation issues. Is it a software issue or just my tablet being old?
pclewis said:
I use TWRP 3.0.2 ….. I tried SuperSU 2.79
Click to expand...
Click to collapse
Thanks, I wanted to make sure I was using the same files.
I think you may have a few things mixed up.
pclewis said:
The decision to not support root is not consistent with the Linage teams.
Click to expand...
Click to collapse
Lineage changed that. (With the current and newer builds the biggest change the user will see, is selinux enforcing and non rooted. This way clean installs with work with banking apps and pass SafetyNet.)
pclewis said:
I use TWRP 3.0.2 and it has root built in. Works fine with 1/25/2016 but root is lost with the Linage.
Click to expand...
Click to collapse
This has nothing to do with TWRP itself. Lineage removed root access from their builds.
TWRP has root access to modify your device. - All recoveries do.
(Recovery is limited by the developer depending on what they allow the user to do. This is why we can not just install what we want with stock recovery and need custom recoveries like TWRP or Clockwork.)
TWRP will NOT root your rom automatically, you will need to install a su and manager.
SuperSU (Download link in OP of thread.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
SuperSU-v2.79-201612051815.zip
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- - - Now back to your prior post.
pclewis said:
SuperSU will not root with TWRP ..... It just looks for a missing binary,
Click to expand...
Click to collapse
Initially you can not install su binary from the apk.
Install one of the following using twrp. (These are the current SuperSU zip files.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
SuperSU-v2.79-201612051815.zip
All three worked for me regardless.
I installed 20170113 and pico gapps only. Ran through the setup and then dirty flashed 20170116. (Lost root access.) Rebooted into twrp and installed SuperSU-v2.79-201612051815.zip. Rebooted and SuperSU took over root access.
Sent from my Nexus 7 using XDA Labs
20170120 : lineage boot animation?
Sent from my SM-G935F using XDA-Developers Legacy app
ipdev said:
Thanks, I wanted to make sure I was using the same files.
I think you may have a few things mixed up.
Lineage changed that. (With the current and newer builds the biggest change the user will see, is selinux enforcing and non rooted. This way clean installs with work with banking apps and pass SafetyNet.)
This has nothing to do with TWRP itself. Lineage removed root access from their builds.
TWRP has root access to modify your device. - All recoveries do.
(Recovery is limited by the developer depending on what they allow the user to do. This is why we can not just install what we want with stock recovery and need custom recoveries like TWRP or Clockwork.)
TWRP will NOT root your rom automatically, you will need to install a su and manager.
SuperSU (Download link in OP of thread.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
SuperSU-v2.79-201612051815.zip
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
- - - Now back to your prior post.
Initially you can not install su binary from the apk.
Install one of the following using twrp. (These are the current SuperSU zip files.)
SR3-SuperSU-v2.79-SR3-20170114223742.zip
UPDATE-SuperSU-v2.79-20161211114519.zip
SuperSU-v2.79-201612051815.zip
All three worked for me regardless.
I installed 20170113 and pico gapps only. Ran through the setup and then dirty flashed 20170116. (Lost root access.) Rebooted into twrp and installed SuperSU-v2.79-201612051815.zip. Rebooted and SuperSU took over root access.
Sent from my Nexus 7 using XDA Labs
Click to expand...
Click to collapse
Thanks, I get it. I really don't root the phones I use. I let them update OTA and need the security. The older ones I used to use Titanium and needed root. Now a TWRP BU is fine and I really don't need root I suppose. Thanks for your reply and I understand the logic.
Why do some devices allow root to be turned off and on in developer options for either apps, adb or both?
BTW, just installed 11/20/2017. Seems to work fine and does not have root. I will run this for a while. Thanks again?
Phil
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
As far as I'm aware the rom should be pre rooted and all you'll need to do is install supersu from googleplay and then update the su binaries from within the supersu app.
Set it to option 4 (apps and abd) and go about installing supersu first as the app from googleplay and if no joy then as a flashable zip file.
Beamed in by telepathy.
amitrider04 said:
I had recently upgrade my s3 using TWRP recovery from 4.4 to 7.1 lineage os
But I am facing problem with rooting.
I am not able to root my device from
1)TWRP recovery
2)Odin(CF Auto Root)
3)Kingroot(Android and PC )
I have installed TWRP properly
PLz give an idea to root my device
I have checked in developer option
That is ROOT ACCESS
Their is 2 Option only
1)Disable
2)Adb only
But I am not able to get root access any of this Or Adb only
Previously I tried with different ROM
Their is option of
1)disabled
2)Apps only
3)Adb only.
4)apps and Adb
But in this ROM I am not able to find suggest me any way to fix this
I installd 4 time s same ROM to get this root access but failed
Check below screenshot
In SuperSU application
No su binary installed
https://dropfile.to/bRO4jKc
https://dropfile.to/MMWxWrp
Click to expand...
Click to collapse
Did you try to flash the addonsu.zip from LineageOS website?
You must flash it to get root access in LineageOS 14.1
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Flash a stock firmware and start over.
Beamed in by telepathy.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
Are you sure you flashed the correct addonsu???
As far as i remember, the s3 doesn't have 64x, flash the normal arm version (arm32x).
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
flash supersu.zip 2.79 with twrp it worked for me
Thanks it also worked for me:laugh:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Zwolly said:
Thank you!!!
That worked for me.
Now i would like to know why this works and not the file from Lineage itself....
Click to expand...
Click to collapse
It works, you will get an error in recovery, but when you boot, you will get root access normally, i don't why the error happens, but it's harmless anyway.
Root fix
I'm not sure if you have fixed it yet but just in case if this helps the way I got around this is by simply downloading the latest super su zip from the official site and manually flashing via twrp kinda sucks but it works the first boot took a little though so if you try this and it takes forever for your device to not just wait because it can take up to 15 min the first time. So basically as long as you have twrp you are rooted technically it's just based on the rom wether they chose to support it if not the zip always works but you need the app too.
amitrider04 said:
I have tried to flash addonsu for lineage os
×64
But failed now i am getting just option to
Apps and adb but its not giving me obtain root
Options are available in root acces
Apps only
Adb only
Adb and apps
But if i checked adb and apps or anything
Root checker still says No root
I am not able to get root access:crying:
Click to expand...
Click to collapse
amitrider04 said:
Bro i have tried to flash ARM AND ARM X86 but it says
update failed in twrp recovery
So i flashed with x64
It was done but not worked properly
Check this
https://s21.postimg.org/99z5kiw07/Screenshot_2017_03_20_12_21_53.png
Click to expand...
Click to collapse
S3 has arm32. So neither x86 not x64 would work. You should've flashed addonsu.zip for 32.
Sent from my Pixel XL using Tapatalk
I'm currently running Android 11 based Wave OS on my Redmi Note 9 Pro (Curtana). I have OrangeFox recovery installed. I want to flash latest stock ROM which is also based on Android 11.
So, can anyone help me with the correct procedure for the flashing of Stock MIUI 12 based on Android 11 on my Curtana with OF recovery installed?
Azamsm said:
I'm currently running Android 11 based Wave OS on my Redmi Note 9 Pro (Curtana). I have OrangeFox recovery installed. I want to flash latest stock ROM which is also based on Android 11.
So, can anyone help me with the correct procedure for the flashing of Stock MIUI 12 based on Android 11 on my Curtana with OF recovery installed?
Click to expand...
Click to collapse
You can flash this directly from ofox. It's the current updated Android R stock firmware which is stable. Just format your data, flash the recovery rom (not the fastboot rom) and reboot.
But I highly recommend you to try EU rom from xiaomi.eu website.
MPK99 said:
You can flash this directly from ofox. It's the current updated Android R stock firmware which is stable. Just format your data, flash the recovery rom (not the fastboot rom) and reboot.
But I highly recommend you to try EU rom from xiaomi.eu website.
Click to expand...
Click to collapse
So, I can flash this one by the same method?
Azamsm said:
So, I can flash this one by the same method?
Click to expand...
Click to collapse
Ys. It's the eu one that I mentioned.
But note that eu roms are always little behind the latest versions.
Right now, eu rom is 12.0.1 & stock is 12.0.4.
But don't worry, differences are very minor. Go with EU.
MPK99 said:
Ys. It's the eu one that I mentioned.
But note that eu roms are always little behind the latest versions.
Right now, eu rom is 12.0.1 & stock is 12.0.4.
But don't worry, differences are very minor. Go with EU.
Click to expand...
Click to collapse
Hi @MPK99
I successfully flashed eu rom 12.0.1. Thanks for the guidance.
Can you also help me gaining root. I flashed Magisk 22.0 zip via OFox, it's successfully installed, root checker shows phone is rooted and even able to grant apps root access but it actually doesn't seem to be working. I can't modify system files and root apps don't do what they are supposed to do. Please help.
Thanks in advance!
Azamsm said:
Hi @MPK99
I successfully flashed eu rom 12.0.1. Thanks for the guidance.
Can you also help me gaining root. I flashed Magisk 22.0 zip via OFox, it's successfully installed, root checker shows phone is rooted and even able to grant apps root access but it actually doesn't seem to be working. I can't modify system files and root apps don't do what they are supposed to do. Please help.
Thanks in advance!
Click to expand...
Click to collapse
What method you used to root? Boot Patch or Recovery flash? Also check & tell whether device is encrypted or not.
MPK99 said:
What method you used to root? Boot Patch or Recovery flash? Also check & tell whether device is encrypted or not.
Click to expand...
Click to collapse
Recovery flash and device in not encrypted.
Can I have your telegram?
Azamsm said:
Recovery flash and device in not encrypted
Click to expand...
Click to collapse
Get latest Magisk (magisk-v22.0.zip), flash it as a module under Magisk app itself. Reboot.
MPK99 said:
Get latest Magisk (magisk-v22.0.zip), flash it as a module under Magisk app itself. Reboot.
Click to expand...
Click to collapse
Didn't work. Thanks for the help btw.
Azamsm said:
Didn't work. Thanks for the help btw.
Click to expand...
Click to collapse
There's no root problems btw. Try to enable root permissions for the explorer manually under magisk. Also check whether you allowed root under your explorer settings.
MPK99 said:
There's no root problems btw. Try to enable root permissions for the explorer manually under magisk. Also check whether you allowed root under your explorer settings.
Click to expand...
Click to collapse
I checked and it's enabled. But it's not working anyhow. Stock MIUI doesn't get rooted too. There's this wave OS rom which I could successfully root so far. But it had heating issue while charging. Maybe I should forget about rooting for a whilr
Azamsm said:
I checked and it's enabled. But it's not working anyhow. Stock MIUI doesn't get rooted too. There's this wave OS rom which I could successfully root so far. But it had heating issue while charging. Maybe I should forget about rooting for a whilr
Click to expand...
Click to collapse
Is root not working for just solid explorer or other root apps too? If root works on other apps, try Mixplorer instead of Solid.
MPK99 said:
Is root not working for just solid explorer or other root apps too? If root works on other apps, try Mixplorer instead of Solid.
Click to expand...
Click to collapse
Not working on any app.
While I retried flashing Magisk through OFox, I saw these lines
Code:
-System as root, keep dm/avb verity
- Encrypted data, keep force encryption
Is this the encryption you were talking about
Azamsm said:
While I retried flashing Magisk through OFox, I saw these lines
Code:
-System as root, keep dm/avb verity
- Encrypted data, keep force encryption
Is this the encryption you were talking about
Click to expand...
Click to collapse
Maybe. Because, Encryption & rooting together doesn't go well.
On Encryption, you have to follow boot patch method. Recovery flashing won't work.
Extract boot.img from your stock firmware (or EU rom firmware), patch that file from magisk patch method. You'll get patched_boot.img. Flash that as boot under recovery.
MPK99 said:
Maybe. Because, Encryption & rooting together doesn't go well.
On Encryption, you have to follow boot patch method. Recovery flashing won't work.
Extract boot.img from your stock firmware (or EU rom firmware), patch that file from magisk patch method. You'll get patched_boot.img. Flash that as boot under recovery.
Click to expand...
Click to collapse
Tried this method too, still can't delete that miui_mod_icons folder. Root isn't working yet.
Azamsm said:
Tried this method too, still can't delete that miui_mod_icons folder. Root isn't working yet.
Click to expand...
Click to collapse
Well, you have some specific reason to root. To remove some system apps right. You can do that on recovery too. Leave rooting, caz it's encrypted.
MPK99 said:
Well, you have some specific reason to root. To remove some system apps right. You can do that on recovery too. Leave rooting, caz it's encrypted.
Click to expand...
Click to collapse
Hey dude, first of all, I'm thankful to you for keeping calm and helping me
But actually both TWRP and OFox recoveries show nothing inside /system except for 4 folders which has nothing inside them. So I can't even see the files I want to delete.
Maybe it's because of the dynamic system partition or super partitions in android 11, idk I'm just super disappointed
Hey, @MPK99
One thing I noticed that system can be mounted read-only in OFox. If I want to mount it read-write, it just won't.