Can anyone help to make change to the read-only file system? - Magisk

I have a pixel 2 (walleye) running the latest stock android that has been successfully rooted by Magisk. Everything works as expected so far.
I however need to make some changes to the "vendor/mbn/mcfg/configs/mcfg_sw/generic" directory, but I am being denied for the "read-only" file system error.
I did some research and unticked the "preserve AVB 2.0/dm-verity" option under Magisk, but using ghost-command file manager in root mode, it still denies my modification to the said directory with the "read-only file system" error.
Can anyone help with the situation?

bonedriven said:
I have a pixel 2 (walleye) running the latest stock android that has been successfully rooted by Magisk. Everything works as expected so far.
I however need to make some changes to the "vendor/mbn/mcfg/configs/mcfg_sw/generic" directory, but I am being denied for the "read-only" file system error.
I did some research and unticked the "preserve AVB 2.0/dm-verity" option under Magisk, but using ghost-command file manager in root mode, it still denies my modification to the said directory with the "read-only file system" error.
Can anyone help with the situation?
Click to expand...
Click to collapse
Are you trying to edit on root / directly? If so, probably this is the point.
This may help you:
https://github.com/topjohnwu/Magisk/blob/master/docs/details.md#file-structure

wilsonhlacerda said:
Are you trying to edit on root / directly? If so, probably this is the point.
This may help you:
https://github.com/topjohnwu/Magisk/blob/master/docs/details.md#file-structure
Click to expand...
Click to collapse
Not sure where to start but I see "If you want to replace files in /vendor, please place it under $MODPATH/system/vendor. Magisk will transparently handle both cases, whether vendor is a separate partition or not."
Thank you for the suggestion.
I finally solved the problem by simply doing "mount -o rw,remount /vendor"

bonedriven said:
Not sure where to start but I see "If you want to replace files in /vendor, please place it under $MODPATH/system/vendor. Magisk will transparently handle both cases, whether vendor is a separate partition or not."
Thank you for the suggestion.
I finally solved the problem by simply doing "mount -o rw,remount /vendor"
Click to expand...
Click to collapse
For clarification: that's information for if you are making Magisk Modules. If you don't want to do systemless modifications you're naturally going to have to mount the partitions read-write.

bonedriven said:
I have a pixel 2 (walleye) running the latest stock android that has been successfully rooted by Magisk. Everything works as expected so far.
I however need to make some changes to the "vendor/mbn/mcfg/configs/mcfg_sw/generic" directory, but I am being denied for the "read-only" file system error.
I did some research and unticked the "preserve AVB 2.0/dm-verity" option under Magisk, but using ghost-command file manager in root mode, it still denies my modification to the said directory with the "read-only file system" error.
Can anyone help with the situation?
Click to expand...
Click to collapse
Here is the solution to your problem my friend. Enjoy!
Works like a charm in Android 10 and later. Now my system, vendor and product partitions are read-write!
Use at your own risk!
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Related

[Q] [DEV] Can someone DUMP P500 Baltic system.img

Hi, Can someone please dump/backup the system.img from baltic P500 or have a offical update for baltics. Thanks
Just do a backup and upload it. Thanks
No one here from Baltic States?
Hey, just show me how to do it, and I will give you.
hi, please use this guide: http://forum.xda-developers.com/showpost.php?p=8917870&postcount=12
or if you have Thunderg installed, then just do a backup and upload these files.
thanks
Hmm, could you be more specific? I just bought this Optimus One like two days ago, and I'm feeling very newb (it's my first Android).
What do I have to do, to give you that system.img and what is that system.img file?
Hi, the system.img a backup from Android /system partition is a main part of the android. But this guide we just dump that /system partition, it's the easiest way.
I'll try to help you do that:
1. Is your phone rooted?
If you haven't done that, then use Z4Root(super easy app ) and you can get it from here: http://www.upload.ee/files/997919/z4root.1.3.0.apk.html
Download that file and copy to sd card and install.
Open that installed app and root your phone
If you need help with that, then there is little how to here: http://www.worldofnubcraft.com/285/rooting-a-lg-optimus-one-android-phone
2. OK, rooting done, now we need terminal app: You'll find that from Market. Just search "Android Terminal Emulator" it's from Jack Palevich and install that.
3. Now open the Terminal Emulator and enter these commands without "" and hit enter after command, these 3 command should be it:
"su" it asks for a root privileges and you allow that
"cd /system"
"tar zcvf /sdcard/system-dump.tar.gz *" and wait when it finishes. it takes some time. It's done when you see #, it takes couple of minutes max.
4. That file is now on your phone SD card and upload that system-dump.tar.gz file to somewhere and let me know
Are you sure about that?
I'm sorry, but it's not working. It gives me an error "tar not found". Any ideas?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By the way, what you can do with that file? What it contains? I'm just a newb, and I want to know everything about Android.
EDIT:
Is it possible to do that dump with Thunderg?
Go to market and install app called "BusyBox" and download / install BusyBox with this tool. After that it will work.
yes, i forgot busybox install that and give a new try
Ok guys, I got it. Before putting it live, I would like to know one thing. Does it contains any personal data, if so, what exactly? Sorry, for being so paranoid.
hi, it won't contain any of your personal data. Personal data is stored mostly on /Data partition and we didn't dump that. Thanks
Ok, so here you have it.
Optimus_One_Baltic_ROM_dump.zip - 89.2 Mb
And it's only contains branded ROM with no changes? That's great. What program do I need to restore my ROM to the branded one, if I'm going later to change it?
i think you should look to Thunderg... it's best way to make a full backup and restore after

[Q] flashing /sbin

I have to mod some files in /sbin without root before i can root my phone, since it's currently only booting to cwm without working 'adb root', and since it has got at least one corrupt filesystem.
I've tried searching the mounted filesystems of factoryfs.rfs etc, but without success. Where is it?
Would it be possible to update a non-/system directory through an update.zip file? As said, I currently do not have root.
What exactly are you looking for?
I don't really understand your problem.
What ROM are you on right now.
How come you have CWM but not root?
This should it i hope
Joel Sjögren said:
I have to mod some files in /sbin without root before i can root my phone, since it's currently only booting to cwm without working 'adb root', and since it has got at least one corrupt filesystem.
I've tried searching the mounted filesystems of factoryfs.rfs etc, but without success. Where is it?
Would it be possible to update a non-/system directory through an update.zip file? As said, I currently do not have root.
Click to expand...
Click to collapse
Try the following :
Samsung Galaxy S I9000 Custom ROM List
http://forum.xda-developers.com/showthread.php?t=886000
How to root
http://forum.xda-developers.com/showthread.php?t=723596
U need a tool called "ODIN" to root and install most roms
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit : u could also see the videos if u want to here r a few :
http://www.youtube.com/user/TheAndro.../1/ssflhnyzeYc
http://www.youtube.com/watch?v=LjBEBvRVRYs
http://www.youtube.com/watch?v=2O8KT...eature=related
"What ROM are you on right now.
How come you have CWM but not root?"
I'm currently using XXJP3 without the /media and /app directories(I mounted the factoryfs.rfs on my computer and moved them elsewhere.)
adb root has worked for me earlier, but suddenly, it stopped. Instead i get the
error: device not found
error when issuing adb shell after adb root.
The problem is, I cannot install root or anything else yet because my /system(stl9) partition does not act the way it should.
No factoryfs containing /media and /app can be flashed. I've tried the --repartition flag(with correct .pit-file.)
To work around it, I'm trying to edit a script, located in /sbin, to be run at boot. The script will hopefully allow me to fix the partition with root privileges. In either case, it will be able to write the output to a log file to be read through $-adb shell.
The /sbin boot script would also allow me to use the external sd instead of the internal memory in case the stl9 partition somehow cannot be fixed.
As rooting is no option yet, I need to flash the /sbin directory, but since I can't find it in the rom, I need your help here.

[Q] OTA fails at hosts check, how can I restore stock hosts file?

Hi everyone:
I'm trying to install the 3.09.661.1 System update (Stock) on my phone.
Every time I try to install it, it fails (red exclamation mark) when verifying my Hosts file. I had modified the hosts file a long time ago to attempt to block ads and it isn't liking the fact that the file is modified, I'm gathering.
Here's the exact error:
Code:
Warning: No file_contextsVerifying current system...
assert failed: apply_patch_check("/system/etc/hosts". "e4a6ce6d4ee32b7de4dfe23e6e82d9ea1c122b20
", "d234177b0b9de5309f78ff539e5eafea00e069df")
Installation aborted.
To combat this, I re-rooted the phone and modified the hosts file to restore it to the original... I think. I used ROM Toolbox Pro and told it to turn off ad blocking and now my Hosts file looks like this:
Code:
127.0.0.1 localhost
127.0.0.1 localhost.localdomain
255.255.255.255 broadcasthost
0.0.0.0 local
Before the "restore" there was mention of IPv6 though, so I'm not sure this is actually the default.
I have old CWM recovery backups of previous clean installs, but I'm not sure if the Hosts file would be included anywhere in there.
If anyone could give me some insight on a way I could install this OTA update without having to lose my information and wipe, I'd very much appreciate it!
Perhaps someone could post their unmodified Hosts file for me to try?
Also, it seems like 3.09.661.1 is one of the newer versions, would anyone like me to post the OTA update file? (Note: I only have it in the original .zip.21363.enc format, not knowing how to convert it to a "normal" ZIP file.)
EDIT (08/26/2013):
How I was able to update:
I was able to pull the original Hosts file from an old CWM backup file--it is stored in the system.ext4.tar file. I use Root Explorer to change the read/write settings on my Hosts file (on the device) then pushed the old Hosts file using ADB. When I tried to do the OTA update again, it worked, and now my device is running:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not sure what that's all about (could be test software), but it's at least 4.2 since I have the quick toggles in the notification drop-down now.
Downside to the update: It deleted all of the contents of my "SD," so all of my photos and music, etc. was lost... Rather annoying and not normal OTA behaviour, in my previous experience. Going to see if there's a way to recover them, but I don't hold out much hope.

Is my device rooted?

I would like to pose a simple question: How can I check if my Nexus 6 is rooted or not? Is there something that can betray it?
liakuras said:
I would like to pose a simple question: How can I check if my Nexus 6 is rooted or not? Is there something that can betray it?
Click to expand...
Click to collapse
easiest way.. download a terminal emulator app, open it, then type in su(press enter). if it then shows a #, then you have root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
I installed "terminal emulator for android" and it said:
[email protected]:/ $ su
/system/bin/sh: su: not found
127|[email protected]:/ $
What does this mean?
liakuras said:
I installed "terminal emulator for android" and it said:
[email protected]:/ $ su
/system/bin/sh: su: not found
127|[email protected]:/ $
What does this mean?
Click to expand...
Click to collapse
no root. did you flash supersu? do you have the supersu app installed? btw, just so that you know, su means superuser, which means root.
No I have not ever installed such things. Just once, I accidentally deleted some photos and I would like to recover them back and I used a freeware programme at my windows PC which gave me temporary root access, but I was unable to recover them and I cancelled the whole process. And therefore, I didn't know if I was rooted or not.
The problem is that I can not install the latest security patch/fix and I assumed I was rooted....
liakuras said:
No I have not ever installed such things. Just once, I accidentally deleted some photos and I would like to recover them back and I used a freeware programme at my windows PC which gave me temporary root access, but I was unable to recover them and I cancelled the whole process. And therefore, I didn't know if I was rooted or not.
The problem is that I can not install the latest security patch/fix and I assumed I was rooted....
Click to expand...
Click to collapse
The program may have modified your system files. Once modified the OTA won't run. Would have to reflash stock.
If I just perform a factory reset?
liakuras said:
If I just perform a factory reset?
Click to expand...
Click to collapse
Won't fix it if system files have been modified. Factory reset only clears cache and data. Does not touch system files. Have to fastboot flash the factory system image file.

[O][P]Unoficial TWRP 3.4.0 & Root

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.4.0 & Root
Root and absolutely working TWRP 3.4.0 from nemo-nemo!
Oreo & Pie​
Features
In the new TWRP and Root installation method described below, there is no need to format the Data partition to remove the encryption.
Thanks to TWRP's built-in FB Encryption (File Based Encryption), the contents of the Data partition are available with encryption preserved. The folders on the external memory have the correct names and structure.
- Forced DM-Verity removal
- Forcibly removing the protection of Motorola Hab
- Now there is no need to sew additional decoders when installing TWRP and receiving Root or when installing custom firmware!
- Full access to Oem partition modification directly from the running system using Root Explorer, which previously was only possible with Root obtained through SuperSu.
Installation Instruction
1. Download archive with files for installation TWRP and Magisk Google Drive
2. Extract files:
- twrp-3.4.0-nash-nemo-nemo.img to the folder adb with drivers adb & fastboot ;
- twrp-installer-3.4.0-nash-nemo-nemo.zip, Magisk-disable-dm-verity-v20.4.zip to the SD Card..
This is a special modification of Magisk for Motorola devices. You can read about it here Link
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot boot C:\adb\twrp-3.4.0-nash-nemo-nemo.img
4. The phone restart in to Recovery.
5. Go to the "Install" section. Click on "Select Storage" button, select Micro SD card, OK. Install twrp-installer-3.4.0-nash-nemo-nemo.zip and Magisk-disable-dm-verity-v20.4.zip.
6. Reboot into the system.
Attention! Backup creation after TWRP and Magisk installation should be done only after full booting into the system. Otherwise restoration of the Data partition backup will be interrupted with an Error 255.
Сredits:
nemo-nemo
TeamWin-TWRP
ilia3367
Thanks a lot, everything works fine. The only issue I had was the russian language on the first boot in TWRP, but it is easy change to english.
forgottennick said:
Thanks a lot, everything works fine. The only issue I had was the russian language on the first boot in TWRP, but it is easy change to english.
Click to expand...
Click to collapse
Well, this is understandable. This TWRP was created by 4PDA developers.
do I have to flash Magisk-disable-dm-verity whenever I want to install a custom rom?
If you need a Root then of course yes.
Very good, works, thanks!
Will this method work for the Verizon version of the Z2 Force?
ilia3367 said:
If you need a Root then of course yes.
Click to expand...
Click to collapse
Willi this work on the Verizon Z2 Force?
will4958 said:
Willi this work on the Verizon Z2 Force?
Click to expand...
Click to collapse
Verizon and Root concepts are not compatible.
hey, im getting a bootloop when trying this. no idea why?

Categories

Resources