![[-]](https://www.chinaphonearena.com/forum/images/collapse.png "[-]")
2014-09-28, 17:17
I won't go into a detailed discussion of the theory of the android boot process to avoid O.T., that is why my explanation was indeed a bit 'generic'.
Please have a look at
You will see lk.bin at the same level as uboot, which in effect is the bootloader process. Boot.img is on slide 9 as it is where the complete kernel gets loaded.
No need for getting down to who's right or not, maybe the truth is somewhere in the middle, it doesn't matter really. What I was saying is what in my experience are the steps for bringing a phone back from dead.
first part: preloader and pre-boot partitions, logo, secro, lk or uboot, mbr, ebr, recovery etc.
second part: boot.img, where /system /proc and other important folders are setup for the kernel.
third part: data and cache, where you're apps and data are.
extra: nvram which not only contains imei, but also radio, bt and wifi configuration specifics.
this is just to simplify the process so that any one can understand it and get the idea of what is important to bring back your phone from a brick state.
Please have a look at
You will see lk.bin at the same level as uboot, which in effect is the bootloader process. Boot.img is on slide 9 as it is where the complete kernel gets loaded.
No need for getting down to who's right or not, maybe the truth is somewhere in the middle, it doesn't matter really. What I was saying is what in my experience are the steps for bringing a phone back from dead.
first part: preloader and pre-boot partitions, logo, secro, lk or uboot, mbr, ebr, recovery etc.
second part: boot.img, where /system /proc and other important folders are setup for the kernel.
third part: data and cache, where you're apps and data are.
extra: nvram which not only contains imei, but also radio, bt and wifi configuration specifics.
this is just to simplify the process so that any one can understand it and get the idea of what is important to bring back your phone from a brick state.
