На экране Samsung J1 — keep system read only twrp что делать?
keep system read only twrp что делать?
В чем проблема мне не известно, племянник что-то накрутил, сам не знает что. Пытался сбросить настройки, но в итоге скорее всего пытался перепрошить.
На экране телефона
keep system read only?
Проблема на изображена фотографии
Что сделать чтобы заработал телефон Samsung J1?
Голосование за лучший ответ
Если ты сделаешь свайп, то раздел /system будет монтироваться как rw(read-write)(Чтение-запись)
Если ты ткнешь на кнопку, то этот же раздел будет монтироваться как ro(read-only)(Только чтение)
Это он установил рекваери всего лишь. Поставь галочку и сделай свайп
Похожие вопросы
TWRP, can’t uncheck «Mount system partition read-only»
I installed this Twrp on my Samsung a40 using Heimdall, worked well but I can’t uncheck the option «Mount system partition read-only» in Mount. So, I can’t flash Magisk, it fails to mount /system. I get the following error «unable to find partition for path /system» when I try to write to the /system. Any ideas, how I can fix it ?
asked Apr 5, 2020 at 9:50
11 2 2 bronze badges
try mount -r /system_root from twrp terminal. magisk error is most likely not related to read-only problem because it is systemless root method. unable to find partition error is maybe caused by wrong recovery.fstab. claim it to TWRP maintainer or unpack twrp.img and fix yourself. in twrp terminal, type ls -1 $(find /dev/block -name by-name)/* use this paths for /etc/recovery.fstab (or twrp.fstab if exist)
Apr 5, 2020 at 10:06
0
You must log in to answer this question.
- samsung
- twrp
- lineageos
- magisk
-
The Overflow Blog
Related
Hot Network Questions
Subscribe to RSS
Question feed
To subscribe to this RSS feed, copy and paste this URL into your RSS reader.
Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.10.27.43697
The Android robot logo is a trademark of Google Inc. Android is a trademark of Google Inc.
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
Все в порядке, но.
Этот текст мало кто будет читать и мы можем написать здесь все, что угодно, например.
Вы живете в неведении. Роботы уже вторглись в нашу жизнь и быстро захватывают мир, но мы встали на светлый путь и боремся за выживание человечества. А если серьезно, то.
В целях обеспечения безопасности сайта от кибератак нам необходимо убедиться, что вы человек. Если данная страница выводится вам часто, есть вероятность, что ваш компьютер заражен или вы используете для доступа IP адрес зараженных компьютеров.
Если это ваш частный компьютер и вы пытаетесь зайти на сайт, например, из дома — мы рекомендуем вам проверить ваш компьютер на наличие вирусов.
Если вы пытаетесь зайти на сайт, например, с работы или открытых сетей — вам необходимо обратиться с системному администратору и сообщить, что о возможном заражении компьютеров в вашей сети.
- © 2005-2023, «4PDA». 4PDA® — зарегистрированный товарный знак.
Read only file system on Android
I recently rooted my Droid X and everything seems to be working perfectly. I made some changes to build.prop and when I do adb push build.prop /system/ I get the following error: failed to copy ‘c:\build.prop’ to ‘/system//build.prop’: Read-only file system . How can I fix this?
5,993 14 14 gold badges 31 31 silver badges 58 58 bronze badges
asked May 19, 2011 at 23:38
11.5k 16 16 gold badges 64 64 silver badges 116 116 bronze badges
have you tried adb remount , what do you get?
May 19, 2011 at 23:48
Android is Google’s software stack . For non-developer questions, see android.stackexchange.com
Dec 16, 2011 at 14:42
Please note that this question should not be confused with the case where Android Application code fails with a read-only file system error. That is usually caused by trying to write a file without specifying a location, ie, trying to write to the root directory. This question is only about modifying the installation of Android itself on rooted/development/engineering devices.
Apr 23, 2016 at 2:02
Is there a way to do this with an android emulator?? None of these solutions work for my emulator.
Dec 21, 2016 at 17:38
Just use adb shell mount -o rw,remount /sys (instead of /system). Works for me.
Oct 8, 2020 at 7:48
24 Answers 24
Not all phones and versions of android have things mounted the same.
Limiting options when remounting would be best.
Simply remount as rw (Read/Write):
# mount -o rw,remount /system Once you are done making changes, remount to ro (read-only):
# mount -o ro,remount /system answered Dec 16, 2011 at 13:10
CurtisLeeBolin CurtisLeeBolin
4,454 2 2 gold badges 13 13 silver badges 11 11 bronze badges
You can do this on your PC too. adb shell mount -o rw,remount /system
Jul 26, 2012 at 0:47
Use in conjunction with adb root or you’ll get a Permission Denied when pushing the file.
Aug 18, 2013 at 9:06
If I use adb root I get adbd cannot run as root in production builds
Jun 8, 2016 at 16:59
Doesn’t work for me: Balazss-MBP:tools varh1i$ adb shell generic_x86_64:/ # mount -o rw,remount /system ‘/dev/block/vda’ is read-only
Feb 8, 2017 at 13:58
It is not worked for me.It showed «mount: Read-only file system»
Aug 9, 2017 at 6:50
adb remount works for me and seems to be the simplest solution.
answered Apr 23, 2012 at 21:06
1,675 2 2 gold badges 13 13 silver badges 13 13 bronze badges
«adb remount — If you’ve gotten errors trying to push files to /system due to it being in read-only mode, adb remount will remount /system into read-write mode— provided that the shell has the correct root permissions to do so. This replaces having to type a longer command by hand such as mount -o rw,remount /system (as root) or something.» (source). If you have any issue with root permissions, try «adb root» before.
Feb 1, 2014 at 9:13
I’ve got Not running as root. Try «adb root» first. . And then adbd cannot run as root in production builds .
Aug 31, 2017 at 14:44
On newer devices it looks like we also need to $ adb disable-verity and then reboot the device before we can run $ adb remount
Dec 11, 2018 at 18:43
$ adb disable-verity give : disable-verity only works for userdebug builds
Jun 11, 2019 at 18:29
it doesn’t work: Not running as root. Try «adb root» first. . I entered adb root and then again adb remount but still the same error: Not running as root. Try «adb root» first.
Aug 7, 2019 at 11:20
While I know the question is about the real device, in case someone got here with a similar issue in the emulator, with whatever tools are the latest as of Feb, 2017, the emulator needs to be launched from the command line with:
-writable-system For anything to be writable to the /system . Without this flag no combination of remount or mount will allow one to write to /system .
After the emulator is launched with that flag, a single adb remount after adb root is sufficient to get permissions to push to /system .
Here’s an example of the command line I use to run my emulator:
./emulator -writable-system -avd Nexus_5_API_25 -no-snapshot-load -qemu The value for the -avd flags comes from:
./emulator -list-avds answered Feb 16, 2017 at 16:53
12.6k 4 4 gold badges 34 34 silver badges 52 52 bronze badges
my command prompt becomes extremely slow until cannot continue with adb root and adb remount after launch emulator with -writable-system, anyone can help ?
May 17, 2018 at 1:20
Note that in some old kernel versions there is a bug in the ext4 driver that causes the remount to immediately revert to read-only. Check dmesg for error messages like «Inode table for bg 0 marked as needing zeroing». This is fixed by commit 8844618
Sep 2, 2021 at 1:21
What if I want to write to /product directory?
May 21, 2022 at 13:46
In case you are on windows, Right-click the Bluestacks icon on Desktop > Properties > Target (And add flags there)
Jan 7 at 1:13
Got this off an Android forum where I asked the same question. Hope this helps somebody else.
On a terminal emulator on the phone:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system Then on the cmd prompt, do the adb push
answered May 20, 2011 at 0:15
11.5k 16 16 gold badges 64 64 silver badges 116 116 bronze badges
adb shell
May 19, 2014 at 8:38
this comments results in mount: ‘/system’ not in /proc/mounts
Mar 5, 2021 at 3:07
@임정섭 I am also facing the same issue, did you find any solution? nothing is working for me. if I am doing adb remount, I am getting remount of the / superblock failed: Permission denied remount failed and with this answer, I am getting ‘/system’ not in /proc/mounts . Please help.
Sep 18, 2021 at 21:11
@HackRx I kind of gave up and found other proxy methods. Overall, what I wanted to was pushing some data to the phones and I did this by pushing to /data/local/ . Here didn’t raise permission error.
Sep 22, 2021 at 15:23
I think the safest way is remounting the /system as read-write, using:
mount -o remount,rw /system and when done, remount it as read-only:
mount -o remount,ro /system answered Dec 21, 2011 at 19:50
1,030 10 10 silver badges 7 7 bronze badges
Welcome to SO! Your answer is technically useful, but essentially a duplicate of curtlee2002’s prior answer. This might have been better as a comment on his answer saying «I agree it is safest to switch back to read-only after monkeying around in read-write mode.» We have millions of questions, so there will always be another question where you are the first to come with a great solution or a fresh perspective!
Dec 21, 2011 at 20:09
this only worked for me once I removed the «,» from the statement. i.e. «» mount -o remount rw /system «»
Apr 6, 2013 at 18:51
@TechnikEmpire, he does not refer to the accepted answer.
Oct 26, 2015 at 13:20
adb disable-verity adb reboot adb root adb remount This works for me, and is the simplest solution.
answered Jul 25, 2018 at 0:12
byInduction byInduction
405 1 1 gold badge 6 6 silver badges 13 13 bronze badges
adb disable-verity — this was the key solution in my case.
Jul 15, 2020 at 14:41
verity cannot be disabled/enabled — USER build
Apr 26, 2022 at 22:10
This is the right answer. I just had to push «adb root» as the very first command, otherwise I’m getting «Error getting verity state. Try adb root first? Overlayfs setup failed with error Permission denied Maybe run adb root?» on Android Emulator SDK 29.
May 31 at 13:17
On my Samsung galaxy mini S5570 (after got root on cellphone):
Fist, as root, I ran:
systemctl start adb as a normal user:
adb shell su Grant root permissions on touch screen
mount list all mount points that we have and we can see, in my case, that /dev/stl12 was mounted on /system as ro (ready only), so we just need do:
mount -o rw,remount /dev/stl12 /system answered Feb 4, 2013 at 0:37
6,975 1 1 gold badge 48 48 silver badges 53 53 bronze badges
Thank you for this answer. For some reason I never looked at the screen on my phone to grant root permissions and was getting access denied no matter what I tried.
May 10, 2013 at 3:18
saying «You must specify a filesystem type with -t.», whats does this mean?
Mar 27, 2018 at 10:17
mount -o rw,remount -t ext4 /dev/block/vda /system , -t mean the type of file system in my example ext4
Mar 27, 2018 at 17:23
Try the following on the command prompt:
>adb remount >adb push framework-res_old.apk /system/framework-res.apk 8,749 2 2 gold badges 27 27 silver badges 38 38 bronze badges
answered Aug 4, 2012 at 15:00
121 1 1 silver badge 2 2 bronze badges
It should be adb root remount
Oct 2, 2018 at 20:45
Here is what worked for me. I was running an emulated Android 7.1.1 (Nougat) device.
On a terminal, I hit the following command. One thing to be noticed is the -writable-system flag
./emulator -writable-system -avd Nexus_6_API_25 -partition-size 280 ./adb shell su mount -o rw,remount -t ext4 /dev/block/vda /system All the changes that you do on the /system contents will survive a restart.
answered Jan 31, 2018 at 16:04
George Garcés George Garcés
159 1 1 silver badge 6 6 bronze badges
I checked with emulator and following worked.
- adb reboot
- adb root && adb remount && adb push ~/Desktop/hosts /system/etc/hosts
As mentioned above as well, execute second step in single shot.
answered Mar 29, 2019 at 10:27
11.1k 14 14 gold badges 92 92 silver badges 197 197 bronze badges
I had one console open for pushing and one for remounting. Remount, switch to the other terminal where you have the push line ready to submit, and submit it. That’s it.
Dec 5, 2022 at 22:03
Open terminal emulator on the phone: then
adb shell after that daemon is started
su mount -o rw,remount /mnt/sdcard then the read only is converted into the read-Write.
answered May 10, 2015 at 16:18
33 6 6 bronze badges
Sometimes you get the error because the destination location in phone are not exist. For example, some android phone external storage location is /storage/emulated/legacy instead of /storage/emulated/0 .
answered Jan 19, 2016 at 11:54
Geng Jiawen Geng Jiawen
8,924 3 3 gold badges 49 49 silver badges 37 37 bronze badges
mount -o rw,remount /dev/stl12 /system answered Sep 5, 2013 at 2:37
67 6 6 bronze badges
This worked for me #Mount as ReadOnly su -c "mount -o rw,remount /system" # Change Permission for file su -c "chmod 777 /system/build.prop" #Edit the file to add the property su -c "busybox vi /system/build.prop" # Add now service.adb.tcp.port=5678 # Reset old permissions su -c "chmod 644 /system/build.prop" # Mount as readonly again once done su -c "mount -o ro,remount /system" answered Apr 19, 2018 at 20:30
Ashwin Rayaprolu Ashwin Rayaprolu
31 1 1 bronze badge
I found this article from google, and thought I’d add the steps necessary on a Sony Xperia Z (4.2.2).
The Sony has a watchdog process which detects when you’ve changed ro to rw on / and /system (these are the only ones I was trying to modify) and possibly others.
The following was what I ran to perform the changes I was trying to achieve. I pasted these into a window, because removing the execute bit from /sbin/ric needs to be done quickly in order to stop it restarting itself. (I tried stop ric ; this doesn’t work — although it worked on a previous version of android on the phone).
pkill -9 ric; mount -o rw,remount -t rootfs / chmod 640 /sbin/ric mount -o rw,remount /system I modified the hosts file here, so this is the place you make the changes you need to the filesystem. To leave things the way we found them, do this:
mount -o ro,remount /system chmod 750 /sbin/ric mount -o ro,remount -t rootfs / At which point ric should automatically restart. (It restarted for me automatically.)