blocks|key|894817|text|这是从一个Android论坛上得到的，在那里我问了同样的问题。希望这对其他人有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|894818|在电话上的终端模拟器上：|894819|mount+-o+rw,remount+-t+yaffs2+/dev/block/mtdblock3+/system|code-block|syntax|javascript|894820|然后在cmd提示符下执行adb+push|offset|length|style|CODE|894821|entityMap^0|0|0|0|C|8|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@$K|U|L|V|M|N]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Got this off an Android forum where I asked the same question. Hope this helps somebody else.

On a terminal emulator on the phone:

<pre><code>mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
</code></pre>

Then on the cmd prompt, do the <code>adb push</code>

blocks|key|678088|text|并不是所有的手机和android版本都安装了相同的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678089|在重新挂载时限制选项将是最好的。|678090|只需重新装载为rw+(读/写)即可：|678091|#+mount+-o+rw,remount+/system|code-block|syntax|javascript|678092|完成更改后，重新挂载到ro+(只读)：|678093|#+mount+-o+ro,remount+/system|678094|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|S|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|T|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|V|8|@]|9|@]|A|$I|J]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

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):

<pre><code># mount -o rw,remount /system
</code></pre>

Once you are done making changes, remount to ro (read-only):

<pre><code># mount -o ro,remount /system
</code></pre>

blocks|key|678192|text|adb+remount|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|678193|对我来说很有效，而且似乎是最简单的解决方案。|unstyled|678194|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>adb remount
</code></pre>

works for me and seems to be the simplest solution.

blocks|key|678755|text|虽然我知道问题是关于真实设备的，但如果有人在仿真器中遇到了类似的问题，无论使用的是2017年2月的最新工具，仿真器都需要通过以下命令行启动：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678756|-writable-system|code-block|syntax|javascript|678757|使任何内容都可以写入/system。如果没有此标志，则任何remount或mount的组合都不允许写入/system。|offset|length|style|CODE|678758|使用该标志启动仿真器后，adb+root之后的单个adb+remount就足以获得推送到/system的权限。|678759|下面是我用来运行模拟器的命令行示例：|678760|./emulator+-writable-system+-avd+Nexus_5_API_25+-no-snapshot-load+-qemu|678761|-avd标志的值来自：|678762|./emulator+-list-avds|678763|entityMap^0|0|0|A|7|T|7|11|5|1F|7|0|C|8|P|B|18|7|0|0|0|0|4|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@$I|11|J|12|K|L]|$I|13|J|14|K|L]|$I|15|J|16|K|L]|$I|17|J|18|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@$I|1A|J|1B|K|L]|$I|1C|J|1D|K|L]|$I|1E|J|1F|K|L]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1H|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1I|8|@$I|1J|J|1K|K|L]]|9|@]|A|$]]|$1|U|3|V|5|D|7|1L|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|1M|8|@]|9|@]|A|$]]]|X|$]]

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:

<pre><code>-writable-system
</code></pre>

For anything to be writable to the <code>/system</code>. Without this flag no combination of <code>remount</code> or <code>mount</code> will allow one to write to <code>/system</code>.

After the emulator is launched with that flag, a single <code>adb remount</code> after <code>adb root</code> is sufficient to get permissions to push to <code>/system</code>.

Here's an example of the command line I use to run my emulator:

<pre><code>./emulator -writable-system -avd Nexus_5_API_25 -no-snapshot-load -qemu
</code></pre>

The value for the <code>-avd</code> flags comes from:

<pre><code>./emulator -list-avds
</code></pre>

blocks|key|678123|text|我认为最安全的方法是以读写方式重新挂载/system，使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678124|mount+-o+remount,rw+/system|code-block|syntax|javascript|678125|完成后，将其重新挂载为只读：|678126|mount+-o+remount,ro+/system|678127|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I think the safest way is remounting the /system as read-write, using:

<pre><code>mount -o remount,rw /system
</code></pre>

and when done, remount it as read-only:

<pre><code>mount -o remount,ro /system
</code></pre>

blocks|key|895614|text|adb+disable-verity
adb+reboot
adb+root
adb+remount|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|895615|这对我来说是可行的，也是最简单的解决方案。|unstyled|895616|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>adb disable-verity
adb reboot
adb root
adb remount
</code></pre>

This works for me, and is the simplest solution.

blocks|key|678313|text|在我的三星galaxy迷你S5570上(在手机上扎根之后)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678314|首先，我以root用户的身份运行：|678315|systemctl+start+adb|code-block|syntax|javascript|678316|作为普通用户：|678317|adb+shell+
su+|678318|在触摸屏上授予root权限|678319|mount+|678320|列出我们拥有的所有挂载点，我们可以看到，在我的示例中，/dev/stl12作为ro+(仅限就绪)挂载在/system上，因此我们只需执行以下操作：|678321|mount+-o+rw,remount+/dev/stl12+/system|678322|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|11|8|@]|9|@]|A|$]]|$1|O|3|P|5|F|7|12|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|13|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|14|8|@]|9|@]|A|$G|H]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

On my Samsung galaxy mini S5570 (after got root on cellphone):

Fist, as root, I ran:

<pre><code>systemctl start adb
</code></pre>

as a normal user: 

<pre><code>adb shell 
su 
</code></pre>

Grant root permissions on touch screen

<pre><code>mount 
</code></pre>

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: 

<pre><code>mount -o rw,remount /dev/stl12 /system
</code></pre>

blocks|key|678223|text|在命令提示符下尝试执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678224|>adb+remount
>adb+push+framework-res_old.apk+/system/framework-res.apk|code-block|syntax|javascript|678225|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Try the following on the command prompt:

<pre><code>&gt;adb remount
&gt;adb push framework-res_old.apk /system/framework-res.apk
</code></pre>

blocks|key|678796|text|以下是对我起作用的方法。我运行的是一个模拟的Android7.1.1+(Nougat)设备。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678797|在终端上，我点击了以下命令。需要注意的一点是-writable-system标志|678798|./emulator+-writable-system+-avd+Nexus_6_API_25++-partition-size+280|code-block|syntax|javascript|678799|在另一个选项卡上|678800|./adb+shell
su
mount+-o+rw,remount+-t+ext4+/dev/block/vda+/system|678801|您对/system内容所做的所有更改在重新启动后仍然有效。|678802|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

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

<pre><code>./emulator -writable-system -avd Nexus_6_API_25 -partition-size 280
</code></pre>

On another tab

<pre><code>./adb shell
su
mount -o rw,remount -t ext4 /dev/block/vda /system
</code></pre>

All the changes that you do on the /system contents will survive a restart.

blocks|key|678456|text|在手机上打开终端模拟器:然后|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678457|adb+shell|code-block|syntax|javascript|678458|在启动该守护进程之后|678459|su
mount+-o+rw,remount+/mnt/sdcard|678460|则将只读转换为读写。|678461|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Open terminal emulator on the phone:
then

<pre><code>adb shell
</code></pre>

after that daemon is started

<pre><code>su
mount -o rw,remount /mnt/sdcard
</code></pre>

then the read only is converted into the read-Write.

blocks|key|895099|text|mount+-o+rw,remount+/dev/stl12+/system|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|895100|对我很管用|unstyled|895101|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>mount -o rw,remount /dev/stl12 /system
</code></pre>

works for me

blocks|key|678810|text|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"|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|678811|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>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"
</code></pre>

blocks|key|895174|text|我从google找到了这篇文章，我想我应该在Sony+Xperia+Z+(4.2.2)上添加必要的步骤。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|895175|索尼有一个看门狗进程，它会检测你在/和/system上将ro更改为rw的时间(这些是我唯一想要修改的)，也可能是其他的。|895176|以下是我运行以执行我试图实现的更改的内容。我将它们粘贴到一个窗口中，因为需要快速地从/sbin/ric中删除执行位，以阻止它自己重新启动。(我试过stop+ric；这不起作用--尽管它可以在手机上的前一个版本的安卓上运行)。|offset|length|style|CODE|895177|pkill+-9+ric;+mount+-o+rw,remount+-t+rootfs+/
chmod+640+/sbin/ric
mount+-o+rw,remount+/system|code-block|syntax|javascript|895178|我在这里修改了hosts文件，因此这里是您对文件系统进行所需更改的地方。要让事情保持原样，请执行以下操作：|895179|mount+-o+ro,remount+/system
chmod+750+/sbin/ric
mount+-o+ro,remount+-t+rootfs+/|895180|此时ric应自动重新启动。(它会自动为我重新启动。)|895181|entityMap^0|0|0|21|8|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@$F|Z|G|10|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|11|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|12|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|14|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|V|$]]

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 <code>stop ric</code>; this doesn't work - although it worked on a previous version of android on the phone).

<pre><code>pkill -9 ric; mount -o rw,remount -t rootfs /
chmod 640 /sbin/ric
mount -o rw,remount /system
</code></pre>

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:

<pre><code>mount -o ro,remount /system
chmod 750 /sbin/ric
mount -o ro,remount -t rootfs /
</code></pre>

At which point ric should automatically restart. (It restarted for me automatically.)

blocks|key|895310|text|对Jan+Bergström的回答补充一点:因为Android是基于Linux的系统，并且Linux中的路径包含正斜杠(../)，所以在使用push命令时，请使用"/“来定义Android设备中的目标路径。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|895311|例如，命令如下:+adb+push+C:\Users\admin\Desktop\1.JPG+sdcard/pictures/|895312|请注意，在这里，反斜杠用于定义要从windows+PC推送的文件的源路径，而正斜杠用于定义目标路径，因为Android是基于Linux的系统。您不必以root用户的身份使用此命令，而且，它在生产设备上运行得很好。|895313|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Adding a little bit more to Jan Bergström's answer: Because Android is a Linux based system, and the path in Linux contains forward slashes(../), while using push command, use "/" to define destination path in the Android device.

For Example, the command goes: adb push C:\Users\admin\Desktop\1.JPG sdcard/pictures/

Notice that here, back slashes are used to define source path of the file to be pushed from windows PC and forward slashes are used to define destination path because Android is a Linux based system. You don't have to act as a root to use this command and also, it works perfectly fine on production devices.

blocks|key|895354|text|有时你会收到错误，因为电话中的目标位置不存在。例如，一些安卓手机的外部存储位置是/storage/emulated/legacy而不是/storage/emulated/0。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|895355|entityMap^0|14|O|1V|J|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|M|8|@]|D|@]|E|$]]]|G|$]]

Sometimes you get the error because the destination location in phone are not exist. For example, some android phone external storage location is <code>/storage/emulated/legacy</code> instead of <code>/storage/emulated/0</code>.

blocks|key|895514|text|同样，必须用挂载/system的代码解压和重新打包initrc.img和编辑init文件|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|895515|entityMap^0|12|4|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

it sames that must extract and repack initrc.img and edit <code>init</code> file with the code of mount /system

blocks|key|895428|text|如果复制只读文件失败，您可以尝试在根目录中找到原始文件，并使用根文本编辑器(最好是RB文本编辑器)对其进行修改，它随ROM工具箱应用程序一起提供。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|895429|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If there's a failure in copying the read-only file you can try locating the original file in the root directory and modify it with a root text editor (preferably) RB text editor, it comes with ROM Toolbox app.

blocks|key|678692|text|以root用户身份在终端仿真程序中尝试执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678693|restorecon+-v+-R+/data/media|code-block|syntax|javascript|678694|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Try this in a Terminal Emulator as root:

<pre><code>restorecon -v -R /data/media
</code></pre>

blocks|key|678894|text|在我的例子中，我使用了命令adb+push+~/Desktop/file.txt+~/sdcard/|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|678895|我把它改成了~/Desktop/file.txt+/sdcard/，然后它就起作用了。|678896|请确保断开并重新连接电话。|678897|entityMap^0|M|S|0|6|R|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

In my case I was using the command adb push <code>~/Desktop/file.txt ~/sdcard/</code>

I changed it to <code>~/Desktop/file.txt /sdcard/</code> and then it worked.

Make sure to disconnect and reconnect the phone.

blocks|key|678914|text|我只需要这个：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|678915|su+-c+"mount+-o+rw,remount+/system"|code-block|syntax|javascript|678916|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I just only needed this:
<pre><code>su -c &quot;mount -o rw,remount /system&quot;
</code></pre>

I recently rooted my Droid X and everything seems to be working perfectly. I made some changes to <code>build.prop</code> and when I do <code>adb push build.prop /system/</code> I get the following error: <code>failed to copy 'c:\build.prop' to '/system//build.prop': Read-only file system</code>.

How can I fix this?

Read only file system on Android

文件系统

Android

Linux

我最近在我的Droid上建立了根目录，一切似乎都运行得很完美。我对build.prop做了一些更改，当我执行adb push build.prop /system/时，我得到了以下错误：failed to copy 'c:\build.prop' to '/system//build.prop': Read-only file system。我该如何解决这个问题呢？

问Android上的只读文件系统
EN

回答 20

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android上的只读文件系统EN

回答 20

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android上的只读文件系统
EN