经验5452 米
在线时间791 小时
版本6.12.16
机型小米手机3/4 WCDMA版
签到次数50
MIUI版本6.12.16
通过手机发布
魅族Mx4 Unlock Bootloader装载程序教程
魅族Mx4解锁引导装载程序教程我从forum.重写本教程:
解锁的引导加载程序魅族Mx4你需要ADT包***和配置。从这个链接下载ADT的包:/sdk/index.html
以后一旦完成了配置正确,那么你可以连接你的设备,使USB调试选项。
1。下载Modaco Superboot文件魅族Mx4从这个链接:[url=]http://downloadsafe.org/file/0YgX7[/url],并保存到你的电脑。
教程视频:下载文件的简单方法[url=]http://how-/10[/url]
2。下载完成后,通过右击并提取提取它。
3。在你的设备,点击设置&开发人员选项&打开USB调试。
4。设备插入你的电脑通过USB电缆。
5。打开superboot文件夹,我们只是提取(直到你看到fastboot-windows里面的文件夹),然后按住shift键在你的电脑上,右击任何空白区域。
6。现在,选择打开命令窗口。
7。在命令提示符中,输入以下与输入的每一行。
adb-windows重新启动引导程序,等待设备(重新启动)fastboot-windows oem解锁*如果它会停留在等待设备在这里,在你的电脑上下载并***PDANet,一旦***完毕,然后拔掉插头装置在修复它,看看。
一旦它运行的设备应显示一个屏幕问你如果你确定。使用音量按钮单击yes。设备将回到引导装载程序屏幕底部但说解锁。
魅族Mx4棒棒糖5.0更新教程
魅族Mx4棒棒糖更新教程我从forum.重写本教程:
魅族Mx4的用户现在可以更新他们的手机使用自定义ROM Android 5.0棒棒糖。新的Android 5.0棒棒糖有许多新特点:
- 4 x的性能改进。
----电池保护功能,延长设备使用90分钟。
-它有一个更快、更顺畅的和更强大的计算体验。
----支持64位的soc使用手臂,x86,mips处理器内核。
----OpenGL ES 3.1和Android扩展包使Android移动图形把它的前沿与桌面和控制台类性能。
----响应,自然运动、现实的灯光和阴影,和熟悉的视觉元素更容??导航你的设备。
----更智能的排名基于从和他们的通知类型的通信。看到你所有的通知在一个地方利用屏幕的顶部。
----新设备来帮助保护数据加密自动打开设备丢失或被盗。
----SELinux执行所有应用程序意味着更好的防范漏洞,恶意软件。
----先进的视频技术支持HEVC主要配置文件允许UHD 4 k 10位视频回放,以及硬件视频解码节约能源和提高hl支持流媒体。
----和其他很酷的特性。
这里有一些更多的方面,用户应该知道尝试自定义ROM之前:----用户需要有适当的备用设备上的个人数据。
----手机应该有至少80%的电池。
----用户也需要确保启用USB调试设备。
----在***过程中,如果设备被困在引导,用户可以执行擦除缓存分区和擦dalvik之前重启设备。
Tutorial1。下载Android 5.0棒棒糖ROM魅族Mx4从下面的链接:ROM文件大小的大,所以我把文件分成3部分:
ROM第1部分:[url=]下载[/url]或[url=]http://goo.gl/7pyL97[/url]
ROM第2部分:[url=]下载[/url]或[url=]http://goo.gl/ffHU2x[/url]
ROM3部分:[url=]下载[/url]或[url=]http://goo.gl/l1zKh5[/url]
教程视频:简单的方法下载ROM=[url=]http://how-/10[/url]
结合三部分文件:把所有的零件到相同的文件夹,然后双击ROM-Part1。rar,所有的其他部分将自动解压缩和合并。如果出现问题,也许因为ROM在下载过程中有损坏,你可以尝试重新下载ROM。
2。***魅族Mx4ROM管理。把它从谷歌商店,然后*** clockwork mod recovery。您也可以使用ROM***应用程序从JRummy应用Inc .(把它从谷歌play商店)。
3。你的魅族Mx4连接到你的电脑使用USB电缆的信息。复制“罗。”zip文件下载到SD记忆卡。
4。重启你的设备使用罗经理在恢复模式。就在恢复模式下,去罗经理并选择备份/恢复备份您的信息。
5。从恢复菜单中总共数据擦除(包括Delvik缓存)。当完成后,回到复苏从SD卡主菜单,然后选择“闪速存储器。导航的位置你复制“罗。邮政”文件和遵循的方向***Android 5.0魅族Mx4棒棒糖。尽快***,重启你的魅族Mx4设备,给你,你刚升级到新的Android 5.0棒棒糖。
翻译可能有点不当，如果看的懂得就试试吧
这是原地址：http://www./mp3-0/meizu-mx4-6627.html
(235.88 KB, 下载次数: 28)
18:29 上传
(218.57 KB, 下载次数: 18)
18:29 上传
(173.68 KB, 下载次数: 26)
18:29 上传
(221.73 KB, 下载次数: 16)
18:29 上传
分享到微信朋友圈
打开微信，点击底部的“发现”，使用 “扫一扫” 即可将网页分享到我的朋友圈。
经验620 米
在线时间96 小时
版本4.11.7
积分 804, 距离下一级还需 1196 积分
积分 804, 距离下一级还需 1196 积分
机型未知设备
签到次数40
MIUI版本4.11.7
来自网页版
什么情况，是真的还是假的？？？
经验141 米
在线时间101 小时
版本4.2.14
积分 344, 距离下一级还需 156 积分
积分 344, 距离下一级还需 156 积分
机型HTC One X
签到次数13
MIUI版本4.2.14
通过手机发布
靠，真要试试
经验5452 米
在线时间791 小时
版本6.12.16
机型小米手机3/4 WCDMA版
签到次数50
MIUI版本6.12.16
通过手机发布
在线时间6 小时
积分 107, 距离下一级还需 93 积分
积分 107, 距离下一级还需 93 积分
机型小米手机5
MIUI版本6.8.4
来自网页版
如果是真的，那就爽了。
经验112 米
在线时间5 小时
积分 115, 距离下一级还需 85 积分
积分 115, 距离下一级还需 85 积分
来自网页版
谁去尝试一下
经验288 米
在线时间118 小时
版本4.9.12
积分 470, 距离下一级还需 30 积分
积分 470, 距离下一级还需 30 积分
机型魅族 MX
签到次数48
MIUI版本4.9.12
来自网页版
以刷。正在试用，暂无BUG
经验5452 米
在线时间791 小时
版本6.12.16
机型小米手机3/4 WCDMA版
签到次数50
MIUI版本6.12.16
来自网页版
以刷。正在试用，暂无BUG
能发个截图吗
在线时间0 小时
版本4.6.13
积分 77, 距离下一级还需 123 积分
积分 77, 距离下一级还需 123 积分
机型小米手机1/1S
MIUI版本4.6.13
来自网页版
真的假的啊？？
在线时间6 小时
积分 107, 距离下一级还需 93 积分
积分 107, 距离下一级还需 93 积分
机型小米手机5
MIUI版本6.8.4
来自网页版
以刷。正在试用，暂无BUG
可以即时分享一下刷机后的使用么
小火箭勋章
神舟11号 话题活动
MIUI 300周
MIUI 300周更新纪念勋章
MIUI 7纪念勋章
MIUI五周年
MIUI五周年纪念勋章
已关注微信
已关注极客秀微信
关注腾讯微博
已关注腾讯微博
关注新浪微博
已关注新浪微博
Copyright (C) 2016 MIUI
京ICP备号 | 京公网安备34号 | 京ICP证110507号最小bootloader的实现,完整源代码_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
最小bootloader的实现,完整源代码
上传于||文档简介
&&bootloader的完整实现
阅读已结束，如果下载本文需要使用5下载券
想免费下载本文？
定制HR最喜欢的简历
下载文档到电脑，查找使用更方便
还剩33页未读，继续阅读
定制HR最喜欢的简历
你可能喜欢From OSDev Wiki
A bootloader is a program written to load a more complex . Implementation details are gathered in
The boot loader ultimately has to:
Bring the kernel (and all the kernel needs to bootstrap) into memory
Provide the kernel with the information it needs to work correctly
Switch to an environment that the kernel will like
Transfer control to the kernel
On the x86, the boot loader runs in . Consequently it has easy access to BIOS resources and functions. Therefore it's a good place to perform memory map detection, detection of available video modes, loading of additional files, etc. The boot loader will collect this information and present it in a way the kernel will be able to understand.
The bits of your kernel are somewhere on some disk (presumably the booting disk, but this is not mandatory). Question is: where on the disk? Is it a regular file on a
floppy? Is it a collection of consecutive sectors in the "reserved area" of the FAT12 floppy (in which case you may need a dedicated tool to format the disk and install the kernel on it)? Or is the floppy simply left unformatted and the kernel pasted directly with a disk image tool?
All the above options are possible. Maybe the one I'd choose myself would be to reserve enough space on a FAT12 floppy to store the list of sectors used by the kernel file. The "advantage" of being fully-FAT12 is that you don't need to re-write the bootsector every time you rewrite the kernel.
What needs to be loaded mainly depends on what's in your kernel. Linux, for instance, requires an additional 'initrd' file that will contain the 'initialization process' (as user level). If your kernel is modular and if Filesystems are understood by some modules, you need to load the modules along with the kernel. Same goes for 'microkernel services' like disk/files/memory services, etc.
Some kernels require some extra information to run. For example, you'll need to tell Linux the root partition to start from. Pretty useful information to have is a map of the address space - effectively a map of where physical memory is and where it's not. Other popular queries regard video modes.
In general, anything that involves a BIOS call is easier to do in , so better do them while in real mode than trying to come back to real mode for a trip later.
Most kernels require protected mode. For these kernels you'll have to
before giving control to the kernel.
It's common for the loader to keep interrupts disabled (the kernel will enable them later when an IDT is properly set up).
Note: take time to think about whether or not you'll enable paging here. Keep in mind that debugging paging initialization code without the help of exception handlers may quickly become a nightmare!
Virtually any bootloader follows a common design.
A single stage bootloader consists of a single file that is loaded entirely by the BIOS. This image then performs the steps described above to start the kernel.
However, on the x86 you are usually limited to 512 bytes for a first stage (An exception is no-emulation ), which is not much. Also, a lot of this size may be dedicated to bios structures and
headers, which leaves even less space to work with
A two-stage bootloader actually consists of two bootloaders after each other. The first being small with the sole purpose of loading the second one. The second one can then contain all the code needed for loading the kernel.
uses two (or arguably, three) stages.
Another way to avoid the 512-byte barrier is to split the bootloader in two parts, where the first half (512 bytes) can load the rest. This can be achieved by inserting a '512-bytes' break in the ASM code, making sure the rest of the loader is put after the bootsector.
The easiest way to boot another OS is a mechanism called chainloading. Windows stores something akin to a second-stage bootloader in the boot sector of the partition it was installed in. When installing Linux, writing e.g. LILO or GRUB to the partition boot sector instead of the MBR is also an option. Now, the thing your MBR bootsector can do is to relocate itself (copying from 0xc00 to, traditionally, 0x0), parse the partition table, display some kind of menu and let the user choose which partition to boot from. Then, your (relocated) MBR bootsector would load that partition boot sector to 0xc00, and jump there. The partition boot sector would be none the wiser that there already was a bootsector loaded before, and could actually load yet another bootsector - which is why it's called chainloading.
You see that with displaying a menu in some intelligible way and accepting keystrokes, such a multi-option bootloader can get quite complex rather quickly. We didn't even touch the subject of booting from extended partitions, which would require sequentially reading and parsing multiple extended partition tables before printing the menu.
Taken to the extreme, bootmanagers like that can become as complex as a simple OS,
being a good example: It offers reading from various filesystems, booting
kernels, chainloading, loading initrd
from Carnegie Mellon Computer Science Department
In other languages
