Modifying the /OEM partition? - Moto Z2 Force Questions & Answers

Has anyone figured out how to edit the /OEM partition? I've tried through root Explorer and through adb shell Su via terminal
Sent from my Moto Z (2) using Tapatalk

If it's anything like /system it's mounted read-only.
If you're rooted and run Linux:
# adb shell
$ su
# mount -o remount,rw /OEM
... and see what happens.
I don't know if the phone is running SELinux or not, and if so you'll need more special steps. Find out with # getenforce

Quantumstate said:
If it's anything like /system it's mounted read-only.
If you're rooted and run Linux:
# adb shell
$ su
# mount -o remount,rw /OEM
... and see what happens.
I don't know if the phone is running SELinux or not, and if so you'll need more special steps. Find out with # getenforce
Click to expand...
Click to collapse
Aye, I attempted to remount like this but it will not work for some weird reason.
Sent from my Moto Z (2) using Tapatalk

elijahaf97 said:
Aye, I attempted to remount like this but it will not work for some weird reason.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
wipe it using twrp, and dont use it. remove the items from oem you wish to keep and migrate them to the /system where they need to go, set perms and enjoy.
OEM is read only and is mounted to google, and if you delete something it gets put back, just wipe that partition and enjoy lol

Team DevDigitel said:
wipe it using twrp, and dont use it. remove the items from oem you wish to keep and migrate them to the /system where they need to go, set perms and enjoy.
OEM is read only and is mounted to google, and if you delete something it gets put back, just wipe that partition and enjoy lol
Click to expand...
Click to collapse
Last time I wiped it I was unable to boot.
Sent from my Moto Z (2) using Tapatalk

elijahaf97 said:
Last time I wiped it I was unable to boot.
Sent from my Moto Z (2) using Tapatalk
Click to expand...
Click to collapse
that shouldnt be the case... again you can just move everything from oem to /system and match the perms 1st then wipe it and essentiall all would be good, may need to wipe cache/dalvik cache to rebuild data for apps after move.

You can't add data to oem, but I was able to remove items from oem in TWRP with a kernel that had verity removed and state still green. (The TWRP custom kernel on Oreo and Pantheon both have this option). I still kept safetynet status green as well doing it through TWRP. Be sure to mount oem first!

Doesn't work on latest stock, OEM r/o. Any thought?

If you're just trying to debloat then you can follow this guide.

Uzephi said:
You can't add data to oem, but I was able to remove items from oem in TWRP with a kernel that had verity removed and state still green. (The TWRP custom kernel on Oreo and Pantheon both have this option). I still kept safetynet status green as well doing it through TWRP. Be sure to mount oem first!
Click to expand...
Click to collapse
Can you explain how to mount /oem partition like you did? I cannot for the life of me mount it in twrp to remove unnecessary apps and keep safetynet good?
Latest Sprint firmware. Latest TWRP. Latest Magisk. Latest Pantheon 8.0 kernel. Any help is greatly appreciated.
Typically I use superSU. But Epic games just made the gamepad Fortnite compatible and I'd like to try it WITH some type of root (Magisk) that won't mess up the safetynet check, yet be able to still have most of my usual root freedom.

gokart2 said:
Can you explain how to mount /oem partition like you did? I cannot for the life of me mount it in twrp to remove unnecessary apps and keep safetynet good?
Latest Sprint firmware. Latest TWRP. Latest Magisk. Latest Pantheon 8.0 kernel. Any help is greatly appreciated.
Typically I use superSU. But Epic games just made the gamepad Fortnite compatible and I'd like to try it WITH some type of root (Magisk) that won't mess up the safetynet check, yet be able to still have most of my usual root freedom.
Click to expand...
Click to collapse
Haven't tried on Oreo. Only got it to work on nougat by forcing verity off and disabling encryption.

deleted ...

Related

[Q] Unrooting

Hi All,
This is just a quick 2 part question as I see many threads for the GNEX on rooting, but none very concrete on removing root. I've tried searching, but I must have missed it.
So, my questions are:
1. Once rooted via whatever method (I used fastboot method myself, thanks efrant for teaching the fastboot stuff), how do I unroot this thing to bring it back to stock configuration?
2. To make the unit truly stock again, can I just use fastboot and flash a factory google image? I know doing this will eliminate all my data, but will it remove all traces of any rooting done? (Insecure Kernal, SU, Busybox and whatever else)?
Please let me know.
Thanks guys... wasn't planning on rooting, but I miss the ability to do it. lol
1. See two.
2. Yes.
Flashing the stock image will bring your phone back to an out-of-the-box state.
Sent from my Galaxy Nexus using Tapatalk 2
infazzdar said:
1. See two.
2. Yes.
Flashing the stock image will bring your phone back to an out-of-the-box state.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks man,
Makes me feel better about my decision to root this phone.
Appreciate the reply.
If you installed Superuser to system when you rooted then you'll need to remove that also but here are the basic adb commands for the job (make sure you have data and system mounted via CWM so you have access):
Code:
adb shell
rm /system/bin/su
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
BusyBox is another matter since CWM installs it to sbin every time you boot with it. Perhaps someone has a better idea (?), but from messing around a bit the other night the best method I've come up with is to use BusyBox to remove BusyBox, as follows:
Code:
adb shell
cd /sbin
cp busybox /data/local/tmp/busybox
chmod 06755 /data/local/tmp/busybox
rm busybox
/data/local/tmp/busybox rm `/data/local/tmp/busybox find -follow -maxdepth 1 -type l`
/data/local/tmp/busybox rm /data/local/tmp/*
exit
that second to last line gets rid of all the stray symlinks busybox left behind, not sure if CWM leaves any of those recovery/symlinks in sbin also or if those should be removed as well; perhaps someone else can fill us in on that point!
osm0sis said:
If you installed Superuser to system when you rooted then you'll need to remove that also but here are the basic adb commands for the job (make sure you have data and system mounted via CWM so you have access):
Code:
adb shell
rm /system/bin/su
mount -o remount,ro -t ext4 /dev/block/mmcblk0p1 /system
exit
BusyBox is another matter since CWM installs it to sbin every time you boot with it. Perhaps someone has a better idea (?), but from messing around a bit the other night the best method I've come up with is to use BusyBox to remove BusyBox, as follows:
Code:
adb shell
cd /sbin
cp busybox /data/local/tmp/busybox
chmod 06755 /data/local/tmp/busybox
rm busybox
/data/local/tmp/busybox rm `/data/local/tmp/busybox find -follow -maxdepth 1 -type l`
/data/local/tmp/busybox rm /data/local/tmp/*
exit
that second to last line gets rid of all the stray symlinks busybox left behind, not sure if CWM leaves any of those recovery/symlinks in sbin also or if those should be removed as well; perhaps someone else can fill us in on that point!
Click to expand...
Click to collapse
So flashing a Google factory image won't remove root? Or it will, but won't remove all evidence if someone went searching around trying to deny warranty.
When I rooted, I used the method of flashing recovery, then installed the su.zip via recovery. When I unrooted I simply flashed a factory image.
when you say installed superuser to system I'm guessing you mean something more advanced than the typical root process, correct?
Sent from my Galaxy Nexus using XDA
thos25 said:
So flashing a Google factory image won't remove root? Or it will, but won't remove all evidence if someone went searching around trying to deny warranty.
When I rooted, I used the method of flashing recovery, then installed the su.zip via recovery. When I unrooted I simply flashed a factory image.
when you say installed superuser to system I'm guessing you mean something more advanced than the typical root process, correct?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Flashing the factory system image DOES remove root (and busybox and anything else you changed on the ROM).There is no need to do anything that osm0sis said to do.
And there is no "more advanced" process of rooting. Root is two files placed on you system: /system/bin/su and /system/app/Superuser.apk. Nothing more. (Whether you place them there yourself, or have CWM do it for you, is irrelevant.) Remove those those and root is gone.
Sent from my Galaxy Nexus using Tapatalk 2
if you grab wugfresh's toolkit itll do all of that with one-click convenience. thats what I do to un-root my Nexus.
Zbraptorsdr said:
if you grab wugfresh's toolkit itll do all of that with one-click convenience. thats what I do to un-root my Nexus.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=21936493
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Flashing the factory system image DOES remove root (and busybox and anything else you changed on the ROM).There is no need to do anything that osm0sis said to do.
Click to expand...
Click to collapse
Right, I was referring to "unroot"ing without reflashing the system.img, since my intent with that method was to keep all settings, etc. as-is, just remove all traces of root.
osm0sis said:
Right, I was referring to "unroot"ing without reflashing the system.img, since my intent with that method was to keep all settings, etc. as-is, just remove all traces of root.
Click to expand...
Click to collapse
Yup, you would need to remove it manually if you were running a custom ROM, but with a stock ROM, flashing the system partition only WOULD leave all your data/settings as is.
osm0sis said:
BusyBox is another matter since CWM installs it to sbin every time you boot with it.
Click to expand...
Click to collapse
IS this true? Can someone confirm? And is it true for all phones?
Zbraptorsdr said:
if you grab wugfresh's toolkit itll do all of that with one-click convenience. thats what I do to un-root my Nexus.
Click to expand...
Click to collapse
The easiest way to do it, just click and its does it on its own.
The-Droidster said:
IS this true? Can someone confirm? And is it true for all phones?
Click to expand...
Click to collapse
Just wanted to clear this up now that I'm a bit more wise on the subject. The sbin stuff doesn't matter since it's all part of the ramdisk, and gets generated on each boot (to recovery or OS) and otherwise doesn't exist. No need to delete anything but su. :good:
osm0sis said:
Just wanted to clear this up now that I'm a bit more wise on the subject. The sbin stuff doesn't matter since it's all part of the ramdisk, and gets generated on each boot (to recovery or OS) and otherwise doesn't exist. No need to delete anything but su. :good:
Click to expand...
Click to collapse
he means, of course, "su" as in /system/bin/su AND /system/app/Superuser.apk. partially correct, i think, ramdisk is only used for early OS boot. Ramdisk + kernel = boot.img.
Recovery is on a different partition, for starters, and AFAIK, deploys needed files to a temporary location on the phone's ram or in the file system, which would be the recovery partition. Busybox gets placed in there as well.
Sent from my i9250
stock kernel has a ramdisk but not all kernels are packaged with one. recovery also has a ramdisk, just as it also has a kernel. Decompile/split/unzip one some time and you'll see /sys/ and /proc/ and /sbin/ all get generated from the ramdisk. And yes, if you for some reason put Superuser.apk or SuperSU.apk in /system/app/ (a completely unnecessary step), then naturally they need to go too.

Messed up build.prop, phone won't boot, can I push build.prop via adb?

My phone is on 4.1.2 still, and I had edited the build.prop to not update to 4.2 (after hearing all the problems). Now that 4.2.2. is out i decided to update, I tried restoring the build.prop file that i had as a backup of 4.1.2. I guess I must've changed some text without realizing.
Now my phone is stuck, it gives me the Google Logo with the unlocked sign, and then it disappears...and where there should be a boot animation...black. Nothing. Stays like that.
Any way I can push the build.prop via the computer using abd or something?
Not sure if adb will push to system, since i had an issue pulling from system.
Are you rooted?
You could try booting to recovery to enable adb, then remount system as r/w
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cd /system/ NOT SURE IF THIS IS REQUIRED, I'D TRY IT FIRST WITHOUT THIS LINE TO SEE
chmod 644 build.prop
chown root.root build.prop
exit
I've never had to do that, but i belive my linux syntax is correct, i pulled it from http://www.linux.org/article/view/file-permissions-chown. This is only of course if the build.prop failed bc on the incorrect permissions and ownership(maybe you had it on your sdcard). If this doesn't work, it looks like you'll be fastboot flashing a system image. [Sometimes the time and date of your build.prop may affect the ability to ota even if you get it to boot, to which you would need to reflash the system image anyway]. But i'd like to know if you try this and it works.
So what I ended up doing was installing clockwork recovery and then installing an odexed Rom version of the stock image of 4.1.2. Everything works, nothing got wiped.
Sent from my GT-N7100 using xda app-developers app
bodh said:
Not sure if adb will push to system, since i had an issue pulling from system.
Are you rooted?
You could try booting to recovery to enable adb, then remount system as r/w
adb shell
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
cd /system/ NOT SURE IF THIS IS REQUIRED, I'D TRY IT FIRST WITHOUT THIS LINE TO SEE
chmod 644 build.prop
chown root.root build.prop
exit
I've never had to do that, but i belive my linux syntax is correct, i pulled it from http://www.linux.org/article/view/file-permissions-chown. This is only of course if the build.prop failed bc on the incorrect permissions and ownership(maybe you had it on your sdcard). If this doesn't work, it looks like you'll be fastboot flashing a system image. [Sometimes the time and date of your build.prop may affect the ability to ota even if you get it to boot, to which you would need to reflash the system image anyway]. But i'd like to know if you try this and it works.
Click to expand...
Click to collapse
Yes, you need to 'cd /system' before typing the commands to change permissions and ownership, as you have them.
Sent from my Nexus
ksc6000 said:
So what I ended up doing was installing clockwork recovery and then installing an odexed Rom version of the stock image of 4.1.2. Everything works, nothing got wiped.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
How did you install clockwork recovery when it was not booting at all ??! Could you please guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Claureid said:
How did you install clockwork recovery when it was not booting at all ??! Could you please guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Click to expand...
Click to collapse
Then you should go to your own forums, as 99% of the info here wont do you any good
Claureid said:
How did you install clockwork recovery when it was not booting at all ??! Could you pbootlease guide me ? I actually have an LG Optimus G stuck in boot loop ..... (T_T)
Click to expand...
Click to collapse
I don't think you can do that with your phone what I did. But here is the gu ide that I used to temporarily boot into clockwork recovery to use it:
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
ksc6000 said:
I don't think you can do that with your phone what I did. But here is the gu ide that I used to temporarily boot into clockwork recovery to use it:
http://forum.xda-developers.com/showpost.php?p=23229578&postcount=3
Click to expand...
Click to collapse
Thanked you buddy !!

[Q] Rooting does not work 100% fine

Hello.
I have rooted my phone using
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
(in short, it's using SuperSU 2.00)
After some efforts, Root Checker says i am fine. I can get id 0 from adb, and via ssh.
But ... Busybox fails to install.
And if I remount /system RW, and mess in there a bit (like mkdir /system/tmp ), the mess is removed after reboot. Changes are not permanent.
Must I change my su app for superuser mentionned in the FAQ of the section (via recovery) ? Are there things to do before this migration ?
Other possible issues ?
I am used to fully unlocked HTC Sensation, where I changes to /system are easily permanent. But it was done using an exploit, few before HTC allowed rooting officially. Rooted M8 does not seem as much friendly ...
I *really* need busybox to work, and make permanent changes to /system. I am stuck.
Thanks.
doublehp said:
Hello.
I have rooted my phone using
http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/
(in short, it's using SuperSU 2.00)
After some efforts, Root Checker says i am fine. I can get id 0 from adb, and via ssh.
But ... Busybox fails to install.
And if I remount /system RW, and mess in there a bit (like mkdir /system/tmp ), the mess is removed after reboot. Changes are not permanent.
Must I change my su app for superuser mentionned in the FAQ of the section (via recovery) ? Are there things to do before this migration ?
Other possible issues ?
I am used to fully unlocked HTC Sensation, where I changes to /system are easily permanent. But it was done using an exploit, few before HTC allowed rooting officially. Rooted M8 does not seem as much friendly ...
I *really* need busybox to work, and make permanent changes to /system. I am stuck.
Thanks.
Click to expand...
Click to collapse
The /system partition is write protected on stock, meaning you can't add, modify, or delete files there. To disable this, you need to flash a kernel or rom with this disabled. Pretty much all sense based roms/kernels will state this in the features. I believe S-Off also disables it if you want to go the extra mile.
PS: Write protection is disabled in recovery. That is why superuser/root could be installed there.
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
akitten007 said:
The /system partition is write protected on stock, meaning you can't add, modify, or delete files there. To disable this, you need to flash a kernel or rom with this disabled. Pretty much all sense based roms/kernels will state this in the features. I believe S-Off also disables it if you want to go the extra mile.
PS: Write protection is disabled in recovery. That is why superuser/root could be installed there.
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
Click to expand...
Click to collapse
So, is there a way to install busybox via recovery ?
I did 3 things in recovery: all in /system/xbin
- chmod +s su
- touch t
- mkdir tmp
after reboot to normal mode, SUID bit was removed, but t and tmp are still here.
So, how do I install busybox ?
New issue: /data has the nodev flag; is it possible to remove it ?
I did not found /dev/shm ; was it moved somewhere else ? Any other place for similar use ? (world write temp folder in RAM).
akitten007 said:
PPS: Here is the kernel I run (protection disabled): http://forum.xda-developers.com/showthread.php?t=2705613
Click to expand...
Click to collapse
If your kernel allows me to install busybox, can i backup my original kernel to restaure it afterwards ?
Can I install busybox manually via recovery+adb ? I don't have any dev suite, but a good linux station; so, I can unzip, list, copy, and so on ... if there is not too much work to do.
doublehp said:
If your kernel allows me to install busybox, can i backup my original kernel to restaure it afterwards ?
Can I install busybox manually via recovery+adb ? I don't have any dev suite, but a good linux station; so, I can unzip, list, copy, and so on ... if there is not too much work to do.
Click to expand...
Click to collapse
Now you're starting to go over my head. If you want to keep your current kernel, I would try using this method here to manually add the module that disables the protection http://forum.xda-developers.com/showthread.php?t=2702575. I usually just install busybox using rom toolbox or any other busybox app. You could search for a busybox zip, but just disabling the write protection is a better option in my opinion. And I have actually 0.00 idea what flags mean on folders (sorry).
I rooted using TWRP recovery and super su. That guide you posted gives unnecessary instructions. TWRP automatically installs the SU binary and Super su the first time you boot into it. I was able to update Super su via google play, no need for the update zip. Just follow the instructions after rebooting to system from TWRP recovery.
I'm s-off, unlocked, my kernel, firmware and os are stock, only thing that isn't is recovery. I have write access to system and external sd card. All I did was make it writable with root explorer and have installed busy box no problem using this app https://play.google.com/store/apps/details?id=stericson.busybox.
I was given a better fix.
http://forum.xda-developers.com/showthread.php?t=2701816
In short:
adb push /mnt/big/tmp/wp_mod_m8.ko /mnt/sdcard/Download/
insmod /mnt/sdcard/Download/wp_mod_m8.ko
mount -o remount,rw /system
cd /system
touch z
mkdir zz
reboot
[email protected]_m8:/storage/emulated/legacy # cd /system/
[email protected]_m8:/system # ls
app
bin
build.prop
customize
etc
fonts
framework
lib
lost+found
media
priv-app
tts
usr
vendor
xbin
z
zz
[email protected]_m8:/system #
The miror is on maintainance for now. So, the guy on IRC gave me his local backup. I will push it here for 30 days:
http://dl.free.fr/gSha53ljz
(server will delete it after 30d nobody downloads it)
Busybox still fails to install; don't know why.

[Mod][Systemless Root][Pixel/Pixel XL] TetherMod - Bypass provisioning checks.

This guide presupposes that you have Supersu installed as systemless, and that you have access to adb.
This will bypass provisioning checks for builtin tether app. The modded apk should work with future updates without touching /system at all.
Installation
Method 1 - Manual install
Download the attached CarrierEntitlement apk.
If you have su.img su:
Code:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
mkdir /su/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /su/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /su/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /su/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /su/su.d/05TetherMod
chmod +x /su/su.d/05TetherMod
reboot
If you have sbin su (Android 8.0+)
Code:
adb push CarrierEntitlement.apk /sdcard/CarrierEntitlement.apk
adb shell
su
mkdir /sbin/supersu/CarrierEntitlement
cp /sdcard/CarrierEntitlement.apk /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
chmod 644 /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk
echo "mount -o bind /sbin/supersu/CarrierEntitlement/CarrierEntitlement.apk /system/priv-app/CarrierEntitlement/CarrierEntitlement.apk" > /sbin/supersu/su.d/05TetherMod
chmod +x /sbin/supersu/su.d/05TetherMod
reboot
Method 2 - Flashable Zip (su.img only)
Code:
1. Download attached zip.
2. Flash in TWRP (Last tested in alpha 2)
Information
This mod is accomplished by replacing the following function:
Code:
.method public static getCarrierEntitlement(Landroid/content/Context;)Lcom/google/android/carrierentitlement/CarrierEntitlement;
.registers 2
.param p0, "context" # Landroid/content/Context;
.prologue
.line 56
const/4 v0, 0x0
return-object v0
.end method
NOTE: Post install
You may need to edit your APNs to get tethering working for your carrier.
On sprint, where editing APNs is disabled, the fix is here: Sprint Fix
Be sure to thank @Builtfordtough1 for all his help in diagnosing the issue at this post: The Solution!
Be sure to thank sb1893 for sbin su instructions.
Worked Perfectly
This worked perfectly. Fantastic job!
So I am on stock with unlocked bootloader, twrp installed, and rooted with SuperSU. Because this is an apk file, do i just download onto the phone and install as I would with any other .apk file?
coolhandz said:
So I am on stock with unlocked bootloader, twrp installed, and rooted with SuperSU. Because this is an apk file, do i just download onto the phone and install as I would with any other .apk file?
Click to expand...
Click to collapse
The directions clearly state in adb speak that you need to create a directory for the file. Move to said directory, change permissions, etc etc. Nothing about installing via the apk.
pcriz said:
The directions clearly state in adb speak that you need to create a directory for the file. Move to said directory, change permissions, etc etc. Nothing about installing via the apk.
Click to expand...
Click to collapse
well, i can follow basic commands in minimal adb & fastboot. I think this may be above me unless there is an idiots' guide.
coolhandz said:
well, i can follow basic commands in minimal adb & fastboot. I think this may be above me unless there is an idiots' guide.
Click to expand...
Click to collapse
Do you have access to adb? They are pretty straight forward. May need to view them on the website but if you are using an app it may throw the word wrap off and make the commands seem confusing. The directions are pretty word for word.
pcriz said:
Do you have access to adb? They are pretty straight forward. May need to view them actually on the website but if you are using an app it may throw the word wrap off and make the commands seem confusing. The directs are pretty word for word.
Click to expand...
Click to collapse
If by adb you mean minimal adb & fastboot, then yes I have access and I could probably brave it.
coolhandz said:
If by adb you mean minimal adb & fastboot, then yes I have access and I could probably brave it.
Click to expand...
Click to collapse
I wouldn't suggest doing it how I did it but I downloaded the file to my phone. I created the directory using a root enabled file browser (see mkdir command {make directory}). I even used the file properties option in solid explorer to change the permissions (see chmod 644). Every other command I did on the phone from a terminal emulator. Just had to ignore the adb shell command because I am actually doing them on the device and not through a shell on my computer.
pcriz said:
I wouldn't suggest doing it how I did it but I downloaded the file to my phone. I created the directory using a root enabled file browser (see mkdir command {make directory}). I even used the file properties option in solid explorer to change the permissions (see chmod 644). Every other command I did on the phone from a terminal emulator. Just had to ignore the adb shell command because I am actually doing them on the device and not through a shell on my computer.
Click to expand...
Click to collapse
yeah, all that is definitely outside of my comfort zone, but thank you for the info.
Can you normally update your device with OTA-updates like a un-rooted device, without flashfire or connect to your computer?
Is there an advantage to doing this over adding "net.tethering.noprovisioning=true" to the build.prop file?
airmaxx23 said:
Is there an advantage to doing this over adding "net.tethering.noprovisioning=true" to the build.prop file?
Click to expand...
Click to collapse
This mod is systemless, and should survive OTAs. That mod changes the build.prop on the system partition, which could prevent taking OTAs.
njeri123 said:
Can you normally update your device with OTA-updates like a un-rooted device, without flashfire or connect to your computer?
Click to expand...
Click to collapse
Any modification to the boot image *should* prevent OTAs from working at all. However, you can flash back to stock boot images, and take OTAs as long as you have not modified /system, which this mod does not do.
Furthermore, as long as you don't wipe /data/ this mod will live in su.img and survive when you flash newer system software.
Fenny said:
This mod is systemless, and should survive OTAs. That mod changes the build.prop on the system partition, which could prevent taking OTAs.
Any modification to the boot image *should* prevent OTAs from working at all. However, you can flash back to stock boot images, and take OTAs as long as you have not modified /system, which this mod does not do.
Furthermore, as long as you don't wipe /data/ this mod will live in su.img and survive when you flash newer system software.
Click to expand...
Click to collapse
Thanks for the explanation, I removed the build.prop line and used this method and it's working fine. Thank you.
@Fenny
Thank you so much for putting this into a .zip file. It is greatly appreciated!
is there a non root method to bypass the checks? i dont plan on unlocking or rooting since i use android pay...
ddarvish said:
is there a non root method to bypass the checks? i dont plan on unlocking or rooting since i use android pay...
Click to expand...
Click to collapse
I also use Android pay, so I have two boot images ready to fastboot or flash. I have a boot image with root, and a boot image without root running a kernel that hides the bootloader unlocked flag.
So, the way I handle this, I flash the unrooted (bootloader flag hidden) image as my daily driver kernel, this passes safetynet, and allows me to use Android pay.
I make a backup of that boot image. Then, I install TWRP, my custom kernel, and SuperSU. I make a backup of that image as well.
So I have two backed up boot images:
rooted.img
HideBLUnlock.img
I flash HideBLUnlock.img to boot a, and boot b, safetynet passes.
Whenever I need to tether I have my computer with me, so I "fastboot boot rooted.img" which leaves me rooted until my next reboot.
Depending on your usage you might want to reverse that.
All my mods get stored in su.img, so switching out the boot images is all I need to have the best of both worlds.
Is it possible to fastboot boot twrp and flash the zip without being rooted or having twrp actually installed? O unlocked my bootloader but that's been it
Ocelot13 said:
Is it possible to fastboot boot twrp and flash the zip without being rooted or having twrp actually installed? O unlocked my bootloader but that's been it
Click to expand...
Click to collapse
You can use the fastboot twrp image to install this mod but you MUST have SuperSu. I have basic validation to check that in my update.zip. If you don't have a su.img in /cache or /data, this mod cannot be installed.
Flashed via TWRP and now i finally have a fully functioning hotspot!!
Fenny said:
I also use Android pay, so I have two boot images ready to fastboot or flash. I have a boot image with root, and a boot image without root running a kernel that hides the bootloader unlocked flag.
So, the way I handle this, I flash the unrooted (bootloader flag hidden) image as my daily driver kernel, this passes safetynet, and allows me to use Android pay.
I make a backup of that boot image. Then, I install TWRP, my custom kernel, and SuperSU. I make a backup of that image as well.
So I have two backed up boot images:
rooted.img
HideBLUnlock.img
I flash HideBLUnlock.img to boot a, and boot b, safetynet passes.
Whenever I need to tether I have my computer with me, so I "fastboot boot rooted.img" which leaves me rooted until my next reboot.
Depending on your usage you might want to reverse that.
All my mods get stored in su.img, so switching out the boot images is all I need to have the best of both worlds.
Click to expand...
Click to collapse
This is facinating, do you ever think where we can use boot a and boot b in a multiboot like fashion so that when you turn on the device you can choose what to boot?

Can not mount /system rw?

Hi everyone I'm trying to make a Tasker task to delete some apps which included in LOS after build update but Tasker or built-in terminal can't mount /system rw ( tried command "mount -o rw,remount /system" command causes no errors or anything but still system is ro ) but apps like Root Explorer can mount it using LOS 15.1 on Xiaomi Mi6 with Magisk v17.1 thanks in advance and sorry for my terrible English :/
Are there any hope for this? For now, my device has only the LOS recovery and so I can't flash a zip. Is there a way to mount /. Set the selinux to moderat didn't do the trick?
Any ideas?
Micha_Btz said:
Are there any hope for this? For now, my device has only the LOS recovery and so I can flash a zip. Is there a way to mount /. Set the selinux to moderat didn't do the trick?
Any ideas?
Click to expand...
Click to collapse
I solved my issue with making a flashable zip for delete apps etc. So, i didn't tried again to mount system RW
A little spelling mistake by me. I can't flash a zip for now.
Micha_Btz said:
A little spelling mistake by me. I can't flash a zip for now.
Click to expand...
Click to collapse
I assume u r using Mi6 right? Did you tried another recovery like THIS?
No, I use a BQ Aquaris X2 Pro
Micha_Btz said:
No, I use a BQ Aquaris X2 Pro
Click to expand...
Click to collapse
Oh, sorry man I couldn't find TWRP for your device. But its must be recovery related so try to find another TWRP besides yours, good luck.
For all that looking for a solution:
enable root for adb
and then
adb root
adb disable-verity
now you can reboot and can remount /
Micha_Btz said:
For all that looking for a solution:
enable root for adb
and then
adb root
adb disable-verity
now you can reboot and can remount /
Click to expand...
Click to collapse
Thanks very much for posting this. Could you explain what this is supposed to do? Is there something that changed in the filesystem structure in Android 8.x that makes `/system` not mountable as an independent partition?
Although your instructions work (I can see that `adb disable-verity` persists across reboots), I still can't do `mount -o remount,rw /` afterwards. I get an error telling me that "device /dev/root[/code] is read-only". Hrm.
Are you sure you did the disable-verity command as root? There should be an answer from adb that is really been disabled.
https://source.android.com/security/verifiedboot/dm-verity

Categories

Resources