博客正式落户51CTO
2012-05-06 15:39
239 查看
G1到手,是已经经Root过的,刷的是hiapk版,由于radio还是1_22_12_29,在使用耳机是系统很不稳定。首先将radio刷到了2_22_19_26I,然后将SPL刷成ADP1的,这样就支持fastboot。fastboot要比recovery mode厉害啊,前者是和bootloader(SPL)通信来刷机,而后者是要进入linux的,所以fastboot是最强大的,即使你的linux坏掉,进入不了recovery mode,也可以刷机。
担心变砖,看这个吧
引用Like Disconnect said, it's possible, but regular operations
(developing apps, flashing supported or home-built images) and minor
mistakes around those aren't supposed to brick an ADP1.
To entirely brick one, you need to end up in both the following
situations at the same time (a bit simplified):
-bootloader without fastboot support.
-non-reachable or non-functional recovery.
The most likely way to end up with the first one is to flash a
bootloader with fastboot disabled, or a radio that's incompatible with
the bootloader (or a broken variant of either of those). Normal ADP1
operation doesn't involve flashing the bootloader, and official ADP1
radio images are compatible with the ADP1 bootloader. Note that as an
added safeguard the ADP1 bootloader doesn't allow to flash the
bootloader or the radio via fastboot.
Not being able to reach recovery is essentially a broken bootloader or
a broken radio, and the safeguards around the bootloader and the radio
mentioned above also apply here.
A reachable non-functional recovery is a much more likely scenario if
you're doing development in recovery itself, but in that case you're
expected to be flashing your device through fastboot, i.e. you still
have a way to flash an official (functional) recovery.
I have my guess of what the most likely way would be to brick an ADP1
while following the normal steps, but I'm also not going to post it
here.
Please don't try to brick your device. Really, please don't.
adp: http://www.htc.com/www/support/android/adp.html adp bootloader spl: http://forum.xda-developers.com/showthread.php?t=455860
担心变砖,看这个吧
引用Like Disconnect said, it's possible, but regular operations
(developing apps, flashing supported or home-built images) and minor
mistakes around those aren't supposed to brick an ADP1.
To entirely brick one, you need to end up in both the following
situations at the same time (a bit simplified):
-bootloader without fastboot support.
-non-reachable or non-functional recovery.
The most likely way to end up with the first one is to flash a
bootloader with fastboot disabled, or a radio that's incompatible with
the bootloader (or a broken variant of either of those). Normal ADP1
operation doesn't involve flashing the bootloader, and official ADP1
radio images are compatible with the ADP1 bootloader. Note that as an
added safeguard the ADP1 bootloader doesn't allow to flash the
bootloader or the radio via fastboot.
Not being able to reach recovery is essentially a broken bootloader or
a broken radio, and the safeguards around the bootloader and the radio
mentioned above also apply here.
A reachable non-functional recovery is a much more likely scenario if
you're doing development in recovery itself, but in that case you're
expected to be flashing your device through fastboot, i.e. you still
have a way to flash an official (functional) recovery.
I have my guess of what the most likely way would be to brick an ADP1
while following the normal steps, but I'm also not going to post it
here.
Please don't try to brick your device. Really, please don't.
adp: http://www.htc.com/www/support/android/adp.html adp bootloader spl: http://forum.xda-developers.com/showthread.php?t=455860
相关文章推荐
- 正式启用51CTO博客
- 正式落户CSDN博客
- 启用博客,落户51CTO!
- 2013.1.29正式落户csdn博客
- 红坚果(RedNut)个人博客正式落户博客园
- 正式启用51CTO博客
- 「博客产品记」“51CTO订阅专栏”小程序正式和大家见面了
- 第一篇:今天正式开始写博客~哇哈哈~~~
- 此博客从今日起正式启用
- python解析51cto博客用户的相关信息
- IT民工正式开始写技术博客了
- 51CTO稿酬标准2016版正式发布!
- 纪念csdn博客今天正式开通
- 我的博客正式成立了,本博客记录每天的点点滴滴,学习到的知识和大家一起分享,希望大家多多包涵。
- 51CTO博客带给我的…知识,朋友,快乐[博友话题] 推荐
- 将博客搬至51CTO
- 开了51cto博客
- 个人博客正式开通
- 使用 windows live writer 上传51cto博客
- 本人博客已经转到简书,不再更新51cto,谢谢大家。