h*e
10 楼
系统字体在/system下,nook系统会监视/system,一旦检测到/system被修改,就会回
到2.0.0。我是觉得nook hd+没有任何改字体的必要,有方便得多的自定义字体方案。
自带的reader也没有Mantano好(加载中文字体太慢)。你要非想改,先准备好字体(
一般是用fontcreator把英文字体与中文字体合并)然后:
Modifying System Files on the HD/HD+
Ordinarily you cannot modify system files on these devices because they will
detect the change and reset themselves back to factory stock, wiping out
all your data at the same time. But there is a safe way to do it if you are
rooted.
The HD/HD+ has a manifest file included in the boot files that has a listing
of each file that is supposed to be in /system and a checksum of each file.
On boot, it reads the files in /system and makes sure each file that is
there is on the list and matches the checksum. It ignores directories,
symlinks and missing files. If one is added or has the wrong checksum, it
stops and tries to boot again. If it reboots 8 times in a row without
completing the boot, the automatic reset feature kicks in and your device is
formatted and the factory ROM is reinstalled.
So you can see that missing files are OK and symlinks are OK. So if you want
to modify a system file, first copy it to /data somewhere, delete the
original, and make a symlink in /system to replace the deleted file. The
symlink points to the file copied to /data. But be careful, some files, like
framework-res.apk, are being used all the time and if you delete it, even
temporarily, the system goes crazy.
The scheme that someone0 and I use is to mimic /system under /data/su so
that the structures are the same to avoid confusion. For example, if you
wanted to modify build.prop, it would be copied to /data/su/system/build.
prop and the symlink would point there. Since build.prop is not used very
often, it is safe to now modify it however you want. But be careful, some
settings there are vital, like hardware rotation. Mess with that and things
will go all wonky on the next reboot.
Here are the specific commands to make this happen using build.prop as an
example:
1. Use your root file manager to copy /system/build.prop to /data/su/system/
build.prop. Set the file's permissions to match the original.
2. Delete /system/build.prop also using your root file manager
3. Set up Terminal Emulator. Start the program and type su enter. After you
allow superuser access, the prompt turns to #
4. Type the following command at the # prompt (without the quotes):
"mount -o remount,rw /system"
5. Then this command:
"ln -s /data/su/system/build.prop /system/build.prop"
(That first letter is a lower case L)
6. Then this command:
"mount -o remount,ro /system"
You are done. You can now modify build.prop in /data any way you want and
the system will not reset.
But before you do this mod or any other system file mod, I recommend you
have backed up your system using CWM as described in the previous section.
That way if you did not get it right somehow and it starts to reset, you can
insert your CWM card to stop the rebooting and selectively restore /system
and try again.
One side benefit of doing this build.prop mod is if B&N tries to update you
in the future, it will fail because it cannot verify your build.prop because
it is missing. And, in my experience, it does not try again.
【在 w*****g 的大作中提到】
: 我就是要换系统子体让reader完美啊。
:
: ★ 发自iPhone App: ChineseWeb 7.8
到2.0.0。我是觉得nook hd+没有任何改字体的必要,有方便得多的自定义字体方案。
自带的reader也没有Mantano好(加载中文字体太慢)。你要非想改,先准备好字体(
一般是用fontcreator把英文字体与中文字体合并)然后:
Modifying System Files on the HD/HD+
Ordinarily you cannot modify system files on these devices because they will
detect the change and reset themselves back to factory stock, wiping out
all your data at the same time. But there is a safe way to do it if you are
rooted.
The HD/HD+ has a manifest file included in the boot files that has a listing
of each file that is supposed to be in /system and a checksum of each file.
On boot, it reads the files in /system and makes sure each file that is
there is on the list and matches the checksum. It ignores directories,
symlinks and missing files. If one is added or has the wrong checksum, it
stops and tries to boot again. If it reboots 8 times in a row without
completing the boot, the automatic reset feature kicks in and your device is
formatted and the factory ROM is reinstalled.
So you can see that missing files are OK and symlinks are OK. So if you want
to modify a system file, first copy it to /data somewhere, delete the
original, and make a symlink in /system to replace the deleted file. The
symlink points to the file copied to /data. But be careful, some files, like
framework-res.apk, are being used all the time and if you delete it, even
temporarily, the system goes crazy.
The scheme that someone0 and I use is to mimic /system under /data/su so
that the structures are the same to avoid confusion. For example, if you
wanted to modify build.prop, it would be copied to /data/su/system/build.
prop and the symlink would point there. Since build.prop is not used very
often, it is safe to now modify it however you want. But be careful, some
settings there are vital, like hardware rotation. Mess with that and things
will go all wonky on the next reboot.
Here are the specific commands to make this happen using build.prop as an
example:
1. Use your root file manager to copy /system/build.prop to /data/su/system/
build.prop. Set the file's permissions to match the original.
2. Delete /system/build.prop also using your root file manager
3. Set up Terminal Emulator. Start the program and type su enter. After you
allow superuser access, the prompt turns to #
4. Type the following command at the # prompt (without the quotes):
"mount -o remount,rw /system"
5. Then this command:
"ln -s /data/su/system/build.prop /system/build.prop"
(That first letter is a lower case L)
6. Then this command:
"mount -o remount,ro /system"
You are done. You can now modify build.prop in /data any way you want and
the system will not reset.
But before you do this mod or any other system file mod, I recommend you
have backed up your system using CWM as described in the previous section.
That way if you did not get it right somehow and it starts to reset, you can
insert your CWM card to stop the rebooting and selectively restore /system
and try again.
One side benefit of doing this build.prop mod is if B&N tries to update you
in the future, it will fail because it cannot verify your build.prop because
it is missing. And, in my experience, it does not try again.
【在 w*****g 的大作中提到】
: 我就是要换系统子体让reader完美啊。
:
: ★ 发自iPhone App: ChineseWeb 7.8
w*g
13 楼
原来如此,不仅查文件名,还查checksum,太变了。
昨天就是遭遇8次重启。
★ 发自iPhone App: ChineseWeb 7.8
★ 发自iPhone App: ChineseWeb 7.8
【在 h****e 的大作中提到】
: 系统字体在/system下,nook系统会监视/system,一旦检测到/system被修改,就会回
: 到2.0.0。我是觉得nook hd+没有任何改字体的必要,有方便得多的自定义字体方案。
: 自带的reader也没有Mantano好(加载中文字体太慢)。你要非想改,先准备好字体(
: 一般是用fontcreator把英文字体与中文字体合并)然后:
: Modifying System Files on the HD/HD+
: Ordinarily you cannot modify system files on these devices because they will
: detect the change and reset themselves back to factory stock, wiping out
: all your data at the same time. But there is a safe way to do it if you are
: rooted.
: The HD/HD+ has a manifest file included in the boot files that has a listing
昨天就是遭遇8次重启。
★ 发自iPhone App: ChineseWeb 7.8
★ 发自iPhone App: ChineseWeb 7.8
【在 h****e 的大作中提到】
: 系统字体在/system下,nook系统会监视/system,一旦检测到/system被修改,就会回
: 到2.0.0。我是觉得nook hd+没有任何改字体的必要,有方便得多的自定义字体方案。
: 自带的reader也没有Mantano好(加载中文字体太慢)。你要非想改,先准备好字体(
: 一般是用fontcreator把英文字体与中文字体合并)然后:
: Modifying System Files on the HD/HD+
: Ordinarily you cannot modify system files on these devices because they will
: detect the change and reset themselves back to factory stock, wiping out
: all your data at the same time. But there is a safe way to do it if you are
: rooted.
: The HD/HD+ has a manifest file included in the boot files that has a listing
相关阅读
android.process.acore 疯狂运行,怎么办ATT真流氓2款新iPhone亮相, 9.20开卖, 指纹系统太给力了!(手机+8寸pad) vs 大屏幕手机请教版上达人,哪里下载garmin的英国地图啊,谢谢有没有一对多的蓝牙耳机方案? (转载)爸妈在国内用iphone的问题比较烂。 (转载)安卓哪款机子电池最强看了眼5S的相机,直入了。金色iphone 5s会在中国大卖的新ip下周五才开卖,现在就在店外排队的果粉怎么办apple的宣传能力还是很好的..iphone 5S no NFC?n7下一代4gb内存了果子竟然没有发布retina iPad mini?2T装满的同学 能再分享一下么? 谢谢。一件事情证明果子的贪婪和无奈传闻iPod touch今年不更新 (转载)iphone5s的指纹可不可以这么破解